Policies

​

Policy object

A policy represents the contract between the insurer and the insured. A policy is always linked to a customer, and can contain one or multiple assets. Policies are the core object on the Korint platform. It contains many different attributes, including but not limited to: General information

• product: the insurance product the policy belongs to
• author: the user who created the policy
• customer: link to the customer who owns the policy
• assets: links to the insured assets covered by this policy
• quote: if the policy is quoted, the currently active quote

Brokerage firm

• brokerageFirmId: the brokerage firm that manages the policy
• brokerageFees: the percentage breakdown of broker fees on the policy

Lifecycle

• status: the policy status determines what actions are currently possible for that policy, and informs other operations such as billing
• startedAt: the date at which the policy becomes or became active
• stoppedAt: the stop date of the policy
  • stop: if the policy is stopped, more details about the stop reason
• suspendedAt: the suspension date of the policy

Configuration

• billing configuration: the chosen billing configuration for this policy
• periodDuration: the length of the contract
• externalId: product specific id, typically used for external reports

Product specific information

• custom fields: a list of product specific attributes. For more details check out custom fields.

​

Policy statuses

​

Stopping a policy

When a policy is stopped, a cleanup workflow is automatically triggered to reconcile any billing differences. The system first waits for all pending payments to complete before computing the cleanup invoice. This ensures accurate reconciliation of the final billing state. Once all payments are finalized:

• If the policy was billed in advance and the stop date falls before the end of a billing period, a cleanup invoice is generated to refund the overpaid amount
• If there are outstanding amounts due, the cleanup invoice will charge the remaining balance

​

Internal notes

Internal notes let brokers attach free-form comments to a policy: context gathered during a phone call, the reason behind a derogation request, a reminder for a colleague picking up the file. They are a collaboration tool between brokers and are never part of the contractual record. Notes belong to the policy, not to a specific quote. A note written while preparing a quote remains visible after the policy is signed, throughout amendments, and even if the quote it referred to is later archived. This makes notes a reliable place to keep the history of a relationship with a customer.

​

Who can see a note

Internal notes are strictly internal:

• Never visible to the customer. Notes never appear on customer-facing documents, emails, or portals.
• Siloed by brokerage firm. A note is only visible to brokers belonging to the same brokerage firm as its author. When several firms work on the same policy (for example after a distribution change), each firm only sees its own notes — notes from other firms are not shown at all.

Each note displays its author’s name and business role, along with creation and last-edit timestamps, so readers always know who said what and when.

​

Editing and deleting notes

Ownership rules preserve the integrity of what each broker wrote:

• Anyone in the firm can read all notes written by colleagues of the same firm.
• Only the author can edit their own notes. Not even platform administrators can change the content of someone else’s note.
• Only the author can delete their own notes. A deleted note disappears for everyone but is retained internally for audit purposes; permanent removal can be performed by Korint on request (for example for data-privacy compliance).

Notes are plain text and can hold up to 5,000 characters each. There is no limit on the number of notes per policy.