data.day
master data / audit / fraud prevention / procurement

The Duplicate Vendor Trap: A Case of Two IBANs and One Angry Auditor

You have 'Google' and 'Google Ireland' in your system. This is not a detail; it is a financial landmine waiting to explode your VAT return.

Klara Budget Klara Budget

One Vendor. Two Records. Zero Control.

Bad data costs more than bad software.

I saw a ledger last month where the company had paid €12,000 to a cleaning service. Or rather, they tried to.

  • Record A: “CleanCo BV” (Active, correct IBAN).
  • Record B: “CleanCo” (Inactive, old IBAN from 2021).

The Office Manager received the PDF. She typed “Clean” into the system. She clicked the first result (Record B). She approved the payment. The money left the building. The money bounced back three days later. The vendor called, angry, threatening to stop cleaning the toilets.

This wasted four hours of my life. We had to trace the bounce, void the payment, find the right record, and pay again. Total cost of this error: €200 in labor time for a €500 bill.

If you allow your team to create vendors like they are creating playlists on Spotify, your finance stack is rotting from the inside.

The Audit Risk: The VAT Split

Duplicates are not just annoying; they are tax leaks.

In Europe, the VAT number is the unique identifier. It is the fingerprint. If you have Vendor A with a VAT number and Vendor B without one, your tax reporting engine breaks.

I often see this with US tech giants.

  • Entry 1: Adobe Systems (US Entity, No VAT).
  • Entry 2: Adobe Ireland (EU Entity, Reverse Charge VAT).

If you book the invoice to Entry 1, you fail to apply the Reverse Charge mechanism. You are now non-compliant. When the tax auditor runs a query for “Total Spend per VAT ID” and sees zero, but sees expenses in the P&L, they start asking questions. An audit should be boring. Questions are exciting. We hate questions.

[Image of Venn diagram. Circle A: “Vendor Record 1 (Old IBAN)”. Circle B: “Vendor Record 2 (No Tax ID)”. Overlap: “The Invoice that gets paid twice”.]

The Control: The “Gatekeeper” Protocol

We fix this by closing the gate.

1. Lock the “Create” Button Only Finance Operations can create a new vendor. Not the intern. Not the Head of Marketing. If they want to buy from a new supplier, they fill out a form with the VAT ID and IBAN Proof. No form, no vendor, no payment.

2. The Unique Identifier Rule Configure your accounting software to forbid duplicate Tax IDs. If I try to create a new vendor with VAT NL823... and that number already exists in the system, the software must scream at me. It must block the action.

3. The Annual Scrub Once a year, export your vendor list. Sort by name. Look for:

  • Google vs Google Inc
  • Shell vs Royal Dutch Shell
  • Uber vs Uber BV

Merge them. Archive the duplicates. Mark them “DO NOT USE”.

Summary

Your Vendor Master Data is the foundation of your house. If the foundation is cracked, the roof (reporting) will collapse.

Meten is weten. You cannot measure spend by vendor if the vendor has five different names. Clean it up.

FAQs

Why does it matter if I have two records for one vendor?

Because eventually, you will receive Invoice #101. You will log it against Vendor A. Then you will log it again against Vendor B. And you will pay it twice.

How do duplicates happen?

Laziness. A user searches for 'FedEx', doesn't see it immediately, and clicks 'Create New'. Now you have 'FedEx Corp' and 'Federal Express'.

What is the fix?

Gatekeeping. Restrict who can create new vendors. Make it hard. Require a tax ID check before saving.