Statutory Reporting
Late & Non-Submission of Financial Statements
Missing the legislated AFS deadline is itself a reportable contravention, regardless of how clean the underlying numbers are.
Why Submission Deadlines Matter
Section 126 of the MFMA requires a municipality to submit its annual financial statements to the Auditor-General within two months of year-end (three months for consolidated statements), and the PFMA imposes parallel deadlines on departments and public entities. Late or non-submission is a material compliance breach in its own right, delays the audit, and is a recurring driver of adverse AGSA findings on consequence management. AuditPro Core tracks each entity's submission status against its statutory deadline so the accounting officer sees slippage while there is still time to act.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
On-time submissions
388
93% of entities
Late submissions
21
Non-submissions
8
no AFS lodged
Avg days late
17
Submission status by entity type
Entities still outstanding
| Entity | Due date | Days late | Status |
|---|---|---|---|
| Entity A | 2025-08-31 | 42 | Not submitted |
| Entity B | 2025-08-31 | 28 | Submitted late |
| Entity C | 2025-08-31 | 21 | Submitted late |
| Entity D | 2025-08-31 | 35 | Not submitted |
| Entity E | 2025-08-31 | 14 | Submitted late |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
The statutory clock
The deadline runs from financial year-end, not from when management feels the statements are ready. Once the date passes, the contravention is recorded irrespective of the eventual submission, so the calendar is the control.
Late versus non-submission
A late submission still produces statements the auditor can work with; a non-submission stalls the entire assurance cycle. The two carry different severities and the dashboard must distinguish them clearly.
Downstream consequences
Late AFS delays the audit, the annual report and the tabling cycle, cascading into Section 71 and oversight reporting. A single missed deadline therefore compromises a chain of statutory obligations, not just one.
How AuditPro Core Bridges the Gap
- Deadline calendar: every entity's statutory submission date is tracked against actual status, with countdown alerts before the date lapses.
- Exception workflow: entities trending toward late submission are escalated to the accounting officer with a reason and recovery date.
- Traceability to source: the submission record links to the acknowledgement of receipt from the Auditor-General.
- Audit-ready export: the late and non-submission register exports for the compliance audit and consequence-management file.
Key Takeaways
- The deadline runs from year-end; readiness of the numbers does not stop the clock.
- Late and non-submission are distinct severities and must be reported separately.
- A missed AFS deadline cascades into the annual report and oversight cycle.
- Early visibility of slippage is the only practical defence against the contravention.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.