The Pre-Audit Health Check: Running the Verifier Over Your Numbers Before the Auditors Do

There’s a meaningful difference between an auditor finding a break in your numbers and you finding it first. One is a footnote in a planning conversation. The other is a fieldwork extension, a follow-up request, and a controller explaining after the fact why the balance sheet didn’t tie. The audit preparation work most teams do is about the trail behind each figure. This is the narrower, more mechanical companion to it: running the same checks the model already enforces on every export, deliberately, as a health check, in the weeks before an auditor ever opens the file.

What actually gets checked

Rexfin’s verifier doesn’t just look at whether a number exists: it checks whether the accounting identities that have to hold actually do. The balance sheet identity (assets equal liabilities plus equity) and the cash flow identity (operating, investing, and financing cash flow plus the currency effect nets out to the real change in cash) are the two everyone already knows have to be true. What’s less visible is that Rexfin now runs three more alongside them: an income-tie check, an operating-profit subtotal check, and a tax-consistency check. None of these are new arithmetic (they’re identities any accountant already expects to hold), but running them mechanically on every relevant period, instead of trusting that they hold because the workbook looks fine, is what turns “should tie” into “checked.”

Before any of that math runs, every operand has to be anchored: matched back to the exact source-PDF page it came from, not just assumed correct because the number looks plausible. A pre-audit health check is really asking the same question an auditor will ask during fieldwork (does this number trace to something real), just weeks earlier and without anyone waiting on the answer.

Hard fail versus advisory, and why the distinction matters here

Not every break is treated the same way, and that distinction is exactly what makes a pre-audit run useful rather than noisy. If every operand in a failing identity comes from an actual, filed period, the failure is real and blocks export outright: no board pack or statement leaves with a balance sheet that doesn’t balance. If any operand is a forecast or modeled figure, the same failure is advisory only, because a projection is allowed to be provisional in a way an audited actual isn’t. Running the check yourself before fieldwork means you see this distinction early: a hard fail on a closed period is something to fix now, while an advisory flag on a forecast tells you where the plan still has assumptions baked in, not where the books are wrong.

The tolerance the check applies also scales with how the statement is actually presented (to the reporting unit, not a fixed number), so a balance sheet rounded to the nearest thousand or million doesn’t throw a false break on rounding alone. When something does fail, the difference reported is exact, not a shrug that says “close enough.” And because the check is deterministic, the same model state produces the same verdict every time, which means you can run this health check repeatedly through the close cycle without the result drifting between runs.

Running it on your calendar, not the auditor’s

Audit pressure isn’t spread evenly across the year: it concentrates around the filing deadline and around any change in audit status, like crossing a small-company exemption threshold or bringing on a new auditor. The months before that filing are exactly when a deliberate health check earns its keep: catch a broken identity in November and it’s a quiet fix; have an auditor catch it in March and it’s a request that turns into several more, the kind covered in audit fieldwork requests. Running the verifier as a standing pre-audit habit (not just relying on it to catch a break at export time) is what lets a controller walk into fieldwork already knowing which figures will hold up before anyone else asks.

Who this is for

This is for controllers who want one clean pass over the numbers before an auditor asks for one, for CFOs bringing on a new external auditor who don’t yet know how deep that auditor will want to dig, and for anyone who has watched a spreadsheet “balance” only because a difference got plugged into a suspense line and nobody checked it again. For the mechanics behind the check itself, see how verification works; for the rest of what a defensible close looks like before, during, and after fieldwork, visit the finance team use cases hub.