Seriatim Data for Life Reinsurance: Validate Before Booking
On this page
- Seriatim Data for Life Reinsurance: Validating Policy-Level Files Before They Hit Your Books
- Key Takeaways
- What Is Seriatim Data in Life Reinsurance?
- Why Do Seriatim Files Arrive With Errors?
- Which Fields Should a Seriatim File Contain?
- Which Checks Should Every Seriatim File Pass?
- How Do You Decide Whether to Accept a File?
- How Do You Validate a Seriatim File, Step by Step?
- What Does a Validation Run Look Like?
- Why Can't Audits Replace File Validation?
- Who Should Own Seriatim Data Quality?
- Where Does Automation Help?
- Which Metrics Show Data Quality Is Improving?
- What Should Chief Actuaries Do Next?
- Key Terms
- Sources
- Frequently Asked Questions
Seriatim Data for Life Reinsurance: Validating Policy-Level Files Before They Hit Your Books
Last reviewed: November 2026
A seriatim file can balance to the penny and still contain a thousand wrong policies. Summary totals only tell you the errors cancel out.
Short answer: Seriatim data for life reinsurance should pass structural, field, treaty, period-to-period and financial checks before it is booked. Files that fail structurally go back, while record-level issues become a tracked exception list.
Key Takeaways
- Seriatim means one record per policy. That detail is what lets a reinsurer check rather than trust.
- Validate in layers. Each layer catches errors the others miss.
- Gate the file, not the record. Reject broken files, but book good records with tracked exceptions.
- Audits are not enough. They find systematic process faults, not individual wrong policies.
What Is Seriatim Data in Life Reinsurance?
Seriatim data in life reinsurance is a policy-by-policy file of reinsured lives or cessions. It replaces summary totals with one record per policy.
Under self-administered or bordereau arrangements, the cedent sends this file each period. The SOA's Commentary on Life Reinsurance Treaties contrasts it with bulk administration, where only summary data arrives.
Why does a reinsurer need it?
A reinsurer needs seriatim data to recalculate, not just receive. With policy detail, it can test premiums, retentions, limits and claims against its own records.
It also feeds the reinsurer's own experience studies. Our article on individual life reinsurance mortality data explains why that evidence matters for pricing.
Why Do Seriatim Files Arrive With Errors?
Seriatim files arrive with errors because each cedent extracts them from its own systems, in its own layout. The reinsurer sees the result, not the process behind it.
An SOA Reinsurance 101 session names lack of uniformity in cedent data as the main challenge for reinsurers. The 1994 commentary adds late reports, missing information and unannounced format changes.
What does lag do to the file?
Lag leaves the file out of date on arrival. Participants in the SOA's Life Reinsurance Treaty Construction study said lapsed policies can still show as in force because of reporting lags.
That inflates the in-force book and the premium you expect. It can also distort per-life accumulation checks.
Which Fields Should a Seriatim File Contain?
A seriatim file should contain every field needed to recalculate the cession and identify the life. Missing fields turn checks into guesses.
| Field group | Why it matters |
|---|---|
| Policy number and insured identifier | Links records across files and policies on one life |
| Date of birth, sex, smoker status, class | Drives rate lookup and experience analysis |
| Issue date and issue age | Sets the rate duration and treaty version |
| Ratings, such as table ratings or flat extras | Changes premium and eligibility |
| Face amount, retention, ceded amount | Tests the cession against treaty terms |
| Amount at risk and premium | Supports billing and reserve checks |
| Transaction type and effective date | Explains every movement since the last file |
Agree the list in the treaty, with an agreed layout. The SOA commentary suggests settling the level of detail, such as full date of birth or age only, up front.
Which Checks Should Every Seriatim File Pass?
Every seriatim file should pass five layers of checks, from structure to money. Run them in order, because later checks assume earlier ones passed.
| Layer | What it tests | Example error caught |
|---|---|---|
| Structural | Layout, row counts, control totals, duplicate keys | Rows dropped during extract |
| Field validity | Dates, codes, ranges, mandatory fields | Issue age that conflicts with date of birth |
| Treaty consistency | Retention, shares, classes, treaty version | Ceded amount that ignores the retention |
| Period-to-period | Changes versus last file | Date of birth or sex changing between periods |
| Financial | Totals versus billing and ledger | Premium total that differs from the cedent's bill |
What do period-to-period checks catch?
Period-to-period checks catch changes that no single file reveals. A policy that disappears without a termination record is the classic example.
Identity fields should not change between files. When they do, treat it as a data break until the cedent explains it.
How Do You Decide Whether to Accept a File?
Decide by severity: reject files that are structurally broken, and accept the rest with exceptions. That keeps good data flowing while errors are fixed.
| Finding | Action |
|---|---|
| Control totals do not match row data | Reject and request a new file |
| Mandatory field missing on many records | Reject or escalate to the cedent |
| Invalid values on a few records | Accept, hold those records as exceptions |
| Treaty mismatch on specific policies | Accept, query each policy with the cedent |
| Small premium difference, explained | Accept and record the explanation |
Set these thresholds with actuarial and finance users. They depend on how each team uses the data.
How Do You Validate a Seriatim File, Step by Step?
Validate a seriatim file with a repeatable routine that runs the same way every period. Six steps cover the full cycle.
- Receive with controls. Ask for record counts, total amount at risk and total premium alongside every file.
- Map to one record. Convert each cedent layout into one internal policy record.
- Run the five layers. Apply structural, field, treaty, period and financial checks in order.
- Gate the file. Accept, accept with exceptions, or reject, using the agreed severity rules.
- Query once. Send the cedent one consolidated exception list per file.
- Track recurrence. Log exceptions by cedent and type, and raise repeat issues at treaty reviews.
Step six turns validation into leverage. Evidence of recurring breaks supports a firmer data clause at renewal.
What Does a Validation Run Look Like?
A validation run should end with a short, numbered result, not a feeling. Here is an illustrative summary for one cedent file of 52,000 records.
| Check | Records flagged |
|---|---|
| Duplicate policy keys | 12 |
| Issue age inconsistent with date of birth | 48 |
| Ceded amount not equal to share of face less retention | 31 |
| Policy missing with no termination record | 27 |
| Premium total vs cedent bill | Difference under review |
The file is accepted with 118 exceptions. Each one has an owner and a due date.
Why Can't Audits Replace File Validation?
Audits cannot replace file validation because they sample processes, not every record. The SOA commentary notes audits generally find systematic errors rather than errors on individual policies.
Self-administration also reduced the clerical oversight once present. Every-file checks restore that oversight at scale.
Who Should Own Seriatim Data Quality?
Life reinsurance operations should own seriatim data quality, with actuarial and finance as named users. Operations runs the checks and talks to cedents.
Actuaries and finance set the rules that matter for reserves, experience and accounts. Without that split, every team builds its own private fixes.
Where Does Automation Help?
Automation helps by running the same calculations and comparisons on every record, every period. It does not decide why a difference exists or how it is settled.
Bordereaux calculation and reconciliation calculates premium and claim allocation and participation shares. It then reconciles bordereaux, master data, premium, claims and settlement, and identifies variances by reinsurer.
The platform identifies the difference, and operations and finance teams determine the cause. For the cross-cedent view, see manual bordereaux reconciliation across cedents.
Data quality is also a portfolio issue, not just an operations one. Our piece on why bordereaux quality is a portfolio problem makes that case.
Which Metrics Show Data Quality Is Improving?
Track metrics that show fewer breaks per file and faster resolution. Compare cedents, because the worst files usually come from a few sources.
| Metric | What it tells you |
|---|---|
| Files rejected on structure | Basic extract quality |
| Exceptions per 10,000 records | Record-level quality |
| Days from file receipt to booking | Process speed |
| Exceptions open past target | Cedent responsiveness |
| Repeat exceptions by type | Whether fixes stick |
What Should Chief Actuaries Do Next?
Chief actuaries should agree what "good enough" means for their own uses of the data. Operations can then enforce it consistently.
- Define which fields are mandatory for reserves and experience studies.
- Agree severity thresholds for rejecting or accepting files.
- Ask cedents for control totals with every seriatim file.
- Review exception trends by cedent at least quarterly.
Key Terms
- Seriatim: Policy by policy, one record for each reinsured policy or cession.
- Self-administered reinsurance: The cedent prepares billings and listings and sends them to the reinsurer.
- Control total: A summary figure sent with a file to prove it arrived complete.
- Retention: The amount of each life the cedent keeps for its own account.
- Exception list: Records accepted with a known issue, each tracked to resolution.
- Net amount at risk: Typically the death benefit less the policy reserve, the base for YRT reinsurance premium.
Sources
- Society of Actuaries: Commentary on Life Reinsurance Treaties (1994)
- Society of Actuaries: Reinsurance 101, 2019 Annual Meeting Session 026
- Society of Actuaries: Life Reinsurance Treaty Construction (March 2013)
- Insurnest: Bordereaux Calculation & Reconciliation
Frequently Asked Questions
What is seriatim data for life reinsurance?
Seriatim data for life reinsurance is a policy-by-policy file listing every reinsured life or cession, rather than summary totals. Each record carries details such as insured identity, issue age, class, face amount, retention, ceded amount and premium, so the reinsurer can check and analyse each policy.
Why do life reinsurers need seriatim data instead of summary reports?
Life reinsurers need seriatim data because summary reports hide individual errors. With policy-level records, a reinsurer can recalculate premiums, test retention and limits, match claims to in-force cessions, and build its own mortality experience studies instead of relying on cedent totals.
What checks should be run on a seriatim reinsurance file?
A seriatim reinsurance file should pass structural checks, field validity checks, treaty consistency checks, period-to-period checks and financial reconciliation. Together these confirm the file is complete, each record is plausible, each cession matches treaty terms, and totals agree with the cedent's billing.
What is the difference between seriatim and aggregate reinsurance reporting?
Seriatim reinsurance reporting lists every policy or cession individually. Aggregate reporting gives totals such as premium, amount at risk and policy counts by group. Aggregate figures are easier to produce but cannot show which individual policies are wrong.
Should a reinsurer reject a seriatim file with errors?
A reinsurer should not reject every seriatim file with errors. Structural failures, such as missing rows or broken control totals, justify rejection. Record-level issues are usually better accepted with an exception list, then corrected with the cedent in the next cycle.
Can audits replace seriatim data validation?
Audits cannot replace seriatim data validation. Periodic administrative audits tend to find systematic process errors, while errors on individual policies need checks on every record in every file. Audits remain useful for testing the controls themselves.
What does a cedent need to provide for seriatim validation?
For seriatim validation, a cedent needs to provide a stable policy and insured identifier, all fields required by the treaty, a transaction type for each change, and control totals for counts, amounts at risk and premiums. An agreed file layout removes most mapping errors.
Which team should own seriatim data quality at a reinsurer?
Seriatim data quality at a reinsurer is best owned by life reinsurance operations, with actuarial and finance as named users. Operations runs the checks and talks to cedents, while actuaries and finance agree the rules that matter for reserves, experience and accounts.
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 →
