The Export Gate: Why Rexfin Refuses to Export Numbers It Cannot Verify

Plenty of finance tools will flag a balance-sheet break with a red banner and let you export the board pack anyway. The warning gets acknowledged, the deck goes out, and the untied number rides along with everyone’s sign-off attached to it. Rexfin does something less comfortable and more useful: when a model doesn’t tie out and the check is enforced, the export button does not work. Not “produces a document with a caveat”: refuses to produce a document at all.

Two checks, one verdict

Every export request runs through a single decision that combines two things. First, a local balance check on the seeded statements: does Assets equal Liabilities plus Equity, period by period, with equity correctly including non-controlling interest. Second, a cash-flow identity check: does the net change reported in the cash flow statement actually match the movement in the balance sheet’s cash position, including the effect of exchange-rate changes on cash for companies with foreign operations. Skipping that FX line is the most common way a cash-flow check produces a false failure: Rexfin includes it by default.

Both checks are pure functions: given the same model state, they always return the same verdict. That matters because every export path (the API route, the background job that assembles the pack, the button in the UI) reads from the exact same decision. There is no second copy of the rule that could quietly drift out of sync.

What actually blocks, and what only warns

The rule is deliberately asymmetric. A failing identity on an actual, source-anchored period is blocking: no export, full stop, with the specific broken identity named (the amount, the period, the delta). A failing identity on a forecast period is advisory only: it surfaces as a warning because a forecast is allowed to be provisional in a way an audited actual is not. This is what keeps the gate from becoming a nuisance that blocks every model over a modelling assumption nobody has finalized yet.

The gate also only runs enforced once it has been calibrated: on real filings, the policy has to reach zero false positives and near-complete true-positive detection before it flips from advisory-only to actually blocking exports. That calibration decision is recorded, not silent: the point is that the gate earns the right to block before it starts blocking.

Citability is part of the gate, not a separate claim

A number can balance perfectly and still not be citable. Rexfin’s gate also checks whether each figure feeding an identity came from at least two independent extraction backends agreeing on the value. A figure below that threshold cannot make an identity “actual-anchored” for gating purposes: a number nobody can defend to a source page doesn’t get to count as verified, even if the arithmetic happens to be correct.

Because real IFRS statements are printed in thousands, the tolerance used throughout is scale-relative rather than a flat dollar threshold: the greater of the statement’s rounding unit or half a percent of the printed figure. A one-unit rounding artifact on a statement expressed in thousands should never trigger a false block, and a genuine break beyond that band should never slip through as a rounding artifact.

A badge that can’t overstate itself

The verdict is also what the trust badge on screen and on the artifact itself reflects: verified, verified with advisories, blocked, or (for a forecast-only model with no actuals yet) honestly stamped “modelled only.” The badge never shows green because export happened to be allowed in advisory mode; it shows the true state of the identities, every time, and any edit to the model invalidates a prior verified stamp until it’s re-checked.

Who needs a gate, not a warning

If your board pack has ever gone out with a footnote acknowledging a known discrepancy “we’ll fix next quarter,” this is built for you. It’s aimed at CFOs and advisors who need the export itself to be the proof, not a claim of diligence sitting next to a number nobody re-checked. The gate is what turns everything upstream of it (the statement grid’s reconciliation status and the provenance drawer’s source pages) from a nice interface into an enforced precondition. See the rest of how Rexfin’s trust chain fits together at the product tour hub.