Reinsurance Treaty Register: One Record of Every Treaty
On this page
- Reinsurance Treaty Register: Building One Trusted Record of Every Active and Expired Treaty
- Key Takeaways
- What Is a Reinsurance Treaty Register?
- How Is a Register Different From a Single Source of Truth for Terms?
- What Goes Wrong Without a Treaty Register?
- Why Should Expired Treaties Stay in the Register?
- What Fields Should a Treaty Register Hold?
- Which Lifecycle Statuses Should the Register Use?
- What Does a Register Extract Look Like?
- How Do You Build a Treaty Register Step by Step?
- Who Relies on the Register?
- Where Does Automation Help?
- Which Metrics Show the Register Is Trusted?
- What Should COOs and Compliance Leaders Do Next?
- Key Terms
- Sources
- Frequently Asked Questions
Reinsurance Treaty Register: Building One Trusted Record of Every Active and Expired Treaty
Last reviewed: November 2026
Ask three departments how many treaties you have, and you may get three numbers. The gap is usually the expired treaties that still pay claims.
Short answer: A reinsurance treaty register is one complete inventory of every active, expired and run-off treaty, with status, shares and documents linked. Reinsurers build it treaty by treaty and reconcile it against the ledger every quarter.
Key Takeaways
- A register is an inventory, not a document store. It lists every treaty and points to the governing terms.
- Expired does not mean finished. Run-off treaties belong in the register until every liability is closed.
- Statuses need owners. Each lifecycle change should have a named owner and recorded evidence.
- Reconcile to prove completeness. Any balance on a treaty missing from the register is a gap.
What Is a Reinsurance Treaty Register?
A reinsurance treaty register is a complete inventory of every treaty a reinsurer has written or bought. It holds one record per treaty, underwriting year and section.
Each record shows what the treaty is, where it stands and who owns it. It links to the documents rather than replacing them.
How Is a Register Different From a Single Source of Truth for Terms?
A treaty register answers which treaties exist and what status each has. A single source of truth answers what each treaty's terms actually say.
Both are needed, and they solve different problems. Our article on having no single source of truth for treaty terms covers conflicting versions of terms across teams.
The register is the index that sits above those terms. Without it, a perfectly maintained treaty record can still be missing from every report.
What Goes Wrong Without a Treaty Register?
Without a treaty register, each team builds its own list, and the lists drift apart. Problems then surface in reports, audits and claims rather than in daily work.
Why do reports disagree?
Reports disagree because each one starts from a different list. Finance may count treaties with balances, while underwriting counts treaties renewed this year.
Why is counterparty exposure understated?
Counterparty exposure is understated when expired treaties drop out of view. A reinsurer's share on an old long-tail treaty can still carry significant open claims.
Why do audits take longer?
Audits take longer because completeness has to be proven from scratch each time. A reconciled register lets you show completeness instead of rebuilding it.
Why Should Expired Treaties Stay in the Register?
Expired treaties should stay in the register because many still carry liabilities. Long-tail claims, adjustments and profit commissions can continue for years.
Risks-attaching and run-off terms extend this further. The Reinsurance Association of America describes run-off as continued liability for policies in force at termination.
Claims teams feel this first. When a loss arrives years later, they must find which treaty, year and share responds to that loss date.
What Fields Should a Treaty Register Hold?
A treaty register should hold enough fields to identify, classify and track each treaty, without copying the whole wording. Use eight field groups.
| Field group | Example fields |
|---|---|
| Identity | Treaty reference, name, underwriting year, section or layer |
| Direction | Inward, outward or retrocession, cedent, broker |
| Type and basis | Quota share, surplus, excess of loss, losses occurring or risks attaching |
| Scope | Class of business, territory, currency |
| Period | Inception, expiry, continuous or fixed, notice period |
| Structure | Limit, retention, estimated premium income, commission type |
| Counterparties | Reinsurers or cedent, signed shares, security at binding, collateral |
| Control | Lifecycle status, owners, document links, last review date |
Keep the register lean. Detailed terms belong in the treaty record, while the register holds what every team needs to find and classify a treaty.
For background on how treaty and facultative business differ, see our treaty vs facultative reinsurance guide.
Which Lifecycle Statuses Should the Register Use?
The register should use a small set of statuses, each with a clear exit condition. More statuses usually mean less consistent use.
| Status | Meaning | What moves it on |
|---|---|---|
| Quoted | Terms offered, not bound | Firm order or declinature |
| Bound | Terms agreed, setup in progress | Configuration complete |
| Active | In force and administered | Expiry or cancellation |
| Expired in run-off | No new cover, liabilities remain | All claims and balances closed, or commutation |
| Commuted | Liabilities settled by agreement | Final payment confirmed |
| Closed | No liabilities or balances remain | None, record retained |
The step from expired to closed matters most. Closing too early hides future claims, while never closing clutters every report.
Set a closure review for every expired treaty. Claims, finance and underwriting should each confirm nothing remains open before the status changes.
What Does a Register Extract Look Like?
This illustrative extract shows why active treaties are only part of the picture. All treaties and figures are invented.
| Treaty | Year | Direction | Status | Note |
|---|---|---|---|---|
| Casualty excess of loss | 2019 | Inward | Expired in run-off | Open claims, 4 reinsurer shares |
| Marine quota share | 2021 | Inward | Commuted | Final payment confirmed |
| Property quota share | 2026 | Inward | Active | Q3 account outstanding |
| Retrocession catastrophe cover | 2027 | Outward | Quoted | Firm order pending |
The 2019 casualty treaty is the record most likely to be missing elsewhere. It has no renewal and no new premium, yet it still pays claims.
The 2027 retrocession cover matters for the opposite reason. Quoted business belongs in the register too, so renewal planning and counterparty limits see it before it binds.
How Do You Build a Treaty Register Step by Step?
You build a treaty register by defining the unit of record, loading active treaties, backfilling expired ones and reconciling. The process has seven steps.
- Define the unit of record. Choose treaty, underwriting year and section as the key, and apply it everywhere.
- Set mandatory fields. Agree which fields must be complete before a record is accepted.
- Load active treaties. Start with treaties in force, where data is freshest.
- Backfill expired treaties. Add expired treaties with open claims or balances, largest first.
- Link documents. Point each record to the governing slip, wording and endorsements.
- Assign status owners. Name who can change each status, and require evidence for each change.
- Reconcile quarterly. Compare the register with ledger and claims systems, and close every gap.
Step four is usually the hardest. Older documents may sit in archives, which our guide to indexing the reinsurance archive addresses.
Who Relies on the Register?
Almost every reinsurance function relies on the register, each for a different question. That is why one owner and one definition matter.
| Function | Question the register answers |
|---|---|
| Underwriting | Which treaties are due for renewal or notice |
| Finance | Which treaties need accounts, adjustments or settlements |
| Claims | Which treaty and share respond to a loss date |
| Risk | Which counterparties carry exposure, and how much |
| Compliance | Which treaties feed regulatory returns and audits |
Regulatory returns show the stakes. For Solvency II, EIOPA has explained that S.30.03 and S.30.04 are completed when the outgoing reinsurance programme includes or overlaps the next reporting year.
S.30.04 also works from each reinsurer's share. A register holding periods and signed shares gives that return a reliable starting point.
Where Does Automation Help?
Automation helps by keeping the register and treaty records in one system, so they cannot drift apart. It does not decide when a treaty should be commuted or closed.
Reinsurance treaty management software supports treaty creation, structure management, participation and share configuration, amendments and versioning, and an audit trail. It gives teams centralised visibility of treaties and their terms.
People still own every status change. A commutation or closure is a business decision, and the system should record who made it and why.
Evidence of those decisions also matters to auditors. Our guide to the reinsurance audit trail explains what regulators expect to see.
Which Metrics Show the Register Is Trusted?
The best metrics show completeness, data quality and timeliness. Review them quarterly with each function that relies on the register.
| Metric | What it tells you |
|---|---|
| Balances on treaties missing from the register | Whether the register is complete |
| Records missing mandatory fields | Whether data standards hold |
| Status changes without evidence | Whether controls work |
| Days from binding to register entry | Whether new business is captured promptly |
| Expired treaties with no closure review | Whether run-off is managed |
What Should COOs and Compliance Leaders Do Next?
COOs and compliance leaders should define the register's unit of record and test completeness against the ledger. Both steps can start this quarter.
- Agree the record key and mandatory fields across underwriting, finance and claims.
- Reconcile last quarter's balances against the register and list every gap.
- Backfill expired treaties with open claims, starting with long-tail classes.
- Name one owner for each lifecycle status change.
Key Terms
- Treaty register: A complete inventory of every treaty, with status, key attributes and document links.
- Unit of record: The key that defines one register entry, such as treaty, underwriting year and section.
- Run-off: Continued reinsurer liability after termination for policies in force at that date.
- Commutation: An agreement that settles all remaining treaty liabilities for an agreed payment.
- Lifecycle status: The defined stage a treaty is in, from quoted to closed.
- S.30.04: A Solvency II template reporting outgoing reinsurance programme data by reinsurer share.
Sources
- EIOPA: Questions and answers on S.30.03 and S.30.04 (Q&A 1064) (submitted April 2017)
- Reinsurance Association of America: Glossary of Reinsurance Terms
- Insurnest: Reinsurance Treaty Management
Frequently Asked Questions
What is a reinsurance treaty register?
A reinsurance treaty register is a complete inventory of every treaty a reinsurer has written or bought, held as one record per treaty, underwriting year and section. Each record shows status, period, basis, counterparties, signed shares, owners and links to the governing documents.
Why should a treaty register include expired treaties?
A treaty register should include expired treaties because many still carry liabilities. Long-tail claims, premium adjustments, profit commissions and run-off cover can continue for years after expiry, and claims teams must know which treaty responds to an old loss.
How is a treaty register different from a single source of truth for treaty terms?
A treaty register is the index of which treaties exist and what status each has. A single source of truth for treaty terms holds the authoritative content of each treaty. Reinsurers need both, and the register should point to the governing version of terms.
What fields should a reinsurance treaty register hold?
A reinsurance treaty register should hold treaty identity, underwriting year and section, inward or outward direction, treaty type and basis, period and notice terms, currency, limits and retention, counterparties and signed shares, lifecycle status, owners, and links to the slip, wording and endorsements.
Which lifecycle statuses should a treaty register use?
A treaty register should use a small set of defined lifecycle statuses, such as quoted, bound, active, expired in run-off, commuted and closed. Each status needs a clear definition, an owner who can change it, and evidence recorded whenever it changes.
Who uses a reinsurance treaty register?
A reinsurance treaty register is used by underwriting for renewals, finance for closing and settlements, claims for identifying which treaty responds, risk for counterparty exposure, and compliance for regulatory returns and audits. Each team relies on the register being complete.
How does a treaty register support Solvency II reporting?
A treaty register supports Solvency II reporting by holding the treaty periods and per-reinsurer shares that outgoing reinsurance templates need. EIOPA has explained that S.30.03 and S.30.04 are completed when the outgoing programme includes or overlaps the next reporting year.
How do you check that a treaty register is complete?
A treaty register is checked for completeness by reconciling it against the ledger and claims systems every quarter. Any premium balance, claim or settlement booked to a treaty that is missing from the register shows a gap that must be investigated and closed.

Hitul Mistry
CEO, Insurnest
An InsurTech leader with more than a decade of experience across insurance and technology, focused on solving business problems with the help of technology. Has worked with brokers, insurance carriers, and reinsurance firms across the India, UAE, and US markets.
View LinkedIn profile →