Object Model

The core object model used in Socotra looks like this:

graph TD Policyholder --- Policy Policy --- Exposure Policy --- Claim Policy --- Endorsement Policy --- Renewal Policy --- Invoice Policy --- Document Exposure --- Peril Endorsement --- Document Renewal --- Document Claim ---- SubClaim Peril --- SubClaim SubClaim --- Payable Endorsement ---- Invoice Renewal ---- Invoice Invoice --- Document Invoice --- Payment Invoice --- FinancialTransaction click Policyholder "../api/policyholder.html#policyholderresponse3" _top click Policy "../api/policy.html#policy2response" _top click Exposure "../api/policy.html#exposureresponse" _top click Peril "../api/policy.html#perilresponse" _top click Claim "../api/claims.html#claim3response" _top click SubClaim "../api/claims.html#subclaimresponse" _top click Endorsement "../api/endorsements.html#endorsementresponse" _top click Renewal "../api/renewals.html#renewalresponse" _top click Invoice "../api/policy.html#policyinvoice2response" _top click Document "../api/policy.html#policydocumentresponse" _top click Payment "../api/invoice.html#paymentresponse2" _top click FinancialTransaction "../api/policy.html#financialtransactionresponse" _top click Payable "../api/claims.html#subclaimpayableresponse" _top

Many of these object types can be extended to store additional information. See the fields documentation for more details.

The Policy

The policy object contains details of the contract, including:

  • Product name

  • Exposures

  • Contract start and end dates

  • Premiums, taxes, and fees

  • Commissions

  • Additional data as defined by the insurer

Exposures

Exposures represent the person or asset that can experience an economic loss. The exposure object contains details of the particular exposure and a collection of covered perils, including:

  • Data as defined by the insurer

  • Individual coverages called “Perils.”

Perils

Perils represent coverages and causes of loss, and the limits to which an exposure is covered loss cause. These also can be extended with configurable data.

Note

See the Characteristics and Modifications topics for information about custom information and versioning associated with policies, exposures, and perils.

Claims and SubClaims

A claim is a container for subclaims, and it is the subclaims that represent potential losses and expenses. Reserves and payables are managed at the subclaims level. See the claims feature topic for more information.

Documents

Documents are rendered from templates or stored statically as PDF files. They can be attached to policies, endorsements, renewals, or invoices. See the document templates and static documents topics for more information.

Invoices and Payments

For policy transactions, such as initial issurance, endorsement, renewal, and cancellation, an invoice or series of invoices is generated. These are then marked as paid by the creation of a payment object. See the invoicing topic for more information.