Glossary
What Is a Price File? Definition for AP Teams
A price file is the vendor-maintained record of contracted prices used to check invoices for accuracy. Learn what it is and why it drifts from invoices.
Margin drift is the gap between what a vendor contract says and what the invoice actually charges. A price file is one of the documents where that gap starts, because it is the reference table AP and procurement use to decide whether an invoiced price is correct.
For $100M+ industrial manufacturers and distributors, a price file can sit outside the ERP as well as inside it: a spreadsheet from a freight carrier, a PDF rate card from a staffing vendor, a tier table buried in a service contract. When the price file is outdated or not matched against the invoice, drift goes uncaught.
What is a price file?
A price file is the record of prices a vendor has agreed to charge: a rate card, a SKU-level price list, a volume-tier table, or a surcharge schedule. It is the reference AP and procurement use to test whether a specific invoice line matches the contracted price rather than an arbitrary or outdated one. A price file can live inside the ERP, in a vendor portal, or in a standalone spreadsheet or PDF.
An ERP stores a price file as a table linked to a vendor or item master. A rate set in a side letter or contract amendment does not always reach that table, so invoice review has no reference point for it, and the rate goes untested against the actual contract.
Where does a price file come from?
A price file comes from whatever document created the pricing terms: a signed contract, a vendor's published rate card, an addendum negotiated after the original agreement, or a rebate and volume-tier schedule. Some vendors issue a new price file on a fixed schedule, such as an annual rate card update. Other vendors send pricing only in an email or an updated PDF attached to an invoice, with no formal file at all.
Because price files originate in different departments, procurement for a new contract, sales for a rebate side letter, the version AP uses to check an invoice can lag the version that actually governs it. Matching against the correct, current version is a discipline the invoice line itself does not surface.
How does a price file relate to margin drift?
A price file is the baseline invoice-to-contract matching is checked against. When a price file is missing, outdated, or not linked to the invoice review process, an invoice can carry a rate that no longer matches what the contract specifies, and nothing in AP's normal workflow will flag it. Margin drift accumulates specifically in that gap, between the price actually on file and the price actually paid.
Three-way matching checks an invoice against a purchase order and a receipt. It does not test whether the unit price on that PO reflects the current price file, so a stale price can pass every standard check the ERP performs.
Who should own and maintain the price file?
Ownership divides naturally between the person who negotiates the rate and the person who reconciles the invoice. Procurement or the contract owner updates the price file the moment terms change. AP or a controller function tests every invoice line against that current file before payment. Neither task alone closes the gap; both are required for the price file to actually prevent drift rather than just document it.
A margin drift diagnostic reviews both sides of this handoff: whether the price file on record still matches the actual contract terms, and whether AP's matching process tests invoices against it before payment.
For the wider pattern this sits inside, start with the margin drift guide. See also the Margin Drift Diagnostic and our insights.
Common questions
What is the difference between a price file and a rate card?
A rate card is one type of price file, published by a freight, staffing, or service vendor listing standard prices by lane, role, or item. A price file is the broader term for any record, rate card, tier table, or contract exhibit, that states the price a vendor is contracted to charge. An ERP uses "price file" as the generic label for whichever source document set the price.
How often should a price file be updated?
A price file should be updated any time the underlying contract term changes: at renewal, at a rate escalation date, or when a rebate or volume tier resets. There is no fixed universal interval; the trigger is the contract, not the calendar. Leaving a price file unchanged after a contract amendment is a direct cause of margin drift.
Can an ERP flag a price file mismatch automatically?
An ERP can flag a mismatch only if the current price file is loaded into the system and the invoice is matched against it at the line level. Standard three-way matching checks the invoice against a purchase order and receipt, not against a price file, so a rate error passes unless a separate rule or review step tests it.
What happens if a price file is not linked to invoice review?
Invoices continue to be paid against whatever price the vendor bills, whether or not it matches the current contract. Nothing in a standard AP workflow compares the invoiced rate to the price file unless that check is built in explicitly, so an incorrect price can repeat across invoice cycles until someone audits it directly.
Who supplies the price file for a service contract?
The vendor supplies the initial price file as part of the contract or a signed exhibit. Updates can come from the vendor directly, such as an annual rate card, or from a negotiated amendment procurement signs separately. Either way, the buyer is responsible for loading and maintaining the current version internally; the vendor has no obligation to confirm it is being used.
ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms. Two to four weeks, and you keep 100% of what is recovered.
Arrange a scoping call