% Response.CharSet="utf-8" %>
|SOURCE:||D9 - Insurance (SWG)|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, UN/ECE UNSM General Introduction
This message also occurs in the following versions of this standard:|
D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B
This specification provides the definition of the Intermediary system enablement or disablement message (ISENDS) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
The Intermediary system enablement or disablement message is a multi-functional message designed specifically for insurance intermediary systems administration allowing trading agreements between insurance companies and their agents (intermediaries) for insurer products to be initially authorised and consequently controlled by the insurer. This encompasses the enabling (or disabling) of separately identifiable software driven business functions (new business, mid-term adjustment, renewal etc.) and thus administering the authorisation for point of sale usage for the individual components of the function. Associated ranges of numbers for insurer products can be initially allocated and maintained via the use of this message.
The Intermediary system enablement or disablement message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.
The message contains information relating to the agreement between one insurance intermediary (using software supplied by one software house) and one insurer.
The message can be used for the following scenarios:
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.
A service segment starting and uniquely identifying a message. The message type code for the Intermediary system enablement or disablement message is ISENDS.
Note: Intermediary system enablement or disablement messages conforming to this document must contain the following data in segment UNH, composite S009:
To specify the function of the message as being an enablement or disablement.
To specify the type of an enablement or disablement, e.g. authorisation, new instruction etc.
To specify the creation date of the message.
A group of segments used to identify all the parties involved in the transaction.
To identify both the sender and intended receiver of the message, and the insurer and the intermediary in every case. The software house need only be identified when the sending party is the intermediary or software house itself. The marketing group should be identified where the Intermediary has membership of the marketing group
To identify the network address of the party. This may only be required when the message is to notify network address change.
A group of segments to identify any contacts for the insurance company whether a representative for the whole company or for one product. These may be contacts for underwriting referral, general product support or EDI Help Desk etc.
To specify the name and department details of one contact for the party.
To specify the contact number and applicable communication channel.
To specify the action to be taken as regards the contact information.
To specify the order of preference for contacts if there is more than one.
To specify the class of insurance product relevant to the contact.
A group of segments to specify one component of the software used to produce the message.
To specify the identity of the software product and version number.
To specify the dates relating to the software product. These are the date the software was released from the software house and the date the software was applied to the intermediaries system.
A group of segments to identify one policy accounting and/or reporting class or one insurer product relating to the insurer identified in the party group, depending on the transaction type.
To specify the business class and identifier for the insurer product.
To specify the agency reference and the policy booklet version for the intermediary for the insurer product. This may be required when the message is an authorisation. When the message is a new instruction, this information is only required if there is a change to the agency number and/or policy booklet version. This segment is used in conjunction with the date segment.
To specify the date that the data in the corresponding reference segment becomes effective. No associated date segment with the reference identifies that it is effective immediately.
To specify the insurer product scheme and/or marketing group identifier.
A group of segments to identify the business functions for one insurer product. For a request message, the functions identified will indicate what is available for the software loaded by the intermediary's system. For every subsequent authorisation of new instruction message from the insurer, there will be instructions related to the functions. The group should be used when the message is a request or authorisation and only in new instruction if the instruction relates to business functionality.
To specify one business function, e.g. new business, mid term adjustment etc.
To specify the actions to be performed relative to the authorities and documents for a business function.
To specify the date and time that an authority comes into effect, also supplies the expiry date and time of an authority - for instance EDI, for a given business function.
A group of segments to identify individual attributes of a business function that the intermediary has available on a system when used from intermediary to insurer and additionally indicates whether authority has been granted to use these attributes and any conditions associated when used from insurer to intermediary. The group should be used when the message is a request or an authorisation and only in a new instruction if the instruction relates to the attributes of business functionality, e.g. premium override.
A segment to specify one attribute of a business function, e.g. quote, EDI, etc.
To specify monetary amounts associated with the business function attribute.
To specify percentage information associated with the business function attribute.
To specify information on how to use the preceding segments.
A group of segments to identify documents at point of sale for one business function e.g. new business. In a request message this will identify the documents currently available on the Intermediary’s system. When used from insurer to intermediary this will be able to identify whether authority is granted, refused or revoked to produce the document at point of sale.
To specify one document.
To request use of document or grant or deny or revoke authority to use the document.
A group of segments providing information on amounts, ranges, and numbering associated with an insurer. Product identification, scheme identification and associated marketing group are all restated (if necessary) within this group. Group used in request when new ranges etc. are identified as being required by the intermediary, otherwise used in an authorisation and a new instruction.
To specify one insurance consumable and its number range, if applicable, that the range is for, e.g. covernotes.
To specify the action to be taken within the range stated.
To cater for monetary amounts instead of range numbers.
To specify the prefix of a document number.
To specify the effective date and time and/or the expiry date and time for one range identified.
To specify the marketing group or scheme to which the range applies if not applicable to all marketing groups or all schemes.
To identify a specific insurer product to be associated with the range. The absence of this segment indicates that the range applies across all of the identified insurer’s products.
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.
|BGM||Beginning of message|
|ICD||Insurance cover description|
|MKS||Market/sales channel information|
|QRS||Query and response|
|RCS||Requirements and conditions|
|├─UNH Message header||×1||(M)|
|├─BGM Beginning of message||×1||(M)|
|├─Segment Group 1||×9||(M)|
|│─├─PNA Party identification||×1||(M)|
|│─└─Segment Group 2||×9||(C)|
|│───├─CTA Contact information||×1||(M)|
|│───├─COM Communication contact||×9||(C)|
|│───├─GEI Processing information||×9||(C)|
|│───├─SEQ Sequence details||×1||(C)|
|├─Segment Group 3||×9||(C)|
|├─Segment Group 4||×99||(C)|
|│─├─ICD Insurance cover description||×1||(M)|
|│─├─MKS Market/sales channel information||×9||(C)|
|│─└─Segment Group 5||×9||(C)|
|│───├─PRC Process identification||×1||(M)|
|│───├─GEI Processing information||×1||(C)|
|│───├─Segment Group 6||×9||(C)|
|│───│─├─MOA Monetary amount||×1||(C)|
|│───│─├─PCD Percentage details||×1||(C)|
|│───│─└─RCS Requirements and conditions||×9||(C)|
|│───└─Segment Group 7||×9||(C)|
|│─────├─DOC Document/message details||×1||(M)|
|│─────└─QRS Query and response||×1||(C)|
|├─Segment Group 8||×9||(C)|
|│─├─RNG Range details||×1||(M)|
|│─├─GEI Processing information||×9||(C)|
|│─├─MOA Monetary amount||×9||(C)|
|│─├─MKS Market/sales channel information||×9||(C)|
|│─└─ICD Insurance cover description||×9||(C)|
|└─UNT Message trailer||×1||(M)|