STATAC — EDIFACT Statement of Account Message (D.01B)
The STATAC message is the customer statement of account sent by a supplier to a buyer: list of open invoices, credit notes and payments at a given date, with amounts, due dates and status. It underpins dunning letters and accounting reconciliation. This page summarises the segment structure as published by UN/CEFACT for directory D.01B.
Purpose
The STATAC message is the customer statement of account sent by a supplier to a buyer: list of open invoices, credit notes and payments at a given date, with amounts, due dates and status. It underpins dunning letters and accounting reconciliation.
This page focuses on the structure published by UN/CEFACT for directory D.01B. The segments listed, their status (M / C), position and repetition factor are extracted from the official file statac_c.htm hosted on service.unece.org.
Segment structure
The STATAC D.01B message has 10 header entries, 5 detail entries and 4 summary entries (segments and groups combined). Groups are shown in bold and their members are indented by actual nesting depth.
Header
| Pos. | Tag | Name | S | Rep. |
|---|---|---|---|---|
0010 | UNH | Message header | M | 1 |
0020 | BGM | Beginning of message | M | 1 |
0030 | DTM | Date/time/period | M | ×5 |
0040 | RFF | Reference | C | ×5 |
0050 | CUX | Currencies | C | 1 |
0060 | SG1 | Group (×99) | M | ×99 |
0070 | NAD | Name and address | M | 1 |
0080 | SG2 | Group (×5) | C | ×5 |
0090 | CTA | Contact information | M | 1 |
0100 | COM | Communication contact | C | ×5 |
Detail
| Pos. | Tag | Name | S | Rep. |
|---|---|---|---|---|
0110 | SG3 | Group (×200000) | M | ×200000 |
0120 | DOC | Document/message details | M | 1 |
0130 | MOA | Monetary amount | M | ×5 |
0140 | DTM | Date/time/period | C | ×5 |
0150 | RFF | Reference | C | ×5 |
Summary
| Pos. | Tag | Name | S | Rep. |
|---|---|---|---|---|
0160 | UNS | Section control | M | 1 |
0170 | MOA | Monetary amount | M | ×9 |
0180 | FTX | Free text | C | ×99 |
0190 | UNT | Message trailer | M | 1 |
Changes vs D.96A
Top-level differences between D.96A and D.01B for the STATAC 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.
Max-repeat changes
MOA(summary): repeat ×5 in D.96A → ×9 in D.01B.FTX(summary): repeat ×5 in D.96A → ×99 in D.01B.
Structural example
Minimal example of an STATAC D.01B message with mandatory segments only. The goal is to show the exact version declared in UNH (STATAC:D:01B:UN) — not to replicate a full business case (see the STATAC D.96A page for an annotated example).
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL001001'
UNH+1+STATAC:D:01B:UN'
BGM+451+STATAC-2026-04+9'
DTM+137:20260514:102'
DTM+9:20260430:102'
RFF+ACK:CUSTOMER-12345'
NAD+SU+5410000000123::9'
NAD+BY+5410000000456::9'
CUX+2:EUR:4'
MOA+12:18420.00'
DOC+380+INV-2026-7811'
MOA+9:1240.00'
DTM+13:20260530:102'
UNT+12+1'
UNZ+1+CTRL001001'Common errors
- Misaligned UNH tokens — The
UNH+...+STATAC:D:01B:UNtoken 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.01B, 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: STATAC D.96A, STATAC D.10A, STATAC D.16B, STATAC D.21B, STATAC D.24A, STATAC D.97A, STATAC D.99B, STATAC D.00B, STATAC D.02B, STATAC D.05A, STATAC D.08A, STATAC D.13B, STATAC D.18B, STATAC D.20B.
X12 functional equivalent: X12 811.