REMADV — EDIFACT Remittance Advice Message (D.16B)

The REMADV message is the remittance advice sent from a buyer to a supplier: it lists which invoices are paid, by which means, with which deductions (discounts, withholdings) and the payment references. This page summarises the segment structure as published by UN/CEFACT for directory D.16B.

Purpose

The REMADV message is the remittance advice sent from a buyer to a supplier: it lists which invoices are paid, by which means, with which deductions (discounts, withholdings) and the payment references.

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

Segment structure

The REMADV D.16B message has 19 header entries, 37 detail entries and 6 summary entries (segments and groups combined). Groups are shown in bold and their members are indented by actual nesting depth.

Header

Detail

Summary

Changes vs D.96A

Top-level differences between D.96A and D.16B for the REMADV 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

• GEI in the header section (status C, repeat ×5) — not present at the top of the corresponding D.96A section.
• QTY in the detail section (status C, repeat ×9) — not present at the top of the corresponding D.96A section.
• TAX in the detail section (status M, repeat ×1) — not present at the top of the corresponding D.96A section.
• ALC in the summary section (status M, repeat ×1) — not present at the top of the corresponding D.96A section.

Max-repeat changes

• FTX (header): repeat ×5 in D.96A → ×99 in D.16B.
• MOA (summary): repeat ×5 in D.96A → ×99 in D.16B.

Structural example

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

UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL016001'
UNH+1+REMADV:D:16B:UN'
BGM+481+REM-2026-0125+9'
DTM+137:20260514:102'
DTM+209:20260520:102'
NAD+PR+5410000000123::9'
NAD+PE+5410000000456::9'
CUX+2:EUR:4'
DOC+380+INV-2026-7811'
MOA+12:1240.00'
UNS+S'
MOA+128:1240.00'
UNT+12+1'
UNZ+1+CTRL016001'

Common errors

• Misaligned UNH tokens — The UNH+...+REMADV:D:16B: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.16B, 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: REMADV D.96A, REMADV D.01B, REMADV D.10A, REMADV D.21B, REMADV D.24A, REMADV D.97A, REMADV D.99B, REMADV D.00B, REMADV D.02B, REMADV D.05A, REMADV D.08A, REMADV D.13B, REMADV D.18B, REMADV D.20B.

X12 functional equivalent: X12 820.

← All EDIFACT versions