Function: submitClaim

Deliver information with regard to a notification of loss in order to register an insurance claim with an insurance provider.

Usage: submitClaim

This function is used to initiate the claim process with a first notification of loss. The insurance provider creates a claim file and assesses the claim. In the following steps the claim can be rejected, or claim handling will commence. These subsequent steps make use of the changeClaim function.

There is only one single variant for the submitClaim function.

# Variant Description
1 fnol First Notification Of Loss

The following rules apply to the function:

  • A notification of loss is related to one single policy only.
  • A notification of loss cannot pertain to a package policy itself, only to one of the underlying policies.
  • A loss or an event may be related to more than one policy (single or in a package). If that is the case, a separate notification of loss must be made for each policy that is applicable.

Technical specifications: submitClaim

Input: submitClaim

Name Variant Type Description
claimStructure
commonFunctional Entity for general information with regard to structure, handling and processing.
entityType 1 string Set to ‘default’.
dataCatalogVersion 1 ADNAFM Version of the data catalog on which the message is based.
functionVariant 1 APIVAR The function variant is used to determine the additional set of required and optional input and output data.
claim The claim entity is used for grouping claim-related data. A claim is a request made by the insured for insurer remittance of payment due to loss incurred, and covered under the policy agreement.
entityType 1 string Set to ‘default’.
lossNotificationDate 1 date Date on which the damage was notified.
DateOfLoss 1 date Date of the accident.
policy With entityType policyDetails.
businessline 1 ADNBRA Type of business line. To be used for addressing within a financial institution.
porCompany 1 PORMAA Identification of the insurance company. Applies to companies and authorized agents. The codes are maintained by SIVI.
afdDefinitionName 1 string Name of the AFD-definition.
afdDefinitionVersion 1 string Version of the AFD-definition.
contractNumber 1 string The identifying characteristic that a company (or underwriting agent) assigns to the policy.
incident The incident entity is used for grouping information about the circumstances and damage/loss due to an incident.
entityType 1 string Set to ‘default’.
causeOfLoss 1 string What is the cause of the loss suffered?
incidentType 1 date Code indicating the type of incident.
postalCode date Postal Code.
houseNumber string House number.
city string City.
object The entityType of an insured, named/registered object on the policy, or ‘lossObject’ for unspecified objects.
party With entityType policyHolder.
Any additional attributes within the claimStructure.

Output: submitClaim

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

A positive response for the submitClaim function may contain a dataset.
In order to simplify processing it is advised that the input data is returned in the output for reference. As mentioned in the Usage section, any additional information that was collected during the transaction may also be added to the output for reference purposes.

Name Variant Type Description
claimStructure
commonFunctional Entity for general information with regard to structure, handling and processing.
entityType 1 string Set to ‘default’.
dataCatalogVersion 1 string Version of the data catalog on which the message is based.
functionVariant 1 APIVAR The function variant is used to determine the additional set of required and optional input and output data.
claim The claim entity is used for grouping claim-related data. A claim is a request made by the insured for insurer remittance of payment due to loss incurred, and covered under the policy agreement.
entityType 1 string Set to ‘default’.
claimNumberCompany 1 string The identifying number of the claim with the company / underwriting agent. This number is linked to the claim file and (usually) does not change.
Any additional attributes within the claimStructure.

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