Walmart Chargeback Code 60: Unauthorized Handling Charge

Executive Summary & Quick Answer

Executive summary: Code 60 isn't Walmart fining you — it's Walmart editing your invoice. You added a handling charge the vendor agreement doesn't authorize, or one that differs from the agreed terms, and AP struck it. The classic case: the agreement states handling is included in the item cost, and your billing system tacks a handling fee on anyway. The deduction equals exactly the charge removed. The problem is rarely a person deciding to overbill; it's a fee line hard-coded into an invoice template or ERP pricing procedure that nobody reconciled against the Walmart agreement.

Quick answer: Walmart Chargeback Code 60 is applied when a handling charge appears on an invoice without authorization or differs from the agreed terms — for example, a handling fee billed although the agreement says handling is included. Walmart removes the charge, deducting its exact amount. Prevention means billing only explicitly agreed fees.

---

Deep Dive: How a Fee Nobody Approved Gets on the Invoice

No supplier decides to bill Walmart an unauthorized fee. Code 60 happens because invoices are assembled by systems, and systems bill what they're configured to bill — for every customer, unless told otherwise.

On the EDI 810, charges ride the same allowance/charge (SAC) segments that discounts do, just signed the other way. A handling fee your ERP applies as a default surcharge lands in the 810 as a charge segment. Walmart's AP match then asks one question: does the agreement authorize this charge at this amount? Three outcomes:

Invoice charge	Vendor agreement says	Result
Handling fee billed	Handling included in item cost	Code 60 — charge removed
Handling fee billed at $X	Handling agreed at less than $X	Code 60 — the difference (or the charge) removed
Handling fee billed at agreed rate	Handling agreed at that rate	Paid

The pattern to internalize: Walmart pays the contract, not the invoice. Any line item the agreement doesn't explicitly support is a deduction waiting to be keyed — and unlike shortage codes, there's no evidence you can gather later. The agreement either authorizes the fee or it doesn't.

---

Business & Financial Impact

• Deduction = the unauthorized handling charge, exactly. No penalty multiplier in the record — but no payment either.
• Phantom revenue: the fee sat in your receivables until the deduction landed. Recurring Code 60 means your revenue forecast systematically overstates what Walmart will actually pay.
• Reconciliation drag: each removed charge is a line your finance team must research before writing off — labor spent confirming you billed something you shouldn't have.
• Relationship signal: a supplier who repeatedly bills unagreed fees looks, from AP's side, careless at best. Clean invoices are cheap credibility.

---

Root Causes (Ranked)

1. A handling fee added despite an "included" agreement — the agreement bundles handling into item cost; billing charges it separately anyway.
2. The handling charge differs from agreed terms — a fee exists in the deal, but the invoice bills the wrong rate or basis.
3. A fee applied without approval — default ERP surcharges (handling, fuel, processing) applied account-wide, never carved out for Walmart.
4. Stale fee configuration — terms renegotiated, invoice templates not updated.
5. Manual invoice edits — a one-off fee typed onto an invoice outside the governed billing flow.

---

Step-by-Step Prevention Workflow

AGREEMENT REVIEW ──► FEE WHITELIST ──► ERP CONFIG ──► 810 FEE AUDIT ──► TRANSMIT
 (what's allowed?)   (per customer)   (defaults off)   (block rogue SAC)

1. Extract the fee terms from the Walmart vendor agreement. Is handling included? If a handling charge is allowed, at what rate and basis? Write it down as a whitelist.
2. Configure Walmart as an exception in the ERP. Account-wide default surcharges must not flow onto Walmart invoices.
3. Audit every 810 for charge segments before transmission. Any charge not on the whitelist blocks the invoice.
4. Kill manual fee edits. If a fee can be typed onto an invoice outside the governed flow, it eventually will be.
5. Re-check the whitelist at every agreement renewal. Terms change; templates don't update themselves.

---

The Dispute Path

1. Pull the deduction detail from the APDP in Retail Link: invoice, charge removed, amount.
2. Check the vendor agreement. Is the handling charge explicitly authorized, at that amount?
3. If authorized: file in APDP citing the agreement clause that permits the charge and its rate.
4. If not authorized: the deduction is valid. Remove the fee from the Walmart billing config so it stops recurring — that's the only "win" available.

---

Code 60 in the Unauthorized-Charge Family

Code	The story
60	A handling charge specifically — unauthorized or off-terms, removed
90	Any unapproved charge or surcharge on the invoice — removed
55	The mirror image: an agreed allowance you failed to apply
57	An agreed quantity discount you failed to apply

Related: Code 90 · Code 55 · Code 57

---

Supplier Checklist

• Walmart fee terms extracted from the vendor agreement into a whitelist
• Handling: confirmed included vs separately billable, and at what rate
• ERP default surcharges disabled for the Walmart account
• 810 charge segments audited against the whitelist before transmission
• Manual fee edits blocked outside the governed billing flow
• Weekly: Code 60 deductions reconciled — config fixed or APDP dispute filed

---

FAQs

What is Walmart chargeback Code 60? A deduction applied when a handling charge on the invoice is not authorized or differs from the agreed terms — for example, a handling fee billed although the agreement states handling is included. Walmart removes the charge.

How much does Code 60 cost? The deduction equals the unauthorized handling charge that was removed. The compounding cost is phantom receivables and the reconciliation labor on every removed line.

Can I dispute a Code 60 deduction? Yes, through the APDP in Retail Link — but only if the vendor agreement explicitly authorizes the handling charge at the billed amount. Cite the clause. If it doesn't, the deduction is valid.

How is Code 60 different from Code 90? Code 90 covers unapproved charges generally — any fee or surcharge Walmart didn't agree to. Code 60 is the handling-charge case specifically: a handling fee that's unauthorized or differs from the agreed terms.

Why does my system keep adding a handling fee for Walmart? Usually an account-wide default: a surcharge configured globally in the ERP or invoice template that was never carved out for customers whose agreements bundle handling into item cost.

What single habit prevents the most Code 60 pain? Maintain a per-customer fee whitelist from the vendor agreement and validate every 810's charge segments against it before transmission.

---