When ERP Reports Stop At The Company Boundary

For many private groups, reporting starts in a controlled way. Each company has its own accounting or ERP system. Local finance can pull trial balances, profit and loss reports, voucher lists and account details. The numbers exist. The reports exist. Still, month-end becomes heavier as the group adds another company, another country, another chart of accounts, or another Excel workbook in the reporting package.

This is rarely because the local systems are poor. It is because they are designed for local accounting and local operational control. Group control requires something different: one place to collect, compare, explain and control numbers across company boundaries.

ERP reports do not solve the whole group need

An ERP or accounting system is usually good at what happens inside one legal entity. It handles vouchers, customers, suppliers, bank, VAT, periodization, departments, projects and local reporting. For the subsidiary, that may be the right working surface.

The CFO of a group asks a different question:

What is happening across the group, and can we explain the number back to its source?

That question often stops at the company boundary. Company A uses one accounting system. Company B uses another. Company C has a different chart of accounts or dimension setup. One company reports by project, another by department, and a third uses Excel columns to explain the same kind of number.

ERP reports become useful source material, but not enough as the group’s control system.

A practical scenario: month-end in a seven-company group

Imagine a private Nordic group with seven companies in Norway and Sweden. Five companies use one accounting system. Two joined through acquisitions and use different systems. The group reports monthly to the board, bank and owners.

At month-end, the controller pulls reports from each system. Data is exported to Excel. Accounts are mapped to group reporting lines. Intercompany revenue and costs are checked. Variances are commented. The CFO asks why EBITDA is lower than expected in one business area, and the controller has to trace the explanation through several files and systems.

The process works. But it is fragile.

The risk is not one dramatic failure point. It sits in many small manual handovers:

• exports from local systems
• mapping between charts of accounts
• copying data into reporting workbooks
• manual control of eliminations
• variance explanations in comments and emails
• person-dependent logic in Excel

When the CFO explains the numbers to the board, the question is not only whether the report is finished. The question is whether the numbers can be checked quickly.

Local reports create local confidence

It is useful to separate local confidence from group confidence.

Local ERP reports can be fully correct for the subsidiary. They can show the right result, balance sheet, vouchers and reconciliations. Local finance can trust them.

Group confidence starts when the numbers can be seen together:

• Are accounts mapped consistently across companies?
• Are dimensions comparable?
• Are intercompany transactions treated consistently?
• Are eliminations documented and traceable?
• Can the CFO move from a group reporting line back to underlying accounts, transactions or vouchers when the data is available?

This is not only a reporting question. It is a control question.

When Excel becomes the glue between systems

In many groups, Excel becomes the layer between local ERP systems and the group report. That is understandable. Excel is flexible, fast and familiar. Controllers can solve urgent reporting needs without waiting for system projects.

But flexibility has a cost when Excel becomes the place where group logic lives.

Critical decisions then sit in formulas, lookups, tabs and manual routines. An experienced controller knows which sheets must be updated, which cells must not be touched, and which variances usually come from mapping issues. The problem is that this knowledge is often invisible to the rest of the finance team.

Excel is still useful. Many finance teams will and should keep some Excel workflows. But Excel should not be the only place where the group creates control across companies and accounting systems.

One ERP platform or one control layer?

Some groups consider standardizing everything on one ERP platform. That can be the right path when the group wants one operational system for processes, data and reporting.

For many private groups, it is not the most realistic first step. Their local systems already work. Acquisitions arrive with their own accounting systems. Replacing ERP across all subsidiaries can become a larger project than the reporting need requires.

The more practical question is:

Do we need one shared ERP system right now, or do we need one control layer above the systems we already have?

A control layer should not replace local accounting systems. It should collect the group’s finance control where ERP reports stop:

• shared overview of companies
• comparable accounts and dimensions
• group reporting
• consolidation and eliminations
• variance analysis
• traceability to transactions, vouchers and attachments where the data supports it

For the CFO and controller, this is the difference between producing a report and being able to explain it.

What CFOs should look for

When a group outgrows local ERP reporting, review the process through a control lens.

Ask these questions:

1. How many manual export and import steps exist at month-end?
2. Who understands the whole reporting workbook?
3. Can we see numbers across all companies without building another Excel model?
4. Can we explain group lines down to account, dimension, transaction or voucher?
5. Are eliminations and intercompany variances documented so others can review them?
6. What happens when we acquire a company with another accounting system?
7. How much of board and owner reporting depends on one person?

If several answers point back to Excel, email and manual mapping, the group needs more than local ERP reports.

Control is about explanation

Good group reporting is not only about collecting numbers. It is about explaining them.

Why did costs increase in one company but not the others? Why does intercompany invoicing not match? Is the variance real, or is it caused by different account use? Is the margin change operational, or does the explanation sit in periodization, currency, mapping or eliminations?

These questions cannot always be answered in a local ERP report. They require context across companies, systems and data levels.

For the controller, that means fewer manual bridges. For the CFO, it means more confidence when numbers must be explained to management, the board, banks or owners.

Where Sumledger fits

Sumledger is built for private Nordic groups that have become too complex for pure Excel reporting, but do not need heavy enterprise finance systems.

The platform connects to the accounting systems used by subsidiaries and gives CFOs and controllers one control layer for group reporting, consolidation, eliminations, Excel workflows and analysis across companies. Where the data is available, finance teams can work with accounts, dimensions, transactions, vouchers and attachments in the same control context.

The point is not to remove every local system. The point is to give the group one shared place to control and explain finance.

From local reports to group control

ERP reports remain important. They are the source of much local truth. But when the group has several companies, several systems and rising reporting pressure, CFOs and controllers need a working surface that crosses company boundaries.

This is often the stage where group reporting has outgrown Excel, but still does not need enterprise weight.

Book a short demo to see how Sumledger can bring group finance together across companies, ERP systems and vouchers.