Walmart Chargeback Code 25: No Merchandise Received

Executive Summary & Quick Answer

Executive summary: Code 25 is the scariest line on a Walmart remittance because it deducts the entire invoice — Walmart's system found no receipt to match it. Nine times out of ten, nothing was actually lost: the invoice simply arrived before the freight, or an ASN/PO mismatch orphaned the receipt. It's a timing and matching failure, which makes it one of the most preventable codes on the board — and one of the most disputable when the goods really did arrive.

Quick answer: Walmart Chargeback Code 25 is a deduction taken when Walmart's system shows no merchandise receipt matching an invoice — commonly because the EDI 810 invoice arrived before the shipment was delivered and received. Walmart deducts the full invoice value. Prevention: transmit invoices at or after delivery, with ASN and PO data matching.

---

Deep Dive: What Triggers Code 25

Walmart pays invoices it can match to receipts. Code 25 means the match found nothing — an invoice standing alone with no receiving record behind it. Three mechanisms produce that orphan:

1. The race condition (most common). Your 810 transmits at ship time; the freight delivers three days later. The AP match runs, finds no receipt, and deducts the whole invoice. The goods arrive the next morning — but the deduction already exists, and now you're disputing to get your own money back.

2. The orphaned receipt. The goods arrived and were scanned, but the ASN or PO data didn't line up (wrong PO number, wrong DC number, ASN never sent), so the receipt couldn't attach to the invoice. Both records exist; the join failed.

3. The genuine miss. Delivered to the wrong DC, or never scanned at receiving. Rare, but real.

Timing discipline in one line: the 856 leaves before the truck arrives; the 810 leaves at or after delivery. Reverse either order and you're manufacturing Code 25s.

correct:   856 ──► freight arrives ──► receipt ──► 810 ──► clean match ──► paid
broken:    810 ──► match runs (no receipt!) ──► CODE 25 ──► freight arrives (too late)

---

Business & Financial Impact

• Deduction = 100% of the invoice. Not a delta — the whole thing. By dollar value, Code 25 events dwarf other shortage codes.
• Cash-flow shock: a large PO's full value vanishes from a remittance, often triggering internal fire drills.
• High dispute-win potential, high labor: if the goods arrived, a POD + receipt evidence wins — but you're spending AP hours to recover money that a timing rule would have kept.
• Repeat offender pattern: a billing system configured to invoice at ship time produces Code 25s on every slow lane, forever.

---

Root Causes (Ranked)

1. 810 transmitted before delivery — invoice-at-ship configurations.
2. ASN/PO mismatch orphaning the receipt — wrong PO number, DC number, or a missing 856.
3. Delivery to the wrong DC — receipt exists at a facility the match doesn't check against the PO.
4. Receiving scan misses — freight arrived, cartons never scanned against the PO.
5. Duplicate/split PO confusion — invoice references a PO line the receipt landed against differently.

---

Step-by-Step Prevention Workflow

1. Gate the 810 on delivery. Configure billing to release invoices on POD/delivery confirmation — not on ship confirmation. This single change eliminates the race condition.
2. Send the 856 on time, always. The ASN creates the receiving expectation that the receipt attaches to. No ASN, fragile match.
3. Validate join keys before transmission: PO number, DC number, and item data identical across 850 → 856 → 810.
4. Track delivery vs invoice status daily: any invoice older than X days with no matching receipt is a pre-deduction alarm — chase it before AP does.
5. Weekly sweep: Code 25s matched to PODs and receipts → dispute with evidence; no POD → trace the freight.

---

The Dispute Path

Code 25 disputes are unusually winnable when the goods arrived:

1. Pull the deduction (invoice, PO, amount).
2. Gather the POD (signed, dated) and any receiving evidence.
3. File in APDP referencing PO + invoice; attach POD.
4. If freight truly went astray (wrong DC), work with your buyer to locate/redirect — then dispute or re-bill per the resolution.

---

Code 25 vs Its Siblings

Code	Receipt exists?	Deducts
25	No matching receipt at all	Full invoice
22	Receipt exists, quantity lower	The difference
24	Receipt exists, signed short	The short cartons

Related: Code 22 · Code 24 · Code 21

---

Supplier Checklist

• 810 release gated on delivery/POD confirmation (never ship-time)
• 856 transmitted before arrival on every PO
• PO #, DC #, item keys identical across 850/856/810
• Daily alarm: invoices with no matching receipt after X days
• Weekly: Code 25 sweep — dispute with POD, or trace the freight

---

FAQs

What is Walmart chargeback Code 25? A deduction taken when Walmart's system finds no merchandise receipt matching an invoice. The full invoice value is deducted — most often because the invoice arrived before the freight.

Why did Walmart deduct my entire invoice? That's Code 25's signature: with no receipt to match, the system treats the whole invoice as unsupported. Usually the goods arrived later or the receipt failed to join due to PO/ASN data mismatches.

How do I dispute Code 25? Via the APDP in Retail Link with the signed POD and the PO/invoice references. When the goods genuinely arrived, Code 25 disputes are among the most winnable.

How do I prevent Code 25 permanently? Gate invoice transmission on delivery confirmation, always send the ASN before arrival, and keep PO/DC join keys identical across the 850, 856, and 810.

Is Code 25 the same as Code 22? No. Code 22 is a partial gap (received less than billed). Code 25 means no receipt matched at all, so the entire invoice is deducted.

---