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 856 ASN Example with Shipment Hierarchy

Read BSN, HL, PRF, MAN, LIN and SN1 as one shipment hierarchy instead of validating isolated segments.

Use the free validator See batch and API plans

Direct answer

Direct answer

An X12 856 advance ship notice describes a hierarchy, commonly shipment, order, pack and item. BSN identifies the ASN, HL01 identifies each node, HL02 points to its parent, and HL03 declares the level. PRF ties an order loop to a purchase order, MAN carries container identifiers, LIN identifies an item and SN1 carries shipped quantity. A valid-looking segment can still sit under the wrong parent, so hierarchy validation is essential.

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. 01Require unique, ordered HL01 values.
  2. 02Require every non-root HL02 parent to exist earlier.
  3. 03Confirm the agreed HL03 profile.
  4. 04Reconcile PRF, LIN and SN1 with the 850.
  5. 05Validate MAN SSCC check digits against physical labels.

Working example

BSN → HL(S) → HL(O)+PRF → HL(P)+MAN → HL(I)+LIN+SN1

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