Who Should Approve Packaging and Corrugate Invoices?

Executive Summary

Packaging and corrugate contracts commonly tie unit price to a published index, most often a pulp and paperboard series, with a formula for how often price resets and by how much. The invoice that arrives months later rarely shows the formula, just a new number. Whoever approves that invoice needs to reconcile the new price against the index movement the contract cites, not against last quarter's invoice.

The mechanism that produces drift here is simple: procurement negotiates the index-linked clause, AP receives and pays the invoice, and neither party owns the job of checking that the new price actually matches what the index did. A buyer who only compares this invoice to the last one will approve a price that moved correctly on the index but was rounded, timed, or tiered against the reader's contract incorrectly.

The fix is not a new signature tier. It is putting the index value and the contract's reset formula in front of whoever holds final approval, whether that is a procurement lead, a plant controller, or AP itself. Below, we lay out the approval structure and the checks that belong in it.

1. Who has the authority to approve a packaging invoice?

Final approval belongs with whoever owns the packaging contract, typically a procurement lead or plant-level buyer, because they are the only person who holds the pricing formula the invoice has to be checked against. AP can process the payment, but AP should not be the last check on price accuracy unless it has been given the contract's index clause and reset schedule to work from directly.

Packaging contracts are usually negotiated at the plant or category level, not centrally, which means the person who signed the agreement is often not the person who receives the invoice. That gap is where approval authority gets murky.

The practical answer is to split the check in two. A receiving check confirms the box count, spec, and PO match, and can sit with AP or a receiving clerk. A pricing check confirms the unit rate against the contract's formula, and that has to sit with someone who has the contract terms in hand, whether that is the original buyer or a controller who has been given a copy.

Neither check alone is sufficient. An invoice can pass PO matching cleanly and still carry a price that drifted from the contract's own formula, because the PO was cut once and never updated when the index moved.

2. What should the approver check before signing off?

The approver should confirm three things: the unit price matches the contract's index-linked formula as of the invoice date, the reset happened on the contract's stated schedule and not early or late, and any minimum order quantity or tiered discount that applies at this volume was actually applied. Missing any one of these lets a technically on-contract invoice still overcharge.

Corrugate and packaging contracts that reference a paper index, such as US Bureau of Labor Statistics Producer Price Index series for converted paper and paperboard products, specify how often price resets and against which reading of the index. The July 2026 reading for that series was 325.968, up 2.8% year over year, per BLS PPI data read September 7, 2026.

An approver checking an invoice against that kind of clause needs the invoice date, the contract's stated lag between index reading and price effective date, and the index value itself. Without those three, the approver is only confirming that a number changed, not that it changed correctly.

1. Match the index date: Confirm the invoice's price reset uses the index reading the contract specifies, not a more recent or older one.
2. Confirm the reset timing: Check the reset landed on the contract's stated cadence, not triggered early by the vendor.
3. Verify tier and minimum thresholds: Confirm any volume tier or minimum order quantity discount that applies at this order size was actually credited.

3. How does a stale reference price cause packaging drift?

A stale reference price happens when the index moves but the invoice keeps citing an older reading, or when a formula meant to reset quarterly gets applied monthly. The invoice looks internally consistent because the math is done correctly against the wrong input. This is a recurring, easy-to-miss source of drift because nothing about the invoice format signals which index date was actually used.

The contract's formula is usually written once, at signing, and then nobody revisits it until a renewal. Meanwhile the vendor's billing system applies whatever reference the accounting team configured, which may not match the negotiated cadence exactly.

This kind of drift survives standard AP checks because the invoice total reconciles against the formula shown, just not against the formula in the signed contract. A three-way match against the PO catches quantity and item errors. It does not test whether the price basis cited on the invoice is the one the contract actually specifies.

4. Should plant-level buyers or corporate procurement own the sign-off?

Plant-level buyers should own line-item approval because they see the receiving dock and the day-to-day vendor relationship, while corporate procurement should own the underlying contract terms and any renegotiation. Splitting it this way keeps the person closest to the invoice doing the check, as long as corporate procurement has actually distributed the current formula to the plant.

A common failure mode is that corporate procurement negotiates a favorable index-linked clause, then never sends the plant buyer the reset schedule or the specific index series it references. The plant approves invoices against whatever the vendor states, because that is the only number available locally.

The fix is distribution, not centralization. Corporate procurement keeps ownership of the contract and any amendment. Plant buyers get a one-page summary: which index, what lag, what reset cadence, what tiers apply. That summary is what makes plant-level approval meaningful instead of a formality.

5. What happens when packaging invoices are approved without contract visibility?

When the approver cannot see the contract's pricing formula, approval becomes a check on arithmetic and totals rather than on correctness. The invoice can be internally consistent, correctly summed, and still charge a price the contract does not support. That gap tends to persist for a full renewal cycle before anyone reconciles it against the underlying terms.

This is not a fraud scenario. It is a visibility gap. AP systems are built to catch math errors, duplicate invoices, and PO mismatches. None of those checks touch whether a unit price correctly reflects an index-linked formula, because that formula usually lives in a PDF contract outside the ERP.

The cost of this gap compounds because packaging invoices recur monthly or quarterly, and a price that drifted once tends to carry forward at the same drifted level through every subsequent reset, since each new invoice is checked against the prior invoice rather than against the contract.

6. How should approval authority be documented for packaging spend?

Documentation should name a single accountable approver per contract, state which fields that approver checks beyond PO match, and specify where the current index value and reset schedule are stored so the check can actually be performed. Without that documentation, approval authority defaults informally to whoever happens to receive the invoice first.

A short approval record for each packaging contract should cover four fields: the named approver, the index series referenced, the reset cadence, and the location of the current contract terms. This does not need to be elaborate. A shared reference sheet updated at each contract renewal is enough.

Without this, approval authority tends to drift to AP by default, since AP is the last party to touch the invoice before payment. That default is workable only if AP is actually equipped with the same index and formula information the approver would need, which in most organizations it is not.

For the wider pattern this sits inside, start with the margin drift guide. See also the six categories drift hides in and accessorial charge audit: the surcharges nobody validates.

7. Frequently Asked Questions (People Also Ask)

Who is legally responsible for approving a packaging invoice for payment?

There is no fixed legal rule assigning this to a specific title. It is an internal control decision. The organization should name one accountable approver per contract in its AP policy, typically the buyer who holds the contract terms, so responsibility is documented rather than assumed.

Can AP approve packaging invoices without procurement involvement?

AP can process and match invoices against the PO, but a price check against an index-linked formula requires the contract terms procurement negotiated. Without those terms passed to AP, AP is only confirming the math, not the correctness of the price itself.

What index do corrugate and packaging contracts typically reference?

Many reference a pulp, paper, and allied products producer price index series. The US Bureau of Labor Statistics publishes one such series, WPU0915, for converted paper and paperboard products; the specific series used depends on what the contract names.

How often should packaging contract pricing reset?

This is set by the individual contract, not a standard. Some reset quarterly, some annually. The approver's job is to confirm the invoice's price change actually landed on the cadence the contract states, not to assume a standard interval.

What is the difference between a receiving check and a pricing check on a packaging invoice?

A receiving check confirms the quantity and spec delivered match the PO. A pricing check confirms the unit rate charged matches the contract's formula as of the invoice date. Both are needed; passing one does not confirm the other.

Does a three-way match catch packaging price drift?

Three-way matching checks the invoice against the purchase order and the receipt. It does not test whether the unit price reflects the index reading and reset timing the contract specifies, because that formula sits in the contract document, not the PO.

Should the same person approve packaging and other indirect spend categories like MRO?

Categories are distinct enough that this depends on organizational structure rather than a general rule. What matters is that whoever approves packaging invoices has the packaging contract's specific pricing formula in hand, whichever role that turns out to be.

What should a plant buyer do if they were never given the pricing formula?

Request the current contract summary from corporate procurement before approving further invoices on index-linked terms. Approving against the invoice's own stated math alone confirms internal consistency, not whether that math matches the signed contract.