Duplicate Treaty Records: Match Scores and Merge Rules
On this page
- Key Takeaways
- What Are Duplicate Treaty Records at a Reinsurer?
- How Do Reinsurers Find Duplicate Treaty Records?
- What Match Score Makes Two Treaty Records Duplicates?
- How Do Three Candidate Treaty Pairs Score?
- How Should a Reinsurer Merge Duplicate Treaty Records?
- How Does Insurnest Help Keep One Record Per Treaty?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
The 2026 quota share showed EPI of EUR 18m in the portfolio report. The slip said EUR 9m.
The London team had booked it as "Northwind Insurance Co Ltd". The branch had booked "NORTHWIND INSURANCE COMPANY LIMITED".
Duplicate treaty records are two or more system records for the same reinsurance contract, often keyed by different teams.
They matter because every report that sums records, from EPI to exposure, counts the contract twice.
This guide gives you a weighted match-scoring table, hard override rules, three scored pairs and merge rules for the survivor.
Key Takeaways
- Normalise before matching. Most duplicates differ only in how the cedent is spelt.
- Score, do not guess. Weighted fields beat eyeballing a list.
- Let hard rules win. A different underwriting year means a renewal.
- Merge, never delete. Re-point every transaction and keep the old ID as an alias.
What Are Duplicate Treaty Records at a Reinsurer?
Duplicate treaty records at a reinsurer are separate records for one contract, with the same cedent, year, layer and terms.
They are different from duplicate payments; for those, see duplicate claim payments in reinsurance.
What damage do double-booked reinsurance contracts cause?
Double-booked reinsurance contracts cause damage wherever records are summed or transactions are split.
- Doubled EPI and exposure. Portfolio and capital reports overstate the line.
- Split claims. Some losses post to one record, some to the other.
- Two statements. The cedent receives conflicting accounts.
- Broken audit trail. Neither record shows the true position.
- False capacity limits. Line checks see twice the share and may block new business with that cedent.
How Do Reinsurers Find Duplicate Treaty Records?
Reinsurers find duplicate treaty records in two steps: group likely pairs into blocks, then score each pair on weighted fields.
BLOCKING QUERY (candidate pairs)
Group treaty records by:
normalised_cedent_name (or cedent LEI)
underwriting_year +/- 1
treaty_type
Keep groups with 2+ records; compare every pair in the group.
Blocking keeps the work small. A 5,000-treaty register would otherwise need about 12.5 million comparisons.
| Field | Agreement | Points |
|---|---|---|
| Cedent | Same LEI | 30 |
| Normalised name exact | 25 | |
| Name similar (spelling variant) | 15 | |
| Underwriting year | Same | 15 |
| Different | –20 | |
| Inception date | Same | 15 |
| Within 31 days | 8 | |
| Layer or section | Same attachment, limit, share basis and currency | 20 |
| Same type, different figures | 5 | |
| Broker reference | Same | 15 |
| Missing on one record | 0 | |
| Different | –10 | |
| Class and treaty type | Same | 5 |
The maximum is 100. Match broker references in the form your policy number mapping uses.
How should cedent names be normalised before treaty matching?
Cedent names should be normalised before treaty matching with fixed, written rules, applied the same way to every record.
- Lower-case and trim spaces.
- Remove punctuation and legal suffixes: ltd, limited, plc, co, company, sa, ag, gmbh.
- Standardise "&" to "and" and known spelling variants (harbour, harbor).
- Map the result to the cedent's LEI, where one exists.
The LEI is a 20-character code under ISO 17442. Each LEI identifies only one legal entity.
What Match Score Makes Two Treaty Records Duplicates?
A match score of 80 or more makes two treaty records probable duplicates, subject to hard rules that override the score.
| Score or condition | Decision | Action |
|---|---|---|
| Different underwriting year | Not a duplicate (renewal) | Link as prior year |
| Different attachment in the same programme | Not a duplicate (another layer) | Check programme structure |
| Different cedent LEI | Not a duplicate | Close |
| 80 – 100 | Probable duplicate | Merge after checker review |
| 55 – 79 | Possible duplicate | Clerical review with the slip |
| Below 55 | Distinct | Close |
This three-band rule follows the classic Fellegi–Sunter approach to record linkage.
A Census Bureau research report describes it: match above the upper threshold, review between, non-match below.
Set your thresholds from a sample you have checked by hand, then adjust them.
When should a reinsurer run the duplicate treaty check?
A reinsurer should run the duplicate treaty check at set-up, monthly, and before each renewal season and quarter-end close.
- At set-up. Score every new record against the register before saving it.
- Monthly. Run the full blocking query over records created that month.
- Before 1 January, 1 April and 1 July. Renewal peaks create the most double keying.
- Before quarter-end. Duplicates inflate the EPI that finance reports.
The check at set-up is the cheapest. A duplicate stopped before its first premium posts needs no merge at all.
How Do Three Candidate Treaty Pairs Score?
Three candidate treaty pairs, illustrated below, show a merge, a review and a renewal.
| Field | Pair 1 | Pair 2 | Pair 3 |
|---|---|---|---|
| Names | "Northwind Insurance Co Ltd" / "NORTHWIND INSURANCE COMPANY LIMITED" | "Harbor Mutual" / "Harbour Mutual Assurance" | "Delta General" / "Delta General" (same LEI) |
| Cedent | 25 | 15 | 30 |
| Underwriting year | 2026 / 2026: 15 | 2026 / 2026: 15 | 2025 / 2026: –20 |
| Inception | 1 Jan / 1 Jan: 15 | 1 Apr / 1 Apr: 15 | 1 Jan 2025 / 1 Jan 2026: 0 |
| Layer | 30% QS / 30% QS: 20 | EUR 10m xs 5m both: 20 | EUR 10m xs 5m both: 20 |
| Broker reference | Same: 15 | Missing on one: 0 | Different: –10 |
| Class | Same: 5 | Same: 5 | Same: 5 |
| Score | 95 | 70 | 25 |
| Decision | Merge | Review | Renewal (hard rule) |
Pair 2 went to review. The slip confirmed one contract, keyed twice by a branch, so it was merged.
Pair 3 is a renewal. Merging it would wipe out a year of history.
Instead, link the 2026 record to the 2025 record as its prior year, so renewal and loss history stay connected.
How Should a Reinsurer Merge Duplicate Treaty Records?
A reinsurer should merge duplicate treaty records in a fixed order, so no transaction is lost or counted twice.
- Choose the survivor. Apply the rule below.
- Re-point transactions. Premiums, claims, cash, bordereaux and documents move to the survivor.
- Reverse double-counts. Where both records took the same premium, reverse one.
- Check shares. Recalculate with reinsurer participation share calculation.
- Retire the duplicate. Status "merged into [survivor ID]", kept as an alias.
- Log it. Who merged, when, and why, with the score and evidence.
Update the reinsurance treaty register so the alias resolves to the survivor.
Which treaty record should survive a merge?
The treaty record that should survive a merge is the one whose terms match the signed slip, with the most transactions posted.
If both match and both carry transactions, keep the earliest created record. Never pick by whoever spots the duplicate first.
How Does Insurnest Help Keep One Record Per Treaty?
Reinsurance Treaty Management holds each treaty as one controlled digital record of structure, participation, retention and limits.
It keeps commission formulas, premium and settlement calculations, treaty versions and an audit trail of changes.
It does not detect, score or merge duplicates. Run the matching in your data tools, then keep the survivor as the controlled record.
Key Terms
- Blocking: Grouping records by a few keys so only likely pairs are compared.
- Clerical review: Manual check of pairs that score between the two thresholds.
- Survivor record: The record kept after a merge, holding all re-pointed transactions.
Sources
- U.S. Census Bureau: Overview of Record Linkage and Current Research Directions (W. Winkler)
- GLEIF: Introducing the Legal Entity Identifier (LEI)
- Insurnest: Reinsurance Treaty Management
Frequently Asked Questions
What are duplicate treaty records at a reinsurer?
Duplicate treaty records at a reinsurer are two or more system records for the same reinsurance contract, usually keyed by different teams under slightly different cedent names or references.
What damage do double-booked reinsurance contracts cause?
Double-booked reinsurance contracts cause doubled EPI and exposure, claims split across two records, two settlement statements and an audit trail that cannot show one true position.
How do reinsurers find duplicate treaty records?
Reinsurers find duplicate treaty records by grouping candidates on normalised cedent and underwriting year, then scoring each pair on name, year, inception, layer, broker reference and class.
How should cedent names be normalised before treaty matching?
Cedent names should be normalised before treaty matching by lower-casing, removing legal suffixes and punctuation, standardising '&' and spelling, then mapping each name to its LEI where one exists.
What match score makes two treaty records duplicates?
A match score of 80 or more out of 100 makes two treaty records probable duplicates. Scores of 55 to 79 go to clerical review, and hard rules override any score.
How do three candidate treaty pairs score?
Three illustrative candidate treaty pairs score 95, 70 and 25: one clear duplicate to merge, one for clerical review that proved a duplicate, and one renewal that is not.
How should a reinsurer merge duplicate treaty records?
A reinsurer should merge duplicate treaty records by choosing a survivor, re-pointing premiums, claims, cash and bordereaux to it, reversing double-counts and retiring the duplicate as an alias.
Which treaty record should survive a merge?
The treaty record that should survive a merge is the one matching the signed terms with the most transactions posted. Ties go to the earliest created record.

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 →