Procurement Anomalies
Procurement Card Abuse Detection
Flags procurement-card transactions showing split spend, weekend use and MCC red flags.
Why procurement cards invite abuse
Procurement cards speed up low-value buying but, by removing the order-and-approval friction, they create fertile ground for split spend, personal use and weekend transactions that the MFMA's control requirements and good governance are meant to prevent. Card abuse is easy to commit and easy to miss in aggregate. AuditPro Core flags card transactions showing split spend, weekend use and merchant-category red flags so misuse is detected continuously rather than at an annual sample-based review.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Flagged Cards
23
▲ 4 vs last quarter
Suspect Spend
R 3.8 m
▲ R 0.6 m
Weekend Transactions
187
9% of all swipes
Within Policy
94%
▲ 2%
Flagged Transactions by Risk Type
Highest-Risk Cardholders
| Cardholder | Department | Flags | Spend (R'000) |
|---|---|---|---|
| P. Dlamini | Facilities | 14 | 412 |
| S. Botha | Fleet | 11 | 388 |
| N. Khumalo | Community Services | 9 | 274 |
| R. Pillay | Electricity | 7 | 196 |
| M. van Wyk | Corporate Services | 5 | 143 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Splitting to dodge limits
A purchase broken into several transactions just under the card limit evades the single-transaction control. Detecting same-merchant, same-day splits exposes this directly.
Merchant category codes
Every transaction carries an MCC describing the merchant type. Spend at categories incompatible with official duties, such as entertainment or fuel anomalies, is an immediate red flag.
Timing patterns
Weekend, public-holiday or after-hours transactions on a card meant for official operational buying warrant explanation. Timing alone is not proof, but it sharply narrows where to look.
Card controls
Effective card programmes set limits, restrict categories and require timely reconciliation of each transaction to a receipt. Where reconciliation lapses, abuse goes undetected.
How AuditPro Core Bridges the Gap
- Pattern detection: flags split transactions, weekend use and high-risk merchant categories across all cards.
- Exception workflow: flagged transactions are routed to the cardholder for receipt and justification.
- Reconciliation: matches each transaction to its supporting receipt and business purpose.
- Continuous monitoring: screens card activity as it posts rather than at an annual review.
Key Takeaways
- Same-merchant same-day splits evade single-transaction limits.
- Merchant category codes quickly flag out-of-scope spend.
- Weekend and after-hours use warrants explanation.
- Tie every card transaction to a receipt and business purpose.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.
