The AmerisourceBergen 855 Purchase Order Acknowledgment, explained

What AmerisourceBergen expects in the 855

AmerisourceBergen trades on X12 4010 over AS2. Beyond the base standard, watch these:

How EDISQ maps it

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

Common rejection reasons

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

Sample AmerisourceBergen 855

A representative 855 interchange addressed to AmerisourceBergen — envelope, body segments, and control totals:

1ISA*00*          *00*          *ZZ*ACMESUPPLY     *ZZ*AMERISOURCEBERG*260101*1200*U*00401*000000001*0*P*>~
2GS*PR*ACMESUPPLY*AMERISOURCEBERG*20260101*1200*1*X*004010~
3ST*855*0001~
4BAK*00*AC*PO12345*20260101~
5PO1*1*24*EA*9.75**UP*012345678905~
6ACK*IA*24*EA~
7PO1*2*12*EA*14.50**UP*012345678912~
8ACK*IA*12*EA~
9CTT*2~
10SE*8*0001~
11GE*1*1~
12IEA*1*000000001~

FAQ