X12 810 Invoice
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.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
- ZZ
- Mutually Defined
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
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
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
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- IN
- Invoice Information (810,819)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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)
Assigned number originated and maintained by the sender
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
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
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Invoice
To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates
Date expressed as CCYYMMDD
- BIG01 is the invoice issue date.
INVOICE DATE
YYYYMMDD
Identifying number assigned by issuer
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.
Date expressed as CCYYMMDD
- BIG03 is the date assigned by the purchaser to purchase order.
PO DATE - sent in 850-PO message
YYYYMMDD
Identifying number for Purchase Order assigned by the orderer/purchaser
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)
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Code identifying an organizational entity, a physical location, property or an individual
- SE
- Selling Party
Code (Standard ISO) for country in whose currency the charges are specified
Accepted currency codes are "USD" and "CAD"
Bill To Loop
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
Free-form name
"Zulily LLC." as default Bill To name
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
Bill To code will always be code "0000" for Zulily Corporate for FC
shipments
Zulily, Inc - HQ = 0000
Ship To Loop
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
Please reference the ZULILY FC Adress List included in this onboarding
package
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
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- RE
- Party to receive commercial invoice remittance
Free-form name
Include name of 3rd party remittance service provider
DO NOT INCLUDE SHIPPER COMPANY NAME WHERE THERE IS NO
3RD PARTY FACTOR
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
Reference "Zulily Invoicing Party Codes" pdf for full list of accepted factor IDs.
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
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.
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
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.
Number of units invoiced (supplier units)
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
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Currently we only support 'EA' as a unit of measure
- EA
- Each
Price per unit of product, service, commodity, etc.
This field will be the cost of the item per unit.
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)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
Monetary amount
- TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
This field will be the cost of the item per unit. Two
decimal places are assumed.
The value 40775 would represent $407.75
Transaction Totals
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.
Total number of line items in the transaction set
This field will contain the sum of the line items in this invoice (sum of all
IT101).
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.
-.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.
This field will contain the total number of items being invoiced (sum of all
IT102).
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Zulily Invoice
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.