Reinsurance treaty reporting obligations that stay visible

Reinsurance treaties are negotiated with care and then administered from habit. The wording specifies when premium and claims bordereaux are due, what a claim has to exceed before it is individually notifiable, how quickly balances settle, what notice a change in underwriting guidelines requires and what access the reinsurer has to the cedent's records. In practice, most of that is carried in the heads of the people who have run the account for years.

That works until it does not. A treaty renews with a changed notification threshold and the old one keeps being applied. An account handler leaves and the bordereau cadence for three treaties goes with them. A dispute arises and the inspection right turns out to have sat unused for a decade, which weakens the argument that the cedent's records were ever relied upon.

None of this requires a different treaty. It requires the duties in the treaty to exist somewhere other than the wording, as dated obligations with owners, so that administration does not depend on institutional memory.

The duty families inside a treaty wording

Treaty obligations fall into recognizable families. Abstracting by family rather than clause by clause keeps the register usable across a portfolio of wordings that differ in drafting but not much in substance.

• Periodic reporting, premium and claims bordereaux, account statements and technical accounts, each with a frequency and a due date measured from period end
• Settlement, the period within which balances are paid once agreed, together with interest or offset provisions where payment is late
• Event notification, individual claim notification above a threshold, catastrophe notifications, and notification of circumstances likely to give rise to a claim
• Change notification, material changes to underwriting guidelines, retention, policy wordings, claims handling authority or outwards reinsurance protection
• Access and inspection, the right to inspect records, the notice required, the scope permitted and any limits on frequency or on the period that may be examined

The structure is the same one used for regulated vendor oversight, where each required provision is mapped to a field, a cadence and a named evidence artifact. The control matrix approach in vendor contract controls for OCC and FFIEC exam readiness translates directly to treaty administration.

What the treaty record should hold

The record is not the wording. It is a structured view of who owes what, by when, in what form, with the last submission visible against each duty.

• Each duty as a dated obligation. Record the party, the frequency, the due date formula and the responsible individual. A duty expressed as thirty days after quarter end should resolve to an actual date on a calendar, not a rule somebody applies
• Thresholds as fields, not memory. Hold the individual claim notification threshold, the currency and any aggregation rule on the record, and version it by treaty year so the correct threshold applies to the correct period
• Submission history per duty. Keep the date each bordereau or statement was actually provided alongside the date it was due. Lateness is only manageable once it is measured, and the measure is usually surprising
• Inspection rights with last exercise date. Note the right, the notice period and when it was last used, so that a long gap is a visible fact rather than a discovery made during a dispute
• Change notification triggers. List the changes that require notice and route them to the underwriting and claims functions that would make those changes, rather than leaving the duty with treaty administration alone

A five-step path to a working register

Step 1, Abstract one treaty year completely

Take a single year of wordings and pull every duty into the register, including the ones that look boilerplate. The first pass establishes the field set and reveals how much drafting variation actually exists across the portfolio.

Step 2, Resolve due dates to calendar dates

Convert every relative deadline into a generated calendar date for the current period. Duties expressed as formulas are reliably missed, because applying the formula is itself a task nobody owns.

Step 3, Version thresholds by treaty year

Attach notification thresholds, retentions and limits to the treaty year rather than the treaty, so that a claim arising in a prior year is assessed against the terms that applied then.

Step 4, Route change notifications to the source

Give underwriting and claims a visible list of the changes that trigger a notice obligation. The duty is breached by people who never read the treaty, so the control has to reach them.

Step 5, Report lateness, not just completion

Publish a simple view of due versus actual for each recurring duty. The gap is the operational signal, and it is the one measure that reliably improves once it is visible.

Why administration drifts

Treaty administration drifts for a structural reason. The people who negotiate the wording are not the people who perform most of the duties it creates, and the handover between them is usually a conversation rather than a record. Underwriting agrees a change notification clause; the underwriters who would trigger it never see it. Claims agrees a notification threshold; the handlers apply the threshold they remember from last year. Finance agrees a settlement period; the ledger runs on its own cycle. Each function is doing its job competently against an incomplete picture. The register fixes the handover rather than the behavior. Once the duties are visible, owned and dated, the same people perform them correctly without needing to read the wording, and the renewal conversation becomes better informed because both sides can see what was actually delivered during the period rather than what the wording required. There is a second structural cause worth naming. Treaty wordings are often finalized weeks or months after the inception date, so administration begins against a slip or a draft and is never fully reconciled to the executed text. The register should be built from the executed wording and compared against whatever administration has been using, because the differences between the two are both common and material, and they are easiest to resolve while the relationship is comfortable rather than during a contested claim.

Treaty duties, owners and evidence

The table sets out the duties that appear in most treaty wordings. Frequencies and thresholds vary by treaty and should be read from the executed wording.

Reinsurance is a relationship business, which is exactly why the administrative discipline tends to be informal. A treaty register is a small artifact with a disproportionate effect. It makes administration independent of the individual who has always done it, it gives both parties a factual basis for the renewal conversation, and it means an inspection or a dispute starts from a report rather than an archaeology exercise. The equivalent model for regulatory commitments is described in our financial services obligation management datasheet.

For related guidance, see Vendor contract controls for OCC and FFIEC examinations, The bank’s guide to DORA ICT third-party contract terms and What agentic AI changes in contract operations.

Aavenir Financial Services PracticeFinancial services practice at Aavenir, covering regulatory obligation tracking, vendor controls and contract administration.