Financial Misconduct
Supplier Payment Anomalies
Duplicate, split and out-of-sequence payments detected across supplier disbursements.
Finding the leakage in the disbursement run
Duplicate, split and out-of-sequence payments are among the most common and recoverable forms of financial loss in public-sector accounts payable. They sit squarely within the internal-control objectives of COSO and the financial-management duties imposed by the MFMA and PFMA, and they are routinely tested in AGSA expenditure audits. AuditPro Core runs continuous analytics over the full disbursement population so these anomalies are caught before the payment clears.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Anomalous payments
9,640
Value flagged
R1.4 bn
Duplicates confirmed
R210 m
Recovered to date
R96 m
▲ 21%
Anomalies by type
Anomaly detail
| Anomaly type | Payments | Value (R m) |
|---|---|---|
| Duplicate payment | 3120 | 420 |
| Split payment | 2480 | 380 |
| Out of sequence | 1860 | 290 |
| Round-amount | 1280 | 190 |
| Weekend / after-hours | 900 | 120 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Duplicate payments
The same invoice paid twice, or two vendors created for one supplier, drains cash that must then be recovered. Matching on amount, date, invoice number and bank account exposes the classic patterns.
Split payments
Breaking one purchase into several smaller payments to stay under a delegation or procurement threshold is a deliberate control circumvention. Clustering payments to a supplier just below a threshold reveals the behaviour.
Out-of-sequence anomalies
Payments dated before the invoice, before goods receipt, or outside normal run cycles often indicate manual override or backdating. Sequence testing turns these into investigable exceptions.
Full-population over sampling
Because the analytics run over every transaction rather than a sample, low-value but high-frequency leakage that sampling would miss is captured, in line with data-analytics expectations under ISSAI.
How AuditPro Core Bridges the Gap
- Continuous monitoring: the full payment population is scanned for duplicate, split and sequence patterns on each run rather than once a year.
- Reconciliation: invoices, goods receipts and bank details are matched three ways to confirm a genuine anomaly before it is raised.
- Exception workflow: flagged payments are assigned, investigated and either cleared or pushed to recovery, with the outcome recorded.
- Traceability to source: each anomaly links back to the original invoice image, voucher and approval for audit evidence.
Key Takeaways
- Duplicate and split payments are highly recoverable if caught quickly.
- Clustering just below a threshold is a deliberate-circumvention signal, not coincidence.
- Full-population analytics catch the low-value, high-frequency leakage sampling misses.
- Sequence testing exposes backdated and overridden payments.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.