ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.
REMADV D.00B

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

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.00B.

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.00B. 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.00B message has 15 header entries, 36 detail entries and 6 summary entries (segments and groups combined). Groups are shown in bold and their members are indented by actual nesting depth.

Pos.TagNameSRep.
0010UNHMessage headerM1
0020BGMBeginning of messageM1
0030DTMDate/time/periodM×5
0040RFFReferenceC×5
0050FIIFinancial institution informationC×5
0060PAIPayment instructionsC1
0070FTXFree textC×99
0090  SG1Group (×99)C×99
0100  NADName and addressM1
0110    SG2Group (×5)C×5
0120    CTAContact informationM1
0130    COMCommunication contactC×5
0140      SG3Group (×5)C×5
0150      CUXCurrenciesM1
0160      DTMDate/time/periodC1

Detail

Pos.TagNameSRep.
0170  SG4Group (×999999)C×999999
0180  DOCDocument/message detailsM1
0190  MOAMonetary amountM×5
0200  DTMDate/time/periodC×5
0210  RFFReferenceC×5
0220  NADName and addressC×2
0230    SG5Group (×5)C×5
0240    CUXCurrenciesM1
0250    DTMDate/time/periodC1
0260      SG6Group (×100)C×100
0270      AJTAdjustment detailsM1
0280      MOAMonetary amountC1
0290      RFFReferenceC1
0300      FTXFree textC×5
0310        SG7Group (×9)C×9
0320        TAXDuty/tax/fee detailsM1
0330        MOAMonetary amountC×9
0340          SG8Group (×5)C×5
0350          INPParties and instructionM1
0360          FTXFree textC×5
0370            SG9Group (×9999)C×9999
0380            DLIDocument line identificationM1
0390            MOAMonetary amountC×5
0400            PIAAdditional product idC×5
0410            DTMDate/time/periodC×5
0420              SG10Group (×5)C×5
0430              CUXCurrenciesM1
0440              DTMDate/time/periodC1
0450                SG11Group (×10)C×10
0460                AJTAdjustment detailsM1
0470                MOAMonetary amountC1
0480                RFFReferenceC1
0490                FTXFree textC×5
0500                  SG12Group (×9)C×9
0510                  TAXDuty/tax/fee detailsM1
0520                  MOAMonetary amountC×9

Summary

Pos.TagNameSRep.
0530UNSSection controlM1
0540MOAMonetary amountM×99
0550  SG13Group (×99)C×99
0560  ALCAllowance or chargeM1
0570  MOAMonetary amountC×9
0580UNTMessage trailerM1

Changes vs D.96A

Top-level differences between D.96A and D.00B 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

  • 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.00B.
  • MOA (summary): repeat ×5 in D.96A → ×99 in D.00B.

Structural example

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

edifact remadv-d00b-example.edi
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL000001'
UNH+1+REMADV:D:00B: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+CTRL000001'

Common errors

  • Misaligned UNH tokens — The UNH+...+REMADV: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.

Other versions of this message available on ediverse.io: REMADV D.96A, REMADV D.01B, REMADV D.10A, REMADV D.16B, REMADV D.21B, REMADV D.24A, REMADV D.97A, REMADV D.99B, 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