Back to blogs

    Tracing a missed MABD chargeback back to the shipment

    By TransportOne Editorial Team•November 22, 2026•7 min read
    Empty loading dock doors along the exterior wall of a distribution warehouse.

    A Walmart remittance lands short by $4,100 against invoices you shipped six weeks ago. The backup is a single line: a claim number, deduction code 99, and the words On Time In Full. Nothing says which purchase order missed, by how much, or whether the trailer was late or the pallet was short.

    Accounts payable codes it to compliance fines and closes the month. Next scorecard period you get another one, same distribution center, same carrier.

    What a code 99 deduction actually says

    The must-arrive-by date is the delivery date the retailer stamps on the purchase order, and OTIF scores every PO against it. On-time means the freight hit the DC inside the MABD window. In-full means the cases received matched the cases ordered.

    Walmart set both thresholds at 98 percent in September 2020, which FreightWaves covered at the time. They moved to 90 percent on-time and 95 percent in-full effective February 1, 2024, announced on Retail Link and reported by Logistics Viewpoints that week. The fine runs 3 percent of the cost of the goods, and it lands as a deduction against what you're owed, not as an invoice you can route through AP.

    That difference decides how you fight it. SPS Commerce's walkthrough of Walmart's Accounts Payable Disputes Portal lists code 99 among the codes you can't file against in APDP at all. OTIF disputes go to the merchant team with documentation attached, so a human reads whatever you send and nothing reverses automatically. The evidence has to exist before anyone looks at it, and nobody builds a case file for a line that reads only $4,100.

    Walmart's program is the best documented one, and the mechanism repeats at the other large retailers: a delivery window on the PO, a scorecard behind it, a deduction when the scorecard slips. The evidence that answers one of them answers all of them, so build the trace once instead of per account. It's also why freight audit for retail suppliers has to reach chargeback evidence and not stop at the carrier invoice.

    A missed MABD lands at PO grain, your freight data lives at load grain

    The deduction names a PO. Your TMS doesn't have a concept of a PO. It knows load IDs, BOL numbers, stops and SCACs, and its relationship to a purchase order is many-to-many in both directions.

    One trailer into a single DC can carry nine POs. One PO of 140 cases can split across two trailers when the first one cubes out, and then half of it is on time and half of it isn't. Most teams bridge the gap with a spreadsheet that one person maintains until they change jobs.

    Start from the ASN

    The 856 is the only document that already carries both keys. The shipment loop holds the BOL number and the SCAC. The order loop holds the PO. Join the deduction to the ASN on PO, join the ASN to the TMS on BOL, and the load is in front of you.

    It breaks when a corrected ASN goes out with a new BOL after the trailer has already left, which on collect freight happens more than anyone admits to. Keep both BOL values on the record. This is the same join that makes matching invoices back to loads hard, and it fails for the same reason: the identifier changed after the event it was supposed to describe.

    Read the 214 against the carrier's own invoice

    With the load identified, pull the status feed. X3 is arrival at the pickup location, AF is departure with the shipment, X1 is arrival at the delivery location, D1 is completed unloading. Those four timestamps place the failure at your dock, on the road, or at the retailer's gate.

    An X1 at 06:40 and a D1 at 15:20 on the day after the window closed describes a trailer that sat at the gate for almost nine hours and still arrived a day late. Those are two failures with different owners, and the deduction collapses them into one number.

    Then read what the carrier billed for the same stop. A detention charge against that delivery is the carrier stating in writing that the DC held the truck. Run those accessorials through an automated freight invoice audit against the same event feed your shipment exception tracking already collects, and the detention claim and the arrival timestamps get reconciled before the chargeback ever appears on a remittance.

    None of that clears you on the arrival date. Late is late, and the merchant team will say so.

    What it buys you is the next conversation, because a driver who ran out of hours and a DC that can't unload inside four hours need completely different fixes.

    Four misses that look identical on the deduction line

    What the scorecard sawWhat actually happenedWhere the proof isWho can fix it
    Late arrivalCarrier accepted the tender and arrived at origin after the pickup window closed, then ran short on hoursTender acceptance timestamp against the X3, driver hours on the carrier's sideCarrier management, or the award on that lane
    Late arrivalThe first delivery appointment the DC would give was two days past the MABDScheduling request time against the slot that was grantedOrder release date, nothing in transportation
    In-full missThe pick line cut 12 cases of 140 and the freight was perfectly on timeCases on the 856 against cases on the 850Warehouse and inventory, not the carrier
    Late arrivalDriver hit the gate before the window opened, got turned away, redelivered the next morningX1 ahead of the window, plus a redelivery charge on the carrier invoiceRouting instructions and the appointment itself

    The second row is the one to measure first. When the earliest appointment a DC will offer already sits outside the MABD window, no amount of carrier performance work moves the scorecard, and the only lever left is releasing the order sooner. The cost side of that same squeeze shows up as the appointment you cannot get.

    Where we'd stop arguing

    Three percent of cost of goods reads like a number worth staffing a recovery team against, and the aggregate doesn't support that. Russell Zuppo of Uber Freight told Logistics Viewpoints in February 2024 that Walmart suppliers in Uber Freight's customer base pay OTIF fines amounting to roughly 0.16 percent of cost of goods sold.

    Across a large book that's still real money, and nowhere near enough to justify a standing dispute desk for a code you can't even file in the portal. Our position: the fine is worth more as a diagnostic signal than as a recovery target. Most shippers throw that value away in the first five minutes, by booking every one of them to a single GL account with no PO attached.

    The step teams skip is classifying each fine to a cause while the trail is still warm. Status history ages out of carrier portals and the driver moves to another fleet. By the time a quarterly review notices the total, the only surviving fact is the dollar amount.

    One split is worth checking before you touch a carrier relationship. Sort the fines into late versus short. If the in-full failures outnumber the on-time ones, your scorecard is being driven by the pick line and the inventory behind it, and rebidding lanes won't move the number. That surprises transportation teams more often than it should, and confirming it takes an afternoon: cases ordered against cases shipped on the ASN, for every fined PO.

    Start with last quarter

    Pull every code 99 deduction from the last three months. For each one find the PO, the ASN, the BOL and the 214 feed, then put four columns next to the dollar amount: when the MABD window closed, the X1 arrival timestamp, cases ordered, cases received. Sort the result by DC.

    If the money concentrates in one or two buildings, you've got a dock and appointment problem at specific sites, and the fix is a scheduling conversation rather than a carrier one. If it spreads evenly across everywhere you ship, the orders are going out too late and transportation is only where the damage surfaces. Most teams find some of both, in a ratio they'd have guessed wrong.

    Book a walkthrough to see Chase join a quarter of OTIF deductions back to the loads and the stop events behind them.

    Frequently asked questions

    What does Walmart deduction code 99 mean?
    Code 99 is the On Time In Full compliance fine, assessed when purchase orders miss the must-arrive-by date or arrive short against the ordered case count. It reaches you as a deduction on a remittance rather than as an invoice. SPS Commerce's guide to Walmart's Accounts Payable Disputes Portal lists code 99 as one of the codes you cannot file against in APDP, so the dispute goes to the merchant team with documentation attached.
    What is the MABD window and how is it scored?
    The must-arrive-by date is the delivery date carried on the purchase order, and the retailer scores on-time performance against it at PO level. In-full is scored separately, comparing cases received to cases ordered. Missing the window in either direction causes trouble: a trailer that arrives before the window opens often gets turned away at the gate, and the redelivery the next day is recorded as a late receipt.
    Can you dispute an OTIF chargeback?
    Yes, but not through the self-service portal for Walmart code 99. You send documentation to the merchant team, which means the evidence has to be assembled by hand first. What carries weight is specific: EDI 214 arrival and unload timestamps for the load, the appointment the DC actually granted against the one you requested, the signed receipt, and ASN case counts against the PO.
    How much do Walmart OTIF fines cost suppliers?
    The headline rate is 3 percent of the cost of the goods on the non-compliant portion. The aggregate is much smaller: Russell Zuppo of Uber Freight told Logistics Viewpoints in February 2024 that Walmart suppliers in Uber Freight's customer base pay OTIF fines equal to roughly 0.16 percent of cost of goods sold. The thresholds that trigger the fine moved to 90 percent on-time and 95 percent in-full on February 1, 2024.

    See it on your freight

    Stop Overpaying On Freight Invoices

    Penny checks every invoice against your contracts and what the shipment actually did, then disputes what doesn’t hold up. You pay 30% of what she saves you, and nothing if she saves nothing.

    See how Penny works

    Found this useful? Share it with your team.

    Share on LinkedIn