Predetermined Objectives
APP Tabling Timeliness
An Annual Performance Plan that is tabled late is not merely an administrative lapse; it weakens the link between budget, planning and the mandate the council approved.
Why Tabling on Time Matters
The MFMA and the municipal planning regulations require the Annual Performance Plan to be tabled before the start of the financial year so that targets, budget and the IDP are aligned from day one. Late tabling severs that chain and is a recurring source of AGSA compliance findings on predetermined objectives. AuditPro Core dates each tabling event against the prescribed deadline so timeliness becomes a tracked control rather than an afterthought.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Entities tracked
64
Tabled on time
49
77%
Late tabling
15
23%
Avg delay (days)
11
▼ 4 days
Days late by entity tier
Late tabling register
| Entity | Due | Tabled | Days late |
|---|---|---|---|
| Mahikeng LM | 30 Jun | 16 Jul | 16 |
| Thabazimbi LM | 30 Jun | 08 Jul | 8 |
| Naledi LM | 30 Jun | 22 Jul | 22 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
The Statutory Deadline
The plan must reach council and be tabled within the timeframe the MFMA prescribes relative to the financial year start. Missing it means the year begins without an approved performance mandate, undermining in-year monitoring.
Alignment with Budget and IDP
The APP only carries assurance when it is tabled alongside the budget and integrated development plan it draws from. Tabling out of sequence breaks the golden thread auditors test between plan, budget and reported results.
Oversight Consequence
A late or absent plan leaves the council and oversight committees without the baseline against which quarterly and annual performance is later assessed, eroding accountability for the whole cycle.
How AuditPro Core Bridges the Gap
- Deadline tracking: each tabling date is captured and measured against the MFMA-prescribed cut-off, with overdue plans flagged automatically.
- Exception workflow: a missed or at-risk deadline routes to the responsible official with a documented escalation trail.
- Audit-ready evidence: the tabling record exports as a dated schedule that supports the compliance working paper on predetermined objectives.
- Year-on-year traceability: repeat late tablers surface across cycles before they become a recurring AGSA finding.
Key Takeaways
- The APP must be tabled before the financial year starts to keep budget, IDP and targets aligned.
- Late tabling is a common compliance finding and weakens the basis for in-year monitoring.
- Treat the tabling date as a tracked control with a clear owner and escalation path.
- A dated tabling record is the simplest evidence of compliance for the audit file.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.