Vendor Master Data
Vendor master data is the central, permanently stored collection of all information about a company’s suppliers – such as address, contacts, payment and delivery terms, bank details and tax numbers. In the ERP system it is the binding reference for purchasing, goods receipt and accounts payable.
Vendor master data is the central collection of all permanent information about a company’s suppliers. For each supplier it holds a unique vendor number, company name and address, contacts, communication details, payment and delivery terms, bank details, and tax information such as the VAT identification number. This makes vendor master data the binding reference that every procurement-related process in the ERP system draws on – from the purchase order through goods receipt to invoice verification and accounts payable.
As part of master data, vendor master data does not describe individual transactions but the stable attributes of a business partner that stay the same across many processes. When you order from a supplier or post an incoming invoice, the system accesses this one record instead of re-entering address, terms or bank details every time. Well-maintained vendor master data is therefore a prerequisite for accurate purchase orders, smooth payments and reliable procurement reporting.
At a glance
- One central record per supplier: address, contacts, terms, bank and tax details
- Part of master data – long-lived and referential, unlike transactional data
- Maintained once, used everywhere: purchase order, goods receipt, invoice verification, accounting
- Creditor: the supplier as a business partner in accounting
- Data quality determines payment security, verification efficiency and procurement analytics
What belongs in vendor master data?
A vendor master record bundles all the details that describe a supply partner across the entire business relationship. The fields fall into a few groups: identification and address, communication and contacts, commercial terms, payment and bank details, and tax and accounting information. Depending on the industry and system, additional fields for certificates, framework agreements, supplier classification or sustainability evidence may be added.
The scope of a vendor master record depends on the needs of procurement. A simple office-supplies vendor often needs only a few fields, while a strategic raw-material supplier with a framework agreement, quality agreement and several plant addresses carries far more attributes. What matters is not the number of fields but that the details actually used are unambiguous, consistent and up to date.
Typical data fields
Commercial fields include payment terms, cash discount, delivery terms (Incoterms), minimum order values and standard lead times. Payment-relevant fields are the bank details (IBAN/BIC), alternative payees and payment methods. Important for accounting are the creditor account, the tax code, the VAT identification number and – for construction services – information on the reverse charge mechanism.
The vendor number as the key
Every vendor master record is identified by a unique, unchangeable vendor number. It is the key through which purchase orders, goods receipts and postings reference the supplier. In financial accounting it usually corresponds to the creditor account. It is often supplemented by your own customer number at the supplier and by the supplier’s vendor article numbers in the item master.
How vendor master data works in the ERP system
In the ERP system, vendor master data is the single source of truth for all supplier-related information. Once a supplier is created, downstream transactions reference this record rather than duplicating data. A purchase order takes address, payment term and delivery terms from the master record; goods receipt posts the delivered quantity against this supplier’s purchase order; the incoming invoice is checked against the purchase order and goods receipt and posted to the creditor account.
This means vendor master data connects several modules: purchasing, inventory management, invoice verification and financial accounting all access the same base data. A changed payment term only has to be maintained in one place and takes effect in all future purchase orders. Conversely, an error in the master record – such as an incorrect IBAN – propagates unchecked all the way into the payment. This central role makes data quality in vendor master data a safety-critical factor.
Vendor master data is tightly interlinked with the item master: through vendor-item relationships, purchase prices, price breaks and lead times are stored per item-supplier combination. This lets planning automatically propose the right supply partner. For data exchange with upstream systems or supplier portals, the master data is often connected via an API, for example to import catalogs, prices or electronic invoices.
Why vendor master data matters
The value of well-maintained vendor master data shows in every procurement process. Because terms, payment targets and bank details are stored centrally, purchase orders are created automatically and payments go to the right account. Invoice verification becomes faster because the tax code and creditor account are already attached to the supplier. Analyses of purchasing volume, supplier loyalty or payment behaviour become reliable because they rest on a consistent data basis.
Conversely, poor vendor master data is a frequent source of errors and risks: duplicate suppliers, outdated addresses or incorrectly entered bank details lead to wrong orders, late payments and, in the worst case, misdirected transfers. Manipulated or unnoticed changes to bank details in particular are a classic entry point for payment fraud. A controlled creation and change process is therefore not just a matter of tidiness, but of financial security.
Distinction: vendor master data, customer master data and transactional data
Vendor master data belongs to master data and sits alongside other master data objects such as customer master data and the item master. What they have in common is that they describe stable reference objects that transactions point to. This is distinct from transactional data – purchase orders, goods receipts, invoices and payments – which record individual, point-in-time events, use the vendor master data but do not change it.
Supplier, creditor and business partner
Supplier and creditor denote the same party from two perspectives: in purchasing you speak of the supplier, in accounting of the creditor, that is the creditor to whom the company owes money. Some ERP systems keep both as separate views, others combine them – like customers – in the overarching concept of the business partner. If a partner is both customer and supplier, a central business-partner master can avoid duplicates and simplify netting of open items.
Maintaining vendor master data: data quality and DACH specifics
For vendor master data to deliver its value, clear rules for creation and maintenance are needed: a well-thought-out numbering system, mandatory fields per supplier type, an approval process for new records and a four-eyes principle when changing bank details. Regular clean-ups remove duplicates and deactivate inactive suppliers instead of deleting them, so that historical documents remain reproducible.
In the DACH region, tax and legal requirements must be observed. The VAT identification number should be checked via the confirmation procedure of the German Federal Central Tax Office (BZSt) in order to handle intra-Community supplies correctly. For construction services the reverse charge mechanism applies, which must be stored on the supplier. Because vendor data feeds into tax-relevant documents, it is indirectly subject to the GoBD requirements for traceability and immutability – changes to payment- or tax-relevant fields should be logged.
In a system migration, vendor master data is one of the central migration objects. Fields are mapped between the old and new system, tax codes and payment terms are standardised, and duplicates are cleaned up before the transfer. Good data quality in the legacy system shortens the migration and lowers the risk of faulty payments after go-live.
Example
Example: wholesaler secures bank details against payment fraud
A mid-sized wholesaler sourced goods from around 400 suppliers. The master data had been maintained over the years by several employees without firm rules. Some suppliers were duplicated, others lacked a verified VAT ID, and anyone in purchasing could change bank details without any control.
After a forged email nearly led to a payment being misdirected to a foreign account, the company reorganised its vendor master data: a clear numbering scheme, mandatory fields, an approval process for new records and a four-eyes principle for every change to bank details. The VAT ID is now confirmed with the BZSt, and duplicates were merged. The result: secure payments, faster invoice verification and purchasing analyses that management can rely on.
Frequently asked questions
Matching ERP systems
Related services
Sources
Questions about Vendor Master Data in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.