Report results: where consolidated international reporting breaks

Consolidated reporting usually breaks where local entities hand numbers to the group. The common failures are intercompany balances that disagree, exchange rates applied inconsistently, adjustments made after the pack is locked, and cost or cash figures built outside the ledger. Each one leaves traces in timing, reconciliations and email traffic.

Intercompany balances that never quite agree

This is the most persistent failure. One entity books a charge. The counterparty books it later, at a different rate, or against a different account. At group level the elimination will not net to zero, and someone forces it with a plug.

The signs are easy to find once someone looks. Elimination differences carry forward from period to period. A suspense or "intercompany clearing" account grows. The same counterparty pairs show up in the dispute log every close. Group accountants spend the final stretch of the close chasing confirmations by email instead of reviewing results.

The root cause is often upstream in payment processing. An invoice raised in one currency and settled in another creates a timing gap and a rate gap at the same moment.

Exchange rates applied in more than one place

Translation should happen once, with one approved rate table. In practice local teams often convert in their own systems, the consolidation tool converts again, and a treasury spreadsheet uses a third source for cash.

A translation reserve that moves without explanation is a strong signal. Another is a local CFO who cannot reproduce the group's view of their own entity. When the reconciliation between local currency and reporting currency needs a manual bridge, the rate logic has split.

Late adjustments after the submission deadline

Entities submit, then discover an accrual or a reclassification. Some resubmit the whole pack. Others send a journal by email for the group team to post on their behalf. Either way, the version that was reviewed is no longer the version that gets reported.

Tell-tale evidence: top-side journals with vague descriptions, multiple versions of the same entity file in a shared folder, and review sign-offs dated before the final numbers changed. If the audit trail shows group staff posting entries that belong to a local ledger, ownership has blurred.

Cost views that do not tie to the ledger

Management often wants results by cost centre, project or responsibility segment alongside the statutory view. When that analysis is rebuilt from extracts, allocations drift. Budget holders then dispute their numbers, and finance re-cuts the data under pressure.

Look for allocation keys held in personal files. Watch for a recurring "unallocated" line. A management pack whose totals differ from the consolidated ledger by an unexplained amount means the cost view and the books have parted company.

Cash and receivables figures sourced outside the close

Cash flow projections and receivable status reports frequently come from treasury or credit teams working to their own cut-off. The figures arrive in the results pack without being reconciled to closing balances. Large expected receipts or disbursements may be reported in the forecast yet missing from the ledger, or the reverse.

Delinquent debt is a related weak point. Write-offs and cancellations agreed in collections may not reach the ledger before reporting, so aged receivables in the pack overstate what is collectable.

The giveaway is a cash or receivables number that needs a footnote every period to explain why it differs from the balance sheet.

Workarounds that become the process

Most of the breaks above get patched by a capable individual with a spreadsheet. The patch works, so nobody fixes the cause. Over time the documented process describes systems and controls, while the real process runs on that person's file and their memory of which entity always submits late.

Key-person dependency shows when results slip during someone's leave. It also shows when the reviewer cannot explain a reconciling item without asking the preparer. Macros or lookups that nobody else maintains are a further warning.

Questions to ask the people who run it

What is documented and what happens at close often differ. Ask the preparers, and ask them separately from their managers.

• Which entities or counterparties cause trouble every period, and what is the usual reason?
• Where does the exchange rate in each schedule come from, and who loaded it?
• After an entity submits, how do corrections reach the group? Who posts them?
• Which numbers in the pack are typed in from another file instead of pulled from the system?
• What would stop the close if one particular colleague were absent?
• How are intercompany disputes settled, and who has authority to decide?
• When the cash forecast and the balance sheet disagree, which one wins, and who explains the gap?
• Which reconciling items have been open so long that everyone stopped asking about them?
• What checks happen before sign-off that are not written down anywhere?

The answers usually locate the real handoffs faster than any process map. Changes aimed at those points tend to remove rework. Changes aimed at the documented flow often leave the workarounds in place, running beside a new system.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.