EDIFACT message guide · Government and legal
CASRES Legal administration response in civil proceedings
The UN/EDIFACT message a court or legal administration uses to respond to a request to start or enforce a civil proceeding.
- Sent by
- Court or legal administration
- Received by
- Claimant, law firm or creditor
- Standard
- UN/EDIFACT · Batch message
- X12 equivalent
- No direct equivalent
What is the EDIFACT CASRES message?
CASRES is the UN/EDIFACT legal administration response in civil proceedings. The directory defines it as a legal response to a request for the lodgement of data to commence or enforce a civil proceeding.
The response tells the filer whether the request was accepted and what happened next: a case number issued, a hearing date set, a judgment entered or a request rejected with reasons. Case management systems update each matter from the responses. Responses can follow each step of a case, so one filing may receive several over its life.
How to read this diagram: the top row shows who sends CASRES, 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 CASRES 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
- Confirming acceptance of a filing with a case number
- Reporting rejections with reasons
- Reporting the outcome of enforcement requests
Where it fits in the message flow
Structure
Mandatory segments in CASRES (directory D.21A)
In UN/EDIFACT directory D.21A, the CASRES message has 18 segment positions arranged in 2 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
- DTM
- UNT
Practical example
CASRES in practice
The court processes 300 bulk claims and returns a CASRES for each: 296 issued with case numbers and service dates, and four rejected because the defendant's address was incomplete. The law firm's system updates each matter and queues the rejected claims for correction.
Implementation
Implementation considerations for CASRES
- Route rejections to people who can correct the filing.
- Record case numbers and dates against each matter.
- Follow the court's specification for response codes.
- Keep responses as part of the case record.
How ECOM helps
Automate CASRES 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 CASRES?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.