# Reasonable exception rates for corrugate invoices > There is no benchmark exception rate for packaging invoices. Here is how to build a mechanical reconciliation against your contract's own price clause instead. Source: https://valuexpa.com/insights/what-is-a-reasonable-exception-rate-for-packaging-and Publisher: ValueXPA (https://valuexpa.com) Updated: 2026-09-07 --- Margin drift is the gap between what a vendor contract says and what the invoice actually charges. In packaging and corrugate spend, that gap hides inside a category everyone assumes is just prices going up. Corrugate pricing does move for real reasons: pulp costs, mill capacity, freight to convert. The problem isn't that prices change. It's that most packaging contracts name a specific index or formula for how much they're allowed to change, and most AP review never checks the invoice against that formula. ## Executive Summary Packaging and corrugate invoices carry a structural excuse most other categories don't: input costs genuinely move, and a vendor can point to that fact to justify almost any increase. The mechanism is not fraud. It's a price change clause written loosely enough that any invoice above the prior price looks defensible, even when the index the contract actually cites moved less, moved later, or didn't move in the direction billed. What fixes this is not a benchmark percentage, because none exists for this category. What fixes it is tying every price change on a corrugate invoice to the specific index, lag period, and pass-through formula the contract names, and treating anything that doesn't reconcile as an exception regardless of the dollar amount. A reasonable exception rate, in that sense, is not a number you compare against. It's whatever share of invoices fails a mechanical reconciliation against the contract's own price change language in a given period. Some months that's close to zero. In a month following a mill price announcement it can be a large share of the file. The rate itself tells you nothing until you know whether each exception traces to a documented index movement or to a vendor applying whichever number was easiest to bill. ## 1. What is a reasonable exception rate for packaging and corrugate invoices? **There is no single reasonable exception rate for packaging and corrugate invoices, because no dataset exists to benchmark one against. The useful question is not a percentage but a reconciliation: does every price change on the invoice trace to the specific index, lag, and formula named in the contract's price change clause? An invoice that fails that check is an exception whether it is one dollar or ten thousand. One that passes is not, no matter how large the increase.** Treating exception rate as a target number invites the wrong behavior: AP teams start tolerating a fixed share of variance because it feels normal, rather than checking whether each variance is contractually earned. The right frame is binary per invoice, not aggregate per period. Either the price change reconciles to the contract's formula or it doesn't. Aggregating those results over a quarter tells you how much attention the category needs, not whether any single invoice is correct. This is also why a vertical or revenue-band benchmark would mislead even if one existed. A distributor buying standard case sizes and a manufacturer buying custom die-cut cartons face different cost pass-through structures. The reconciliation method holds across both; a shared target percentage would not. ## 2. What counts as an exception on a corrugate invoice? **An exception is any price change that cannot be traced, line by line, to the mechanism the contract specifies for changing price. That includes an increase applied before the index it cites actually moved, an increase larger than the formula's pass-through percentage allows, a surcharge with no clause authorizing it at all, and a price that never rolled back after the referenced index fell. Each is a distinct failure mode, not a variation on one theme.** Four patterns recur on corrugate invoices: - **Early application**: the new price appears on invoices dated before the contract's stated lag period has elapsed. - **Over-application**: the increase exceeds what the formula's pass-through percentage would produce from the cited index move. - **Unauthorized surcharge**: a freight, energy, or resin surcharge line with no clause in the agreement permitting it. - **Missing rollback**: the vendor raised price on an index increase but did not lower it when that same index later declined. Each requires checking a different piece of contract language, which is why a single "exception rate" number flattens four different problems into one. ## 3. Why does corrugate pricing move outside your control? **Corrugate is a converted paper product, and its cost base moves with pulp and paperboard input costs that no single buyer controls. The US Bureau of Labor Statistics' Producer Price Index for converted paper and paperboard products (series WPU0915) stood at 325.968 in July 2026, up 2.8% year over year, per the US Bureau of Labor Statistics, read 2026-09-07. That movement is real. Whether your vendor's invoice reflects it correctly, on the timeline your contract specifies, is a.** A real index move is the reason price change clauses exist in the first place. Vendors need a way to pass through genuine cost increases, and buyers need a way to verify the size and timing of that pass-through rather than accept whatever number appears on the invoice. The index itself is public and dated, which makes it one of the few pieces of packaging pricing you can check independently rather than take on the vendor's word. If a contract references WPU0915 or a similar published series, the [reconciliation is mechanical](/guides/indirect-spend-audit-categories): pull the index value for the invoice period, apply the contract's formula, and compare the result to what was billed. Where contracts reference a private mill price sheet instead of a public index, that verification step is harder and depends on the vendor supplying the sheet, which is itself worth negotiating into the contract. ## 4. How should a packaging rate card handle price change clauses? **A workable price change clause names four things: the specific index or price sheet used, the lag between an index move and when the new price takes effect, the pass-through percentage or formula applied to that move, and whether the mechanism runs both directions. A clause missing any of the four cannot be reconciled against an invoice later, because the reconciliation has nowhere to anchor. This is the single most common gap found when a packaging contract is read against.** The table below shows what a checkable clause specifies against what a vague one leaves open. What a checkable price change clause specifies compared to a vague one. | Element | Checkable clause | Vague clause | Reference index | Names a public series, e.g. a converted paperboard PPI series | "Market conditions" | Lag period | States days between index move and invoice effect | Not stated | Pass-through formula | States a percentage or formula tied to the index move | "As needed" | Direction | Applies to both increases and decreases | Increases only, implicitly ## 5. What does a defensible exception threshold look like? **A defensible threshold is not a percentage ceiling. It is a documented tolerance for rounding and timing noise, typically a small dollar or percentage band around what the formula produces, set so that immaterial rounding differences don't generate false exceptions while real deviations still surface. Anything outside that band is flagged and investigated, not averaged away into a period-wide rate that hides which specific invoices actually failed the reconciliation.** Set the tolerance band before you start reviewing, not after seeing the results, so the threshold isn't quietly adjusted to make an inconvenient finding disappear. Document the reason for the band itself: rounding in unit pricing, minor timing differences in when a mill announcement reaches different plants, or currency conversion where relevant. Each of those is a legitimate reason for small variance. None of them explains a variance that runs in one direction only, invoice after invoice, always in the vendor's favor. A pattern where every exception favors the same party is itself a finding, independent of the size of any single one. ## 6. How do you build the check without a category-wide dataset to benchmark against? **Build the check from your own contract file and your own invoice history rather than waiting for an industry benchmark that does not exist. Pull every packaging and corrugate contract's price change clause, extract the index, lag, and formula each one names, then run twelve to eighteen months of invoices against that formula line by line. The output is your own exception rate for your own vendor file, which is the only rate that means anything for your decisions.** This mirrors how the same reconciliation method works across other indirect categories: an accessorial charge audit checks freight surcharges against the carrier's own tariff rather than an industry average, and substitution pricing checks a part number change against the original quoted price rather than a market guess. Once the reconciliation is built once, it is a formula, not a research project. It runs the same way against next quarter's invoices, and the exception list from each run becomes the input for a renegotiation conversation, because it names specific invoices and specific clause violations rather than an impression that pricing feels high. ## 7. What should you do when exception rates spike? **A spike in exceptions after a published index move is not automatically a problem; it may mean invoices simply have not caught up to a rollback the contract requires. Separate the exceptions by direction and cause before reacting: increases with no matching index move, increases that arrived before the contract's lag period elapsed, and decreases that never happened all require different conversations with the vendor and different documentation to bring to that conversation.** Bring the vendor the specific invoices, the specific clause, and the specific index value for the period, not a summary complaint about pricing feeling high. That specificity is what turns a dispute into a credit memo rather than a negotiation that goes nowhere. Where the exceptions are numerous enough that manual review can't keep pace, that volume itself is the signal that the reconciliation needs to run as a [standing control against every invoice](/guides/sub-hub-mro-and-class-c-spend-audit), not a periodic sample, so the next index move doesn't produce the same backlog. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. ## 8. Frequently Asked Questions (People Also Ask) ### Is there an industry-standard exception rate for packaging invoices? No. There is no dataset available to the engine, or published elsewhere to our knowledge, that reports exception rates by category for packaging and corrugate spend. Build the rate from your own contract file and invoice history using a mechanical reconciliation against each contract's price change clause rather than comparing to an external number. ### What index do most corrugate contracts reference? It varies by contract; some reference a published index such as the Producer Price Index for converted paper and paperboard products, others reference a mill's private price sheet. The US Bureau of Labor Statistics reported that series (WPU0915) at 325.968 in July 2026, up 2.8% year over year, read 2026-09-07. ### Should we tolerate small pricing variances without flagging them? A small, documented tolerance band for rounding and timing noise is reasonable if set in advance. It should not be so wide that it absorbs real formula deviations, and any variance pattern running consistently in one direction deserves review regardless of its size. ### How far back should we check corrugate invoices for exceptions? Twelve to eighteen months is a practical window because it captures at least one full price change cycle and gives enough invoices to see whether variances are random or directional. Going back further adds volume without necessarily adding new patterns. ### Does a price increase that matches the index automatically pass the check? It has to match on timing and formula, not just direction. An increase that correctly reflects an index rise but arrives before the contract's stated lag period, or applies a larger pass-through percentage than the formula allows, still fails the reconciliation even though the underlying index movement is real. ### What if our packaging contract doesn't name a specific index at all? Then there is nothing to reconcile the invoice against, which is itself the finding. The fix is renegotiating the clause to name a specific public index, a lag period, and a pass-through formula before the next renewal, so future invoices can actually be checked. ### Can a vendor apply a price increase without notifying us first? That depends entirely on the notice provisions in your specific contract, which vary. This is general information, not legal advice; review your contract's notice and price change terms, and consult counsel where the answer affects a dispute. ### Does this reconciliation catch unauthorized surcharges too? Yes. A freight, energy, or resin surcharge line with no clause authorizing it fails the same check as a mistimed price increase: there is no contract provision for it to reconcile against, so it is flagged as an exception regardless of its dollar size. ### 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 and corrugate invoices carry a structural excuse most other categories don't: input costs genuinely move, and a vendor can point to that fact to justify almost any increase. The mechanism is not fraud. It's a price change clause written loosely enough that any invoice above the prior price looks defensible, even when the index the contract actually cites moved less, moved later, or didn't move in the direction billed. What fixes this is not a benchmark percentage, because none exists for this category. What fixes it is tying every price change on a corrugate invoice to the specific index, lag period, and pass-through formula the contract names, and treating anything that doesn't reconcile as an exception regardless of the dollar amount. A reasonable exception rate, in that sense, is not a number you compare against. It's whatever share of invoices fails a mechanical reconciliation against the contract's own price change language in a given period. Some months that's close to zero. In a month following a mill price announcement it can be a large share of the file. The rate itself tells you nothing until you know whether each exception traces to a documented index movement or to a vendor applying whichever number was easiest to bill. ## 1. What is a reasonable exception rate for packaging and corrugate invoices? There is no single reasonable exception rate for packaging and corrugate invoices, because no dataset exists to benchmark one against. The useful question is not a percentage but a reconciliation: does every price change on the invoice trace to the specific index, lag, and formula named in the contract's price change clause? An invoice that fails that check is an exception whether it is one dollar or ten thousand. One that passes is not, no matter how large the increase. Treating exception rate as a target number invites the wrong behavior: AP teams start tolerating a fixed share of variance because it feels normal, rather than checking whether each variance is contractually earned. The right frame is binary per invoice, not aggregate per period. Either the price change reconciles to the contract's formula or it doesn't. Aggregating those results over a quarter tells you how much attention the category needs, not whether any single invoice is correct. This is also why a vertical or revenue-band benchmark would mislead even if one existed. A distributor buying standard case sizes and a manufacturer buying custom die-cut cartons face different cost pass-through structures. The reconciliation method holds across both; a shared target percentage would not. ## 2. What counts as an exception on a corrugate invoice? An exception is any price change that cannot be traced, line by line, to the mechanism the contract specifies for changing price. That includes an increase applied before the index it cites actually moved, an increase larger than the formula's pass-through percentage allows, a surcharge with no clause authorizing it at all, and a price that never rolled back after the referenced index fell. Each is a distinct failure mode, not a variation on one theme. Four patterns recur on corrugate invoices: - Early application: the new price appears on invoices dated before the contract's stated lag period has elapsed. - Over-application: the increase exceeds what the formula's pass-through percentage would produce from the cited index move. - Unauthorized surcharge: a freight, energy, or resin surcharge line with no clause in the agreement permitting it. - Missing rollback: the vendor raised price on an index increase but did not lower it when that same index later declined. Each requires checking a different piece of contract language, which is why a single "exception rate" number flattens four different problems into one. ## 3. Why does corrugate pricing move outside your control? Corrugate is a converted paper product, and its cost base moves with pulp and paperboard input costs that no single buyer controls. The US Bureau of Labor Statistics' Producer Price Index for converted paper and paperboard products (series WPU0915) stood at 325.968 in July 2026, up 2.8% year over year, per the US Bureau of Labor Statistics, read 2026-09-07. That movement is real. Whether your vendor's invoice reflects it correctly, on the timeline your contract specifies, is a. A real index move is the reason price change clauses exist in the first place. Vendors need a way to pass through genuine cost increases, and buyers need a way to verify the size and timing of that pass-through rather than accept whatever number appears on the invoice. The index itself is public and dated, which makes it one of the few pieces of packaging pricing you can check independently rather than take on the vendor's word. If a contract references WPU0915 or a similar published series, the [reconciliation is mechanical](/guides/indirect-spend-audit-categories): pull the index value for the invoice period, apply the contract's formula, and compare the result to what was billed. Where contracts reference a private mill price sheet instead of a public index, that verification step is harder and depends on the vendor supplying the sheet, which is itself worth negotiating into the contract. ## 4. How should a packaging rate card handle price change clauses? A workable price change clause names four things: the specific index or price sheet used, the lag between an index move and when the new price takes effect, the pass-through percentage or formula applied to that move, and whether the mechanism runs both directions. A clause missing any of the four cannot be reconciled against an invoice later, because the reconciliation has nowhere to anchor. This is the single most common gap found when a packaging contract is read against. The table below shows what a checkable clause specifies against what a vague one leaves open. What a checkable price change clause specifies compared to a vague one. | Element | Checkable clause | Vague clause | | --- | --- | --- | | Reference index | Names a public series, e.g. a converted paperboard PPI series | "Market conditions" | | Lag period | States days between index move and invoice effect | Not stated | | Pass-through formula | States a percentage or formula tied to the index move | "As needed" | | Direction | Applies to both increases and decreases | Increases only, implicitly | ## 5. What does a defensible exception threshold look like? A defensible threshold is not a percentage ceiling. It is a documented tolerance for rounding and timing noise, typically a small dollar or percentage band around what the formula produces, set so that immaterial rounding differences don't generate false exceptions while real deviations still surface. Anything outside that band is flagged and investigated, not averaged away into a period-wide rate that hides which specific invoices actually failed the reconciliation. Set the tolerance band before you start reviewing, not after seeing the results, so the threshold isn't quietly adjusted to make an inconvenient finding disappear. Document the reason for the band itself: rounding in unit pricing, minor timing differences in when a mill announcement reaches different plants, or currency conversion where relevant. Each of those is a legitimate reason for small variance. None of them explains a variance that runs in one direction only, invoice after invoice, always in the vendor's favor. A pattern where every exception favors the same party is itself a finding, independent of the size of any single one. ## 6. How do you build the check without a category-wide dataset to benchmark against? Build the check from your own contract file and your own invoice history rather than waiting for an industry benchmark that does not exist. Pull every packaging and corrugate contract's price change clause, extract the index, lag, and formula each one names, then run twelve to eighteen months of invoices against that formula line by line. The output is your own exception rate for your own vendor file, which is the only rate that means anything for your decisions. This mirrors how the same reconciliation method works across other indirect categories: an accessorial charge audit checks freight surcharges against the carrier's own tariff rather than an industry average, and substitution pricing checks a part number change against the original quoted price rather than a market guess. Once the reconciliation is built once, it is a formula, not a research project. It runs the same way against next quarter's invoices, and the exception list from each run becomes the input for a renegotiation conversation, because it names specific invoices and specific clause violations rather than an impression that pricing feels high. ## 7. What should you do when exception rates spike? A spike in exceptions after a published index move is not automatically a problem; it may mean invoices simply have not caught up to a rollback the contract requires. Separate the exceptions by direction and cause before reacting: increases with no matching index move, increases that arrived before the contract's lag period elapsed, and decreases that never happened all require different conversations with the vendor and different documentation to bring to that conversation. Bring the vendor the specific invoices, the specific clause, and the specific index value for the period, not a summary complaint about pricing feeling high. That specificity is what turns a dispute into a credit memo rather than a negotiation that goes nowhere. Where the exceptions are numerous enough that manual review can't keep pace, that volume itself is the signal that the reconciliation needs to run as a [standing control against every invoice](/guides/sub-hub-mro-and-class-c-spend-audit), not a periodic sample, so the next index move doesn't produce the same backlog. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. ## Common questions ### Is there an industry-standard exception rate for packaging invoices? No. There is no dataset available to the engine, or published elsewhere to our knowledge, that reports exception rates by category for packaging and corrugate spend. Build the rate from your own contract file and invoice history using a mechanical reconciliation against each contract's price change clause rather than comparing to an external number. ### What index do most corrugate contracts reference? It varies by contract; some reference a published index such as the Producer Price Index for converted paper and paperboard products, others reference a mill's private price sheet. The US Bureau of Labor Statistics reported that series (WPU0915) at 325.968 in July 2026, up 2.8% year over year, read 2026-09-07. ### Should we tolerate small pricing variances without flagging them? A small, documented tolerance band for rounding and timing noise is reasonable if set in advance. It should not be so wide that it absorbs real formula deviations, and any variance pattern running consistently in one direction deserves review regardless of its size. ### How far back should we check corrugate invoices for exceptions? Twelve to eighteen months is a practical window because it captures at least one full price change cycle and gives enough invoices to see whether variances are random or directional. Going back further adds volume without necessarily adding new patterns. ### Does a price increase that matches the index automatically pass the check? It has to match on timing and formula, not just direction. An increase that correctly reflects an index rise but arrives before the contract's stated lag period, or applies a larger pass-through percentage than the formula allows, still fails the reconciliation even though the underlying index movement is real. --- 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