Audit Quality
Audit Cycle Turnaround Time
Elapsed days from AFS submission to signed audit report, benchmarked against the legislated timeframe.
Why audit turnaround time is an accountability metric
The MFMA and PFMA set firm deadlines for submitting financial statements and for the Auditor-General to report, because late accountability erodes the value of oversight. Elapsed time from AFS submission to a signed audit report reflects both the quality of the statements submitted and the efficiency of the audit. AuditPro Core benchmarks turnaround against the legislated timeframe so delays can be attributed and addressed before they become a pattern of non-compliance.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Avg turnaround
94 days
target 90
Within legislated window
71%
Reports over 180 days
28
Fastest sphere
National
82 days avg
Average turnaround by sphere (days)
Slowest turnarounds
| Entity | Days | Main delay driver |
|---|---|---|
| District D | 241 | Disputed balances |
| Local Muni F | 198 | Late evidence |
| SOE G | 176 | Group consolidation |
| Metro A | 142 | Scope expansion |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
The legislated clock
The MFMA requires municipalities to submit AFS within two months of year-end and the AG to report within three months of receipt. Each leg of the cycle has a statutory boundary that can be measured.
What drives delay
Long turnaround usually reflects poor-quality submissions that generate many queries, late evidence provision, or unresolved disagreements. The delay is often a symptom of control weakness, not auditor pace.
Consequences of lateness
Late or outstanding audits delay tabling, weaken oversight and can themselves become a compliance finding. They also defer the corrective action that the report should trigger.
How AuditPro Core Bridges the Gap
- Timeline reconciliation: submission and sign-off dates are reconciled against statutory deadlines to compute slippage.
- Exception workflow: engagements breaching the legislated window raise a flag with the responsible parties identified.
- Audit-ready export: turnaround data exports for inclusion in oversight and treasury monitoring reports.
- Continuous monitoring: turnaround is trended across cycles to expose entities with chronic delay.
Key Takeaways
- Turnaround time measures both AFS quality and audit efficiency against a legal deadline.
- Most delay originates in poor submissions and slow evidence, not auditor pace.
- Late audits weaken oversight and defer the corrective action reports should drive.
- Benchmarking each leg of the cycle isolates where the slippage actually occurs.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.