In short
- Find duplicates by tax ID, bank account, address and normalized name.
- Clear balances and credits before merging or deactivating.
- Deactivate vendors with no activity for a set period.
- Make tax ID and bank details required at setup.
- Repeat the check on a schedule; duplicates come back.
What the check does
Cleaning up the vendor master means making the supplier list fit for paying and crediting the right party. The target is a single record per supplier, with the legal name, tax ID, bank details and remit address complete. It is maintenance work, not a one-time purge. Duplicates return through onboarding, acquisitions and rushed setup.
A packaging supplier can sit in your ERP under the trading name and again under the parent company name. The invoice lands on one record and a credit memo lands on the other. The credit sits unused because the next payment run looks at the record with the invoice. A cleanup finds those matches by tax ID, bank account, address and normalized name. It also finds records that are missing a tax ID or bank details, which makes matching and payment checks weaker.
The same pattern shows up with a freight carrier set up by different regions, a landlord billed under a property name and a management company name, or a stationery supplier whose name changed after a rebrand. None of these need a dramatic story. They need a list you can trust, a review step before records are merged, and a rule that new records carry the details AP needs. The cleanup is done when the list has a single payable record per supplier and no orphan credits on retired records.
Setting it up
Start by pulling the full vendor list from your ERP, including inactive records. Keep a copy for reference. Normalize the names in that copy: trim extra spaces, remove punctuation and strip common legal suffixes so that a supplier trading under a short name lines up with its registered name. Then match in a fixed order. Tax ID is the strongest key. Bank account is next. Address comes after that. Normalized name is the fallback, not the first test.
Build a review queue rather than merging as you go. For each candidate match, note why it matched and what evidence supports the merge. A shared tax ID and a shared bank account is strong. A shared address alone is weak. A name match with different bank details is a question, not a duplicate. Give the queue to a named owner in AP, with a separate reviewer for bank detail changes and for any supplier with an open balance.
Before you merge or deactivate, clear balances and credits. Apply open credits to open invoices where the contract allows it, or get a refund or write-off approved under your own policy. Move no open item to a new record without a reconciliation that shows what moved and why. A merged record with a stranded credit is worse than duplicate records, because the credit is harder to see.
At setup, make tax ID and bank details required. Your vendor setup form should not accept a new supplier without them. Add the legal name and remit address as required too. When a supplier gives new bank details, use your own verification process before you change the record. Record who approved the change and when. The point is to stop the next duplicate at the door instead of finding it in a cleanup.
Where it falls short
Name matching is the weak point. Duplicate records for the same supplier may share no address if a former site and a current site sit on different records. They may share no bank account if one record pays by check. A tax ID may be entered with different spacing or a missing digit. A normalized name helps, but it will not catch a trading name that has no words in common with the legal name.
Address matching creates false pairs. A shared office, an accountant's address or a virtual office can make unrelated suppliers look like one. A parent company can share a tax ID or a bank account with a subsidiary, and merging them can hide a real payable. Treat a shared address as a lead, not proof. Treat a shared bank account the same way when the suppliers are in different lines of business.
A merge can erase the history you need. If an old record held a credit, a prepayment or a disputed invoice, moving the open item without a clear trail leaves the next clerk guessing. Deactivation has the same risk. A supplier with no activity for a set period may still have an open balance or a credit. Check the balance before you deactivate, not after.
Tax ID formats, validation and record retention depend on the jurisdiction and on advice from your own adviser. This page is about AP practice, not about legal or tax rules. No match list is final. A person has to look at the evidence and sign off.
Checking that it works
Judge the cleanup by what changes in the payables process. Log the duplicate records cleared, the credits applied or refunded, the vendors deactivated and the new records that arrived without a tax ID or bank detail. Keep a short decision log for each merge: who reviewed it, what matched, what happened to open items and when it was approved. That log is what lets a controller answer a question months later.
Sample the setup work after the cleanup. Pull recent vendor additions and check that tax ID and bank details are present and that the legal name and remit address are complete. Walk a payment run with a supplier that had duplicate records before. Confirm that the invoice and the credit now land in the same place. If a credit is still sitting on a retired record, the cleanup is not finished.
Watch for repeat duplicates at the next scheduled pass. A pair that comes back after a merge usually points to a setup habit, such as a clerk creating a new record because the old one was inactive. Fix the habit, not just the record. Review the inactive list before you reuse or reactivate anything.
Set a repeat date and keep it. The check is a cycle, not a project. Duplicates come back through new suppliers, bank changes and regional buying. A short pass on a schedule costs less than a large cleanup after a payment error. Compare the list before and after each pass and keep the evidence with the vendor records.
Questions
How often should we clean the vendor master?
Put it on a schedule that matches your vendor volume and risk, and repeat it. A short pass at a fixed interval is better than a large cleanup after a problem. Duplicates come back through onboarding and bank changes, so the repeat date matters more than the first sweep.
Can we merge duplicate vendors if one has an open credit?
Clear the balance and the credit before you merge. Apply the credit where the contract allows, or get a refund or write-off approved under your policy. If you move an open item, reconcile it to the new record. A merge that leaves a credit behind makes the credit harder to find.
What should be required when setting up a new vendor?
Tax ID and bank details should be required, along with the legal name and remit address. Your setup form should not accept a record that lacks them. That control prevents many future duplicates and failed payment checks.
How do we find duplicates when the supplier names are different?
Match on tax ID first, then bank account, then address, then normalized name. Review near matches by hand. Do not merge on a name match alone, and do not merge on a shared address alone.
Updated Nov 15, 2026. Figures on this page are calculated by ERPSav from the definitions shown. The explanatory text is drafted with AI from those figures and checked automatically before it is published. General information only, not legal, tax or financial advice.