Inconsistent reporting
Quarterly Report Submission Timeliness
Late quarterly performance reports break the oversight chain that the MFMA builds between management, council and Treasury.
Why Timely Section 52 Reporting Matters
Section 52 of the MFMA requires the mayor to submit quarterly reports on budget and performance to council, supporting in-year oversight. Late submission deprives council of the timely information needed to intervene, and chronic lateness is itself a compliance finding. AuditPro Core tracks submission dates against statutory deadlines so reporting timeliness is monitored and defensible.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Reports due
4
On time
2
50%
Avg delay
11 days
Council noted
4
of 4
Days late by quarter
Submission detail
| Quarter | Due | Submitted | Days late |
|---|---|---|---|
| Q1 | 2025-07-30 | 2025-07-29 | 0 |
| Q2 | 2025-10-30 | 2025-11-13 | 14 |
| Q4 | 2026-04-30 | 2026-05-20 | 20 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Section 52 obligation
The MFMA sets specific timeframes for quarterly reporting to council and Treasury. These are legal deadlines, not internal targets, and missing them is a compliance breach.
In-year oversight
Quarterly reports exist so council can act on emerging problems before year-end. A report delivered late loses most of its corrective value.
Submission timeliness
Timeliness measures the gap between the deadline and actual submission. Tracking it per quarter reveals whether lateness is occasional or systemic.
Treasury alignment
The same figures flow to provincial and national Treasury for consolidated oversight. Late or inconsistent submission disrupts that consolidation and draws attention.
How AuditPro Core Bridges the Gap
- Deadline tracking: each report's submission date is measured against the statutory deadline automatically.
- Exception workflow: overdue or at-risk reports escalate before the deadline passes.
- Continuous monitoring: timeliness trends across quarters expose systemic reporting delays.
- Audit-ready export: the submission log exports as evidence of MFMA section 52 compliance.
Key Takeaways
- Section 52 deadlines are statutory; missing them is a compliance finding in its own right.
- Late reports forfeit the in-year corrective value that justifies quarterly reporting.
- Tracking timeliness per quarter distinguishes occasional slippage from systemic delay.
- A clean submission log is the simplest defence against a timeliness 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.