Custom fields
Each policy, asset, and customer has a list of custom fields which is configured at a product level, making it easy to adapt the three core entities to any insurance product’s needs.Custom field attributes
- name
- type: string, number, enumeration, date
- Business requirements
- whether it is required to quote the policy, to sign the policy, or not required at all
- whether its modification is allowed during the contract
- whether its modification during the contract should require a new quote or a new signature
- Validation rules such as maximum length, minimum and maximum values.
Example 1: B2B car insurance
- Policy custom fields: killing questions results
- Asset custom fields: car value, fiscal power, energy
- Customer custom fields: siret, address, number of employees, ceo email
- the asset’s fiscal power and energy are compulsory for quote calculation
- the asset’s fiscal power and energy can only be modified in a mid term agreement with a new quote and signature
- the asset’s car value is not required for quote, but because it appears in the contract document it is required for signature of the policy
- the asset’s car value can be modified in a mid term agreement with only a new signature
- the customer’s ceo email can be modified at any time
- Policy custom fields: documents are validated by broker
- Asset custom fields: address, size, type (House or apartment)
- Customer custom fields: first name, last name, monthly salary
- the asset’s size and type are required for quoting
- the asset’s size and type can only be modified in a mid term agreement with a new quote and signature
- the asset’s address is required for the initial signing, but afterwards can be modified at any time
- the customer’s first name and last name can be modified in a mid term agreement with a new contract signature
Once configured for a product, Korint will use these custom fields for various operations such as quoting, billing, and reports.

