File an OTIF Dispute in APDP and Walmart Auto-Denies It

The memo lands. Walmart took a deduction, the reason line mentions OTIF or an ASN, and the money is already off the invoice.

The instinct is to open Retail Link, find the invoice, and dispute. If the deduction is an OTIF or compliance chargeback, that filing is auto-denied, and the clock you were trying to beat keeps running while it happens.

Walmart runs two dispute queues. They measure their windows from different events. Nothing on the deduction memo tells you which one you are in.

Two queues, two clocks

Two things make that split expensive rather than merely annoying.

The windows are measured from different events. APDP counts from posting. HighRadius counts from invoicing. Those are different dates on different documents, so the same deduction can sit comfortably inside one window and near the edge of the other. Working out which date applies is not a formality. It is the whole task.

HighRadius access is a separate request, and it takes time you do not have. It is requested by email to HiRadCS@walmart.com. If nobody on your team has already opened it, the queue holding your OTIF dispute is not available to you on the day the memo arrives, and the clock does not pause while access is provisioned.

The APDP filing sequence itself is straightforward. Log in at retaillink.login.wal-mart.com with your Supplier User ID and password, navigate to the AP Disputes Portal, find the deduction by invoice number, PO number or date range, click Dispute on the line item, upload the documents, then submit and keep the dispute reference number for tracking.

We cannot walk you through the HighRadius sequence, and the honest reason is that we do not have a verified filing procedure for it. Ask for it in writing when you request access. An improvised sequence is how a dispute gets auto-denied in the first place.

The six reason codes

Walmart's deduction lines carry a short code, and the code tells you what kind of argument you have.

MABD is Walmart's Must Arrive By Date: the date the DC expects the shipment, not the date you shipped it.

Routing follows the nature of the deduction. WM-PRC is an invoice price against PO price discrepancy, which is an AP dispute, so it belongs in APDP on the posting clock. WM-OTIF is an accounts-receivable deduction counted from invoicing, and it goes to HighRadius. The ASN codes are compliance chargebacks, and compliance chargebacks run to HighRadius on that same basis.

Two codes not worth a day of your time

WM-LBL and WM-RTG are marked as not usually disputable, and the reason is structural rather than procedural. Neither one is an error in Walmart's posting. A label either scans or it does not, and the carrier you tendered to is on your own record. There is no document you can attach that turns a physical non-compliance into a bookkeeping correction.

The amounts are also small enough that the money sits in the recurrence, not the filing: labeling runs $50-500 per incident, and routing runs the freight-cost difference.

A labeling packet does exist, and it is worth having in reserve: label artwork approval, GS1 barcode verification, carton label photos. But the same hour is better spent on the label template that produced the unscannable cartons, and on the carrier list your team tenders against.

What each class of deduction needs

The pattern is worth noticing. OTIF disputes are won on timestamps; ASN disputes are won on transmission records. A POD carrying a receiver signature is the anchor in a quantity argument, and a 997 functional-acknowledgment gap is the anchor in a transmission argument.

How to assemble the shortage packet is in what wins a shortage dispute, and the two Walmart compliance programs generating most of these deductions are covered in OTIF and SQEP, which are not the same thing.

Three checks before you file

Was the ASN actually transmitted on time? OTIF and ASN fines are routinely reversed when the 997 functional-acknowledgment gap shows the ASN went out inside the window. Attach the 997 transmission log every time. It is the document that turns an ASN charge into a winnable dispute.

Was the truck early rather than late? Walmart's DCs schedule dock capacity tightly, and arriving before the MABD or appointment window is penalised exactly like a late delivery, at 3% of cost of goods. If the POD timestamp shows delivery inside the scheduled appointment, the fine is disputable. Check this before you assume the DC recorded your arrival wrong.

Are you inside the first-supplier grace period? First-time Walmart suppliers get a three-month grace period in which OTIF fines are waived. Confirm your tenure before you build a packet. If the grace period applies, the correct action is not a dispute at all.

Windows, portals and filing quirks across every retailer are in the dispute window table.

An OTIF deduction is 3% of cost of goods on the non-compliant case, and you have roughly 30 days counted from the invoice date. That window does not pause while you request portal access, and it does not restart when an auto-denial comes back. Open the HiRadCS access this week, and count from the invoice date, not the posting date.