For the people who answer for the outwards programme

Your reinsurance is worth what you can collect

A practical case for running the ceded desk on its own workbench — instead of spreadsheets and bordereaux by email, or a module inside the policy or claims system.

Written for CFOs, CROs and heads of reinsurance. The questions a buying committee actually asks: what goes wrong today, what changes, what it does not do, and how long it takes.

The cost of standing still

Four things the spreadsheet is quietly costing you

None of these are anyone’s fault. They are what happens when the outwards programme is run from a workbook and an inbox.

Unbilled

Ceded, but never asked for

A cession says the contract responds; nobody is owed anything until the reinsurer is billed. In a spreadsheet the gap between ceding and billing is invisible, and money sits in it for quarters.

  • Recoverables found at year end
  • Cash calls waiting for the quarterly account
  • Reinstatement premium nobody raised
  • Ageing that starts late
Free cover

Erosion tracked, cost forgotten

A layer that has eroded has consumed capacity and owes a reinstatement premium. A workbook that tracks one and not the other reports cover the carrier no longer has, at a price it did not pay.

  • Reinstatements counted, not priced
  • Erosion stored and drifting from the cessions
  • Retained losses that look recoverable
  • Surprises at renewal
Two nets

Underwriting’s net and finance’s net

When the policy system computes a ceded figure and the reinsurance workbook computes another, every month-end begins with reconciling them — and every board pack carries the one that won.

  • Net derived in two places
  • Manual true-ups at close
  • Schedule F assembled by hand
  • No single answer for the auditor
Inbox

Bordereaux by email

Statements struck in a workbook, attached to an email, acknowledged or not. Chasers written from scratch. The trail is somebody’s sent folder.

  • No record of what was sent, when, to whom
  • Chasers depend on who remembers
  • Disputes in email threads
  • Concentration noticed after the downgrade
The alternatives

Spreadsheets, a module, or a workbench of its own

Most carriers run the ceded desk one of two ways. Here is what each gets right, and what it cannot do.

Spreadsheets & bordereaux by emailA module inside the policy or claims systemInsightCede
Where a cession comes fromCopied from extracts, re-keyed monthlyOnly the transactions of the host system — a policy module cannot cede a claim, a claims module has no home for premiumPolicy and claim transactions from both systems, ceded by one engine
Which treaty year, in what orderA formula, a person’s judgementOften fixed to the host’s own yearRisks-attaching or losses-occurring from the contract; inuring order read, never assumed
ReinstatementsCounted by hand, often not pricedVariesFinite, priced pro rata from the loss date, derived from the ledger
NetOne of several versionsOwned by the host, contested by financeDerived once and published as a read; never written back
Notices, cash calls, chasersWritten from scratch when someone remembersRarely in scopeDrafted by an agent with the evidence, held until a person releases them
Credit and Schedule FAssembled at year endRarely in scopeConcentration watched continuously; Schedule F drafted from the ledger with what is missing named
Audit trailFile versions and a sent folderThe host’s audit logEvery decision, run and release recorded, with who prepared and who decided
What changes

The shifts your team will feel in the first month

Not features — the operating differences.

The work arrives prepared

The analyst opens a queue of decisions with their evidence and drafts — the chaser, the notice, the statement — instead of a blank email and three extracts.

The numbers come from one engine

Every cession is computed the same way from the contract, with a note on every outcome. Nobody re-derives net at month end.

Money is asked for sooner

Cash calls go when a paid loss crosses the threshold, not with the quarterly account; chasers go when an item ages, not when someone notices.

Credit risk is visible before it bites

Concentration against your limit, ratings and the news on each reinsurer, turned into a proposal — collateral or a limit change — for a person to decide.

The honest part

What it does not do, and what it needs from you

We would rather you heard it here than in month two.

It needs the transactions

Cede cedes what underwriting and claims report. If your policy and claims systems are not InsightUW and InsightCW, they need to send the same two event contracts — a project, not a setting.

Agents do not act alone on day one

Everything starts at Draft or Ask first, and the tenant ceiling stops at Ask first unless you raise it. Expect a person to answer every decision for months; that is the point.

It is not an exposure model

Cede does not receive limits profiles or aggregates, and does not price cover. The renewal pack carries experience and cost of cover, not modelled exposure.

Some structures are not built yet

Retrocession, aggregate deductibles and stop-loss are in the contract vocabulary and not implemented. Facultative placement stays in underwriting.

The first 90 days

A sequence that keeps the spreadsheet running until it is not needed

Run both in parallel for one period close; compare; switch.

1

Weeks 1–2

Deploy into your cloud on Postgres with your sign-in. Load the programme: treaties, layers, panel shares, reinsurers.

2

Weeks 3–5

Connect the policy and claims transactions. Backfill the open years; check every “nothing ceded” reason.

3

Weeks 6–8

Reconcile the position, recoverables and bordereaux against the workbook for one period. Explain every difference.

4

Weeks 9–11

Close a period in Cede: strike, send, chase. The agents prepare; your team answers every decision.

5

Week 12

Retire the workbook for the closed period. Review the agreement rates; leave the dial where the evidence says.

Scope it on your programme

Send us a treaty list and a month of bordereaux; we will show you the position Cede derives from them.

Request a demo