01Establish identity, scope and version
Give every notice a unique sender-controlled number, creation time, status and version. Identify supplier, consignor, buyer, consignee, ship-from and ship-to using validated master data. Link the purchase order, release, transfer, booking, shipment and despatch references without assuming they are interchangeable. Define whether the notice covers the entire order, one partial shipment, several orders in one consignment or one destination from a split movement. UNECE DESADV is intended to communicate detailed contents of goods despatched or ready for despatch and can cover items and packages; that scope is narrower than an open order forecast. Prevent the same physical load from receiving two active ASN identities through portal, email and EDI. Preserve superseded versions with reason, sender, recipient and effective time rather than overwriting them. A receiver should be able to tell which version was accepted for planning and which correction arrived after work had started.
02Match authorized order and shipment facts
Compare each ASN line with the latest approved order or release: item, buyer and supplier codes, description where needed, unit, ordered quantity, approved substitute, destination and requested date. Record packed and shipped facts separately from ordered, backordered and previously shipped quantities. If the supplier combines purchase orders, retain allocation by order and line. If one order is split, identify the current part and remaining expectation without presenting the remainder as packed. Validate carrier, mode, route, service, booking, equipment, container, trailer and seal only from the actual movement record. Do not invent a transport reference to satisfy a required field. Check that despatch time precedes expected arrival and that both include an agreed time-zone interpretation. Escalate a destination, currency, terms or ownership conflict to the responsible commercial or logistics owner; an ASN must not silently amend the purchase order or transport agreement.
03Build the package and item hierarchy
Represent the physical structure in the order receiving will encounter it: consignment, pallet or master package, carton or inner package and item. Give each identifiable logistic unit one package ID and one parent where a hierarchy exists. Record package type, count, marks, label identity, measured weight or dimensions only when verified, and handling data required by the agreed process. Under each package, assign item, lot, batch, serial, expiry or other trace data only when the product and control plan require it. UNECE DESADV provides a top-down consignment packing sequence and supports package identity, quantities and item detail. GS1 EPCIS can then connect the identified objects with packing, shipping and receiving events. Reject circular parentage, orphan cartons, a child assigned to two pallets, duplicated serials and package IDs reused inside the active traceability period.
04Reconcile quantities, units and control totals
Normalize each unit before comparing numbers. Distinguish pieces, pairs, cartons, cases, kilograms and other units; never multiply by a pack factor that has not been validated. Sum item quantities inside every package, package counts inside every parent and line totals across the shipment. Compare the result with packed output and the authorized order. Record shortage, overage, substitution, sample, free-of-charge unit and backorder as explicit states rather than forcing totals to match. Use control totals for line count, package count and quantity where the trading setup supports them. Check that weight and volume are plausible only as exception signals, not as proof of contents. A clean shipment-level total can still hide a carton assigned to the wrong item or destination, so sample and automated checks must operate at several hierarchy levels. Keep rounding rules and quantity tolerance visible and approved.
05Validate dates, readiness and transmission
Record notice creation, packing completion, despatch, carrier collection and estimated arrival as separate events. Identify the source and time zone of each operational date. Test the arrival estimate against the planned movement without claiming precision the carrier has not provided. Confirm that required commercial, transport, customs, inspection, security or product documents are present or visibly pending under the applicable workflow. Transmit through the agreed channel, validate technical acknowledgement where used and retain the exact payload or rendered notice received by the buyer. An accepted syntax response proves message handling, not physical accuracy. Send early enough for receiving to assign a dock, labor, equipment, inspection, quarantine and putaway path, but do not send guessed package detail simply to meet a lead-time target. Protect personal contact and shipment security information according to need and policy.
06Control corrections and late changes
Define states such as draft, validated, sent, acknowledged, replaced, canceled, departed and received. When the load changes, issue a linked correction that identifies the prior notice, changed fields, reason and effective time. Revalidate the full hierarchy and totals because a single removed carton can affect parent counts, line quantities and weight. Notify receiving when the correction changes dock capability, inspection scope, storage, destination or arrival. Do not delete the earlier notice after receiving has planned against it. Prevent a correction sent after receipt from being treated as prior notice; classify it as late and reconcile it as evidence of process failure. If the transport departs before complete data is available, send only the facts supported by policy and surface the missing data with owner and deadline rather than manufacturing completeness.
07Reconcile receipt and improve accuracy
At receiving, compare the last accepted ASN with actual vehicle or container, seal where used, package IDs, labels, package count, item, lot or serial, quantity, unit, condition and arrival time. UNECE RECADV supports reporting physical receipt and discrepancies against despatch information. Keep expected, advised, physically received, accepted, held, rejected and returned values separate. Close the ASN only when every advised package and line has a received or explained final status and every unexpected package has an exception record. Measure on-time transmission, first-version accuracy, package-ID match, line and quantity match, arrival estimate variance, correction rate and unadvised receipt. Analyze by supplier, facility, message channel and error type. Sample apparently perfect notices against physical evidence so automatic matching does not reward copied order quantities. Feed recurring label, unit, pack-master, order-change and transport-reference failures to the upstream owner.