Financial Management
Duplicate Payment Detection
Fuzzy matching of invoice number, amount and vendor to find duplicate disbursements.
Why duplicate payments erode public funds
Paying the same invoice twice is a direct loss of public money and a control failure that auditors expect to be prevented and detected, yet duplicates persist where invoice numbers vary slightly or vendors are recorded inconsistently. Strong detection supports the accounting officer's duty under the MFMA to safeguard resources and recover overpayments. AuditPro Core applies fuzzy matching across invoice, amount and vendor fields to find duplicates that exact-match controls miss.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Duplicates flagged
87
Value at risk
R6.2 m
Recovered to date
R2.1 m
▲ R0.9 m
Confirmed false positives
14
Duplicate exposure by match type
Top duplicate candidates
| Invoice | Vendor | Amount (R) |
|---|---|---|
| INV-20451 | Fleet Services | 412300 |
| INV-88120 | Office Mart | 96750 |
| INV-33902 | Civil Works | 287400 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Why exact matching fails
Duplicates often differ by a leading zero, a transposed digit, a trailing space or a slightly different vendor spelling. Exact-key matching passes these straight through.
Fuzzy matching logic
Comparing normalised invoice numbers, amounts within tolerance and similar vendor names catches near-duplicates. Each candidate pair carries a similarity score to rank likelihood.
Same-amount, same-vendor clusters
Repeated identical amounts to one vendor over a short period are a strong duplicate indicator even where invoice references differ, and warrant a closer look at the underlying obligation.
Recovery and prevention
Confirmed duplicates trigger recovery action and a review of the control that allowed them, since detection without prevention leaves the door open to recurrence.
How AuditPro Core Bridges the Gap
- Fuzzy candidate matching: normalised invoice, amount-tolerance and vendor-name similarity surface near-duplicates that exact keys miss.
- Scored ranking: each candidate pair carries a confidence score so the strongest matches are reviewed first.
- Exception workflow: confirmed duplicates are routed for recovery and the false positives cleared with a documented reason.
- Traceability to source: every flagged pair links back to both payment records and supporting invoices for verification.
Key Takeaways
- Exact-match controls miss duplicates caused by formatting and spelling variance.
- Score candidate pairs to prioritise the most likely duplicates.
- Repeated identical amounts to one vendor warrant scrutiny even with different references.
- Pair detection with recovery action and a control fix to prevent recurrence.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.