Loss runs
Bring carrier loss runs in as text-based PDF, Excel or CSV. Each import is checked against the carrier’s own printed subtotal, reviewed row by row, and certified by a person before it counts.
Risk numbers you can defend.
LiteRMIS records where every number came from, what kind of number it is, and when it cannot answer.
From the carrier’s loss run to the reserve position
LiteRMIS connects intake, claims, reserving and the work around them, and keeps the source of each figure attached as it moves.
Claims
One workspace per claim, with its overview, financials, documents, tasks and workflow, and every change kept in the audit trail.
Reserves and actuarial
Chain ladder, paid development, Bornhuetter-Ferguson, expected loss ratio and case reserve development sit beside your actuary’s signed study. Missing inputs are named, never filled in.
Workflows and AI
Configurable workflows run the process. The assistant answers from your indexed documents and shows the source wording, so a person can check it before anyone relies on it.
Anyone can show you a number. LiteRMIS shows you where it came from.
Where an actuary has signed a study, the study governs, and the platform’s own estimate is a check against it. Without a study, the estimate is labelled Indicated, never Selected.
Principles
Defensible by design
Most systems store what somebody typed. LiteRMIS records where every number came from, what kind of number it is, and what it will not say.
Book a walkthroughEvery number shows its source
Imported rows keep the page they came from, how they were read and how sure the read was. A reviewer judges rows instead of trusting them.
It says when it does not know
No development factor, no exposure base, no case reserve: the platform names the gap instead of inventing a number. A blank is never a zero.
Your data stays in your own install
One installation per organization, with no tenant switcher and no data path between customers.
Four facts for your security review
One installation per organization
Each organization runs its own installation with its own database. There is no tenant switcher and no shared data path to get wrong.
A permission on every API route
Every API route checks a named permission. Certifying an actuarial study is a separate permission from entering one.
An audit trail on every record type
Every data model carries an audit policy, and certifications, rollbacks and discards are recorded with who and why.
Two-factor sign-in
Sign-in can require a one-time code sent by email. Connector credentials are referenced by secret name, never stored on the connector.
Bring us your messiest loss run.
We’ll reconcile it against the carrier’s own printed subtotal and walk you through the review before anything is certified.
Book a walkthrough