{
  "id": 11931621,
  "title": "The EDI 810, Decoded: What an Invoice Actually Looks Like on the Wire",
  "url": "https://urgent.news/2026/10/04/the-edi-810-decoded-what-an-invoice-actually-looks-like-on-the-wire",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-04T13:26:58.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/challan116ux/the-edi-810-decoded-what-an-invoice-actually-looks-like-on-the-wire-31hb"
  },
  "original_language": "en",
  "account": "Every EDI series eventually delves into the invoice, specifically the 810, as this segment transforms integrations from an IT project to a financial one. A typo in an invoice leads to disputes, delayed payments, and potential chargebacks. Here's a breakdown of the 810 structure, segment by segment, to understand where integrations commonly falter.\n\nThe 810, or Invoice, serves as the counterpart to the 850 (Purchase Order) and 856 (Advance Ship Notice), forming the order-to-cash sequence in retail EDI. The header segment, ST*810*0001~, contains essential data: invoice date, invoice number, purchase order date and number. Incorrect PO numbers can disrupt the three-way matching process, causing invoices to pile up in queues, aging beyond their discount window. The payment terms, including discount percentage and days, are housed in the ITD segment, a critical yet often overlooked area, especially for small suppliers who may hard-code outdated spreadsheets.\n\nThe IT1 loop, where line items reside, is where most invoice issues arise. IT1*1*24*EA*18.50**UP*012345678905*VN*ACME-WIDGET-BLU specifies item details: item number, UPC, vendor number, item description, and unit price. The buyer's AP system matches these details against their item master, and any mismatch silently forces manual review. The TDS segment, representing the invoice total in implied-decimal cents, is a common source of error: misinterpreting this field can lead to significant discrepancies, such as a $440,000 invoice error, which can be costly and difficult to resolve. Additional segments like SAC handle allowances and charges, such as freight or promotional allowances, which, if omitted, result in buyers deducting these amounts, leading to short-payments and challenging reconciliations.\n\nBuyers have started employing automatic three-way (or four-way) matching, comparing the 810 against the original 850, the 856 ship quantities, and physical receiving records. Even minor price or quantity variances can lead to substantial short-payments, straining supplier-customer relationships. The lesson here extends beyond EDI: invoices must accurately reflect three key documents—orders, shipments, and receipts. Integrations that generate invoices solely from orders, without considering actual shipments, often encounter matching exceptions. To mitigate these, generating invoices from shipment data, pricing from orders, and conducting pre-send validations that mirror the buyer's matching rules are crucial steps. Establishing these practices not only streamlines invoice processing but also reduces the likelihood of monthly reconciliation projects.",
  "summary": "Every EDI series I write eventually gets to the invoice, because the 810 is where integrations stop being an IT project and start being a money project. A purchase order with a typo is an inconvenience. An invoice with a typo is a dispute, a delayed payment, and — if it drags past the retailer's payment window — a chargeback conversation nobody wants. Here's what an 810 actually looks like,…",
  "key_points": [
    "The 810 invoice links to 850 PO and 856 ASN, forming order-to-cash sequence",
    "IT1 loop contains line item details, prone to matching issues",
    "TDS segment represents invoice total in implied-decimal cents, error-prone"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}