Lowe's Deduction Code PRC: Cost Difference on the Invoice

Executive Summary & Quick Answer

Executive summary: PRC is a pricing referee, and Lowe's item file is the rulebook. When the cost on your 810 invoice differs from the cost Lowe's has on file for that item, the invoice fails the match and generates a chargeback — roughly $50 per erroneous invoice or incorrect line item. The insidious part is repetition: a single stale price in your billing system doesn't produce one PRC, it produces one on every invoice until someone fixes the sync. Suppliers who bill from their internal catalog instead of the PO price are effectively running a PRC subscription. The cure is a sequencing rule: no invoice at a new price until Lowe's has acknowledged the cost change.

Quick answer: Lowe's Deduction Code PRC is a cost-difference deduction assessed when the invoiced cost differs from the cost Lowe's has on file for the item. The EDI 810 invoice must match the PO exactly; pricing discrepancies generate chargebacks of approximately $50 per erroneous invoice or incorrect line item.

---

Deep Dive: What Triggers Code PRC

PRC fires at the invoice-match step. Lowe's AP compares each line of your 810 against the cost it has on file — the price that flowed onto the 850 purchase order from Lowe's item file. Any line where your unit cost disagrees is flagged, and the invoice earns a deduction.

The core misunderstanding that drives PRC: suppliers treat their internal price list as the source of truth. In Lowe's AP process, it isn't. The cost on file wins, whether or not your list price changed last quarter.

The price-authority chain:

LOWE'S ITEM FILE ──► 850 PO (unit cost) ──► YOUR ORDER ENTRY ──► 810 INVOICE (unit cost)
        │                                                              │
        └────────────── PRC = these two disagree ─────────────────────┘

  Your internal catalog ──✗──► should never touch the 810 directly

EDI segment insight. The two fields that must be identical:

Document	Segment	Field
850 PO	PO1	Unit price Lowe's is committing to pay
810 Invoice	IT1	Unit price you're billing

A three-way match (850 price → 856 items → 810 price) run before the 810 transmits catches PRC at zero cost. The same mismatch caught by Lowe's AP costs ~$50 and dispute labor.

The DB record also flags allowances: an allowance that appears on the PO but is missing or unmatched on the invoice changes the net cost — and lands in the same bucket.

---

Business & Financial Impact

Per the DB record: approximately $50 per erroneous invoice or incorrect line item.

• It multiplies silently. One stale SKU price × weekly invoicing = ~$200/month from a single row in a price table, until the sync is fixed.
• It's per line, not per event. An invoice with four mispriced lines is four errors, not one.
• Administrative drag: each PRC forces a research-and-correct cycle in AR — often costing more in labor than the $50 itself.
• Relationship signal: chronic invoice mismatches mark a supplier as high-touch for Lowe's AP, which is not where you want to sit ahead of line reviews.

---

Root Causes (Ranked)

1. Price changes not loaded into Lowe's item file before invoicing — you raised prices internally, billed the new number, and Lowe's file still says the old one.
2. Invoice generated from an internal price list instead of the PO price — the structural version of cause #1; every invoice is a coin flip.
3. Missing or unmatched allowances on the invoice — the gross price matches but the net doesn't, because an allowance was dropped or double-entered.
4. Manual invoice keying — rekeyed prices drift; a transposed digit is a PRC.
5. No pre-transmission 810 validation — mismatches that a simple PO-price comparison would catch go out the door unchecked.

---

Step-by-Step Prevention Workflow

1. Price the 810 from the PO — mechanically. Configure order-to-cash so IT1 unit prices are copied from the 850, never looked up from the internal catalog.
2. Sequence price changes. New price → submit to Lowe's → wait for acknowledgment that the item file is updated → only then bill at the new price. Never invoice ahead of the file.
3. Three-way match before transmission. Validate invoice against PO and ASN (price, item, quantity) as a hard gate on 810 release.
4. Reconcile allowances line by line. Every allowance on the PO must appear once — exactly once — on the invoice.
5. Audit PRC weekly by SKU. Repeated PRCs on one SKU means a price-sync failure, not a random error; fix the row, not the symptom.

PRICE CHANGE ──► SUBMIT TO LOWE'S ──► CONFIRMED IN ITEM FILE ──► BILL NEW PRICE
                        │
              (billing early = PRC on every invoice until confirmed)

---

Code PRC vs Related Lowe's Codes

Code	Category	The story
PRC	AP / Pricing	Invoiced cost ≠ cost on Lowe's file — the price itself is wrong
PMT	AP / Allowances	Price fine; the discount taken at payment differs from the invoice
DT	AP / Shortage	Price fine; fewer units received than billed

Related: Code PMT · Code DT

---

Supplier Checklist

• 810 unit prices sourced from the 850 PO, not the internal catalog
• Price changes confirmed in Lowe's item file before billing at new prices
• Allowances reconciled PO-to-invoice on every order
• Pre-transmission three-way match (810 vs 850 vs 856) as a hard gate
• Weekly: PRC deductions grouped by SKU — fix repeat offenders at the source
• Price-change log kept with submission and acknowledgment dates for disputes

---

FAQs

What is Lowe's Deduction Code PRC? A cost-difference deduction assessed when the invoiced cost differs from the cost Lowe's has on file for the item. The 810 invoice must match the PO exactly; discrepancies run approximately $50 per erroneous invoice or incorrect line item.

Why do I keep getting PRC on the same SKU? Almost always a price-sync failure: your billing system carries a price Lowe's item file doesn't. Every invoice for that SKU will mismatch until the file and your system agree.

Can I bill at my new price as soon as I announce a price change? No. Confirm the cost change is acknowledged by Lowe's before billing at new prices. Invoicing ahead of the item file generates a PRC on every affected invoice.

How do allowances cause PRC? An allowance that's on the PO but missing or unmatched on the invoice changes the net cost, so the invoice no longer matches what Lowe's expects to pay.

How is PRC different from PMT? PRC is a mismatch in the invoiced item cost. PMT is a mismatch in the discount taken at payment versus what the invoice shows. One is a price error, the other a terms/allowance error.

---