RECADV — EDIFACT Receiving Advice Message (D.00B)

The RECADV message is the receiving advice sent by the buyer once a shipment is physically received: it confirms received quantities, flags discrepancies against the DESADV, and traces rejections or damages. This page summarises the segment structure as published by UN/CEFACT for directory D.00B.

Purpose

The RECADV message is the receiving advice sent by the buyer once a shipment is physically received: it confirms received quantities, flags discrepancies against the DESADV, and traces rejections or damages.

This page focuses on the structure published by UN/CEFACT for directory D.00B. The segments listed, their status (M / C), position and repetition factor are extracted from the official file recadv_c.htm hosted on service.unece.org.

Segment structure

The RECADV D.00B message has 110 header entries, 0 detail entries and 0 summary entries (segments and groups combined). Groups are shown in bold and their members are indented by actual nesting depth.

Header

Detail

No segment in this section.

Summary

No segment in this section.

Changes vs D.96A

Top-level differences between D.96A and D.00B for the RECADV message (segments directly inside header / detail / summary, ignoring nested groups). The comparison is indicative: a given tag may have evolved inside nested groups without showing up in this synthesis.

Segments added vs D.96A

• CUX in the header section (status C, repeat ×9) — not present at the top of the corresponding D.96A section.
• FTX in the header section (status C, repeat ×99) — not present at the top of the corresponding D.96A section.
• GEI in the header section (status C, repeat ×99) — not present at the top of the corresponding D.96A section.
• MOA in the header section (status C, repeat ×99) — not present at the top of the corresponding D.96A section.
• ALC in the header section (status C, repeat ×1) — not present at the top of the corresponding D.96A section.
• PRI in the header section (status C, repeat ×1) — not present at the top of the corresponding D.96A section.

Structural example

Minimal example of an RECADV D.00B message with mandatory segments only. The goal is to show the exact version declared in UNH (RECADV:D:00B:UN) — not to replicate a full business case (see the RECADV D.96A page for an annotated example).

UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL000001'
UNH+1+RECADV:D:00B:UN'
BGM+632+REC-2026-0098+9'
DTM+137:20260514:102'
DTM+50:20260513:102'
NAD+SU+5410000000456::9'
NAD+BY+5410000000123::9'
RFF+ON:ORDER789'
CPS+1'
LIN+1++3520000001234:EN'
QTY+194:10'
QTY+12:10'
UNT+13+1'
UNZ+1+CTRL000001'

Common errors

• Misaligned UNH tokens — The UNH+...+RECADV:D:00B:UN token must reflect exactly the directory in use — a mismatch between the UNH release and the release agreed with the partner is rejected by every strict validator.
• Wrong UNT segment count — The value after UNT+ must include UNH and UNT themselves. By far the most common sender-side error, regardless of the directory in use.
• Stale code lists — Between D.96A and D.00B, several code lists received new qualifiers (DTM status, RFF qualifier, NAD codes…). Reusing an older directory’s code tables triggers warnings or even rejections depending on the partner’s strict-conformance mode.

Related messages

Other versions of this message available on ediverse.io: RECADV D.96A, RECADV D.01B, RECADV D.10A, RECADV D.16B, RECADV D.21B, RECADV D.24A, RECADV D.97A, RECADV D.99B, RECADV D.02B, RECADV D.05A, RECADV D.08A, RECADV D.13B, RECADV D.18B, RECADV D.20B.

X12 functional equivalent: X12 861.

← All EDIFACT versions