Operations teams
“A supplier operations team can see partner setup, validation, exceptions, and QuickBooks handoff in one workspace instead of chasing spreadsheets.”
X12 segment reference
IT1 — Baseline Item Data (Invoice)
X12 IT1 segment on EDI 810 invoices: quantity invoiced, unit price, product IDs, and PO line references for retail remittance matching.
IT1 segment facts
- IT1 invoiced quantity must reconcile with 856 shipped quantity and 850 ordered quantity for most retail three-way match programs.
- IT107 product ID qualifiers must match the retailer's item master — UPC padding errors are a common 810 rejection.
- QuickBooks EDI workflows map IT1 lines to invoice line items after operator review — see /solutions/quickbooks-edi.
What the IT1 segment does
IT1 describes each invoiced line on an 810 — quantity, unit of measure, unit price, and product identifiers. IT107 and IT113 tie lines back to the original PO and ASN for three-way match.
Loop: Per invoice line
Common transaction sets: 810
Key elements
| Element | Name | Description |
|---|---|---|
| IT102 | Quantity invoiced | Must not exceed shipped quantity per partner rules. |
| IT103 | Unit of measure | EA, CA, PK — must match PO and ASN UoM. |
| IT104 | Unit price | Disputes when price drifts from contracted PO price. |
| IT107 | Product ID qualifier | UP=UPC, VN=vendor SKU, IN=buyer item number. |
Example IT1 segment
IT1*1*24*EA*12.50**UP*012345678905*PO*PO-1042~
Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.
Common IT1 errors
- Invoiced qty greater than ASN qty
- UPC not on retailer item master
- PO line reference missing on IT1
Related reference
FAQ
Frequently asked questions
PO1 appears on 850 purchase orders; IT1 appears on 810 invoices with invoiced quantity and price.
Retail AP matches IT1 lines to ASN and PO — quantity or price drift triggers deduction notices.
Trust & proof
Built for SMB teams that need API-first EDI, healthcare diligence, and predictable pricing.
SignalEDI keeps the public promise consistent across every route: real-time processing, transparent monthly plans, no per-document fees, QuickBooks-friendly handoffs, and core healthcare X12 workflows on paid plans.
HIPAA-aware handlingBAA path documentedSecure API + webhooksNo per-document fees
Healthcare billing
“837, 835, and 270/271 workflows are explained in plain English, with HIPAA-aware handling and a documented BAA review path for diligence.”
Developer teams
“JSON/CSV in and X12 out, with API docs, webhooks, real-time status, and validation responses that make EDI feel like modern infrastructure.”