# How to build a checkable packaging rate card > A step-by-step method for building a structured packaging rate card AP can match invoices against, covering index resets, tooling amortization, and ownership. Source: https://valuexpa.com/insights/how-to-build-a-packaging-rate-card-your-ap-team-can-check Publisher: ValueXPA (https://valuexpa.com) Updated: 2026-09-06 --- Margin drift is the gap between what a vendor contract says and what the invoice actually charges. For packaging spend, that gap usually starts before the first invoice ever arrives: it starts with a rate card that was never built to be checked against. A corrugate or flexible packaging contract typically states a base price per unit or per weight, a resin or board index adjustment, minimum order quantities, and freight terms. If those terms live only in a signed PDF, your AP team has no reference table to match an invoice line against. This guide walks through building the reference table itself. ## Executive Summary Packaging invoices carry more variable pricing logic than almost any other indirect category: per-unit base rates, board or resin index pass-throughs, tiered volume pricing, tooling and plate amortization, and freight. Most AP teams three-way match the invoice against the PO and receipt, which confirms quantity and a unit price field but never tests whether that unit price is the one the contract actually specifies this month. The mechanism that causes drift is simple: a rate card exists in a contract document, but no structured, machine-checkable version of it exists anywhere the AP team can query it at invoice time. When a board index adjustment clause changes the price and nobody updates a reference table, the invoice looks correct against itself and wrong against the contract, and nobody is testing against the contract. What changes it is building the rate card as a structured table, independent of the ERP price file, with an explicit effective-date and index-linkage field for every line, and routing every packaging invoice through that table before payment rather than after. ## 1. What has to be on a packaging rate card before AP can use it? **A usable packaging rate card lists, for every SKU or spec: base unit price, unit of measure, minimum order quantity, any index-linked adjustment clause and its reset frequency, freight terms, tooling or plate amortization schedule, and an effective date range. Without all seven fields, AP can confirm an invoice matches itself but cannot confirm it matches the contract, which is the actual test that prevents margin drift from accumulating unnoticed.** Most packaging contracts state price per thousand units, per pallet, or per pound of board or resin, and AP systems are not built to hold that variety natively. The rate card has to normalize all of it into one row format regardless of how the contract phrased it. The minimum order quantity field matters because packaging vendors commonly apply a small-order surcharge or round up to a case pack, and that adjustment has to be visible as its own line rather than buried inside a higher unit price. The index-linkage field is the one most cards skip entirely. If a corrugate contract ties price to a board index, the card needs to name the index, the reset date, and the formula, not just the price that happened to be in effect when the card was built. - **Base unit price:** Stated per the same unit of measure the vendor invoices against, not converted or assumed. - **Minimum order quantity:** And the surcharge or rounding rule that applies below it. - **Index-linkage clause:** Name of the index, reset frequency, and the formula that converts an index move into a price change. - **Tooling and plate amortization:** A schedule showing what has already been recovered and what remains, per die or plate. - **Freight terms:** Whether freight is included, prepaid and billed, or collect, and under what weight or distance breakpoints. - **Effective date range:** So an invoice can be matched to the rate that was actually live on the ship date, not the current one. ## 2. How do you turn a signed contract into a structured table? **Read the packaging contract clause by clause and transcribe every price-bearing term into a row-based table, not a summary paragraph. Each row needs one SKU or spec, one unit price, one effective date range, and a pointer back to the contract clause number it came from, so a disputed invoice can be traced to the exact language it should match rather than to someone's memory of what the contract says.** Start with the pricing exhibit or schedule, usually an appendix rather than the main contract body. Transcribe every SKU, spec, or board grade as its own row rather than grouping similar items under one price, because vendors frequently differentiate price by flute type, print coverage, or case configuration even when the difference looks trivial. Where the contract states a formula instead of a fixed price, such as an [index-linked board price](/guides/surcharge-sunset-dating-as-a-control), encode the formula itself as a field, not the dollar figure it produced on the day you built the table. A formula field stays correct after the next index reset; a static number does not. Cross-reference each row back to the contract's clause number. When AP disputes an invoice later, the rate card should be able to point to the exact contractual language behind the number, not just assert that a number is correct. ## 3. Where does a static rate card fall out of date? **A rate card goes stale at three points: when an index resets and nobody recalculates the derived price, when a contract amendment changes a single SKU's price without a corresponding card update, and when a new SKU ships under the master agreement before anyone adds a row for it. Each of these is a normal business event, not a rare failure, so the card needs an update trigger tied to each one rather than a periodic refresh alone.** Index resets are the most predictable and the most commonly missed, because the reset date is set by an external index publisher, not by anyone on the vendor or buyer side, and nobody owns the calendar reminder. Contract amendments create drift when they are filed with legal or procurement but never routed to whoever maintains the rate card. A one-line amendment changing a single SKU's price is easy to lose track of against a 40-page master agreement. New SKUs are the quiet third failure. A packaging vendor adding a new box size or print run under an existing master agreement will typically invoice it at a negotiated price immediately, while the rate card may not gain that row for months if the update process is manual and infrequent. ### A. Index resets The Producer Price Index for converted paper and paperboard products (US Bureau of Labor Statistics, series WPU0915, read 2026-09-06) stood at 325.968 in July 2026, up 2.8% year over year. A contract that ties board price to a published index moves whenever that index moves, whether or not anyone updates the rate card to match. The fix is a reset trigger tied to the index publication date, not a manual review cycle. ### B. Amendment routing An amendment that changes one SKU's price is procurement's business, but the rate card is often maintained by AP or a finance analyst. Unless the amendment is routed to whoever owns the card on the day it is signed, the card keeps the superseded price indefinitely. ## 4. How should AP match an invoice against the rate card? **AP should match each invoice line against the rate card row with the matching SKU and the effective date range that covers the invoice's ship date, comparing unit price, minimum order quantity treatment, and any index-derived adjustment separately rather than as one blended total. A single combined variance figure hides which term actually broke; matching term by term shows exactly which clause the invoice failed.** Three-way matching checks the invoice against the purchase order and the receipt. It confirms that a quantity was ordered, received, and billed, and that the unit price on the invoice agrees with the unit price on the PO. It does not test whether that PO price is still the price the contract specifies this month. A rate-card match is a separate, fourth check: the invoice's unit price, freight treatment, and any index adjustment are tested against the contract's current terms, not against whatever price was keyed into the PO when it was cut. A PO price can be wrong for months without the PO itself ever changing. When a line fails, record which specific field broke: base price, MOQ surcharge, index formula, or freight. That granularity is what makes a dispute back to the vendor fast, because the finding points to one clause rather than an unexplained total variance. ## 5. What breaks a packaging rate card that other categories don't have to deal with? **Packaging pricing carries two structural features that freight and MRO rate cards usually do not: tooling and plate amortization schedules that change the effective price over the life of a die, and print or coating variations on an otherwise identical SKU that vendors price separately even when the difference is invisible on the invoice description line. Both require fields a generic rate-card template omits by default.** Tooling amortization means the price for the same box, printed with the same die, is supposed to decline or hold flat once the tooling cost has been recovered, per the contract's amortization schedule. If the rate card does not track how much of the die cost has already been recovered, AP has no way to test whether a vendor kept charging a tooling recovery fee past the point it was earned. Print and coating variants create a second problem: two invoice lines can describe what looks like the same box but carry different contracted prices because one has a coating pass or a second ink color. If the rate card only has one row per box style, it cannot distinguish the two, and AP either overpays the plain version's price or wrongly disputes the coated one. ## 6. Who should own the packaging rate card once it exists? **The rate card needs one named owner responsible for updating it against every index reset, amendment, and new SKU addition, distinct from whoever runs the AP match against it. Splitting build-and-maintain from check-and-flag creates the separation that keeps a stale card from silently degrading the check: the person running the match has no incentive to let a discrepancy pass, and the person maintaining the card is accountable for keeping it current.** A common failure pattern is assigning card maintenance to the same AP analyst who processes the invoices, because a busy AP analyst under invoice-volume pressure has every incentive to skip an update that would only create more line-item exceptions to chase. Procurement is a natural owner for the underlying contract terms, since they negotiated the index clauses and amendments in the first place. AP can then own the matching process against the card procurement maintains, with a clear escalation path when the two functions disagree about what the current price should be. This split does not require new headcount. It requires a written assignment of the update trigger points from the prior section to a specific role, so an index reset or amendment has a defined next action instead of depending on someone noticing. ## 7. How do you keep the rate card from drifting out of sync with the ERP price file again? **Treat the rate card as the source of truth and the ERP price file as a downstream copy, checked against the card on a fixed schedule rather than assumed correct because it was uploaded once. An annual price file upload, common practice at contract renewal, leaves eleven months where any mid-term index reset or amendment goes unreflected in what AP's own system shows as the approved price.** The rate card and the ERP price file will diverge again unless something forces them to be reconciled on a cadence shorter than the contract's own renewal cycle. An annual upload assumes prices only change at renewal, which is false for any contract carrying an index clause. A [quarterly reconciliation](/guides/the-quarterly-margin-drift-review-a-control-design-pattern), checking the ERP price file against the rate card's current effective rows, catches an index reset or amendment within one quarter instead of within a year. The reconciliation itself is a short, mechanical task once the rate card exists in structured form: it is a table comparison, not a re-read of the contract. The choice of cadence, and whether to run this as a standing control or a periodic project, is itself a decision with its own tradeoffs worth working through separately. For the wider pattern this sits inside, start with the [margin drift](/guides/contract-compliance-controls-p2p) guide. ## 8. Frequently Asked Questions (People Also Ask) ### Does a packaging rate card need to be in the ERP, or can it live in a spreadsheet? It can live outside the ERP as long as it is structured, dated, and used as the reference AP checks against before payment. The ERP price file is a downstream copy of the rate card, not the source of it. What matters is that one document is treated as authoritative and everything else is reconciled to it. ### How often should a packaging rate card be updated? Update it at three trigger points: whenever a linked index resets, whenever a contract amendment changes a price, and whenever a new SKU ships under the master agreement. Waiting for an annual review misses any of these that fall between renewal dates, and packaging contracts with index clauses reset more often than once a year. ### What is the difference between a rate card check and a three-way match? A three-way match confirms the invoice agrees with the purchase order and the goods receipt: quantity ordered, received, and billed. A rate card check tests whether the price on all three of those documents is still the price the contract actually specifies, which the three-way match never tests. ### Can tooling and plate costs really change what looks like the same unit price? Yes. A contract's amortization schedule can call for a die or plate cost to be recovered over a set volume or time period, after which the per-unit price is supposed to drop or the tooling line should stop appearing. Without tracking recovery progress on the rate card, there is no way to test whether that reduction actually happened. ### Should procurement or AP own the rate card? Procurement typically owns the underlying contract terms since they negotiated the index clauses and amendments. AP owns the invoice-matching process against the card procurement maintains. Keeping these separate means the person checking invoices has no reason to let a stale price pass unnoticed. ### What is a board index and why does it matter for packaging pricing? A board index is a published price series for paperboard or corrugate inputs, such as the US Bureau of Labor Statistics Producer Price Index series for converted paper and paperboard products. Contracts that tie price to this index change price whenever the index resets, which is why the rate card needs the formula, not just a fixed number. ### Is a rate card check something the ERP does automatically? Not structurally. A three-way match in the ERP tests the PO and receipt against the invoice, which confirms internal consistency but not whether the PO price itself is current against the contract. That gap is one your ERP cannot see on its own. ### How granular should the SKU rows be on the card? One row per distinct priced variant, including print, coating, and case configuration differences, not one row per box style. Two SKUs that look identical on an invoice description line can carry different contracted prices if one includes an extra coating pass or print color. ### What should happen when an invoice fails the rate card check? Record which specific field failed, such as base price, minimum order quantity treatment, index formula, or freight, rather than a single blended variance. That specificity lets the dispute point to one contract clause instead of an unexplained total difference. ### Is contract complexity quietly draining your operating margin? A small systematic drift between your negotiated contracts and your actual vendor billing compounds quietly across a year of invoices. Stop guessing at your exposure and run a targeted audit. **[Take the Free Screener → https://valuexpa.com/margin-drift-screener](https://valuexpa.com/margin-drift-screener)** ## Executive Summary Packaging invoices carry more variable pricing logic than almost any other indirect category: per-unit base rates, board or resin index pass-throughs, tiered volume pricing, tooling and plate amortization, and freight. Most AP teams three-way match the invoice against the PO and receipt, which confirms quantity and a unit price field but never tests whether that unit price is the one the contract actually specifies this month. The mechanism that causes drift is simple: a rate card exists in a contract document, but no structured, machine-checkable version of it exists anywhere the AP team can query it at invoice time. When a board index adjustment clause changes the price and nobody updates a reference table, the invoice looks correct against itself and wrong against the contract, and nobody is testing against the contract. What changes it is building the rate card as a structured table, independent of the ERP price file, with an explicit effective-date and index-linkage field for every line, and routing every packaging invoice through that table before payment rather than after. ## 1. What has to be on a packaging rate card before AP can use it? A usable packaging rate card lists, for every SKU or spec: base unit price, unit of measure, minimum order quantity, any index-linked adjustment clause and its reset frequency, freight terms, tooling or plate amortization schedule, and an effective date range. Without all seven fields, AP can confirm an invoice matches itself but cannot confirm it matches the contract, which is the actual test that prevents margin drift from accumulating unnoticed. Most packaging contracts state price per thousand units, per pallet, or per pound of board or resin, and AP systems are not built to hold that variety natively. The rate card has to normalize all of it into one row format regardless of how the contract phrased it. The minimum order quantity field matters because packaging vendors commonly apply a small-order surcharge or round up to a case pack, and that adjustment has to be visible as its own line rather than buried inside a higher unit price. The index-linkage field is the one most cards skip entirely. If a corrugate contract ties price to a board index, the card needs to name the index, the reset date, and the formula, not just the price that happened to be in effect when the card was built. - Base unit price: Stated per the same unit of measure the vendor invoices against, not converted or assumed. - Minimum order quantity: And the surcharge or rounding rule that applies below it. - Index-linkage clause: Name of the index, reset frequency, and the formula that converts an index move into a price change. - Tooling and plate amortization: A schedule showing what has already been recovered and what remains, per die or plate. - Freight terms: Whether freight is included, prepaid and billed, or collect, and under what weight or distance breakpoints. - Effective date range: So an invoice can be matched to the rate that was actually live on the ship date, not the current one. ## 2. How do you turn a signed contract into a structured table? Read the packaging contract clause by clause and transcribe every price-bearing term into a row-based table, not a summary paragraph. Each row needs one SKU or spec, one unit price, one effective date range, and a pointer back to the contract clause number it came from, so a disputed invoice can be traced to the exact language it should match rather than to someone's memory of what the contract says. Start with the pricing exhibit or schedule, usually an appendix rather than the main contract body. Transcribe every SKU, spec, or board grade as its own row rather than grouping similar items under one price, because vendors frequently differentiate price by flute type, print coverage, or case configuration even when the difference looks trivial. Where the contract states a formula instead of a fixed price, such as an [index-linked board price](/guides/surcharge-sunset-dating-as-a-control), encode the formula itself as a field, not the dollar figure it produced on the day you built the table. A formula field stays correct after the next index reset; a static number does not. Cross-reference each row back to the contract's clause number. When AP disputes an invoice later, the rate card should be able to point to the exact contractual language behind the number, not just assert that a number is correct. ## 3. Where does a static rate card fall out of date? A rate card goes stale at three points: when an index resets and nobody recalculates the derived price, when a contract amendment changes a single SKU's price without a corresponding card update, and when a new SKU ships under the master agreement before anyone adds a row for it. Each of these is a normal business event, not a rare failure, so the card needs an update trigger tied to each one rather than a periodic refresh alone. Index resets are the most predictable and the most commonly missed, because the reset date is set by an external index publisher, not by anyone on the vendor or buyer side, and nobody owns the calendar reminder. Contract amendments create drift when they are filed with legal or procurement but never routed to whoever maintains the rate card. A one-line amendment changing a single SKU's price is easy to lose track of against a 40-page master agreement. New SKUs are the quiet third failure. A packaging vendor adding a new box size or print run under an existing master agreement will typically invoice it at a negotiated price immediately, while the rate card may not gain that row for months if the update process is manual and infrequent. ### A. Index resets The Producer Price Index for converted paper and paperboard products (US Bureau of Labor Statistics, series WPU0915, read 2026-09-06) stood at 325.968 in July 2026, up 2.8% year over year. A contract that ties board price to a published index moves whenever that index moves, whether or not anyone updates the rate card to match. The fix is a reset trigger tied to the index publication date, not a manual review cycle. ### B. Amendment routing An amendment that changes one SKU's price is procurement's business, but the rate card is often maintained by AP or a finance analyst. Unless the amendment is routed to whoever owns the card on the day it is signed, the card keeps the superseded price indefinitely. ## 4. How should AP match an invoice against the rate card? AP should match each invoice line against the rate card row with the matching SKU and the effective date range that covers the invoice's ship date, comparing unit price, minimum order quantity treatment, and any index-derived adjustment separately rather than as one blended total. A single combined variance figure hides which term actually broke; matching term by term shows exactly which clause the invoice failed. Three-way matching checks the invoice against the purchase order and the receipt. It confirms that a quantity was ordered, received, and billed, and that the unit price on the invoice agrees with the unit price on the PO. It does not test whether that PO price is still the price the contract specifies this month. A rate-card match is a separate, fourth check: the invoice's unit price, freight treatment, and any index adjustment are tested against the contract's current terms, not against whatever price was keyed into the PO when it was cut. A PO price can be wrong for months without the PO itself ever changing. When a line fails, record which specific field broke: base price, MOQ surcharge, index formula, or freight. That granularity is what makes a dispute back to the vendor fast, because the finding points to one clause rather than an unexplained total variance. ## 5. What breaks a packaging rate card that other categories don't have to deal with? Packaging pricing carries two structural features that freight and MRO rate cards usually do not: tooling and plate amortization schedules that change the effective price over the life of a die, and print or coating variations on an otherwise identical SKU that vendors price separately even when the difference is invisible on the invoice description line. Both require fields a generic rate-card template omits by default. Tooling amortization means the price for the same box, printed with the same die, is supposed to decline or hold flat once the tooling cost has been recovered, per the contract's amortization schedule. If the rate card does not track how much of the die cost has already been recovered, AP has no way to test whether a vendor kept charging a tooling recovery fee past the point it was earned. Print and coating variants create a second problem: two invoice lines can describe what looks like the same box but carry different contracted prices because one has a coating pass or a second ink color. If the rate card only has one row per box style, it cannot distinguish the two, and AP either overpays the plain version's price or wrongly disputes the coated one. ## 6. Who should own the packaging rate card once it exists? The rate card needs one named owner responsible for updating it against every index reset, amendment, and new SKU addition, distinct from whoever runs the AP match against it. Splitting build-and-maintain from check-and-flag creates the separation that keeps a stale card from silently degrading the check: the person running the match has no incentive to let a discrepancy pass, and the person maintaining the card is accountable for keeping it current. A common failure pattern is assigning card maintenance to the same AP analyst who processes the invoices, because a busy AP analyst under invoice-volume pressure has every incentive to skip an update that would only create more line-item exceptions to chase. Procurement is a natural owner for the underlying contract terms, since they negotiated the index clauses and amendments in the first place. AP can then own the matching process against the card procurement maintains, with a clear escalation path when the two functions disagree about what the current price should be. This split does not require new headcount. It requires a written assignment of the update trigger points from the prior section to a specific role, so an index reset or amendment has a defined next action instead of depending on someone noticing. ## 7. How do you keep the rate card from drifting out of sync with the ERP price file again? Treat the rate card as the source of truth and the ERP price file as a downstream copy, checked against the card on a fixed schedule rather than assumed correct because it was uploaded once. An annual price file upload, common practice at contract renewal, leaves eleven months where any mid-term index reset or amendment goes unreflected in what AP's own system shows as the approved price. The rate card and the ERP price file will diverge again unless something forces them to be reconciled on a cadence shorter than the contract's own renewal cycle. An annual upload assumes prices only change at renewal, which is false for any contract carrying an index clause. A [quarterly reconciliation](/guides/the-quarterly-margin-drift-review-a-control-design-pattern), checking the ERP price file against the rate card's current effective rows, catches an index reset or amendment within one quarter instead of within a year. The reconciliation itself is a short, mechanical task once the rate card exists in structured form: it is a table comparison, not a re-read of the contract. The choice of cadence, and whether to run this as a standing control or a periodic project, is itself a decision with its own tradeoffs worth working through separately. For the wider pattern this sits inside, start with the [margin drift](/guides/contract-compliance-controls-p2p) guide. ## Common questions ### Does a packaging rate card need to be in the ERP, or can it live in a spreadsheet? It can live outside the ERP as long as it is structured, dated, and used as the reference AP checks against before payment. The ERP price file is a downstream copy of the rate card, not the source of it. What matters is that one document is treated as authoritative and everything else is reconciled to it. ### How often should a packaging rate card be updated? Update it at three trigger points: whenever a linked index resets, whenever a contract amendment changes a price, and whenever a new SKU ships under the master agreement. Waiting for an annual review misses any of these that fall between renewal dates, and packaging contracts with index clauses reset more often than once a year. ### What is the difference between a rate card check and a three-way match? A three-way match confirms the invoice agrees with the purchase order and the goods receipt: quantity ordered, received, and billed. A rate card check tests whether the price on all three of those documents is still the price the contract actually specifies, which the three-way match never tests. ### Can tooling and plate costs really change what looks like the same unit price? Yes. A contract's amortization schedule can call for a die or plate cost to be recovered over a set volume or time period, after which the per-unit price is supposed to drop or the tooling line should stop appearing. Without tracking recovery progress on the rate card, there is no way to test whether that reduction actually happened. ### Should procurement or AP own the rate card? Procurement typically owns the underlying contract terms since they negotiated the index clauses and amendments. AP owns the invoice-matching process against the card procurement maintains. Keeping these separate means the person checking invoices has no reason to let a stale price pass unnoticed. --- ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms, for $100M+ US industrial manufacturers and distributors. Two to four weeks. The client retains 100% of recoveries. https://valuexpa.com/contact-us