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.
CASINT D.10A

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.

Pos.TagNameSRep.
0010UNHMessage headerM1
0020BGMBeginning of messageM1
0030DTMDate/time/periodC×9
0040LOCPlace/location identificationC×9
0050RFFReferenceC×9
0060ATTAttributeC×9
0070FTXFree textC×9
0080  SG1Group (×1)C1
0090  NADName and addressM1
0100  LOCPlace/location identificationC×9
0110    SG2Group (×99)C×99
0120    MOAMonetary amountM1
0130    DTMDate/time/periodC1
0140    FCAFinancial charges allocationC1

Detail

Pos.TagNameSRep.
0150UNSSection controlM1
0160  SG3Group (×99)M×99
0170  NADName and addressM1
0180  SEQSequence detailsC1
0190  LOCPlace/location identificationC×9
0200  CTAContact informationC1
0210  COMCommunication contactC×9
0220  RFFReferenceC×9
0230  ATTAttributeC×9
0240  PRCProcess identificationC1
0250  MEAMeasurementsC×9
0260  DTMDate/time/periodC×9
0270  EMPEmployment detailsC×9
0280  FTXFree textC×9
0290    SG4Group (×99)C×99
0300    DOCDocument/message detailsM1
0310    GIRRelated identification numbersC×99
0320    PYTPayment termsC1
0330    DTMDate/time/periodC×9
0340    FTXFree textC×9
0350      SG5Group (×1)C1
0360      NADName and addressM1
0370      LOCPlace/location identificationC×9
0380        SG6Group (×99)C×99
0390        MOAMonetary amountM1
0400        DTMDate/time/periodC1
0410        FCAFinancial charges allocationC1
0420UNTMessage trailerM1

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.

edifact casint-d10a-example.edi
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: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.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.

Other versions of this message available on ediverse.io: CASINT D.16B, CASINT D.21B, CASINT D.24A.

← All EDIFACT versions