972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Insurance

RELIST Reinsured objects list

The UN/EDIFACT message that gives structured details of individual items to be reinsured when placing a contract or endorsement.

Sent by
Cedent or broker
Received by
Reinsurer
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT RELIST message?

RELIST is the UN/EDIFACT reinsured objects list. The directory describes it as giving partners involved in placing a reinsurance contract or endorsement structured details of individual items to be reinsured, partly for facultative risks. This generic item list can describe any type of insured object.

Objects can be buildings, vessels, aircraft or other risks, with their locations, values and characteristics. Reinsurers use the list to assess exposure, for example to natural catastrophes in particular areas. It is often used with RECORD, which carries the contract terms.

How the EDIFACT RELIST message worksDiagram of the UN/EDIFACT RELIST Reinsured objects list message. Cedent or broker sends it to reinsurer. It usually follows RECORD. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message), DTM (Date/time/period), AGR (Agreement identification) and RFF (Reference) and body and segment groups: the required SG1 loop with PNA (Party identification) and the required SG3 loop with IDE (Identity) and the required SG4 loop with ROD (Risk object type). 5 conditional segment groups are listed by their trigger segment.How the EDIFACT RELIST message worksReinsured objects list: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSRECORDReinsurance core dataRELISTSENDERCedent or brokerRECEIVERReinsurerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage RELISTUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodAGRAgreement identificationRFFReferenceBODY AND SEGMENT GROUPSMandatory group SG1 · repeats up to 99PNAParty identificationMandatory group SG3 · repeats up to 99IDEIdentityMandatory group SG4 · repeats up to 999RODRisk object type+ 5 conditional groups, starting with:CTAPERADRATTPRVBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for RELIST. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT RELIST message worksDiagram of the UN/EDIFACT RELIST Reinsured objects list message. Cedent or broker sends it to reinsurer. It usually follows RECORD. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message), DTM (Date/time/period), AGR (Agreement identification) and RFF (Reference) and body and segment groups: the required SG1 loop with PNA (Party identification) and the required SG3 loop with IDE (Identity) and the required SG4 loop with ROD (Risk object type). 5 conditional segment groups are listed by their trigger segment.How the EDIFACT RELISTmessage worksReinsured objects list: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSRECORDReinsurance core dataRELISTSENDERCedent or brokerRECEIVERReinsurerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message RELIST (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodAGRAgreement identificationRFFReferenceBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 99PNAParty identificationMandatory group SG3 · repeats upto 99IDEIdentityMandatory group SG4 · repeatsup to 999RODRisk object type+ 5 conditional groups, starting with:CTAPERADRATTPRVBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for RELIST.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends RELIST, 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 RELIST 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.

Expand diagram Download SVG

When it is used

  • Listing locations for property reinsurance
  • Detailing individual facultative risks
  • Updating schedules of insured objects

Where it fits in the message flow

Usually follows RECORD Reinsurance core data
This message RELIST Reinsured objects list

Structure

Mandatory segments in RELIST (directory D.21A)

In UN/EDIFACT directory D.21A, the RELIST message has 37 segment positions arranged in 10 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
  • AGR
  • RFF
  • SG1 (PNA)
  • SG3 (IDE)
  • UNT

Practical example

RELIST in practice

An insurer seeks facultative reinsurance for a portfolio of warehouses. Its broker sends reinsurers a RELIST with each warehouse's address, construction type, sum insured and protection features. The reinsurers model their exposure and decide their participation.

Implementation

Implementation considerations for RELIST

  • Describe objects with the attributes reinsurers model.
  • Use precise location data for catastrophe exposure.
  • Keep insured values current at each renewal.
  • Link the list to the placement it supports.

How ECOM helps

Automate RELIST with ECOM

Industry

Financial Services

Secure file transfer and B2B integration for banks and financial institutions.

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related insurance messages

All 18 insurance messages

Need help with RELIST?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us