Statutory Reporting
AFS Restatement Tracker
Prior-year corrections of errors and restatements disclosed in the current annual financial statements.
Restatements are a barometer of financial reporting reliability
A high volume of prior-year restatements signals that the annual financial statements were not reliable when first published, which directly undermines the accounting officer's assertion and attracts AGSA scrutiny under the going-concern and internal-control narratives. GRAP 3 governs how corrections of errors and changes in policy are disclosed, and oversight bodies read restatement trends as a leading indicator of control weakness. AuditPro Core maintains a structured register of every restatement so that the cause, magnitude and recurrence of corrections are visible long before the audit committee meets.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Restatements disclosed
37
▼ 11 vs prior year
Net value restated
R 318 m
Errors vs policy changes
29 / 8
Entities restating
14
of 41
Restatements by cause and year
Largest restatements
| Entity | AFS line item | Value | Cause |
|---|---|---|---|
| Dept of Health (KZN) | PPE depreciation | R 92 m | Error |
| Buffalo City Metro | Provision for landfill | R 64 m | Estimate |
| Gauteng Transport | Accrued income | R 48 m | Error |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Correction of error versus change in estimate
GRAP 3 distinguishes prior-period errors, which require retrospective restatement of comparatives, from changes in accounting estimate, which are applied prospectively. Misclassifying one as the other is itself a disclosure failure.
Why recurrence matters more than incidence
An isolated restatement may reflect a genuine one-off error, but the same line item restated year after year points to a systemic control breakdown that the audit committee must escalate.
Materiality and aggregation
Individually immaterial corrections can aggregate to a material restatement. Tracking each correction with its rand impact allows the cumulative effect on the prior-year position to be assessed against the materiality threshold.
The trail back to source
Each restatement should be traceable to the originating transaction, the misstatement it corrected and the management or audit finding that triggered it, so the correction can be defended in the audit file.
How AuditPro Core Bridges the Gap
- Structured register: each restatement is logged with GRAP classification, affected line, rand impact and originating cause.
- Recurrence analytics: the dashboard highlights line items restated across multiple cycles to expose systemic weakness.
- Materiality aggregation: individual corrections roll up so the cumulative impact is tested against the disclosed threshold.
- Traceability to source: every entry links to the originating transaction and finding for defensible audit evidence.
Key Takeaways
- Restatement volume and recurrence are leading indicators of weak financial controls.
- GRAP 3 requires errors to be restated retrospectively but estimate changes applied prospectively.
- Aggregate immaterial corrections to test whether the combined effect is material.
- Every restatement should trace to its originating transaction and triggering finding.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.