# How to audit packaging and corrugate invoices step by step

> A concrete, numbered method for auditing packaging and corrugate invoices against contract terms, from vendor master pull through resin-linked pricing checks.

Source: https://valuexpa.com/insights/how-to-audit-packaging-and-corrugate-invoices-step-by-step
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. On packaging and corrugate spend, that gap hides in board grade substitutions, freight-in charges bundled into unit price, and index-linked pricing that never gets checked against the index it cites.

This guide walks through the audit as a sequence of steps, not a concept. Each step names what to pull, what to compare it against, and what a mismatch looks like on the page in front of you.

## Executive Summary

Packaging and corrugate invoices carry more embedded pricing logic than most AP teams test. Unit prices reference board grade, flute type, and sometimes a published index; freight and tooling charges get folded into line items instead of itemized; and rebate or volume-tier terms sit in a contract PDF the ERP never reads. A [three-way match](/guides/the-three-way-match-gap-what-your-erp-structurally-cannot) confirms quantity and PO reference. It does not confirm that the price itself was calculated the way the contract says it should be.

The mechanism is simple: pricing terms live in a document, invoice data lives in the ERP, and nothing routinely puts the two side by side at the line-item level. Corrugate pricing in particular can be tied to containerboard or linerboard cost movement, and a vendor's own published index adjustment can be tested independently of what the invoice claims.

What changes this is a repeatable, step-by-step comparison: pull the contract terms into a checkable format, pull the invoice population, and match unit price, grade, and any index adjustment line by line rather than trusting the total.

## 1. How do you prepare before pulling a single invoice?

**Preparation means building a checkable reference file before you look at a single invoice. Pull the current signed contract or rate agreement, extract every priced item into a spreadsheet with grade, flute type, caliper or board weight, unit price, and any index-adjustment clause, and confirm the vendor record in your ERP matches the contracting entity on the agreement. Skipping this step is why most audits stall midway: the reviewer discovers a rate discrepancy and has no clean reference to prove.**

Step 1: Locate the signed contract, rate schedule, or purchase agreement for the vendor. If the file lives in email or a shared drive rather than the ERP, copy it into a working folder before starting.

Step 2: Transcribe every priced SKU or item family into a spreadsheet: description, board grade, flute (B, C, E, or combo), caliper or basis weight, unit of measure, and contracted unit price. This becomes your reference table for every later comparison.

Step 3: Note any clause that adjusts price outside the base rate: a containerboard index pass-through, a fuel surcharge on freight-in, a tooling amortization schedule, or a minimum order charge.

Step 4: Check the vendor master record against the contracting entity's legal name and remit-to address. A mismatch here is worth resolving before the price audit, since a [duplicate or stale vendor record](/guides/vendor-master-hygiene-and-the-duplicate-vendor-problem) can mean two rate agreements are active at once.

## 2. What invoice population should you pull, and how far back?

**Pull the full invoice population for the vendor over the contract's current term, not a sample, because a fixed-scope diagnostic tests every line rather than a subset chosen in advance. Export invoice date, PO reference, item description, quantity, unit price, and total from the ERP, then sort by item description so every instance of the same board grade and flute sits together for comparison against your one reference price.**

Step 5: Export the invoice detail, not just invoice headers, so you get line-level unit price rather than a blended total. Most ERPs allow this as a standard AP export; if yours does not, pull it from the vendor's own remittance file.

Step 6: Sort the export by item description or SKU. Grouping every corrugate box style together, rather than reviewing invoices in date order, makes a price change on one style visible immediately against the others.

Step 7: Flag any line where the item description does not map cleanly to a row in your reference table from Step 2. An unmapped line usually means either a new SKU was never priced under contract, or a substitution occurred, both of which need a paper trail before you can call them a finding.

## 3. How do you check unit price against the contract line by line?

**Compare each invoiced unit price to the reference table price for that exact grade, flute, and caliper combination, not to a similar item. A three-way match confirms the invoice ties to a PO and a receipt; it does not test whether the price on that PO was calculated correctly against the rate schedule. Any variance becomes its own row in a findings log with the invoice number, the contracted price, the billed price, and the dollar difference per unit and.**

Step 8: For each invoice line, look up the matching row in your Step 2 reference table using grade, flute, and caliper together, not description text alone, since two SKUs can share a name but differ in specification.

Step 9: Record the contracted price, the billed price, the unit variance, and the extended dollar variance for every line, whether it favors the vendor or the buyer. A full findings log, not just the overcharges, is what makes the audit defensible.

Step 10: Where a variance recurs across multiple invoices for the same item, check the invoice date against any contract amendment or price increase notice on file. A justified increase that was never updated in the ERP price list looks identical to overbilling until you check the paper.

What to compare at each layer of a corrugate invoice review.

| Layer
| Reference document
| What a mismatch means

| Unit price
| Signed rate schedule
| Billed above or below contracted rate for that spec

| Board grade / flute
| Item specification sheet
| Substitution billed at original grade's price

| Freight-in
| Freight terms in the contract
| Delivery cost embedded in unit price rather than itemized

| Index adjustment
| Index-linked pricing clause
| Adjustment applied without matching the cited index period

## 4. How does index-linked corrugate pricing get tested?

**Some corrugate contracts tie unit price to a published containerboard or converted paperboard index rather than a fixed rate, and this clause has to be tested against the actual index, not against the vendor's stated adjustment. Per the US Bureau of Labor Statistics Producer Price Index for converted paper and paperboard products (series WPU0915, read September 6, 2026), the July 2026 index value was 325.968, up 2.8% year over year, giving a concrete reference point to check a.**

Step 11: Find the exact index series and base period named in the contract clause. If the clause cites a general paper index without naming the series, that ambiguity itself is a finding worth raising with the vendor.

Step 12: Pull the index value for the adjustment period the vendor cites on the invoice or price notice, and compare the percentage change the vendor applied to the percentage change the index actually shows for that period.

Step 13: Where the clause caps the pass-through, such as a maximum quarterly adjustment, confirm the applied increase respects that cap rather than passing through the full index movement.

A vendor invoice that references an index adjustment without stating the period and the source figure cannot be verified from the document alone, and that gap belongs in the findings log as a documentation exception even before any dollar variance is calculated.

## 5. What packaging-specific drift types should the audit watch for?

**Beyond unit price, packaging and corrugate audits need to watch for grade or flute substitution billed at the original price, freight-in cost bundled into a per-unit rate the contract prices separately, and minimum-order surcharges applied against a threshold that no longer matches the current contract. Each of these produces an invoice that passes a standard three-way match because quantity and PO reference are correct, while the price calculation underneath is not.**

These three drift types share a common cause: the invoice looks structurally normal against the fields a standard AP review checks, while the specification or component pricing underneath has shifted. A reviewer working from the total dollar amount alone has no way to catch any of them.

### A. Grade and flute substitution

A box specified at one caliper or flute combination gets supplied at a lighter, cheaper alternative but billed at the original contracted price. This shows up as a match between invoice price and contract price, which is why the specification field, not just the price field, needs to be checked against the packing slip or a physical sample when volume justifies it.

### B. Freight-in bundling

Corrugate is heavy and low-value relative to its volume, so freight-in cost is a meaningful share of landed cost. Where the contract prices freight separately, a vendor invoice that folds delivery into a single unit price makes it impossible to check either component against its own term, and the bundled line should be flagged for itemization.

### C. Minimum order and short-run charges

Contracts commonly set a minimum order quantity with a surcharge below it. Invoices should be checked for whether the surcharge applied matches the contracted threshold and rate, since a threshold that was renegotiated downward in one amendment can persist unchanged in the vendor's billing system for months afterward.

## 6. How do you close out findings and build the recovery request?

**Once the findings log is complete, group variances by root cause, whether a stale price file, a substituted grade, or a mis-applied index adjustment, and total the dollar impact by cause rather than by invoice. This groups the evidence into a form a vendor can review and confirm quickly, and it tells you which control to fix so the same drift type does not reappear on the next invoice cycle.**

Step 14: Group the findings log from Steps 9 and 12 by root cause rather than by invoice number. A single stale price in the vendor's billing system can generate variance on a dozen invoices, and grouping shows that immediately.

Step 15: For each root cause group, prepare a recovery request with the invoice numbers, the contract clause or price reference, and the total dollar variance. Vendors respond faster to a grouped request tied to a specific clause than to a list of disputed invoice totals.

Step 16: Update the reference table from Step 2 with any confirmed price change, amendment, or corrected index period, so the next audit cycle starts from a current baseline rather than repeating this reconciliation from scratch.

Step 17: Decide whether the recurring drift type warrants [a standing control](/guides/continuous-enforcement-vs-periodic-audit-choosing-a-cadence), such as a periodic price file refresh or an automated check against the reference table, rather than a one-time correction.

For the wider pattern this sits inside, start with the [margin drift](/guides/contract-compliance-controls-p2p) guide.

## 7. Frequently Asked Questions (People Also Ask)

### How often should packaging and corrugate invoices be audited?

This depends on invoice volume and contract complexity rather than a fixed calendar rule. A full population review at contract renewal, supplemented by spot checks after any price notice or index adjustment, catches drift closer to when it starts rather than waiting for an annual cycle.

### Does a three-way match catch corrugate pricing errors?

A three-way match confirms the invoice ties to a purchase order and a goods receipt. It does not test whether the unit price on that PO was calculated correctly against the contract's rate schedule, grade specification, or index clause, so pricing errors pass through undetected.

### What documents do I need before starting a corrugate invoice audit?

You need the current signed contract or rate agreement, the full invoice population for the contract term, the vendor master record, and any price change notices or index references cited in the contract. Without all four, several of the comparison steps cannot be completed.

### How do I test an index-linked corrugate pricing clause?

Identify the exact index series and adjustment period named in the contract, pull the actual published value for that period, and compare the percentage change the index shows to the percentage the vendor applied on the invoice or price notice, checking any stated cap.

### What is a board grade substitution and why does it matter?

It happens when a box is supplied at a lighter caliper or different flute than the specification calls for, but billed at the originally contracted price. The invoice price matches the contract, so only a specification-level check, not a price-level check, catches it.

### Should freight-in charges be itemized separately from unit price?

Where the contract prices freight separately, yes. A bundled unit price that folds delivery cost into the per-unit rate makes it impossible to verify either the packaging price or the freight cost against its own contract term.

### What's the difference between auditing packaging invoices and freight invoices?

Packaging audits center on specification-to-price matching (grade, flute, caliper) and index-linked clauses, while freight audits center on lane rates, accessorials, and carrier tariffs. The line-by-line comparison method is similar; the reference data being checked against differs.

### How do I present findings to a packaging vendor for recovery?

Group variances by root cause rather than by invoice, and cite the specific contract clause or index period each finding relies on. A grouped request with a clear reference document is easier for a vendor to verify and typically moves faster than a raw list of disputed totals.

### Can this audit be done with a sample of invoices instead of the full population?

A sample can flag that a problem exists, but it cannot size the total dollar impact or confirm which specific invoices to dispute. A fixed-scope diagnostic tests the full population precisely because sampling leaves recoverable dollars unquantified.

### What happens after the audit is complete?

The reference price table should be updated with any confirmed changes, and a decision made on whether the recurring drift type needs a standing control such as a periodic price file refresh, rather than treating each audit as a one-time correction.

### 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 more embedded pricing logic than most AP teams test. Unit prices reference board grade, flute type, and sometimes a published index; freight and tooling charges get folded into line items instead of itemized; and rebate or volume-tier terms sit in a contract PDF the ERP never reads. A [three-way match](/guides/the-three-way-match-gap-what-your-erp-structurally-cannot) confirms quantity and PO reference. It does not confirm that the price itself was calculated the way the contract says it should be. The mechanism is simple: pricing terms live in a document, invoice data lives in the ERP, and nothing routinely puts the two side by side at the line-item level. Corrugate pricing in particular can be tied to containerboard or linerboard cost movement, and a vendor's own published index adjustment can be tested independently of what the invoice claims. What changes this is a repeatable, step-by-step comparison: pull the contract terms into a checkable format, pull the invoice population, and match unit price, grade, and any index adjustment line by line rather than trusting the total.

## 1. How do you prepare before pulling a single invoice?

Preparation means building a checkable reference file before you look at a single invoice. Pull the current signed contract or rate agreement, extract every priced item into a spreadsheet with grade, flute type, caliper or board weight, unit price, and any index-adjustment clause, and confirm the vendor record in your ERP matches the contracting entity on the agreement. Skipping this step is why most audits stall midway: the reviewer discovers a rate discrepancy and has no clean reference to prove. Step 1: Locate the signed contract, rate schedule, or purchase agreement for the vendor. If the file lives in email or a shared drive rather than the ERP, copy it into a working folder before starting. Step 2: Transcribe every priced SKU or item family into a spreadsheet: description, board grade, flute (B, C, E, or combo), caliper or basis weight, unit of measure, and contracted unit price. This becomes your reference table for every later comparison. Step 3: Note any clause that adjusts price outside the base rate: a containerboard index pass-through, a fuel surcharge on freight-in, a tooling amortization schedule, or a minimum order charge. Step 4: Check the vendor master record against the contracting entity's legal name and remit-to address. A mismatch here is worth resolving before the price audit, since a [duplicate or stale vendor record](/guides/vendor-master-hygiene-and-the-duplicate-vendor-problem) can mean two rate agreements are active at once.

## 2. What invoice population should you pull, and how far back?

Pull the full invoice population for the vendor over the contract's current term, not a sample, because a fixed-scope diagnostic tests every line rather than a subset chosen in advance. Export invoice date, PO reference, item description, quantity, unit price, and total from the ERP, then sort by item description so every instance of the same board grade and flute sits together for comparison against your one reference price. Step 5: Export the invoice detail, not just invoice headers, so you get line-level unit price rather than a blended total. Most ERPs allow this as a standard AP export; if yours does not, pull it from the vendor's own remittance file. Step 6: Sort the export by item description or SKU. Grouping every corrugate box style together, rather than reviewing invoices in date order, makes a price change on one style visible immediately against the others. Step 7: Flag any line where the item description does not map cleanly to a row in your reference table from Step 2. An unmapped line usually means either a new SKU was never priced under contract, or a substitution occurred, both of which need a paper trail before you can call them a finding.

## 3. How do you check unit price against the contract line by line?

Compare each invoiced unit price to the reference table price for that exact grade, flute, and caliper combination, not to a similar item. A three-way match confirms the invoice ties to a PO and a receipt; it does not test whether the price on that PO was calculated correctly against the rate schedule. Any variance becomes its own row in a findings log with the invoice number, the contracted price, the billed price, and the dollar difference per unit and. Step 8: For each invoice line, look up the matching row in your Step 2 reference table using grade, flute, and caliper together, not description text alone, since two SKUs can share a name but differ in specification. Step 9: Record the contracted price, the billed price, the unit variance, and the extended dollar variance for every line, whether it favors the vendor or the buyer. A full findings log, not just the overcharges, is what makes the audit defensible. Step 10: Where a variance recurs across multiple invoices for the same item, check the invoice date against any contract amendment or price increase notice on file. A justified increase that was never updated in the ERP price list looks identical to overbilling until you check the paper. What to compare at each layer of a corrugate invoice review. | Layer | Reference document | What a mismatch means | | --- | --- | --- | | Unit price | Signed rate schedule | Billed above or below contracted rate for that spec | | Board grade / flute | Item specification sheet | Substitution billed at original grade's price | | Freight-in | Freight terms in the contract | Delivery cost embedded in unit price rather than itemized | | Index adjustment | Index-linked pricing clause | Adjustment applied without matching the cited index period |

## 4. How does index-linked corrugate pricing get tested?

Some corrugate contracts tie unit price to a published containerboard or converted paperboard index rather than a fixed rate, and this clause has to be tested against the actual index, not against the vendor's stated adjustment. Per the US Bureau of Labor Statistics Producer Price Index for converted paper and paperboard products (series WPU0915, read September 6, 2026), the July 2026 index value was 325.968, up 2.8% year over year, giving a concrete reference point to check a. Step 11: Find the exact index series and base period named in the contract clause. If the clause cites a general paper index without naming the series, that ambiguity itself is a finding worth raising with the vendor. Step 12: Pull the index value for the adjustment period the vendor cites on the invoice or price notice, and compare the percentage change the vendor applied to the percentage change the index actually shows for that period. Step 13: Where the clause caps the pass-through, such as a maximum quarterly adjustment, confirm the applied increase respects that cap rather than passing through the full index movement. A vendor invoice that references an index adjustment without stating the period and the source figure cannot be verified from the document alone, and that gap belongs in the findings log as a documentation exception even before any dollar variance is calculated.

## 5. What packaging-specific drift types should the audit watch for?

Beyond unit price, packaging and corrugate audits need to watch for grade or flute substitution billed at the original price, freight-in cost bundled into a per-unit rate the contract prices separately, and minimum-order surcharges applied against a threshold that no longer matches the current contract. Each of these produces an invoice that passes a standard three-way match because quantity and PO reference are correct, while the price calculation underneath is not. These three drift types share a common cause: the invoice looks structurally normal against the fields a standard AP review checks, while the specification or component pricing underneath has shifted. A reviewer working from the total dollar amount alone has no way to catch any of them. ### A. Grade and flute substitution A box specified at one caliper or flute combination gets supplied at a lighter, cheaper alternative but billed at the original contracted price. This shows up as a match between invoice price and contract price, which is why the specification field, not just the price field, needs to be checked against the packing slip or a physical sample when volume justifies it. ### B. Freight-in bundling Corrugate is heavy and low-value relative to its volume, so freight-in cost is a meaningful share of landed cost. Where the contract prices freight separately, a vendor invoice that folds delivery into a single unit price makes it impossible to check either component against its own term, and the bundled line should be flagged for itemization. ### C. Minimum order and short-run charges Contracts commonly set a minimum order quantity with a surcharge below it. Invoices should be checked for whether the surcharge applied matches the contracted threshold and rate, since a threshold that was renegotiated downward in one amendment can persist unchanged in the vendor's billing system for months afterward.

## 6. How do you close out findings and build the recovery request?

Once the findings log is complete, group variances by root cause, whether a stale price file, a substituted grade, or a mis-applied index adjustment, and total the dollar impact by cause rather than by invoice. This groups the evidence into a form a vendor can review and confirm quickly, and it tells you which control to fix so the same drift type does not reappear on the next invoice cycle. Step 14: Group the findings log from Steps 9 and 12 by root cause rather than by invoice number. A single stale price in the vendor's billing system can generate variance on a dozen invoices, and grouping shows that immediately. Step 15: For each root cause group, prepare a recovery request with the invoice numbers, the contract clause or price reference, and the total dollar variance. Vendors respond faster to a grouped request tied to a specific clause than to a list of disputed invoice totals. Step 16: Update the reference table from Step 2 with any confirmed price change, amendment, or corrected index period, so the next audit cycle starts from a current baseline rather than repeating this reconciliation from scratch. Step 17: Decide whether the recurring drift type warrants [a standing control](/guides/continuous-enforcement-vs-periodic-audit-choosing-a-cadence), such as a periodic price file refresh or an automated check against the reference table, rather than a one-time correction. For the wider pattern this sits inside, start with the [margin drift](/guides/contract-compliance-controls-p2p) guide.

## Common questions

### How often should packaging and corrugate invoices be audited?

This depends on invoice volume and contract complexity rather than a fixed calendar rule. A full population review at contract renewal, supplemented by spot checks after any price notice or index adjustment, catches drift closer to when it starts rather than waiting for an annual cycle.

### Does a three-way match catch corrugate pricing errors?

A three-way match confirms the invoice ties to a purchase order and a goods receipt. It does not test whether the unit price on that PO was calculated correctly against the contract's rate schedule, grade specification, or index clause, so pricing errors pass through undetected.

### What documents do I need before starting a corrugate invoice audit?

You need the current signed contract or rate agreement, the full invoice population for the contract term, the vendor master record, and any price change notices or index references cited in the contract. Without all four, several of the comparison steps cannot be completed.

### How do I test an index-linked corrugate pricing clause?

Identify the exact index series and adjustment period named in the contract, pull the actual published value for that period, and compare the percentage change the index shows to the percentage the vendor applied on the invoice or price notice, checking any stated cap.

### What is a board grade substitution and why does it matter?

It happens when a box is supplied at a lighter caliper or different flute than the specification calls for, but billed at the originally contracted price. The invoice price matches the contract, so only a specification-level check, not a price-level check, catches it.

---

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