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
- 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
BIG200604249929293200604205000002341***DI
Date expressed as CCYYMMDD
- BIG01 is the invoice issue date.
Invoice Date
Date expressed as CCYYMMDD
- BIG03 is the date assigned by the purchaser to purchase order.
Insight Purchase Order Date
Identifying number for Purchase Order assigned by the orderer/purchaser
Insight Purchase Order Number
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
NTEINVTHIS IS WHERE INVOICE NOTES WOULD GO
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
CURBYUSD
CURBYCAD
Reference Identification
To specify identifying information
If the document is a credit memo (BIG07 = CR), the REF01 must contain one of the following qualifiers: 8V, BD, PI or RZ. These qualifiers are mutually exclusive.
REFBD82919282
Code qualifying the Reference Identification
- 8V
- Credit Reference
This is used for miscellaneous credit memos for items other than returns, bids and price protection.
- BD
- Bid Number
This is used for rebate credit memos. It is the bid number that is issued to Insight by the vendor.
- PI
- Price List Change or Issue Number
This is the price protection reference issued to Insight by the vendor.
- RZ
- Returned Goods Authorization Number
This is the return authorization number issued to Insight by the vendor.
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
IT1000101EA29.99CPBP1000001VP*452930
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
This is the line item number from the original Purchase Order. This number must match the line item number on the original purchase order. This line item number should only appear once on the invoice.
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
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
- CP
- Current Price (Subject to Change)
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.
- BP
- Buyer's Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's (Seller's) Part Number
Tax Information
To specify tax information
The detail TXI segment should only be used by our APAC partners. Any taxes that are sent in this segment should be included in the TDS:01 invoice total amount.
TXIPS1.85
TXIGS11.51
TXIZZ3.7
Code specifying the type of tax
- GS
- Goods and Services Tax
(GST) Goods and Services Sales Tax
- PS
- State or Provincial Tax on Services
(PST) Provincial Sales Tax
- ZZ
- Mutually Defined
Any additional taxes
Monetary amount
- TXI02 is the monetary amount of the tax.
Reference Identification
To specify identifying information
REFIV788392
Code qualifying the Reference Identification
- DO
- Delivery Order Number
Vendor's delivery number. This is the BSN02 number from the BSN02.
This number is required on all invoices with serialized product. - IV
- Seller's Invoice Number
End-User Invoice Number. This is sent on rebate credit requests.
- OI
- Original Invoice Number
This is used for credit memos or rebills. It is the original invoice assigned to Insight by the vendor.
- PO
- Purchase Order Number
Insight Purchase Order Number.
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
TDS*2999
Monetary amount
- TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
For our US vendors taxes SHOULD NOT be included in the TDS total. For our CANADA and APAC vendors taxes SHOULD BE included in the TDS total.
Tax Information
To specify tax information
The summary TXI segment should only be used by our CAN/APAC partners. Any taxes that are sent in this segment should be included in the TDS:01 invoice total amount.
APAC
TXIGS1.85
TXIVA25.10
CAN
TXIGS1.85
TXISP3.7
TXITX11.51
Code specifying the type of tax
- GS
- Goods and Services Tax
GST sales tax
- SP
- State/Provincial Tax
Provincial Sales Tax
- TX
- All Taxes
Harmonized Sales Tax
- VA
- Value Added Tax
Value Added Tax
Monetary amount
- TXI02 is the monetary amount of the tax.
Service, Promotion, Allowance, or Charge Information
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
SACCD2405*06FREIGHT
Code which indicates an allowance or charge for the service specified
- If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
- A
- Allowance
- C
- Charge
- N
- No Allowance or Charge
Code identifying the service, promotion, allowance, or charge
- D240
- Freight
- G470
- Restocking Charge
Monetary amount
- SAC05 is the total amount for the service, promotion, allowance, or charge.
- If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
Code indicating method of handling for an allowance or charge
- 02
- Off Invoice
- 06
- Charge to be Paid by Customer
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.
CTT*1
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
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.