Verified transaction set reference
Amazon EDI 855 Purchase Order Acknowledgment Validation
Acknowledgement defects become fulfilment defects because the 856 and invoice are often generated from what the supplier believes it accepted. Cross-document checks catch over-acceptance, stale revisions, unknown items and inconsistent dates before warehouse work begins.
Direct answer
Direct answer
An 855 should be validated as a response to a specific current 850, not as an isolated file. Every acknowledged item, quantity, status, date and reason must resolve to the active purchase order; the acknowledgement must not accept more than ordered or silently omit a line the workflow expects to address.
What to check
- Resolve the acknowledgement to one active purchase order.
- Compare every response line with the matching ordered line.
- Prevent acknowledged quantity from exceeding ordered quantity.
- Validate accepted, rejected and changed status semantics.
- Explain rejected or changed lines with the required reason.
- Persist the final accepted quantity for shipment reconciliation.
Accepted shape
PO1001 line 1 ordered 12 EA; the 855 accepts 10 EA and records the remaining disposition explicitly.Rejected shape
PO1001 line 1 ordered 12 EA; the 855 accepts 15 EA or refers to an item absent from the current order.How to fix it
Join the 855 to the current 850 snapshot by partner, PO and item identity; compute the permitted response from order state; reject unexplained omissions and over-acceptance; then publish one versioned acknowledgement state for fulfilment.
Evidence boundary
Amazon's public API guidance establishes key order-acknowledgement business rules, while exact X12 segment usage remains account-guide and licence controlled. The current validator does not yet claim full 855 conformance.
Sources