How Do You Spot Duplicate Payment on a Packaging Invoice?

Executive Summary

Duplicate payment on packaging invoices survives because the controls built to catch it were designed around a single clean invoice per purchase order, and packaging spend does not arrive that way. Corrugate and film converters bill against blanket releases, split shipments across trucks, and resubmit invoices after a pricing correction without canceling the original. Each of those normal business events creates an opening that looks, to a three-way match system, exactly like a legitimate second charge.

The mechanism is not fraud. It is a matching system that checks invoice number, PO number and amount, and packaging invoices that vary any one of those three fields slip through even when the underlying shipment is identical. A price correction reissued as a new invoice number, a partial shipment billed twice under two release numbers, or an intercompany plant paying a freight-in charge that a converter already billed as delivered, all clear standard matching.

What changes it is matching on the shipment, not the invoice. Comparing packing slip number, ship date, item and quantity across invoices, rather than invoice number alone, surfaces the pairs that a name-and-amount match cannot see. That comparison also needs a stated cost basis, because packaging invoice amounts move with paperboard pricing and a reviewer who does not know the cost trend will wave through a repeat charge that simply looks like the new normal price.

1. Why does duplicate payment happen more on packaging invoices than other categories?

Packaging invoices duplicate because pricing and shipment data change constantly and independently of each other. A converter's price per thousand units moves with paperboard cost, a blanket PO releases in partial shipments, and a single truckload can appear on both a materials invoice and a freight invoice. Standard three-way matching checks invoice number, PO number and amount, three fields that packaging billing patterns naturally vary, so a second charge for the same shipment passes as a distinct, legitimate invoice.

A converter selling corrugate or flexible film rarely bills one invoice per purchase order. Blanket POs release in partial shipments over weeks, and each partial release gets its own invoice number, its own ship date, and sometimes a slightly different unit price if a paperboard cost adjustment landed between releases.

That variability is normal and contractual. It is also exactly what defeats an invoice-number-and-amount match, because the system compares three fields that are supposed to be identical for a duplicate and are instead different by design on every legitimate partial shipment.

A second driver is corrective resubmission. A converter that billed the wrong per-unit rate against a paperboard index adjustment often issues a new invoice rather than a credit memo against the old one. If AP pays both because the first was already in the payment run, the correction becomes a duplicate rather than a fix.

2. What does three-way matching actually check, and what does it miss?

Three-way matching checks the invoice against the purchase order and the receipt: same PO number, same item, same quantity, same amount within tolerance. It does not check whether the underlying shipment already appears under a different invoice number. Two invoices referencing two different partial releases of the same blanket PO, for the same truckload, both pass three-way matching individually because each one, viewed alone, ties correctly to its own PO line and receipt record.

The control was built for a single-shipment, single-invoice relationship. Each invoice is validated against its own PO line and its own goods receipt, in isolation from every other invoice sitting in the same AP queue.

That isolation is the gap. A packing slip number, a ship date, and a bill of lading number are the fields that would tie two invoices to the same physical shipment, and none of those three fields are part of a standard three-way match.

Multi-plant operations add a second version of the same gap. A shared converter contract billed to two plant codes can generate two invoices for one delivery split across two receiving docks, and each plant's AP process matches its own invoice cleanly, with no visibility into what the other plant paid.

3. Which fields actually catch a packaging duplicate?

Catching a packaging duplicate means comparing shipment-level identifiers across invoices, not just invoice-level identifiers within one match. Packing slip number, ship date, item code and quantity, checked across every invoice from a vendor in a rolling window, surface the pairs that invoice number and PO number alone cannot. A near-identical amount on a different invoice number, tied to the same packing slip, is the actual signature of a duplicate on packaging spend.

Shipment-level fields carry the real signal. Packing slip number and bill of lading number identify the physical shipment independent of how the vendor numbered the invoice, and two invoices citing the same packing slip number are the clearest duplicate signal available regardless of what their invoice numbers or dates say. Ship date and item code narrow this further, since a converter invoice and a freight invoice covering the same truckload will often share a ship date even when every other field differs.

Amount-level fields catch a different pattern. Quantity and unit price, checked together rather than as a single total, catch the case where a corrected invoice restates a different unit price for the same quantity shipped, something a total-only comparison misses because the two totals differ enough to look like separate charges. A rolling window matters here too: packaging invoices from the same vendor for the same plant, compared across a 60 to 90 day window rather than invoice by invoice, is what exposes a resubmitted correction that arrived weeks after the original.

4. How does paperboard and resin pricing complicate the review?

A reviewer without a cost basis cannot tell a legitimate price increase from a duplicate charge disguised as one, because both look like a higher invoice amount from the same vendor. Per the US Bureau of Labor Statistics Producer Price Index for converted paper and paperboard products (series WPU0915), the August 2026 index stood at 330.943, up 4.4% year over year (read 2026-09-25). A packaging invoice that reflects roughly that movement is priced consistently with the market; one.

AP reviewers checking packaging invoices for reasonableness often have no reference point beyond the prior invoice's amount, which means a genuine market increase and an inflated or duplicated charge look identical on the page.

Anchoring the review to a published cost index gives that reference point. When the vendor's per-unit rate tracks the index movement, the increase is explainable. When it exceeds the index without a corresponding contract amendment or rate letter on file, that gap deserves a line-by-line check against the rate card, not a rubber stamp.

This does not replace the shipment-level match described above. It is a second, independent flag: a price that moves faster than its market basis is worth checking even when the invoice numbers, packing slips and quantities all look clean on their own.

5. Can multi-plant AP teams catch this without centralizing the process?

Yes, but only by comparing vendor-level invoice data across plant codes, not by asking each plant to review its own queue more carefully. A shared converter or corrugate supplier billing multiple plants under one master agreement can duplicate a shipment across two plant codes in ways neither plant's AP team can see from inside its own ERP instance, because each transaction looks complete and correctly matched in isolation.

A single-plant review, however careful, only ever sees its own invoices tied correctly to its own PO and receipt. It has no way to know that a sister plant, ordering under the same master agreement, received and paid an invoice for an overlapping shipment.

The fix does not require merging AP departments. It requires a periodic export of vendor-level invoice data, packing slip numbers, ship dates, amounts, across every plant code sharing that vendor, compared against each other rather than each plant comparing only against its own PO history.

That comparison can run on a schedule outside the daily payment cycle, since the goal is catching a pattern across plants, not blocking any single plant's normal processing.

Where a packaging duplicate becomes visible, by review scope

6. What should an AP team do when a suspected duplicate surfaces?

Hold the second payment, pull both invoices and their supporting packing slips or bills of lading side by side, and confirm whether the vendor's own credit memo history shows an acknowledgment of the error. If the vendor has not issued a credit and the shipment match is confirmed, request one in writing before offsetting a future payment, since offsetting unilaterally can create its own reconciliation problem on the vendor's side of the ledger.

A held payment costs nothing. A recovered duplicate after the check has cleared costs a collections conversation the AP team would rather not have, so the sequence matters: confirm before you pay, not after.

Document the match itself, not just the conclusion. A packing slip number shared across two invoice numbers, saved alongside both invoices, is what makes the recovery conversation with the vendor short instead of contested.

Where the pattern repeats across more than one invoice pair from the same vendor, treat it as a process gap rather than a one-off error. A converter that regularly reissues corrected invoices without canceling the original will keep producing this exposure until the rate amendment process changes on their side or the receiving check changes on yours.

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)

Is a duplicate payment on a packaging invoice usually the vendor's fault or an internal AP error?

It can originate on either side: a converter reissuing a corrected invoice without canceling the original, or an AP team processing two invoices that reference the same shipment under different numbers. The fix is the same regardless of origin: match on shipment-level fields, not invoice number alone, before the second payment clears.

Does three-way matching in an ERP catch packaging invoice duplicates automatically?

Three-way matching checks an invoice against its own purchase order line and receipt record. It does not compare that invoice against other invoices for signs of an overlapping shipment, so two invoices tied to the same delivery under different invoice numbers can each pass three-way matching independently.

What is the single best field for catching a packaging duplicate?

Packing slip number or bill of lading number, because it identifies the physical shipment independent of how the invoice itself is numbered. Two invoices citing the same packing slip number are the clearest signal available, even when totals, dates and invoice numbers all differ.

How does paperboard pricing affect duplicate detection?

A rising cost index makes it harder to tell a legitimate price increase from an inflated or duplicated charge, since both raise the invoice total. Comparing the vendor's rate movement against a published index, such as BLS series WPU0915, gives a reference point for whether the increase is market-consistent.

Can a duplicate payment happen even when the PO number matches correctly on both invoices?

Yes. A blanket PO releases across multiple shipments, so two invoices can both cite the same PO number correctly while billing for the same partial release twice. Matching on PO number alone does not distinguish one release from another.

What should we ask the vendor for once a duplicate is confirmed?

A written credit memo referencing both invoice numbers and the shared packing slip or bill of lading. Offsetting the amount unilaterally against a future payment, without the vendor's documented acknowledgment, tends to create a reconciliation dispute on their side.

Does this problem get worse across multiple plants?

It can, when a shared converter contract bills more than one plant code for the same or an overlapping shipment. Each plant's AP team sees a correctly matched invoice inside its own system, and the overlap is only visible when vendor-level data is compared across plant codes.

Is this the same issue as duplicate freight billing?

It is related but distinct. Duplicate freight billing concerns carriers rebilling the same shipment, often through multiple carrier codes on a consolidated load. Packaging duplicate payment concerns the materials invoice itself, though the two can overlap when a packaging shipment and its freight charge both reference the same delivery.