Function: underwrite

Assessment of the risk exposure for a policy application, a mid-term change, or special limit.

Usage: underwrite

Underwriting is done in several insurance processes during the policy life cycle. Each type of event has its own variant, these are listed in the table below.

# Variant Description
1 new Initial underwriting of the first policy version after application.
2 change Review of the initial underwriting in the context of a policy change. For instance a change of cover or insured amount, or a change of insured interest.
3 specialLimit Underwriting of a policy outside the standard scope of the MGA agreement.

New or initial underwriting is used for the first policy version upon application. The ‘new’ variant is often the completely developed underwriting function. This is considered the minimal requirement for this function. A mid-term change to the policy can be a reason to assess the impact of additional coverage or risk exposure of a new object, for instance.
Underwriting uses the policyStructure to deliver the input information for the underwriting function. The output also uses the policystructure to deliver policy details, including specific conditions, as well as possible clauses resulting from the underwriting process.
The underwriting function is based on the current VPI process and returns the outcome and status of the underwriting process (received, accepted, declined, apply as special limit, aborted).

NOTE that in order to facilitate a swift and easy user dialog one can allow for calls with partial filled input messages. In this way an underwriting dialog can be executed in subsequent steps using the validation feedback of the service in order to get a better dialog. The provider of the service has to specify which subsequent steps are supported and what data has to be specified. This way of working is primarily relevant for use with more complex products.

Technical specifications: underwrite

Input: underwrite

Name Variant Type Description
policyStructure
commonFunctional Entity for general information with regard to structure, handling and processing.
dataCatalogVersion all ADNAFM Version of the data catalog on which the message is based.
functionVariant all APIVAR Variant is used to determine the additional set of required and optional input and output data.
policy General policy information on contract level.
entityType all string Unique identification of an entity.
businessLine all ADNBRA Classification of the type of contract. E.g. to be used for addressing within a company.
porCompany all PORMAA The identification of the insurer is necessary to find the correct product and rate combination.
afdDefinitionName all string Name of the AFD-definition.
afdDefinitionVersion all string Version of the AFD-definition.
externalIndicative 1 string The identifying characteristic that an intermediary assigns. Can also be used as a temporary contract number.
effectiveDate all date Date on which the data of this entity take/took effect.
effectiveChangeDate 2 date Date on which the change takes effect. Not intended for the date on which the change is registered by the company / is registered on the contract.
party all Party with the entityTyp policyHolder.
coverage all Coverage of any entityType
all Any additional attributes within the policyStructure

Output: underwrite

The output of underwrite is a response body with an AFD structure containing a partial or full dataset. The minimal result is the outcome of the automated underwriting process.
In order to simplify processing it is advised that the input data is returned in the output for reference purposes. Any additional information that was collected as part of the underwriting process may also be added to the output for reference purposes.

Name Variant Type Description
policyStructure
commonFunctional Entity for general information with regard to structure, handling and processing.
dataCatalogVersion all string Version of the data catalog on which the message is based.
functionVariant all APIVAR Variant is used to determine the additional set of required and optional input and output data
policy General policy information on contract level.
entityType all string Unique identification of an entity.
businessLine all string Classification of the type of contract. E.g. to be used for addressing within an company.
porCompany all string The identification of the insurer is necessary to find the correct product and rate combination.
afdDefinitionName all string Name of the AFD-definition.
afdDefinitionVersion all string Version of the AFD-definition.
externalIndicative 1 string The identifying characteristic that an intermediary assigns. Can also be used as a temporary contract number.
effectiveDate all date Date on which the data of this entity take/took effect.
effectiveChangeDate 2 date Date on which the change takes effect. Not intended for the date on which the change is registered by the company / is registered on the contract.
party all Party with the entityTyp policyHolder.
coverage all Coverage of any entityType.
underwriting all Provide a risk indication (often green, orange, red) based on the deducted risk exposure for the to be insured risk.
all Any additional attributes within the policyStructure

Errors

When a negative response is generated, it follows the general rules as described in the Error section of the Status codes and error handling chapter.

Click below to see the Open Api Specification (3.0.0)

Feedback

Thanks for your feedback.

Post your comment on this topic.

Post Comment