ERP management information: why your team still works in Excel

The meeting stops at one number

The CFO opens the ERP dashboard for the quarterly figures. Two seats away, the controller opens an Excel file with the same title: margin per product group. The numbers do not match. Nobody in the meeting can say which screen is right, so the decision is pushed back a week while someone traces the difference by hand.

The cause is rarely a calculation error in the ERP system. It is usually the missing agreement behind the number: what margin per product group means, who owns that definition, and which source has the final word when two reports disagree. The controller trusts the Excel version because he built it and understands it. The CFO trusts the dashboard because it comes from the source system. Both positions are understandable. That is exactly the problem.

Excel is not the enemy in this situation. It is the signal. As long as definitions, ownership and escalation routes are not explicit, every report remains open to debate. That can happen even when the ERP system itself is technically sound.

The short answer

ERP management information becomes useful only when the management team knows what each key figure means, who owns the definition, and which source is leading when doubt appears. Without those governance agreements, a correct ERP system and a polished dashboard can still exist next to private Excel files. The first problem is ownership. The tooling comes after that.

What management information means in an ERP context

Management information is the data a management team actually uses for decisions, not every data point an ERP system happens to register. That distinction decides whether reporting creates trust or becomes background noise.

An ERP system records transactions: orders, invoices, stock movements, production hours and project costs. Those registrations are often reliable because the daily operation depends on them. Management information is a different layer. It turns those transactions into numbers a director, CFO or operations manager is willing to use when choosing what to do next.

Reliable management information starts when one person owns the definition behind each key figure. Without that owner, every department can create its own version of revenue, margin, productivity or stock value.

That is why management information is not the same as a BI tool. A dashboard, Power BI report or ERP reporting module is technology. Management information is an organisational agreement: which definition applies, who maintains it, and what happens when a team challenges the number.

Where trust breaks down

Sources from Data Governance Institute, Oracle, GovernanceWerkt and BI.nl point in the same direction: trust depends on clear responsibilities, consistent definitions and a traceable route from source to report. In ERP and BI programmes, three fault lines are worth checking first.

Cause	Signal	Effect
No owner for each key figure	Two departments calculate margin or revenue differently, and nobody can say which version is leading	Every number becomes a discussion instead of a basis for decisions
Reporting treated as an IT project	The dashboard is delivered, but the management team does not use it consistently	Reporting quietly ages, and users return to their own spreadsheets
Source system and reporting layer drift apart	ERP changes are not reflected in BI, or BI logic changes without source governance	Numbers from two sources keep diverging, and trust drops further

These signals can be technical and organisational at the same time. A useful diagnosis first finds where the difference starts. Only then can you decide whether the answer is source data, reporting governance, ownership or tooling.

The five roles that make reporting trustworthy

A reliable BI layer around an ERP system does not begin with more dashboards. It begins with five roles and a clear mandate.

Role	Responsibility	Common risk
Data owner for each key figure	Defines and protects what a number means, for example margin or revenue	Missing entirely, or different per report
BI or reporting owner	Maintains dashboards and investigates differences between source and report	Appointed too late, after shadow Excel files already exist
Functional owner of the source system	Protects data quality at the source: fields, input discipline and process rules	Works separately from the BI owner, so source and reporting drift apart
IT architect	Guards the data route from source to reporting layer and knows where transformations happen	Involved only in technology, not in definition decisions
Management consumer	Reports when a number conflicts with business reality	Stays silent and builds a private Excel version instead

One person can hold more than one role, as long as the mandate and replacement are clear. If the data owner is missing, the technology can be correct while the definition remains contested.

Eight questions for your management team

Use these questions for the figures your management team relies on monthly or quarterly.

Ownership

Is there one named owner for each key figure, such as revenue, margin, stock value or productivity?
Do people know who to call when two reports show different numbers for the same metric?

Reliability

Is there a fixed control moment where source and reporting layer are compared?
Does the management team use the ERP dashboard, or do parallel Excel files circulate with the same figures?

Governance

Is reporting managed as an ongoing business product, or was it treated as a one-off IT delivery?
Is there an escalation route when a department disagrees with a published number?

Future readiness

Is the BI layer updated when the ERP system changes?
Can a new management team member see within a day where each key figure comes from and who signs off on it?

If most answers are no, start with one contested number. Define it, name the owner, map the source and agree what happens when a difference appears.

When to act

Six signals show that management information has become a governance risk, not just a technical inconvenience:

Two managers draw opposite conclusions from what they both call the same report.
A decision is delayed because nobody knows which number is reliable.
Departments build their own Excel files next to the ERP dashboard, just to be safe.
A new ERP module is live, but the reporting layer still shows the old structure.
Nobody can explain exactly how a published key figure is calculated.
Management meetings spend more time debating the reliability of the numbers than acting on what the numbers mean.

When several of these signals appear, investigate the chain of source, definition, owner and decision first. Otherwise a new dashboard may only give the same uncertainty a cleaner layout.

When a separate BI layer is not needed

Not every organisation needs a separate BI layer on top of its ERP system. If there are only a few key figures, one clear source and a management team that trusts the ERP reporting module, an extra BI layer can add cost and maintenance without solving a real problem.

The better question is not whether you need BI. The better question is whether your management team trusts the figures it uses, and whether everyone knows where those figures come from. If the answer to both is yes, a well maintained ERP reporting module with a named owner can be enough.

Internal, hybrid or external support

Situation	Recommended approach
Few key figures, one source, trusted ERP reporting	ERP-native reporting is enough, with a named owner
Multiple source systems feeding one management number	Separate BI layer with an owner who guards source and report
Repeated debates about which number is right	Independent management information diagnosis before investing in another tool
BI project delivered as IT output, without ownership	Reframe governance first, technology second
Fast growth or new management questions	Periodic independent review of definitions and ownership

The core choice is not the tool. It is whether your organisation has the ownership, discipline and counterweight to keep management information reliable. If that is missing, another dashboard will not fix the underlying issue.

Why we start with people and agreements

Our work is people work. Behind every debate about which number is right there is a controller who built his own sheet because he did not trust the dashboard, a CFO who delayed a decision to be careful, or a manager who has doubts but never says them out loud in the meeting. The technology is often not the first failure. The agreement about who owns the number is missing.

That is why ERP Company starts a management information diagnosis with ownership and definitions before discussing tooling. Not because technology is unimportant, but because we have no interest in selling an extra dashboard when the real issue is governance. We do not sell BI tools or licences. We deliver an honest view of which parts of your management information can be trusted, and which parts need attention first.

Within Business Intelligence & Reporting, we first look at who owns the figures and why. The dashboard comes after that. Independence is not a sales line for us. It is why the advice can be trusted.

The maintenance moment that protects trust

Definitions do not stay current on their own. A new module, process change or management question can influence a key figure. Agree when source and reporting are compared, who investigates differences, and who approves a change in definition.

That maintenance moment turns reporting into a managed business product. The discussion then shifts from competing versions to one controllable question: which agreement changed, and has that change been processed correctly?

An independent party without a stake in a specific BI tool can first test that governance chain. Sometimes a BI layer is needed. Sometimes better ownership of existing ERP reporting is enough.

Frequently asked questions about ERP management information

What is the difference between ERP reporting and management information?

ERP reporting shows what the system records. Management information is the number a management team actually uses for decisions, with a clear definition and an owner. Reporting without ownership is rarely trusted for important decisions.

Why does our management team not trust ERP numbers when the system works?

Trust depends on ownership, not only on technology. When departments calculate the same number differently and nobody protects the definition, differences appear and confidence drops. A technically correct system does not solve that governance problem by itself.

Do we need a separate BI layer next to our ERP system?

That depends on the number of source systems and key figures. With one clear source and a limited set of figures, a maintained ERP reporting module can be enough. With several sources feeding one management number, a separate BI layer with governance may be the better route.

How should we start a management information diagnosis?

Choose one key figure that regularly creates debate. Document the definition, source, owner, reporting route and escalation path. ERP Company defines the wider scope only after a short inventory.

Have your management information assessed independently

Do you recognise the debate about which number is right in your own management meetings? Or are you building a new BI layer and want to know whether ownership and definitions are sound before choosing a tool?

We do not decide for you. We help you make decisions on numbers you can trust, reviewed by a party without an interest in a specific BI tool or licence.

Request a management information diagnosis

Or contact our team via info@erpcompany.nl or +31 85 0607 626.

Sources

These sources were used as background for the analysis of data ownership, BI governance and spreadsheet risk. They support the importance of clear definitions, responsibilities and traceability. The exact diagnosis, approach and lead time differ per organisation and are defined only after an inventory.

Data Governance Institute, Assigning Data Ownership, on ownership for data and definitions, accessed 12 July 2026: https://datagovernance.com/assigning-data-ownership/
Oracle, 10 Common Spreadsheet Risks, on risks from standalone spreadsheets beside central reporting, accessed 12 July 2026: https://www.oracle.com/analytics/spreadsheet-risks/
GovernanceWerkt, Datastromen en data-eigenaarschap, on data flows and responsibility, accessed 12 July 2026: https://governancewerkt.nl/breng-datastromen-en-data-eigenaarschap-in-kaart/
BI.nl, BI governance, on responsibility and governance around BI, accessed 12 July 2026: https://www.bi.nl/geen-categorie/bi-governance-verantwoordelijkheid-en-eigenaarschap/

ERP management information: why your management team still works in Excel