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
BIG — Beginning Segment for Invoice
X12 BIG segment reference for EDI 810 invoices: invoice number, date, PO reference, and transaction purpose.
BIG segment facts
- BIG04 purchase order reference is the three-way match anchor between 850, 856, and 810 in retail programs.
- BIG02 invoice numbers must stay unique per trading partner to avoid duplicate payment or rejection loops.
- QuickBooks handoff flows use BIG02 and BIG01 as the primary invoice identity before line-level IT1 mapping.
What the BIG segment does
BIG opens an 810 invoice. It carries invoice number, invoice date, and the purchase order number used to match the original 850 and 856.
Loop: Once per 810
Common transaction sets: 810
Key elements
| Element | Name | Description |
|---|---|---|
| BIG01 | Invoice date | CCYYMMDD — drives payment terms and retailer accrual windows. |
| BIG02 | Invoice number | Must be unique per partner; duplicates trigger rejections. |
| BIG04 | Purchase order number | Must match the original 850 BEG03 for three-way match. |
Example BIG segment
BIG*20250609*INV-90012***PO-1042~
Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.
Related reference
FAQ
Frequently asked questions
Retailers require PO linkage for accrual and deduction matching; missing BIG04 is an automatic reject at several majors.
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.”