EDIFACT message guide · Insurance
RETACC Reinsurance technical account
The UN/EDIFACT message used to report a party's position in the sender's books for a single reinsurance contract.
- Sent by
- Insurer, reinsurer or broker
- Received by
- Counterparty to the reinsurance contract
- Standard
- UN/EDIFACT · Batch message
- X12 equivalent
- No direct equivalent
What is the EDIFACT RETACC message?
RETACC is the UN/EDIFACT reinsurance technical account. The directory defines it as a message the sender uses to report to the receiver the receiver's position in the sender's books for one reinsurance contract. It is a type of account for services rendered and may initiate a payment.
A technical account summarizes, for a period, the premiums, claims, commissions and other items under a contract and the resulting balance. It is the basic accounting document of reinsurance, and its balances are later settled with RESETT.
How to read this diagram: the top row shows who sends RETACC, 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 RETACC 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
- Reporting quarterly accounts on a reinsurance treaty
- Showing premiums, claims and commissions for a period
- Initiating payment of a contract balance
Where it fits in the message flow
Structure
Mandatory segments in RETACC (directory D.21A)
In UN/EDIFACT directory D.21A, the RETACC message has 33 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
- GEI
- SG1 (NAD)
- DTM
- SG2 (CUX)
- UNS
- UNT
Practical example
RETACC in practice
A cedent prepares the second-quarter accounts for a quota share treaty. It sends each reinsurer a RETACC with the ceded premium, ceded claims paid, reinsurance commission and the balance due. The reinsurers check the figures and include the balance in the next settlement.
Implementation
Implementation considerations for RETACC
- Report one contract and period per account.
- Break down premium, claims and commission items clearly.
- Use contract references consistently across accounts and settlements.
- Follow the market's agreed accounting standards.
How ECOM helps
Automate RETACC 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
- RECALCReinsurance calculation
- REPREMReinsurance premium
- REBORDReinsurance bordereau
- RESETTReinsurance settlement
- LREACTLife reinsurance activity
- LRECLMLife reinsurance claims
- RECLAMReinsurance claims
- RECORDReinsurance core data
- ICASRPInsurance claim assessment and reporting
- ICSOLIInsurance claim solicitor's instruction
- IFTICLCargo insurance claims
- INSPREInsurance premium
Need help with RETACC?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.