Here's the bottom line: when an EDI 810 invoice lands in a retailer's exception queue, the root cause is usually not in the finance department. It is in the warehouse. Whether the invoice was generated from the ship confirmation or copied from the purchase order decides whether the money arrives in 30 days or drags past 75. I have seen this exact failure three times, and all three followed the same script: the warehouse shipped correctly, the paperwork moved correctly, and the invoice still pulled its numbers from the wrong place.
September 2024, a 3PL warehouse in Los Angeles shipping home goods for a client to a national retail chain. The 850 purchase order said 1,200 cases. Two pallets turned up damaged during picking, so the crew shipped 1,176. The 856 advance ship notice went out with the real shipped quantity. The invoice went out with 1,200. The retailer's system compared the three documents, the quantities did not tie, and the whole invoice dropped into the exception queue. The client's receivable sat an extra 40-plus days while finance chased the warehouse and the warehouse waved the signed ship confirmation. Nobody was lying. The invoice had simply taken its quantity from the order instead of the ship confirmation. A credit memo eventually freed the money, six weeks later.
The case shows what an EDI 810 invoice actually is: a claim built on three other documents. The 850 says what was bought and at what price. The 856 says what actually shipped. The receiving record says what the other side took in. When the three agree, the money moves. The X12 structure follows the same logic: the BIG segment carries the invoice number, invoice date, and PO number; the IT1 loop carries shipped quantity and price line by line; the TDS segment carries the total. If any line disagrees, no human needs to read it — the buyer's system parks it for manual handling.
EDI 810 Invoice Breakpoint One: Quantity Must Follow the Ship Confirmation
Quantity is the most common breakpoint and the one the warehouse can prevent most reliably. Damage, short picks, repacks, split pallets — shipped quantities differ from ordered quantities all the time. The guardrail is a single rule: invoice lines take their numbers from the ship confirmation. Whatever the confirmation says shipped is what the IT1 line says. Partial shipments get partial invoices; never bill the unshipped balance to round out the order. One more detail: units of measure. The order prices by the case, the warehouse ships by the each, and one wrong conversion breaks every line. On the night before go-live, we always walk three historical orders line by line to check unit conversions. That step is not optional.
EDI 810 Invoice Breakpoint Two: Price, Tax, and Surcharges
Price breaks usually do not come from the warehouse typing a wrong number. They come from the wrong price list version. In March 2025, a consumer electronics client repriced 40 SKUs at once. The old price list stayed live in the system, and the first three invoices after the change went out at the old prices. Two of the three hit the exception queue, and the client's finance team spent two weeks unwinding the deductions line by line. The warehouse-side fix is low-tech and it works: print the price list version on the ship confirmation, and finance checks that version before issuing the invoice. Taxes and surcharges follow the same rule. Freight, fuel surcharges, and handling fees belong in the allowance and charge segments of the 810, with amounts and reasons spelled out. Bury a fee inside the unit price and the line math never reconciles again.
Run the numbers and the stakes get clear. Illustrative example: a shipment of 10,000 units with a one-cent price difference is a $100 short-pay on paper. That looks small until the retailer's deduction process starts, and finance, customer service, and the warehouse spend days going back and forth — labor that costs far more than $100. The expensive part is the payment terms: an invoice in the exception queue routinely stretches 30-day terms toward 75, and the cash-flow cost never shows up on the invoice itself.
| Breakpoint | Exception signal | Warehouse guardrail | Evidence for disputes | | Quantity | Invoiced qty above shipped qty | Invoice lines take ship confirmation qty | Ship confirmation | | Price | Unit price differs from the 850 | Price list version printed on confirmation | Price list version record | | Tax and surcharges | Charges with no basis | Charges listed separately in charge segments | Charge detail | | Dates and lots | Receiving date does not match | Scans transmitted live, receipts photographed | Scan records, signed receipts |
Receiving Dates and Lot Numbers: The Signature Is the Evidence
The third breakpoint is the receiving date, the fourth is the lot. If the retailer's receiving scan date does not line up with the ship date on the EDI 810 invoice, the system starts doubting the shipment happened as agreed. Lot numbers and expiry dates work the same way for food and personal care: the receiver inspects by lot, and an invoice line with no lot information leaves a return dispute with nothing to stand on. What the warehouse can do is concrete: transmit receiving scans in real time instead of batching them at end of shift; photograph the signed delivery receipt with a timestamp; carry the lot number from the receiving scan straight into the ship confirmation instead of copying it by hand.
Here is the counterintuitive part: a 997 with an A does not mean the invoice is fine. The 997 is a functional acknowledgment — it says the file arrived and parsed. A means accepted, E means accepted with errors, R means rejected. It says nothing about whether the business content is right. Plenty of teams see a 997 A and assume the money is safe, then discover six weeks later that the invoice has been sitting in an exception queue. The real signal that money is coming is the 820 payment advice, or the cash hitting the account. A 997 proves the file arrived. It never proves the money will.
When a deduction dispute arrives, the warehouse defends itself with three things: the ship confirmation, the receiving scan record, and the signed delivery photo. With all three, a dispute letter takes half a day to write. Missing one, and the team spends a month digging through chat logs and paper files. In my projects, clients with complete evidence win deduction appeals far more often. The reason is simple: the buyer's payables system trusts documents, not verbal explanations.
One thing you can do tomorrow: add three lines to the ship confirmation — actual shipped quantity, price list version, and receiving lot. Finance checks those three lines before issuing the invoice, every time. Do not wait until the invoice is already stuck in an exception queue to go hunting for evidence. By then, whatever you find arrives too late.
By Lin Xiao, WMS Implementation Consultant







