CASINT — EDIFACT Request for Legal Administration Action in Civil Proceedings Message (D.10A)
The CASINT message conveys the initial request sent to a legal administration to commence or pursue a civil proceeding: it identifies the parties, subject of the request, lodged documents, amounts at stake and target deadline. The formal response is carried by CASRES. This page summarises the segment structure as published by UN/CEFACT for directory D.10A.
Purpose
The CASINT message conveys the initial request sent to a legal administration to commence or pursue a civil proceeding: it identifies the parties, subject of the request, lodged documents, amounts at stake and target deadline. The formal response is carried by CASRES.
This page focuses on the structure published by UN/CEFACT for directory D.10A. The segments listed, their status (M / C), position and repetition factor are extracted from the official file casint_c.htm hosted on service.unece.org.
Segment structure
The CASINT D.10A message has 14 header entries, 28 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. |
|---|---|---|---|---|
0010 | UNH | Message header | M | 1 |
0020 | BGM | Beginning of message | M | 1 |
0030 | DTM | Date/time/period | C | ×9 |
0040 | LOC | Place/location identification | C | ×9 |
0050 | RFF | Reference | C | ×9 |
0060 | ATT | Attribute | C | ×9 |
0070 | FTX | Free text | C | ×9 |
0080 | SG1 | Group (×1) | C | 1 |
0090 | NAD | Name and address | M | 1 |
0100 | LOC | Place/location identification | C | ×9 |
0110 | SG2 | Group (×99) | C | ×99 |
0120 | MOA | Monetary amount | M | 1 |
0130 | DTM | Date/time/period | C | 1 |
0140 | FCA | Financial charges allocation | C | 1 |
Detail
| Pos. | Tag | Name | S | Rep. |
|---|---|---|---|---|
0150 | UNS | Section control | M | 1 |
0160 | SG3 | Group (×99) | M | ×99 |
0170 | NAD | Name and address | M | 1 |
0180 | SEQ | Sequence details | C | 1 |
0190 | LOC | Place/location identification | C | ×9 |
0200 | CTA | Contact information | C | 1 |
0210 | COM | Communication contact | C | ×9 |
0220 | RFF | Reference | C | ×9 |
0230 | ATT | Attribute | C | ×9 |
0240 | PRC | Process identification | C | 1 |
0250 | MEA | Measurements | C | ×9 |
0260 | DTM | Date/time/period | C | ×9 |
0270 | EMP | Employment details | C | ×9 |
0280 | FTX | Free text | C | ×9 |
0290 | SG4 | Group (×99) | C | ×99 |
0300 | DOC | Document/message details | M | 1 |
0310 | GIR | Related identification numbers | C | ×99 |
0320 | PYT | Payment terms | C | 1 |
0330 | DTM | Date/time/period | C | ×9 |
0340 | FTX | Free text | C | ×9 |
0350 | SG5 | Group (×1) | C | 1 |
0360 | NAD | Name and address | M | 1 |
0370 | LOC | Place/location identification | C | ×9 |
0380 | SG6 | Group (×99) | C | ×99 |
0390 | MOA | Monetary amount | M | 1 |
0400 | DTM | Date/time/period | C | 1 |
0410 | FCA | Financial charges allocation | C | 1 |
0420 | UNT | Message trailer | M | 1 |
Summary
No segment in this section.
Changes vs D.96A
The CASINT message is not published in directory D.96A. No "D.96A → D.10A" 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 CASINT D.10A message with mandatory segments only. The goal is to show the exact version declared in UNH (CASINT:D:10A:UN) — not to replicate a full business case.
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL010001'
UNH+1+CASINT:D:10A:UN'
BGM+702+CASINT-2026-CIV-0042+9'
DTM+137:20260514:102'
NAD+MS+5410000000123::9'
NAD+MR+5410000000456::9'
UNT+6+1'
UNZ+1+CTRL010001' Common errors
- Misaligned UNH tokens — The
UNH+...+CASINT:D:10A: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.10A, 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: CASINT D.16B, CASINT D.21B, CASINT D.24A.