# EDIFACT RECADV: Receiving Advice and Examples

> EDIFACT RECADV receiving advice explained: QTY 194, QVR discrepancy codes, per-SSCC receipts, three live EANCOM examples and the X12 861 mapping.

<QuickAnswer>
EDIFACT RECADV is the receiving advice message, the equivalent of the X12 861. The buyer sends it after goods arrive and are checked, confirming what was received and accepted. BGM+632 identifies it, QTY+194 carries the accepted quantity per GTIN, and QVR explains any shortfall, damage or over-delivery against the despatch advice or order.
</QuickAnswer>

RECADV is the buyer telling you what actually made it onto their shelves. Your DESADV said 120 units on pallet one. The RECADV says 108 were accepted and 12 arrived crushed. That difference becomes a credit note, a deduction from your next payment, or a dispute, so the receiving advice is the document your finance team should be reading as closely as your warehouse team.

This guide follows the [GS1 EANCOM 2002 RECADV](https://www.gs1.org/sites/default/files/docs/eancom/ean02s3/part2/recadv/toc.htm) layout (subset version EAN009, directory D.01B). Every example continues the same fictional order used in the [ORDERS](/guides/edi/edifact-orders), [ORDRSP](/guides/edi/edifact-ordrsp) and [DESADV](/guides/edi/edifact-desadv) guides, so you can follow one purchase order from start to finish.

<EDIGuideCTA
  badge="For EDIFACT RECADV"
  transactionType="861"
  headline="Turn RECADV discrepancies into actions, not arguments"
  body="Paste a RECADV into the free EDIFACT inspector to check quantities, SSCCs and segment counts. OrderSync processes EDIFACT, EANCOM and TRADACOMS alongside X12, PDF, CSV and email, and matches each receipt back to the order and despatch advice in your ERP."
  secondaryHref="/edifact-inspector"
  secondaryLabel="Try the free EDIFACT inspector"
/>

## What is an EDIFACT RECADV?

**RECADV (receiving advice) is the UN/EDIFACT message a buyer or receiving site sends to the supplier after goods have been physically received and inspected.** It confirms receipt, reports any differences between what was received and accepted and what was despatched or ordered, and can say what should happen to the difference: return it, destroy it, or keep the line open as a backorder.

GS1 describes two uses for the message:

- **Confirmation of receipt.** Only the header is sent. It names the despatch advice and order and says, in effect, "all arrived".
- **Notification of discrepancies.** The detail section lists each item (and optionally each pallet) with the accepted quantity and a QVR variance explaining any gap.

GS1 says the message should be sent within a commercially agreed period after receipt, giving 24 hours as an example. In practice the partner's implementation guide sets the deadline.

## Where RECADV sits in the order-to-cash flow

| Step | Message | Sent by | X12 equivalent |
|---|---|---|---|
| 1 | [ORDERS](/guides/edi/edifact-orders) | Buyer | 850 |
| 2 | [ORDRSP](/guides/edi/edifact-ordrsp) (optional) | Supplier | 855 |
| 3 | [ORDCHG](/guides/edi/edifact-ordchg) (if the order changes) | Buyer | 860 |
| 4 | [DESADV](/guides/edi/edifact-desadv) | Supplier, at despatch | 856 |
| 5 | **RECADV** | Buyer, after receipt | **861** |
| 6 | [INVOIC](/guides/edi/edifact-invoic) | Supplier | 810 |

Some partners want the invoice to follow the RECADV, so you bill for what was accepted rather than what was despatched. Others invoice from the DESADV and use the RECADV to raise deductions afterwards. Find out which model your partner runs before go-live, because it decides whether a short receipt shows up as a smaller invoice or as a debit note weeks later.

Each RECADV covers one despatch point and one receiving point. A delivery to two depots produces two receiving advices.

## Example 1: full receipt, header only

The fictional retailer Harbour Lane Stores receives despatch advice KV-DES-7781 from Kestrel Valley Homeware at its distribution centre on 15 October 2026. Everything checks in. Following the GS1 "simple scenario", only the header is sent.

<EdifactSample
  title="RECADV confirming a complete receipt"
  description="Header-only receiving advice: references the DESADV and order, no line detail because nothing differed."
  label="EANCOM D.01B EAN009"
  raw="UNA:+.? '
UNB+UNOC:3+5012345000008:14+5098765000002:14+261015:1630+HLS000478++RECADV'
UNH+1+RECADV:D:01B:UN:EAN009'
BGM+632+HL-REC-30417+9'
DTM+137:20261015:102'
DTM+50:202610150715:203'
RFF+AAK:KV-DES-7781'
DTM+171:20261013:102'
RFF+ON:HL-PO-88231'
DTM+171:20261011:102'
NAD+BY+5012345000008::9'
NAD+SU+5098765000002::9'
NAD+DP+5012345000107::9'
UNT+12+1'
UNZ+1+HLS000478'"
/>

| Segment | What it says |
|---|---|
| `BGM+632+HL-REC-30417+9'` | Document 632 (goods receipt), receiving advice number HL-REC-30417, function 9 (original) |
| `DTM+137:20261015:102'` | Message date |
| `DTM+50:202610150715:203'` | Goods receipt date and time: 07:15 on 15 October 2026 |
| `RFF+AAK:KV-DES-7781'` | The despatch advice this receipt relates to |
| `DTM+171:20261013:102'` | Date of that despatch advice |
| `RFF+ON:HL-PO-88231'` | The buyer's order number |
| `NAD+BY` / `NAD+SU` / `NAD+DP` | Buyer, supplier and the delivery point that received the goods |
| `UNT+12+1'` | 12 segments from UNH to UNT inclusive |

## Example 2: short delivery and a backorder

Same delivery, different outcome. On line 1 the DESADV said 120 chopping boards but only 114 were counted. On line 2 the supplier had already told the buyer, through ORDRSP, that only 40 of the 60 mill sets would ship now. The buyer accepts the 40 and keeps the remaining 20 open, but only until 30 October.

<EdifactSample
  title="RECADV with a short count and an open backorder"
  description="Line 1 short against the despatch advice; line 2 short against the order with a backorder deadline."
  label="EANCOM D.01B EAN009"
  raw="UNA:+.? '
UNB+UNOC:3+5012345000008:14+5098765000002:14+261015:1645+HLS000479++RECADV'
UNH+1+RECADV:D:01B:UN:EAN009'
BGM+632+HL-REC-30418+9'
DTM+137:20261015:102'
DTM+50:202610150715:203'
RFF+AAK:KV-DES-7781'
DTM+171:20261013:102'
RFF+ON:HL-PO-88231'
DTM+171:20261011:102'
NAD+BY+5012345000008::9'
NAD+SU+5098765000002::9'
NAD+DP+5012345000107::9'
CPS+1'
LIN+1++5098765100016:SRV'
QTY+194:114'
QTY+12:120'
QVR+-6:12+CP'
LIN+2++5098765100023:SRV'
QTY+194:40'
QTY+21:60'
QVR+-20:21+BP'
DTM+61:20261030:102'
CNT+2:2'
UNT+23+1'
UNZ+1+HLS000479'"
/>

| Segment | What it says |
|---|---|
| `CPS+1'` | Start of the detail section. GS1 recommends level 1 when you are not describing packing levels |
| `LIN+1++5098765100016:SRV'` | Line 1, the GTIN received |
| `QTY+194:114'` | Received and accepted: 114 |
| `QTY+12:120'` | Despatch quantity from the DESADV: 120 |
| `QVR+-6:12+CP'` | Variance of minus 6 against the despatch quantity. CP: shipment partial, considered complete, no backorder |
| `QTY+21:60'` | Line 2 ordered quantity |
| `QVR+-20:21+BP'` | Minus 20 against the ordered quantity. BP: partial shipment, back order to follow |
| `DTM+61:20261030:102'` | Cancel the backorder if not delivered by 30 October |
| `CNT+2:2'` | Two LIN lines |

Read the QVR quantity qualifier carefully. It names the quantity the variance is measured against. `-6:12` means "6 fewer than despatched", which is a supplier or carrier problem. `-20:21` means "20 fewer than ordered", which the supplier already announced. The same minus sign means very different things for your invoice.

## Example 3: damaged pallet, goods to be returned

This time the buyer reports by pallet. The first pallet, SSCC 350987650000000010, arrived with 12 boards damaged. They will be returned and the supplier must collect them on 20 October. The second pallet is fine. Reporting by SSCC uses the PCI, QTY, QVR and GIN group under each LIN, so the supplier can trace the damage to a specific pallet and, from there, to a carrier and a loading bay.

<EdifactSample
  title="RECADV rejecting damaged goods on one SSCC"
  description="Per-pallet receipt: 12 units on the first SSCC rejected for return, with a collection date."
  label="EANCOM D.01B EAN009"
  raw="UNA:+.? '
UNB+UNOC:3+5012345000008:14+5098765000002:14+261015:1710+HLS000480++RECADV'
UNH+1+RECADV:D:01B:UN:EAN009'
BGM+632+HL-REC-30419+9'
DTM+137:20261015:102'
DTM+50:202610150715:203'
RFF+AAK:KV-DES-7781'
DTM+171:20261013:102'
RFF+ON:HL-PO-88231'
DTM+171:20261011:102'
NAD+BY+5012345000008::9'
NAD+SU+5098765000002::9'
NAD+DP+5012345000107::9'
CPS+1'
LIN+1++5098765100016:SRV'
QTY+194:108'
QTY+12:120'
QVR+-12:195+AF'
DTM+200:20261020:102'
PCI+39'
QTY+194:108'
QVR+-12:195+AF'
GIN+BJ+350987650000000010'
LIN+2++5098765100023:SRV'
QTY+194:40'
QTY+12:40'
PCI+39'
QTY+194:40'
GIN+BJ+350987650000000027'
CNT+2:2'
UNT+29+1'
UNZ+1+HLS000480'"
/>

| Segment | What it says |
|---|---|
| `QTY+194:108'` (under LIN) | Total accepted for the item across all pallets |
| `QVR+-12:195+AF'` | 12 received but not accepted, to be returned (195), because goods were delivered damaged (AF) |
| `DTM+200:20261020:102'` | Collection date for the returned goods |
| `PCI+39'` | The following quantities relate to a package marked with an SSCC |
| `QTY+194:108'` (under PCI) | Accepted quantity on this pallet |
| `GIN+BJ+350987650000000010'` | The pallet's SSCC, matching the DESADV and the label |

If the damaged goods are destroyed on site instead of returned, use quantity qualifier `196` (received, not accepted, to be destroyed) and drop the collection date.

## RECADV segment reference

Status and repeats follow the EANCOM 2002 message structure chart. M is mandatory, C conditional.

| Segment | Name | Status | Repeats | Carries | X12 861 equivalent |
|---|---|---|---|---|---|
| UNH | Message header | M | 1 | `RECADV:D:01B:UN:EAN009` | ST |
| BGM | Beginning of message | M | 1 | 632, receiving advice number, function | BRA |
| DTM | Date/time | M | 10 | 137 message date, 50 receipt date | BRA date, DTM |
| ALI | Additional information | C | 5 | Special conditions | |
| FTX | Free text | C | 99 | Header notes | NTE |
| RFF (SG1) | Reference | M in group | 10 | AAK despatch advice, ON order | REF, PRF |
| NAD (SG4) | Name and address | M | 99 | BY, SU, DP, DEQ, UC by GLN | N1 |
| TDT (SG10) | Transport details | C | 10 | Carrier and vehicle | TD5 |
| EQD, SEL, CDI | Equipment, seal, seal condition | C | 9999 | Broken or missing seals | |
| CPS (SG16) | Consignment packing sequence | M in group | 9999 | Detail section start | |
| PAC, QVR, PCI, GIN | Package level detail | C | 9999 | Pallets damaged or unknown | |
| LIN (SG22) | Line item | M in group | 9999 | GTIN received | LIN |
| PIA | Additional product id | C | 10 | Buyer or supplier item number, batch | LIN |
| QTY | Quantity | C | 10 | 194 accepted, 12 despatched, 21 ordered, 46 delivered | RCD |
| QVR | Quantity variance | C | 10 | Difference and reason | RCD |
| DTM | Line date | C | 5 | 61 cancel-by, 200 collection, 360 sell-by | DTM |
| PCI, QTY, QVR, GIN (SG29) | Per-SSCC receipt | C | 9999 | Quantity accepted per pallet | RCD |
| CNT | Control total | C | 1 | 2 = number of LIN lines | CTT |
| UNT | Message trailer | M | 1 | Segment count, reference | SE |

## Code tables

### BGM message function

| Code | Meaning in EANCOM RECADV |
|---|---|
| `9` | Original receiving advice |
| `5` | Replace: corrects an earlier RECADV, which is then quoted in `RFF+ALO` |
| `29` | Accepted without amendment: the referenced message is entirely accepted |
| `27` | Not accepted: the referenced message is not accepted |
| `31` | Copy for a third party, for information |

### QTY qualifiers

| Qualifier | Meaning |
|---|---|
| `194` | Received and accepted |
| `46` | Delivered quantity |
| `48` | Received quantity |
| `12` | Despatch quantity (as advised in DESADV) |
| `21` | Ordered quantity |
| `192` | Free goods quantity |

### QVR: what the variance is measured against

The second component of QVR is a quantity qualifier. A negative value means less than expected, positive means more.

| Qualifier | Variance against |
|---|---|
| `12` | Despatch quantity |
| `21` | Ordered quantity |
| `46` | Delivered quantity |
| `195` | Received, not accepted, to be returned |
| `196` | Received, not accepted, to be destroyed |

### QVR discrepancy codes (third element)

| Code | Meaning |
|---|---|
| `AC` | Over-shipped |
| `AE` | Delivered but not advised |
| `AF` | Goods delivered damaged |
| `AG` | Delivered too late |
| `BP` | Shipment partial, back order to follow |
| `CP` | Shipment partial, considered complete, no backorder |

QVR can also carry a change reason code in its fourth element, such as `AT` (item not ordered), `BH` (batch number difference), `BN` (temperature outside agreed range) or `PC` (pack difference). Which reasons a partner sends, and what each one triggers commercially, is set in their guide and trading agreement.

### Line-level DTM qualifiers

| Qualifier | Use |
|---|---|
| `61` | Cancel if not delivered by this date (backorder deadline) |
| `200` | Pick-up or collection date for returned goods |
| `360` | Sell-by date, used when rejecting short-dated product |

## RECADV vs the X12 861

| Data | EDIFACT RECADV | X12 861 |
|---|---|---|
| Receiving advice number | `BGM` second element | `BRA01` |
| Receipt date | `DTM+50` | `BRA02` |
| Despatch advice reference | `RFF+AAK` | `REF` (qualifier set by the partner) |
| Order number | `RFF+ON` | `PRF01` |
| Item | `LIN` with GTIN | `LIN` |
| Accepted quantity | `QTY+194` | `RCD` quantity received |
| Discrepancy | `QVR` value, qualifier and reason code | `RCD` condition code and quantities |
| Line count | `CNT+2` | `CTT01` |

The biggest structural difference: X12 861 puts the condition and the quantity in one `RCD` segment. RECADV separates the accepted quantity (`QTY+194`) from the explanation (`QVR`), and lets you report the same item twice: once overall, and again per SSCC. When mapping between them, build each `RCD` from the `QTY` and `QVR` pair, not from `QTY` alone. The [EDI 861 guide](/guides/edi/861-receiving-advice) lists the X12 condition codes.

## Common RECADV errors and fixes

- **Reading QTY+12 as the accepted quantity.** It is what you said you despatched. The figure that drives the invoice is `QTY+194`. Map the right one or you will invoice for goods that were rejected.
- **Ignoring the QVR qualifier.** A variance against `12` is a despatch problem; against `21` it is an order shortfall the buyer may already have agreed. Route them to different queues.
- **SSCCs that do not match the DESADV.** If the RECADV quotes an SSCC your system never sent, the pallet was relabelled or the DESADV was wrong. Check the [inspector](/edifact-inspector) for the GS1 check digit first, then compare against your despatch records.
- **No RECADV is not the same as a clean receipt.** GS1 notes that a full, discrepancy-free receipt often produces no RECADV or a header-only one. Agree with the partner which applies, or you will wait for a message that never comes.
- **Replacements treated as new receipts.** A `BGM` function `5` replaces an earlier RECADV quoted in `RFF+ALO`. Update the original receipt; do not add a second one.
- **Backorder deadlines lost.** `DTM+61` under a line is a cancel-by date. If you ship after it, the buyer can refuse the delivery.

## Testing checklist

1. Agree whether the partner sends header-only RECADVs for clean receipts, or none at all.
2. Confirm which quantity qualifiers they send (`194` only, or `194` plus `12`, `21` and `46`).
3. Get their full list of QVR discrepancy and reason codes, and decide what each one does in your ERP.
4. Ask whether they report by item, by SSCC, or both.
5. Test a short receipt, an over-delivery and a damaged pallet before go-live.
6. Check that `UNT` counts and `CNT+2` match by pasting each test file into the [EDIFACT inspector](/edifact-inspector).
7. Agree how disputes are raised: through EDI, a portal or email.

OrderSync reads RECADV, matches each line back to the order and despatch advice, and shows accepted, short and rejected quantities next to each other, so your team works the exceptions instead of re-keying them.

## Frequently Asked Questions

### What is a RECADV in EDI?

RECADV is the UN/EDIFACT receiving advice message. The buyer or receiving warehouse sends it after goods arrive to confirm what was received and accepted and to report shortages, damage or over-deliveries against the despatch advice or the order. It is the EDIFACT equivalent of the X12 861.

### What is the difference between DESADV and RECADV?

DESADV is sent by the supplier when goods leave and says what was shipped. RECADV is sent by the buyer after the goods arrive and says what was received and accepted. Comparing the two, line by line and SSCC by SSCC, is how both sides find and settle delivery discrepancies.

### What does QTY+194 mean?

Qualifier 194 means "received and accepted". It is the quantity the buyer has taken into stock and will pay for. Other quantities in the same line, such as 12 (despatched) or 21 (ordered), are there for comparison.

### Is RECADV mandatory?

No. EANCOM defines it but does not require it, and many retailers never send one. Where it is used, the trading partner agreement sets when it is sent and what it triggers, such as invoice matching or automatic deductions.

### How quickly is a RECADV sent?

GS1 recommends sending it within a commercially agreed period after receipt and gives 24 hours as an example. The partner's guide sets the actual window.

### Can a RECADV reject a whole delivery?

Yes. A rejected item is reported as its own line with a received and accepted quantity of zero and a QVR explaining why, for example item not ordered or goods damaged. GS1 also defines message function 27 (not accepted) in BGM for a receiving advice that does not accept the referenced message.

### What is the X12 equivalent of RECADV?

The X12 861 Receiving Advice/Acceptance Certificate. The data is similar, but X12 combines condition and quantity in the RCD segment, while RECADV splits them into QTY and QVR.

## Related guides

- **[EDIFACT explained](/guides/edi/edifact)**: syntax, envelopes and the full X12 mapping
- **[EDIFACT DESADV](/guides/edi/edifact-desadv)**: the despatch advice RECADV is checked against
- **[EDIFACT ORDERS](/guides/edi/edifact-orders)** and **[ORDRSP](/guides/edi/edifact-ordrsp)**: the order and the supplier's response
- **[EDIFACT INVOIC](/guides/edi/edifact-invoic)**: the invoice that should agree with the receipt
- **[EDIFACT APERAK](/guides/edi/edifact-aperak)**: application errors on a message, as opposed to goods discrepancies
- **[EDIFACT message types](/guides/edi/edifact-message-types)**: every EDIFACT message and its X12 equivalent
- **[EDI 861 receiving advice](/guides/edi/861-receiving-advice)**: the X12 counterpart

## Sources

- [EANCOM 2002 S3: RECADV receiving advice message](https://www.gs1.org/sites/default/files/docs/eancom/ean02s3/part2/recadv/toc.htm), GS1
- [UN/EDIFACT D.01B RECADV message](https://service.unece.org/trade/untdid/d01b/trmd/recadv_c.htm), UNECE
- [Serial Shipping Container Code (SSCC)](https://www.gs1.org/standards/id-keys/sscc), GS1

Paste any RECADV into the free [EDIFACT inspector](/edifact-inspector) to see each line, quantity and SSCC laid out and checked.