An advance shipping notice is wrong for one of five reasons, and four of them are synchronisation failures rather than mistakes anybody made. The label came from one system and the notice from another. The shipment data was captured before the pick changed. The message went out after the truck arrived. The hierarchy described a pack structure the trailer did not contain. None of that is carelessness at the supplier — it is an architecture in which the document describing the goods is assembled separately from the process that moves them. Published analysis of the failure pattern reaches the same conclusion repeatedly: most compliance problems trace not to a single bad document but to a chain of manual handoffs between disconnected systems. Which means an accuracy programme built on supplier training will underperform one built on where the data comes from. Request an enterprise demo to see reconciliation running against your own receipts.
Inbound Logistics · ASN Accuracy
ASN Accuracy Improvement Programmes
Mismatches sorted into categories that point at a cause rather than a culprit, receipts reconciled through a standard discrepancy message instead of email, root causes traced back to the system that generated the data, and an escalation path suppliers can see coming.
Delivery schedule
›
Despatch advice
›
Goods receipt
›
Discrepancy advice
›
Invoice match
What the Notice Is Actually Carrying
Three jobs, and the second is the one most accuracy programmes forget exists.
Confidence and receiving preparation
It tells the customer that parts required for production will arrive on time, lets them prepare the reception, and enables the goods receiving process to be automated rather than performed against a paper note at the dock.
Instructions for the transport provider
The despatch advice can also be sent to the service provider moving the parts, which matters particularly where cross-dock activity is involved. A notice that only reaches the customer leaves the intermediate handler working from something else.
The basis for getting paid
On the supplier side it serves as the basis for the subsequent invoicing process, enabling automatic matching and removing delays in payment. That connection is why an accuracy problem is never only a logistics problem — an invoice arriving without a corresponding notice sits in manual review, and the supplier's cash position is the first thing to notice.
Five Mismatch Categories, and What Actually Causes Them
Sorting failures by category rather than by supplier is what turns a complaint into a fix, because each category has a different origin and a different remedy.
Swipe to see all columns
| Category | What receiving sees | Usual root cause | The fix |
|---|---|---|---|
| Handling unit mismatch | The label scans and no matching record exists in the notice, so the unit cannot be received automatically | Labels generated from one system and notice data from another, with the two not synchronised | Generate the label and the notice data from the same source, so a mismatch is not possible to create |
| Quantity discrepancy | Advised quantity does not match the physical count, so the three-way match between schedule, notice and shipment cannot close | Data captured before the pick was finalised, or a late change not reflected back into the message | Build the notice from confirmed pick and pack data rather than from the order |
| Timing violation | The notice arrives after the shipment, so receiving could not be planned against it | Manual review inserted between generation and transmission, delaying the send past the window | Automate validation so checking does not cost transmission time |
| Missing or invalid data | Mandatory fields absent, identifiers not recognised, or references that do not resolve | Manual creation, stale order data, or a field the customer requires that the supplier's template omits | Validate against the customer's specific implementation before sending, not after rejection |
| Hierarchy error | The described structure of shipment, order, pack and item does not match the physical build of the load | Pack structure assembled independently of the message structure | Derive the hierarchy from the actual packing operation rather than restating the order |
Read the root cause column and a pattern emerges. Four of the five originate in a gap between systems rather than in an error of judgement — which is why supplier training produces a temporary improvement and an architectural change produces a permanent one. The governing principle across all of them is the same: the notice should be generated from the same fulfilment and shipment data that controls the physical movement of the goods.
The Single Change That Fixes Most of It
Worth isolating, because it addresses several categories at once and it is a design decision rather than a discipline one.
The problem
Two systems describing one shipment
The label carries an identifier produced by a printing template while the notice carries data assembled in the enterprise system. Both describe the same carton and neither knows what the other said. When they diverge, the divergence is discovered at somebody else's dock.
The fix
One source creates the identifier, the label and the message
Where the same system generates the serial identifier, prints the label and populates the notice simultaneously, a mismatch between them becomes impossible to produce rather than merely unlikely. That removes an entire failure category by construction instead of by vigilance.
The extension
Same principle, applied to quantity and structure
Build the message from confirmed pick and pack output rather than from the order that preceded it. An order says what should ship; the pick says what did. A notice derived from the first will be accurate only when nothing changed.
Which Standard, and Where
The same document under several names, which matters when a programme spans regions or when a customer changes format.
Swipe to see all columns
| Format | What it is | Where it is used | Status worth knowing |
|---|---|---|---|
| VDA 4913 | Delivery note and transport data — the older, flat text-based automotive standard, effectively an automotive-specific despatch advice | European automotive, long established | Being decommissioned by at least one major manufacturer, with suppliers advised to move to the alternative format |
| VDA 4987 | Despatch advice — the newer, EDIFACT-based automotive standard | European automotive, the migration target | Guidance is explicit that moving from the older format helps keep supplier ratings high |
| EDIFACT DESADV | The general despatch advice message; commonly cited versions include D96A, D97A and D01B | Europe and Asia broadly | The parent standard the automotive variants derive from |
| ANSI X12 856 | Ship notice and manifest — the North American equivalent, describing shipment, order, pack and item levels | North America | Same function, different syntax and different trading partner rules |
| RECADV | Receiving advice — reports discrepancies between what was advised and what actually arrived | Alongside any of the above | The reconciliation mechanism most programmes are missing |
One item on that table deserves emphasis. Format migration is not a purely technical matter — published guidance ties it directly to supplier rating, on the basis that a supplier still transmitting a deprecated format will eventually be assessed on it. If a customer has announced a decommissioning, the migration date belongs on the supplier development plan rather than in the IT backlog.
How many of last month's receipts had a discrepancy nobody reported back?
Most inbound operations resolve mismatches at the dock and never close the loop to the supplier, which means the same error recurs next week because nothing told anyone it happened. Bring a month of goods receipts and the matching notices to a 30-minute demo and we'll reconcile them in Fleet Rabbit — sorted by mismatch category, by supplier and by whether a correction was ever issued.
Reconciliation Needs a Message, Not an Email
The mechanism that closes the loop, and the reason discrepancies keep recurring where it is absent.
A standard exists for exactly this
Where discrepancies appear between what was advised and what was actually received, they can be reported through a receiving advice message — allowing the supplier to take immediate corrective action and avoid disruption to production on the customer side.
Immediate is the operative word
A discrepancy resolved locally at the dock and never transmitted teaches the supplier nothing. The next shipment carries the same fault, because the process that produced it received no signal. Structured feedback is what converts a receiving problem into a supplier correction.
And it makes the pattern countable
Discrepancies reported through a standard message can be categorised, counted and trended by supplier and by type. Discrepancies resolved verbally cannot, which is why operations running on informal correction have plenty of frustration and no data.
Every Customer Implements a Subset
The reason a technically valid message still gets rejected, and a genuine source of supplier frustration worth acknowledging.
Record types differ by customerPublished manufacturer guidelines routinely mark which record types within the standard are used and which are not, so two customers on the same standard require different messages from the same supplier.
Mandatory and optional fields are set locallyElements are specified as mandatory or optional per implementation. A field one customer ignores is a rejection condition at another, which is why a generic setup fails specific requirements.
Structural rules varyReal published examples include a requirement that each part number and order number occupies its own position in the notice, and a prohibition on combining the gross weight of two or more notices. Neither is inferable from the standard alone.
Labels and paperwork must agreeManufacturer guidelines ask explicitly that information printed on labels is shown consistently on the accompanying paperwork. That is the same synchronisation problem as the handling unit mismatch, restated as a documentation rule — and it points at the same fix.
There is a fairness point buried in this section worth making to your own team. A supplier serving several customers is maintaining several different implementations of the same standard, and a rejection is often a specification difference rather than negligence. Programmes that acknowledge that get better cooperation than programmes that treat every rejection as a performance failure.
Detection Speed Is the Whole Difference
Three tiers, and the gap between the first and the third is where most of the cost lives.
Same day
Rejections and failed acknowledgements caught immediately
Monitoring the transmission layer so a rejected message or a missing acknowledgement surfaces the day it happens. This is described as the difference between operational monitoring and reactive firefighting, and it costs a configured alert.
At receipt
Physical mismatch identified at the dock
Where the notice and the shipment disagree, receiving stops, investigates and reconciles manually — which slows the operation and creates an inventory discrepancy even when it is resolved correctly.
Weeks later
Discovered through a deduction or a held invoice
The worst tier, because the fault has recurred continuously in the interval and the conversation now starts with a financial dispute rather than a technical one. By this point nobody can reconstruct which shipment went wrong or why.
An Escalation Path Suppliers Can See Coming
Five stages. Publishing the ladder in advance is what makes the early stages effective, because the supplier knows what the next one is.
1Automated discrepancy reportIssued through the standard receiving advice message on the day of receipt, categorised by mismatch type. No human involvement and no judgement — the record simply exists.
2Threshold breach flaggedWhere a supplier crosses an agreed rate within a category, raised automatically rather than noticed. A single mismatch is an incident; a rate is a signal.
3Structured root cause requestUsing whatever problem resolution format the two parties have agreed — a structured report, an eight-discipline format, or an A3. Agreeing the format in advance means the response arrives in a shape you can compare against the last one.
4Joint technical reviewBecause most causes are architectural, this is a conversation between systems people rather than a commercial escalation. Ask which system generates the label, which generates the message, and whether either knows about the other.
5Commercial consequenceReflected in the supplier rating and, where the rating drives allocation, in volume. Reaching stage five should be rare — and where it is not, the earlier stages are not being run properly.
Frequently Asked Questions
What are the main categories of ASN mismatch?
Five: handling unit mismatches where the label and the notice disagree, quantity discrepancies where advised and physical counts differ, timing violations where the message arrives too late to support receiving, missing or invalid data, and hierarchy errors where the described shipment, order, pack and item structure does not match the physical load. Categorising by type rather than by supplier is what makes the pattern actionable, since each category has a different root cause.
Why do accurate suppliers still produce bad notices?
Because the failures are usually architectural. Published analysis puts the root cause of most compliance problems not in a single bad document but in a chain of manual handoffs between disconnected systems, with errors tracing to synchronisation gaps between enterprise, warehouse and messaging systems rather than to protocol failures. Manually created notices are specifically more likely to carry stale order data, incorrect pack details or invalid labels.
What is the single most effective fix?
Generating the notice from the same fulfilment and shipment data that controls the physical movement of the goods. Where one system creates the serial identifier, prints the label and populates the message simultaneously, a mismatch between them becomes impossible to produce rather than merely unlikely. Extend the same principle to quantity and structure by building the message from confirmed pick and pack output rather than from the original order.
How should discrepancies be reported back to suppliers?
Through the standard receiving advice message, which exists precisely for reporting differences between advised and actually received deliveries so the supplier can take immediate corrective action and avoid disrupting production. A discrepancy resolved at the dock and never transmitted teaches the supplier nothing — the next shipment carries the same fault. Structured reporting also makes the pattern countable by supplier and by type, which verbal correction never does.
Which format should we be on?
In European automotive the older flat text-based standard is being superseded by the newer EDIFACT-based one, and at least one major manufacturer has announced decommissioning with suppliers advised to move. Guidance ties the migration directly to supplier rating — a supplier still transmitting a deprecated format will eventually be assessed on it. Elsewhere the equivalents are the general EDIFACT despatch advice in Europe and Asia and the ANSI ship notice in North America. Same function, different syntax, different partner rules.
Why does a valid message still get rejected by some customers?
Because every customer implements a subset of the standard. Published manufacturer guidelines mark which record types are used and which are not, specify fields as mandatory or optional locally, and add structural rules — real examples include requiring each part and order number to occupy its own position, and prohibiting the combination of gross weight across notices. A generic setup fails these customer-specific requirements, which means validation has to run against each customer's implementation rather than against the standard.
How quickly should problems surface?
The same day. Catching rejected messages and failed acknowledgements on the day they occur, rather than discovering them through a deduction or a held invoice weeks later, is described as the difference between operational monitoring and reactive firefighting. By the time a financial dispute raises the issue, the fault has recurred continuously in the interval and nobody can reconstruct which shipment went wrong. Start free with three assets and put the reconciliation in place first.
Fix the Source, Not the Supplier
Sort mismatches into categories before assigning blame, generate the label and the message from the system that controls the goods, report every discrepancy through the standard message on the day it happens, validate against each customer's actual implementation rather than the standard, and publish the escalation ladder so the early stages have something to escalate toward.
Format names, record structures and customer-specific rules vary by manufacturer, region and agreement — confirm the implementation guideline issued by each customer rather than working from the base standard alone.
September 8, 2026
By Alex Rowan
All Articles
