# Missed credit memo in packaging and corrugate > How missed credit memos happen in packaging and corrugate spend, the contract mechanism behind them, and how to close the gap. Written for finance and AP teams. Source: https://valuexpa.com/insights/missed-credit-memo-in-packaging-and-corrugate Publisher: ValueXPA (https://valuexpa.com) Updated: 2026-09-06 --- Margin drift is the gap between what a vendor contract says and what the invoice actually charges. In packaging and corrugate spend, one of the most persistent forms of that gap is a credit memo the vendor owes and never sends, and the buyer never chases. Corrugate pricing moves with board index adjustments, damaged-load returns, and short-ship corrections. Every one of those events is supposed to produce a credit. Many never do, and the obligation quietly expires. ## Executive Summary The mechanism is straightforward and almost never audited. A packaging supplier's contract sets a formula for adjusting price against a board index, a return allowance for damaged or rejected loads, and a short-ship credit when a delivery arrives under the ordered quantity. Each clause creates an obligation on the vendor's side of the ledger, not the buyer's. Nobody at the buyer has to do anything for the credit to be owed, and that is exactly why it goes unclaimed: there is no invoice event that forces a reconciliation, only a contract clause sitting in a PDF that AP never opens. AP's job ends when an invoice is coded and paid. It does not include checking whether a prior return, index drop, or short shipment ever generated the memo the contract promises. Without a standing log that ties each qualifying event to a credit memo number and a received date, the obligation expires against the vendor's own record-keeping or gets buried in a reconciliation nobody runs. What changes it is treating the credit memo clause as a payable in reverse: tracked, dated, and matched against a received document, the same way an invoice is matched against a purchase order. Absent that discipline, the credit is real on paper and never becomes cash. The Producer Price Index for converted paper and paperboard products moved 2.8% higher year over year in the July 2026 reading (US Bureau of Labor Statistics, PPI series WPU0915, read 2026-09-06), which is the kind of index movement a board-linked pricing clause is built to track in both directions. ## 1. How does a corrugate contract create a credit memo obligation in the first place? **A corrugate supply contract typically creates credit obligations through three separate clauses: a board index adjustment that lowers price when the referenced index falls, a damaged or rejected load allowance, and a short-ship credit for quantities delivered under the purchase order. Each clause is triggered by a different event, tracked in a different place, and owed by the vendor without the buyer having to request it, which is exactly why each one is easy to let lapse unclaimed.** The board index clause ties unit price to a published containerboard or linerboard index, often reset monthly or quarterly. When the index falls, the contract calls for the lower price to apply, sometimes retroactively to the start of the pricing period. If the vendor invoices at the old, higher price during the gap between the index move and the system update, the difference is owed back as a credit. The damaged-load allowance covers corrugate that arrives crushed, wet, or otherwise unusable on receipt. The contract usually states a rejection process and a credit timeline, separate from a return-to-vendor process some receiving teams use instead, which does not generate the same paperwork trail. The short-ship credit applies when a truckload arrives under the ordered case count. Receiving may accept the load as delivered because production needs the boxes, without flagging the shortfall as a billable difference the vendor owes back. ## 2. Where does the credit memo actually go missing? **The credit memo goes missing at the handoff between the event that creates it and the record that would surface it. Receiving logs a damaged load or a short ship in a warehouse system that AP never queries. The board index reset lives in a supplier contract file, not in the ERP's pricing table. None of these systems talks to the other, so the obligation exists in three places and is reconciled in none of them.** Consider the sequence for a damaged load. Receiving marks the pallet as rejected in the warehouse management system and moves on. The purchase order still shows the full quantity received, because the rejection was noted outside the PO line. AP pays the invoice as billed, since nothing in the invoice-to-PO match flags a rejected pallet that was never subtracted from the billed quantity. The board index case is subtler. Pricing resets happen on a schedule set in the contract, not in the vendor's billing system. If the vendor's system is not updated to the new index value on the reset date, invoices continue at the old rate until someone notices, and by contract the difference for that whole gap is owed as a credit. Short ships fail for a similar reason: the receiving document and the invoice both show a lower quantity than ordered, which looks consistent on its face. Nothing forces a comparison between what was actually charged and what should have been charged after the shortfall. ## 3. What does three-way matching catch here, and what does it miss? **Three-way matching checks that the invoice quantity and price agree with the purchase order and the receiving document. It does not test whether a rejected pallet was ever subtracted from the receiving record, and it does not test whether the price on the invoice reflects the current board index. Both checks require information the match was never built to hold, so the invoice clears even when a credit is owed.** A standard three-way match compares three numbers: what was ordered, what was received, and what was billed. If those three agree, the invoice passes, regardless of whether the received quantity itself was correct. That is the gap. A damaged pallet accepted onto the dock, then rejected on a separate quality form, never changes the receiving quantity the match checks against. A board index that dropped after the PO was cut is invisible to a match built around quantity and PO price, not a live index feed. The control is doing exactly what it was designed to do: confirm the invoice matches the order and the receipt. It was never designed to test a pricing formula or a post-receipt quality rejection, which is why closing this gap needs a separate check built specifically around the credit memo clauses in the contract. ## 4. Which contract terms should you check before assuming a credit was earned? **Three fields determine whether a credit is actually owed: the index adjustment mechanism and its reset date, the damaged-load claim window and documentation requirement, and the short-ship threshold and credit formula. All three sit in the master supply agreement or a pricing addendum, not in the invoice, so confirming an obligation means reading the contract, not the AP ledger.** None of these terms appears on an invoice. They live in the master agreement, an amendment, or a pricing schedule that was negotiated once and then filed away. Reading them is a one-time task per vendor relationship, not a recurring one, but skipping it means every subsequent question about a specific event has no reference point. A rejection logged eighty days after delivery may be worthless if the contract sets a sixty-day claim window, regardless of how clearly the pallet was damaged. Knowing the window in advance is what turns a receiving-dock event into an actionable claim instead of a dispute nobody can resolve. - **Index reset date:** The exact date the contract requires the new board index price to take effect, and whether the adjustment applies retroactively to shipments during the gap. - **Claim window:** The number of days after a damaged or rejected load within which a claim must be filed, after which the vendor's obligation may lapse by the contract's own terms. - **Documentation requirement:** What the vendor requires as proof of a rejection: a signed delivery exception, photos, or a formal return authorization number. - **Short-ship threshold:** Whether a shortfall triggers a credit automatically or only above a stated case-count or percentage threshold. - **Credit formula:** Whether the short-ship credit is the full unit price, a prorated freight adjustment, or both, since contracts vary on this point. ## 5. How do you build a log that actually catches these before they expire? **A credit memo log ties each qualifying event, a rejection, a short ship, an index reset, to an expected credit amount, a claim deadline, and a received memo number. It is reconciled on a fixed schedule against what the vendor has actually issued, the same way a bank reconciliation checks a ledger against a statement, so a gap between expected and received credits surfaces before the claim window closes.** The log needs four columns at minimum: the event date, the event type, the dollar amount expected under the contract formula, and the claim deadline derived from the contract's claim window. A fifth column records the credit memo number once issued, and a sixth flags anything still open past its deadline. Receiving needs a simple way to feed this log the moment a load is rejected or short, rather than relying on someone in AP to notice it later. A standard exception form at the dock, routed to whoever owns the log, closes that gap without adding headcount. The index adjustment line is populated on a calendar basis, not an event basis: on each contractual reset date, someone checks the invoiced price against the current index value and logs the difference if the vendor has not already corrected it. Reconciling this log monthly against the vendor's issued credits is what catches a lapsed claim while the window is still open, not after. ## 6. Should you chase every missed credit, or focus on the biggest contracts first? **Start with contracts carrying board index clauses and high freight-weighted volume, since a missed index reset compounds across every invoice until it is corrected, while a single short ship is a one-time amount. Prioritizing by which contract mechanism compounds over time, rather than by vendor name or invoice count, targets the claims that grow largest the longer they go unclaimed.** An index-linked price that failed to reset affects every invoice issued after the reset date until someone catches it. A short ship or a damaged load, by contrast, is a single event with a single dollar value attached. That difference in how the error compounds is a better prioritization signal than vendor size or invoice volume alone. The practical order is: confirm which corrugate contracts carry an index adjustment clause and check those pricing tables first, since a missed reset is silently recurring. Then work through open rejections and short ships against their claim deadlines, oldest first, since those are the ones closest to expiring. This is a sequencing decision, not a claim that one category of drift outweighs another across a broader set of contracts. It reflects how a specific clause behaves once it is missed, nothing more. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. See also [the six categories drift hides in](/guides/indirect-spend-audit-categories) and [accessorial charge audit: the surcharges nobody validates](/guides/accessorial-charge-audit-the-surcharges-nobody-validates). ## 7. Frequently Asked Questions (People Also Ask) ### What is a missed credit memo in packaging and corrugate spend? It is a credit the vendor owes under the contract, for a board index adjustment, a damaged load, or a short ship, that was never issued or never claimed. The obligation exists in the contract language regardless of whether either side ever generates the paperwork for it. ### Does three-way matching catch a missed credit memo? No. Three-way matching confirms the invoice agrees with the purchase order and the receiving document on quantity and price. It does not test whether a rejected pallet was subtracted from the receiving record or whether the invoiced price reflects the current board index. ### How long do we have to claim a damaged-load credit? The claim window is set in the supply contract, not by law or convention, and varies by vendor. Check the master agreement or pricing addendum for the specific number of days from delivery, since filing after that window can void the claim under the contract's own terms. ### Who is responsible for catching a missed board index adjustment? Typically no single role owns it. Receiving does not see pricing, AP does not track index resets, and procurement negotiated the clause once and moved on. A standing log with a named owner and a fixed reconciliation schedule is what closes that gap. ### Can a corrugate vendor refuse a credit claimed after the fact? Yes, if the contract sets a claim window and the request falls outside it. This is why logging the event date and deadline at the time of the rejection or short ship matters more than trying to reconstruct it later from receiving records. ### Is a return-to-vendor process the same as a credit memo claim? No. A return-to-vendor process moves physical product back to the supplier, but it does not automatically generate a billing credit unless it is separately documented and submitted against the contract's claim process. ### What documentation does a corrugate vendor usually require for a rejected load? This is set by the individual contract, but commonly includes a signed delivery exception noted at receipt, photos of the damage, and sometimes a formal return authorization number issued by the vendor before a credit is processed. ### Does a falling board index automatically lower our invoice price? Only if the contract's adjustment mechanism is applied on the invoicing side. A falling published index does not change a supplier's billing system automatically. Someone has to verify the invoiced price against the index on each contractual reset date. ### How does this differ from a rebate that goes unclaimed? A rebate is typically tied to a volume threshold across a period and paid retrospectively. A missed credit memo in packaging is tied to a specific delivery event, a rejection, a shortfall, or a price reset, each with its own claim window and documentation requirement. ### Where does this fit within a broader indirect spend audit? It is one drift type within the packaging and corrugate category, alongside pricing and accessorial issues covered elsewhere. A full indirect spend review checks credit memo obligations across all vendor categories, not packaging alone. ### Is contract complexity quietly draining your operating margin? A small systematic drift between your negotiated contracts and your actual vendor billing compounds quietly across a year of invoices. Stop guessing at your exposure and run a targeted audit. **[Take the Free Screener → https://valuexpa.com/margin-drift-screener](https://valuexpa.com/margin-drift-screener)** ## Executive Summary The mechanism is straightforward and almost never audited. A packaging supplier's contract sets a formula for adjusting price against a board index, a return allowance for damaged or rejected loads, and a short-ship credit when a delivery arrives under the ordered quantity. Each clause creates an obligation on the vendor's side of the ledger, not the buyer's. Nobody at the buyer has to do anything for the credit to be owed, and that is exactly why it goes unclaimed: there is no invoice event that forces a reconciliation, only a contract clause sitting in a PDF that AP never opens. AP's job ends when an invoice is coded and paid. It does not include checking whether a prior return, index drop, or short shipment ever generated the memo the contract promises. Without a standing log that ties each qualifying event to a credit memo number and a received date, the obligation expires against the vendor's own record-keeping or gets buried in a reconciliation nobody runs. What changes it is treating the credit memo clause as a payable in reverse: tracked, dated, and matched against a received document, the same way an invoice is matched against a purchase order. Absent that discipline, the credit is real on paper and never becomes cash. The Producer Price Index for converted paper and paperboard products moved 2.8% higher year over year in the July 2026 reading (US Bureau of Labor Statistics, PPI series WPU0915, read 2026-09-06), which is the kind of index movement a board-linked pricing clause is built to track in both directions. ## 1. How does a corrugate contract create a credit memo obligation in the first place? A corrugate supply contract typically creates credit obligations through three separate clauses: a board index adjustment that lowers price when the referenced index falls, a damaged or rejected load allowance, and a short-ship credit for quantities delivered under the purchase order. Each clause is triggered by a different event, tracked in a different place, and owed by the vendor without the buyer having to request it, which is exactly why each one is easy to let lapse unclaimed. The board index clause ties unit price to a published containerboard or linerboard index, often reset monthly or quarterly. When the index falls, the contract calls for the lower price to apply, sometimes retroactively to the start of the pricing period. If the vendor invoices at the old, higher price during the gap between the index move and the system update, the difference is owed back as a credit. The damaged-load allowance covers corrugate that arrives crushed, wet, or otherwise unusable on receipt. The contract usually states a rejection process and a credit timeline, separate from a return-to-vendor process some receiving teams use instead, which does not generate the same paperwork trail. The short-ship credit applies when a truckload arrives under the ordered case count. Receiving may accept the load as delivered because production needs the boxes, without flagging the shortfall as a billable difference the vendor owes back. ## 2. Where does the credit memo actually go missing? The credit memo goes missing at the handoff between the event that creates it and the record that would surface it. Receiving logs a damaged load or a short ship in a warehouse system that AP never queries. The board index reset lives in a supplier contract file, not in the ERP's pricing table. None of these systems talks to the other, so the obligation exists in three places and is reconciled in none of them. Consider the sequence for a damaged load. Receiving marks the pallet as rejected in the warehouse management system and moves on. The purchase order still shows the full quantity received, because the rejection was noted outside the PO line. AP pays the invoice as billed, since nothing in the invoice-to-PO match flags a rejected pallet that was never subtracted from the billed quantity. The board index case is subtler. Pricing resets happen on a schedule set in the contract, not in the vendor's billing system. If the vendor's system is not updated to the new index value on the reset date, invoices continue at the old rate until someone notices, and by contract the difference for that whole gap is owed as a credit. Short ships fail for a similar reason: the receiving document and the invoice both show a lower quantity than ordered, which looks consistent on its face. Nothing forces a comparison between what was actually charged and what should have been charged after the shortfall. ## 3. What does three-way matching catch here, and what does it miss? Three-way matching checks that the invoice quantity and price agree with the purchase order and the receiving document. It does not test whether a rejected pallet was ever subtracted from the receiving record, and it does not test whether the price on the invoice reflects the current board index. Both checks require information the match was never built to hold, so the invoice clears even when a credit is owed. A standard three-way match compares three numbers: what was ordered, what was received, and what was billed. If those three agree, the invoice passes, regardless of whether the received quantity itself was correct. That is the gap. A damaged pallet accepted onto the dock, then rejected on a separate quality form, never changes the receiving quantity the match checks against. A board index that dropped after the PO was cut is invisible to a match built around quantity and PO price, not a live index feed. The control is doing exactly what it was designed to do: confirm the invoice matches the order and the receipt. It was never designed to test a pricing formula or a post-receipt quality rejection, which is why closing this gap needs a separate check built specifically around the credit memo clauses in the contract. ## 4. Which contract terms should you check before assuming a credit was earned? Three fields determine whether a credit is actually owed: the index adjustment mechanism and its reset date, the damaged-load claim window and documentation requirement, and the short-ship threshold and credit formula. All three sit in the master supply agreement or a pricing addendum, not in the invoice, so confirming an obligation means reading the contract, not the AP ledger. None of these terms appears on an invoice. They live in the master agreement, an amendment, or a pricing schedule that was negotiated once and then filed away. Reading them is a one-time task per vendor relationship, not a recurring one, but skipping it means every subsequent question about a specific event has no reference point. A rejection logged eighty days after delivery may be worthless if the contract sets a sixty-day claim window, regardless of how clearly the pallet was damaged. Knowing the window in advance is what turns a receiving-dock event into an actionable claim instead of a dispute nobody can resolve. - Index reset date: The exact date the contract requires the new board index price to take effect, and whether the adjustment applies retroactively to shipments during the gap. - Claim window: The number of days after a damaged or rejected load within which a claim must be filed, after which the vendor's obligation may lapse by the contract's own terms. - Documentation requirement: What the vendor requires as proof of a rejection: a signed delivery exception, photos, or a formal return authorization number. - Short-ship threshold: Whether a shortfall triggers a credit automatically or only above a stated case-count or percentage threshold. - Credit formula: Whether the short-ship credit is the full unit price, a prorated freight adjustment, or both, since contracts vary on this point. ## 5. How do you build a log that actually catches these before they expire? A credit memo log ties each qualifying event, a rejection, a short ship, an index reset, to an expected credit amount, a claim deadline, and a received memo number. It is reconciled on a fixed schedule against what the vendor has actually issued, the same way a bank reconciliation checks a ledger against a statement, so a gap between expected and received credits surfaces before the claim window closes. The log needs four columns at minimum: the event date, the event type, the dollar amount expected under the contract formula, and the claim deadline derived from the contract's claim window. A fifth column records the credit memo number once issued, and a sixth flags anything still open past its deadline. Receiving needs a simple way to feed this log the moment a load is rejected or short, rather than relying on someone in AP to notice it later. A standard exception form at the dock, routed to whoever owns the log, closes that gap without adding headcount. The index adjustment line is populated on a calendar basis, not an event basis: on each contractual reset date, someone checks the invoiced price against the current index value and logs the difference if the vendor has not already corrected it. Reconciling this log monthly against the vendor's issued credits is what catches a lapsed claim while the window is still open, not after. ## 6. Should you chase every missed credit, or focus on the biggest contracts first? Start with contracts carrying board index clauses and high freight-weighted volume, since a missed index reset compounds across every invoice until it is corrected, while a single short ship is a one-time amount. Prioritizing by which contract mechanism compounds over time, rather than by vendor name or invoice count, targets the claims that grow largest the longer they go unclaimed. An index-linked price that failed to reset affects every invoice issued after the reset date until someone catches it. A short ship or a damaged load, by contrast, is a single event with a single dollar value attached. That difference in how the error compounds is a better prioritization signal than vendor size or invoice volume alone. The practical order is: confirm which corrugate contracts carry an index adjustment clause and check those pricing tables first, since a missed reset is silently recurring. Then work through open rejections and short ships against their claim deadlines, oldest first, since those are the ones closest to expiring. This is a sequencing decision, not a claim that one category of drift outweighs another across a broader set of contracts. It reflects how a specific clause behaves once it is missed, nothing more. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. See also [the six categories drift hides in](/guides/indirect-spend-audit-categories) and [accessorial charge audit: the surcharges nobody validates](/guides/accessorial-charge-audit-the-surcharges-nobody-validates). ## Common questions ### What is a missed credit memo in packaging and corrugate spend? It is a credit the vendor owes under the contract, for a board index adjustment, a damaged load, or a short ship, that was never issued or never claimed. The obligation exists in the contract language regardless of whether either side ever generates the paperwork for it. ### Does three-way matching catch a missed credit memo? No. Three-way matching confirms the invoice agrees with the purchase order and the receiving document on quantity and price. It does not test whether a rejected pallet was subtracted from the receiving record or whether the invoiced price reflects the current board index. ### How long do we have to claim a damaged-load credit? The claim window is set in the supply contract, not by law or convention, and varies by vendor. Check the master agreement or pricing addendum for the specific number of days from delivery, since filing after that window can void the claim under the contract's own terms. ### Who is responsible for catching a missed board index adjustment? Typically no single role owns it. Receiving does not see pricing, AP does not track index resets, and procurement negotiated the clause once and moved on. A standing log with a named owner and a fixed reconciliation schedule is what closes that gap. ### Can a corrugate vendor refuse a credit claimed after the fact? Yes, if the contract sets a claim window and the request falls outside it. This is why logging the event date and deadline at the time of the rejection or short ship matters more than trying to reconstruct it later from receiving records. --- ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms, for $100M+ US industrial manufacturers and distributors. Two to four weeks. The client retains 100% of recoveries. https://valuexpa.com/contact-us