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
- None included
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
- 00400
- Standard Issued as ANSI X12.5-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
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
MAXIMUM TWELVE M390 CARD NUMBERS ON A MANIFEST
- M380
- Initial/spot purchase
- M381
- Raw Materials
- M382
- Steel
- M390
- North American parts
- M391
- Supplemental
- M394
- Supply parts
- M395
- Transportation
- M621
- Tier 1 of direct supply
- M622
- Tier 2 of direct supply
- M640
- Office supplies
- MA02
- Returns
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
- EA
- Each
- PC
- Piece
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
- QT
- Quoted
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.
- PN
- Company Part Number
Identifying number for a product or service
TMM part # and color code
'YN' PART NUMBERS ARE TEN (10) DIGITS & DO NOT HAVE A TWO
(2) DIGIT COLOR CODE. THIS IS FOR RAW MATERIAL (M381)
PART NUMBERS THAT START WITH A 7 ARE BROADCAST (NO
ORDER VIA EDI)
SUPPLEMENTAL MANIFESTS START WITH A 52 ( NO ORDER VIA EDI )
TRIAL ORDERS START WITH A 1
THE IT107 FIELD (PART NUMBER) SHOULD NOT INCLUDE ANY DASHES OR ANY OTHER SPECIAL CHARACTERS.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PK
- Packaging Drawing
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- ZZ
- Mutually Defined
Identifying number for a product or service
DATA ELEMENT IS MANDATORY FOR THE FOLLOWING CARD NUMBERS:
M390, M391,M380,M381, & M382
DATA ELEMENT IS OMITTED FOR THE FOLLOWING CARD NUMBERS:
M621, M622, M640, ,M394, M395, & MA02
IF THE CARD CODE IS A M621, M622, M640, M395, OR MA02, DO NOT SEND A NEGATIVE PRICE, JUST THE POSITIVE PRICE QUOTED.
Reference Identification
To specify identifying information
1 THIS FIELD IS MANDATORY FOR ALL CARD CODES
(EVERY GROUP OF IT101).
2. Must have at least 1 occurrence of REF01 with value of MK
3. If REF01 is MK, REF02 will be the 8 character Manifest
Number. If REF01 is IK, REF02 will be the Suppliers Invoice Number – this is optional.
Code qualifying the Reference Identification
- IK
- Invoice Number
- MK
- Manifest Key Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time Reference
To specify pertinent dates and times
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
TDS01 is the total amount of invoice (including charges, less
allowances) before terms discount (if discount is applicable).
Monetary amount
- TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
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
Number of line items (IT1 segments)
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
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.