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.08A

COACSU — EDIFACT Commercial Account Summary Message (D.08A)

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.08A.

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.08A. 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.08A 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.
0010UNHMessage headerM1
0020BGMBeginning of messageM1
0030DTMDate/time/periodM×9
0040ALIAdditional informationC×9
0050FTXFree textC×99
0060  SG1Group (×9)C×9
0070  RFFReferenceM1
0080  DTMDate/time/periodC×9
0090    SG2Group (×99)C×99
0100    NADName and addressM1
0110    FIIFinancial institution informationC×9
0120    FTXFree textC×99
0130      SG3Group (×9)C×9
0140      RFFReferenceM1
0150      DTMDate/time/periodC×9
0160        SG4Group (×9)C×9
0170        CTAContact informationM1
0180        COMCommunication contactC×9
0190          SG5Group (×9)C×9
0200          CUXCurrenciesM1
0210          DTMDate/time/periodC×9
0220            SG6Group (×9)C×9
0230            PYTPayment termsM1
0240            MOAMonetary amountC×9
0250            PCDPercentage detailsC×9
0260            DTMDate/time/periodC×9
0270            FIIFinancial institution informationC1
0280            PAIPayment instructionsC×9

Detail

Pos.TagNameSRep.
0290  SG7Group (×99999)C×99999
0300  DOCDocument/message detailsM1
0310  DTMDate/time/periodC×9
0320    SG8Group (×9)C×9
0330    NADName and addressM1
0340      SG9Group (×99)C×99
0350      RFFReferenceM1
0360      DTMDate/time/periodC×9
0370        SG10Group (×99)C×99
0380        MOAMonetary amountM1
0390        TAXDuty/tax/fee detailsC×9
0400        DTMDate/time/periodC×9
0410        PAIPayment instructionsC1
0420        PYTPayment termsC1
0430        STSStatusC×9
0440          SG11Group (×9)C×9
0450          AJTAdjustment detailsM1
0460          MOAMonetary amountM1
0470          RFFReferenceC1
0480          FTXFree textC×9

Summary

Pos.TagNameSRep.
0490UNSSection controlM1
0500  SG12Group (×99)C×99
0510  MOAMonetary amountM1
0520  QTYQuantityC1
0530  TAXDuty/tax/fee detailsC×9
0540  DTMDate/time/periodC×9
0550  CNTControl totalC1
0560UNTMessage trailerM1

Changes vs D.96A

The COACSU message is not published in directory D.96A. No "D.96A → D.08A" 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.08A message with mandatory segments only. The goal is to show the exact version declared in UNH (COACSU:D:08A:UN) — not to replicate a full business case.

edifact coacsu-d08a-example.edi
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL008001'
UNH+1+COACSU:D:08A: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+CTRL008001'

Common errors

  • Misaligned UNH tokens — The UNH+...+COACSU:D:08A: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.08A, 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.13B, COACSU D.18B, COACSU D.20B.

X12 functional equivalent: X12 844.

← All EDIFACT versions