Every reserve movement on a claim is a movement in what reinsurers owe. When claims and reinsurance live in separate systems, reinsurance learns about those movements at bordereau time — monthly or quarterly — and the first sign of a large loss in the treaty is a number that has already been on the claim for weeks. InsightCW and InsightCede share claim movements as they happen.
What Cede receives
| Event | What Cede does with it |
|---|---|
claim.reserve_movement | Cedes the movement to the treaties that attach |
claim.payment_issued | Cedes the paid loss |
claim.payment_voided | Takes the paid cession back |
claim.recovery_received | A contra cession: the recovery reduces what is ceded |
claim.closed / claim.reopened | Status for the ceded record |
claim.large_loss | The reinsurers' large-loss notice |
cat.event_loss | A catastrophe's roll-up: recorded as a notice with the position against each CAT XoL treaty in force; never a second cession |
Each claim event carries the policy inception, so a risks-attaching treaty is matched on when the policy incepted rather than when the loss happened, and the catastrophe code where the claim is tagged to an event.
on a claim"] --> B["Outbox, same
transaction"] B --> C["Signed delivery
to Cede intake"] C --> D["Idempotent on
event id"] D --> E["Cessions to the
treaties that attach"] E --> F["Cede's net back to the
reserving worksheet"] style E fill:#efeafe,stroke:#7c6cf0
And back again
The reserving worksheet reads, for each claim, what InsightCede publishes as its net — what is recoverable — read-only over Cede's data API, or says why it cannot. An adjuster setting a reserve on a large loss sees the gross and the net side by side.
Why the catastrophe roll-up is not a cession
Each claim's movements already cede as they happen. Ceding the event total again would count the same dollars twice. The roll-up exists so reinsurance can see the occurrence against each catastrophe layer next to the per-claim ledger. See the CAT surge use case.