% Response.CharSet="utf-8" %>
|
This message is available for formal trial for at least six months from the date of approval by UN/ECE/TRADE/WP.4. Organisations are invited to trial this message. Comments on the results from the trial should be forwarded to their Rapporteur's Team Secretariat as soon as they are available. Based on the results of the trials, a UNSM may be issued. The segments, composite data elements, data elements and codes for use in the trial of this message are contained in the Draft directory. However, this information may differ from that in the Standard directory (UNTDID), even for material having the same identifying tags. |
| Message Type: | RETACC |
|---|---|
| Version: | D |
| Release: | 96B |
| Contr. Agency: | UN |
| Status: | 1 |
| Revision: | 1 |
| Date: | 96-07-04 |
| SOURCE: | Western European EDIFACT Board - MD7 |
|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.6, UN/ECE UNSM General Introduction |
|
This message also occurs in the following versions of this standard: D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B |
This specification provides the definition of the Reinsurance technical account message (RETACC) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
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.
The Reinsurance technical account message may be used for both national and international trade. It is based on universal commercial practice and is not dependent on the type of business or industry.
The RETACC will report technical and financial accounting entries that are informational (i.e. the latter items such as reserves will not impact the balance of the account). In the summary section of the RETACC, the ability is given to split the account balance into sub-amounts using different criteria. Such sub-amounts may be collectable and non- collectable. One may even go a level further and split a non- collectable balance into amounts per company or participant.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements.
Information to be provided in the Header section:
A 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 | 96B | |
| 0051 | UN |
A segment to give a processing indicator relating to the whole message.
A group of segments to specify relevant parties for the whole transaction.
A segment to specify the name and address and the related function of the party involved.
A segment to identify a person or department to whom communication should be directed.
A segment to identify a communication number of a department or a person to whom communication should be directed.
A segment to specify the references of the party identified in the leading NAD.
A segment to specify the message transaction date, accounting period, accounting year, accounting periodicity.
A segment to provide general message information, and/or narrative descriptions of references or account period given.
Information to be provided in the Detail section:
0100 Segment group 2: CUX-RFF-FTX-SG3 A group of segments to specify accounting breakdowns within the contract.
A 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.
A 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.
A segment used to provide free text information regarding the contract section reported in the sub-account (particularly for facultative contracts).
A group of segments to specify accounting entries for the sub-account, and if required the sub-account balance(s).
A segment to specify the accounting entries or the sub-account balance(s).
A segment to specify pertinent dates and periods relating to the entry.
A segment to specify the percentage used to calculate the entry, and/or the receiver's share percentage.
A segment to give an indicator to specify the way to process the entry.
A segment to identify the geographical scope to which the entry pertains or - for facultative accounts - the location of the risk.
A 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.
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.
A segment to specify a reference to a supporting document or message and/or (in case of losses reported), the event reference.
A segment to specify the date of transaction of the supporting document or message.
A segment to identify the means by which the referenced document or message was transmitted.
A segment used to provide free text information regarding the document or message that is referenced.
A segment used to prevent collisions between the detail and the summary sections of the message.
Information to be provided in the Summary section:
0270 Segment group 5: MOA-GIS-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.
A 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.
A segment to give a processing indicator relating to the settlement.
A group of segments used to make breakdowns of the amount reported, per party in the underlying market.
A 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.
A 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.
A segment to specify the references of the party named in the leading NAD.
A segment to give a processing indicator relating to the settlement by specific parties involved in the transaction.
A segment to specify the share amount of the party specified.
A segment to specify the means of settlement.
A segment to specify references related to the settlement of the account balance.
A segment to specify pertinent dates and periods relating to the settlement of the RETACC.
A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
| COM | Communication contact | |
| CTA | Contact information | |
| CUX | Currencies | |
| DTM | Date/time/period | |
| FTX | Free text | |
| GIS | General indicator | |
| LOC | Place/location identification | |
| MOA | Monetary amount | |
| NAD | Name and address | |
| PAI | Payment instructions | |
| PCD | Percentage details | |
| RFF | Reference | |
| UNH | Message header | |
| UNS | Section control | |
| UNT | Message trailer |
| ├─UNH Message header | ×1 | (M) |
| ├─GIS General indicator | ×6 | (M) |
| ├─Segment Group 1 | ×9 | (M) |
| │─├─NAD Name and address | ×1 | (M) |
| │─├─CTA Contact information | ×1 | (C) |
| │─├─COM Communication contact | ×5 | (C) |
| │─└─RFF Reference | ×6 | (C) |
| ├─DTM Date/time/period | ×4 | (M) |
| ├─FTX Free text | ×5 | (C) |
| ├─Segment Group 2 | ×99 | (M) |
| │─├─CUX Currencies | ×1 | (M) |
| │─├─RFF Reference | ×5 | (M) |
| │─├─FTX Free text | ×1 | (C) |
| │─└─Segment Group 3 | ×999 | (M) |
| │───├─MOA Monetary amount | ×1 | (M) |
| │───├─DTM Date/time/period | ×10 | (M) |
| │───├─PCD Percentage details | ×2 | (C) |
| │───├─GIS General indicator | ×10 | (C) |
| │───├─LOC Place/location identification | ×1 | (C) |
| │───├─FTX Free text | ×3 | (C) |
| │───└─Segment Group 4 | ×9 | (C) |
| │─────├─RFF Reference | ×1 | (M) |
| │─────├─DTM Date/time/period | ×1 | (C) |
| │─────├─COM Communication contact | ×1 | (C) |
| │─────└─FTX Free text | ×1 | (C) |
| ├─UNS Section control | ×1 | (M) |
| ├─Segment Group 5 | ×99 | (C) |
| │─├─MOA Monetary amount | ×1 | (M) |
| │─├─GIS General indicator | ×1 | (C) |
| │─├─Segment Group 6 | ×999 | (C) |
| │─│─├─NAD Name and address | ×1 | (M) |
| │─│─├─PCD Percentage details | ×1 | (C) |
| │─│─├─RFF Reference | ×2 | (C) |
| │─│─├─GIS General indicator | ×1 | (C) |
| │─│─└─MOA Monetary amount | ×1 | (C) |
| │─├─PAI Payment instructions | ×1 | (M) |
| │─├─RFF Reference | ×9 | (C) |
| │─└─DTM Date/time/period | ×3 | (C) |
| └─UNT Message trailer | ×1 | (M) |