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.
COACSU D.18B

COACSU — EDIFACT Commercial Account Summary Message (D.18B)

The COACSU message is the summary of a commercial account sent from a supplier to a buyer — or symmetrically between two corporates: over a given period it aggregates the flows of invoices, credit notes, payments and outstanding differences and sets a net balance due. It is the consolidated-reconciliation layer that sits above STATAC and REMADV. This page summarises the segment structure as published by UN/CEFACT for directory D.18B.

Purpose

The COACSU message is the summary of a commercial account sent from a supplier to a buyer — or symmetrically between two corporates: over a given period it aggregates the flows of invoices, credit notes, payments and outstanding differences and sets a net balance due. It is the consolidated-reconciliation layer that sits above STATAC and REMADV.

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

Segment structure

The COACSU D.18B message has 28 header entries, 20 detail entries and 8 summary entries (segments and groups combined). Groups are shown in bold and their members are indented by actual nesting depth.

Pos.TagNameSRep.
00010UNHMessage headerM1
00020BGMBeginning of messageM1
00030DTMDate/time/periodM×9
00040ALIAdditional informationC×9
00050FTXFree textC×99
00060  SG1Group (×9)C×9
00070  RFFReferenceM1
00080  DTMDate/time/periodC×9
00090    SG2Group (×99)C×99
00100    NADName and addressM1
00110    FIIFinancial institution informationC×9
00120    FTXFree textC×99
00130      SG3Group (×9)C×9
00140      RFFReferenceM1
00150      DTMDate/time/periodC×9
00160        SG4Group (×9)C×9
00170        CTAContact informationM1
00180        COMCommunication contactC×9
00190          SG5Group (×9)C×9
00200          CUXCurrenciesM1
00210          DTMDate/time/periodC×9
00220            SG6Group (×9)C×9
00230            PYTPayment termsM1
00240            MOAMonetary amountC×9
00250            PCDPercentage detailsC×9
00260            DTMDate/time/periodC×9
00270            FIIFinancial institution informationC1
00280            PAIPayment instructionsC×9

Detail

Pos.TagNameSRep.
00290  SG7Group (×99999)C×99999
00300  DOCDocument/message detailsM1
00310  DTMDate/time/periodC×9
00320    SG8Group (×9)C×9
00330    NADName and addressM1
00340      SG9Group (×99)C×99
00350      RFFReferenceM1
00360      DTMDate/time/periodC×9
00370        SG10Group (×99)C×99
00380        MOAMonetary amountM1
00390        TAXDuty/tax/fee detailsC×9
00400        DTMDate/time/periodC×9
00410        PAIPayment instructionsC1
00420        PYTPayment termsC1
00430        STSStatusC×9
00440          SG11Group (×9)C×9
00450          AJTAdjustment detailsM1
00460          MOAMonetary amountM1
00470          RFFReferenceC1
00480          FTXFree textC×9

Summary

Pos.TagNameSRep.
00490UNSSection controlM1
00500  SG12Group (×99)C×99
00510  MOAMonetary amountM1
00520  QTYQuantityC1
00530  TAXDuty/tax/fee detailsC×9
00540  DTMDate/time/periodC×9
00550  CNTControl totalC1
00560UNTMessage trailerM1

Changes vs D.96A

The COACSU message is not published in directory D.96A. No "D.96A → D.18B" comparison line can therefore be produced — see the block below for details.

This message is not published in directory D.96A: it was introduced into the standard after that release and therefore has no historical baseline for comparison. The first directory indexed on ediverse.io sets the reference; later changes are then documented from one release to the next in subsequent directories.

Structural example

Minimal example of an COACSU D.18B message with mandatory segments only. The goal is to show the exact version declared in UNH (COACSU:D:18B:UN) — not to replicate a full business case.

edifact coacsu-d18b-example.edi
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL018001'
UNH+1+COACSU:D:18B:UN'
BGM+329+COACSU-2026-Q1+9'
DTM+137:20260514:102'
DTM+9:20260331:102'
RFF+ACK:ACCOUNT-12345'
NAD+SU+5410000000123::9'
NAD+BY+5410000000456::9'
CUX+2:EUR:4'
LIN+1'
MOA+9:24580.00'
DOC+380+INV-2026-7811'
MOA+9:1240.00'
UNS+S'
MOA+86:24580.00'
UNT+14+1'
UNZ+1+CTRL018001'

Common errors

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

X12 functional equivalent: X12 844.

← All EDIFACT versions