Procurement Anomalies
Fuzzy-Match Vendor Duplicates
Detects near-duplicate vendor names created to bypass spend or approval limits.
Why near-duplicate vendors defeat spend and approval limits
Exact-match deduplication misses the real abuse: slightly altered vendor names created to split spend below thresholds or to evade an approval limit, a pattern the AGSA links to irregular and even fraudulent expenditure. Fuzzy matching surfaces 'ABC Trading', 'A.B.C. Trading' and 'ABC Tradng' as the related entities they really are. AuditPro Core applies near-duplicate detection so SCM can collapse these variants and restore the integrity of threshold controls.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Fuzzy Clusters
112
Probable Duplicates
248
records
Combined Spend
R 41.2m
Match Confidence > 90%
67
clusters
Duplicate Clusters Detected by Confidence Band
Highest-Confidence Duplicate Pairs
| Record A | Record B | Match % | Spend (R'm) |
|---|---|---|---|
| Alpha Trading Pty | Alpha Trading (Pty) Ltd | 98 | 5.2 |
| Beta Civils CC | Beta Civil's CC | 96 | 3.4 |
| Khanya Supplies | Khanya Suplies | 95 | 2.1 |
| MJ Logistics | M.J. Logistics | 93 | 1.7 |
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 is insufficient
Duplicate vendors are rarely created with identical spelling. Punctuation, abbreviations, typos and trailing entity types defeat exact matching while leaving the underlying duplication intact.
Threshold and limit evasion
Creating a near-duplicate lets a buyer route additional spend to the same supplier without breaching a per-vendor limit or triggering a higher approval tier. The duplicate exists precisely to fragment the spend.
False positives and confirmation
Fuzzy matching produces candidates, not verdicts. Legitimate branches and genuinely different firms must be confirmed against registration numbers and banking before a duplicate is actioned.
How AuditPro Core Bridges the Gap
- Fuzzy matching: scores name similarity to surface near-duplicate vendor records that exact matching misses.
- Spend aggregation: recombines spend across suspected duplicates to reveal breached limits and thresholds.
- Exception workflow: routes candidate pairs for confirmation against registration and banking before merge.
- Audit-ready export: documents confirmed duplicates and the aggregated spend they concealed.
Key Takeaways
- Exact-match dedup misses the variants deliberately created to duplicate a vendor.
- Near-duplicates usually exist to split spend and dodge approval tiers.
- Aggregate spend across variants to expose the threshold breach.
- Confirm candidates against registration and banking before merging.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.