**These specifications are a base model. All customers are responsible for ensuring their map or EDI is compliant with their trading partner's most current specifications.
Amazon
Retail X12 810 Invoice
X12 / V4010 / 810: Invoice
Version: 3.3
Field | Value |
Company | Amazon |
Created | 1/15/2013 |
Modified | 1/23/2024 |
810 Invoice
Functional Group = IN
Purpose: 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.
Not Defined
Pos | Id | Segment Name | Req | Max Use | Repeat | Notes | Usage |
| ISA | Interchange Control Header | M | 1 |
|
| Must use |
| GS | Functional Group Header | M | 1 |
|
| Must use |
Heading
Pos | Id | Segment Name | Req | Max Use | Repeat | Notes | Usage |
010 | ST | Transaction Set Header | M | 1 |
|
| Must use |
020 | BIG | Beginning Segment for Invoice | M | 1 |
|
| Must use |
040 | CUR | Currency | M | 1 |
|
| Must use |
|
| LOOP ID - N1 |
|
| 200 |
|
|
070 | N1 | Name | M | 1 |
|
| Must use |
080 | N2 | Additional Name Information | O | 2 |
|
| Used |
090 | N3 | Address Information | M | 2 |
|
| Must use |
100 | N4 | Geographic Location | M | 1 |
|
| Must use |
|
| LOOP ID - N1 (Ship-To) |
|
| 200 |
|
|
070 | N1 | Name | M | 1 |
|
| Must use |
080 | N2 | Additional Name Information | O | 2 |
|
| Used |
090 | N3 | Address Information | M | 2 |
|
| Must use |
100 | N4 | Geographic Location | M | 1 |
|
| Must use |
|
| LOOP ID - N1 (Bill-To) |
|
| 200 |
|
|
070 | N1 | Name | M | 1 |
|
| Must use |
080 | N2 | Additional Name Information | O | 2 |
|
| Used |
090 | N3 | Address Information | M | 2 |
|
| Must use |
100 | N4 | Geographic Location | M | 1 |
|
| Must use |
130 | ITD | Terms of Sale/Deferred Terms of Sale | M | >1 |
|
| Must use |
Detail
Pos | Id | Segment Name | Req | Max Use | Repeat | Notes | Usage |
|
| LOOP ID - IT1 |
|
| 200000 |
|
|
010 | IT1 | Baseline Item Data (Invoice) | M | 1 |
|
| Must use |
040 | TXI | Tax Information | M | 10 |
| N2/040 | Must use |
050 | CTP | Pricing Information | C | 25 |
|
| Dependent |
120 | REF | Reference Identification | O | >1 |
|
| Used |
Summary
Pos | Id | Segment Name | Req | Max Use | Repeat | Notes | Usage |
010 | TDS | Total Monetary Value Summary | M | 1 |
|
| Must use |
020 | TXI | Tax Information | C | 10 |
| N3/020 | Dependent |
|
| LOOP ID - SAC |
|
| 25 |
|
|
040 | SAC | Service, Promotion, Allowance, or Charge Info | C | 1 |
|
| Dependent |
050 | TXI | Tax Information | C | 10 |
|
| Dependent |
070 | CTT | Transaction Totals | M | 1 |
|
| Must use |
080 | SE | Transaction Set Trailer | M | 1 |
|
| Must use |
| GE | Functional Group Trailer | M | 1 |
|
| Must use |
| IEA | Interchange Control Trailer | M | 1 |
|
| Must use |
ISA — Interchange Control Header | Pos: — | Max: 1 | Not Defined – Mandatory |
Loop: N/A | Elements: 16 | Usage: Must use
Purpose: To start and identify an interchange of zero or more functional groups and interchange-related control segments
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
ISA01 | I01 | Authorization Information Qualifier | M | ID | 2/2 | Must use |
ISA02 | I02 | Authorization Information | M | AN | 10/10 | Must use |
ISA03 | I03 | Security Information Qualifier | M | ID | 2/2 | Must use |
ISA04 | I04 | Security Information | M | AN | 10/10 | Must use |
ISA05 | I05 | Interchange ID Qualifier | M | ID | 2/2 | Must use |
ISA06 | I06 | Interchange Sender ID | M | AN | 15/15 | Must use |
ISA07 | I05 | Interchange ID Qualifier | M | ID | 2/2 | Must use |
ISA08 | I07 | Interchange Receiver ID | M | AN | 15/15 | Must use |
ISA09 | I08 | Interchange Date (YYMMDD) | M | DT | 6/6 | Must use |
ISA10 | I09 | Interchange Time (HHMM) | M | TM | 4/4 | Must use |
ISA11 | I10 | Interchange Control Standards ID | M | ID | 1/1 | Must use |
ISA12 | I11 | Interchange Control Version Number | M | ID | 5/5 | Must use |
ISA13 | I12 | Interchange Control Number | M | N0 | 9/9 | Must use |
ISA14 | I13 | Acknowledgment Requested | M | ID | 1/1 | Must use |
ISA15 | I14 | Usage Indicator | M | ID | 1/1 | Must use |
ISA16 | I15 | Component Element Separator (>) | M |
| 1/1 | Must use |
Code List for ISA01:
Code | Name |
00 | No Authorization Information Present |
Code List for ISA03:
Code | Name |
00 | No Security Information Present |
Code List for ISA07:
Code | Name |
ZZ | Mutually Defined |
Code List for ISA14:
Code | Name |
1 | Interchange Acknowledgment Requested |
Code List for ISA15:
Code | Name |
P | Production Data |
Only one ISA per file is accepted by Amazon.com. More than one ISA segment per file will result in that file being rejected. |
Segment Usage:
Must use
Example:
ISA*00* *00* *ZZ*SENDERID *ZZ*AMAZON *230331*0200*U*00400*000013229*0*P*>
GS — Functional Group Header | Pos: — | Max: 1 | Not Defined – Mandatory |
Loop: N/A | Elements: 8 | Usage: Must use
Purpose: To indicate the beginning of a functional group and to provide control information
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
GS01 | 479 | Functional Identifier Code | M | ID | 2/2 | Must use |
GS02 | 142 | Application Sender's Code | M | AN | 2/15 | Must use |
GS03 | 124 | Application Receiver's Code | M | AN | 2/15 | Must use |
GS04 | 373 | Date (CCYYMMDD) | M | DT | 8/8 | Must use |
GS05 | 337 | Time (HHMM) | M | TM | 4/8 | Must use |
GS06 | 28 | Group Control Number | M | N0 | 1/9 | Must use |
GS07 | 455 | Responsible Agency Code | M | ID | 1/2 | Must use |
GS08 | 480 | Version / Release / Industry ID Code | M | AN | 1/12 | Must use |
Code List for GS01:
Code | Name |
IN | Invoice Information (810, 819) |
Code List for GS07:
Code | Name |
X | Accredited Standards Committee X12 |
Code List for GS08:
Code | Name |
004010 | Draft Standards Approved for Publication by ASC X12 PRB through October 1997 |
Only one GS per file is accepted by Amazon.com. More than one GS segment per file will result in that file being rejected. |
Segment Usage:
Must use
Example:
GS*IN*SENDERID*AMAZON*20230331*1038*5*X*004010
ST — Transaction Set Header | Pos: 010 | Max: 1 | Heading – Mandatory |
Loop: N/A | Elements: 2 | Usage: Must use
Purpose: To indicate the start of a transaction set and to assign a control number
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
ST01 | 143 | Transaction Set Identifier Code | M | ID | 3/3 | Must use |
ST02 | 329 | Transaction Set Control Number | M | AN | 4/9 | Must use |
Code List for ST01:
Code | Name |
810 | Invoice |
Multiple ST loops are only allowed if they are for the same message type (ST*810). |
Segment Usage:
Must use
Example:
ST*810*000001967
ST*810*0200
BIG — Beginning Segment for Invoice | Pos: 020 | Max: 1 | Heading – Mandatory |
Loop: N/A | Elements: 4 | Usage: This segment provides the invoice date, the unique invoice number, PO date, and PO number.
Purpose: To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
BIG01 | 373 | Date — Invoice date (CCYYMMDD) | M | DT | 8/8 | Must use |
BIG02 | 76 | Invoice Number | M | AN | 1/22 | Must use |
BIG03 | 373 | Date — PO date (CCYYMMDD) | O | DT | 8/8 | Used |
BIG04 | 324 | Purchase Order Number | M | AN | 1/22 | Must use |
Comments:
The PO number in BIG04 must be a valid Amazon PO#, format annnnnnn. When sending multiple PO#s in one invoice, use the first PO# at the header level.
Segment Usage:
This segment provides the invoice date, the unique invoice number, PO date, and PO number.
Example:
BIG*20230330*901092*20230310*U2093709
CUR — Currency | Pos: 040 | Max: 1 | Heading – Mandatory |
Loop: N/A | Elements: 2 | Usage: Provides the currency code for the invoice. This should match the currency from your Amazon contract.
Purpose: To specify the currency used in a transaction
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
CUR01 | 98 | Entity Identifier Code | M | ID | 2/3 | Must use |
CUR02 | 100 | Currency Code | M | ID | 3/3 | Must use |
Code List for CUR01:
Code | Name |
BT | Bill-to-Party |
Code List for CUR02:
Code | Name |
CAD | Canadian Dollar |
EUR | Euro |
GBP | British Pound |
JPY | Japanese Yen |
USD | US Dollar |
Segment Usage:
Provides the currency code for the invoice. This should match the currency from your Amazon contract.
Example:
CUR*BT*USD
CUR*BT*CAD
CUR*BT*EUR
CUR*BT*JPY
CUR*BT*GBP
N1 Loop — Remit-To Name (RI) | Pos: 070 | Repeat: 200 | Mandatory |
Loop: N1 | Elements: N/A | Usage: If the remit-to address does not match, the invoice will fail in processing. Reach out to Amazon's AP department if your remit-to address needs to be updated.
Purpose: To identify a party by type of organization, name, and code
Loop Summary:
Pos | Id | Segment Name | Req | Max Use | Repeat | Usage |
070 | N1 | Name | M | 1 |
| Must use |
080 | N2 | Additional Name Information | O | 2 |
| Used |
090 | N3 | Address Information | M | 2 |
| Must use |
100 | N4 | Geographic Location | M | 1 |
| Must use |
Comments:
The remit-to address MUST be the same as the Amazon AP department has on file. Please work with your AR department to verify this is a match.
Segment Usage:
If the remit-to address does not match, the invoice will fail in processing. Reach out to Amazon's AP department if your remit-to address needs to be updated.
Example:
N1*RI*Vendor company name
N2*Additional name*Additional name
N3*Street address
N4*City*State*Postal code*Country code
N1 — Name (Remit-To) | Pos: 070 | Max: 1 | Heading – Mandatory |
Loop: N1 | Elements: 2 | Usage: Must use
Purpose: To identify a party by type of organization, name, and code
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
N101 | 98 | Entity Identifier Code | M | ID | 2/3 | Must use |
N102 | 93 | Name | M | AN | 1/60 | Must use |
Code List for N101:
Code | Name |
RI | Remit To |
Segment Usage:
Must use
Example:
N1*RI*Vendor company name
N2 — Additional Name Information | Pos: 080 | Max: 2 | Heading – Optional |
Loop: N1 | Elements: 2 | Usage: Used
Purpose: To specify additional names or those longer than 35 characters in length
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
N201 | 93 | Name | O | AN | 1/60 | Used |
N202 | 93 | Name | O | AN | 1/60 | Used |
Segment Usage:
Used
N3 — Address Information | Pos: 090 | Max: 2 | Heading – Mandatory |
Loop: N1 | Elements: 2 | Usage: Must use
Purpose: To specify the location of the named party
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
N301 | 166 | Address Information | M | AN | 1/55 | Must use |
N302 | 166 | Address Information | O | AN | 1/55 | Used |
Segment Usage:
Must use
Example:
N3*PO BOX 10307
N3*3925 NORTH HASTINGS WAY
N4 — Geographic Location (Remit-To) | Pos: 100 | Max: 1 | Heading – Mandatory |
Loop: N1 | Elements: 4 | Usage: Must use
Purpose: To specify the geographic place of the named party
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
N401 | 19 | City Name | M | AN | 2/30 | Must use |
N402 | 156 | State or Province Code | M | ID | 2/2 | Must use |
N403 | 116 | Postal Code | M | ID | 3/15 | Must use |
N404 | 26 | Country Code | M | ID | 2/3 | Must use |
Code List for N404:
Code | Name |
US | United States |
CA | Canada |
GB | United Kingdom |
FR | France |
DE | Germany |
JP | Japan |
MX | Mexico |
AU | Australia |
SG | Singapore |
Segment Usage:
Must use
Example:
N4*SAN RAFAEL*CA*949120307*US
N4*TORONTO*ON*M1H 2X3*CA
N1 Loop — Ship-To (ST) | Pos: 070 | Repeat: 200 | Mandatory |
Loop: N1 | Elements: N/A | Usage: Must use
Purpose: This is the address of the Amazon fulfillment center that received the shipment.
Loop Summary:
Pos | Id | Segment Name | Req | Max Use | Repeat | Usage |
070 | N1 | Name | M | 1 |
| Must use |
080 | N2 | Additional Name Information | O | 2 |
| Used |
090 | N3 | Address Information | M | 2 |
| Must use |
100 | N4 | Geographic Location | M | 1 |
| Must use |
Code List for N101 (Ship-To):
Code | Name |
ST | Ship To |
Segment Usage:
Must use
Example:
N1*ST*AMAZON.COM
N3*1600 East Newlands Drive
N4*Fernley*NV*89408*US
N1 Loop — Bill-To (BT) | Pos: 070 | Repeat: 200 | Conditional |
Loop: N1 | Elements: N/A | Usage: Dependent
Purpose: The N1*BT loop with bill-to name and address is required for Canada, Mexico, Australia, and Singapore vendors. It is optional for other marketplaces.
Loop Summary:
Pos | Id | Segment Name | Req | Max Use | Repeat | Usage |
070 | N1 | Name | M | 1 |
| Must use |
080 | N2 | Additional Name Information | O | 2 |
| Used |
090 | N3 | Address Information | M | 2 |
| Must use |
100 | N4 | Geographic Location | M | 1 |
| Must use |
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
N101 | 98 | Entity Identifier Code | M | ID | 2/3 | Must use |
N102 | 93 | Name | M | AN | 1/60 | Must use |
N103 | 66 | Identification Code Qualifier (TA = Taxpayer ID) | C | ID | 1/2 | Used |
N104 | 67 | Identification Code (Amazon Tax ID) | C | AN | 2/80 | Used |
For US POs, use the address of the ship-to Amazon FC for the bill-to address. For other marketplaces, use the addresses as documented below. |
Segment Usage:
Dependent
Example:
N1*BT*Amazon.com
N1*BT*Amazon.com.ca ULC
N1*BT*Servicios Comerciales Amazon México S. de R.L. de C.V.*TA*ACA140623TXA
N1*BT*Amazon Commercial Services Pty Ltd*TA*30616935623
N1*BT*Amazon Asia-Pacific Holdings Private(PTE) Limited*TA*201411358G
ITD — Terms of Sale / Deferred Terms of Sale | Pos: 130 | Max: >1 | Heading – Mandatory |
Loop: N/A | Elements: 8 | Usage: Must use
Purpose: To specify terms of sale
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
ITD01 | 336 | Terms Type Code | M | ID | 2/2 | Must use |
ITD02 | 333 | Terms Basis Date Code | M | ID | 1/2 | Must use |
ITD03 | 338 | Terms Discount Percent | C | R | 1/6 | Used |
ITD04 | 370 | Terms Discount Due Date | C | DT | 8/8 | Used |
ITD05 | 351 | Terms Discount Days Due | C | N0 | 1/3 | Used |
ITD06 | 446 | Terms Net Due Date | C | DT | 8/8 | Used |
ITD07 | 386 | Terms Net Days | M | N0 | 1/3 | Must use |
ITD13 | 765 | Day of Month (fixed date) | C | N0 | 1/2 | Used |
Code List for ITD01:
Code | Name |
01 | Basic |
02 | End of Month (EOM) |
03 | Fixed Date |
09 | Proximo |
23 | Payment Due Upon Receipt of Invoice |
41 | Letter of Credit |
Code List for ITD02:
Code | Name |
3 | Invoice Date |
Segment Usage:
Must use
Example:
ITD*01*3****20010323*30 (Basic NET 30 Days)
ITD*01*3*2*20010315*10*20010323*60 (2% 10, NET 60 Days)
ITD*02*3****20010323*150 (End of Month, 150 days)
ITD*03*3*2*20010323*15*20010323*30 (Fixed Date: 2% 15th, NET 30)
ITD*09*3*2*20010323*15*20010323*120 (Proximo: 2% 15 PROX 120)
IT1 Loop — Baseline Item Data (Invoice) | Pos: 010 | Repeat: 200,000 | Detail – Mandatory |
Loop: IT1 | Elements: N/A | Usage: Must use
Purpose: To specify the basic and most frequently used line item data for the invoice
Loop Summary:
Pos | Id | Segment Name | Req | Max Use | Repeat | Usage |
010 | IT1 | Baseline Item Data (Invoice) | M | 1 |
| Must use |
040 | TXI | Tax Information | M | 10 |
| Must use |
050 | CTP | Pricing Information | C | 25 |
| Dependent |
120 | REF | Reference Identification | O | >1 |
| Used |
Segment Usage:
Must use
IT1 — Baseline Item Data (Invoice) | Pos: 010 | Max: 1 | Detail – Mandatory |
Loop: IT1 | Elements: 11 | Usage: Must use
Purpose: To specify the basic and most frequently used line item data for the invoice and related transactions
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
IT101 | 350 | Assigned Identification (line ID) | M | AN | 1/20 | Must use |
IT102 | 358 | Quantity Invoiced (must be > 0) | M | R | 1/10 | Must use |
IT103 | 355 | Unit or Basis for Measurement Code | M | ID | 2/2 | Must use |
IT104 | 212 | Unit Price (nnnnn.nn) | M | R | 1/17 | Must use |
IT105 | 639 | Basis of Unit Price Code | M | ID | 2/2 | Must use |
IT106 | 235 | Product/Service ID Qualifier | M | ID | 2/2 | Must use |
IT107 | 234 | Product/Service ID | M | AN | 1/48 | Must use |
IT108 | 235 | Product/Service ID Qualifier (optional) | O | ID | 2/2 | Used |
IT109 | 234 | Product/Service ID (ASIN or SKU) | O | AN | 1/48 | Used |
IT110 | 235 | Product/Service ID Qualifier (PO) | M | ID | 2/2 | Must use |
IT111 | 234 | Product/Service ID (Amazon PO number) | M | AN | 1/48 | Must use |
Code List for IT103:
Code | Name |
CA | Case |
EA | Each |
Code List for IT105:
Code | Name |
NT | Net |
Code List for IT106/108:
Code | Name |
BP | Buyer's Part Number |
EN | EAN |
IB | ISBN |
UA | UPC/EAN Case Code |
UK | UPC/EAN Shipping Container |
UP | UPC Consumer Package Code |
VN | Vendor's Item Number |
Code List for IT110:
Code | Name |
PO | Purchase Order Number |
Segment Usage:
Must use
Example:
IT1*001*1*EA*11.96*NT*UP*025091005628***PO*F6580987
IT1*001*1*EA*60.75*NT*IB*0895031892***PO*F6580987
TXI — Tax Information (Detail) | Pos: 040 | Max: 10 | Detail – Mandatory |
Loop: IT1 | Elements: 4 | Usage: Must use
Purpose: To specify tax information
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
TXI01 | 963 | Tax Type Code | M | ID | 2/2 | Must use |
TXI02 | 782 | Monetary Amount | M | R | 1/18 | Must use |
TXI03 | 954 | Percent (nn.nnn) | M | R | 1/10 | Must use |
TXI06 | 441 | Tax Exempt Code | O | ID | 1/1 | Used |
Code List for TXI01:
Code | Name |
GS | Goods and Services Tax |
ST | State Sales Tax (Québec only) |
VA | Value Added Tax |
ZZ | Mutually Defined |
Code List for TXI06:
Code | Name |
F | Exempt (Goods and Services Tax) — Singapore only |
Tax is required at both the line item and summary level based on country requirements. This segment is not required for US vendors. If a line item is not taxable, include 0% tax lines at both line and summary level. |
Segment Usage:
Must use
Example:
TXI*GS*18.99*7
TXI*GS*1.715*7
TXI*GS*700.513*7***F
TXI*ST*14.94*9.975
CTP — Pricing Information | Pos: 050 | Max: 25 | Detail – Conditional |
Loop: IT1 | Elements: 4 | Usage: The CTP segment is required if price information was provided on the corresponding 855 for these items. The multiplier × list price (CTP03) = net price (IT104). A 20% discount = multiplier of 0.8.
Purpose: To specify pricing information
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
CTP02 | 236 | Price Identifier Code | M | ID | 3/3 | Must use |
CTP03 | 212 | Unit Price (nnnnn.nn) | M | R | 1/17 | Must use |
CTP06 | 648 | Price Multiplier Qualifier | M | ID | 3/3 | Must use |
CTP07 | 649 | Multiplier (discount decimal) | M | R | 1/10 | Must use |
Code List for CTP02:
Code | Name |
LPR | List Price |
SLP | Suggested List Price |
Code List for CTP06:
Code | Name |
DIS | Discount Multiplier |
Segment Usage:
The CTP segment is required if price information was provided on the corresponding 855 for these items. The multiplier × list price (CTP03) = net price (IT104). A 20% discount = multiplier of 0.8.
Example:
CTP**SLP*19.95***DIS*.55
CTP**SLP*19.95***DIS*1
REF — Reference Identification | Pos: 120 | Max: >1 | Detail – Optional |
Loop: IT1 | Elements: 2 | Usage: This is the tracking number provided by your shipping carrier for this item.
Purpose: To specify identifying information
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
REF01 | 128 | Reference Identification Qualifier | M | ID | 2/3 | Must use |
REF02 | 127 | Reference Identification | X | AN | 1/30 | Used |
Code List for REF01:
Code | Name |
2I | Tracking Number |
Segment Usage:
This is the tracking number provided by your shipping carrier for this item.
Example:
REF*2I*982103923402394823
TDS — Total Monetary Value Summary | Pos: 010 | Max: 1 | Summary – Mandatory |
Loop: N/A | Elements: 1 | Usage: Must use
Purpose: To specify the total invoice discounts and amounts
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
TDS01 | 610 | Amount (total including charges, allowances, and tax) | M | N2 | 1/15 | Must use |
Data type is N2 — the decimal is implied for two positions. For example, $26.34 must be sent as 2634. |
Segment Usage:
Must use
Example:
TDS*2634
TXI — Tax Information (Summary) | Pos: 020 | Max: 10 | Summary – Conditional |
Loop: N/A | Elements: 6 | Usage: Dependent
Purpose: To specify tax information
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
TXI01 | 963 | Tax Type Code | M | ID | 2/2 | Must use |
TXI02 | 782 | Monetary Amount (nnnnn.nn) | M | R | 1/18 | Must use |
TXI03 | 954 | Percent (nn.nnn) | M | R | 1/10 | Must use |
TXI06 | 441 | Tax Exempt Code | C | ID | 1/1 | Dependent |
TXI08 | 828 | Dollar Basis For Percent | M | R | 1/12 | Must use |
TXI09 | 325 | Tax Identification Number | M | AN | 1/20 | Must use |
Code List for TXI01:
Code | Name |
GS | Goods and Services Tax |
ST | State Sales Tax (Québec only) |
VA | Value Added Tax |
ZZ | Mutually Defined |
Code List for TXI06:
Code | Name |
F | Exempt (Goods and Services Tax) |
T | Totally Exempt |
DO NOT use for US marketplace — any US invoice with a TXI segment will fail. Required for Canada (GST/HST/QST ID), Australia (ABN), Japan (JCT ID), Mexico, and Singapore. For Québec CA vendors, two TXI summary segments are needed: one for GST/HST ID and one for QST ID. |
Segment Usage:
Dependent
Example:
TXI*GS*1.23*5*****24.62*VENDORTAXID
TXI*ST*79.42*9.975*****796.19*VENDORTAXID
SAC Loop — Service, Promotion, Allowance, or Charge | Pos: 040 | Repeat: 25 | Summary – Conditional |
Loop: SAC | Elements: N/A | Usage: Dependent
Purpose: To request or identify a service, promotion, allowance, or charge
Loop Summary:
Pos | Id | Segment Name | Req | Max Use | Repeat | Usage |
040 | SAC | Service, Promotion, Allowance, or Charge Information | C | 1 |
| Dependent |
050 | TXI | Tax Information | C | 10 |
| Dependent |
The SAC loop should ONLY be sent when an actual charge is applied to this invoice's total. |
Segment Usage:
Dependent
SAC — Service, Promotion, Allowance, or Charge Information | Pos: 040 | Max: 1 | Summary – Conditional |
Loop: SAC | Elements: 4 | Usage: Dependent
Purpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
SAC01 | 248 | Allowance or Charge Indicator | M | ID | 1/1 | Must use |
SAC02 | 1300 | Service, Promotion, Allowance, or Charge Code | M | ID | 4/4 | Must use |
SAC05 | 610 | Amount (N2 format) | M | N2 | 1/15 | Must use |
SAC15 | 352 | Description (free-form) | O | AN | 1/80 | Used |
Code List for SAC01:
Code | Name |
A | Allowance |
C | Charge |
Code List for SAC02:
Code | Name |
B720 | Cooperative Advertising/Merchandising Allowance |
C000 | Defective Allowance |
C260 | Discount – Incentive |
C310 | Discount |
C530 | Duty Charge |
C680 | Environmental Protection Service |
D240 | Freight |
D500 | Handling |
D920 | Insurance Fee |
F800 | Promotional Allowance |
G730 | Service Charge (with Cash Discount) |
G970 | Small Order Charge |
H000 | Special Allowance |
I410 | Unsaleable Merchandise Allowance |
Segment Usage:
Dependent
Example:
SAC*C*D240***278**********Freight
TXI — Tax Information (SAC) | Pos: 050 | Max: 10 | Summary – Conditional |
Loop: SAC | Elements: 3 | Usage: This segment is only required if the preceding SAC segment is taxable.
Purpose: To specify tax information applicable to the preceding SAC charge
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
TXI01 | 963 | Tax Type Code | M | ID | 2/2 | Must use |
TXI02 | 782 | Monetary Amount | M | R | 1/18 | Must use |
TXI03 | 954 | Percent (nn.nnn) | M | R | 1/10 | Must use |
Code List for TXI01:
Code | Name |
GS | Goods and Services Tax |
VA | Value Added Tax |
ZZ | Mutually Defined |
Segment Usage:
This segment is only required if the preceding SAC segment is taxable.
Example:
TXI*GS*18.99*7
CTT — Transaction Totals | Pos: 070 | Max: 1 | Summary – Mandatory |
Loop: N/A | Elements: 2 | Usage: Must use
Purpose: To transmit a hash total for a specific element in the transaction set
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
CTT01 | 354 | Number of Line Items (count of IT1 segments) | M | N0 | 1/6 | Must use |
CTT02 | 347 | Hash Total (sum of all IT102 quantities) | M | R | 1/10 | Must use |
Segment Usage:
Must use
Example:
CTT*10*10
CTT*3*6
SE — Transaction Set Trailer | Pos: 080 | Max: 1 | Summary – Mandatory |
Loop: N/A | Elements: 2 | Usage: Must use
Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
SE01 | 96 | Number of Included Segments (including ST and SE) | M | N0 | 1/10 | Must use |
SE02 | 329 | Transaction Set Control Number | M | AN | 4/9 | Must use |
Segment Usage:
Must use
Example:
SE*122*000001967
SE*14*0200
GE — Functional Group Trailer | Pos: — | Max: 1 | Not Defined – Mandatory |
Loop: N/A | Elements: 2 | Usage: Must use
Purpose: To indicate the end of a functional group and to provide control information
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
GE01 | 97 | Number of Transaction Sets Included | M | N0 | 1/6 | Must use |
GE02 | 28 | Group Control Number | M | N0 | 1/9 | Must use |
Segment Usage:
Must use
Example:
GE*5*5
IEA — Interchange Control Trailer | Pos: — | Max: 1 | Not Defined – Mandatory |
Loop: N/A | Elements: 2 | Usage: Must use
Purpose: To define the end of an interchange of zero or more functional groups
Element Summary:
Ref | Id | Element Name | Req | Type | Min/Max | Usage |
IEA01 | I16 | Number of Included Functional Groups | M | N0 | 1/5 | Must use |
IEA02 | I12 | Interchange Control Number | M | N0 | 9/9 | Must use |
Segment Usage:
Must use
Example:
IEA*1*000013229
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article