Skip to content
Independent EDI conversion and validation software. Retailer names identify interoperability targets; no retailer endorsement is implied.
Shipment Sentry
Start routing

Operational EDI reference

EDI 855 Purchase Order Acknowledgement Example

Connect BAK and PO1/ACK responses to the original 850 and identify rejected, changed or accepted lines.

Use the free validator See batch and API plans

Direct answer

Direct answer

An X12 855 communicates a seller response to an 850 purchase order. BAK carries the purpose, acknowledgement type and referenced order. PO1 identifies the line, while ACK can communicate acceptance status, quantity and date. A header acceptance should not hide a rejected or changed line, so the 855 must be reconciled line by line with the original order and routed for review when quantity or promise dates change.

Why a parser is not enough

The useful unit is not a file that parses; it is a business document with a known decision, an owner, a source trail and a matched downstream response. This page connects the technical structure to that operating workflow.

What the control should check

  1. 01Match BAK03 to the 850 purchase-order number.
  2. 02Interpret header and line acknowledgement codes separately.
  3. 03Match PO1 lines by qualifier and identifier.
  4. 04Compare acknowledged quantity with ordered quantity.
  5. 05Escalate rejected or date-changed lines to an owner.

Working example

BAK*00*AC*PO-77821*20260718~PO1*1*12*EA*18.50**BP*SKU-104~ACK*IA*12*EA~

The excerpt is intentionally compact. Use the working validator or authenticated gateway with the complete interchange to obtain a decision.

Failure modes worth catching

  • A transport receipt is mistaken for business acceptance.
  • Control identifiers are regenerated between validation and submission.
  • A warning has no owner and becomes a recurring manual investigation.
  • The document is checked alone even though the truth exists in a purchase order, label or acknowledgement.

Put it into the dispatch workflow

  1. 1Validate the source document before transport.
  2. 2Block deterministic failures and assign every review item.
  3. 3Release with a recorded owner and timestamp.
  4. 4Match functional and application acknowledgements.
  5. 5Reconcile confirmed outcomes back into fixtures and rules.
Use batch validation and acknowledgement tracking

Questions

Implementation answers

Does Shipment Sentry replace my EDI provider?

No. It sits before the existing transport as a validation and evidence sidecar.

What does cleared mean?

The document has no blocking finding in the current rule pack. It is not a guarantee of trading-partner or receiving acceptance.

How are repeat requests kept safe?

The API requires an idempotency key, stores only a token hash, scopes every record to one workspace and rejects reuse with different content.

Sources and limits

Reviewed 2026-07-18. Public references cannot establish every partner-specific rule. Current implementation guides and agreements remain controlling.

Keep investigating

Related EDI controls

View the library
Add an EDI API gate without rebuilding partner operations Connect Business Central records to controlled EDI delivery Send EDI over AS2 without mistaking HTTP success for delivery proof Connect validated invoices to a certified Peppol access point Turn EDI partner testing into a versioned release gate Give EDI users reports that lead back to transaction evidence