Book a systems review
Core insurance system

What is in the system.

The module list, line by line. Everything below is in the platform today and runs in the demonstration environment; where a capability is configured per client rather than shipped, the text says so.

General

Motor and non-motor classes
  • Motor private, commercial and PSV with digital certificates issued through DMVIC and printed by branch.
  • Non-motor classes defined in configuration: fire, burglary, all risks, WIBA, contractors, business interruption and more.
  • Quick underwriting for high-volume business and bulk policy processing for embedded and bank-distributed products.
  • Policy servicing: endorsements, renewals, reinstatements, refunds, contra and lapse, each with a premium audit trail.
  • Reinsurance allocation at underwriting, cash calls and settlements at claim.

Medical

Schemes, members and providers
  • Schemes and categories with cover limits, sub-limits, family sizes, loadings and exclusions.
  • Members and dependants with bulk upload, medical cards and card types.
  • Provider networks, contracts, specialist fees and service catalogues.
  • Pre-authorisation requests and service logs, then medical claims against the benefit.
  • Self-funded schemes with their own parameters, alongside insured ones.

Life

Individual and group business
  • Individual life with beneficiaries, instalments, accruals and maturity payout schedules.
  • Group, credit and mortgage life processed in bulk from lender and employer schedules.
  • Endorsements and contra transactions with a full premium audit trail.
  • Receipts and allocations matched to instalments, with agent and sub-agent commission rates.

Claim lifecycle

Notification, claimants, service providers, assessment, reserve movements that cannot be edited afterwards, and a claim lock while a transaction is in flight.

Payments and salvage

Payment requests drafted by one person and authorised by another, a separate execution step with bank reference, and salvage registered and realised against the loss.

Treaties

Quota share and excess of loss set up as configuration and applied at underwriting, with versioned allocations per policy.

Recoveries

Excess-of-loss recoveries recalculated on gross incurred less salvage, authorised independently, with cash calls above a threshold and receipts tracked to settlement.

Claim accounting

Every reserve, payment, salvage and recovery event maps to balanced journals in the general ledger, and a reconciliation screen shows what has posted, what is blocked and why.

Work queues

Maker and checker queues per user, so nothing waits in an inbox.

Finance

Receipting, allocations, commissions, sub-agent commissions, requisitions with independent approval and execution, petty cash, general ledger and reconciliation.

Distribution

Brokers, agents and bancassurance channels with their own commission handling, a quotation web service, a portal for policy creation, and the IRA return for a bancassurance intermediary.

Kenyan integrations

DMVIC motor certificates through AKI (issue, re-issue, verify, cancel), M-Pesa receipting, SMS and email notices, sanctions screening, bank payment files, Active Directory sign-in.

Reporting

More than two hundred report templates covering underwriting, accounts, GL listings, claims ageing, certificate expiry and audit trail, plus a designer for custom reports.

Control

Roles and permissions per screen and action, maker-checker on every financial transaction, immutable audit logs, document management.

Product Studio

A class of business is defined through its risk fields, rating inputs, cover period rules, clauses, taxes and levies, in configuration on the subclass. The underwriting team does it with us the first time and alone after that.

Deployment

PostgreSQL, in a cloud region you choose or on your own servers. The full core, or the claims and reinsurance modules beside an existing core through APIs.

Engineering

Over 1,900 automated tests across the platform and its claims and reinsurance services, run on every build.

Start with a thirty-minute systems review.

Tell us what runs your book today and what it cannot do. We come back with a written view of what would migrate, what would be configured and how we would stage it. If it makes sense, the next step is a demonstration on scenarios shaped like your own portfolio. Sanitised cases are fine; no customer data changes hands.