Spotting a rate violation on a packaging invoice

Executive Summary

A packaging rate schedule violation is a unit price on an invoice that no longer matches the price the vendor agreed to in the rate card, price sheet, or supply agreement. It happens at the SKU level, not at the invoice total, which is why it survives a total-dollar review and a three-way match against the purchase order.

The mechanism is straightforward. A vendor's cost base moves, a price increase letter goes out, and the new number gets loaded into the vendor's own billing system before it gets checked against the signed rate schedule. AP pays the invoice because the PO quantity and unit count reconcile; nobody re-derives the unit price from the contract itself.

What changes this is a line-by-line comparison between the invoiced unit price and the current, dated rate card for that SKU, repeated on a schedule, not once at contract signing. The comparison catches the drift at the point it starts rather than after twelve months of it have accumulated.

1. What does a rate schedule violation look like on a packaging invoice?

A rate schedule violation on a packaging invoice is a per-unit price that has drifted from the number in the signed rate card for that SKU, while the invoice format, quantity, and purchase order all still reconcile normally. It is not a new fee or an unusual line item; it is the same corrugated case, pallet wrap, or label SKU billed at a price that no longer traces back to any dated, signed document either party can produce on request.

The invoice itself gives almost no signal. Quantity matches the shipment. Unit count matches the purchase order. The total looks like every other month's total, off by a few percent that could plausibly be volume.

The signal only appears when the unit price on the line is set next to the unit price in the rate card, SKU for SKU. A $0.42 carton billed at $0.46 will not trip a three-way match, because the match checks quantity received against quantity ordered, not price against contract.

This is why the violation persists. Nothing in a standard AP workflow asks the question a rate check asks: does this specific number still match what was signed.

2. Why does the rate card drift instead of the invoice format?

The rate card drifts because packaging vendors update pricing more often than buyers update their reference copy of it. A cost pass-through, a resin or fiber price change, or an annual escalator gets applied inside the vendor's billing system on the vendor's schedule, and the version the AP team is checking against, if anyone is checking, is often the one signed at onboarding and never refreshed since.

Packaging cost inputs move. Converted paper and paperboard product prices were up 4.4% year over year as of August 2026, per the US Bureau of Labor Statistics Producer Price Index series WPU0915 (read September 25, 2026). A vendor passing through a cost increase of that shape has a real, defensible reason to reprice.

The problem is not that the price changed. It is that the change has to be authorized under the contract's own escalation clause, at the rate and on the schedule that clause specifies, and then reflected in an updated, dated rate card both sides hold.

When the vendor's system updates faster than the buyer's reference copy, every invoice in between bills against a rate card that is technically still in force on paper but already wrong in practice.

3. How do you build the comparison that catches it?

Catching a rate schedule violation requires three things held side by side for every packaging SKU: the current dated rate card, the invoice's per-unit price, and the effective date of any approved increase. Without the effective date, a genuine, contract-compliant price change and a violation look identical on the page, because both present as a unit price higher than what the buyer remembers agreeing to.

Three pieces have to be pulled together before the comparison means anything: the reference set, the line-by-line pass, and the effective-date check described below. Skipping any one of them turns the exercise into a guess.

A. The reference set

Pull the most recent signed rate card, price sheet, or supply agreement addendum for the vendor, dated. If more than one version exists, use the one with the latest effective date that has actually passed, not the one furthest out.

B. The line-by-line pass

For each SKU on the invoice, locate the matching line on the rate card and compare unit price directly. Flag any mismatch regardless of size; a small, consistent overcharge across every invoice for a year is worth more than one large one-time error.

C. The effective-date check

Where a mismatch exists, check whether an approved increase notice with a matching effective date exists. If it does, the invoice is compliant even though the price moved. If it does not, the difference is unauthorized and recoverable.

4. Can a legitimate cost pass-through be mistaken for a violation?

Yes, and treating every price increase as a violation is its own error. A packaging vendor facing a documented input cost increase has a legitimate basis to reprice under most supply agreements, provided the increase follows the contract's notice period, applies from the stated effective date, and does not exceed the agreed cap or index. The test is documentation and timing, not the fact that the number changed.

The correct response to a price increase is to verify it, not to reject it on sight. Ask for the increase notice, the effective date, and the clause that authorizes it. If the agreement ties pricing to a named index, a documented industry-wide input cost movement is exactly the kind of evidence that supports a pass-through.

What makes it a violation is the absence of that paperwork, or an effective date that predates the notice, or an increase that exceeds what the clause allows. Those are checkable facts, not judgment calls.

A supplier relationship survives this kind of check better than it survives silence. Vendors who know their increases get verified tend to send cleaner notices; the ones who do not are the ones worth checking hardest.

5. Where does this fit against other packaging invoice checks?

A rate schedule violation is one of several distinct ways a packaging invoice can drift from what was agreed, alongside substitution pricing, where the part itself changes without the price adjusting to match, and accessorial or surcharge additions layered on top of a correct base price. Each requires its own comparison, because a control built for one will not catch the other.

The table below sets these three side by side. Each one needs a purpose-built check; a control designed for one issue will not surface the others, which is why a packaging audit has to run more than one comparison rather than treating a single check as sufficient.

How a rate violation differs from two adjacent packaging invoice issues

6. Who should own the recurring rate check?

The check belongs wherever the current, dated rate card actually lives, which in practice means procurement or the category owner, not AP alone. AP can run the SKU-level comparison mechanically once it has the reference document, but it cannot verify whether a price increase was properly authorized without the contract and the notice, both of which sit with whoever manages the vendor relationship.

Splitting the task this way avoids the usual failure mode: AP flags a mismatch, has no authority to resolve it, and the flag sits unresolved until someone closes the invoice anyway to avoid a late payment penalty.

A workable split gives AP the mechanical comparison against a rate card that procurement keeps current, with a short path back to procurement whenever a mismatch needs the contract to interpret it. Neither side needs to own both halves of the job.

This is the same pattern that shows up across every indirect spend category, not just packaging: the control only works when someone owns the reference document as tightly as someone else owns the comparison against it.

For the wider pattern this sits inside, start with the margin drift guide.

7. Frequently Asked Questions (People Also Ask)

What is a rate schedule violation on a packaging invoice?

It is a unit price charged on the invoice that no longer matches the price set in the signed rate card, price sheet, or supply agreement for that SKU, without an approved, dated increase notice to account for the difference.

Will a three-way match catch this?

No. A three-way match reconciles quantity ordered, received, and invoiced. It does not compare the invoiced unit price against the contract's rate card, so a price that has drifted from the agreement passes the match cleanly.

How often should the rate card comparison run?

On a recurring schedule tied to invoice cycles, not once at contract signing. A rate card checked only at onboarding stops reflecting reality the first time the vendor issues a legitimate or illegitimate price change.

Is every packaging price increase a violation?

No. A price increase backed by a documented notice, a valid effective date, and the contract clause that authorizes it is compliant even though the number moved. The violation is the absence of that paperwork, not the increase itself.

Can rising input costs explain a price increase?

They can support one. Converted paper and paperboard product prices were up 4.4% year over year as of August 2026, per the US Bureau of Labor Statistics PPI series WPU0915 (read September 25, 2026), which is the kind of documented movement an index-linked clause would reference.

What document do I need before I can run this check?

The most recent signed, dated rate card or price sheet for the vendor. Without a current reference document, there is nothing to compare the invoice against, and any mismatch found is unverifiable either way.

Who should resolve a flagged mismatch?

Procurement or the category owner, since resolving it requires the contract and any increase notice. AP can run the mechanical comparison but usually lacks the authority or documentation to decide whether a flagged price is authorized.

How is this different from substitution pricing?

A rate violation is the same SKU billed at the wrong price. Substitution pricing is a different part or spec billed under the original SKU's price, so the price may be technically correct for a SKU that was never actually shipped.

Does this apply only to packaging?

The mechanism, a unit price drifting from a signed reference document, applies to any category with a rate card: freight, contract labor, maintenance. Packaging is a clear example because the SKU list is usually stable and finite, which makes the comparison tractable.