Claims · Agentic claims
Claims, moved to the age of agents.
We bring the agentic engineering. You bring the claims judgment and the reserving view. Claims are the main ingredient: every claim a durable record with an appended development history, integrity rules running as business-rules scopes, its own mounted file storage for advices and adjuster reports — and the renewal bordereau reconciled automatically against the book, hand in hand with UW Deepfield.
The claims process in two minutes
What ships
- Claim — the claim record: identity, stored lifecycle (Open → Reopened → Closed), and the development history (paid / outstanding per as-of date, appended never rewritten). The
ClaimMetricsscope computes the latest position and the ✓/✗ integrity checks (as-of order, paid monotone, closed ⇒ no outstanding). Each claim carries its own mountedfilescollection —<claim>/files, mapped to the mesh's storage atclaims/<claimAddressPath>— for any supporting content. - Enquiry — the question to the cedent (Draft → Sent → Answered), created under the claim it concerns; the Underwriting reconciliation raises one when a submission reports more outstanding than we hold.
- Register — the live book by stored status with per-programme paid/outstanding/incurred totals; the Claims Book page hosts it.
- A Tests area on every type running the full suite through the real scopes.
The flow
A renewal submission reports the claims bordereau, and the Underwriting module reconciles it against these records and highlights every difference. Where the pack reports more outstanding, it offers two ways forward:
- take the reported figure over as a
Source = Submissiondevelopment, or - raise an Enquiry asking the cedent for a formal advice.
Sample data ships separately in ReinsuranceDemo.