Reinsurance

Policy Number Mapping Between Cedent and Reinsurer: Key Spec

On this page

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.

FieldRuleWhy it mattersExample value
Cedent IDFixed code per cedentTwo cedents can share a policy numberCED-014
Cedent policy numberText; never trimmed, padded or reusedLeading zeros must survive0071234
Coverage IDOne row per base plan, rider or benefitRiders are ceded separatelyBASE, WOP
Insured sequence1 or 2 on a joint lifeJoint policies carry two insureds1
Treaty pointerTreaty and plan the cession sits underOne policy can span two treatiesTR-07
LayerRetention basis and ceded amountExcess and quota share split differentlyExcess of USD 1,000,000
Reinsurer cession IDIssued by the reinsurer; never reusedThe reinsurer's own keyRA-55120
Predecessor keyKey of the row this one replacedFollows conversions and reissues0071234 / BASE
Link typeControlled listSays why the number changedREISSUE
StatusControlled listActive, terminated, reissued, claimACTIVE
Effective from / toDates; rows never overwrittenShows what was true when2026-08-01 / open
Source fileFile name and load dateAudit trailinforce_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.

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.

RowCedent policyCoverageCession IDCeded amountPredecessorLink typeStatusFromTo
10071234BASERA-55120USD 2,000,000NoneNoneREISSUED2019-01-012026-07-31
20071234WOPRA-55121Follows baseNoneNoneREISSUED2019-01-012026-07-31
30094471BASERA-55120USD 1,500,0000071234 / BASEREISSUEACTIVE2026-08-01Open
40094471WOPRA-55121Follows base0071234 / WOPREISSUEACTIVE2026-08-01Open

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.

  1. Take the cedent's and the reinsurer's in-force files at the same quarter-end date.
  2. Load every key field as text. Never let a spreadsheet guess the type.
  3. Join on cedent ID, policy number, coverage ID, insured sequence and treaty pointer.
  4. List rows found on one side only, and search predecessor links for each.
  5. Flag any key with two active cession IDs, or any cession ID on two keys.
  6. Compare status and ceded amount on every matched row.
  7. 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

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

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 →
ShareLinkedInX

Read our latest blogs and research

Featured Resources

Reinsurance

Seriatim Data for Life Reinsurance: Validate Before Booking

Seriatim data for life reinsurance drives premiums, reserves and experience studies. Learn the checks that stop bad policy-level files reaching your books.

Read more
Reinsurance

Reinsurance Data Lineage: From Bordereau to Capital Filing

Reinsurance data lineage traces every number from bordereau to capital filing. Learn why end-to-end traceability is now a regulatory expectation, not a data-governance luxury.

Read more
Reinsurance

Life Reinsurance Cession Administration Off Spreadsheets

Life reinsurance cession administration still runs on spreadsheets at many reinsurers. See what a policy-level cession record needs and how to migrate safely.

Read more

Meet Our Innovators:

We aim to revolutionize how businesses operate through digital technology driving industry growth and positioning ourselves as global leaders.

circle basecircle base
Pioneering Digital Solutions in Insurance

Insurnest

Empowering insurers, re-insurers, and brokers to excel with innovative technology.

Insurnest specializes in digital solutions for the insurance sector, helping insurers, re-insurers, and brokers enhance operations and customer experiences with cutting-edge technology. Our deep industry expertise enables us to address unique challenges and drive competitiveness in a dynamic market.

Get in Touch with us

Ready to transform your business? Contact us now!

We respond within one business day.