Amazon 810 - Direct Fulfillment Invoice Specifications

Modified on Tue, May 26 at 9:48 AM

**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.com

Direct Fulfillment X12 810 Invoice

X12 / V4010 / 810: Invoice

Version: 2.2 Final

Field	Value
Company	Amazon.com
Created	1/12/2015
Modified	12/13/2023

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 (Remit-To)			200
070	N1	Name - Remit To 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-From)			200
070	N1	Name - Ship From Name	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	C	10			Used
		LOOP ID - SAC			25
040	SAC	Service, Promotion, Allowance, or Charge Info	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			Used
070	CTT	Transaction Totals	M	1		N3/070	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 — Always "00"	M	ID	2/2	Must use
ISA02	I02	Authorization Information — Always 10 blank spaces	M	AN	10/10	Must use
ISA03	I03	Security Information Qualifier — Always "00"	M	ID	2/2	Must use
ISA04	I04	Security Information — Always 10 blank spaces	M	AN	10/10	Must use
ISA05	I05	Interchange ID Qualifier (Vendor)	M	ID	2/2	Must use
ISA06	I06	Interchange Sender ID	M	AN	15/15	Must use
ISA07	I05	Interchange ID Qualifier — Always "ZZ"	M	ID	2/2	Must use
ISA08	I07	Interchange Receiver ID — Always "AMAZONDS"	M	AN	15/15	Must use
ISA09	I08	Interchange Date	M	DT	6/6	Must use
ISA10	I09	Interchange Time	M	TM	4/4	Must use
ISA11	I10	Interchange Control Standards Identifier — Always "U"	M	ID	1/1	Must use
ISA12	I11	Interchange Control Version Number — Always "00401"	M	ID	5/5	Must use
ISA13	I12	Interchange Control Number	M	N0	9/9	Must use
ISA14	I13	Acknowledgment Requested — Always "1"	M	ID	1/1	Must use
ISA15	I14	Usage Indicator — "P" for Production, "T" for Test	M	ID	1/1	Must use
ISA16	I15	Component Element Separator — Always ">"	M		1/1	Must use

Code List — ISA05 — Vendor Qualifier:

Code	Name
01	Duns (Dun & Bradstreet)
02	SCAC
08	UCC EDI Communications ID
14	Duns Plus Suffix
ZZ	Mutually Defined

Code List — ISA07:

Code	Name
ZZ	Mutually Defined

Code List — ISA12:

Code	Name
00401	Draft Standards for Trial Use – ASC X12 PRB through October 1997

Code List — ISA14:

Code	Name
1	Interchange Acknowledgment Requested

Code List — ISA15:

Code	Name
P	Production Data
T	Test Data

Segment Usage:

Only one ISA/IEA loop per data file is allowed.

Example:

ISA*00* *00* *ZZ*SENDERID *ZZ*AMAZONDS *231213*1813*U*00401*100038733*1*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 — Always "IN"	M	ID	2/2	Must use
GS02	142	Application Sender's Code (unique sender GS ID)	M	AN	2/15	Must use
GS03	124	Application Receiver's Code — Always "AMAZONDS"	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 (assigned by sender)	M	N0	1/9	Must use
GS07	455	Responsible Agency Code — Always "X"	M	ID	1/2	Must use
GS08	480	Version / Release — Always "004010"	M	AN	1/12	Must use

Code List — GS01:

Code	Name
IN	Invoice Information (810, 819)

Code List — GS07:

Code	Name
X	Accredited Standards Committee X12

Code List — GS08:

Code	Name
004010	Draft Standards Approved for Publication by ASC X12 PRB through October 1997

Segment Usage:

Only one GS/GE loop is allowed per data file.

Example:

GS*IN*SENDERID*AMAZONDS*20231213*1813*39733*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 — Always "810"	M	ID	3/3	Must use
ST02	329	Transaction Set Control Number (assigned by sender)	M	AN	4/9	Must use

Code List — ST01:

Code	Name
810	Invoice

Segment Usage:

Multiple ST/SE loops are only allowed if they are for the same message type.

Example:

ST*810*000000001~

BIG — Beginning Segment for Invoice

Pos: 020 | Max: 1 | Heading – Mandatory

Loop: N/A | Elements: 4 | Usage: Must use

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 (vendor's unique invoice number)	M	AN	1/22	Must use
BIG03	373	Date — Invoice Date repeated (CCYYMMDD)	M	DT	8/8	Must use
BIG07	640	Transaction Type Code — Always "CI"	M	ID	2/2	Must use

Code List — BIG07:

Code	Name
CI	Consolidated Invoice

Payment terms are calculated based on the Invoice Date. If an invoice has to be resent, the original Invoice Date must be sent. Invoice Date should be on or after the PO date.

Segment Usage:

This segment provides the invoice date and number.

Example:

BIG*20231213*SINV00050450*20231213****CI~

CUR — Currency

Pos: 040 | Max: 1 | Heading – Mandatory

Loop: N/A | Elements: 2 | Usage: Must use

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 — Always "BT"	M	ID	2/3	Must use
CUR02	100	Currency Code (ISO 4217)	M	ID	3/3	Must use

Code List — CUR01:

Code	Name
BT	Bill-to-Party

Code List — CUR02:

Code	Name
USD	US Dollar
CAD	Canadian Dollar
EUR	Euro
JPY	Japanese Yen
GBP	British Pound

Segment Usage:

This segment provides the currency code for the invoice.

Example:

CUR*BT*USD~

CUR*BT*CAD~

CUR*BT*EUR~

CUR*BT*JPY~

CUR*BT*GBP~

N1 — Name (Remit-To)

Pos: 070 | Max: 1 | Heading – Mandatory

Loop: N1 | Elements: 4 | 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 — Always "RI"	M	ID	2/3	Must use
N102	93	Name (vendor's remit-to name)	M	AN	1/60	Must use
N103	66	Identification Code Qualifier — Always "92"	M	ID	1/2	Must use
N104	67	Identification Code (vendor Payee Code from Amazon onboarding)	M	AN	2/80	Must use

Code List — N101:

Code	Name
RI	Remit To

Code List — N103:

Code	Name
92	Assigned by Buyer or Buyer's Agent

N104 is a five-character alpha-numeric Payee code provided by Amazon during the direct fulfillment onboarding process. This is NOT your regular Amazon vendor code.

Example:

N1*RI*VendorRemitToName*92*PAYE1~

N2 — Additional Name Information

Pos: 080 | Max: 2 | Heading – Optional

Loop: N1 | Elements: 1 | 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 (vendor remit-to name if different from N1)	M	AN	1/60	Used

Example:

N2*ABC Company~

N3 — Address Information

Pos: 090 | Max: 2 | Heading – Mandatory

Loop: N1 | Elements: 1 | 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 (vendor's remit-to address)	M	AN	1/55	Must use

Amazon's AP department will verify that the remit-to address provided via N3 and N4 matches the address on file. If the addresses do not match, the invoice will fail to process.

Example:

N3*705 5TH AVE S~

N4 — Geographic Location

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 (vendor's remit-to city)	M	AN	2/30	Must use
N402	156	State or Province Code (vendor's remit-to state)	M	ID	2/2	Must use
N403	116	Postal Code — 5 to 9 digit ZIP/postal code	M	ID	3/15	Must use
N404	26	Country Code (ISO 2-character)	M	ID	2/3	Must use

Example:

N4*SEATTLE*WA*981054425*US~

N1 — Name (Ship-From)

Pos: 070 | Max: 1 | Heading – Mandatory

Loop: N1 | Elements: 4 | Usage: Must use

Purpose: To identify the vendor warehouse that the order(s) shipped from

Element Summary:

Ref	Id	Element Name	Req	Type	Min/Max	Usage
N101	98	Entity Identifier Code — Always "SF"	M	ID	2/3	Must use
N102	93	Name — Amazon warehouse code (typically 4-character alpha, e.g. ABCD)	M	AN	1/60	Must use
N103	66	Identification Code Qualifier — Always "92"	M	ID	1/2	Must use
N104	67	Identification Code — Same Amazon warehouse code as N102	M	AN	2/80	Must use

Code List — N101:

Code	Name
SF	Ship From

Code List — N103:

Code	Name
92	Assigned by Buyer or Buyer's Agent

Segment Usage:

Use the warehouse code configured by Amazon for your account in N102 and N104. This code differs from your regular vendor code and must match the rest of the message flow (PO, POA, ASN).

Example:

N1*SF*WHSE*92*WHSE~

ITD — Terms of Sale / Deferred Terms of Sale

Pos: 130 | Max: >1 | Heading – Mandatory

Loop: N/A | Elements: 12 | 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 — Always "01"	M	ID	2/2	Must use
ITD02	333	Terms Basis Date Code — Always "3"	M	ID	1/2	Must use
ITD03	338	Terms Discount Percent	O	R	1/6	Used
ITD04	370	Terms Discount Due Date (CCYYMMDD)	O	DT	8/8	Used
ITD05	351	Terms Discount Days Due	O	N0	1/3	Used
ITD06	446	Terms Net Due Date (CCYYMMDD)	O	DT	8/8	Used
ITD07	386	Terms Net Days (required)	M	N0	1/3	Must use
ITD08	362	Terms Discount Amount	O	N2	1/10	Used
ITD09	388	Terms Deferred Due Date	O	DT	8/8	Used
ITD10	389	Deferred Amount Due	O	N2	1/10	Used
ITD11	342	Percent of Invoice Payable	O	R	1/5	Used
ITD12	352	Description (free-form, e.g. "NET 30")	M	AN	1/80	Must use

Code List — ITD01:

Code	Name
01	Basic

Code List — ITD02:

Code	Name
3	Invoice Date

Example:

ITD*01*3*****30*****NET 30~

IT1 — Baseline Item Data (Invoice)

Pos: 010 | Max: 1 | Detail – Mandatory

Loop: IT1 | Elements: 13 | 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 Item ID (same as 850 PO101)	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 — Always "EA"	M	ID	2/2	Must use
IT104	212	Unit Price	M	R	1/17	Must use
IT105	639	Basis of Unit Price Code — Always "NT"	M	ID	2/2	Must use
IT106	235	Product/Service ID Qualifier — Always "SK"	M	ID	2/2	Must use
IT107	234	Product/Service ID — SKU (same as PO107 in corresponding 850)	M	AN	1/48	Must use
IT108	235	Product/Service ID Qualifier — Always "PO"	M	ID	2/2	Must use
IT109	234	Product/Service ID — Amazon encrypted Ship ID / PO Number (from BEG03 of 850)	M	AN	1/48	Must use
IT110	235	Product/Service ID Qualifier — Always "VO"	O	ID	2/2	Used
IT111	234	Product/Service ID — Vendor Order Reference Number (sales order number; must match POA and ASN)	M	AN	1/48	Must use
IT112	235	Product/Service ID Qualifier — Always "ON"	M	ID	2/2	Must use
IT113	234	Product/Service ID — Amazon 19-digit customer order number (e.g. 123-1234567-1234567)	M	AN	1/48	Must use

Code List — IT103:

Code	Name
EA	Each

Code List — IT105:

Code	Name
NT	Net

Code List — IT106:

Code	Name
SK	Stock Keeping Unit (SKU)

Code List — IT108:

Code	Name
PO	Purchase Order Number

Code List — IT110:

Code	Name
VO	Vendor's Order Number

Code List — IT112:

Code	Name
ON	Customer Order Number

IT101 must match the Line Item ID from the corresponding 850. The combination of PO101 and PO107 must remain constant throughout the order cycle and across messages.

Example:

IT1*1*1*EA*18.04*NT*SK*1617*PO*TesT0008139*VO*SO00067877*ON*000-0000000-0008148~

TXI — Tax Information (Detail)

Pos: 040 | Max: 10 | Detail – Conditional

Loop: IT1 | Elements: 3 | Usage: Used

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	X	R	1/18	Used
TXI03	954	Percent (expressed as a decimal)	X	R	1/10	Used

Code List — TXI01:

Code	Name
GS	Goods and Services Tax
ST	State Sales Tax (Québec only)
VA	Value Added Tax
ZZ	Mutually Defined

MANDATORY for all vendors in Australia, Japan, and Canada. DO NOT use for US marketplace — any US invoice with the TXI segment will fail to be processed. The line item level TXI segment must be provided for every invoiced item, even if tax is not applicable (use 0% rate).

Example:

TXI*GS*7.45*7~

TXI*ST*14.86*9.975~

TXI*GS*0*0~

SAC — Service, Promotion, Allowance, or Charge Information (Detail)

Pos: 040 | Max: 1 | Detail – Optional

Loop: SAC | Elements: 3 | Usage: Used

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 — Always "C"	C	ID	1/1	Used
SAC02	1300	Service, Promotion, Allowance, or Charge Code	C	ID	4/4	Used
SAC05	610	Amount (N2 format)	C	N2	1/15	Used

Code List — SAC01:

Code	Name
C	Charge

Code List — SAC02:

Code	Name
B790	Crafting — use for Gift Wrap fees
D240	Freight — inbound transportation charges only (not customer shipping)
D500	Handling — use for Fulfillment Fees; also for US environmental/excise taxes (HI, CO)
E170	Labeling — use for Marketing Insert Fees
F155	Packaging — use for Packaging Fees
G821	Shipping — carrier charges when Amazon accounts are not used (e.g. USPS)

Example:

SAC*C*D500***45~

SAC*C*B790***75~

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 invoice amount (N2: implied 2 decimal places)	M	N2	1/15	Must use

Segment Usage:

Total Invoice Amount = Line-item total + Taxes + Charges – Allowances. N2 data type: $18.04 is sent as 1804.

Example:

TDS*1804~

TXI — Tax Information (Summary)

Pos: 020 | Max: 10 | Summary – Conditional

Loop: N/A | Elements: 7 | Usage: Used

Purpose: To specify summary 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	X	R	1/18	Used
TXI03	954	Percent (expressed as a decimal)	X	R	1/10	Used
TXI05	956	Tax Jurisdiction Code	O	AN	1/10	Used
TXI06	441	Tax Exempt Code	X	ID	1/1	Used
TXI08	828	Dollar Basis For Percent	O	R	1/9	Used
TXI09	325	Tax Identification Number (vendor registered business TAX ID)	C	AN	1/20	Used

Code List — TXI01:

Code	Name
GS	Goods and Services Tax
ST	State Sales Tax (Québec only)
VA	Value Added Tax
ZZ	Mutually Defined

MANDATORY for all vendors in Europe, Australia, Japan, and Canada. DO NOT use for US marketplace. TXI09 is required for Canada (GST/HST/QST ID), Australia (ABN), Europe (VAT ID), and Japan (JCT ID). For Québec CA vendors, two TXI summary segments are needed: one for GST/HST ID and one for QST ID.

Example:

TXI*GS*9.15*5*****183*VENDORTAXID~

TXI*ST*18.25*9.975*****183*VENDORTAXID~

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 (total IT1 segments)	M	N0	1/6	Must use
CTT02	347	Hash Total (total number of units — sum of all IT102)	M	R	1/10	Must use

Example:

CTT*1*1~

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 (same as ST02)	M	AN	4/9	Must use

Segment Usage:

Multiple ST/SE loops are only allowed if they are for the same message type.

Example:

SE*12*000000001~

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 (same as GS06)	M	N0	1/9	Must use

Segment Usage:

Only one GS/GE loop is allowed per data file.

Example:

GE*1*39733~

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 (same as ISA13)	M	N0	9/9	Must use

Segment Usage:

Only one ISA/IEA loop per data file allowed.

Example:

IEA*1*100038733~