Full-Year Reconciliation: Tying Twelve Closes to the Number You Actually Filed
Twelve monthly closes can each be sealed and correct on their own terms and still not add up to the audited annual statement. Here's how full-year reconciliation catches that gap.
By The Rexfin team
Twelve monthly closes can each be sealed, signed off, and pass every check running against them, and still not add up to the number that ends up in the audited annual statement. That isn’t a contradiction: the two numbers come from different processes on different timelines. The monthly closes run all year against interim, internal figures, each one a best answer given what was known that month. The filed annual is what survives audit fieldwork: adjustments, reclassifications, and corrections that no one closing month six could have seen coming. Full-year reconciliation is the discipline of tying those two together: checking whether twelve interim closes actually sum to the one figure the entity filed, and surfacing exactly where they don’t.
A check that structurally can’t run early
This isn’t a variance review against budget. It’s a comparison between what the year’s closes said, month by month, and what got filed once the year was audited, and it can only run once both sides of that comparison exist. Rexfin ties each trial balance upload to a content-derived version identifier, so there’s never ambiguity about which numbers a given month’s close actually reflects. Once twelve months of that history have accumulated, an annual-tie check compares the accumulated year against the filed figure. Earlier months can’t run this check at all, not because the check is disabled but because its precondition (a full year plus a filed annual to compare against) simply doesn’t exist yet. That’s also why this isn’t just a year-end afterthought: it’s a distinct pass over the whole year’s closes once the filing lands, not a box ticked in December.
Where interim and filed diverge, and why that’s the point
A gap between the interim sum and the filed figure isn’t automatically an error. Audit fieldwork routinely produces adjustments a monthly close was never positioned to catch: a reclassification, a true-up, a provision resolved differently than assumed mid-year. The reconciliation’s job is to locate exactly which months and which lines the divergence lives in, not to assume the interim numbers were wrong just because they don’t match. That distinction matters because the monthly integrity checks each close already ran, tie-outs, ratio bounds, trend-break detection, are built to catch patterns within a single period. None of them are positioned to catch a gap that only exists across the whole year, against a number that didn’t exist yet when those checks ran.
The same trail, not a special exception
When a full-year reconciliation does turn up a real discrepancy (an entry that was simply wrong all year, not just adjusted by audit), it doesn’t get quietly folded back into the sealed monthly closes it came from. A sealed close’s manifest is what it is; correcting it is its own tracked action, going through the same preparer/reviewer separation and append-only event log that governs everything else in the close, not a silent edit to twelve months that already shipped. That’s the same discipline described in the year-end close: a seal buys honesty about what a period said at the time, and a correction later is its own visible event, not a rewrite of history.
What this doesn’t replace
Reconciling twelve closes to a filed annual figure doesn’t replace the judgment of whoever prepared the filing, and it isn’t a substitute for the audit itself. What it does is give you a systematic answer to a question that’s otherwise easy to leave to memory or a spreadsheet built after the fact: which months, which lines, and how much moved between what was reported through the year and what was ultimately filed. Walking into that comparison with a version-identified trail behind every monthly figure is the same posture that makes audit preparation faster: a number that already resolves back to a specific, timestamped close is a shorter conversation than one someone has to reconstruct from memory.
Who this is for
This is built for the controller or group finance lead who owns the moment the audited annual lands and has to explain, line by line, why it does or doesn’t match what the business reported all year. It’s for anyone whose monthly close discipline only proves itself once a full year is on the table, and for finance teams who’d rather find their own gaps before an auditor, a lender, or a board member finds them first.
See the rest of what a reconciled close year looks like at the finance team use cases hub, or book a demo to see a full year of closes tied to a filed annual figure end to end.
Part of Finance Team Use Cases: Real Workflows on Verified Numbers