Vendor Master Data Management: The Single Source of Payee Truth
Vendor master data is the central, verified record of every payee — names, categories, and complete banking details — maintained as the single source of truth that payment data is pulled from, never typed against.
Every payment your company makes has two parts: the decision (should we pay this?) and the destination (payee and account). Workflows govern the decision; the vendor master governs the destination. This guide covers what it contains, who owns it, and the lifecycle that keeps it trustworthy. Part of the Vendors cluster; the fraud context: How to Prevent Vendor Fraud.
What the vendor master file contains
| Field group | Fields | Why it matters |
|---|---|---|
| Identity | Legal name, trade name, tax registration, trade license | The payee is a real, identifiable entity |
| Classification | Supplier / contractor / utility; local vs. international | Routing rules and approval depth key off these |
| Banking | Account name, IBAN, SWIFT, account number | The payment destination — verified, then pulled, never typed |
| Status | Verified, pending verification, deactivated | Unverified payees can't receive payments; deactivated ones stop future ones |
Two models of payee data — and why one loses
The per-transaction model: whoever submits a request types the vendor's bank details from the invoice. It feels efficient and is the single most common fraud vector — because the invoice is exactly where fraudsters do their editing. The master-data model: payment data lives in one verified place and auto-fills onto every request — read-only, no typing, no diversion.
Who owns the vendor master
Finance — not the people requesting purchases, and not the people approving them. The person who adds a vendor should never be the person who approves it or pays it: segregation of duties applied to the payee itself. Entrants pass through the vendor approval gate; exits happen by deactivation, protected by vendor lock.
The vendor master lifecycle
- Add — a vendor submission enters the verification queue
- Verify — named approvers check documentation and bank details against independent contact
- Use — verified payees appear in request forms; payment data auto-fills, read-only
- Review — periodic scans for duplicates, dormant vendors, and changed details
- Deactivate — departing vendors stop future payments; history is preserved, never deleted
Frequently Asked Questions
What is vendor master data management?
Maintaining the central, verified record of every payee — identity, classification, and banking — as the single source payment data is pulled from, with controlled entry, review, and deactivation.
Who should manage the vendor master file?
Finance or a dedicated administrator — separated from both requesting and approving. One owner, one verified source, no self-service entry by requesters.
How does vendor master data stop fraud?
Payment data can't be typed from documents — it auto-fills from the verified master — so edited invoices and "we changed our bank" emails have nothing to attack.
Approvdit's vendor master holds verified banking details centrally — gated entry, auto-fill on every request, and lock-protected history. Book a live demo.