Fruitless & Wasteful
Duplicate & Double Payment Detection
Duplicate and double-payment detection scans the creditors ledger for invoices paid more than once — whether by error or deliberate resubmission.
Why Duplicate-Payment Detection Matters
Paying the same invoice twice is fruitless and wasteful expenditure that high transaction volumes make almost inevitable without analytics. A duplicate may be an honest capture error or a deliberate resubmission, but either way the state loses money it can only sometimes claw back, and the MFMA and PFMA require such losses to be prevented, detected and recovered. AuditPro Core runs forensic duplicate-detection across the creditors ledger so double payments surface before they are made and overpayments are recovered when they slip through.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Duplicate payments
2 140
▲ 7%
Value duplicated
R96 m
Recovered to date
R31 m
32%
Avg detection lag
47 days
Duplicate-payment value by month (R m)
Duplicates by match type
| Match type | Count | Value (R m) |
|---|---|---|
| Exact invoice number | 980 | 42.6 |
| Same amount & vendor | 612 | 28.4 |
| Fuzzy reference | 348 | 15.2 |
| Split across runs | 200 | 9.8 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Exact and Fuzzy Duplicates
Some duplicates share an identical invoice number; others alter a digit, date or reference to evade simple matching. Detection must catch both the exact and the near-match.
Error vs Fraud
An accidental double capture and a deliberate resubmission look similar in the ledger but demand different responses. Pattern and timing usually distinguish the careless from the calculated.
Recovery Window
Overpayments are most recoverable while the supplier relationship is active and the payment recent. Speed of detection directly determines how much of the money comes back.
Prevention vs Detection
Catching duplicates before release is far cheaper than recovering them after. Pre-payment screening converts a recovery problem into a prevented loss.
How AuditPro Core Bridges the Gap
- Forensic matching: AuditPro Core applies exact and fuzzy logic across invoice number, amount, date and vendor to catch disguised duplicates.
- Pre-payment screening: suspected duplicates are flagged before release where possible, preventing the loss outright.
- Exception workflow: confirmed double payments route to recovery against the supplier with a documented trail.
- Audit-ready output: the duplicate-payment schedule exports for the fruitless-expenditure disclosure.
Key Takeaways
- High volume makes some duplicate payments almost inevitable without analytics.
- Fuzzy matching is essential; the deliberate ones alter a digit to evade checks.
- Detect fast — recoverability falls as the payment ages.
- Pre-payment screening beats post-payment recovery every time.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.