Function: submitPolicy

Supply input variables in a policyStructure to the insurer or MGA to submit a policy.

Usage: submitPolicy

Automatic underwriting may be used for certain simple risk products like extended product warranty or cell phone insurance, whereas complex products may go through a process of partial/manual underwriting.
Other functional contexts have to do with superseding contracts which affect the underlying policies by regulating part of their properties based on a general agreement or arrangement.
Furthermore, there are also situations where the MGA informs the insurance company of exceeding coverage limits within an agreed range, or applies for coverage which exceeds that range.
The functionVariant parameter enables a differentiation in requirements to suit the specific circumstances.

# Variant Description
1 new A policy application that will go through an underwriting process.
2 underwritten Registration of a new policy with a standard underwriting.
3 basedOnOffer Conversion of an offer into a policy, limited underwriting.
4 partOfPackage Addition of a new policy to an existing package policy.
5 partOfFrameworkAgreement A policy that inherits certain default values or features from a general agreement (e.g. employee benefits).
6 notificationThirdParty Supply of policy information to third parties who provide supporting services. For instance car or glass repair, salvage, repatriation and medical aid.
7 notificationSpecialLimit Providing the insurer with information on policies under special limit conditions.
8 requestSpecialLimit Application to the insurer for a policy under special limit conditions.

Technical specifications: submitPolicy

Input: submitPolicy

Name Variant Type Description
policyStructure
commonFunctional Entity for general information with regard to structure, handling and processing.
entityType all string Set to ‘default’.
dataCatalogVersion all ADNAFM Version of the data catalog on which the message is based.
functionVariant all APIVAR The function variant is used to determine the additional set of required and optional input and output data.
policy With entityType policyDetails.
businessLine all ADNBRA Classification of the type of contract. E.g. to be used for addressing within an 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, 2 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 takes/took effect.
paymentTermInMonths all integer The payment term is necessary to calculate the premium amount for the given term; monthly, bimonthly, quarterly, semesterly.
offerNumber 3 string offerNumber.
packageNumber 4 string packageNumber.
party all With the entityType policyHolder.
object Object with any entityType.
coverage all Coverage with any entityType.
party 6 With a third party entityType like appraiser, damageRepair.
Any additional attributes within the policyStructure.

Output: submitPolicy

There are three basic types of output which are described in the Output section of the Design principles chapter.

A positive response for the submitPolicy function may contain a dataset. The minimal result is a reference to the transaction with the number.
In order to simplify processing it is advised that the input data is returned in the output for reference. Any additional information that was collected during the transaction 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.
entityType all string Set to ‘default’.
dataCatalogVersion all ADNAFM Version of the data catalog on which the message is based.
functionVariant all APIVAR The function variant is used to determine the additional set of required and optional input and output data.
policy With entityType policyDetails.
businessLine all ADNBRA Classification of the type of contract. E.g. to be used for addressing within an 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.
contractNumber all* string Number of the policy attributed by the insurance provider.
referralNumber all* string The number assigned to refer. The insurer / underwriting agent can determine which attribute is used for this.
status all integer Indication of the current status.
effectiveDate all date Date on which the data of this entity takes/took effect.
paymentTermInMonths all integer The payment term is necessary to calculate the premium amount for the given term; monthly, bimonthly, quarterly, semesterly.
party 4, 5 Party of the entityType carrier.
party 4, 5 Party of the entityType policyHolder.
object Object with any entityType.
coverage all Coverage with any entityType.
party 6 With a third party entityType like appraiser, damageRepair.
Any additional attributes within the policyStructure.
  • One of contractNumber and referralNumber is required.
    If the request can be processed immediately (straight through processing), the contractNumber and the effectiveDate is required.
    When the request is redirected to an internal workflow, for instance for manual underwriting, the referralNumber is required to enable the client application to inquire after the status.

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