Financial Management
Fruitless & Wasteful Expenditure
Fruitless and wasteful expenditure incurred by primary cause.
Why Fruitless and Wasteful Expenditure Is Tracked by Cause
Fruitless and wasteful expenditure is spending that was made in vain and could have been avoided had reasonable care been taken, and the MFMA and PFMA require it to be recorded, investigated and recovered from the responsible person. Analysing it by primary cause, such as interest on late payments or penalties, turns a compliance register into a tool for preventing the next avoidable loss. AuditPro Core breaks down fruitless and wasteful expenditure by primary cause so root causes are addressed, not just the amounts disclosed.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Total Incurred
R 42 m
▲ 8% YoY
Incidents Logged
318
this year
Recovered
R 4.1 m
10% of total
Under Investigation
R 21 m
pending
Fruitless Expenditure by Cause (R m)
Cause Detail
| Cause | Amount (R m) | Incidents | Status |
|---|---|---|---|
| Interest on Arrears | 18 | 142 | Recurring |
| Penalties | 11 | 86 | Recurring |
| Cancelled Contracts | 7 | 24 | Investigated |
| Litigation Costs | 4 | 41 | Ongoing |
| Other | 2 | 25 | Closed |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
The avoidability test
Expenditure is fruitless and wasteful only if a reasonable person would have avoided it given the circumstances. The test is care taken, which is why interest and penalties from negligence are the classic examples.
Cause analysis
Grouping losses by cause, such as late-payment interest, cancelled travel or contract penalties, reveals which control weaknesses are recurring. The same cause appearing repeatedly is a control failure, not bad luck.
Recovery and liability
Where an official is responsible, the loss must be recovered from them following investigation. Linking each amount to its cause and responsible function supports that recovery and the required consequence management.
How AuditPro Core Bridges the Gap
- Continuous monitoring: fruitless and wasteful items are captured and classified by cause as they arise, keeping the register and its disclosure current.
- Exception workflow: recurring causes, such as repeated late-payment interest, are flagged so the underlying control is fixed.
- Audit-ready export: the register by cause exports for the financial-statement note and the AGSA's review of the response.
- Traceability to source: each loss links to the transaction and responsible function, supporting recovery and consequence management.
Key Takeaways
- The test is avoidability with reasonable care, not merely poor outcome.
- Cause analysis turns a register into prevention of the next loss.
- Recurring causes are control failures that demand a fix, not just disclosure.
- Link losses to responsible functions to enable recovery.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.