Two people pull the same report. The numbers do not match. Sales says one figure, finance says another, and the dashboard on the wall says a third. Everyone is using the system they were told to use. Everyone is technically right. And nobody can answer the simple question: which number is true?
This is one of the most common problems in a growing business, and one of the most corrosive. It is rarely a problem with the numbers. It is a problem with how the data underneath them is structured. Once you see that, the fix becomes clear, and so does why buying another reporting tool will not solve it.
The numbers disagree because the definitions do
Start with the most common cause, because it is the least technical. Two reports show different revenue figures because they are measuring different things and calling them the same word. One counts revenue when the invoice is raised. The other counts it when the payment lands. One includes VAT, the other strips it. One counts a refunded order, the other does not.
Free · 4 minutes
When two of your systems disagree, do you know which one to believe?
Fourteen questions on ownership, lineage, and quality — the difference between a number on a dashboard and a number you could defend. Banded finding on screen, full sheet by email.
Neither is wrong. They are answering different questions that happen to share a label. The business never agreed on what “revenue” means, so every system invented its own definition. The reports are faithfully reporting incompatible truths.
The data lives in more than one place
The deeper cause is structural. The same information is stored in several systems — the CRM, the accounting package, the e-commerce platform, a spreadsheet someone maintains. Each holds its own copy. The copies were accurate the day they were entered and have drifted apart ever since. A customer’s details get updated in one place and not the others. An order is amended in the shop but not the CRM.
Now you do not have one set of facts with different views onto it. You have several sets of facts that disagree. When you report from them, the reports disagree too. They have no choice. They are built on data that no longer agrees with itself.
This is what “single source of truth” actually means
The phrase gets used loosely, usually to sell software. It has a precise meaning. A single source of truth is an arrangement where, for any given fact, there is exactly one place that holds the authoritative version. Other systems may display that fact, but they read it from the source. They do not keep their own copy and hope it stays in sync.
When a business has this, the question “which number is true?” disappears, because there is only one number. When it does not, every report is a negotiation. The point is not that everyone sees the same screen. It is that everyone is ultimately reading from the same underlying fact.
Why buying a reporting tool does not fix it
The instinct, when reports disagree, is to buy a better reporting tool — a dashboard, a business intelligence platform, something that promises a single view. It does not work, and it is worth understanding why before you spend the money.
A reporting tool reads from your data. If the data underneath is fragmented and inconsistent, a better tool gives you a faster, prettier, more confident presentation of the same disagreement. It often makes things worse, because the polish lends authority to numbers that are still wrong. The tool is downstream of the problem. The problem is the structure of the data, and no reporting layer can fix what sits beneath it.
What the fix actually involves
The work is unglamorous and decisive. It has three parts.
First, agree the definitions. What does revenue mean. What counts as an active customer. When is an order complete. These are business decisions, not technical ones, and until they are made, no system can be made consistent.
Second, decide where each fact lives. For every important piece of information, name the one system that owns it. The CRM owns customer details. The accounting system owns financial truth. Everything else reads from the owner.
Third, connect the systems so they read from the source rather than holding their own copies. This is where integration work earns its place — not to move data around, but to remove the duplicate copies that were causing the drift.
This is a data architecture problem, and it is solved with data architecture, not tooling. It is also why every engagement worth its fee starts with the data model. The reports are the symptom. The model is where the truth is decided.
The cost of leaving it
Conflicting numbers are not just an irritation. They erode the thing a business runs on: confidence in its own information. Decisions slow down because the figures are argued over. Trust in the data falls, so people build private spreadsheets they believe more than the system, which fragments the data further. The board asks a question and gets three answers. Left alone, it compounds.
The good news is that it is diagnosable quickly. The disagreement always traces to a definition or a duplicated source, and once you can see which, the path is clear. A conversation will identify where the break is before it becomes a bigger problem. We will find out why your numbers do not agree.
Start a ConversationBuild and rescue work
Hands-on delivery of this kind is handled by Sixteen Pillars Studio.
Free interactive tool
Website compliance checklist
What your site has to do, based on what it actually does
Answer as much or as little as you like — the list builds as you go. Nothing is stored against your name and no email is required.
Everything that applies
Ordered by what to do first: legal requirements you can close quickly, then larger pieces of work, then what is expected rather than required. Not exhaustive, and not a legal audit.
Dated PDF, yours to keep or circulate.
Can you trust the architecture you have?
Architecture diagrams rarely show the reality of how systems actually operate. An independent review establishes what is really there.