Cedent Mergers in Treaty Records: Change Runbook
On this page
- Key Takeaways
- What Do Cedent Mergers in Treaty Records Change?
- Which Record Change Does Each Cedent Corporate Event Need?
- What Is the Runbook for Updating Treaty Records After a Cedent Merger?
- When Should a Cedent Merger Case Be Escalated?
- Where Do Handoffs Fail When a Cedent Merges or Renames?
- How Does Insurnest Support Treaty Record Changes After Cedent Mergers?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
The broker's email said the cedent had "rebranded" and attached new bank details. Finance updated the payee the same afternoon.
It was not a rebrand. It was a merger, and the email did not come from the broker.
Cedent mergers in treaty records change either who the counterparty is or only what it is called. Each needs a different record change.
It matters because a wrong change moves money, balances and sanctions exposure to the wrong legal entity.
This guide gives you an event-to-record change table, a seven-stage runbook, escalation rules and the handoffs that fail most.
Key Takeaways
- Name the event first. Rename, acquisition, merger and portfolio transfer differ.
- Check the LEI. GLEIF records legal entity events and successors.
- Re-screen on ownership change. New owners can change sanctions status.
- Verify bank details by call-back. Never from the email that asks.
What Do Cedent Mergers in Treaty Records Change?
Cedent mergers in treaty records change the counterparty, the name, or both, from a legal effective date.
The record change must follow the legal event, not the broker's description of it.
"Rebrand", "integration" and "new group name" can each hide a rename, an acquisition or a full merger. Ask for the legal document every time.
Which Record Change Does Each Cedent Corporate Event Need?
Each cedent corporate event needs a different record change, because each has a different legal effect.
| Event | Legal entity | LEI effect | Treaty record change | Screening | Bank details |
|---|---|---|---|---|---|
| Rename | Same entity | Same LEI, name updated | Update name, keep treaty IDs, add former name as alias | Screen new name | Only if notified; verify |
| Acquisition, entity retained | Same entity, new parent | Same LEI; parent data changes | No contract change; update group and concentration | Re-screen owners | Usually unchanged |
| Merger, cedent absorbed | Absorbed entity ceases | Record retired; successor shown | Re-point treaties to successor from effective date | Screen successor | New; verify |
| Portfolio transfer | Business moves to transferee | Both entities continue | Move affected treaties only, from transfer date | Screen transferee | Transferee's; verify |
Acquisitions also change your group exposure; update cedent concentration in reinsurer portfolios.
How can the LEI confirm a cedent rename or merger?
The LEI can confirm a cedent rename or merger because GLEIF tracks such changes as legal entity events on the record.
The LEI is a 20-character ISO 17442 code. Its Level 2 data shows "who owns whom".
GLEIF reports 20 types of legal entity events, including name changes, mergers and acquisitions.
The same post describes checks that retired records carry successor information, where relevant.
What Is the Runbook for Updating Treaty Records After a Cedent Merger?
The runbook for updating treaty records after a cedent merger has seven stages. The time limits shown are suggested defaults.
| Stage | Trigger | Action | Owner | Approver | Evidence | Time limit |
|---|---|---|---|---|---|---|
| 1. Detect | Cedent or broker notice, GLEIF event, court notice | Open a change case | Treaty admin | – | Notice copy | 2 working days |
| 2. Confirm legal facts | Case open | Name the event, effective date, successor | Legal | Head of legal | Registry extract, order, LEI record | 10 working days |
| 3. Re-screen | Facts confirmed | Sanctions and KYC on entity and owners | Compliance | MLRO | Screening result | Before stage 4 |
| 4. Change record | Screen clear | Rename or re-point, new version from effective date | Treaty admin | Checker | Before and after record | 5 working days |
| 5. Bank details | New details received | Call-back on a known number | Finance | Finance manager | Call note | Before next payment |
| 6. Downstream | Record changed | Bordereaux mapping, claims, accounts, exposure | Operations | Head of operations | Update checklist | 10 working days |
| 7. Close | All updated | Confirm balances sit on the right entity | Treaty admin | COO | Closing note | Month-end |
Keep the old entity's record for history. Run the KYC refresh in your counterparty KYC for reinsurance process.
Why must sanctions screening be repeated after a cedent acquisition?
Sanctions screening must be repeated after a cedent acquisition because the entity's owners have changed, even though its name has not.
Under OFAC's 50 percent rule, an entity owned 50% or more in aggregate by blocked persons is itself blocked.
OFAC FAQ 401 explains that indirect ownership through intermediaries counts. Screen the new owner chain, not just the cedent.
How should a reinsurer verify new cedent bank details after a merger?
A reinsurer should verify new cedent bank details after a merger by calling a known contact on a number already held.
Mergers are a natural cover story for payment fraud, because new bank details look expected.
The FBI's IC3 alert reports USD 55.5 billion of exposed email compromise losses from October 2013 to December 2023.
The alert advises verifying account-change requests through secondary channels. Never use contact details from the request itself.
When Should a Cedent Merger Case Be Escalated?
A cedent merger case should be escalated as soon as any of three conditions appears.
- Succession unclear at the effective date. Escalate to legal; hold payments to the new entity.
- Sanctions match. Stop the case; compliance and the MLRO decide.
- Bank details unverified. Hold payment; escalate to the finance manager.
Any case still open 30 days after the effective date goes to the COO.
Where Do Handoffs Fail When a Cedent Merges or Renames?
Handoffs fail when a cedent merges or renames wherever one team updates its records and the next team is not told.
| Handoff | What fails | Control |
|---|---|---|
| Treaty admin to finance | Cash still allocates to the old name | Alias on the old ID; see unallocated cash in reinsurance |
| Email to finance | New bank details accepted from email | Call-back, two approvers |
| Current to prior years | Old years' balances left on the absorbed entity | Re-point by year, with sign-off |
| Operations to risk | Group exposure counted twice | Update parent before month-end |
| Legal to operations | Part VII notice filed, operations never told | Legal copies operations on every notice |
For UK transfers, the PRA's statement of policy says Part VII transfers need court approval under section 111 FSMA.
It also says notice of the application goes to reinsurers, unless the court directs otherwise. That notice should start stage 1.
For a full book moving between reinsurers, see treaty portfolio handover for reinsurers.
How Does Insurnest Support Treaty Record Changes After Cedent Mergers?
Reinsurance Treaty Management keeps each treaty as a controlled record of structure, participation, retention, limits and commission logic.
When terms are amended, it keeps controlled versions and an audit trail of who changed what, with linked calculation history.
It does not manage legal entities, screen sanctions, hold bank details, send alerts or run approvals. Those stages stay in your other systems.
Key Terms
- Successor entity: The legal entity that takes over another's rights and obligations after a merger.
- Legal entity event: A change to an entity's reference data, life cycle or structure recorded in the LEI system.
- Call-back: Verifying a request by phoning a contact on a number already held.
Sources
- GLEIF: Introducing the Legal Entity Identifier (LEI)
- GLEIF: Metric of the month: legal entity events
- U.S. Treasury OFAC: FAQ 401, indirect ownership
- FBI IC3: Business Email Compromise: The $55 Billion Scam
- PRA Rulebook: The PRA's approach to insurance business transfers
- Insurnest: Reinsurance Treaty Management
Frequently Asked Questions
What do cedent mergers in treaty records change?
Cedent mergers in treaty records change who the counterparty is, or only what it is called. Treaties, balances, screening and bank details may all need updating from an effective date.
Which record change does each cedent corporate event need?
Each cedent corporate event needs a different record change: a rename updates the name, an acquisition updates ownership, a merger re-points treaties, and a portfolio transfer moves the affected treaties.
How can the LEI confirm a cedent rename or merger?
The LEI can confirm a cedent rename or merger because GLEIF records legal entity events, such as name changes and mergers, against the 20-character code, including successor information.
What is the runbook for updating treaty records after a cedent merger?
The runbook for updating treaty records after a cedent merger has seven stages: detect, confirm legal facts, re-screen, change the record, verify bank details, update downstream, and close.
Why must sanctions screening be repeated after a cedent acquisition?
Sanctions screening must be repeated after a cedent acquisition because new owners change the risk. Under OFAC's 50 percent rule, blocked owners holding 50% or more in aggregate block the entity.
How should a reinsurer verify new cedent bank details after a merger?
A reinsurer should verify new cedent bank details after a merger by calling a known contact on a number already on file, never one given in the email asking for the change.
When should a cedent merger case be escalated?
A cedent merger case should be escalated when legal succession is unclear at the effective date, a sanctions screen returns a match, or bank details cannot be verified before payment.
Where do handoffs fail when a cedent merges or renames?
Handoffs fail when a cedent merges or renames at cash allocation, bank details, prior-year balances, exposure aggregation and Part VII notices that never reach operations.

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 →