Ask most finance controllers how many vendors they work with, and you'll get a confident number. Ask how many vendor records exist in the system, and the number is almost always higher — sometimes by a third. The gap is duplicate masters: the same supplier entered multiple times under slightly different names, tax numbers, or banking details.
How duplicates happen
It rarely starts as an error. A vendor changes their trading name. A new hire enters a supplier without checking the existing master list first. A subsidiary onboards a vendor independently of head office. Each event is small and reasonable on its own — the accumulation is the problem.
What it actually costs
Duplicate vendor masters aren't a cosmetic issue. They create three concrete costs:
- Fragmented spend visibility. Total spend with a supplier is split across records, undermining negotiating leverage and budget tracking.
- Audit friction. Auditors flag duplicate masters as a control weakness, and reconciling them retroactively is slow, manual work.
- Payment risk. Duplicate records with outdated banking details raise the risk of a payment routed to a stale or incorrect account.
A vendor master isn't just a lookup table — it's the control layer between your finance team and money leaving the business.
Fixing it deterministically
The fix isn't a one-time manual merge. It's a rule-based deduplication pass — fuzzy-matching on name, TRN, and banking details, with every proposed merge routed through a discrepancy dashboard for human review before anything is combined. Nothing is auto-merged silently; every decision is auditable.
Done once as part of a data remediation sprint, and paired with an ingestion rule that checks new vendor entries against the existing master before they're created, the problem doesn't just get fixed — it stays fixed.
See this applied to your own data.
Book a 20-minute audit and bring a sample export — we'll show you the fix live.