Irregular Expenditure
Condonation — National Treasury Applications
Status of irregular expenditure condonation applications submitted to National and Provincial Treasury.
Why condonation applications matter
Condonation by National or Provincial Treasury is the formal mechanism that clears irregular expenditure from the books once a section 32 investigation supports it, and the status of these applications shows whether the resolution pipeline reaches its end. The MFMA and PFMA, together with Treasury's irregular expenditure framework, prescribe what an application must contain and who may condone. AuditPro Core tracks each application from submission through Treasury decision, so an entity cannot let condonable balances sit unsubmitted or stall in a treasury queue without that delay being visible and owned.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Applications submitted
318
Value awaiting decision
R14 bn
Approved
112
35%
Rejected / returned
97
Condonation application outcomes
Application detail
| Treasury | Submitted | Approved | Value pending (R bn) |
|---|---|---|---|
| National Treasury | 177 | 64 | 8.4 |
| Provincial Treasuries | 141 | 48 | 5.6 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Condonation as closure
Condonation is the act by which the empowered treasury accepts the irregular expenditure and authorises its removal from the disclosed balance. It is the only lawful way to clear an item that will not be recovered or written off.
Application prerequisites
A valid application must show the investigation outcome, the loss determination and the steps taken on consequence management. Incomplete applications are returned, adding months to the cycle.
Treasury decision latency
Applications can sit in the treasury queue for extended periods, and tracking that latency separates entity delay from treasury delay. Knowing where the bottleneck lies directs the right escalation.
How AuditPro Core Bridges the Gap
- Application lifecycle: each condonation application is tracked from preparation to Treasury decision with dates and outcomes.
- Completeness checks: the system validates that investigation and loss-determination evidence is attached before submission.
- Latency attribution: delays are attributed to the entity or the treasury so escalation targets the real bottleneck.
- Audit-ready trail: the application and its supporting pack export for the audit file and oversight reporting.
Key Takeaways
- Condonation is the only lawful exit for irregular expenditure that will not be recovered or written off.
- Applications need investigation and loss-determination evidence or they are returned.
- Tracking latency separates entity delay from treasury queue delay.
- Unsubmitted condonable balances are a self-inflicted source of a growing register.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.