ediverse

Type to search across standards, messages, tools and glossary.

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.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

REMADV — Remittance Advice Message (D.96A)

The REMADV message — the Remittance Advice — communicates between trading partners a detailed accounting of a payment or other form of financial settlement for the goods and services that have been provided.

Purpose

Per the official UN/CEFACT definition, the Remittance Advice "is a communication between trading partners, e.g. seller, buyer, financial institutions, which provides a detailed accounting relative to a payment, or other form of financial settlement, for the provision of goods and/or services as detailed in the advice."

In plain terms, REMADV explains which documents are being settled by a given wire transfer or direct debit, including amounts, deductions and adjustments (credit notes, end-of-period rebates, withholding tax). On the supplier side, this is the message that drives automatic cash-application of incoming wires against open invoices.

Segment structure

REMADV D.96A has three sections: a Header, a Detail (repeatable SG4 group, up to 9,999 occurrences), and a Summary. Each SG4 describes a settled document (typically an invoice) with its net amount after adjustments.

Mandatory header segments: UNH M , BGM M , and DTM M .

Header conditional segments: RFF C , FII C , PAI C , and FTX C .

Then come the groups: SG1 NAD (parties — payer, payee, optionally bank on either side), with SG2 CTA+COM. Then SG3 CUX+DTM for the settlement currency.

Detail (settled documents)

The Detail rides on the SG4 loop (up to 9,999 occurrences), built around: DOC M + MOA M + DTM C + RFF C + NAD C .

The DOC[0] code qualifies the document type: 380 commercial invoice, 381 credit note, 383 debit note, 389 self-billed invoice, etc. The MOA[0] code qualifies the amount type: 12 amount paid for the invoice, 9 total amount payable, 52 withholding tax, etc.

Each SG4 nests: SG5 CUX+DTM (document-specific currency if different from the header), SG6 AJT+MOA+RFF+FTX — Adjustment Details — for adjustments (allowances, charges, prompt-payment discount, withholding), SG7 INP+FTX — Parties to Instruction — and the sub-loop SG8 DLI+MOA+PIA+DTM with its SG9 CUX+DTM and SG10 AJT+MOA+RFF+FTX. SG8 (Document Line Identification) lets you drill down to the invoice-line level when needed.

Summary

The Summary section contains: UNS M , MOA M , and UNT M .

The Summary MOA typically carries MOA+9 (total amount paid) — and that total must match the algebraic sum of the SG4 MOAs (positive invoices, negative credit notes).

Mandatory / conditional

Five structural items are strictly mandatory in every D.96A REMADV:

  • UNH — opens the message.
  • BGM — gives the function (481 = remittance advice) and the number.
  • DTM in the header — at least one date (typically DTM+137 issue date and DTM+209 value date).
  • UNS+S — separates Detail and Summary.
  • MOA in Summary — total paid amount, mandatory.

On the business side you also need a NAD+PR (Payer), a NAD+PE (Payee), a CUX currency, and at least one SG4 with its DOC + MOA. Automated cash-application typically demands a RFF+IV (invoice reference) or a RFF+CD (credit-note reference) inside each SG4 for matching.

Real-world example

A remittance advice for two documents: an invoice of EUR 1,707.45 less a credit note of EUR 50, i.e. a net wire of EUR 1,657.45.

edifact remadv-d96a-example.edi 
UNB+UNOC:3+5410000000123:14+5410000000456:14+260610:1100+CTRL000020'
UNH+1+REMADV:D:96A:UN:EAN008'
BGM+481+REMADV-2026-06-10+9'
DTM+137:20260610:102'
DTM+209:20260612:102'
RFF+PQ:WIRE-FR76-2026-06-10'
FII+OR+12345600789::25+SOCIETE GENERALE'
PAI+::1'
NAD+PR+5410000000123::9'
NAD+PE+5410000000456::9'
CUX+2:EUR:4'
DOC+380:INV-2026-0512'
MOA+12:1707.45'
DTM+171:20260512:102'
RFF+IV:INV-2026-0512'
DOC+381:CN-2026-0007'
MOA+12:-50.00'
DTM+171:20260530:102'
RFF+CD:CN-2026-0007'
UNS+S'
MOA+9:1657.45'
UNT+19+1'
UNZ+1+CTRL000020'
  • BGM+481+REMADV-2026-06-10+9 — type 481 (remittance advice), number REMADV-2026-06-10, status 9.
  • DTM+137 — issue date. DTM+209 — value date (date the wire is settled).
  • RFF+PQ — payment reference number from the bank side.
  • FII+OR — Ordering Bank: the payer's bank (Société Générale, truncated IBAN).
  • PAI+::1 — Payment Instructions, method 1 (cash, per UN/EDIFACT 4461).
  • NAD+PR / NAD+PE — Payer and Payee.
  • CUX+2:EUR:4 — payment reference currency: EUR (role 2 = currency reference, code 4 = invoicing currency).
  • Two SG4: DOC+380 (invoice) with MOA+12:1707.45, then DOC+381 (credit note) with MOA+12:-50.00. Each doc is referenced via a RFF+IV (Invoice) or RFF+CD (Credit note).
  • UNS+S + MOA+9:1657.45 — total amount paid.
  • UNT+19+1 — 19 segments.

Common errors

  • MOA+9 total inconsistent with SG4 MOA+12 sum — the supplier's AP system systematically rejects any REMADV where the algebraic sum of per-document amounts doesn't equal the total. This is the #1 consistency check on REMADV.
  • Non-negative credit note — a credit note (DOC+381) must carry a negative MOA (e.g. MOA+12:-50.00). Many generators send the credit positive and subtract manually, which breaks matching.
  • Missing matching RFF — without RFF+IV in each SG4, the invoice can't be located in the supplier's ERP. The DOC[1] (invoice number) alone is rarely enough if the buyer truncated the number.
  • Currency dropped — REMADV requires a CUX in the header (or in SG5 for a document-specific currency). Without a currency, amounts are ambiguous in any multi-currency context.
  • FII without qualifier — the financial institution must carry a qualifier: OR Ordering Bank (payer), BF Beneficiary Bank (payee), I1 Intermediary. Skipping it makes fraud cross-checks impossible.

REMADV closes the order-to-cash cycle:

JSON equivalent

JSON projection matching the example above. The mapping is not normative — it's an ediverse convention to ease integration in TypeScript / Python environments.

json remadv-d96a-equivalent.json 
{
  "interchange": {
    "controlRef": "CTRL000020",
    "from": { "id": "5410000000123", "qualifier": "14" },
    "to": { "id": "5410000000456", "qualifier": "14" },
    "datetime": "2026-06-10T11:00:00Z",
    "syntax": { "id": "UNOC", "version": "3" }
  },
  "message": {
    "ref": "1",
    "type": "REMADV",
    "version": { "syntax": "D", "release": "96A", "agency": "UN", "association": "EAN008" }
  },
  "remittanceAdvice": {
    "number": "REMADV-2026-06-10",
    "function": "481",
    "status": "9",
    "issueDate": "2026-06-10",
    "valueDate": "2026-06-12",
    "paymentReference": "WIRE-FR76-2026-06-10",
    "payerBank": { "iban": "12345600789", "qualifier": "25", "name": "SOCIETE GENERALE" },
    "paymentMethod": "1",
    "parties": {
      "payer": { "gln": "5410000000123" },
      "payee": { "gln": "5410000000456" }
    },
    "currency": "EUR",
    "documents": [
      { "type": "380", "number": "INV-2026-0512", "amount": 1707.45, "date": "2026-05-12" },
      { "type": "381", "number": "CN-2026-0007", "amount": -50.00, "date": "2026-05-30" }
    ],
    "totals": { "paid": 1657.45 }
  }
}