BANSTA — EDIFACT Banking Status Message (D.21B)
The BANSTA message is the status response returned by a bank to a corporate after receiving banking instructions (PAYMUL, PAYORD, DIRDEB): it indicates acceptance, rejection or execution status on a per-operation basis. This page summarises the segment structure as published by UN/CEFACT for directory D.21B.
Purpose
The BANSTA message is the status response returned by a bank to a corporate after receiving banking instructions (PAYMUL, PAYORD, DIRDEB): it indicates acceptance, rejection or execution status on a per-operation basis.
This page focuses on the structure published by UN/CEFACT for directory D.21B. The segments listed, their status (M / C), position and repetition factor are extracted from the official file bansta_c.htm hosted on service.unece.org.
Segment structure
The BANSTA D.21B message has 42 header entries, 0 detail entries and 0 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. |
|---|---|---|---|---|
00010 | UNH | Message header | M | 1 |
00020 | BGM | Beginning of message | M | 1 |
00030 | DTM | Date/time/period | M | 1 |
00040 | BUS | Business function | C | 1 |
00050 | SG1 | Group (×2) | C | ×2 |
00060 | RFF | Reference | M | 1 |
00070 | DTM | Date/time/period | C | 1 |
00080 | SG2 | Group (×5) | C | ×5 |
00090 | FII | Financial institution information | M | 1 |
00100 | CTA | Contact information | C | 1 |
00110 | COM | Communication contact | C | ×5 |
00120 | SG3 | Group (×3) | C | ×3 |
00130 | NAD | Name and address | M | 1 |
00140 | CTA | Contact information | C | 1 |
00150 | COM | Communication contact | C | ×5 |
00160 | SG4 | Group (×999) | M | ×999 |
00170 | LIN | Line item | M | 1 |
00180 | SG5 | Group (×5) | C | ×5 |
00190 | RFF | Reference | M | 1 |
00200 | DTM | Date/time/period | C | 1 |
00210 | SG6 | Group (×99) | C | ×99 |
00220 | SEQ | Sequence details | M | 1 |
00230 | GEI | Processing information | M | 1 |
00240 | DTM | Date/time/period | C | ×2 |
00250 | MOA | Monetary amount | C | 1 |
00260 | CUX | Currencies | C | 1 |
00270 | PCD | Percentage details | C | 1 |
00280 | FTX | Free text | C | 1 |
00290 | DOC | Document/message details | C | ×5 |
00300 | SG7 | Group (×1) | C | 1 |
00310 | FII | Financial institution information | M | 1 |
00320 | CTA | Contact information | C | 1 |
00330 | COM | Communication contact | C | ×5 |
00340 | SG8 | Group (×1) | C | 1 |
00350 | NAD | Name and address | M | 1 |
00360 | CTA | Contact information | C | 1 |
00370 | COM | Communication contact | C | ×5 |
00380 | CNT | Control total | C | ×5 |
00390 | SG9 | Group (×5) | C | ×5 |
00400 | AUT | Authentication result | M | 1 |
00410 | DTM | Date/time/period | C | 1 |
00420 | UNT | Message trailer | M | 1 |
Detail
No segment in this section.
Summary
No segment in this section.
Changes vs D.96A
Top-level differences between D.96A and D.21B for the BANSTA 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
GEIin the header section (status M, repeat ×1) — not present at the top of the corresponding D.96A section.
Segments removed vs D.96A
GISin the header section — present in D.96A but missing in D.21B at the same level.
Structural example
Minimal example of an BANSTA D.21B message with mandatory segments only. The goal is to show the exact version declared in UNH (BANSTA:D:21B:UN) — not to replicate a full business case (see the BANSTA D.96A page for an annotated example).
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL021001'
UNH+1+BANSTA:D:21B:UN'
BGM+350+BANSTA-2026-0099+9'
DTM+137:20260514:102'
RFF+AEK:PAYMUL-2026-0042'
NAD+MS+5410000000123::9'
NAD+MR+5410000000456::9'
LIN+1'
RFF+AEK:PAYMUL-2026-0042-L1'
STS+8+3+:::Payment executed'
MOA+9:1240.00:EUR'
UNT+11+1'
UNZ+1+CTRL021001'Common errors
- Misaligned UNH tokens — The
UNH+...+BANSTA:D:21B: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.21B, 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: BANSTA D.96A, BANSTA D.01B, BANSTA D.10A, BANSTA D.16B, BANSTA D.24A, BANSTA D.97A, BANSTA D.99B, BANSTA D.00B, BANSTA D.02B, BANSTA D.05A, BANSTA D.08A, BANSTA D.13B, BANSTA D.18B, BANSTA D.20B.
X12 functional equivalent: X12 824.