Master Data

Master data is the standing vendor, item, and contract information systems match invoices against. Wrong entries let drifted charges pass every check.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Master Data

Master data is the standing reference information a system uses every time it processes a transaction: the vendor record, the item or service code, the rate card tied to that vendor, and the general ledger account it posts to.

An invoice never gets checked against the actual contract sitting in a file cabinet or a shared drive. It gets checked against whatever version of that contract was typed into master data, which is why the accuracy of that entry decides whether margin drift gets caught or waved through.

1. What counts as master data?

Master data covers the standing records a system reuses across many transactions: vendor name and payment terms, approved item and service codes, the rate card or price list attached to a vendor, contract start and end dates, and the general ledger account a charge posts to. It excludes the transaction itself. An invoice, a purchase order, and a payment are transactional data, generated once and matched against the master records that were already in place.

The distinction matters because controls are built around it. Three-way matching, tolerance checks, and approval routing all read master data to decide whether a transaction looks correct.

2. How does master data differ from a contract?

A contract is a negotiated legal document. Master data is someone's typed summary of the parts of that contract a system can act on, such as a unit rate, a volume tier, or an escalation clause. The summary is often incomplete, because contracts contain conditional language that a flat data field cannot represent, like a rebate that only applies above a volume threshold.

That gap is where a rate card entry can look correct on screen while missing the condition that should have changed it. See how this plays out in practice on the page about a rate card and in volume tier.

3. How does bad master data create margin drift?

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. When master data was entered incorrectly, or never updated after a renewal, an invoice can pass every automated check while still charging the old rate, the wrong tier, or a surcharge the new contract removed. The system is matching the invoice correctly. It is matching it to the wrong reference.

This is distinct from a vendor billing error. The vendor may bill exactly what the system expects, because the system itself holds the outdated term.

A diagnostic reviews the underlying contract language, not just the system's own record of it, to find where the two have separated. Related failure patterns are cataloged under rebate gap and index escalation misapplied.

4. Who should keep master data current?

Responsibility is usually split three ways: procurement negotiates the contract terms, an AP or master data function enters them into the ERP, and IT maintains the underlying tables. No single owner sees both the signed contract and the system record end to end, which is exactly why a change made in one place can fail to reach the other.

A clear handoff at each renewal reduces this gap. Without one, an updated rate card can sit unentered for months.

Billings tied to stale master data show up across categories, including a freight and 3PL audit and a contract labor and staffing audit, wherever a rate table changes on a schedule the ERP does not track automatically.

For the wider pattern this sits inside, start with the margin drift guide.

5. Frequently Asked Questions (People Also Ask)

What is master data in accounts payable?

Master data is the reference information a system uses to process a transaction: the vendor record, item or service code, the contract or rate card tied to that vendor, and the general ledger account. An invoice is checked against this data automatically, so if the data is wrong the check still passes.

Is master data the same as transactional data?

No. Transactional data is a single event, one invoice, one purchase order, one payment. Master data is the standing record that transaction refers back to, such as a vendor's rate card. Transactional data changes constantly; master data is meant to change only when the underlying contract changes.

Why does master data quality matter for margin drift?

Automated matching compares an invoice to master data, not to the contract itself. If a vendor's rate card was entered incorrectly, or never updated after a renewal, the invoice can match the system perfectly while still charging a rate the current contract does not support.

Who owns vendor master data?

Ownership typically splits across procurement, which negotiates terms, AP or a master data function, which enters them, and IT, which maintains the underlying tables. A gap between the negotiated term and the entered term is a common point where drift starts.

How often should master data be checked against the contract?

There is no single interval that fits every vendor. A check makes the most sense at each renewal, rate change, or renegotiation, since that is the moment the ERP record and the signed contract are most likely to move apart.

Can bad master data cause a duplicate payment?

Yes. If the same vendor is entered under two different vendor codes, invoices can be paid twice without either payment triggering a duplicate check, since the system sees two separate vendors. See duplicate payment for how this pattern is found.

Does fixing master data alone stop margin drift?

It removes one source of it. Correcting an entry stops future invoices from matching a stale term, but it does not recover charges already paid against the old data, and it does not catch drift caused by scope or usage rather than a bad reference field.

Where does master data usually go stale first?

It goes stale wherever a contract term changes on its own schedule and nobody re-enters it, such as an annual rate escalation, a volume tier that resets each quarter, or a surcharge table a carrier updates independently of the customer's ERP.

1. What counts as master data?

Master data covers the standing records a system reuses across many transactions: vendor name and payment terms, approved item and service codes, the rate card or price list attached to a vendor, contract start and end dates, and the general ledger account a charge posts to. It excludes the transaction itself. An invoice, a purchase order, and a payment are transactional data, generated once and matched against the master records that were already in place. The distinction matters because controls are built around it. Three-way matching, tolerance checks, and approval routing all read master data to decide whether a transaction looks correct.

2. How does master data differ from a contract?

A contract is a negotiated legal document. Master data is someone's typed summary of the parts of that contract a system can act on, such as a unit rate, a volume tier, or an escalation clause. The summary is often incomplete, because contracts contain conditional language that a flat data field cannot represent, like a rebate that only applies above a volume threshold. That gap is where [a rate card](/glossary/rate-card) entry can look correct on screen while missing the condition that should have changed it. See how this plays out in practice on the page about a rate card and in [volume tier](/glossary/volume-tier).

3. How does bad master data create margin drift?

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. When master data was entered incorrectly, or never updated after a renewal, an invoice can pass every automated check while still charging the old rate, the wrong tier, or a surcharge the new contract removed. The system is matching the invoice correctly. It is matching it to the wrong reference. This is distinct from a vendor billing error. The vendor may bill exactly what the system expects, because the system itself holds the outdated term. A diagnostic reviews the underlying contract language, not just the system's own record of it, to find where the two have separated. Related failure patterns are cataloged under [rebate gap](/glossary/rebate-gap) and [index escalation misapplied](/glossary/index-escalation-misapplied).

4. Who should keep master data current?

Responsibility is usually split three ways: procurement negotiates the contract terms, an AP or master data function enters them into the ERP, and IT maintains the underlying tables. No single owner sees both the signed contract and the system record end to end, which is exactly why a change made in one place can fail to reach the other. A clear handoff at each renewal reduces this gap. Without one, an updated rate card can sit unentered for months. Billings tied to stale master data show up across categories, including [a freight and 3PL audit](/glossary/freight-and-3pl-audit) and a contract labor and staffing audit, wherever a rate table changes on a schedule the ERP does not track automatically. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide.

Questions & Answers

What is master data in accounts payable?

Master data is the reference information a system uses to process a transaction: the vendor record, item or service code, the contract or rate card tied to that vendor, and the general ledger account. An invoice is checked against this data automatically, so if the data is wrong the check still passes.

Is master data the same as transactional data?

No. Transactional data is a single event, one invoice, one purchase order, one payment. Master data is the standing record that transaction refers back to, such as a vendor's rate card. Transactional data changes constantly; master data is meant to change only when the underlying contract changes.

Why does master data quality matter for margin drift?

Automated matching compares an invoice to master data, not to the contract itself. If a vendor's rate card was entered incorrectly, or never updated after a renewal, the invoice can match the system perfectly while still charging a rate the current contract does not support.

Who owns vendor master data?

Ownership typically splits across procurement, which negotiates terms, AP or a master data function, which enters them, and IT, which maintains the underlying tables. A gap between the negotiated term and the entered term is a common point where drift starts.

How often should master data be checked against the contract?

There is no single interval that fits every vendor. A check makes the most sense at each renewal, rate change, or renegotiation, since that is the moment the ERP record and the signed contract are most likely to move apart.

Margin Drift Resources