Sources checked: October 29, 2026
B2B Inbound EDI Advance Shipment Notices / DESADV: PO Matching and Receipt Reconciliation
An advance shipment notice (ASN) tells a buyer what a supplier reports as shipped or ready to ship. It gives receiving teams an expectation to match against purchase orders and, later, the goods they handle. Receiving a notice, parsing it successfully, or importing its contents does not prove physical receipt.
For Educational and Informational Purposes Only — Not Legal or Financial Advice.
Commerce Systems Review is a free, vendor-neutral research library. This guide is general technical education for B2B commerce teams. It does not provide legal, tax, accounting, financial, security, performance, pricing, compliance, or individualized implementation advice. Message detail, package hierarchy, receipt states, and correction procedures depend on trading-partner agreements and the configured systems.
Sources checked: October 29, 2026.
Keep the scope on inbound shipment expectations
This guide follows an inbound supplier notice through PO and line correlation, supported shipment packaging detail, comparison with physical receipt, and reconciliation of notice or receiving exceptions. It covers ordinary inbound supply to a receiving facility. Return authorization and disposition belong to the reverse-logistics guide; delivery appointments and carrier evidence belong to the freight handoff guide. A carrier delivery event also does not establish the received item quantity.
DESADV is a despatch advice message, rather than a universal name for every ASN payload. The checked GS1 EANCOM 2002 S4 DESADV document defines goods despatched or ready for despatch under agreed conditions and says the advice should precede physical delivery. It supports detailed consignment contents and an optional hierarchy. That edition can also describe returns; this guide narrows its use to inbound supplier shipments. Microsoft and Oracle examples below describe their own import and receiving workflows, not a required DESADV implementation or an interchangeable schema.
Establish separate checkpoints and owners
Record what each checkpoint actually proves. Use local states such as notice received, validated, PO/line matched, expected shipment available to receiving, physically counted, receipt recorded, and discrepancy resolved only when the corresponding evidence exists. These are operating distinctions, not standardized status codes.
| Checkpoint | Evidence and owner to retain |
|---|---|
| Notice ingestion | Partner, source message/control identifiers, received time, payload reference, selected map/profile, and validation result; integration owner. |
| Expected shipment | Supplier notice/shipment identity, destination, matched PO lines, quantities and units, and supported packaging references; procurement and receiving planners. |
| Physical receipt | Actual site, receipt event, arrival/count time, scanned package references, items and quantities observed; receiving owner. |
| System receipt and reconciliation | Saved receiving transaction references, unresolved differences, approved corrections, and downstream confirmation; receiving-system and procurement owners. |
A syntax result reports the parsing or validation checks performed. It does not establish that the intended PO exists or that a warehouse counted the shipment. Give rejected, unmatched, or partially imported messages their own visible outcome instead of treating a completed job as a complete shipment expectation.
Correlate the notice to purchase orders and lines
Match within the trading relationship and receiving context. Preserve original source values beside normalized internal keys so an operator can explain how a match was made.
- Partner and shipment: sender/receiver identities and qualifiers, supplier/site, notice number, supplier shipment reference, message function or revision where supported, and destination warehouse.
- PO scope: buyer PO number, relevant revision or schedule where supplied, and the receiving system's PO identity. Check the current approved order and retain which version was compared.
- Line scope: PO line or schedule reference, item identifier and qualifier, variant or other required dimensions, shipped quantity, and unit of measure. A notice line number need not be a PO line number.
- Package scope: parent/child references and package or logistics-unit identifiers only at the detail the partner supplies. Keep each item's allocation to the appropriate PO line and package when supported.
- Time and processing: document time, reported despatch time, expected arrival, actual message arrival, map/profile release, import result, and downstream shipment/receipt references. Preserve source time-zone conventions and the interpretation used locally.
Do not match from product description alone. The same item can appear on several PO lines or schedules, one shipment can cover multiple POs, and a PO line can be split across several notices and receipts. If a line reference is absent, use only an agreed and unambiguous alternative matching rule. Route ambiguous PO, line, supplier, destination, item, or unit mappings for review before attaching quantities to an order.
Compare the announced quantity with the relevant open order balance and prior accepted notices. A discrepancy may reflect a split shipment, an order amendment, an incorrect reference, or an overlap with an earlier notice. The ASN does not itself amend the PO. Use the PO amendment and seller-response guide for that separate decision process.
Preserve the hierarchy the partner actually supports
GS1's checked DESADV introduction describes shipment-to-item hierarchy through packaging levels agreed by the partners. It explicitly says describing the shipment hierarchy is not mandatory: an item-and-total-quantity representation is also possible. Its examples progress from item totals to identified cartons and pallet/carton content. Do not infer a carton-to-pallet relationship from carton identifiers alone.
Agree the supported levels, parent references, logistics-unit identifiers, item/quantity placement, units, and correction semantics in the partner implementation guide. Where SSCCs are used, retain the supplied Serial Shipping Container Code with its scope and package relationship. A hierarchy sequence reference is not automatically the physical package identifier.
A local representation might retain shipment → pallet → carton → item allocations, while a less detailed partner supplies shipment → item totals. Mark unavailable package detail explicitly. Do not fabricate missing cartons or require a pallet layer for a floor-loaded shipment. Validate parent references, repeated package identities, unsupported levels, and totals using the agreed representation. Parent summaries and child item quantities can describe the same goods; choose the authoritative counting level so they are not added twice.
Illustrative receiving example, not EDI syntax: notice S-17 announces 24 each for PO P-100 line 10. The supported hierarchy places two cartons, C-1 and C-2, on pallet L-1, with 12 each in each carton. The shipment total and pallet summary describe those same 24 units. If C-1 contains 12 and C-2 contains 10 at physical count, record 22 received and a 2-unit discrepancy against this notice. If the PO ordered 40 and this is its first shipment, the remaining 16 not announced by S-17 are a separate open PO balance; they are not the shortage in these two cartons. Later notices and receipts need their own references.
Compare expected contents with the physical result
Make the expectation available to receiving without giving it authority to overwrite the count. Match scanned or recorded logistics units to the notice where supported, then compare item identity, PO line, quantity, unit, destination, and relevant lot/serial detail at the granularity the operation actually observes. Scanning a pallet label alone does not verify every item's quantity or condition.
Keep announced, physically observed, registered or recorded, and still-unresolved quantities separate. Record a partial arrival with its own receipt reference and retain the expected remainder. Preserve evidence of extra, missing, wrong, or damaged contents; an aggregate shipment total can hide one short item and another excess item. Inspection or availability release remains a separate local process, connected to the inventory availability guide.
Reconcile in both directions: accepted notices without corresponding receipts, and receipts without matching notices. A notice may precede the goods, arrive after receiving, or never arrive; receipt data may also be delayed in the interface. Compare document/event occurrence times with ingestion times before classifying a record as physically late. Set review windows from the partner agreement and the receiving operation, not a universal deadline.
Route exceptions with a next action and closure evidence
| Exception | Review and ownership |
|---|---|
| Goods arrive without an ASN | Receiving records the physical observation through its supported exception process; procurement/partner coordinator investigates the missing notice. Retain temporary correlation evidence and reconcile a later ASN before creating another expectation or receipt. |
| ASN exists, no receipt by the expected window | Receiving/transport coordination checks actual arrival and local receipt records; integration checks delayed processing. Keep missing goods distinct from a missing system update. |
| Duplicate notice or repeated receipt event | Integration compares partner/business identity and prior result. An exact repeat links to the original; a conflicting payload goes to review. Check whether the destination already saved a receipt before retrying a write. |
| Partial notice, shipment, or receipt | Procurement and receiving distinguish an intentionally announced part of a PO from short physical contents or a partial import. Retain the remaining quantities at each scope and each receipt reference. |
| PO/line/item/unit/destination mismatch | Mapping owner or procurement resolves identity and approved scope; receiving preserves what arrived. Record authorized unit conversions rather than silently equating cases and eaches. |
| Package hierarchy mismatch | Receiving compares observed package labels/content with the supplied structure; partner/mapping owner checks repeated or missing parents, unknown cartons, or unsupported detail. Do not reassign goods to a plausible package without evidence. |
| Late notice, late goods, or late receipt update | Compare source and ingestion times, check what already happened, and assign partner, receiving, transport, or integration follow-up according to the cause. A late ASN must not recreate an already recorded receipt. |
| Corrected or replacement notice after processing | Follow the partner's documented message-function and reference rules. Preserve the original expectation and prior receipts; review affected quantities before replacing an expectation or applying any new system action. |
Each case should retain partner, notice, PO/line, package where known, expected versus observed quantity, units, site, timestamps, import/receipt results, reason, next owner, and review state. Close only after the source decision, saved correction or linked receipt, and affected downstream records can be reconciled. A retransmission request, a new notice, and a receiving correction are distinct operations. Avoid blind replay when the first result is uncertain.
Product-specific examples and source limits
Microsoft Dynamics 365 Supply Chain Management: the checked ASN import page documents Inbound ASN V3/V5 composite entities for asynchronous integration, including XML examples. This import applies to WMS-enabled items and requires a purchase or inbound shipment order already registered in the system. Only V5 supports inbound shipment orders. Its examples include purchase-order/item/quantity/unit references and optional case detail; the review procedure exposes load lines and packing structure with pallets, cases, items, and quantities. This is Dynamics 365's entity model, not DESADV wire syntax or a universal hierarchy.
Microsoft's separate product-receipt page distinguishes ASN preregistration, registration when products arrive, and recording products as Received. Its product-receipt workflow allows line quantities to reflect under- or over-delivery. The page also covers other scenarios, including direct delivery; those do not establish a physical count at this guide's inbound warehouse. An imported ASN is an expectation, and an administratively posted receipt still needs the physical evidence appropriate to the operation.
Oracle SCM Cloud 26C: its Advance Shipment Notice Inbound page describes supplier shipment advice in the procure-to-pay business process. The Process Shipment Inbound document has a Retrieve Supplier Site from PO option; selecting it uses the payload PO number to find the supplier site. Incoming data uses Staged Receiving Transaction Interface Version 2, and a scheduled process is needed before ASN information is visible in Manage Inbound Shipments. The page lists cXML and OAGIS definitions. This establishes Oracle-specific configuration and processing checkpoints; it does not document a universal DESADV map or prove delivery when the ASN becomes visible.
GS1 EANCOM 2002 S4 DESADV, Edition 2016 updated 2021: the definition and introduction support pre-delivery advice, optional agreed packaging hierarchy, identified logistics units, and cross-checking physical shipment against the message. This guide uses those principles and illustrative structures, not a complete segment map or a claim that every partner supports every level. Recheck the partner's exact subset and implementation guide before configuration.
Test the correlation and reconciliation path
In a controlled test context, exercise one PO/one notice, several POs in a shipment, repeated items on different PO lines, a PO line split across notices, a totals-only partner, supported pallet/carton detail, a broken parent reference, a unit mismatch, a partial import, a short physical receipt, goods without a notice, a notice without goods, duplicate notice and receipt events, a late notice after receipt, and a replacement notice after partial receipt.
For each case, specify expected matching, counted quantity, allowed system action, unresolved remainder, exception owner, and closure evidence. Verify that parsing, import visibility, physical count, saved receipt, and reconciliation remain distinguishable. The 3PL onboarding guide and OMS architecture guide cover broader provider and state ownership.
First-party source register
All four official references were opened live and checked on October 29, 2026. Microsoft pages displayed updates of May 6, 2026 and January 27, 2026 respectively. Oracle's page is versioned 26C; no page-specific update date was displayed. GS1's PDF identifies Edition 2016 updated 2021. These source dates are separate from this guide's review date; no newer publication date or universal capability is inferred.
- Microsoft Dynamics 365 SCM: Import inbound ASNs through data entities — checked October 29, 2026
- Microsoft Dynamics 365 SCM: Product receipt against purchase orders — checked October 29, 2026
- Oracle SCM Cloud 26C: Advance Shipment Notice Inbound — checked October 29, 2026
- GS1: EANCOM 2002 S4 DESADV — Edition 2016 updated 2021 (PDF), checked October 29, 2026
Editorial and education-only note
This is free, vendor-neutral educational technical research. It does not provide legal, tax, accounting, financial, security, performance, pricing, compliance, or individualized implementation advice. Confirm current first-party documentation, partner agreements, product configuration, and local receiving requirements with the responsible teams. Notice receipt and syntax parsing are not proof of physical receipt.
Continue reading
Automation and integrations
B2B EDI Purchase-Order Amendments During Fulfillment: Seller Responses and Safe Change Control
Read guideFulfillment operations
B2B 3PL Integration Onboarding and Multi-Provider Fulfillment Exceptions
Read guideFulfillment operations
B2B Freight Delivery Appointments and Proof of Delivery
Read guideFulfillment operations
B2B Inventory Availability: Reservations, ATP, and Reconciliation
Read guideFulfillment operations
Order Management System Architecture: Routing, Inventory, and Exceptions
Read guideFulfillment operations
B2B Reverse Logistics: Return Identity, Receipt, and Disposition
Read guideFulfillment operations