Claims operations¶
Development area: Claims operations (insurance)
Claim notification, evidence, assessment, and authorized settlement. Settlement payment execution reuses payments; authority for indemnity decisions stays with the insurer.
Public description: https://fireflysoftware.io/openplatform/#insurance-development
Why this area exists¶
Claims need a case lifecycle (notify, evidence, assess, settle) that is not the same as loan servicing or KYC onboarding, but can reuse party, document, and payment foundations. This area states that intent and the honest gap: no dedicated claims repositories are published yet.
When to use it¶
Use this area when designing claim intake or settlement flows on OpenPlatform foundations. For payment rails and PSP boundaries, use payments directly.
Foundations already in OpenPlatform¶
| Module | Why it matters for claims |
|---|---|
| Customers | Claimant and insured party ids |
| Agreements | Policy or contract document context |
| Payments | Indemnity and refund payment execution |
| Shared services | Notifications and identity |
| Onboarding | Patterns for evidence collection over time |
Layer map¶
No dedicated claims repositories are published under firefly-oss for this area yet.
| Expected layer | Status (2026-10-18/19) |
|---|---|
| Experience | Not published |
| Domain | Not published |
| Core | Not published |
| Adapters | Claims systems and adjuster tools behind adapters |
How to start¶
- Identify party and agreement ids from foundation modules.
- Plan settlement through payments and adapters for rails/PSPs.
- Do not invent claim OpenAPI paths until a repository publishes them.
- Parent pin: 26.10.19 / Boot 4.1.1 / Java 25.
OpenAPI and events¶
Foundation specs: OpenAPI index. Events: stub.
Maturity notes¶
In development. Authorized settlement remains with the insurer’s delegated authority. This hub does not claim claims-system replacement.