A group controller closes the month with inputs from three subsidiaries. One uses a different chart of accounts. Another reports in a different currency. Two subsidiaries recorded opposite sides of the same transaction in different periods. By the time the group numbers are ready, the FP&A team has already started its next forecast using a preliminary file.
Corporate performance management software, often called CPM, can connect consolidation, reporting, and planning across a group. Vendors use the label for different combinations of those functions. The best place to start is with the boundary where your teams lose time or confidence. For many groups, that is the handoff from local close to approved group results and then to management reporting.
Trace one number through the group
Pick a figure that appears in both statutory or group reporting and the management pack, such as revenue or operating expenses. Find the source trial balance for each entity, the mapping into group accounts, the adjustments, and the final number. Record how long it takes to explain the figure and who needs to help.
A group account map translates local account codes into a common reporting structure. It needs an owner, an effective date, and a way to deal with new accounts. Ask the vendor to import a trial balance that contains an unmapped account. Check whether the entity can correct the problem, whether the submission is held for review, and how the group controller sees the status.
Test an adjustment that applies at group level only. The finance team should be able to explain why local results differ from consolidated results and identify the supporting record. A reviewer needs to know who created and approved the adjustment and which periods it affects. Ask to see that history from the published report.
Use intercompany differences to test consolidation
A clean trial balance import says little about consolidation. Give two entities a real-looking intercompany transaction with different amounts or dates. For example, one subsidiary may record an invoice at month-end while the other records the corresponding cost the following month. Ask both teams to investigate through the platform.
Separate three steps in the demonstration. First, the team identifies the difference. Second, the responsible owner resolves it or explains why it remains. Third, the group applies the approved elimination or adjustment. Check whether the system gives the owners enough transaction detail to work together and lets the group reviewer distinguish an open discrepancy from a resolved one.
Add a reporting currency test when the group needs it. Use the rates and treatment approved by your finance team. Ask the platform to show the rate source and version and to reproduce a previous close. If different reports use different rate assumptions, make sure the labels and documentation let a reviewer understand the result.
Oracle’s Financial Consolidation and Close documentation is one example of a product offering built around financial consolidation and close administration. Use official product documentation to confirm the scope of any suite, then test the particular controls and data structure your group requires.
Watch what happens when the close slips
A close workflow needs to describe work people can act on. A dashboard may show that a subsidiary is late. The useful question is whether the group can see what is blocking the submission and who can resolve it. Run an incomplete submission with a failed validation and a missing approval. Ask the entity accountant, group controller, and reviewer to find their next action.
Then reopen an entity after group review. The platform should show which outputs depend on the revised submission and where another review is required under your process. Ask what happens if a report was already circulated. A version label and publication timestamp make it easier to tell which results were available at a particular meeting.
Check access by role and by entity. Local accountants may need full access to their own submission and limited visibility across the group. Reviewers may need access to consolidated results and supporting records. Test those permissions by signing in as each role. Include exported files and scheduled reports in the review, since those are common ways financial information leaves the application.
Connect planning to approved actuals
Planning teams need clear timing and definitions when they refresh actuals. A draft consolidation can help with early discussions. The approved forecast should identify the set of actuals it uses. Ask the system to load a preliminary month, then replace it with the approved result. Check the effect on reports, forecasts, and variance explanations.
The two workflows also use different levels of detail. Consolidation may work by entity and account. Planning may need departments, product lines, or headcount assumptions. Agree on which dimensions to share and how to reconcile the totals. A forced match between every planning dimension and every consolidation field can produce unnecessary maintenance.
Test a late journal that changes a material expense. Can the FP&A analyst see which forecast comparison changed and why? Can the controller preserve the published report from before the correction? Ask both teams to walk through the example. Their answers will show how much coordination the platform saves.
Choose a scope the organization can maintain
| Priority | Practical scope | Evidence to request |
|---|---|---|
| Reduce intercompany and close rework | Consolidation and close workflow | Match a discrepancy, post an elimination, and publish approved results |
| Improve budget ownership | Planning connected to approved actuals | Collect department submissions and reconcile the plan to group reporting dimensions |
| Standardize management reporting | Governed reporting layer over financial and operating sources | Reproduce a published report with the same figures and definitions |
| Replace several disconnected processes | CPM suite or a deliberately integrated set of tools | Demonstrate an end-to-end close, report, and forecast refresh |
Estimate how often group structure, accounts, and reporting definitions change. Ask a finance administrator to add a new entity or reporting line during the evaluation. Check what needs a consultant, what finance can change independently, and how updates reach the people who prepare local submissions.
The implementation budget should include account mapping, historical data, reconciliation, and role setup. A platform can consolidate once the inputs are ready. The group still needs to agree on definitions, reporting dates, and responsibility for exceptions. Assign those decisions to named owners before using software configuration to settle them.
Rehearse a difficult close before signing
Use two or three entities with different source systems. Import balances, handle an unmapped account, resolve an intercompany issue, apply a group adjustment, and publish a pack. Then hand the approved results to the forecast team. Compare the totals to a known close and log any steps that required spreadsheets or manual transfers.
Measure the work that the pilot removes. Count reconciliation hours, delayed submissions, post-publication changes, and manual adjustments. Ask the report owner whether a reader can reproduce a published number with the available evidence. The test is complete when both the controller and the planning lead can show where the figure came from and agree on which version they are using.