Zulily
/
Invoice
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Zulily. Contact Zulily for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Zulily logo

X12 810 Invoice

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the billing for goods and services provided.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • Zulily Invoice
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/zulily/invoice/01HBPJV67Z71P6ENVTRRWVFWH3
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BIG
020
Beginning Segment for Invoice
Max use 1
Required
CUR
040
Currency
Max use 1
Required
N1 Loop Bill To Party
Party to receive commercial invoice remittance
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

ZZ
Mutually Defined
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

>
Component Element Separator

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

IN
Invoice Information (810,819)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code used in conjunction with Data Element 480 to identify the issuer of the standard

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
810
Invoice
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BIG
020
Heading > BIG

Beginning Segment for Invoice

RequiredMax use 1

To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates

Example
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BIG01 is the invoice issue date.
Usage notes

INVOICE DATE
YYYYMMDD

BIG-02
76
Invoice Number
Required
String (AN)
Min 1Max 22

Identifying number assigned by issuer

Usage notes

VENDOR INVOICE NUMBER
Note: if you are currently enrolled in the Zulily Enhanced Payment
Visibility program, this value will be returned to you on payment
remittances.

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BIG03 is the date assigned by the purchaser to purchase order.
Usage notes

PO DATE - sent in 850-PO message
YYYYMMDD

BIG-04
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

ZULILY PO NUMBER
Note: Use value provided in BEG03 of EDI 850s
All Zulily pruchase order IDs are a 12-13 character string.
All POs requiring a shipment begin with "P0"
ZPS Invoice POs not requiring shipments begin with "45" (Triple Z vendors ONLY)

CUR
040
Heading > CUR

Currency

RequiredMax use 1

To specify the currency (dollars, pounds, francs, etc.) used in a transaction

Example
CUR-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

SE
Selling Party
CUR-02
100
Currency Code
Required
Identifier (ID)
Min 3Max 3

Code (Standard ISO) for country in whose currency the charges are specified

Usage notes

Accepted currency codes are "USD" and "CAD"

N1 Loop Bill To Party
RequiredMax 1
Usage notes

Bill To Loop

Variants (all may be used)
N1 Loop Ship ToParty to receive commercial invoice remittance
N1
070
Heading > N1 Loop Bill To Party > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

BT
Bill-to-Party
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

"Zulily LLC." as default Bill To name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Usage notes

Bill To code will always be code "0000" for Zulily Corporate for FC
shipments
Zulily, Inc - HQ = 0000

N1 Loop Bill To Party end
N1 Loop Ship To
RequiredMax 1
Usage notes

Ship To Loop

N1
070
Heading > N1 Loop Ship To > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

ST
Ship To
Required
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Usage notes

Please reference the ZULILY FC Adress List included in this onboarding
package

N1 Loop Ship To end
N1 Party to receive commercial invoice remittance
OptionalMax 1
Usage notes

Remit To Loop
ONLY USED for Third Party Billing Must Have Third Party Billing information on file with ZULILY AP team Or Invoice will fail translation

Variants (all may be used)
N1 Loop Bill To PartyN1 Loop Ship To
N1
070
Heading > Party to receive commercial invoice remittance > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

RE
Party to receive commercial invoice remittance
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes

Include name of 3rd party remittance service provider
DO NOT INCLUDE SHIPPER COMPANY NAME WHERE THERE IS NO
3RD PARTY FACTOR

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Usage notes

Reference "Zulily Invoicing Party Codes" pdf for full list of accepted factor IDs.

N1 Party to receive commercial invoice remittance end
Heading end

Detail

IT1 Loop
RequiredMax 200000
IT1
010
Detail > IT1 Loop > IT1

Baseline Item Data (Invoice)

RequiredMax use 1

To specify the basic and most frequently used line item data for the invoice and related transactions

Usage notes

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.

Example
If either Product/Service ID Qualifier (IT1-06) or Product/Service ID (IT1-07) is present, then the other is required
If either Product/Service ID Qualifier (IT1-08) or Product/Service ID (IT1-09) is present, then the other is required
If either Product/Service ID Qualifier (IT1-10) or Product/Service ID (IT1-11) is present, then the other is required
If either Product/Service ID Qualifier (IT1-12) or Product/Service ID (IT1-13) is present, then the other is required
IT1-01
350
Assigned Identification
Required
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • IT101 is the purchase order line item identification.
Usage notes

Line counter for invoice message detail. Recommended to match the
purchase order line counter sent by Zulily in the corresponding 850
message. Must be a unique number related to this line item.

IT1-02
358
Quantity Invoiced
Required
Decimal number (R)
Min 1Max 10

Number of units invoiced (supplier units)

Usage notes

This field will be the number of units related to this
invoice. Quantity must be greater than zero (0). Must reflect the quanitity
received at Zulily FC

IT1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

Usage notes

Currently we only support 'EA' as a unit of measure

EA
Each
IT1-04
212
Unit Price
Required
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

Usage notes

This field will be the cost of the item per unit.

IT1-06
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

  • IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
EN
European Article Number (EAN) (2-5-5-1)
GS
General Specification Number
IN
Buyer's Item Number
SK
Stock Keeping Unit (SKU)
UP
U.P.C. Consumer Package Code (1-5-5-1)
IT1-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

IT1-08
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

IT1-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

IT1-10
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

IT1-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

IT1-12
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

IT1-13
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

IT1 Loop end
Detail end

Summary

TDS
010
Summary > TDS

Total Monetary Value Summary

RequiredMax use 1

To specify the total invoice discounts and amounts

Example
TDS-01
610
Amount
Required
Numeric (N2)
Min 1Max 15

Monetary amount

  • TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
Usage notes

This field will be the cost of the item per unit. Two
decimal places are assumed.
The value 40775 would represent $407.75

CTT
070
Summary > CTT

Transaction Totals

RequiredMax use 1

To transmit a hash total for a specific element in the transaction set

  • Number of line items (CTT01) is the accumulation of the number of IT1 segments.
    If used, hash total (CTT02) is the sum of the value of quantities invoiced (IT102) for each IT1 segment.
Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

Usage notes

This field will contain the sum of the line items in this invoice (sum of all
IT101).

CTT-02
347
Hash Total
Required
Decimal number (R)
Min 1Max 10

Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.

## Example:
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.

1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.

Usage notes

This field will contain the total number of items being invoiced (sum of all
IT102).

SE
080
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

Zulily Invoice

ISA*00* *00* *01*VENDOR *ZZ*ZVDXPROD *201214*1035*U*00401*000000086*0*P*>~
GS*IN*VENDOR*ZVDXPROD*20201214*1035*86*X*004010~
ST*810*0001~
BIG*20230322*14095248*20230317*P000GAG6OS12V~
CUR*SE*USD~
N1*BT*ZULILY INC*92*0000~
N1*ST*Zulily LLC - NV*92*0008~
IT1*00001*1*EA*22.00**UP*825076667335***PO*P000GAG6OS12V~
IT1*00002*1*EA*20.00**UP*825076666345***PO*P000GAG6OS12V~
IT1*00004*1*EA*25.00**UP*825076703323***PO*P000GAG6OS12V~
IT1*00005*1*EA*20.00**UP*825076332561***PO*P000GAG6OS12V~
IT1*00006*1*EA*25.00**UP*825076726612***PO*P000GAG6OS12V~
IT1*00007*1*EA*25.00**UP*825076728982***PO*P000GAG6OS12V~
IT1*00008*1*EA*20.00**UP*825076666321***PO*P000GAG6OS12V~
IT1*00009*1*EA*22.00**UP*825076667311***PO*P000GAG6OS12V~
IT1*00011*1*EA*25.00**UP*825076679369***PO*P000GAG6OS12V~
IT1*00012*1*EA*25.00**UP*825076703170***PO*P000GAG6OS12V~
IT1*00013*1*EA*20.00**UP*825076676696***PO*P000GAG6OS12V~
IT1*00014*1*EA*25.00**UP*825076703309***PO*P000GAG6OS12V~
IT1*00015*1*EA*20.00**UP*825076635433***PO*P000GAG6OS12V~
IT1*00016*1*EA*20.00**UP*825076676504***PO*P000GAG6OS12V~
TDS*31400~
CTT*14*14~
SE*22*0001~
GE*1*86~
IEA*1*000000086~

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.