General properties

The main characteristics of the policyStructure are the presence of the policy entity, a party entity of type policyHolder, an object entity to record the insured interest, and an entity to describe the coverage. In addition, all relevant entities are available to elaborate on any aspects of policy related information.

Mandatory components*

The table below contains the mandatory entities and attributes of the policyStructure. Please note: these are only the mandatory components; in this case only the presence of a policy. In many functions and messages, the message will be more extensive, including party, object and coverage entities, and often a commonFunctional entity for meta-data. See later in this section for a more detailed example.

Name Occur. Type Description
policyStructure 1..1 entity Structure of policy related data, based on AFD attributes.
policy 1..* entity The main entity of the policy structure.
entityType 1..1 string Unique identification of an entity.
businessLine 1..1 ADNBRA Type of business line. To be used for addressing within a financial institution.
porCompany 1..1 string Identification of the insurance company. Applies to companies and authorized agents. The codes are maintained by SIVI.
afdDefinitionName 1..1 string Name of the AFD-definition.
afdDefinitionVersion 1..1 string Version of the AFD-definition.
contractNumber 0..1 string The identifying characteristic assigned by a company or underwriting agent. Mandatory when available.

(* As indicated by the optional 0 occurrence, the contractNumber is not completely mandatory. When a new policy is submitted, the policy number is unknown because it has not been attributed yet. But once this is done, it becomes the singlemost important attribute within the policy structure. That is the reason it is mentioned here as mandatory in most cases, although not all.)

JSON example

Below is an example of a policyStructure, including hull coverage on a motor vehicle. Note that at the top level within JSON, the policyStructure entity is not explicitly mentioned. When the policyStructure is nested within other structures, such as within the packageStructure, the policyStructure is given an explicit tag. In XML, the structure is always explicitly defined at the highest level as well.

{
	"commonFunctional": [ {
		"entityType": "default",
		"dataCatalogVersion": "34C"
	} ],
	"policy": [ {
		"entityType": "policyDetails",
		"businessLine": "021",
		"porCompany": "A001",
		"afdDefinitionName": "Goed verzekerd op weg",
		"afdDefinitionVersion": "001.00",
		"contractNumber": "P20190101-010",
		"party": [ {
			"entityType": "policyHolder",
			"firstName": "Maria",
			"surname": "de Jong"
		},
		{
			"entityType": "premiumPayer",
			"firstName": "Dennis",
			"surname": "de Jong"
		} ],
		"object": [ {
			"entityType": "motorVehicle",
			"licensePlate": "SIVI20"
		} ],
		"coverage": [ {
			"entityType": "hullVehicle",
			"coverageCode": "2002",
			"deductibleAmount": 400.00
		} ],
		"financialTransaction": [ {
			"entityType": "booking",
			"effectiveDate": "2020-03-01",
			"collectionAccountNumber": "NL12BANK034567892"
		} ]
	} ],
	"document": [ {
		"entityType": "default",
		"sequenceNumber": 1
	} ]
}

Feedback

Thanks for your feedback.

Post your comment on this topic.

Post Comment