Kroger Deduction Code LC: List Cost Difference Explained

Executive Summary & Quick Answer

Executive summary: LC is Kroger's pricing referee: when the unit price on your 810 invoice differs from the list cost Kroger has on file, the difference is deducted from payment. The deduction is small per unit and enormous in aggregate — a two-cent gap across a high-velocity grocery item silently drains thousands per quarter. Almost every LC traces to the same failure: a price change that existed in one system but not the other. You raised prices and Kroger's file didn't update; or a promotion lowered the PO price and your billing system never heard. The prevention is a handshake: never invoice at a new price until Kroger has acknowledged it.

Quick answer: Kroger Deduction Code LC is assessed when the unit price on your invoice differs from the list cost Kroger has on file. Kroger deducts the difference between billed and expected cost per unit. Prevent it by confirming price changes are acknowledged before invoicing and syncing 810 prices to the PO.

---

Deep Dive: What Triggers Code LC

Every Kroger item you sell has two prices living in two systems: yours and theirs. The 850 PO carries the price Kroger expects to pay; your 810 invoice carries the price you expect to receive. When they disagree, Kroger's payables system doesn't negotiate — it pays its own number and deducts the difference as LC.

Where the mismatch is born:

Event	Your system	Kroger's file	Result at invoice time
Price increase, not yet loaded by Kroger	New price	Old price	You bill high → LC deducts the gap
Invoice from an outdated price list	Old price	New price	You bill wrong → LC corrects it
Promotion not reflected on the PO	Promo price expected	List price on PO	Billed vs expected diverge → LC

The EDI view makes the fix obvious:

price change agreed ──► Kroger loads it ──► 850 POs carry NEW price
                              │
        YOUR 810 must price from the PO price actually received
                              │
        810 price ≠ 850 price ──► flag BEFORE transmission, not after payment

The 850 is ground truth for what Kroger will pay today. An 810 priced from your internal list instead of the PO is a bet that both files agree — and LC is what you pay when the bet loses.

---

Business & Financial Impact

• Typical deduction: the price difference per unit billed (per the record). No flat fine — which is precisely why it hides.
• Volume is the multiplier: cents per unit across grocery-scale case volumes compounds into real money before anyone flags it, because no single deduction looks worth investigating.
• Every unit is affected, indefinitely: unlike a one-off shipping failure, an unresolved price mismatch deducts on every invoice until the two files agree.
• Research cost exceeds unit cost: reconciling many small LC lines consumes deduction-management hours out of proportion to each line's value.

---

Root Causes (Ranked)

1. A price change never communicated or loaded into Kroger's system — you invoice at the new price against a file still holding the old one.
2. Invoice generated from an outdated price list — your billing master lags the negotiated price.
3. Promotional pricing not reflected on the purchase order — deal windows and PO pricing out of sync.
4. 810 priced from the internal list instead of the PO — structurally guarantees that any file mismatch becomes a deduction.
5. No dated audit trail of price notifications — mismatches happen, but without dated records, even valid disputes can't be evidenced.

---

Step-by-Step Prevention Workflow

negotiate change ──► notify Kroger (dated) ──► WAIT for acknowledgment
                                                     │
                            only THEN invoice at the new price
                                                     │
      every 810: price vs 850 price ──► mismatch? HOLD + resolve before send

1. Treat price changes as a handshake, not an announcement. Confirm the change is acknowledged and loaded by Kroger before a single invoice carries the new price.
2. Sync the 810 price to the PO price. The 850 tells you what Kroger's file holds; invoice against it and any divergence surfaces as a pre-send flag instead of a deduction.
3. Flag mismatches before transmission. An 810 line priced differently from its 850 line should stop the invoice, route to a human, and get resolved while it's still an email rather than an LC.
4. Calendar promotional windows. Deal pricing needs start/end dates mirrored in both your billing logic and the PO flow.
5. Keep dated records of every price notification. When Kroger's file is the one that's wrong, your dispute rests on proving when the change was communicated.

Disputing an LC: the 180-day window applies, via the Kroger Supplier Hub. The winning evidence is a dated price-change notification (or agreement) predating the PO, showing your invoice price was the agreed price. Without dated records, the file mismatch defaults against you.

---

Code LC Among Kroger's Deduction Codes

Code	The story	Nature of the money
LC	Invoice price differs from Kroger's list cost	An error to prevent
CD	Cash discount taken per payment terms	A term to verify
WV	Vendor/ERP ID doesn't match Kroger's file	Master data to fix

LC and CD both shrink the remittance, but only one is a mistake: LC is a mismatch that shouldn't exist; CD is a contract term that should — at the right rate. Related: CD · WV

---

Supplier Checklist

• Price changes confirmed as acknowledged/loaded by Kroger before invoicing at the new price
• 810 unit prices sourced from the PO price, not the internal list
• Pre-transmission flag on any 810 line that diverges from its 850 line
• Promotional price windows mirrored between billing logic and PO flow
• Dated archive of all price-change notifications and agreements
• Monthly LC review: recurring items escalated as file-sync issues, valid disputes filed within 180 days via Supplier Hub

---

FAQs

What is Kroger Deduction Code LC? A list cost difference deduction: the unit price on your invoice differs from the list cost Kroger has on file, and the difference between billed and expected cost is deducted.

How much does an LC deduction cost? The price difference per unit billed. Small per line, but it repeats on every invoice until the underlying price files agree.

What causes most LC deductions? Price changes that were never communicated to or loaded by Kroger, invoices generated from outdated price lists, and promotional pricing not reflected on the purchase order.

How do I dispute an LC deduction? Within the 180-day window via the Kroger Supplier Hub, with a dated price-change notification or agreement showing your invoiced price was the agreed price when the PO was cut.

What's the single best LC prevention habit? Never invoice at a new price until Kroger has acknowledged the change — and sync your 810 price to the PO price so mismatches surface before transmission.

---