# Duplicate Vendor Detection Worksheet

> Source: https://netray.co/tools/duplicate-vendor-detection-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Record suspected duplicate suppliers, score the matching signals and track the merge decision and owner.

## Category

cost-finance

## Audience

- AP manager
- ERP administrator
- Procurement analyst
- Internal auditor

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Vendor A (ID and name)

**Key:** vendor_a

**Type:** text

#### Vendor B (ID and name)

**Key:** vendor_b

**Type:** text

#### Same tax ID (1/0)

**Key:** same_tax

**Type:** number

#### Same bank account (1/0)

**Key:** same_bank

**Type:** number

#### Same address (1/0)

**Key:** same_addr

**Type:** number

#### Similar name (1/0)

**Key:** same_name

**Type:** number

#### Match score

**Key:** score

**Type:** number

**Expr:** same_tax * 40 + same_bank * 30 + same_addr * 15 + same_name * 15

**Format:** integer

**Help:** Weights: tax ID 40, bank 30, address 15, name 15. Adjust to your policy.

#### Open AP balance

**Key:** open_ap

**Type:** number

**Format:** currency

#### Decision

**Key:** decision

**Type:** select

**Options:**

- Pending
- Merge
- Keep both
- Block one

#### Reviewer

**Key:** owner

**Type:** text

**Rows:**

**Vendor a:** 10042 Northwind Metals Inc

**Vendor b:** 10877 Northwind Metals Incorporated

**Same tax:** 1

**Same bank:** 1

**Same addr:** 1

**Same name:** 1

**Open ap:** 18450

**Decision:** Merge

**Owner:** AP lead

**Vendor a:** 10311 Precision Fasteners LLC

**Vendor b:** 20654 Precision Fasteners Ltd

**Same tax:** 0

**Same bank:** 0

**Same addr:** 0

**Same name:** 1

**Open ap:** 2300

**Decision:** Keep both

**Owner:** Buyer

**Vendor a:** 10590 Apex Logistics

**Vendor b:** 10591 APEX Logistics Services

**Same tax:** 1

**Same bank:** 0

**Same addr:** 1

**Same name:** 1

**Open ap:** 0

**Decision:** Pending

**Owner:** AP lead

**Vendor a:** 11020 Delta Tooling

**Vendor b:** 31004 D. Tooling Co

**Same tax:** 0

**Same bank:** 1

**Same addr:** 0

**Same name:** 0

**Open ap:** 7200

**Decision:** Pending

**Owner:** Controller

**Totals:**

#### Open AP at risk

**Key:** open_ap

**Agg:** sum

**Format:** currency

#### Average match score

**Key:** score

**Agg:** avg

**Format:** integer

#### Pairs logged

**Key:** vendor_a

**Agg:** count

**Format:** integer

**Currency:** $

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use the worksheet

**Body:** 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

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### How do I find duplicate vendors in my ERP?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

duplicate vendor detection, duplicate vendor master cleanup, duplicate supplier check excel, vendor master data cleanup template, find duplicate vendors in ERP, vendor deduplication worksheet, duplicate vendor audit, duplicate payment prevention vendor master

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json