Receiving Advice Message
UN/EDIFACT RECADV reports what a buyer actually received at their dock, allowing the supplier to reconcile shipped versus received quantities.
In this guide
EDIFACT RECADV moves from Buyer / Warehouse to Supplier (Buyer → Seller) via AS2, SFTP, VAN. The interactive diagram below traces every business and technical step the message passes through — press Play Flow to watch it travel, or click any step for detail.
How it works
How EDIFACT RECADV Works
Sender
Buyer / Warehouse
Receiver
Supplier
Direction
Buyer → Seller
Standard
UN/EDIFACT
Version
D.01B
Transport
AS2 / SFTP / VAN
Business Purpose
Logistics & Fulfillment
Sender — Buyer / Warehouse
EDI Transmission
RECADV
Receiving Advice Message
UN/EDIFACT D.96A / D.01B
Receiver — Supplier
Related transaction flows
Need help understanding this EDI flow?
Ask EDI AI →EDIFACT RECADV workflow. Steps: Scan at Receiving, Record Actuals, Generate RECADV, Send to Supplier, Supplier Receives Advice, Reconcile Before Billing. Transmitted from Buyer / Warehouse to Supplier via AS2, SFTP, VAN, following UN/EDIFACT D.96A / D.01B.
Overview
Surfaces shipping discrepancies (shortages, overages, damage) quickly so suppliers can resolve them before or during invoicing.
Sender
Buyer / Warehouse
Receiver
Supplier
Direction
Buyer → Seller
Standard / Version
UN/EDIFACT D.96A / D.01B
Segment structure
Key segments that make up this transaction set:
| Segment | Name | Purpose |
|---|---|---|
| BGM | Beginning of Message | Receiving advice document number. |
| RFF | Reference | References the original order and despatch advice. |
| LIN | Line Item | Item received. |
| QTY | Quantity | Actual quantity received vs. quantity despatched. |
Interactive example
Click any segment below to see its business meaning.
UNH
This is an envelope or control segment. Select a highlighted segment on the left (shown in green) for a full business explanation.
View raw EDI
UNH+1+RECADV:D:96A:UN'
BGM+632+REC-7710+9'
RFF+ON:PO-2024-88213'
RFF+AAK:ASN-55210'
LIN+1++SKU-10293:BP'
QTY+48:98'
QTY+12:100'
UNS+S'
UNT+8+1'Mapping example
A representative field-level mapping from a common source system into this transaction:
| Source | Source Field | Target Field |
|---|---|---|
| WMS Receiving Record | receipt.qty_received | QTY+48 (Quantity) |
| WMS Receiving Record | receipt.reference_asn | RFF+AAK (Reference Number) |
Validation rules
- RFF+AAK must reference a DESADV the supplier actually sent.
- A variance between QTY+48 and QTY+12 should trigger an exception workflow rather than silent acceptance.
Common errors & troubleshooting
Supplier invoices for the despatched quantity despite a shortage report
Cause: RECADV variance wasn't fed back into the billing/invoicing process before INVOIC generation.
Fix: Integrate RECADV variance data into the order-to-cash workflow so invoicing reflects confirmed receipt, not just despatch.
Frequently asked questions
It's most common in retail and grocery supply chains with strict receiving discrepancy processes, particularly in Europe.
Still have questions about RECADV?
Ask EDI AI →