Reinsurance Treaty Setup Checklist for Operations Teams

Reinsurance Treaty Setup Checklist: Configuring Shares, Limits and Commissions Right the First Time

Last reviewed: November 2026

A treaty is negotiated once but calculated hundreds of times. If one share or commission band is keyed wrongly at setup, every account after that inherits the mistake.

Short answer: A reinsurance treaty setup checklist lists every term that drives a calculation, from signed shares to commission bands, with its source clause. Teams configure from final documents, test sample calculations, then sign off under maker-checker control.

Key Takeaways

• Set up from signed documents only. Drafts and quotes create errors that must later be unwound.
• Check the terms that calculate. Shares, limits, retentions and commissions matter more than descriptive fields.
• Test at the edges. Sliding scale band boundaries and share totals are where setups fail.
• Two people, one record. Maker-checker control catches errors that one careful person misses.

What Is a Reinsurance Treaty Setup Checklist?

A reinsurance treaty setup checklist is the list of fields an operations team must configure before a treaty can be administered. Each field links to the clause it came from and the person who checked it.

The checklist is not a summary of the wording. It covers only what drives premium, claims, commission and settlement calculations.

Why Do Treaty Setup Errors Cost So Much?

Treaty setup errors cost so much because they repeat silently. A wrong commission band affects every account until someone notices.

Errors are rarely found at setup. They surface at the first settlement, the first large claim or the next audit, when unwinding them means restating several periods.

Speed adds pressure. Our guide to onboarding delays for newly bound reinsurance programmes explains why teams rush setup, and what slow onboarding costs.

What Should the Treaty Setup Checklist Include?

The treaty setup checklist should cover eight sections, each with fields that feed a calculation. Use it as a starting template and add class-specific items.

Record the source clause next to every field. When a dispute arises, you can show where each value came from.

Which Setup Errors Should You Test For?

You should test for the errors that change money, not the ones that change labels. Five checks catch most problems.

• Shares total 100% per section. A total above 100% usually means written lines were keyed instead of signed lines.
• Commission at every band edge. Calculate the sliding scale at each boundary loss ratio, not just the provisional rate.
• Retention unit. Confirm whether the retention applies per risk, per event or in the aggregate.
• Basis and dates. Check that risks-attaching or losses-occurring matches the wording and the earning pattern.
• Currency. Confirm the currency of limits, premium and settlement, and the exchange rate rule.

How Do You Set Up a Treaty Step by Step?

You set up a treaty by collecting final documents, extracting terms, configuring, testing and locking the record. The process has seven steps.

1. Collect final documents. Gather the signed slip or contract, wording, endorsements, signed lines and any side letters.
2. Extract the terms. Pull every field in the checklist into a structured record, with its source clause.
3. Resolve conflicts. Where the slip and wording disagree, refer the conflict to underwriting before configuring.
4. Configure the treaty. Enter structure, shares, limits, premium and commission rules in the administration system.
5. Check independently. A second person compares each configured value with the source documents.
6. Test-calculate. Run sample premium, claim and commission calculations, and agree the results with underwriting.
7. Approve and lock. Lock the record, and route every later change through a versioned amendment.

Step three is where many problems start. A slip and wording that disagree should never be settled by the person keying the data.

What Does a Test Calculation Look Like?

A test calculation runs the configured rules against simple inputs and compares the result with a manual answer. This illustrative quota share shows the idea.

The treaty cedes 30% with a provisional commission of 30%. The sliding scale pays 35% at a loss ratio of 55% or below, falling one point for each point of loss ratio, to 25% at 65% or above.

If the system returns 34% at 55%, the boundary is configured the wrong way. That one-point error would repeat on every adjustment for the treaty's life.

Run the same idea for shares and claims. Allocate a round claim, such as 1,000,000, across the signed lines and check that the shares add back exactly.

What Happens When Terms Change After Setup?

When terms change after setup, the change should create a new version with an effective date, not overwrite the original. Otherwise past accounts can no longer be recalculated on the terms that applied.

Common mid-term changes include an endorsement to limits, a reinsurer replaced after a downgrade, or a corrected share. Each one should pass the same checking and testing as the original setup.

Keep the old version visible. Auditors and claims teams often need to know which terms applied on a specific loss date.

Who Should Sign Off a New Treaty Setup?

A new treaty setup should be signed off by four roles under maker-checker control. Each confirms a different part of the record.

Operations configures and a second analyst checks. The underwriter confirms the economics, and finance confirms accounting, currency and settlement terms.

Setup quality also depends on cession logic. Our article on cession rules applied inconsistently shows what happens when configured rules drift from the contract.

Where Does Automation Help?

Automation helps with the two slowest parts of setup, reading documents and configuring calculations. It does not decide what an ambiguous clause means.

The Treaty Data Extraction AI agent reads slips, wordings and endorsements. It extracts terms such as cession percentages, retentions, limits, commission and brokerage, links each to its clause, and flags conflicting or missing terms.

Reinsurance treaty management software then holds the configuration. It covers participation and share setup, retention and limit setup, commission formulas, calculation rules, versioned amendments and an audit trail.

Analysts still review every flag and confirm each value. Software reads and calculates, while people decide what the contract says.

Do Market Data Standards Help With Setup?

Market data standards help by fixing the names and formats of core fields. They make extraction and checking easier, but they do not replace testing.

In London, the Core Data Record captures core transaction data at placement. It was updated to support treaty reinsurance in May 2026 with version 3.3.

Contract certainty also helps. Lloyd's expects all terms to be agreed by the time the contract is entered into, so setup can start from final terms.

Which Metrics Show Setup Quality Is Improving?

The best metrics show whether treaties are ready before they are needed, and whether setup errors reach accounts. Track them by treaty and by team.

Moving away from spreadsheets also changes these numbers. See spreadsheet-dependent treaty administration for why manual tracking breaks as volume grows.

What Should Heads of Reinsurance Operations Do Next?

Heads of reinsurance operations should standardise the checklist, enforce maker-checker and require test calculations. These steps work with any system.

• Adopt one setup checklist, with the source clause recorded for every field.
• Refuse setup from drafts, and log any treaty waiting for final documents.
• Require band-edge and share-total tests before a treaty goes live.
• Review every post-live setup error monthly and update the checklist.

Key Terms

• Treaty setup: Configuring a bound treaty's terms in the system used to calculate and administer it.
• Signed line: A reinsurer's final share after any signing down, used for all calculations.
• Sliding scale commission: A ceding commission that moves inversely with the treaty's loss ratio within set bands.
• Maker-checker: A control where one person enters data and a second person verifies it.
• Test calculation: A sample calculation run on configured rules and compared with a manual answer.
• Core Data Record (CDR): The London market standard for core transaction data captured at placement.

Sources

• Lloyd's: Core Data Record
• Reinsurance News: LMG's Data Council updates Core Data Record to support treaty reinsurance (18 May 2026)
• Lloyd's: Contract certainty
• Insurnest: Treaty Data Extraction AI Agent