Supplier Master vs Vendor Master
Supplier master and vendor master often describe the same governed identity record, but organizations may use supplier master for broader sourcing, relationship, risk, performance, contract, and capability data while vendor master emphasizes payable setup, tax, banking, invoices, payments, and accounting integration. The safe design is one canonical supplier identity with controlled views and entity-specific details, not two disconnected masters that can disagree.
Legal and payable identity, contacts, tax and bank details, payment terms and methods, invoice requirements, holds, credits and balances, payment status, ERP mappings, reconciliation, and archive.
Canonical identity and aliases, buyer-entity activation, field ownership, effective dates, sensitive-change verification, approvals, role-based visibility, source systems, synchronization, duplicate and merge rules, audit history, and retention.
Make the definition traceable to authoritative supplier, order, invoice, and payment records.
A trustworthy supplier, invoice, order, approval, or payment concept names its object, lifecycle boundary, source, owner, evidence, authority, limitations, and consequence.
Define the object and boundary
Name the entity, supplier or customer, client and project, policy or contract, request, order, receipt, invoice, credit, payment instruction, account, currency, period, system, rule, and what is included or excluded.
Align authoritative inputs
Use consistent identities, references, versions, dates, quantities, rates, amounts, currencies, tax, statuses, delivery or acceptance evidence, approvals, adjustments, and source systems.
Record the decision or transition
Preserve the rule or authority, actor, time, exact source objects, tolerance or condition, evidence, communication, system event, and downstream supplier, payable, payment, project, client, access, or accounting action.
Keep uncertainty and exceptions visible
Show missing sources, mismatches, duplicate records, partial delivery, credits, disputed terms, changed details, rejected or returned payments, automation failure, corrections, and the recovery owner.
Questions that prevent a misleading supplier, invoice, order, or payment conclusion.
Use these prompts when onboarding suppliers, processing invoices, approving orders or invoices, tracking payments, governing master data, or choosing software.
DefinitionCan two informed people classify the state using the same terminology, source records, policy, and boundary?
SourceCan every supplier fact, purchase, receipt, invoice, credit, approval, payment instruction, event, amount, and status be traced to an authoritative record?
OwnerIs one accountable role responsible for review, correction, communication, approval, professional escalation, recovery, and closure?
UseDoes the result support a responsible action without overstating identity, authority, receipt, invoice support, payment state, liability, settlement, project cost, or accounting position?
supplier master vs vendor master, answered.
Why does this definition matter?
Without stable boundaries, teams can split one supplier into incompatible masters, confuse invoice status with payment status, or treat an approved purchase order as evidence of delivery and invoice correctness.
Can software determine the legal, control, or accounting treatment?
Software can apply selected rules, but accountable owners and qualified professionals must choose policy, evidence, authority, segregation, tolerance, tax, legal, payment, and reporting treatment.
How should a team apply this page?
Map one real supplier, order, invoice, or payment, identify authoritative records and owners, then test the normal path, a correction or reversal, and a meaningful exception.
Make the definition operational.
Connect it to authoritative records, ownership, evidence, limitations, and recovery.