DIRECT ANSWER
A repeated Walmart deduction code is a clue, not a proven cause. Connect each claim to its invoice, PO, receiving evidence and applicable terms. Separate correct charges from possible errors, then track two outcomes: what happened to the claim and whether the same documented mismatch appeared on later transactions.
The same code is back on another Walmart payment. You disputed the previous one, someone said the issue was fixed, and now another invoice has a deduction. Before filing the same explanation again, establish whether this is the same underlying mismatch, a different problem under the same code, or a correct charge that your team expected to disappear.
This guide covers recurring invoice-based accounts-payable deductions for Walmart US merchandise suppliers, with warehouse suppliers as the working example. Marketplace settlements, DSV payments, Pay From Scan, Pay From Receipt and separately billed charges require their own payment records and procedures.
For an optional first-five-minutes start, use the short deduction review note to capture one claim line, the document mismatch or missing evidence, and the next owner. The detailed claim log and recurrence follow-up sheet below support the full investigation.
Start with a few claims you can reconstruct
Choose one recurring code, a defined transaction period and a small group of claims with retrievable documents. Save the original export, supplier ID, filters, reporting cutoff and download date. A chart total cannot tell you which document disagreed with which other document.
Walmart’s Supplier One Deductions Summary describes AP claims as adjustments arising from invoice-matching differences. It identifies the deduction code, invoice number and store number as useful research keys. The official help may require sign-in.
For each selected claim, connect the payment reference to the invoice, PO, item and receiving or shipment evidence. Preserve facility identifiers exactly as recorded; a field labeled store number is not permission to assume that every record concerns a retail store. Keep original quantities and units alongside any case-to-each conversion.
Decide what kind of recurrence you have
The first useful distinction is whether the charge appears consistent with the applicable transaction and terms.
| What the documents show | What to do next |
|---|---|
| The charge matches applicable agreed terms | Record it as expected. If the commercial arrangement needs to change, prepare a separate discussion about future terms. |
| The invoice, PO or receipt disagrees with another record | Identify the exact line, field, amount and effective date in conflict. Establish which record needs correction. |
| A possible duplicate, credit or reversal appears | Link it to the original claim and reconcile the entries before calling it another loss. |
| The necessary document is missing | Mark the cause unconfirmed and assign someone to retrieve it. |
A deduction can be commercially painful and correctly calculated. A cost-change request can exist without proving that its proposed price applied to a particular PO. An open dispute does not establish that a charge was erroneous.
An approval that appears to conflict with the order needs its own comparison. Use the approved-cost and PO guide to establish the item, location, effective basis and order version. Use the case-pack calculation when the apparent mismatch concerns units or pack quantities.
Group by a documented mismatch, not just the code
Use the code to find candidates. Then test narrower connections:
- Item or pack: compare the item identifier, invoiced unit of measure, PO pack and shipment quantities. A shared SKU alone does not identify a conversion error.
- Cost or allowance period: compare the effective agreement, PO version and invoice calculation. Distinguish a request from a confirmed change.
- Shipment or facility: compare the shipping and receiving records for the actual lane. A concentration at one facility also needs an exposure count; it may simply receive most of your volume.
- Invoice process: inspect which system, template or mapping produced the affected field. Check an unaffected transaction from the same process as a counterexample.
Give the pattern a testable description: “These two invoices used a unit cost ten cents above the attached POs.” Avoid labels such as “Walmart pricing problem” until the evidence establishes whose record is wrong.
A worked example: three identical deductions, two evidence states
This example is fictional. A supplier finds three $100 code 11 claims. Walmart’s official description of code 11 concerns item-cost differences, including PO-to-invoice differences.
| Claim | Evidence available | Supported finding |
|---|---|---|
| A: $100 | Invoice: 1,000 eaches at $1.30. PO: 1,000 eaches at $1.20. | A $100 price difference is visible. |
| B: $100 | The same quantities and prices on a second invoice and PO. | The same document mismatch recurred. |
| C: $100 | Invoice available; applicable PO and pricing evidence missing. | Cause remains unconfirmed. |
For A and B, the arithmetic is 1,000 × ($1.30 − $1.20) = $100 per invoice. That explains $200 of the $300 pattern at the document level. It does not establish which price was contractually applicable or how much will be recovered.
The account owner retrieves the price-change approval and effective dates. The invoicing owner checks why the higher price was used. Claim C remains separate until its missing evidence arrives. One code has produced two investigation states, not a proven $300 recovery opportunity.
Track the claim and the prevention change separately
Assign a claim owner to confirm the current filing route, evidence requirements and deadline for the actual charge. Use the dispute-routing guide for that decision; the code 22 guide addresses quantity-related claims specifically. Never choose a filing route from a broad chart category alone.
Assign a prevention owner to the documented process issue. Record the proposed change, approval, implementation date and the first transactions it should affect. Do not change invoice timing, costs or quantities simply to make a claim disappear; reconcile the applicable requirements first.
Then inspect later eligible transactions after enough payment data has arrived. Compare similar items, facilities and terms. Define the transaction unit and unique key before counting, such as invoice line plus invoice number. Build the reviewed population from eligible transaction records, including transactions without deductions. Use the same population and transaction key for both counts; the transactions with the mismatch must be a subset of those reviewed.
Count each eligible transaction once in the reviewed total and once at most in the total with the same documented mismatch. Track affected transactions divided by reviewed transactions, alongside dollars. Fewer claims during a shipment slowdown do not establish an improvement. A later credit may resolve part of the financial claim; it does not show that funds arrived or the invoice process changed. The approved-dispute credit investigation traces those separate outcomes.
Keep claim and prevention records connected
Download the detailed claim-line log. Use one row per original claim line whose amount you can establish. Use supplier ID, claim reference and original claim-line reference as the record key. Update that record when later exports repeat it.
Record the signed amount for that line, with its currency. Keep a claim-level total separately until its line amounts are known; do not repeat that total on every line.
Keep linked credits and reversals separate from the original amount, and include only the amount assigned to this line. If a credit covers several lines, retain an allocation record whose assigned amounts reconcile to the original credit, with any unallocated amount kept separate. Preserve the underlying entry references and reconcile against the remittance before reporting net exposure. Import identifiers as text to preserve leading zeros.
Use the separate recurrence-group follow-up sheet for prevention work, with one row per recurrence group for a defined review window. Join it to the claim log using the recurrence group ID. Record the eligible population, transaction unit and unique key, payment-data cutoff, reviewed unique transactions, and unique transactions with the same documented mismatch. Keep a dated copy when repeating the review. The CSVs organize records; they do not calculate recovery or recurrence rates.
These records connect evidence, uncertainty, claim status and prevention follow-through. When the finding requires a commercial decision, Startup Success Lab’s merchant-decision guide helps turn the issue into a specific request. Its supplier support covers weekly sales, inventory and replenishment reviews and merchant materials, useful when the investigation reveals an account decision to carry forward.
Retail Reason can help interpret the next unfamiliar code and check an evidence plan. See how it works. The useful endpoint tonight is a supported finding, a named owner and a next check that can show whether the problem recurred.
Source and verification scope
Walmart’s indexed official Deductions Summary was reviewed September 13, 2026 and compared with the July 2026 reference text. Direct access required sign-in; current portal menus and individual claim eligibility were not verified. The worksheet, diagnostic sequence and example are original editorial tools, not Walmart filing instructions.