Reinsurance cession management software that recovers what treaties owe

When reinsurance prices rise, every missed recovery costs more. Yet many mid-sized carriers still run cessions on spreadsheets, with the logic known to two or three people.

Each of the four gaps below leaks money the treaty already entitles you to, and the leak grows with every new contract.

• Contract terms scattered across spreadsheets and email
• Premium allocated by hand, with sliding scales and reinstatements easy to miss
• Claims that never attach to the treaty they should recover from
• Reinsurance accounting kept apart from the general ledger

InsureEdge's reinsurance module holds treaties and layers, facultative placements, and every term that drives a calculation: attachment points, retentions, limits, and co-reinsurance shares. Proportional and non-proportional covers sit side by side.

Sliding scale commissions, reinstatement premiums, and profit commissions follow the contract rules. A mid-year endorsement updates every position it touches, with a trace to the record that caused it.

Reinsurance sits on the same data as policy and claims, so a new policy or an endorsement updates what's ceded. A claim attaches to the right treaties when it's registered, and small losses add up toward an aggregate.

Recoveries are worked out and notified on time, before the notice window closes. The reinsurance team and the claims team look at the same figure.

Bordereaux from cedants and brokers arrive in many formats. We build the intake that checks each file for wrong currencies, out-of-range values, and missing fields before it reaches your accounts.

If you buy retrocession, we set it up on the same model one step further. Contracts, premium, and recoveries run from reinsurer to retrocessionaire, with your net retained risk visible across the chain.

Statements of account, receivables, and payables are kept by reinsurer and tied to your general ledger. Reinsurer balances age in plain view, so overdue amounts get chased in the month they fall due.

The data behind IFRS 17, Solvency II, and NAIC Schedule F reporting comes from the same records. Roles decide who can approve and submit each report.

• Net exposure by treaty and by layer
• Outstanding recoverables by reinsurer
• Reinsurer balances aged by month
• Detail from program level down to one claim

Claims already work with AI agents in InsureEdge, so an agent can flag a large loss against your layers as the claim opens. Agents for the reinsurance module itself follow.

Every function is an API, so the module runs beside Guidewire, Duck Creek, Sapiens, or the core you run, and reads policies and claims from it.

The rules recalculate when the triggering event is recorded. When a policy is endorsed or cancelled, ceded premium and commission update across every treaty it touches. Each updated statement of account traces back to the record that caused it, so you and your reinsurer work from the same position.

Yes. It covers quota share, surplus, excess of loss, stop loss, and aggregate covers, with attachment points, retentions, and co-reinsurance shares. Sliding scale commissions, reinstatement premiums, and profit commissions run in the rules without custom code.

If your policy and claims already run on InsureEdge, reinsurance shares their data. If they don't, the module connects through APIs to your policy, claims, billing, and general ledger systems. We work out the approach in the five-day review, before you commit to a build.

Yes. Treaty and facultative arrangements sit in the same module, with the same premium calculation, recovery steps, and reports. A mixed book runs in one place, without separate spreadsheets for facultative cover.

It depends on your systems, the history you migrate, and how complex your treaty book is. The module can go in on its own or with other InsureEdge modules. After the five-day review you get a timeline, the people involved, and the milestones before anything is signed.

A spreadsheet holds the terms but can't see a new policy, an endorsement, or a claim as it happens. The module updates cessions and recoveries from those records, keeps a trace of every calculation, and doesn't depend on the two people who built the workbook. Your book can grow by 10 treaties without the team growing with it.

Not on the reinsurance module itself yet. Accounts, policy, and claims already work with AI agents, and reinsurance follows. Until then, an agent on claims can flag a loss that should recover, and your team works the recovery in the module.