Governance and administration
Why Don't My Reports Reconcile? The Governed Fix
Why don't my reports reconcile? Usually timing and scope explain it. Here's what good looks like and what to ask your team to fix first.
Austin Levine
·
Updated
Why don't my reports reconcile? Usually it comes down to timing and scope rather than a real error. A day-3 preliminary pull and a day-10 final pull cover different windows and different rules, so they show different numbers. Reports reconcile when someone designs them to agree on dates, definitions, and one source.
If you've ever asked "why don't my reports reconcile," you probably weren't staring at a mistake. You were staring at two honest numbers that were built to answer slightly different questions. The preliminary figure your team sent on day 3 and the final figure on day 10 don't match because they never covered the same window, the same accruals, or the same set of accounts. To the person reading the management report, it reads as an error. To the people who built the reports, it's just how they were set up. That gap is where trust goes.
A number that shifts between day 3 and day 10 doesn't just change a cell in a spreadsheet, it changes a decision. A leadership approves a spend on the preliminary margin, then the final margin lands two points lower and the CFO has to walk it back. A close that should wrap in three days drags toward ten because finance keeps re-checking figures that were never going to agree. Each time a final number contradicts a preliminary one, the room trusts the next report a little less. Only 40% of executives say they always trust their data (Talend), and this is one of the reasons the other 60% don't.
Key takeaways
Reports usually fail to reconcile because of timing and scope, not a real error.
A day-3 preliminary pull and a day-10 final pull cover different windows and rules, so they differ.
A preliminary number is supposed to move; the problem is a page that never says it will.
Reports reconcile when someone designs them to agree on dates, definitions, and one source.
Why don't my reports reconcile when nothing looks wrong?
Because the two reports were pointed at different things, and nobody wrote that down. There are three common reasons the numbers drift, and none of them mean anyone did the work wrong.
The first is timing. A preliminary pull on day 3 sees a partial month. Invoices are still landing, accruals aren't booked yet, a few late transactions haven't posted. The day-10 pull sees a more complete picture. Same report, different moment, different total.
The second is scope. One report includes intercompany transactions or pending orders and the other doesn't. One counts a refund as a negative sale, the other parks it somewhere else. The filters differ by one line, and the totals differ by a lot.
The third is definition. In one report "revenue" counts what's booked; in another it counts what's invoiced. "Active customer" means bought-this-month here and bought-ever there. When two teams use the same word for two different calculations, their reports show different numbers and both are correct.
Is a preliminary number that changes really a mistake?
No. A preliminary number is supposed to move. That's what makes it preliminary. The problem is what's missing from the page. Nothing on it tells the reader the number is going to move, or by how much, or why.
Think about how preliminary vs final numbers usually reach a leadership team. A figure gets pulled early so the meeting can happen, it goes into a slide with no label, and everyone treats it as final because it looks final. Ten days later the real number arrives and now there's a contradiction to explain in a room that already made a call on the first figure. The number did its job. The way it was presented did the damage.
This is why manual, spreadsheet-based reporting gets fragile at exactly the wrong moment. When 94% of business spreadsheets used in decisions contain errors (Panko et al., 2024), and each report is rebuilt by hand every month, small differences are baked in before anyone opens the file. Gartner puts the average cost of poor data quality at $12.9M a year. A lot of that's people re-doing work to reconcile numbers that a governed setup would have agreed on the first time.
What does good look like when two reports don't match?
Good doesn't mean every number is identical on every day. It means the differences are expected, labeled, and explainable in one sentence. Here's what that looks like from a CFO's chair.
Every report carries an "as-of" date and a clear status, so a preliminary figure is marked preliminary and a final figure is marked final. Both point at a single source of truth, so they're pulling from the same governed numbers instead of two analysts' separate spreadsheets. The definitions are agreed once and reused everywhere, so "revenue" is the same calculation in finance, sales, and the management report. And when two views do differ, there's a short reconciliation that lists the reason, usually one of those three: timing, scope, or definition.
When that's in place, a changed number stops being an accusation. Someone can say "the day-3 figure was preliminary, the final came in lower because two large invoices posted after we pulled it," and the room moves on. That's the difference between a close that finishes in three days and one that drags to ten. Finance teams that close in under three days are the high performers; eight days is still considered acceptable (SolveXia). The gap between those two is mostly time spent chasing numbers that were never designed to agree.
Why the numbers differ | What it looks like in the room | The governed fix |
|---|---|---|
Timing mismatch | Day-3 preliminary and day-10 final cover different windows | A dated "as-of" stamp and status on every report |
Scope mismatch | One report includes intercompany or pending orders, the other doesn't | Agreed filters and definitions applied once, reused everywhere |
Definition mismatch | "Revenue" means booked in one report, invoiced in another | One definition in a shared model, not per-analyst |
What your team actually does about it
This is the one place worth going a level deeper, and it stays short. The fix lives in the data model, not in the charts.
Your team agrees the definitions once and puts them in a shared semantic model, which is the layer that decides what "revenue" or "active customer" means for every report that reads from it. They stamp each report with an as-of date so a preliminary pull can't be mistaken for a final one. Then they build a small reconciliation view whose only job is to list where two numbers differ and which of the three reasons explains it. None of this is exotic. Most teams already own the tools in Power BI or Microsoft Fabric. What's usually missing is someone deciding the rules and making every report obey them. Data silos make that harder: 82% of companies say silos disrupt their workflows (ZoomInfo), which is a plain way of saying the sales number and the finance number live in separate places and were never reconciled on purpose.
What should you ask your team for first?
You don't need to learn the mechanics to fix this. You need to ask for four things and listen for specific answers.
One agreed definition per number that matters. Ask where "revenue," "margin," and "active customer" are defined, and whether every report uses that same definition. If the answer is "it depends who built the report," that's the whole problem.
A status label on every report. Mark each one preliminary or final and show the date it was pulled. This one change stops most of the day-3-versus-day-10 arguments on its own.
A single source the management report pulls from. Not five spreadsheets that get stitched together the night before. One governed source that both the preliminary and final views read.
A one-page reconciliation when two numbers differ. If sales and finance disagree, you want a short view that says why, so the meeting isn't spent arguing about whose number is right.
Fix those four and the "why don't my reports reconcile" question mostly stops coming up, because the answer is written down before anyone has to ask.
If you want to see where your setup stands, the free Power BI Governance & Cost Scorecard takes about five minutes and shows you your top risks plus how you compare to peers. And if your numbers still won't line up after that, book a scoping call and we'll do a reconciliation and governance review on your actual reports.
Frequently asked questions
Should preliminary and final numbers ever match exactly? Not always, and that's fine. A preliminary number covers a partial month, so it's expected to move as more transactions post. The point is to label the preliminary one clearly and be able to explain any difference in a sentence. Small movements are expected.
How long should our month-end close take? Around eight days is still treated as acceptable, while the high performers wrap it in under three (SolveXia). If yours is dragging, a big part of the delay is usually time spent reconciling reports that were never designed to agree, not the accounting itself.
Is this a Power BI problem or a process problem? Mostly process, made visible by the tool. Power BI and Microsoft Fabric can enforce one definition and one source, but only after someone decides what the rules are. The tool won't reconcile numbers you haven't agreed on.
Can a single source of truth really fix reports that disagree? It fixes most of it. When every report reads from one governed source and one set of definitions, the leftover differences come down to timing, which is easy to label. The disagreements that waste meetings almost always trace back to separate spreadsheets with separate rules.
How do we explain a changed number to leadership without losing credibility? Get ahead of it. Mark the first figure preliminary when you present it, and when the final arrives, say which of the three reasons moved it: timing, scope, or definition. A number that changes with a clear reason reads as control. A number that changes with no explanation reads as a mistake.
Read next: KPI Dashboards Executives Actually Trust and Single Source of Truth: What It Really Means for a Business.
