When an error surfaces after statements are issued
What a firm does when it learns of a material error after the statements and its report are issued: ISA 560, revised statements and a locked file.
By Achekam · · 5 min read · For Accountants & audit firms in South Africa, Nigeria, Kenya
The statements went out, the bank has them, and the file has been assembled and locked. Then the client's new financial manager calls: while setting up the new year, she found that a large batch of sales invoices was recorded twice in the last month of the year. Revenue and receivables in the issued statements are overstated, and the amount is well above materiality.
Nobody on the engagement team did anything wrong to cause this, and the auditor has no duty to keep looking after the report is issued. But once the auditor knows, ISA 560 says what happens next. So does the way the firm keeps its records: the file must show what changed, when and why, without disturbing what was issued.
What the standards expect after issue
After the statements are issued, the auditor has no obligation to perform any audit procedures on them. The obligation arises when a fact becomes known to the auditor that, had it been known at the date of the report, might have caused the auditor to amend the report.
When that happens, ISA 560 requires the auditor to:
- discuss the matter with management and, where appropriate, those charged with governance;
- determine whether the statements need amendment; and
- if they do, inquire how management intends to address the matter in the statements.
The question in step 2 is not whether the fact is uncomfortable, but whether it relates to conditions that existed at the reporting date and is material. A double-recorded batch of invoices clearly is.
Talking to management and those charged with governance
The first conversation sets the tone. Management may prefer to fix the error quietly in next year's statements. Whether that is acceptable depends on the framework, the law and who relies on the issued statements. IAS 8 deals with prior-period errors by correcting them retrospectively, usually by restating the comparatives in the next statements issued after discovery. But where the issued statements are being relied on now, for a loan, a sale of shares or a regulatory filing, users may need revised statements rather than a correction a year later.
The auditor's role is to make sure the decision is properly made and that, if the statements are amended, the auditor does the work the standard requires. Record each discussion: who was present, what was proposed and what was agreed.
Revised statements and a new report
If management amends the statements, ISA 560 requires the auditor to perform the necessary procedures on the amendment and to extend the subsequent events procedures up to the date of the new auditor's report. The new report must not be dated earlier than the date the amended statements are approved.
The new report includes an emphasis of matter or other matter paragraph referring to the note that explains the reason for the amendment and to the earlier report. Where law and the framework allow management to restrict the amendment to the effect of the specific matter, the auditor may restrict the extended procedures to that amendment and dual-date the report, or provide a new or amended report with a statement that the procedures are restricted to the amendment.
The auditor also reviews the steps management takes to make sure anyone who received the original statements, and the original report, is told about the situation.
If management does not take the necessary steps, the auditor notifies management and those charged with governance that the auditor will seek to prevent future reliance on the report, and, if the statements are still used without amendment, takes appropriate action, which may need legal advice.
The issued version stays locked; changes go in as addenda
Correcting an issued set must never mean overwriting it. Readers who relied on the original need to be able to see exactly what they received.
In Achekam, issuing stores the final PDF with a fingerprint and locks that version. When the partner records the audit report as issued, the statements' fingerprint is bound to it and the file-assembly clock starts. Whatever the revised statements look like, the version originally issued can still be shown exactly as it was, with its report.
On the audit file, after the report is issued, the engagement partner assembles and locks it. From then on, changes can only be added as addenda, and unlocking needs a second partner or the quality reviewer. For an error found after issue, that is the right shape: the new procedures, the evidence and the conclusion on the amended statements go into the file as addenda, not as edits to papers that were final.
ISA 230 expects exactly this for work done after the report date: the circumstances, the new procedures, the evidence and conclusions, and who made and reviewed the changes. In South Africa, IRBA Board Notice 512 of 2023, Rule 4, requires the final engagement file to be assembled within 60 days of the report date and kept for at least five years, for audits of periods beginning on or after 15 December 2024. Whatever is added after assembly should say what was added, when, why and by whom. How assembly and locking work is described in audit file assembly and archive.
Recording the consultation
A post-issue error is one of the clearest cases for formal consultation: it involves legal questions, users the firm cannot see and a professional judgement about what management must do. Staff can take a technical consultation on an engagement from question to conclusion and closure, and record a difference of opinion with each party's position, escalation and resolution.
Record Governance keeps a log of changes to governed records, showing who did what, when and with what result, which can be filtered and checked for an unbroken chain. It covers records under record governance, not every screen, so treat it as support for the file's history, not the history itself. The consultation, the addenda and the new report are the primary record.
A response plan, in order
- Confirm the facts and assess materiality against the original materiality.
- Discuss with management and those charged with governance, and record it.
- Open a consultation; take legal advice where reliance or confidentiality is in question.
- Agree how the statements will be amended, or why amendment is not needed.
- Perform procedures on the amendment and extend subsequent events work to the new report date.
- Issue a new report with the required paragraph, and check that recipients of the original are told.
- Add everything to the locked file as addenda.
The IFRS Foundation's page on IAS 8 summarises the standard, now titled Basis of Preparation of Financial Statements, including the treatment of corrections of prior-period errors. Facts found before the report is dated are handled differently, as covered in subsequent events procedures up to the report date.
The conversation to have now
Agree in your firm, before it happens, who decides when a post-issue error is serious enough to recall statements, and who speaks to the client. Working that out on the day the call comes in is how firms make the wrong decision quickly.
General guidance only, not advice on your own circumstances. Tax and payroll rules change: check the current position with the authority or your adviser.
