Duplicate Vendor Detection Worksheet
Duplicate vendors cause duplicate payments, split spend, wrong 1099 or withholding reports and weak negotiating power. This worksheet gives AP and procurement a structured way to log suspect pairs, score the evidence and record a decision.
| Vendor A (ID and name) | Vendor B (ID and name) | Same tax ID (1/0) | Same bank account (1/0) | Same address (1/0) | Similar name (1/0) | Match score | Open AP balance | Decision | Reviewer | |
|---|---|---|---|---|---|---|---|---|---|---|
100 | ||||||||||
15 | ||||||||||
70 | ||||||||||
30 |
A score of 70 or more usually warrants a merge review; a shared bank account with different names deserves a fraud check before any payment. Never merge or delete vendors with open transactions without following your ERP's official merge or block procedure.
Want duplicates found automatically?
Optional: share a sanitized vendor export and we will show how fuzzy matching ranks candidate pairs.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Start from a vendor master export. Sort by tax ID, bank account and normalized name to find candidate pairs, then enter each pair here. Mark each match signal as 1 or 0. The score column adds weighted signals so that stronger evidence rises to the top. Fill in the open AP balance to prioritize by money at risk, then record a decision and a reviewer. Export to Excel to share with finance or audit.
Why these signals
Tax identifiers (such as EIN, PAN, GSTIN or VAT number) and bank accounts are the strongest evidence because they identify a legal entity or a payee. Address and name similarity are weaker, since branches and unrelated companies can share them. Weighting them 40, 30, 15 and 15 is a starting point you should tune. Note that two records with the same bank account but different names is a pattern that internal audit specifically looks for, so those pairs need review even if they score modestly.
- Same tax ID: strongest identity signal
- Same bank account: likely same payee or a risk flag
- Same address: weaker, depends on shared offices
- Similar name: weakest alone, normalize suffixes first
Reading and acting on results
High-score pairs with open AP balances go first, because they carry duplicate payment risk. For a confirmed duplicate, choose the surviving vendor, move open transactions where your ERP allows it, then block or archive the other. Pairs that look similar but are legitimately separate (different remit-to, different legal entity) should be marked Keep both with a note, so the next scan does not raise them again.
Common mistakes
Comparing raw names without removing punctuation and suffixes such as Inc, Ltd, GmbH or Pvt hides obvious duplicates. Merging vendors with open invoices by direct database edit breaks audit trails. Skipping bank account checks leaves the fraud pattern undetected. Cleaning once without blocking creation of new duplicates in the vendor request workflow just refills the problem within months.
Frequently Asked Questions
How do I find duplicate vendors in my ERP?
Export the vendor master and group by tax ID, bank account number, and a normalized name with suffixes and punctuation removed. Then review groups with more than one record. Most ERPs also have a built-in duplicate check at creation, which should be switched on.
Is a shared bank account always a duplicate?
No, but it needs review. It may be the same payee under two records, a related company, or a fraud attempt where someone changed bank details. Verify with the supplier through a known contact before approving any merge or payment.
Can I just delete the duplicate vendor?
Usually not. Vendors with posted transactions cannot be deleted in most ERPs. Block the record for posting or use the standard archive or merge function so history and audit trails stay intact.
How often should duplicate vendors be reviewed?
Quarterly is a common cadence, plus a check at vendor creation. Run it also before year-end reporting, tax filings and any ERP migration, since migrating duplicates just moves the problem into the new system.
If you want duplicate candidates found automatically with fuzzy matching, read-only against your ERP, we can build that and keep the data on your own servers.
Related Tools
Customer Master Cleanup Worksheet
Track customer records with data defects, score cleanup priority by revenue and issue count, and assign an owner and action.
ERP OperationsItem Master Data Quality Checklist
A 33-point checklist for auditing item or material master records before they cause wrong MRP, wrong cost or wrong shipments.
ERP OperationsMaster Data Governance RACI Template
A fill-in RACI matrix and policy outline for item, vendor, customer, BOM and routing master data ownership.
ERP OperationsUnit of Measure Conversion Reference
Searchable table of common UoM conversion factors for ERP item masters, with exact definitions where they exist.
More Costing & Finance tools
See all- SAP QM Inspection Effort and Cost Calculator
- SAP Standard Cost Estimate BOM Rollup Calculator
- Legacy ERP Retirement Cost and Payback Calculator
- JD Edwards World Month-End Close Procedure Template
- Distributor Customer Credit Application Template
- Distributor Customer Profitability Worksheet
- Distributor GMROI and Inventory Turns Calculator
- Vendor Early Pay Discount Worksheet
- SyteLine Cost Rollup Variance Calculator
Keep exploring
Free tools
- Duplicate Item Merge Savings CalculatorSize the business case for merging duplicate item master records: yearly admin saving, split inventory carrying cost and payback on the merge project.
- Duplicate Invoice Payment Leakage CalculatorEstimate annual cash lost to duplicate invoices that slip past controls, and what a higher catch rate would save.
- Fuzzy Match Duplicate Review Workload CalculatorTune your duplicate matching thresholds by seeing the review hours, wrongly merged records and cost per confirmed duplicate each setting produces.
ERP fixes and how-tos
- How to Enter an AP Voucher in SyteLineEnter a SyteLine AP voucher against received POs or as a non-PO expense, understand three-way matching and distributions, and fix common voucher problems.
- M3 API Error: Record already existM3 MI Add transaction returning Record already exist. Read the errorType/errorField response, find the real duplicate key, and fix the calling program.
- Is Your ERP Data Ready for AI? A Readiness ChecklistMost ERP data is ready enough to pilot AI today. A practical checklist of the master-data and access-control issues that actually break AI answers.
Runs with your ERP
- Serrala FS2 AccountsPayable inside SAP S/4HANA and ECCHow Serrala FS2 AccountsPayable runs inside SAP S/4HANA: invoice capture, duplicate detection, PO and goods receipt matching, pitfalls and options.
- Infor Vendor Portal for SyteLine: supplier self-service on your ERP dataHow the Infor CloudSuite Industrial vendor portal gives suppliers self-service access to SyteLine POs and receipts, what to set up, and what tends to break.
Guides
- ERP Master Data Cleanup with AI: A Practical GuideClean up ERP master data with AI: duplicate detection, standardization, and a governance model that keeps your item and customer records clean long term.
- ERP Duplicate Data Identification and ResolutionIdentify and resolve duplicate records in your ERP with fuzzy matching, survivorship rules, and merge strategies. Reduce duplicates by 90% before migration.
- Building an ERP Data Quality Framework for ManufacturingAn ERP data quality framework for manufacturers: profiling item and BOM data, six quality dimensions, automated rules, scorecards, and remediation workflows.
AI on your ERP
- AI for ERP Supplier Onboarding: Document Checks, Duplicates and Approval PacksAI to speed ERP vendor onboarding: document checks, duplicate detection, bank-detail risk flags and approval packs. Human-approved, on-prem if needed.
- AI-assisted data migration for ERP implementationsAI speeds ERP data migration by profiling legacy data, proposing field mappings, and flagging cleansing issues before cutover, with a human validating every rule.