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
00*
*
00*
*
XX*
XXXXXXXXXXXXXXX*
XX*
XXXXXXXXXXXXXXX*
250328*
1908*
U*
00401*
000000000*
X*
X*
>~
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
IN*
XX*
XXXX*
20250328*
1734*
000*
X*
004010~
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
810*
0001~
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
Example: BIG20130812918700792013080820345389****00
20250121*
XXX*
20250123*
XXXXXX*
XXXXXX***
00~
Date expressed as CCYYMMDD
- BIG01 is the invoice issue date.
Date expressed as CCYYMMDD
- BIG03 is the date assigned by the purchaser to purchase order.
850 Source Fields: BEG-05
Identifying number for Purchase Order assigned by the orderer/purchaser
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
Name
To identify a party by type of organization, name, and code
Examples:
N1VNVendor Name9212345
N1VNAmrep Logistics & Program Managemen92868
VN*
XXXXX*
92*
XX~
Code identifying an organizational entity, a physical location, property or an individual
- VN
- Vendor
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.
Subaru’s Vendor Code for the Trading Partner - refer to the vendor - specific configuration information - From 850 N104 VN record.
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
Examples:
IT11500EA0.22PO20371234VN308BPSOA427V0400
IT11.0500EA*0.22PO20371234VN308BPSOA427V0400
IT111EA201.84**PO20345389VN00001BPSOA748V0100
XXX*
00*
EA*
0**
PO*
XXXX*
VN*
XXXX*
BP*
X~
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
Purchase Order Line Number - From PO1-01 (Integer or Real value - decimal optional Ex: 1 or 1.0)
Number of units invoiced (supplier units)
From 850 PO102 Include decimal point and digits if needed. Ex: 5 pieces: enter 5, 153.7 gallons: enter 153.7.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Price per unit of product, service, commodity, etc.
From 850 PO1-04, Explicit decimal point and cents are optional. Ex: $5.00 - enter 5 or 5.0 or 5.00, $242.37: enter 242.37, $175.50: enter 175.5 or 175.50.
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.
- PO
- Purchase Order Number
Identifying number for a product or service
From 850 BEG-03
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VN
- Vendor's (Seller's) Item Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
Examples:
TDS5000
TDS20184
00000000000000~
Monetary amount
- TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
Monetary Amount - sum of extended line amounts for Invoice - from IT1-02 * IT1-04, 2 implied decimal places. Ex: $13518.17: enter 1351817, $2321.00: enter 23210.
Invoice Shipment Summary
To specify summary details of total items shipped in terms of quantity, weight, and volume
Example: ISS1EA
0*
EA~
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
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.
Example: CTT*1
0000~
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)
000000*
0001~
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
000*
000000~
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
00*
000000000~
Sample 1
GS*IN*SENDERGS*RECEIVERGS*20250123*035237*1*X*004010~
BIG*20130812*91870079*20130808*20345389****00~
N1*VN*Amrep Logistics & Program Managemen*92*868~
IT1*1*1*EA*201.84**PO*20345389*VN*00001*BP*SOA748V0100~
TDS*20184~
ISS*1*EA~
CTT*1~
GE*1*1~
IEA*1*000000001~
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.