Irregular Expenditure
Irregular Expenditure — Disclosure Completeness
Audit findings on understated or incomplete irregular expenditure disclosure notes.
Why disclosure completeness is tested
Completeness is the hardest assertion for irregular expenditure because the risk is understatement of what management would rather not disclose. The MFMA and PFMA require full disclosure of all irregular expenditure identified, and the AGSA routinely raises findings where SCM transgressions never reached the note. AuditPro Core cross-references procurement, payment and deviation data against the disclosed register so that items hiding in the transaction stream are surfaced rather than left to a manual sweep at year-end.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Entities with completeness limitation
112
▲ 8 vs prior year
Known understatement
R3.4 bn
Unquantifiable disclosure
58 entities
Complete & reliable notes
39%
Disclosure note reliability (entities)
Completeness limitations by sphere
| Sphere | Entities | Known understatement (R m) |
|---|---|---|
| Local government | 71 | 2140 |
| Provincial | 28 | 880 |
| National & SOEs | 13 | 380 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
The understatement risk
Unlike most balances, irregular expenditure is biased toward understatement because disclosure invites consequence management. Auditors therefore design tests that search for unrecorded items rather than verifying only what was disclosed.
Population to register tracing
Completeness is tested by working from the full population of payments and SCM transactions toward the register, not the other way around. Any transaction bearing a transgression marker that is absent from the note is a potential finding.
Detected versus disclosed
An entity may detect irregular expenditure internally yet fail to disclose it because investigation is incomplete. The framework requires disclosure on detection, with the determination process running in parallel, not as a precondition.
How AuditPro Core Bridges the Gap
- Cross-population matching: procurement, payment and deviation records are matched against the disclosed register to isolate items that were never noted.
- Exception workflow: suspected unrecorded items raise an exception that must be cleared, disclosed or formally rejected with reasons.
- Traceability to source: each disclosed line links back to the originating order, contract and payment so completeness can be evidenced, not asserted.
- Continuous monitoring: transgression markers are evaluated as transactions post, so the register builds through the year instead of in a year-end scramble.
Key Takeaways
- Treat irregular expenditure as an understatement risk and test completeness from the transaction population inward.
- Disclosure is triggered by detection, not by the conclusion of an investigation.
- Every detected transgression should be traceable to a disclosed line or a documented reason for exclusion.
- A complete note is built continuously, reducing the year-end completeness 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.