D10A
Message D10A/RETACC
Reinsurance technical account message
The RETACC is used by the sender to report to the receiver the latter's position in the sender's books with respect to one single reinsurance contract. It is in this sense a type of account for services rendered, and may initiate a payment flow either directly or via a periodical overview statement.
Message description
UNH
M(1) : Message headerA service segment starting and uniquely identifying a message. The message type code for the Reinsurance technical account message is RETACC. Note: Reinsurance technical account messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 RETACC 0052 D 0054 10A 0051 UN
GEI
M(6) : Processing informationA segment to give a processing indicator relating to the whole message.
SG1 M(9) : NAD-CTA-COM-RFF
A group of segments to specify relevant parties for the whole transaction.
NAD
M(1) : Name and addressA segment to specify the name and address and the related function of the party involved.
CTA
C(1) : Contact informationA segment to identify a person or department to whom communication should be directed.
COM
C(5) : Communication contactA segment to identify a communication number of a department or a person to whom communication should be directed.
RFF
C(9) : ReferenceA segment to specify the references of the party identified in the leading NAD.
DTM
M(4) : Date/time/periodA segment to specify the message transaction date, accounting period, accounting year, accounting periodicity.
FTX
C(5) : Free textA segment to provide general message information, and/or narrative descriptions of references or account period given.
SG2 M(99) : CUX-RFF-FTX-SG3
A group of segments to specify accounting breakdowns within the contract.
CUX
M(1) : CurrenciesA segment to specify the account rendering currency (statement currency) of the sub-account, and if required the settlement currency and the exchange rate used to convert from original account currency into settlement currency.
RFF
M(5) : ReferenceA segment used to tie the sub-account to a specific reference and to additionally identify the layer or surplus number of the contract for which data are rendered.
FTX
C(1) : Free textA segment used to provide free text information regarding the contract section reported in the sub-account (particularly for facultative contracts).
SG3 M(999) : MOA-DTM-PCD-GEI-LOC-FTX-SG4
A group of segments to specify accounting entries for the sub- account, and if required the sub-account balance(s).
MOA
M(1) : Monetary amountA segment to specify the accounting entries or the sub- account balance(s).
DTM
M(10) : Date/time/periodA segment to specify pertinent dates and periods relating to the entry.
PCD
C(2) : Percentage detailsA segment to specify the percentage used to calculate the entry, and/or the receiver's share percentage.
GEI
C(10) : Processing informationA segment to give an indicator to specify the way to process the entry.
LOC
C(9) : Place/location identificationA segment to identify the geographical scope to which the entry pertains or - for facultative accounts - the location of the risk.
FTX
C(3) : Free textA segment used to provide free text information regarding the entry. More particularly, the segment can be used to give loss details or additional information concerning bucket entry codes.
SG4 C(9) : RFF-DTM-COM-FTX
A group of segments to refer to supporting messages or documents. The segment may equally be used in case of loss amount reporting to specify the event reference.
RFF
M(1) : ReferenceA segment to specify a reference to a supporting document or message and/or (in case of losses reported), the event reference.
DTM
C(1) : Date/time/periodA segment to specify the date of transaction of the supporting document or message.
COM
C(1) : Communication contactA segment to identify the means by which the referenced document or message was transmitted.
FTX
C(1) : Free textA segment used to provide free text information regarding the document or message that is referenced.
UNS
M(1) : Section controlA segment used to prevent collisions between the detail and the summary sections of the message.
SG5 C(99) : MOA-GEI-SG6-PAI-RFF-DTM
A group of segments that may be used to specify account totals and subdivide them per type of settlement. At the same type this group can be used to break down the account into sub-balances using various criteria, such as collectable or non-collectable, and the embedded group 6 can be used to make breakdowns per party in the underlying market.
MOA
M(1) : Monetary amountA segment to specify the total account balances per settlement currency, or the possible breakdowns e.g. the amounts due in instalments, or per payment means or combined.
GEI
C(1) : Processing informationA segment to give a processing indicator relating to the settlement.
SG6 C(999) : NAD-PCD-RFF-GEI-MOA
A group of segments used to make breakdowns of the amount reported, per party in the underlying market.
NAD
M(1) : Name and addressA segment to identify the bank where the letter of credit was issued, the payer's and beneficiary's bank, the assuming company, the multiple cedants involved.
PCD
C(1) : Percentage detailsA segment used to specify the share of the party in the broker's order or in the 100% of the contract, expressed as a percentage.
RFF
C(2) : ReferenceA segment to specify the references of the party named in the leading NAD.
GEI
C(1) : Processing informationA segment to give a processing indicator relating to the settlement by specific parties involved in the transaction.
MOA
C(1) : Monetary amountA segment to specify the share amount of the party specified.
PAI
M(1) : Payment instructionsA segment to specify the means of settlement.
RFF
C(9) : ReferenceA segment to specify references related to the settlement of the account balance.
DTM
C(3) : Date/time/periodA segment to specify pertinent dates and periods relating to the settlement of the RETACC.
UNT
M(1) : Message trailerA service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.
Message structure
UNH, Message header M 1 GEI, Processing information M 6 --- Segment Group 1 ------------------------- M 9 -------+ NAD, Name and address M 1 | CTA, Contact information C 1 | COM, Communication contact C 5 | RFF, Reference C 9 | ---- -----------------------------------------------------------+ DTM, Date/time/period M 4 FTX, Free text C 5 --- Segment Group 2 ------------------------- M 99 -------+ CUX, Currencies M 1 | RFF, Reference M 5 | FTX, Free text C 1 | | --- Segment Group 3 ------------------------- M 999 ------+| MOA, Monetary amount M 1 || DTM, Date/time/period M 10 || PCD, Percentage details C 2 || GEI, Processing information C 10 || LOC, Place/location identification C 9 || FTX, Free text C 3 || || --- Segment Group 4 ------------------------- C 9 -----+|| RFF, Reference M 1 ||| DTM, Date/time/period C 1 ||| COM, Communication contact C 1 ||| FTX, Free text C 1 ||| ---- ---------------------------------------------------------+++ UNS, Section control M 1 --- Segment Group 5 ------------------------- C 99 -------+ MOA, Monetary amount M 1 | GEI, Processing information C 1 | | --- Segment Group 6 ------------------------- C 999 ------+| NAD, Name and address M 1 || PCD, Percentage details C 1 || RFF, Reference C 2 || GEI, Processing information C 1 || MOA, Monetary amount C 1 || ---- ----------------------------------------------------------+| PAI, Payment instructions M 1 | RFF, Reference C 9 | DTM, Date/time/period C 3 | ---- -----------------------------------------------------------+ UNT, Message trailer M 1