What to Do When a Filing You Relied On Gets Restated

You built last quarter’s board pack, investor update, or covenant certificate off a company’s filed numbers. Then the next filing lands, and the comparative column for that same period shows a different figure than what you used. Is that a typo someone caught, or is the company genuinely restating its history under IAS 8? The two answers require very different responses, and from a single number sitting in a spreadsheet, you often cannot tell which one you are looking at.

This is a real and recurring problem, not an edge case. Comparative periods get corrected for all sorts of reasons (a reclassification, an error found in audit, an actual restatement of prior-year results), and if your reporting stack does not catch the discrepancy, you carry the stale number forward silently. Nobody notices until a board member or a lender cross-references an old deck against a new one and asks why they disagree.

Cross-checking a period against its own future

Rexfin treats each filing’s prior-year comparative as a second, independent read of a period you already have data for. When a new filing arrives, its comparative column for a period is checked against that same period’s originally reported value from the earlier filing, within a scale-relative tolerance that accounts for normal rounding.

If the two agree, the period gets stamped as cross-filing corroborated: a second independent source confirming the same number, which is a meaningfully stronger footing than a single filing’s word for it. If they disagree, the mismatch is never quietly dropped or silently overwritten. It is raised as a discrepancy that carries both values, the size of the delta, and a citation pointing to the exact document and page each number came from.

Telling an error from a restatement

The discrepancy is then classified as one of two things: a probable extraction error, meaning something went wrong reading one of the two documents, or a genuine issuer restatement under IAS 8, meaning the company itself changed the reported figure. That classification, backed by both source citations, is what turns “these two numbers don’t match” into an answer you can act on: chase the extraction if it looks like your side, or update your model and footnote the change if the company actually restated.

This matters most for anyone tracking a company’s history across interim reporting periods or multi-year trends: when a year is genuinely restated, the newer filing’s value should win in any trend view, but only after you have both numbers in front of you and know why they differ, not because the system quietly picked one.

Why this matters beyond your own books

If you are preparing a due diligence data room, tracking a portfolio company’s investor updates, or walking a board through numbers in a variance review meeting, you are frequently relying on someone else’s historicals, not just your own. A restatement upstream (at a subsidiary, an acquisition target, or a company you are analyzing) should not corrupt your downstream reports without you knowing it happened.

The honest limits

This only works when a second filing genuinely exists to compare against; a single filing with no later comparative has nothing to corroborate it. And the classification is a well-evidenced starting point, not a final verdict: deciding how to disclose a restatement to your own board or lenders is still a judgment call that belongs to a human who understands the context.

For more on how finance teams use Rexfin day to day, see the finance team use cases hub.