Duplicate payment in packaging and corrugate

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. In packaging and corrugate spend, that gap often shows up as a shipment paid for twice under two different paper trails rather than as an obvious billing error.

Corrugate contracts run on blanket purchase orders, index-linked pricing, and partial releases spread across a quarter. Each of those mechanisms creates a legitimate reason for multiple invoices to reference the same order, which is also the cover a duplicate payment needs to clear AP unnoticed.

Executive Summary

Duplicate payment in packaging and corrugate spend rarely looks like the same invoice number submitted twice. It looks like one shipment paid through two different documents: a blanket purchase order release and a separate spot invoice, or an original invoice and a "corrected" reissue that was never voided against the first. The corrugate category is built for this to happen, because converters bill against staggered release schedules, index-linked pricing that changes mid-quarter, and consignment draws that never generate a single clean receipt.

The mechanism is structural, not accidental. A blanket PO authorizes many partial shipments over months. Each release can generate its own invoice, and AP systems built to match one PO to one invoice either block legitimate partial billing or get configured to allow multiple invoices per PO number, which is also exactly what a duplicate needs to pass. Add a vendor remit-to change during a converter's M&A activity, or a price index update applied to an invoice already paid at the old rate, and the same physical shipment can clear AP twice under two different reference numbers.

What changes it is matching at the shipment level, not the PO level: reconciling each invoice against a specific bill of lading or delivery ticket and a specific release quantity, so two invoices claiming the same physical roll or bundle collide before payment rather than after.

1. What does duplicate payment actually mean in packaging and corrugate spend?

Duplicate payment in this category means a single physical shipment of corrugate, board, or packaging materials generates two payments through two different documents: an original invoice and a reissued or "corrected" version that was never voided, or a blanket PO release billed once through the release schedule and again through a separate spot invoice for the same load. The materials moved once. AP paid for them twice, usually under two different reference numbers that never sit next to each other.

The category invites this more than most. A corrugate converter typically holds a blanket purchase order covering a full year of board or box orders, released in batches as production schedules require. Each release ships separately, often on its own truck, with its own bill of lading and its own invoice.

That is normal and necessary. The problem is that nothing in a standard three-way match forces every invoice against that blanket PO to reconcile against a unique shipment. Two invoices can both cite the same PO number, the same approximate quantity, and a date within days of each other, and pass independently because each one, viewed alone, looks correct.

A duplicate here is not sloppy data entry. It is two valid-looking documents describing the same shipment, submitted through channels that were never designed to compare against each other.

2. How does a blanket purchase order create the opening for a duplicate payment?

A blanket PO authorizes a total quantity and price over a contract period, then releases against it in batches as orders are placed. AP systems built around one-PO-to-one-invoice matching either reject legitimate partial billing or get configured to accept multiple invoices per PO, and that second configuration is exactly what lets a duplicate invoice for an already-paid release pass through without a second look.

The blanket structure exists for a real reason. A manufacturer commits to volume and price for the year; the converter ships against it as demand requires, rather than negotiating a new order every time a production run needs more corrugate.

Once a PO is configured to accept multiple invoices, the control that would normally catch a duplicate, one PO matched to one invoice, is gone by design. What remains is whichever secondary check AP built to replace it: matching against release number, against a specific ship date, against a delivery ticket. If that secondary check does not exist, or exists but is not enforced consistently, the blanket PO becomes an open channel rather than a control.

The fix is not to abandon blanket POs. It is to match at the release level: every invoice tied to a specific release number and a specific shipment document, so a second invoice against an already-fulfilled release is rejected on sight rather than paid and reconciled later, if at all.

3. Why do partial shipments and split releases make duplicate payment hard to see?

A single release can ship in more than one truck load when a converter's production run does not fit one delivery, and each partial shipment can arrive with its own packing slip and its own invoice. When AP reconciles at the release level rather than the shipment level, two partial invoices that together account for one release can look like two separate, legitimate charges, and a genuine duplicate hides in exactly that same pattern.

Corrugate production runs to press capacity, not to the shape of a purchase order. A release for 40,000 units of a box style might ship as three separate loads over a week because the converter's press schedule produced it in three batches.

Each load gets its own bill of lading. Each bill of lading often becomes its own invoice line, even when all three are billed against the same release number. That is legitimate. The complication is that this is also the exact pattern a duplicate takes: a fourth invoice, citing the same release, for a quantity that overlaps with one of the three genuine loads.

Distinguishing the two requires the shipment documents themselves, not the invoice totals. An invoice audit that reconciles release quantity against the sum of bill-of-lading quantities for that release catches both cases: legitimate split billing that nets to the right total, and a duplicate that pushes the total over what was actually shipped.

4. How does index-linked pricing create a duplicate payment rather than just a pricing error?

Many corrugate and converted paperboard contracts price off a published index, adjusted quarterly or on a lag. When a converter updates its billing system for a new index period, an invoice already paid at the prior rate sometimes gets reissued at the new rate rather than credited and rebilled, producing two payments for the same shipment: one at the old price, one at the new one, both for materials that moved once.

Converted paperboard and corrugate pricing frequently references a producer price series. The US Bureau of Labor Statistics reported the Producer Price Index for pulp, paper, and allied products, converted paper and paperboard products (series WPU0915), not seasonally adjusted, at 325.968 in July 2026, up 2.8% year over year (BLS, read 2026-09-06). Contracts that key off a series like this reprice on a schedule the invoice does not always reflect cleanly.

When a converter's system rolls to a new index value mid-quarter, an invoice for a shipment billed under the old rate is sometimes reissued rather than credited. If AP posts the reissue as a new invoice instead of a correction to the original, both clear: one at the old rate, one at the new rate, for the same physical shipment.

The correct fix on the converter's side is a credit memo against the original invoice number, not a fresh invoice number for the same materials. An invoice audit checks for exactly that: a reissued invoice that lacks a matching credit memo reference to the one it replaces.

5. What role does a vendor remit-to change play in duplicate payment?

Corrugate converters consolidate frequently, and a remit-to change during that process, a new entity name, a new bank account, a new AP contact, can cause an already-paid invoice to be resubmitted under the new entity as if it were unpaid. AP systems that match duplicates by vendor ID rather than by underlying shipment miss this, because the second submission arrives from what looks like a different vendor.

Consolidation in the corrugate supply base is common enough that a manufacturer's approved vendor list turns over its remit-to details more often than the underlying relationship changes. A converter acquired by a larger packaging group often keeps the same sales contacts and the same plant, but bills under a new legal entity with a new vendor ID.

If that transition is not managed cleanly, invoices already paid to the old entity sometimes get resubmitted under the new one, either because the converter's own records did not carry payment status across the systems merge, or because a collections effort during the transition flags open-looking balances that were actually settled.

A duplicate payment check keyed only to vendor ID will treat the two entities as unrelated and miss this entirely. Catching it requires matching on invoice content, PO number, shipment reference, and amount, independent of which vendor ID the invoice arrived under.

A. What the audit checks

The check compares invoice line detail across vendor IDs that share a remit-to history, a tax ID, or a physical plant address, rather than assuming vendor ID alone distinguishes payer relationships. Where two vendor IDs trace to the same underlying entity, invoices under both are reconciled as one stream, not two, before duplicate detection runs.

B. What the AP team can do without new tooling

A standing rule to flag any new vendor ID sharing a bank account or tax ID with an existing approved vendor catches most of this at intake, before an invoice reaches payment. That single check, run at vendor master setup rather than at invoice review, closes the window a remit-to change opens.

6. Why does standard three-way matching miss duplicate payment in this category?

Three-way matching checks an invoice against a purchase order and a receipt, confirming that a document trail exists and that quantities and price agree with what was ordered and received. It does not test whether a second invoice, correctly matched to the same PO and receipt, describes a shipment that a first invoice already billed. Two invoices can each individually satisfy a three-way match while jointly billing one shipment twice.

The control is built to answer one question per invoice: does this invoice agree with what was ordered and what arrived. It answers that question correctly for a duplicate, because a duplicate invoice, viewed alone, usually does agree with the PO and the receipt. The receipt itself may even get recorded twice if a warehouse team logs a shipment against a release number without checking whether that release was already received.

What the control does not do is compare one invoice against every other invoice previously paid against the same PO, release, or shipment. That comparison sits outside the standard three-way match entirely, and has to be added as a separate step: a duplicate-detection pass across the full payment history for a vendor and PO combination, not just against the current invoice's own paper trail.

What each AP control tests, and what it leaves open in a blanket-PO corrugate relationship.

| Control | What it verifies | What it does not verify | | --- | --- | --- | | Three-way match | Invoice agrees with PO and receipt | Whether a prior invoice already billed this same shipment | | PO-level matching | Total invoiced does not exceed PO value | Whether two invoices double-count one release inside that total | | Vendor ID duplicate check | Same invoice number not paid twice to same vendor ID | A resubmission under a new vendor ID after a remit-to change | | Shipment-level matching | Invoice ties to a specific bill of lading or release | Nothing left uncovered when applied consistently across releases |

7. What should a corrugate invoice audit check to catch duplicate payment before it pays out?

An effective check reconciles at the shipment level: every invoice tied to a specific bill of lading or release number, every credit memo matched to the invoice it corrects rather than posted as a new charge, and every new vendor ID screened against existing bank and tax details before it is treated as unrelated. None of this requires new software. It requires running the comparison across the full payment history rather than against each invoice in isolation.

Start with the shipment document, not the invoice. Every corrugate invoice should trace to a specific bill of lading or delivery ticket with a quantity that can be checked against what the release authorized. An invoice that cannot produce that document is a flag on its own.

Next, check every credit memo and reissue against the original invoice number it replaces. A reissue that arrives as a fresh invoice number, with no reference back to the one it corrects, is the pattern an index-price update or a system migration produces, and it is the pattern that clears as two payments if nobody links the two documents.

Finally, screen new vendor setups against the existing master file for shared bank account or tax ID details before treating them as unrelated. This one check, done once at intake, prevents the remit-to problem from ever reaching the payment queue.

• Match at shipment level: Tie every invoice to a specific bill of lading or release number, not just to the blanket PO.
• Trace credit memos to originals: Confirm every reissued invoice references the invoice number it replaces, not a fresh charge.
• Screen new vendor IDs: Check new setups against existing bank account and tax ID data before assuming they are unrelated vendors.
• Reconcile split shipments to release totals: Sum all partial-shipment invoices against a release and confirm the total matches what was authorized, not just that each invoice looks reasonable alone.

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