![Canadian Tire logo](https://public-assets.guides.us.stedi.com/dc64d147-c125-435b-bdfa-0fd5e002abba/account-config/logo.webp?v=1713886166358)
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
Example: BIG2017040300001234*99990001***00
Date expressed as CCYYMMDD
- BIG01 is the invoice issue date.
Identifying number for Purchase Order assigned by the orderer/purchaser
CTC PO Number
Format: (NNNNNNNN)
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
The currency in the invoice must match the currency indicated in the 850 PO. All PO's are Canadian dollars (CAD) unless indicated otherwise by the presence of a CUR segment. CTC currently only processes Canadian and United States dollars via electronic invoice.
Example: CURBYCAD
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Reference Identification
To specify identifying information
Example: REFVR9999
Code qualifying the Reference Identification
- VR
- Vendor ID Number
Name
To identify a party by type of organization, name, and code
Example: N1RIBOB’S BAIT SHOPPE1123456789
Code identifying an organizational entity, a physical location, property or an individual
- RI
- Remit To
Code designating the system/method of code structure used for Identification Code (67)
- 1
- D-U-N-S Number, Dun & Bradstreet
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.
Address Information
To specify the location of the named party
Example: N3*1234 ELM DRIVE
Geographic Location
To specify the geographic place of the named party
Example: N4TIMBUKTUONA1A 1A1CA
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.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Name
To identify a party by type of organization, name, and code
For Direct Ship use of N1 ST segment optional, or use N1STCT RETAIL - DIRECT SHIP92016136689000 otherwise same rules as Cross Dock.
Storage:
N101 = “ST” (ship to) and N103 = “9” (distribution center #).
Cross-Dock or Direct Ship:
INVOICE BY STORE
N101 = “MA” (ultimate destination) and N103 = “92” (store #). Send one invoice for each store on the PO. This is the only case where product is shipped to two different destinations, the product being first shipped to a distribution center and then to a store. Partial invoicing should be avoided.
INVOICE BY PO
N101 = “ST” (ship to) and N103 = “9” (distribution center #). Do the same as for a storage order, with the DC code in the N1. The invoice, therefore, becomes a summary level invoice showing the total quantity for each item shipped for the PO. The entire PO must be invoiced, however, if this option is chosen. No partial invoicing is allowed.
Example: N1STA J BILLES92016136689005
Code identifying an organizational entity, a physical location, property or an individual
- MA
- Party for whom Item is Ultimately Intended
- ST
- Ship To
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
- 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.
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
IT101 is required in order to process your Invoice. The Purchase Order Line Number is provided by CTC within the Purchase Order Transaction (850) - PO1 Segment 01 Element.
When implementing the 810, CTC will change the 850 PO to have Net cost (inclusive of allowances and charges) sent in the PO104. Please return these costs on the Invoice.
Example: IT1199EA9.99*SK012-3456-7
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
Purchase Order Line Number (PO101 in 850).
Number of units invoiced (supplier units)
Consumer 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.
Net price per unit of product (PO104 in 850). Maximum 4 decimal places.
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.
- SK
- Stock Keeping Unit (SKU)
Product/Item Description
To describe a product or process in coded or free-form format
Example: PIDF***DELUXE TACKLE BOX
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
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
Example: TDS*102857
Tax Information
To specify tax information
Example: TXIZZ69.230.13*****123456789
Code specifying the type of tax
- GS
- Goods and Services Tax
- SP
- Quebec Sales Tax
- ZZ
- Harmonized Sales Tax
Monetary amount
- TXI02 is the monetary amount of the tax.
Percentage expressed as a decimal
- TXI03 is the tax percent expressed as a decimal.
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
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
PROCESS HANDLING - AOM CHANNEL - CROSS DOCK (Inv per PO) MULTIPLE SKUs
GS*IN*SENDERGS*RECEIVERGS*20240506*205538*000000001*X*004010~
BIG*20170403*00001236**99991235****00~
CUR*BY*CAD~
REF*VR*9999~
N1*RI* ABC COMPANY *1*123456789~
N1*ST*A J BILLES*9*2016136689005~
IT1*1*10*EA*4.03**SK*099-9998-6~
PID*F****MOTOMASTER OIL FILTER~
IT1*2*40*EA*7.44**SK*099-9999-9~
PID*F****PERSONA WIDE SLOT TOASTER~
TDS*38851~
TXI*GS*16.90*0.05******123456789~
TXI*SP*33.71*0.09975******2315798~
CTT*2~
GE*1*000000001~
IEA*1*000000001~
PROCESS HANDLING - AOM CHANNEL - CROSS DOCK or Direct Shipto Store (Inv per Store) MULTIPLE SKUs
GS*IN*SENDERGS*RECEIVERGS*20240506*205506*000000001*X*004010~
BIG*20170630*00001252**01132459****00~
CUR*BY*CAD~
REF*VR*9999~
N1*RI* ABC COMPANY *1*123456789~
N1*MA* *92*0330~
IT1*1*20*EA*7.44**SK*099-9999-9~
PID*F****PERSONA WIDE SLOT TOASTER~
TDS*15624~
TXI*GS*7.44*0.05******123456789~
CTT*1~
BIG*20170630*00001253**01132459****00~
CUR*BY*CAD~
REF*VR*9999~
N1*RI* ABC COMPANY *1*123456789~
N1*MA* *92*0397~
IT1*1*10*EA*7.44**SK*099-9999-9~
PID*F****PERSONA WIDE SLOT TOASTER~
IT1*2*5*EA*4.03**SK*099-9998-6~
PID*F****MOTOMASTER OIL FILTER~
TDS*9928~
TXI*GS*4.73*0.05******123456789~
CTT*2~
GE*2*000000001~
IEA*1*000000001~
PROCESS HANDLING - AOM CHANNEL - Direct Ship (Inv per PO) MULTIPLE SKUs
GS*IN*SENDERGS*RECEIVERGS*20240506*205604*000000001*X*004010~
BIG*20170403*00001236**99991235****00~
CUR*BY*CAD~
REF*VR*9999~
N1*RI* ABC COMPANY *1*123456789~
N1*ST* CT RETAIL - DIRECT SHIP *9*2016136689000~
IT1*1*10*EA*4.03**SK*099-9998-6~
PID*F****MOTOMASTER OIL FILTER~
IT1*2*40*EA*7.44**SK*099-9999-9~
PID*F****PERSONA WIDE SLOT TOASTER~
TDS*38093~
TXI*ZZ*43.93*0.13******123456789~
CTT*2~
GE*1*000000001~
IEA*1*000000001~
PROCESS HANDLING - LEGACY or AOM CHANNEL - STORAGE or CROSS DOCK (Inv per PO) MULTIPLE SKUs
GS*IN*SENDERGS*RECEIVERGS*20240506*204749*000000001*X*004010~
BIG*20170403*00001234**99991235****00~
CUR*BY*CAD~
REF*VR*9999~
N1*RI* ABC COMPANY *1*123456789~
N1*ST*A J BILLES*9*2016136689005~
IT1*1*72*EA*9.69**SK*099-9997-3~
PID*F****YARDWORKS PRO-GRADE SHOVEL~
IT1*2*48*EA*4.03**SK*099-9998-6~
PID*F****MOTOMASTER OIL FILTER~
IT1*3*24*EA*7.44**SK*099-9999-9~
PID*F****PERSONA WIDE SLOT TOASTER~
TDS*120874~
TXI*ZZ*139.06*0.13******123456789~
CTT*3~
GE*1*000000001~
IEA*1*000000001~
Sample 1
GS*IN*SENDERGS*RECEIVERGS*20240506*204817*000000001*X*004010~
BIG*20170403*00001234**99990001****00~
CUR*BY*CAD~
REF*VR*9999~
N1*RI*BOB’S BAIT SHOPPE*1*123456789~
N3*1234 ELM DRIVE~
N4*TIMBUKTU*ON*A1A 1A1*CA~
N1*ST*A J BILLES*9*2016136689005~
IT1*1*99*EA*9.99**SK*012-3456-7~
PID*F****DELUXE TACKLE BOX~
TDS*102857~
TXI*ZZ*69.23*0.13******123456789~
CTT*1~
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.