| Segment | Ebene | Beschreibung | Opt/Mand. |
|---|
| UNH | 0 | A service segment starting and uniquely identifying a message. The message type code for the Reinsurance core data message is RECORD. Note: Reinsurance core data messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 RECORD D A UN | Mandatory |
| BGM | 0 | To indicate the type of message, its function and its identifying reference. | Mandatory |
| DTM | 0 | To specify dates and times relating to the transaction and to the process stage. The 'transaction creation date and time' and the 'contract version date and time' are required. The use of the other values depends on the type of transaction. | Mandatory |
| AGR | 0 | A segment primarily used to specify the placing stage (i.e. quotation, order, endorsement) and - in case of an endorsement - the endorsement type. It can also be used to give some high- level indicators regarding the nature of the risk (e.g. contract type). | Mandatory |
| RFF | 0 | The segment must be used to specify the risk reference: this is the key reference that the risk will carry from the start to finish throughout each of the cycles - supplemented with the placing stage type and the contract version date/time stamp which can both change. Other references that may be specified at this level include: the 'link reference' which links this specific placement to the placement of one or more other contracts (required to indicate that a previous contract is renewed as a set of linked contracts); the 'password access reference' which may be required in some implementations to access the risk data; the 'authorising market reference' which is required in some implementations of the endorsement process (London practice only). | Mandatory |
| GEI | 0 | Used to specify at header level whether information has been modified. If both underlying policy and contract have the same data, then there is no need to specify all the insurance policy data: they are simply listed under the reinsurance contract, and a flag here indicates this fact. The segment can equally be used to indicate - specifically for an endorsement - if the data need to be made available to the bureau members (London practice only). The 'reason for declining' can be specified here in a coded format. A further code can be used to identify the character of the transaction. Lastly, codes can be used to indicate the scope of the requested common account protection. | Optional |
| FTX | 0 | Mainly used to specify the reason of the transaction in textual format. Additionally, it can be used to specify the contract name and to explain the nature of the revision or the endorsement. Even though the message allows for text, it should be used sparsely. | Optional |
| SG1 | 0 | SG1 | Optional |
| PNA | 1 | To specify the sender and receiver of the transaction, and optionally third parties such as the information originator (in case the message is simply passed on) and courtesy copy receivers. | Mandatory |
| BUS | 1 | To describe the business function of the party named. | Optional |
| RFF | 1 | To specify contract references for the party named. In case of placement or endorsement of a single contract, the contract reference will be specified. In case of a process that involves a group of contracts (in reinsurance terms: set of layers or bouquet), the contract group reference will be specified. In case of renewal, the previous contract reference(s) need to be specified. The original policy reference will only be used in case of a facultative (i.e. individual risk) placement whereby the policy details are not given as they are a subset of the contract data. The parent contract reference is specified when a declaration is placed. A reference may equally be specified in a response flow to indicate the reference number of the transaction to which this RECORD is a reply or addition. | Optional |
| SG2 | 1 | SG2 | Optional |
| CTA | 2 | To specify the contact within the named party. | Mandatory |
| COM | 2 | To specify the means of communicating with the named party contact. | Optional |
| SG3 | 0 | SG3 | Optional |
| IDE | 1 | To identify the contract and/or section level. | Mandatory |
| GEI | 1 | To indicate what type of general conditions apply and to what the amounts in the section relate (e.g. 100 % of policy, cedent share of original risk, ceded share of risk, etc.). The segment can also be used to indicate whether the primary source of the information is paper-based or electronic. | Optional |
| ICD | 1 | To describe the cover for the section. | Optional |
| RFF | 1 | To specify the contract reference in case a contract group reference was given in the header. It can also be used to indicate the layer/surplus number of the cover if relevant. The policy reference can be specified if a section is used to describe a policy. | Optional |
| ATT | 1 | To specify the class(es) of business, the type(s) of occupancy, the peril(s), the subject(s) of insurance and/or the origin of business that have been used as section or contract level criteria. The segment may also be used to specify the technical nature of the (part of the) contract within this section. | Optional |
| CUX | 1 | If all amounts in the section or contract are expressed in the same currency, the segment can be used to specify this by means of the reference currency; in case conversion agreements are pre-arranged, further repeats can also be used to specify original currencies (calculation base currency) and their exchange rate. | Optional |
| FTX | 1 | To specify the criterion used for the section or contract in textual form, and/or to give further cover details. It can equally be used to render a section heading. | Optional |
| SG4 | 1 | SG4 | Optional |
| PER | 2 | To identify any periods relating to this section or contract. | Mandatory |
| SG5 | 2 | SG5 | Mandatory |
| DTM | 3 | To indicate dates and/or duration for the contract coverage. The first repeat of the date/time/period segment will typically be used to render the 'start date' of the period. It can however also be used to specify the period duration. The second repeat is typically to be used to render the end date of the period. In case the first segment was used to specify the duration, then the second one will be used to specify the (estimated) end date and time. | Mandatory |
| GEI | 3 | To give date or period related indicators such as 'date included', 'date not known', etc. | Optional |
| SG6 | 1 | SG6 | Optional |
| LOC | 2 | To identify the geographical scope(s) or specific coverage location(s) that are used as selection criteria for this section. In case the section is in respect of a voyage, the various ports may be specified here as well. | Mandatory |
| MEA | 2 | To express a location in terms of longitude and latitude. | Optional |
| ADR | 2 | To express the risk location in address format if more appropriate. | Optional |
| SG7 | 1 | SG7 | Optional |
| CLA | 2 | To identify which clause(s) are related to the contract or policy. | Mandatory |
| APP | 2 | To specify the applicability of the clause. | Optional |
| MOA | 2 | To express amounts for the clause. | Optional |
| PCD | 2 | To express the rates applicable for the clause. | Optional |
| DTM | 2 | To indicate the clause reference data (e.g. the date from which cancellation starts), and/or the clause duration. The exact meaning will depend on the type of clause, e.g. retroactive date (sunrise clause), cessation date (sunset clause), etc. | Optional |
| GEI | 2 | To indicate that full details are to be found in the contractual documentation. | Optional |
| FTX | 2 | To provide a clause description. | Optional |
| SG8 | 1 | SG8 | Optional |
| PRV | 2 | To render proviso data of any nature. | Mandatory |
| APP | 2 | To describe how the proviso applies. | Optional |
| MOA | 2 | To express the proviso and/or the proviso basis as an amount. | Optional |
| RTE | 2 | To express the proviso as a rate. | Optional |
| DTM | 2 | To express the proviso as a duration or period. | Optional |
| QTY | 2 | To express the proviso and/or proviso basis (mainly for premium) as a quantity. Additionally, it can be used to specify the total number of reinstatements if the proviso = 'reinstatement coverage'. | Optional |
| FOR | 2 | To specify the formula used in calculating the proviso. | Optional |
| CUX | 2 | To render original currencies and pre-arranged exchange rates. | Optional |
| CLA | 2 | To specify the clause(s) to which the proviso relates. | Optional |
| GEI | 2 | To indicate that full details are to be found in supporting documentation. It can also be used in case the proviso = reinstatement coverage to express that the number of reinstatements is unlimited, and/or that the reinstatement premiums need to be calculated in the loss currency. It may also be used to specify general indicators related to the proviso such as reserve deposit release method, proviso frequency, loss adjustment expenses modality, reserve deposit use, etc. | Optional |
| FTX | 2 | To provide textual details relating to the proviso. | Optional |
| SG9 | 2 | SG9 | Optional |
| BAS | 3 | To specify one basis for the proviso. | Mandatory |
| APP | 3 | To specify how the basis is to be applied. | Optional |
| SG10 | 2 | SG10 | Optional |
| ATT | 3 | To specify the class of business, origin of business, subject of insurance, peril or type of occupancy that the proviso is in respect of. | Mandatory |
| PCD | 3 | To specify the percentage that the accounting class represents in the total reporting. | Optional |
| SG11 | 2 | SG11 | Optional |
| LOC | 3 | To specify one location linked to the proviso. | Mandatory |
| MEA | 3 | To describe a location in terms of longitude and latitude. | Optional |
| ADR | 3 | To describe the location to which the coverage, deductible or premium relates as an address. | Optional |
| SG12 | 2 | SG12 | Optional |
| PYT | 3 | To specify settlement terms. | Mandatory |
| PCD | 3 | To specify the percentage of the total due that needs to be settled. | Optional |
| SG13 | 2 | SG13 | Optional |
| RFF | 3 | To specify the relevant references. | Mandatory |
| MOA | 3 | To specify the amount of the instalment. | Optional |
| PCD | 3 | In case instalments are reported, the segment may be used to specify the percentage of the total amount to be settled in the instalment. The other usages are for commission tables as outlined in the group usage clarification. | Optional |
| DTM | 3 | To specify instalment related dates. | Optional |
| SG14 | 1 | SG14 | Optional |
| PNA | 2 | To identify the name of any party related to the reinsurance contract or policy. | Mandatory |
| ATT | 2 | To specify further attributes of the party. | Mandatory |
| ADR | 2 | To indicate one or more addresses of the party. | Optional |
| CTA | 2 | To specify the name of the authorising underwriter. | Optional |
| COM | 2 | To identify means of communication with the authorising underwriter. | Optional |
| RFF | 2 | For responding parties to specify their quote reference or (previous) contract references. | Optional |
| SG15 | 2 | SG15 | Optional |
| STS | 3 | To describe the involvement of the party. | Mandatory |
| RFF | 3 | To be used to indicate the line identification and when relevant the line number (the sequential number this specific line will have on the contract). Additionally, this segment may carry the 'broker system id', which is an identifying unique reference of the individual who accepted the reinsurers's conditions. | Optional |
| DTM | 3 | To indicate the authorisation period linked to the line. It may be used when the message is used as a market status report to specify the response date/time of each party on the list. | Optional |
| MOA | 3 | To express the involvement as an amount or to request it to be expressed in these terms. | Optional |
| PCD | 3 | To express the involvement as a percentage or to indicate that the line is expected in this format. Additionally, it can be used to report specific condition percentages attached to the party's line in a 'party involvement report'. | Optional |
| QTY | 3 | To express the line as a quantity, or to request the line to be written in such a format. | Optional |
| FTX | 3 | To give additional information regarding the format of the line. Additionally, it can be used to clarify the reason why a party declined interest in the risk. | Optional |
| SG16 | 3 | SG16 | Optional |
| RCS | 4 | To specify the general type of condition and its reference. | Mandatory |
| FTX | 4 | To render the condition in a textual form and optionally the description of the response (to be) given. | Optional |
| ATT | 4 | To specify the accounting class. | Optional |
| RFF | 4 | To specify the reference for the accounting requirements. | Optional |
| PCD | 4 | To specify the percentage split the underwriter wants to see for the specified accounting class. | Optional |
| SG17 | 0 | SG17 | Optional |
| DOC | 1 | To identify supporting documents in the widest sense of the term and details directly related to them. | Mandatory |
| RFF | 1 | To provide a reference to a password which enables access to supporting information. | Optional |
| IDE | 1 | To identify whether the information is related to the contract or to one of more specific sections, and if so, which ones. | Optional |
| COM | 1 | To specify the (possibly various) means of communication by which the information can, will or should be put at the disposal of the other parties involved. | Optional |
| EFI | 1 | To specify the link of a non-EDI document to an UN/EDIFACT message. | Optional |
| PNA | 1 | To specify the originator of the supporting information. | Optional |
| DTM | 1 | To identify the date and time that the supporting information was created and put at the disposal of the partners. | Optional |
| UNT | 0 | A 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. | Mandatory |
