A Walmart remittance advice is the payment document, an EDI 820, showing what was paid against each invoice and what was subtracted first. Deduction lines carry a numeric code, a dollar amount, and a reference back to the invoice or PO. Reading one means matching that code to a claim type, then deciding if the line is worth disputing.
Based on the public X12 820 transaction-set structure (SPS Commerce's EDI reference), vendor guides to Walmart's Accounts Payable Dispute Portal and APIS search fields (SPS Commerce, iNymbus), and a 2025 industry benchmark on deduction write-off rates (Finortal, cited via OverDeduct), August 2026.
You’re holding a Walmart check that’s short. Or you’re staring at an EFT deposit that doesn’t match the invoice total you built the number around. Either way, a chunk of the payment never arrived, and you don’t yet know which line took it.
If you run supply chain, deductions, or finance for a $10M-$500M CPG supplier, this isn’t a one-time puzzle. It’s a line item taken off your check this cycle. If the same code shows up next cycle too, it’s a recurring loss you’re absorbing without a fight, month after month. Upstream teams rarely tell you which invoice it hit or what the code means.
The document that explains the gap is right in front of you. Reading it correctly is what turns a mystery deduction into either a five-minute dispute or a process fix that stops the bleeding for good. This piece teaches you to read it.
What is a remittance advice, and why does it read like noise?
A remittance advice is the payment document, not the bill. Walmart sends it with a check or an EFT deposit. It states what got paid, against which invoices, and what got subtracted first.
The document itself is an EDI 820, Payment Order/Remittance Advice, one of the older transaction sets in the X12 standard. It was built for machine reconciliation, not human reading. That’s why a printed or PDF version reads like a spreadsheet dumped by an accounting system. Because that’s what it is.
Three segments carry what a supplier actually needs. BPR holds the total payment: amount, method, banking detail. RMR maps each invoice to what got applied against it. ADX carries the adjustment itself, a reason code and an amount, for every dollar that didn’t make it into the payment.
That ADX reason code is the number you’re actually hunting for. Everything else on the remittance exists to help you find that one field and figure out what it’s claiming happened.
Where do the invoice number, PO number, and check total actually live?
They’re all there. Just not laid out the way an invoice is.
The check or EFT total appears once, near the top, tied to the BPR segment. Below it, one block per invoice being paid, each carrying its own reference number from RMR. Underneath an invoice block, one line per deduction taken against that invoice, each with its own code and amount from ADX.
No vendor guide publishes a field-by-field screenshot of this layout inside Retail Link or on a printed check stub. Neither Walmart nor its suppliers have made that layout public in a form worth citing here.
What vendor sources describe consistently is the matching workflow on the other end. Suppliers search Walmart’s Accounts Payable Inquiry System (APIS) by invoice number, PO number, deduction code, claim number, or vendor number, per SPS Commerce’s guide to the dispute portal. If the remittance line is confusing, that search is the actual next step. Not a magnifying glass.
How does a deduction code map to a claim type?
The code is a category. Not an explanation.
Vendor sources group Walmart’s deduction codes into families: shortage claims, pricing discrepancies, compliance and OTIF fines, freight and routing violations, and returns-related charges. Each family has a different root cause and a different evidence bar for disputing it.
This site’s own deduction-code hub organizes entries the same way, across seven cause families: Shortage, Pricing, Compliance, Freight, ASN/EDI, Quality, and Returns. A shortage code and a pricing code look identical on a remittance line, a number and a dollar amount. But they call for different evidence.
A shortage dispute needs proof of what physically shipped. A pricing dispute needs proof of the price the buyer actually agreed to. Reading the code correctly is the difference between pulling the right document on the first attempt, and burning a week chasing the wrong one.
Which lines are worth pursuing?
Not all of them. Size alone is the wrong filter.
Vendor sources point to frequency instead, per SPS Commerce’s guide to disputing a deduction. A deduction code that shows up once or twice in a cycle is usually a one-off, an isolated data mismatch or receiving error. Worth a quick dispute and nothing more.
The same code showing up every cycle, on every shipment, at a similar rate, is a process problem wearing a claim number. Disputing it line by line treats the symptom. Tracing it back to the ASN, the invoice timing, or the item file fixes the rate at the source.
Materiality matters too. Just not the way it feels like it should. A single $40 deduction usually costs more in staff time to research and dispute than it returns if you win. The same $40 pattern repeated across two hundred shipments a quarter is a five-figure number, and it’s the same underlying error either way. The unit to evaluate isn’t the line. It’s the pattern the line belongs to.
Vendor and consultant estimates put the invalid or preventable share of retail deductions at 10-40%, citing a 2025 Finortal benchmark. No public industry-wide figure exists. Reported ranges run as wide as roughly 5% to 60%, depending on category and retailer.
What happens after you decide to dispute?
Filing is only the start of the clock.
Vendor documentation of Walmart’s Accounts Payable Dispute Portal (APDP) describes two housekeeping deadlines worth knowing before you open a case. A draft dispute you start but don’t submit expires automatically after 14 days. A case Walmart flags “Supplier Action” auto-closes if you don’t respond within 7 days. That status means Walmart wants more from you before it will rule. Neither deadline is the underlying claim-dispute deadline for a given code. That deadline varies and isn’t confirmed here.
One more nuance worth knowing. Not every deduction routes the same way. Vendor sources describe certain codes as handled outside APDP entirely, through a separate channel. These are mostly returns-related codes (92, 93, 94) that flow through a Returns Center. Filing a standard APDP dispute against one of those gets you nowhere.
If a code doesn’t behave the way this piece describes, that’s the likely reason. Confirm the channel in APIS before assuming the dispute failed on the merits. The dispute deadline table covers the full set of Walmart dispute windows by claim type, plus the equivalent deadlines for Target, Amazon, and Kroger.
If you read a Kroger remittance too, the document works differently enough to need its own map: Kroger splits numeric AP codes from compliance fees onto two tracks with two clocks, walked through in the Kroger supplier deductions guide.
Deduction code to claim type: a quick map
| If the code family is… | It’s typically claiming… | What to pull first |
|---|---|---|
| Shortage | Received quantity was less than invoiced | ASN transmission log, signed BOL or POD |
| Pricing | Invoice price didn’t match the PO | Buyer-approved cost change, three-way match |
| ASN/EDI | The 856 was late, missing, or structurally wrong | 856/824 transmission logs, timestamps |
| Compliance / OTIF | Delivery missed the window, on-time or in-full | Carrier pickup/delivery timestamps |
| Freight | A routing guide requirement wasn’t met | Routing confirmation, carrier selection record |
| Quality | Goods didn’t meet a quality or labeling spec | Inspection records, photos, spec sheet |
Found a code on your remittance? The deduction-codes hub covers it by retailer, with the root cause, evidence checklist, and dispute path for each entry, including Walmart code 22 (goods billed not shipped), Walmart code 24 (freight bill signed short), Walmart code 21 (concealed shortages), and Walmart code 25 (no merchandise received), four of the shortage-family codes this piece’s evidence guidance maps to directly.
If the pattern looks systemic rather than isolated, size it before you commit staff time to tracing it further. The OTIF calculator does that math for the on-time, in-full side of the ledger.
Sources
- “EDI 820 - Payment Order/Remittance Advice,” SPS Commerce, for the BPR/RMR segment structure of the underlying EDI standard.
- “426 Adjustment Reason Code of ADX-2100,” Zenbridge EDI Dictionary, for the ADX segment and adjustment reason code element.
- “Walmart’s APDP: A Clear Guide to the Accounts Payable Dispute Portal,” SPS Commerce, for the APIS search fields, the 14-day draft expiry, the 7-day Supplier Action window, and the returns-center routing exception.
- “How To Dispute A Walmart Deduction,” SPS Commerce, for the frequency-based triage guidance and the deduction-size range.
- “What Is a Deduction?,” OverDeduct, for the invalid/preventable-share estimate range and the Finortal 2025 benchmark citation.
The underlying EDI 820 structure is the public X12 standard. Field layout inside Walmart’s own Retail Link or printed remittance documents is not independently confirmed here. The workflow described (searching APIS by invoice, PO, or code) is vendor-reported. If your own remittance doesn’t match this description, tell us and we’ll correct it.
Frequently Asked Questions
- Why is my Walmart check short?
- It's not a check for the invoice total. It's a check for the invoice total minus every deduction line Walmart's system applied first. Each deduction carries a code and a reason, and the check reflects the net after all of them.
- Where do I find what a Walmart deduction code means?
- The code itself appears on the remittance line, next to the amount and a reference back to the invoice or PO. What the code means isn't printed there. Look it up separately, in Walmart's own Retail Link documentation or a fact-checked reference like this site's deduction-code hub.
- Should I dispute every deduction on a Walmart remittance?
- No. Vendor sources point to frequency as the better signal, not size. One or two deductions in a cycle usually means a one-off error, worth a quick dispute. The same code every cycle points to a process problem upstream, worth fixing at the root.
- How long do I have to respond once I open a Walmart dispute?
- Per vendor documentation of the Accounts Payable Dispute Portal, a draft dispute expires automatically after 14 days if not submitted. A case Walmart marks 'Supplier Action' auto-closes if you don't respond within 7 days. The overall claim-dispute deadline for a given code is separate and varies. It isn't confirmed here.
Find out what your deductions are actually costing you.
A 30-minute call with the founder, who will tell you which of the three scans fits your problem, or that none of them do.