The Amazon Payee Central 850 Purchase Order, explained

What Amazon Payee Central expects in the 850

Amazon Payee Central trades on X12 4010 over AS2 or SFTP. Amazon Payee Central's 850 follows the standard X12 layout — no partner-specific companion-guide quirks are curated for this document yet. The certified base map covers the standard requirements, and validation still runs against the 850 spec before anything transmits.

How EDISQ maps it

The certified Amazon Payee Central 850 map loads when you enable the partner — fields auto-map from NetSuite, QuickBooks, Dynamics, and 33 other systems, validation runs against Amazon Payee Central's spec before transmission, and the sandbox replays Amazon Payee Central test scenarios until everything passes.

Common rejection reasons

Nearly all 850 rejections trace to reference data, not syntax: identifiers that don't match Amazon Payee Central's cross-references, echoed fields dropped from the original PO, or timing that misses the program window. EDISQ flags each before Amazon Payee Central ever sees the document.

Sample Amazon Payee Central 850

A representative 850 interchange addressed to Amazon Payee Central — envelope, body segments, and control totals:

1ISA*00*          *00*          *ZZ*ACMESUPPLY     *ZZ*AMAZONPAYEECENT*260101*1200*U*00401*000000001*0*P*>~
2GS*PO*ACMESUPPLY*AMAZONPAYEECENT*20260101*1200*1*X*004010~
3ST*850*0001~
4BEG*00*SA*PO12345**20260101~
5REF*DP*056~
6DTM*002*20260110~
7N1*ST*AMAZON PAYEE CENTRAL DC 5093*92*5093~
8PO1*1*24*EA*9.75**UP*012345678905~
9PID*F****ACME WIDGET 24CT~
10PO1*2*12*EA*14.50**UP*012345678912~
11PID*F****ACME GADGET 12CT~
12CTT*2~
13SE*11*0001~
14GE*1*1~
15IEA*1*000000001~

FAQ