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
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
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.
Identifying number assigned by issuer
SYSCO Invoice Number (10 digits)
Identifying number for Purchase Order assigned by the orderer/purchaser
Customer PO Number (if available)
Name
To identify a party by type of organization, name, and code
This segment may be used or omitted.
Code identifying an organizational entity, a physical location, property or an individual
- RE
- Party to receive commercial invoice remittance
Code designating the system/method of code structure used for Identification Code (67)
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
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.
DUNS Number of SYSCO house.
Address Information
To specify the location of the named party
This segment may be used or omitted.
Geographic Location
To specify the geographic place of the named party
This segment may be used or omitted.
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Name
To identify a party by type of organization, name, and code
This segment may be used or omitted.
Identifies the concept/chain/unit the Catalog applies to
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
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.
DUNS Number of SYSCO house
Address Information
To specify the location of the named party
This segment may be used or omitted.
Geographic Location
To specify the geographic place of the named party
This segment may be used or omitted.
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
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)
- 91
- Assigned by Seller or Seller'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.
The SYSCO customer number - 6 digits (leading zeroes may appear).
Address Information
To specify the location of the named party
This segment may be used or omitted.
Geographic Location
To specify the geographic place of the named party
This segment may be used or omitted.
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Reference Identification
To specify identifying information
This segment may be used or omitted.
Code qualifying the Reference Identification
- CR
- Customer Reference Number
Date/Time Reference
To specify pertinent dates and times
This segment may be used or omitted.
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
This segment may be used or omitted.
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
PO line number.
Number of units invoiced (supplier units)
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CA
- Case
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
- UM
- Price per Unit of Measure
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.
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
Invoiced SUPC Number.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- OE
- Original Equipment Number
Identifying number for a product or service
Original ordered item.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VO
- Vendor's Order Number
Identifying number for a product or service
SYSCO Order Number (if available).
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IN
- Buyer's Item Number
Identifying number for a product or service
Customer Item Number (if available).
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BS
- Bill Subgroup Code
Quantity
To specify quantity information
- The QTY segment is used to specify a quantity of units which are expected as payments, e.g., trade-ins or returns.
This segment may be used or omitted.
Code specifying the type of quantity
- 01
- Discrete Quantity
Numeric value of quantity
Quantity Invoiced
Other taxes
To specify tax information
This segment may be used or omitted.
State and Local Sales Tax
To specify tax information
This segment may be used or omitted.
Pricing Information
To specify pricing information
This segment may be used or omitted.
Code identifying pricing specification
- INV
- Invoice Billing Price
Price per unit of product, service, commodity, etc.
- See Figures Appendix for an example detailing the use of CTP03 and CTP04.
- See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
Item Unit Price.
Numeric value of quantity
Quantity Invoiced.
Code indicating the type of price multiplier
- SEL
- Selling Multiplier
Value to be used as a multiplier to obtain a new value
- CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of .90 would be the factor if a 10% discount is given.
Always 1
Product/Item Description
To describe a product or process in coded or free-form format
This segment may be used or omitted.
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
Item Pack
To describe marking, packaging, loading, and unloading requirements
Code indicating the format of a description
- If PKG01 equals "F", then PKG05 is used. If PKG01 equals "S", then PKG04 is used. If PKG01 equals "X", then both PKG04 and PKG05 are used.
- F
- Free-form
Code specifying the marking, packaging, loading and related characteristics being described
- PK
- Packing
A code from an industry code list which provides specific data about the marking, packaging or loading and unloading of a product
- PKG04 should be used for industry-specific packaging description codes.
- PG
Item Size
To describe marking, packaging, loading, and unloading requirements
Code indicating the format of a description
- If PKG01 equals "F", then PKG05 is used. If PKG01 equals "S", then PKG04 is used. If PKG01 equals "X", then both PKG04 and PKG05 are used.
- F
- Free-form
Code specifying the marking, packaging, loading and related characteristics being described
- UP
- Unit Pack
A code from an industry code list which provides specific data about the marking, packaging or loading and unloading of a product
- PKG04 should be used for industry-specific packaging description codes.
- PG
Reference Identification
To specify identifying information
This segment may be used or omitted.
Code qualifying the Reference Identification
- OI
- Original Invoice Number
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
Other Taxes
To specify tax information
This segment may be used or omitted.
State and Local Sales Tax
To specify tax information
This segment may be used or omitted.
Carrier Detail
To specify transportation details for the transaction
This segment may be used or omitted.
Code specifying the method or type of transportation for the shipment
- M
- Motor (Common Carrier)
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.
This segment may be used or omitted.
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
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
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample
GS*IN*SYSCOXXX*RECEIVERID*20180726*1146*106258*X*004010~
ST*810*0001~
BIG*20180726*255004940*****DI~
N1*ST*CUSTOMER NAME*91*123456~
N3*123 STREET ADDRESS~
N4*CITY*ST*ZIPCODE~
N1*SF*SYSCO FOOD SERVICES*9*8355689650000~
N3*PO BOX 97054~
N4*KENT*WA*98064-975~
N1*RE*SYSCO FOOD SERVICES*9*8355689650000~
N3*PO BOX 97054~
N4*KENT*WA*98064-975~
DTM*003*20180726~
IT1**3*CA*26.55*UM*VN*7054694***OE*7054694*VO*00030839*IN*0000000~
QTY*01*3*CA~
TXI*LS*7.97~
CTP*DI*INV*26.55*3*CA*SEL*1*79.65~
PID*F****ITEM DESCRIPTION~
PKG*F*PK***1~
PKG*F*UP***500 CT~
TDS*8762~
TXI*LS*7.97~
CAD*M****UNKN~
CTT*1~
SE*24*0001~
GE*1*106258~
IEA*1*000159202~
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.