Procurement Anomalies
Below-Radar Spend Aggregation
Aggregates per-vendor annual spend transacted entirely below the quotation threshold.
Why threshold-splitting is a classic abuse
Procurement thresholds set the point at which quotations give way to formal competitive bidding, and deliberately keeping each order just below the threshold while a vendor's annual total far exceeds it is one of the oldest ways to avoid competition, squarely contravening section 217 and the SCM regulations. The individual orders look compliant; only the aggregate reveals the avoidance. AuditPro Core aggregates per-vendor annual spend transacted entirely below the quotation threshold so structured threshold-splitting is exposed.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Below-Threshold Vendors
318
no large orders
Annual Total > R1m
44
▲ 9
Aggregate Spend
R 96.7m
uncompeted
Avg Transaction
R 11,400
Aggregate Below-Threshold Spend by Band (R'm)
Largest Below-Radar Vendors
| Vendor | Transactions | Avg (R) | Annual (R'000) |
|---|---|---|---|
| Vendor 1180 | 412 | 9800 | 4040 |
| Vendor 1224 | 388 | 8400 | 3260 |
| Vendor 1301 | 297 | 9100 | 2700 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Thresholds and their purpose
Thresholds match procurement effort to value, reserving full competition for larger spend. Splitting a large requirement into many small orders defeats that purpose while appearing to follow it.
Aggregation reveals the pattern
No single sub-threshold order is irregular, so detection requires summing a vendor's orders over the year. The aggregate exceeding what a competitive process would have required is the signal.
Structured avoidance
Regular, similar-value orders to one vendor just under the limit suggest deliberate structuring rather than coincidence. The regularity is as telling as the total.
Planning failure or design
Aggregation also catches poor demand planning, where a foreseeable annual need was never put out to tender. Either way the remedy is a contract, not repeated quotes.
How AuditPro Core Bridges the Gap
- Spend aggregation: sums each vendor's annual orders to reveal totals exceeding the threshold through many small buys.
- Exception workflow: vendors with structured below-threshold spend are flagged for competitive-process review.
- Traceability to source: links the aggregate back to every constituent order for evidence.
- Continuous monitoring: tracks cumulative vendor spend through the year so avoidance is caught before year-end.
Key Takeaways
- Individual sub-threshold orders look fine; the aggregate exposes splitting.
- Regular similar-value orders to one vendor suggest deliberate structuring.
- A foreseeable annual need belongs on a contract, not in repeated quotes.
- Monitor cumulative vendor spend through the year, not only at audit.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.