EDIFACT message guide · Government and legal
CASINT Request for legal administration action in civil proceedings
The UN/EDIFACT message used to lodge data with a court or legal administration to start or enforce a civil proceeding.
- Sent by
- Claimant, law firm or creditor
- Received by
- Court or legal administration
- Standard
- UN/EDIFACT · Batch message
- X12 equivalent
- No direct equivalent
What is the EDIFACT CASINT message?
CASINT is the UN/EDIFACT request for legal administration action in civil proceedings. The directory defines it as a request for the lodgement of data to commence or enforce a civil proceeding.
High-volume civil claims, such as debt recovery, are often filed electronically. The request carries the parties, the claim, the amounts and the action requested, such as issuing a claim or enforcing a judgment. The court answers with CASRES. It suits bulk claims, where many similar cases are filed at once, such as consumer debt recovery by utilities, telecom operators and lenders.
How to read this diagram: the top row shows who sends CASINT, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around CASINT and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.
When it is used
- Filing civil claims electronically
- Requesting enforcement of judgments
- Lodging bulk debt recovery claims
Where it fits in the message flow
Structure
Mandatory segments in CASINT (directory D.21A)
In UN/EDIFACT directory D.21A, the CASINT message has 36 segment positions arranged in 6 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.
- UNH
- BGM
- UNS
- SG3 (NAD)
- UNT
Practical example
CASINT in practice
A utility's law firm files 300 small debt claims with a court's bulk claims center. Its case management system sends a CASINT for each claim with the claimant, the defendant, the amount and the basis of the claim. The court issues the claims and responds with CASRES messages giving the case numbers.
Implementation
Implementation considerations for CASINT
- Follow the court's electronic filing rules and specification.
- Validate party and amount data before filing.
- Protect personal data contained in the claims.
- Track each filing through to the court's response.
How ECOM helps
Automate CASINT with ECOM
Solution
Enterprise Integration
Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.
Solution
EDI Integration
Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.
Industry
Financial Services
Secure file transfer and B2B integration for banks and financial institutions.
Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.
Related messages
Related government and legal messages
Need help with CASINT?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.