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

REBORD Reinsurance bordereau

The UN/EDIFACT message that reports individual policy data and its effect on a reinsurance contract, such as how premiums or claims are built up.

Sent by
Insurer (cedent) or intermediary
Received by
Reinsurer
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT REBORD message?

REBORD is the UN/EDIFACT reinsurance bordereau. The directory defines it as a message made up of individual policy data and their impact on a reinsurance contract. It can report how reinsurance premium or claims figures are built up, or report the risks covered.

Bordereaux give reinsurers the detail behind the totals in technical accounts: which policies were ceded, their sums insured and premiums, or which claims arose. Reinsurers use them to check accounts and analyze the business they assume. Bordereaux are usually sent each period.

How the EDIFACT REBORD message worksDiagram of the UN/EDIFACT REBORD Reinsurance bordereau message. Insurer (cedent) or intermediary sends it to reinsurer. It usually starts the exchange. It is usually followed by RETACC. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: GEI (Processing information) and body and segment groups: the required SG1 loop with NAD (Name and address), DTM (Date/time/period), the required SG2 loop with ARD (Monetary amount function), CUX (Currencies), RFF (Reference) and the required SG3 loop with REL (Relationship) and UNS (Section control). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT REBORD message worksReinsurance bordereau: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeREBORDSENDERInsurer (cedent) orintermediaryRECEIVERReinsurerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYRETACCReinsurance technicalaccount2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage REBORDUNH … UNTSTART OF MESSAGEGEIProcessing informationBODY AND SEGMENT GROUPSMandatory group SG1 · repeats up to 9NADName and addressDTMDate/time/periodMandatory group SG2 · repeats up to 999ARDMonetary amount functionCUXCurrenciesRFFReferenceMandatory group SG3 · repeats up to 999RELRelationship+ required UNS and 3 conditional groups, starting with:PCDMOABlue 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 REBORD. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT REBORD message worksDiagram of the UN/EDIFACT REBORD Reinsurance bordereau message. Insurer (cedent) or intermediary sends it to reinsurer. It usually starts the exchange. It is usually followed by RETACC. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: GEI (Processing information) and body and segment groups: the required SG1 loop with NAD (Name and address), DTM (Date/time/period), the required SG2 loop with ARD (Monetary amount function), CUX (Currencies), RFF (Reference) and the required SG3 loop with REL (Relationship) and UNS (Section control). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT REBORDmessage worksReinsurance bordereau: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeREBORDSENDERInsurer(cedent) orintermediaryRECEIVERReinsurerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYRETACCReinsurance technical account2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message REBORD (UNH … UNT)START OF MESSAGEGEIProcessing informationBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 9NADName and addressDTMDate/time/periodUNSSection control+ required SG2 (ARD) and 3 conditionalgroups, starting with:PCDMOABlue 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 REBORD.Your trading partner's implementation guide adds itsown requirements.

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

  • Reporting ceded policies under a treaty
  • Showing how ceded premiums are calculated
  • Reporting the claims behind recoveries

Where it fits in the message flow

This message REBORD Reinsurance bordereau
Usually followed by RETACC Reinsurance technical account

Structure

Mandatory segments in REBORD (directory D.21A)

In UN/EDIFACT directory D.21A, the REBORD message has 39 segment positions arranged in 8 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
  • GEI
  • SG1 (NAD)
  • DTM
  • SG2 (ARD)
  • UNS
  • UNT

Practical example

REBORD in practice

Each quarter, a life insurer sends its reinsurer a REBORD listing every policy ceded under a surplus treaty, with the insured amount, the retained and ceded shares and the ceded premium. The reinsurer reconciles the bordereau totals with the technical account.

Implementation

Implementation considerations for REBORD

  • Make bordereau totals agree with technical accounts.
  • Protect personal data on individual policies.
  • Agree the fields and frequency with the reinsurer.
  • Use consistent policy and contract identifiers.

How ECOM helps

Automate REBORD with ECOM

Industry

Financial Services

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

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Solution

B2B Integration

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

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 REBORD?

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

Request a Demo Contact us