Financial Management
Split Payments Below Threshold
Detection of orders deliberately split to stay under R30 000 quotation thresholds.
Why split orders signal procurement abuse
Supply chain regulations require formal quotations or competitive bidding above defined limits, and deliberately fragmenting a requirement into smaller orders to dodge the R30 000 quotation threshold is a recognised form of irregular expenditure. The practice defeats competitive process and is a frequent AGSA and PRECCA concern. AuditPro Core analyses purchasing patterns to expose orders that appear engineered to stay just below regulatory thresholds.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Suspected splits
142
▲ 34
Value involved
R18.6 m
Vendors implicated
29
Near R30k clusters
61
Split payment clusters by threshold band
Highest-value split clusters
| Vendor | Orders | Value (R) |
|---|---|---|
| Maintenance CC | 6 | 174900 |
| Catering Co | 5 | 148500 |
| ICT Supplies | 7 | 203700 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
The threshold regime
MFMA supply chain regulations escalate procurement requirements as value rises, with formal written quotations required above R30 000. Splitting a single requirement keeps each piece under the trigger.
Indicators of splitting
Multiple orders to the same vendor for similar goods within a short window, each landing just below the threshold, are the hallmark. Sequential or same-day awards strengthen the inference.
Why it is irregular
Circumventing the competitive process breaches the regulations regardless of whether value for money was obtained, making the resulting expenditure irregular and reportable.
Aggregation principle
The regulations look to the total value of a requirement, not the individual order. Auditors test whether related orders should have been aggregated and procured competitively.
How AuditPro Core Bridges the Gap
- Pattern detection: same-vendor, same-category orders clustered below the threshold within a defined window are flagged automatically.
- Aggregation view: related orders are summed to show the true requirement value against the threshold that should have applied.
- Exception workflow: flagged clusters route for explanation, with legitimate cases cleared and confirmed splits escalated as irregular expenditure.
- Audit-ready evidence: the splitting analysis exports with order-level detail traceable to the procurement source.
Key Takeaways
- Test the aggregate requirement value, not individual order amounts.
- Same-vendor clusters just below R30 000 in a short window are a red flag.
- Circumventing competitive process is irregular regardless of price obtained.
- Confirmed splits must be recorded in the irregular expenditure 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.