Prepare packaging and corrugate data for an audit

Executive Summary

A packaging and corrugate audit fails or succeeds on data assembly, not analysis. Engagements lose their first two weeks to tracking down price files, board grade specs and freight terms scattered across email, ERP fields and a buyer's inbox. The mechanism is simple: corrugate pricing moves on board grade, flute type, and container specification, none of which live in one system of record, so an invoice can look correct against the PO and still be wrong against the contract.

What changes it is assembling four things before anyone opens an invoice: the current price file with effective dates, the contract or purchase agreement with every surcharge and rebate clause, a clean vendor and item master, and a full population of invoices for the audit period rather than a sample. Each of these has a specific failure mode covered below, and each failure mode is checkable before the audit starts rather than discovered during it.

The result of doing this preparation work is that the audit finds real drift instead of data entry noise. An auditor who spends the first week reconciling item numbers instead of testing terms produces a thinner finding, not a more careful one.

1. What data do you need before a packaging audit can start?

You need four data sets assembled before testing begins: the current corrugate price file with effective dates, the signed contract or purchase agreement with every rate, surcharge and rebate clause, a clean vendor and item master mapping SKUs to board grade and flute specification, and a full population of invoices for the audit period pulled directly from the ERP, not a sample or a summary report someone emails you.

Each of these lives in a different place inside most manufacturers, which is the reason preparation takes longer than the testing itself.

The price file usually sits with procurement or the buyer who negotiated it, often as a spreadsheet attachment rather than a system record. The contract sits in a shared drive or with legal. The item master lives in the ERP but is rarely reconciled against the vendor's own SKU numbering.

Invoices sit in AP, and the export a controller pulls on request is frequently a summary, not the line-level detail an audit needs.

Pull all four before scheduling any review meeting. An auditor who starts testing before the price file arrives ends up re-running the same population twice.

1. Current price file: With effective and expiration dates for every SKU, board grade and flute combination in scope.
2. Contract or purchase agreement: Including every rate schedule, minimum order surcharge, freight term and rebate clause as signed, not as summarized.
3. Vendor and item master: Mapping each internal SKU to the vendor's board grade, flute type and container specification.
4. Full invoice population: Line-level detail for the entire audit period, pulled from the ERP directly rather than a summary report.

2. How do you pull a clean invoice population for corrugate spend?

Pull invoice line detail directly from the ERP's AP module for the full audit period, filtered by vendor and by GL or spend category code for packaging and corrugate, not by keyword search on vendor name. Include the PO number, line item description, unit price, quantity, unit of measure and freight terms on each line. A summary export or a keyword search on "box" or "corrugate" both under- and over-includes lines and has to be redone.

Filtering by GL code or spend category catches vendors who supply packaging under a broader account, and catches split invoices that a name search misses entirely.

Unit of measure matters more in this category than most. Corrugate pricing quotes per thousand square feet, per case, or per skid depending on the vendor, and a population pulled without a consistent unit of measure field produces a comparison that looks like drift but is a units mismatch.

Keep the PO number on every line even where the audit is testing against contract terms rather than the PO itself. It lets you trace a disputed line back to the order that triggered it, which matters when a finding needs to go back to the vendor for resolution.

3. How should board grade and flute specifications be normalized before testing?

Build a single reference table mapping every internal SKU to its board grade (single wall, double wall), flute type (A, B, C, E), and basis weight, sourced from the vendor's own specification sheet rather than the internal item description field. Testing an invoice against a contract rate requires matching on the same specification the contract uses, and internal item descriptions frequently drop or abbreviate the flute type the contract prices against.

A contract rate is quoted against a specific board grade and flute combination. If the internal item master describes a SKU only as "32ECT box, 24x18x12" without the flute type, an auditor cannot confirm which contract line applies, and every invoice against that SKU becomes untestable until the specification is resolved.

Build the mapping once, store it as a lookup table, and reuse it across audit periods. This single table matters most in the preparation phase because every other test depends on it.

Where the vendor's specification sheet and the internal item master disagree, treat the vendor's sheet as the reference, since that is what the contract rate was negotiated against.

4. What surcharges and adjustments are specific to corrugate contracts?

Corrugate contracts commonly carry minimum order surcharges, freight adjustments tied to fuel indices, board cost pass-through clauses tied to a published pulp and paper price index, and short-run or die-cut tooling charges. Each has its own trigger condition and expiration date, and each needs its own line in the contract abstract you build before testing, because a generic surcharge test misses index-linked clauses entirely.

Board cost pass-through clauses are the one most specific to this category. Many corrugate contracts tie a price adjustment to a published index for converted paper and paperboard products, and a contract abstract needs to record which index, which date, and which formula the clause applies before an auditor can confirm whether a pass-through was calculated correctly.

Minimum order surcharges apply when a release falls below a volume threshold and are easy to miss because they appear as a flat add-on rather than a rate change.

Tooling and setup charges for die-cut or custom-printed corrugate are one-time in principle but recur in practice when a vendor bills them on repeat orders for the same die.

5. How do you handle multiple ship-to locations and consolidated invoices?

Where corrugate is shipped to multiple plants under one master agreement, build a location-to-contract mapping before testing, since freight terms, volume tiers and even board grade availability can differ by ship-to location under the same vendor number. A consolidated invoice covering several locations has to be split to the ship-to level before line-by-line contract testing, or a volume tier breach at one plant gets masked by volume at another.

Volume tier clauses aggregate across all locations to determine the rate in some agreements, but freight and minimum order surcharges often apply per shipment or per location. Testing the aggregate volume without also testing the per-location shipment terms misses half the clause.

Where a single invoice bills multiple plants, request the ship-to breakdown from the vendor or from the ERP's line-level detail before starting. An invoice that arrives as one lump sum across three plants cannot be tested against a per-location freight term without that breakdown.

Keep a running note of which locations were added or dropped from the master agreement during the audit period. A plant added mid-year may have started on a different rate schedule until it was formally added to the master contract.

6. What internal approvals and sign-offs should precede sharing this data externally?

Before any packaging invoice or contract data leaves the finance function, confirm who has authority to release vendor contract terms to an external auditor, since packaging contracts sometimes carry confidentiality clauses restricting third-party disclosure. This is general information, not legal advice: check your specific vendor agreements and involve legal or procurement before sharing contract language externally, not after.

Procurement or legal, not AP, is the group that knows whether a given corrugate contract has a confidentiality clause restricting disclosure of pricing terms to a third party conducting an audit. Getting that sign-off before the data goes out avoids a delay mid-engagement when a vendor objects.

Where a nondisclosure clause exists, an auditor can often work from a redacted or summarized rate schedule that preserves the numbers needed for testing without exposing the vendor's full commercial terms to anyone outside the engagement.

Document who approved release of each data set and when. This becomes part of the audit trail if a vendor later disputes a finding and asks how their contract terms were obtained and reviewed.

For the wider pattern this sits inside, start with the margin drift guide. See also the three-way match gap: what your erp structurally cannot see and n-way invoice matching explained.

7. Frequently Asked Questions (People Also Ask)

How long does packaging and corrugate data preparation usually take before an audit can begin?

It depends on how scattered the four data sets are across procurement, legal, the ERP and AP. Where a price file and contract are already centralized, assembly is fast. Where a buyer holds the price file in a personal spreadsheet, tracking it down adds real time before testing can start.

Can the audit start with a sample of invoices instead of the full population?

A sample can miss the specific invoices where drift concentrates, since board grade substitutions and surcharge triggers do not occur evenly across a vendor's invoices. A full population pulled from the ERP for the audit period lets every line be tested against the contract rather than relying on a sample to be representative.

What if the vendor's specification sheet has changed since the contract was signed?

Keep both versions. Test invoices dated before a specification change against the original sheet and invoices after against the updated one, and flag the transition date so a rate difference around that date is not mistaken for drift.

Who inside the company usually owns the price file for corrugate purchases?

It varies by company. In many manufacturers it sits with the procurement buyer who negotiated the contract rather than with AP or the ERP system of record, which is why it needs to be requested directly rather than assumed to exist in a shared system.

What happens if the item master and the vendor's SKU numbering do not match?

Invoices against unmatched SKUs cannot be tested against the contract rate until the mapping is resolved, since the auditor cannot confirm which contract line applies. Build a crosswalk between internal SKU and vendor SKU before testing rather than during it.

Do freight terms need to be pulled separately from the price file?

Yes. Freight terms for corrugate are often negotiated separately from the per-unit board price and can appear in a different section of the contract, a separate freight agreement, or a carrier-specific addendum. Treat freight terms as their own data set rather than assuming they are embedded in the price file.

Is a board cost pass-through clause the same as a fuel surcharge?

No. A board cost pass-through clause adjusts the base price of the board itself against a published paper and paperboard price index. A fuel surcharge adjusts the freight component against a separate fuel index. They trigger independently and need separate lines in the contract abstract.

What should be done if a vendor refuses to share their board grade specification sheet?

Request the specification through the contract owner rather than AP, since the sheet is typically referenced in the signed agreement even if not attached to it. Where it genuinely cannot be obtained, the internal item description becomes the only available reference and the limitation should be documented before testing.

Does this preparation process differ for a company with a single plant versus multiple plants?

The core four data sets are the same. A single-plant company skips the location-to-contract mapping step and the consolidated invoice splitting step, since there is only one ship-to location to test against the master agreement.