Skip to content
New: ask the Rexfin Analyst Agent about your model. Every figure comes back cited.
· 6 min read

Reconciliation to Printed Totals: The Arithmetic Check Behind Every Rexfin Number

Rexfin re-adds every extracted line back to the total a filer actually printed, and blocks any figure that doesn't tie out before it ever reaches a model.

By The Rexfin team

A PDF of a 10-K or an annual report already contains its own answer key. The income statement prints a subtotal. The balance sheet prints “total assets.” The cash flow statement prints an opening and closing cash balance. Every one of those totals is arithmetic the filer already did, in public, and signed off on. So the first thing worth checking about any extracted number is not whether it looks plausible. It’s whether it actually adds up to the total the filer printed on the same page.

That check has a name inside Rexfin: reconciliation to printed total. It runs before a single extracted figure is trusted enough to seed a model, sit in an answer, or reach an export.

Why this catches what extraction alone misses

Pulling numbers off a financial statement PDF is harder than it looks. Line items get split across pages, footnotes get mistaken for face lines, a parser reads a subtotal as if it were a line item, or a column shifts by one row. None of these failures look dramatic. The output is still a number, still roughly the right size, still sitting in the right row of a spreadsheet-shaped table. It just doesn’t add up.

Reconciliation to printed total is the check that would catch it: sum the face lines that are supposed to feed a subtotal, and see if they land on the total the document itself prints, within a tolerance that scales with the size of the number (so a rounding difference of a few units doesn’t trip a false alarm, but a genuinely wrong line does). If the sum doesn’t reconcile, the figure doesn’t get treated as verified. It gets a typed flag instead, and shows up on a release-gate report rather than being dropped silently.

It goes beyond one subtotal

A filing isn’t just a list of subtotals in isolation: the three statements are supposed to hang together. Assets should equal liabilities plus equity. Cash flow movements should tie the opening cash balance to the closing one. Profit should roll forward correctly from gross profit to operating profit to pre-tax profit. Rexfin runs these as a set of accounting identity checks across the whole filing (assets, liabilities, equity, gross profit, operating profit, pre-tax profit, and the cash flow tie) as declarative, versioned rules rather than one-off scripts bolted onto a single filing. That matters because a rule you write once for one company’s PDF and never touch again tends to quietly rot the next time a filer changes their layout. A versioned rule is something you can point to and say: this is what “reconciled” has meant, consistently, since this date.

What happens when the numbers don’t tie

A break in reconciliation isn’t a warning label next to an otherwise-usable number. It vetoes the figure. A number that fails to reconcile to the printed total, or fails an identity check like A = L + E, is not eligible to seed a projection or answer a question: it’s blocked at the point where it would otherwise have been treated as fact. If the inputs needed to even run the check are missing, that’s tracked honestly as indeterminate rather than waved through as a pass.

This is also why reconciliation sits downstream of multi-backend extraction agreement rather than replacing it. Agreement between independent extraction passes catches a backend reading a number wrong. Reconciliation to printed total catches something different: a number that every backend read consistently, but that still doesn’t sum to what the filer reported. Both checks have to pass. Either one failing is enough to keep a figure out of the pool of numbers Rexfin will actually cite or calculate from, which is the same pool the trust chain draws its evidence ranking from, and the same gate that later blocks unverified numbers from export.

Who actually needs this

If your team has ever pulled numbers out of a filing with a generic extraction tool and then spent an afternoon reconciling it against the PDF by hand because something felt off, this is the check that replaces that afternoon. It’s built for finance and FP&A teams working from real filings (annual reports, interim statements, regulatory filings) where “close enough” isn’t good enough, because the number is about to feed a valuation, a board pack, or an answer someone will act on. Read more about how this fits into the full Rexfin product tour.

Part of Rexfin Product Tour: Every Number Traceable

Keep reading

Book a demo

See your numbers tie out.

Book a 30-minute demo. Bring a question you can never answer fast enough, and we will model it live against real financial data.