810 Invoice
Zulily · X12 004010
Zulily’s published 810 specification, rendered as an interactive guide. Expand any segment to see its elements, data types, lengths and accepted codes — then validate your own document against it below.
Specification
10 of 10 segments
HEADING
ST
Transaction Set Header ST
pos 010
Optional
max —
BIG
Beginning Segment For Invoice BIG
pos 020
Required
max —
CUR
Currency CUR
pos 040
Required
max —
N1 LoopN1 Loop Bill To Partyvariant 1 of 3required
N1
Name N1
pos 070
Required
max —
N1 LoopParty to receive commercial invoice remittancevariant 2 of 3
N1
Name N1
pos 070
Required
max —
N1 LoopN1 Loop Ship Tovariant 3 of 3required
N1
Name N1
pos 070
Required
max —
DETAIL
IT1 Looprepeats 200000required
IT1
Baseline Item Data Invoice IT1
Item qualifiers may be listed in any order in the IT106, IT108, IT110, and IT112.
Minimum of UPC (or EAN) and IN product ID required to be reported in item data
For Triple Z Invoices GS ID provided in PO113 of EDI 850s is required to be returned.
pos 010
Required
max —
SUMMARY
TDS
Total Monetary Value Summary TDS
pos 010
Required
max —
CTT
Transaction Totals CTT
pos 070
Required
max —
SE
Transaction Set Trailer SE
pos 080
Optional
max —
Validate a 810
Paste or upload a document and check it against Zulily’s published rules — segment order and repetition, required elements, field lengths, data types and accepted codes. Nothing is stored.
Go live on Zulily’s 810 in days, not months
Weredi maps this guide to your ERP, runs the test cycle with Zulily, and keeps the spec current as it changes.