Irregular Expenditure
Deviation & Contract Expansion Abuse
Deviation and expansion abuse tracks SCM deviations and contract expansions that exceed Treasury thresholds and approval limits — the exception turned into routine.
Why Deviation Abuse Matters
Deviations and contract expansions exist as narrow, exceptional escapes from competitive procurement — but when overused they become the standing route around the SCM framework. National Treasury sets thresholds and approval requirements precisely because unjustified deviations and expansions are a leading source of irregular expenditure and AGSA findings. AuditPro Core tracks deviations and expansions against Treasury thresholds and approval limits so the exception does not quietly become the rule.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Deviations reported
8 940
Value
R22.6 bn
▲ 14%
Above 15% expansion
1 240
Not reported to NT
27%
Deviation value by reason (R bn)
Highest-deviation entities
| Entity | Deviations | Value (R m) |
|---|---|---|
| SOE C | 1420 | 4860 |
| Dept B | 1180 | 3240 |
| Metro A | 980 | 2680 |
| Prov dept D | 760 | 1940 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Deviation vs Competition
A deviation departs from competitive bidding on stated grounds such as urgency or sole supplier. It is lawful only when the grounds are genuine and the approval proper; otherwise it is irregular.
Contract Expansion Limits
Expanding a contract beyond defined percentage and value thresholds requires specific approval. Repeated expansions that grow a contract far beyond its award are a classic abuse signature.
Threshold Discipline
Treasury thresholds set the line between an approvable exception and an irregular one. Tracking spend against those thresholds shows where the line has been crossed.
Pattern of Reliance
An entity that meets ordinary needs through deviations has a structural SCM problem, not isolated emergencies. Frequency, not just individual cases, is the real risk signal.
How AuditPro Core Bridges the Gap
- Threshold testing: AuditPro Core checks each deviation and expansion against Treasury limits and approval requirements.
- Pattern detection: recurring deviations by supplier, category or unit surface structural reliance, not just single cases.
- Exception workflow: deviations breaching thresholds route to review and irregular-expenditure determination.
- Traceability to source: each deviation links to its grounds, approval and the contract it modifies.
Key Takeaways
- Deviations are lawful only on genuine grounds with proper approval.
- Repeated expansions that dwarf the original award are a classic abuse signature.
- Watch frequency — habitual deviation is a structural SCM failure.
- Test against Treasury thresholds to know when the line is crossed.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.