Policy Number Mapping Between Cedent and Reinsurer: Key Spec
On this page
- Key Takeaways
- What Should a Policy Number Key Map Contain?
- Why Does Policy Number Mapping Between Cedent and Reinsurer Fail?
- How Should a Reissued Policy Be Linked to Its Cession?
- How Can a Reinsurer Test Its Key Map Against Last Quarter's Files?
- How Does Insurnest Help With Policy Number Mapping?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
"Show me the reinsurer's record for policy 0071234," the auditor asked.
The administrator found two. One sat under 71234, lapsed; the other sat under a new number, active, with no link to the first.
Policy number mapping between cedent and reinsurer is the crosswalk from each cedent policy and coverage to a reinsurer cession ID.
Done well, every ceded life can be traced from first issue to claim, across reissues and system changes.
This guide gives you a field-by-field key map spec, the shortcuts that fail and a filled example of a reissued policy.
Key Takeaways
- The key is more than a policy number. Add cedent, coverage, insured sequence and treaty pointer.
- Never overwrite. Close the old row and link the new one with a predecessor key.
- Store numbers as text. Spreadsheets strip leading zeros and round long numbers.
- Test every quarter. Join both in-force files and chase every unmatched row.
What Should a Policy Number Key Map Contain?
A policy number key map should contain every field needed to find one ceded coverage, on one life, under one treaty, at any date.
The RGA YRT treaty filed with the SEC asks for data on each benefit and each insured.
That includes all insureds on a joint life policy, with a ceding company identifier, policy number and treaty pointer.
| Field | Rule | Why it matters | Example value |
|---|---|---|---|
| Cedent ID | Fixed code per cedent | Two cedents can share a policy number | CED-014 |
| Cedent policy number | Text; never trimmed, padded or reused | Leading zeros must survive | 0071234 |
| Coverage ID | One row per base plan, rider or benefit | Riders are ceded separately | BASE, WOP |
| Insured sequence | 1 or 2 on a joint life | Joint policies carry two insureds | 1 |
| Treaty pointer | Treaty and plan the cession sits under | One policy can span two treaties | TR-07 |
| Layer | Retention basis and ceded amount | Excess and quota share split differently | Excess of USD 1,000,000 |
| Reinsurer cession ID | Issued by the reinsurer; never reused | The reinsurer's own key | RA-55120 |
| Predecessor key | Key of the row this one replaced | Follows conversions and reissues | 0071234 / BASE |
| Link type | Controlled list | Says why the number changed | REISSUE |
| Status | Controlled list | Active, terminated, reissued, claim | ACTIVE |
| Effective from / to | Dates; rows never overwritten | Shows what was true when | 2026-08-01 / open |
| Source file | File name and load date | Audit trail | inforce_2026-08.csv |
Which identifiers form the key between a cedent policy and a reinsurer cession?
The key between a cedent policy and a reinsurer cession is five fields together.
They are cedent ID, policy number, coverage ID, insured sequence and treaty pointer.
That composite key maps to exactly one active cession ID.
A policy number alone fails as soon as a rider is ceded, a second life is added or a treaty changes.
Keep personal data out of the key; see personal data in bordereaux.
How should replacement, conversion and reissue links be recorded in a key map?
Replacement, conversion and reissue links should be recorded on the new row as a predecessor key plus a link type.
Use a controlled list: CONV, REPL, REISSUE and MIGR for system migration.
The RGA treaty uses a transaction type code for events such as conversion and termination.
It also asks for the effective date of any reissue.
The National Life YRT treaty filed with the SEC wants attained age and duration on conversion or replacement lines.
Those fields only make sense if the original policy can be found.
Which status and date fields keep a ceded life traceable over time?
The status and date fields that keep a ceded life traceable are a controlled status, effective dates and the source file.
A row is closed by setting its effective-to date, never deleted.
That gives the reinsurance data lineage an auditor will ask for.
Why Does Policy Number Mapping Between Cedent and Reinsurer Fail?
Policy number mapping between cedent and reinsurer fails when teams take shortcuts that work for a month and break at the first change.
- Matching on name and date of birth. Typos, name changes and data rules make this unreliable.
- Overwriting the old number on reissue. The history disappears and claims cannot be traced back.
- Opening files in Excel. Microsoft confirms Excel removes leading zeros.
- Long numbers. Excel keeps 15 significant digits, so longer numbers are rounded to zero past the 15th digit.
- One row per policy. Riders and second lives vanish from the key map.
- Migration without a crosswalk. New system numbers replace old ones and every link breaks overnight.
National Life asks the cedent to tell the reinsurer of reporting format changes before use.
Layout changes belong in bordereau template mapping.
How Should a Reissued Policy Be Linked to Its Cession?
A reissued policy should be linked to its cession by closing the old rows and adding new rows that point back to them.
The example below is illustrative.
Policy 0071234 was issued on 1 January 2019 for USD 3,000,000 of term cover, with a waiver of premium rider.
The cedent retains USD 1,000,000, so Reinsurer A holds USD 2,000,000 on YRT under cession RA-55120. The rider sits under RA-55121.
On 1 August 2026 the face is cut to USD 2,500,000 and the cedent reissues the policy as 0094471.
The reinsured amount becomes 2,500,000 − 1,000,000 = USD 1,500,000.
| Row | Cedent policy | Coverage | Cession ID | Ceded amount | Predecessor | Link type | Status | From | To |
|---|---|---|---|---|---|---|---|---|---|
| 1 | 0071234 | BASE | RA-55120 | USD 2,000,000 | None | None | REISSUED | 2019-01-01 | 2026-07-31 |
| 2 | 0071234 | WOP | RA-55121 | Follows base | None | None | REISSUED | 2019-01-01 | 2026-07-31 |
| 3 | 0094471 | BASE | RA-55120 | USD 1,500,000 | 0071234 / BASE | REISSUE | ACTIVE | 2026-08-01 | Open |
| 4 | 0094471 | WOP | RA-55121 | Follows base | 0071234 / WOP | REISSUE | ACTIVE | 2026-08-01 | Open |
The reinsurer keeps both cession IDs because the same underwritten risk continues.
If the treaty treats the change as new business, new cession IDs are issued, but the predecessor link stays.
When a claim later arrives on 0094471, the claims team follows row 3 back to the 2019 underwriting in one step.
How Can a Reinsurer Test Its Key Map Against Last Quarter's Files?
A reinsurer can test its key map against last quarter's files by joining both in-force files on the full key and explaining every gap.
- Take the cedent's and the reinsurer's in-force files at the same quarter-end date.
- Load every key field as text. Never let a spreadsheet guess the type.
- Join on cedent ID, policy number, coverage ID, insured sequence and treaty pointer.
- List rows found on one side only, and search predecessor links for each.
- Flag any key with two active cession IDs, or any cession ID on two keys.
- Compare status and ceded amount on every matched row.
- Log the result, with file names, in your reinsurance audit trail.
Score the results over time with ceded data quality scores.
How Does Insurnest Help With Policy Number Mapping?
Reinsurance Bordereaux Reconciliation does not build, store or maintain key maps, and it does not map fields.
It compares calculated values with bordereaux, master, premium, claim and settlement records.
It flags differences between expected and recorded values, and shows reconciliation status by reinsurer.
The platform identifies the difference. Your data team decides whether a broken key caused it.
For cession record controls, see life reinsurance cession administration.
Key Terms
- Cession ID: The reinsurer's identifier for one ceded coverage on one life.
- Treaty pointer: The code that says which treaty and plan a cession sits under.
- Crosswalk: A table linking old identifiers to new ones after a reissue or migration.
Sources
- SEC EDGAR: RGA and Allstate Life of New York automatic/facultative YRT agreement, effective 1 April 2015 (Exhibit F)
- SEC EDGAR: National Life Insurance Company YRT agreement No. 7275-1, effective 16 October 2001 (Exhibit F)
- Microsoft Support: Keeping leading zeros and large numbers
- Insurnest: Reinsurance Bordereaux Reconciliation
Frequently Asked Questions
What should a policy number key map contain?
A policy number key map should contain the cedent ID, policy number, coverage ID, insured sequence, treaty pointer, layer, cession ID, predecessor link, status and dates.
Which identifiers form the key between a cedent policy and a reinsurer cession?
The key between a cedent policy and a reinsurer cession is cedent ID, policy number, coverage ID, insured sequence and treaty pointer, mapped to one cession ID.
How should replacement, conversion and reissue links be recorded in a key map?
Replacement, conversion and reissue links should be recorded as a predecessor key plus a link type from a controlled list, on the new row, never by overwriting.
Which status and date fields keep a ceded life traceable over time?
The status and date fields that keep a ceded life traceable are a controlled status, effective-from and effective-to dates, and the source file version.
Why does policy number mapping between cedent and reinsurer fail?
Policy number mapping between cedent and reinsurer fails through name matching, overwritten numbers, Excel dropping leading zeros, one row per policy and migrations without a crosswalk.
How should a reissued policy be linked to its cession?
A reissued policy should be linked to its cession by closing the old rows, adding new rows with a predecessor key and REISSUE link type, and keeping cession IDs.
How can a reinsurer test its key map against last quarter's files?
A reinsurer can test its key map by joining both in-force files on the full key as text, then listing unmatched rows, duplicate cession IDs and status conflicts.
How does Insurnest help with policy number mapping?
Insurnest Bordereaux Reconciliation compares calculated values with bordereaux, premium, claim and settlement records and flags mismatches. It does not build or maintain key maps.

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 →