How financial reporting is set up in finance and ERP systems

Financial reporting usually runs on a general ledger that holds every posted balance. A mapping layer turns those balances into statement lines. A consolidation tool then combines entities and removes internal activity. Management packs, board papers and external filings are built from that consolidated data, often in a separate reporting or disclosure tool.

The ledger carries the structure

Everything starts with the chart of accounts and the attributes attached to each posting. Account, entity, cost center, project and sometimes fund or program sit on every line. When these segments are designed well, most reports become a matter of filtering and summing. When they are designed loosely, finance teams end up rebuilding the structure in spreadsheets every period.

Subledgers for payables, receivables, fixed assets, payroll and revenue post into the ledger either in detail or as summaries. Manual journals cover accruals, reclassifications and corrections. These go through an approval route before posting. Public sector ledgers add budgetary accounts next to proprietary ones, so the same transaction can hit both sides.

Turning balances into statements

Accounts rarely map one to one onto the face of the statements. A crosswalk or mapping table sits between them. It assigns each account, or each account and attribute combination, to a statement line and a note.

This table is one of the most important objects in the whole setup and one of the least governed. New accounts get added in the ledger and nobody updates the mapping. Balances then fall into a suspense line or vanish from a note. A good setup flags unmapped accounts before the statements are run.

Every figure in a published statement should trace back to ledger balances. Most systems offer a drill path for this. Auditors will test it.

Entity books and the group view

Each business unit closes its own books first. Its trial balance is locked, reviewed and loaded into consolidation. Some organizations consolidate inside the ERP. Larger or more complex groups use a dedicated consolidation application that pulls trial balances from several ledgers, including acquired businesses still on their old systems.

The consolidation step handles currency translation, ownership percentages and minority interests. It also records eliminations for intercompany sales, loans, balances and investments. Intercompany matching is where most delays come from. If the selling entity and the buying entity record different amounts or periods, the elimination leaves a difference that someone must chase.

Legal consolidation follows statutory ownership. Management consolidation follows how the business is run, by segment, region or product line. The two hierarchies often differ, and the system needs to hold both without duplicating data.

Management reporting runs in parallel

Management reports draw on the same ledger but slice it differently. Cost center, project and responsibility views matter more here than statutory lines. Budget and forecast data are loaded beside actuals so variances can be shown.

This work is often done in a planning tool or a business intelligence layer. The risk is that management numbers drift from the ledger through manual adjustments made only in the reporting tool. A reconciliation between management totals and the ledger trial balance closes that gap.

Board papers, filings and regulators

Board statements are usually a curated version of the consolidated results, with commentary, key measures and comparisons. They tend to be assembled in presentation or disclosure software that links back to consolidated figures.

Quarterly and annual filings, shareholder reports and regulatory returns need tagging, version control and sign-off workflows. Disclosure management tools link narrative text to live numbers so a late adjustment flows through the document. Regulatory returns often require their own account mappings, since a regulator's categories seldom match the statutory format. Government entities submit ledger balances to a central treasury function in a prescribed format.

Where setups tend to break

Trouble rarely sits in the reporting tool itself. It sits upstream. Late subledger cutoffs push work into the final days of close. Mappings fall out of date as accounts change. Intercompany partners disagree. Manual top-side entries in consolidation pile up and are never pushed back into entity ledgers, so the same correction reappears each period.

Another common issue is a spreadsheet that quietly became part of the process. It might hold a mapping, an allocation or a disclosure note. It works until the person who built it leaves.

Questions to ask the people who run it

The documented flow and the real flow often differ. These questions tend to surface the gap:

• Which numbers do you adjust after the ledger is closed, and where do those adjustments live?
• When a new account is created, who updates the statement mapping, and how would anyone know if they forgot?
• Which intercompany differences come up every period, and how are they cleared?
• Are any reports built from a spreadsheet extract instead of the system directly?
• Do management totals ever disagree with the statutory trial balance? What explains the difference?
• Which top-side consolidation entries repeat, and why are they not fixed at entity level?
• How do regulatory returns get their figures, and who checks them against the ledger?
• What would stop the board pack going out on time if one person were absent?
• Which steps do auditors ask about most, and what evidence do you hand them?
• If you could change one thing about the close, what would it be?

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.