X12 810 [AmazonStock] 810 Retail 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
- .pdf142.92 kB
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
Sample Data:
BIG2004103090109220041022U2093709
BIG20041030901092**U2093709
Date expressed as CCYYMMDD
- BIG01 is the invoice issue date.
Date when the invoice information was generated in the origins Accounting system. The invoice date should be on or after the PO# creation date.
Identifying number assigned by issuer
Unique number relating to the charges defined in this document.
Date expressed as CCYYMMDD
- BIG03 is the date assigned by the purchaser to purchase order.
Date of the PO creation per Amazon 850 message.
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Example:
CURBTUSD
CURBTCAD
CURBTEUR
CURBTJPY
CURBTGBP
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
The N1*BT loop with bill-to name and address is required for Canada, Mexico, Australia, and Singapore vendors.
Sample Data:
US example (use address of ship-to FC):
N1BTAmazon.com
N31600 East Newlands Drive
N4FernleyNV89408*US
Canada:
N1BTAmazon.com.ca Inc.
N340 King Street West 47th Floor
N4TorontoONM5H 3Y2*CA
Japan:
N1BTAmazon Japan G.K.
N3Arco Tower Annex, 1-8-1 Shimomeguro, Meguro-ku
N4TOKYO*153-0064JP
Domestic Mexico:
N1BTServicios Comerciales Amazon México S. de R.L. de C.V.TAACA140623TXA
N3Blvd. Manuel Ávila Camacho 36 P 10 y 12Lomas De Chapultepec I Secc
N4Miguel HidalgoDF11000MX
Import Mexico:
N1BTImportadora Amazon MexicoTAACA140623TXA
N3Blvd. Manuel Ávila Camacho 36 P 10 y 12Lomas De Chapultepec I Secc
N4Miguel HidalgoDF11000MX
Australia:
N1BTAmazon Commercial Services Pty LtdTA30616935623
N32 Park Street Level 37
N4Sydney*2000AU
Singapore:
N1BTAmazon Asia-Pacific Holdings Private(PTE) LimitedTA201411358G
N31 Robinson Rd AIA Tower #17-00
N4Singapore*048542SG
Comments:
For US PO's, use the address of the ship-to Amazon FC for the bill-to address. For other marketplaces, please use the correct bill-to addresses as provided above.
Name
To identify a party by type of organization, name, and code
Sample Data:
N1BTAmazon.com
N1BTAmazon.com.ca Inc.
N1BTAmazon Japan G.K.
N1BTServicios Comerciales Amazon México S. de R.L. de C.V.TAACA140623TXA
N1BTImportadora Amazon MexicoTAACA140623TXA
N1BTAmazon Commercial Services Pty LtdTA30616935623
N1BTAmazon Asia-Pacific Holdings Private(PTE) LimitedTA201411358G
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
Free-form name
This field will be the name of the Bill-to party.
Code designating the system/method of code structure used for Identification Code (67)
This field is required for Mexico, Australia, and Singapore vendors.
- TA
- Taxpayer ID Number
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.
The Amazon tax ID is required for Mexico, Australia, and Singapore vendors.
Mexico: ACA140623TXA
Australia: 30616935623
Singapore: 201411358G
Address Information
To specify the location of the named party
This segment is required for Canada, Mexico, Australia, and Singapore vendors.
Sample Data:
Canada:
N3*40 King Street West 47th Floor
Japan:
N3*ARCO TOWER ANNEX,1-8-1 Shimomeguro, Meguro-ku
Mexico:
N3Blvd. Manuel Ávila Camacho 36 P 10 y 12Lomas de Chapultepec I Secc
Australia:
2 Park Street Level 37
Singapore:
1 Robinson Rd AIA Tower #17-00
Geographic Location
To specify the geographic place of the named party
This segment is required for Canada, Mexico, Australia, and Singapore vendors.
Sample Data:
N4FernleyNV89408US
N4TorontoONM5H 3Y2CA
N4TOKYO**153-0064JP
N4Miguel HidalgoDF11000MX
N4Sydney**2000AU
N4Singapore**048542SG
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.
Please note that the bill-to addresses for Japan, Australia, and Singapore do not have a state code. As such, this element can be left empty for those particular marketplaces.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
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. If the remit-to address does not match, the invoice will fail in processing.
Sample Data:
N1RIremit to name
N2additional nameadditional name
N3address
N4citystatepostal code*countrycode
Name
To identify a party by type of organization, name, and code
Sample Data:
N1RIName of vendor
Address Information
To specify the location of the named party
Sample Data:
N3PO BOX 10307
N33925 NORTH HASTINGS WAY
Geographic Location
To specify the geographic place of the named party
Sample Data:
N4SAN RAFAELCA949120307US
N4TorontoONM1H 2X3CA
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)
External Information: For US this is a good resource:
http://zip4.usps.com/zip4/welcome.jsp
Formatting Notes:
US: nnnnnnnnn
Canada; ana nan
Japan: nnn-nnnn
Great Britain: aan naa
France: nnnnn
Germany: nnnnn
This is the address of the Amazon FC that received the shipment.
Sample Data:
N1STAMAZON.COM
N31600 East Newlands Drive
N4FernleyNV89408*US
N1STAMAZON.CA
N3500 MCCARTHY DRFAIRVIEW BUSINESS PARK
N4MISSISSAUGAONL5R 3W5CA
N1STNARITA
N32-13-1 Shiohama, Ichikawa-shi
N4Chiba-KenCB272-0127*JP
Name
To identify a party by type of organization, name, and code
Sample Data:
N1STAMAZON.COM
N1STAMAZON.CA
N1STAMAZON JAPAN G.K.
Address Information
To specify the location of the named party
Sample Data:
N3COFFEYVILLE INDUSTRIAL PK2654 NO HIGHWAY 169
N3*2-13-1 Shiohama, Ichikawa-shi
Geographic Location
To specify the geographic place of the named party
Sample Data:
N4COFFEYVILLEKS67337US
N4MISSISSAUGAOTL5R 3W5CA
N4Chiba-KenCB272-0127JP
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)
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
Specific requirements for payment terms will vary according to terms negotiated by an account manager. An Amazon Integration Specialist will work with you to implement applicable terms.
Sample Data:
Basic NET Days ex.30 NET Days
ITD013***2001032330
Basic Net Days/% Discount ex. 2% 10, 60 NET Days
ITD0132200103151020010323*60
End of Month ex. Due 150 days from the end of month
ITD023***20010323150
Fixed Date/Discount: ex. 2% 15TH, 30 NET Days
ITD0332200103231520010323*30
Fixed Date: ex.15TH DUE
ITD0332001032310***15
Proximo / Proxy: ex. 2% 15 PROX 120
ITD0932200103231520010323*120
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)
- 03
- Fixed Date
- 09
- Proximo
- 23
- Payment Due Upon Receipt of Invoice
- 41
- Letter of Credit
Code identifying the beginning of the terms period
- 3
- Invoice Date
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
This field will contain the discount percent value as a whole number (no decimal point), which is good until the discount due date. Please see examples.
Formatting Notes: nnn
Date payment is due if discount is to be earned expressed in format CCYYMMDD
Date payment is due if discount is to be earned
Number of days in the terms discount period by which payment is due if terms discount is earned
This field will contain the number of calendar days from the Base Date until the discount is no longer valid.
Formatting Notes: nnn
Date when total invoice amount becomes due expressed in format CCYYMMDD
Date when total invoice amount becomes due.
Number of days until total invoice amount is due (discount not applicable)
This field will contain the number of calendar days from the Base Date until the total amount on the invoice is due.
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
Sample Data:
IT10011EA11.96NTUP025091005628POF6580987
IT10011EA60.75NTIB0895031892*PO*F6580987
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
This field will be a unique number related to this line item.
Formatting Notes: nnn
Number of units invoiced (supplier units)
This field will be the number of units related to this invoice. Quantity must be greater than zero (0).
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
The same unit of measurement code provided in the Amazon Purchase Order should be used.
- CA
- Case
- EA
- Each
- UN
- Unit
Price per unit of product, service, commodity, etc.
This field will be the cost of the item per unit.
Formatting Notes: nnnnn.nn
Code identifying the type of unit price for an item
- NT
- Net
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
- EN
- European Article Number (EAN) (2-5-5-1)
- IB
- International Standard Book Number (ISBN)
- UA
- U.P.C./EAN Case Code (2-5-5)
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
The value in this field must match the item identifier in the corresponding order file.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
A value in this field is optional and determined by the sender.
Formatting Notes: ASIN:nnnnnnnnnn
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PO
- Purchase Order Number
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
Sample Data:
TDS*2634
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.
Number of line items (CTT01) is the accumulation of the number of IT1 segments.
Hash total (CTT02) is the sum of the value of quantities invoiced (IT102) for each IT1 segment.
Sample Data:
CTT1010
CTT36
Total number of line items in the transaction set
This field will contain the logical count of IT1 segments in this 810.
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.
This field will be the total number of items being invoices (sum of all IT102).
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
ExampleFromProd-Extang
GS*IN*121633481E*AMAZON*20240124*0704*228437*X*004010~
ST*810*0001~
BIG*20240124*2657556*20240115*8DU8GFRK~
CUR*BT*USD~
N1*RI*TRUCK HERO EXTANG~
N3*5400 SOUTH STATE RD.~
N4*ANN ARBOR*MI*48108*US~
N1*ST*ABE8~
N3*401 Independence Road~
N4*Florence*NJ*8518*US~
N1*BT*ABE8~
N3*401 Independence Road~
N4*Florence*NJ*8518*US~
ITD*01*3*150*20240309**20240324*60~
IT1*1*33*EA*16.24*NT*VN*1140*BP*1140*PO*8DU8GFRK~
IT1*2*17*EA*22.39*NT*VN*1932*BP*1932*PO*8DU8GFRK~
IT1*3*1*EA*12.13*NT*VN*1181*BP*1181*PO*8DU8GFRK~
TDS*92868~
CTT*3*51~
SE*19*0001~
GE*1*228437~
IEA*1*000228436~
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.