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
The Purchase Order date (BIG03) and Purchase Order Number (BIG04) should match the BEG segment (BEG03 and BEG05) on corresponding EDI 850. Also note BIG10 Shipment ID number must match EDI 856 BSN02. See examples below.
EDI 850 - BEG00SA47030890596**20200501
EDI 856 - BSN00292707318720200116185636000001
Example: BIG202005011261353272020050147030890596******2927073187
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.
Identifying number for Purchase Order assigned by the orderer/purchaser
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
The currency code must match currency indicated on EDI 850.
Example: CURBYCAD
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Name
To identify a party by type of organization, name, and code
Store and DC values must be numeric. Do not use alphanumeric store or DC code included in EDI 850 SDQ segment. Please replace region code with ‘00’. For example, ecommerce store ‘TR1963’ should be transmitted as ‘001963’ on the electronic invoice.
Examples:
Direct to Store shipment: N1BY**92001101
DC shipment: N1BY**92000596
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Code designating the system/method of code structure used for Identification Code (67)
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.
Store / DC Location Code
Name
To identify a party by type of organization, name, and code
The vendor number on invoice must match the vendor number on EDI 850.
Example: N1SUCOMPANY NAME92012345
Code identifying an organizational entity, a physical location, property or an individual
- SU
- Supplier/Manufacturer
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.
Vendor Number
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
Example: ITD012*****30
Code identifying type of payment terms
- If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.
- 01
- Basic
- 02
- End of Month (EOM)
- 05
- Discount Not Applicable
- 08
- Basic Discount Offered
- 12
- 10 Days After End of Month (10 EOM)
Code identifying the beginning of the terms period
- 1
- Ship Date
- 2
- Delivery Date
- 3
- Invoice Date
- 15
- Receipt of Goods
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
Date payment is due if discount is to be earned expressed in format CCYYMMDD
Number of days in the terms discount period by which payment is due if terms discount is earned
Number of days until total invoice amount is due (discount not applicable)
Date/Time Reference
To specify pertinent dates and times
Example: DTM01120190620
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
Example: IT112EA281QTUP000123456789VN*VENDORSTYLE
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
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
- QT
- Quoted
- RE
- Retail Price per Each
- WE
- Wholesale Price per Each
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)
- 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)
- VN
- Vendor's (Seller's) Item Number
Product/Item Description
To describe a product or process in coded or free-form format
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
Destination Quantity
To specify destination and quantity detail
The store number and quantity pairs may be repeated 10 times within the SDQ segment. Multiple SDQ segments may be sent. For store addresses, please refer to store and DC list available at hbcediextranet.hbc.com/.
Example: SDQEA92CX11142CX11382CX11442CX11502CX11642EY11252EY11472EY11832LS16172TQ15142
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code designating the system/method of code structure used for Identification Code (67)
- SDQ02 is used only if different than previously defined in the transaction set.
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- SDQ03 is the store number.
Region code and Store Number.
Code identifying a party or other code
Region code and Store Number.
Code identifying a party or other code
Region code and Store Number.
Code identifying a party or other code
Region code and Store Number.
Code identifying a party or other code
Region code and Store Number.
Code identifying a party or other code
Region code and Store Number.
Code identifying a party or other code
Region code and Store Number.
Code identifying a party or other code
Region code and Store Number.
Code identifying a party or other code
Region code and Store Number.
Code identifying a party or other code
Region code and Store Number.
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
Amounts should not include decimal places. For example, $2472.65 should be transmitted as ‘247265’.
Example: TDS247265247265
Monetary amount
- TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
Monetary amount
- TDS02 indicates the amount upon which the terms discount amount is calculated.
- TDS02 is required if the dollar value subject to discount is not equal to the dollar value of TDS01.
Monetary amount
- TDS03 is the amount of invoice due if paid by terms discount due date (total invoice or installment amount less cash discount).
Carrier Detail
To specify transportation details for the transaction
Examples:
CADMABFS*ABF FREIGHT SYSTEM INCBM*00684740032552578
Code specifying the method or type of transportation for the shipment
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Carrier Name
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
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
Do not include decimal in charge amount. SAC15 Element must include 2 byte Provincial Code and Tax Charge Code. For example, if a shipment from Ontario is shipped to various stores with variant provincial tax requirements, SAC15 should include ‘ONHST.’
Acceptable SAC02 / SAC15 Combinations:
Element / Code / Element / Code
SAC02 H770 SAC15 PQQST
SAC02 H770 SAC15 QCQST
SAC02 D360 SAC15 ONHST
SAC02 D360 SAC15 NSHST
SAC02 D360 SAC15 NBHST
SAC02 D360 SAC15 NFHST
SAC02 D360 SAC15 PEHST
SAC02 D361 SAC15 ABGST
SAC02 D361 SAC15 BCGST
SAC02 D361 SAC15 MBGST
SAC02 D361 SAC15 SKGST
SAC02 D361 SAC15 YTGST
SAC02 D361 SAC15 NTGST
SAC02 D361 SAC15 NUGST
SAC02 D361 SAC15 PQGST
SAC02 D361 SAC15 QCGST
Provincial Codes:
Province / Abbreviation
Alberta AB
British Columbia BC
Manitoba MB
New Brunswick NB
Newfoundland & Labrador NF
Northwest Territories NT
Nova Scotia NS
Nunavut NU
Ontario ON
Prince Edward Island PE
Quebec PQ
Saskatchewan SK
Yukon YT
Example: SACCD36013720*******ONHST
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
Code identifying the service, promotion, allowance, or charge
- D360
- Goods and Services Tax Charge
- D361
- Goods and Services Tax Charge
- H770
- Tax - State Tax
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.
A free-form description to clarify the related data elements and their content
Provincial Code and Tax Charge Code
- ABGST
- Alberta GST
- BCGST
- British Columbia GST
- MBGST
- Manitoba GST
- NBHST
- New Brunswick HST
- NFHST
- Newfoundland & Labrador HST
- NSHST
- Nova Scotia HST
- NTGST
- Northwest Territories GST
- NUGST
- Nunavut GST
- ONHST
- Ontario HST
- PEHST
- Prince Edward Island HST
- PQGST
- Quebec GST
- PQQST
- Quebec QST
- QCGST
- Quebec GST
- QCQST
- Quebec QST
- SKGST
- Saskatchewan GST
- YTGST
- Yukon GST
Tax Information
To specify tax information
TXI is only to be used if billing tax. Vendors that charge GST or HST to HBC on their invoices must supply their GST or HST Registration Number. Vendors that charge GST and QST to HBC on their invoices must supply their GST and QST Registration Numbers.
HBC requires a TXI segment to be sent with TXI01 = ‘GS’ and TXI09 = GST registration number, if the TXI segment is sent with TXI01 = ‘GS’ and TXI02 not = 0. HBC requires a TXI segment to be sent with TXI01 = ‘OH’ and TXI09 = QST registration number, if the TXI segment is sent with TXI01 = ‘OH’ and TXI02 not = 0. HBC requires a TXI segment to be sent with TXI01 = ‘ST’ and TXI09 = HST registration number, if the TXI segment is sent with TXI01 = ‘ST’ and TXI02 not = 0***
Examples:
TXIGS137.20CDON**1234567
TXILS*27.80CDQC*1234567
TXIST*52.26CDON****1234567
Code specifying the type of tax
- CP
- County/Parish Sales Tax
Goods and Services Tax/GST
- CS
- City Sales Tax
Goods and Services Tax/GST
- CT
- County Tax
Goods and Services Tax/GST
- GS
- Goods and Services Tax
Goods and Services Tax/GST
- LS
- State and Local Sales Tax
Quebec Sales Tax/QST
- LT
- Local Sales Tax (All Applicable Sales Taxes by Taxing Authority Below the State Level)
Quebec Sales Tax/QST
- OH
- Other Taxes
Quebec Sales Tax/QST
- SP
- State/Provincial Tax
Provincial Sales Tax/PST
- ST
- State Sales Tax
Harmonized Sales Tax/HST
- VA
- Value Added Tax
Harmonized Sales Tax/HST
- ZZ
- Mutually Defined
Harmonized Sales Tax/HST
Monetary amount
- TXI02 is the monetary amount of the tax.
Code identifying the source of the data used in tax jurisdiction code
- CD
- Customer defined
Code identifying the taxing jurisdiction
2-Character province or state abbreviation.
Invoice Shipment Summary
To specify summary details of total items shipped in terms of quantity, weight, and volume
Example: ISS5EA11LB
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
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*12
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
Invoice Excluding SDQ Segments
GS*IN*SENDERGS*RECEIVERGS*20231101*015356*000000001*X*004010
ST*810*2037
BIG*20220823*50156307*20220401*15814390596******506546662
CUR*BY*CAD
N1*BY**92*0596
N1*SU**92*070935
ITD*08*15*2*20220902*10**60
IT1*2*7*EA*59.4*WE*UP*190108853445*VN*1017320K-CHE-01
PID*F****K NEUMEL II 1017320K CHESTNUTSIZE01
IT1*1*6*EA*59.4*WE*UP*190108853407*VN*1017320K-CHE-13
PID*F****K NEUMEL II 1017320K CHESTNUTSIZE13
IT1*5*11*EA*59.4*WE*UP*190108853377*VN*1017320K-CHE-04
PID*F****K NEUMEL II 1017320K CHESTNUTSIZE04
IT1*3*7*EA*59.4*WE*UP*190108853452*VN*1017320K-CHE-02
PID*F****K NEUMEL II 1017320K CHESTNUTSIZE02
IT1*7*1*EA*59.4*WE*UP*190108853391*VN*1017320K-CHE-06
PID*F****K NEUMEL II 1017320K CHESTNUTSIZE06
IT1*4*9*EA*59.4*WE*UP*190108853414*VN*1017320K-CHE-03
PID*F****K NEUMEL II 1017320K CHESTNUTSIZE03
TDS*275201*243540*269697*5504
CAD*M***NLGO*SPEEDWAY LOGISTICS**BM*0053822179
SAC*C*H770***31661**********ONHST
TXI*ST*316.61**CD*ON****1234567890
ISS*41*EA*69.58*LB
CTT*6
SE*25*2037
GE*1*000000001
IEA*1*000000001
Invoice Including IT1 and SDQ Segments
GS*IN*SENDERGS*RECEIVERGS*20231101*015407*000000001*X*004010
ST*810*1221
BIG*20220823*152036540*20220808*18068240596******4705026
CUR*BY*CAD
N1*BY**92*0596
N1*SU*Candy Company*92*073643
ITD*05*15**20220823*90**90******0
DTM*011*20220816
IT1*1*672*EA*1.61*WE*UP*071570013202*VN*55199
SDQ*EA*92*VT1101*24*VV1111*24*VT1118*24*VT1119*24*VT1127*24*EY1135*24*EY1147*24*VV1161*24*TW1112*24*TW1113*24
SDQ*EA*92*TW1140*24*TR1517*24*TR1518*24*TQ1523*24*TQ1524*24*TR1527*24*TQ1542*24*TQ1544*24*CX1136*24*CX1150*24
SDQ*EA*92*TR1512*24*TQ1514*24*TR1526*24*TR1532*24*TR1546*24*TQ1547*24*TQ1631*24*TR1633*24
IT1*2*2448*EA*2.18*WE*UP*071570006730*VN*46112
SDQ*EA*92*VT1101*48*VT1104*48*VV1108*48*VT1109*48*VV1111*48*CX1116*48*EY1125*48*VT1127*48*VT1131*48*VT1142*48
SDQ*EA*92*EY1145*48*EY1147*48*VT1162*48*VV1171*48*EY1183*48*TW1112*48*TW1140*48*TQ1515*48*TR1517*48*TR1518*48
SDQ*EA*92*TQ1522*48*TQ1524*48*TR1527*48*TR1530*48*TQ1541*48*TQ1542*48*TR1543*48*TQ1550*48*TQ1575*48*TQ1576*48
SDQ*EA*92*CX1138*48*CX1144*48*CX1150*48*CX1164*48*TR1512*48*TQ1514*48*TR1526*48*TR1532*48*TQ1533*48*TQ1535*48
SDQ*EA*92*TR1546*48*TQ1547*48*TQ1554*48*TR1560*48*TQ1601*48*TR1606*48*TR1610*48*TR1613*48*TR1633*48*TR1649*48
SDQ*EA*92*LS1617*48
TDS*737636*641856*737636*0
CAD*M***MANI*Manitoulin**BM*4705026
SAC*C*D360***95780**********ONHST
TXI*ST*957.80**CD*ON****1234567890
ISS*3120*EA*335.37*LB
CTT*2
SE*25*1221
GE*1*000000001
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.