Personal Accident Bordereaux for Reinsurers: Field Spec
On this page
- Key Takeaways
- What Are Personal Accident Bordereaux for Reinsurers?
- Which Fields Should a Personal Accident Bordereau Carry?
- What Does a Corrected Personal Accident Bordereau Record Look Like?
- How Do Reinsurers Find the Same Insured Life Twice on PA Bordereaux?
- How Is Site Accumulation Checked on a Personal Accident Bordereau?
- How Much Personal Data Does a PA Bordereau Really Need?
- How Does Insurnest Support Personal Accident Bordereaux Reconciliation?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
Three group schemes covered staff at the same industrial park. Each bordereau looked fine on its own.
Added together, one site carried more death benefit than the cedent's personal accident cat cover could pay.
Personal accident bordereaux for reinsurers list insured lives, benefits and sums insured so the reinsurer can price, share and accumulate risk.
Unlike property, the exposure is people: the same life can sit in several schemes, and one event can hit a whole site.
This guide gives you a field spec with tests, benefit coding rules, a before-and-after record and a worked site accumulation check.
Key Takeaways
- One benefit, one sum insured. Death, disablement and medical limits need separate fields.
- Code occupations. Free-text job titles cannot be rated or accumulated.
- Match lives across schemes. The same person can appear on group and individual cover.
- Accumulate by site. A shared workplace is the PA equivalent of a postcode.
What Are Personal Accident Bordereaux for Reinsurers?
Personal accident bordereaux for reinsurers are periodic cedent files listing each insured life, benefit and premium ceded under a PA treaty.
The wider accumulation strategy is set out in personal accident reinsurance catastrophe accumulation.
Which Fields Should a Personal Accident Bordereau Carry?
A personal accident bordereau should carry the fields below, each with a format, a valid range and a test.
| Field | Format | Valid values | Typical error | Test |
|---|---|---|---|---|
| Insured life ID | Text | Unique per person, pseudonymised | Name used as ID | Blank or duplicate in scheme |
| Date of birth | YYYY-MM-DD | Age within policy limits | Text date, 1900-01-01 default | Age at inception outside 16–75 |
| Occupation class | Code | Cedent's agreed scale | Job title as free text | Value not in code list |
| Scheme or policy ref | Text | Matches master list | Group and individual mixed | Lookup fails |
| Site ID | Text | Employer site or work location | Head office for all staff | One site holds all lives |
| Death sum insured | Number, full units | Above 0, within treaty maximum | In thousands | Below 1,000 or above maximum |
| PTD sum insured | Number | 0 to death benefit or scale | Copied from death | Matches death on every row |
| TTD weekly benefit | Number | Weekly amount | Monthly amount | Above 2% of death benefit |
| TTD maximum weeks | Integer | Per policy, e.g. 104 | Blank | Blank where TTD above 0 |
| Medical expenses limit | Number | Per policy | Merged into death | Blank where cover sold |
| Inception and expiry | YYYY-MM-DD | Expiry after inception | Swapped | Expiry before inception |
| Premium and currency | Number, ISO code | Above 0 unless nil endorsement | Mixed currencies | Blank currency |
The age band and the 2% weekly ratio are illustrative tolerances. Set them from the cedent's own product rules.
How should personal accident benefit types be coded on a bordereau?
Personal accident benefit types should be coded on a bordereau as separate fields, so each benefit's exposure is visible.
- Death: lump sum on accidental death.
- PTD: permanent total disablement, often the same as or a scale of the death sum.
- TTD: temporary total disablement, a weekly amount for a maximum number of weeks.
- Medical: a reimbursement limit per accident.
TTD exposure is weekly benefit times maximum weeks. A 500 weekly benefit over 104 weeks is 52,000 per life.
Why does occupation class need a fixed scale on PA bordereaux?
Occupation class needs a fixed scale on PA bordereaux because "driver" or "engineer" means nothing to a rating table.
Ask the cedent for its class definitions once, then reject any value outside that list.
What Does a Corrected Personal Accident Bordereau Record Look Like?
A corrected personal accident bordereau record, illustrated below, replaces text, merged and scaled values with coded fields.
BEFORE (as received)
Name: J. Patel | DOB: 1/2/85 | Job: Forklift driver
Benefits: D/PTD 100 | TTD 2,000 pm | Site: Head Office
Premium: 145 | Currency: (blank)
AFTER (validated)
Life ID: GPA-0193-0417 | DOB: 1985-02-01 (confirmed DD/MM)
Occupation class: 3 (cedent scale)
Death SI: 100,000 | PTD SI: 100,000
TTD: 462 weekly x 104 weeks | Medical limit: 5,000
Site ID: PARK-07 | Premium: 145 | Currency: GBP
Three fixes changed exposure: sums in thousands, monthly TTD converted to weekly, and the real work site.
The TTD conversion is 2,000 x 12 / 52 = 462 weekly. The medical limit came from the scheme schedule.
How Do Reinsurers Find the Same Insured Life Twice on PA Bordereaux?
Reinsurers find the same insured life twice on PA bordereaux by building one match key and testing it across every scheme.
- Best key: a national or staff ID, where the cedent can share it lawfully.
- Fallback key: upper-case surname, first initial and ISO date of birth.
- Test: count each key across all schemes; any count above 1 is a same-life candidate.
Same-life rows are not errors. Both policies may pay, so total the benefits per life before testing per-life limits.
The accidental death claims review for reinsurers shows why this matters at claim time.
How Is Site Accumulation Checked on a Personal Accident Bordereau?
Site accumulation on a personal accident bordereau is checked by summing benefits for all lives linked to one site, across every scheme.
The Munich Re glossary calls the reinsurer's version cumulative liability: several policies, one common event.
Illustrative site PARK-07, with the cedent's PA cat excess of loss at 10m excess of 5m.
| Source | Lives | Death sum each | Death total |
|---|---|---|---|
| Group scheme 1 | 120 | 100,000 | 12,000,000 |
| Group scheme 2 (contractors) | 45 | 50,000 | 2,250,000 |
| Individual PA policies | 6 | 250,000 | 1,500,000 |
| Site total | 171 | – | 15,750,000 |
The cat cover tops out at 15m, so 750,000 of a total-loss scenario at this site falls back on the cedent.
That only shows once Site ID is a real work location. With head office on every row, PARK-07 does not exist.
What should a reinsurer do when a PA site exceeds the cat cover?
A reinsurer should act when a PA site exceeds the cat cover by telling the treaty underwriter before the next renewal, not after an event.
- Confirm: ask the cedent to verify headcount and benefits for the site.
- Report: list the top ten sites by death total each quarter.
- Decide: the underwriter weighs a site limit, an event limit or more cat cover.
How Much Personal Data Does a PA Bordereau Really Need?
A PA bordereau needs only the personal data required to price, match lives and settle claims.
The ICO guide to the data protection principles quotes Article 5(1)(c): data "adequate, relevant and limited to what is necessary".
Use a pseudonymised life ID and date of birth; drop home addresses unless the treaty needs them. See personal data in bordereaux.
How Does Insurnest Support Personal Accident Bordereaux Reconciliation?
Reinsurance Bordereaux Reconciliation does not validate PA fields, match insured lives or run accumulation checks.
It calculates each reinsurer's premium share and claim liability from the configured participation on the treaty.
It compares those calculated values with bordereaux, claim and settlement records and shows the positions that need review.
Variances are surfaced; your team investigates the cause.
Key Terms
- PTD: Permanent total disablement, a lump sum when an accident leaves the insured unable to work permanently.
- TTD: Temporary total disablement, a weekly benefit paid for a limited number of weeks.
- Cumulative liability: Exposure under several policies that a single event can trigger together.
Sources
- Munich Re: Reinsurance Glossary
- ICO: A guide to the data protection principles
- Insurnest: Reinsurance Bordereaux Reconciliation
Frequently Asked Questions
What are personal accident bordereaux for reinsurers?
Personal accident bordereaux for reinsurers are periodic cedent files listing insured lives, benefits, sums insured and premiums ceded under a personal accident treaty.
Which fields should a personal accident bordereau carry?
A personal accident bordereau should carry an insured life ID, date of birth, occupation class, scheme and site, each benefit with its own sum insured, dates, premium and currency.
How should personal accident benefit types be coded on a bordereau?
Personal accident benefit types should be coded on a bordereau as separate rows or columns for death, permanent total disablement, temporary total disablement and medical expenses.
Why does occupation class need a fixed scale on PA bordereaux?
Occupation class needs a fixed scale on PA bordereaux because free-text job titles cannot be rated, compared or accumulated. Map every title to the cedent's agreed class codes.
What does a corrected personal accident bordereau record look like?
A corrected personal accident bordereau record has an ISO date of birth, a coded occupation class, one sum insured per benefit in full units, and a site identifier.
How do reinsurers find the same insured life twice on PA bordereaux?
Reinsurers find the same insured life twice on PA bordereaux by matching a normalised key of national ID or name plus date of birth across schemes and policies.
How is site accumulation checked on a personal accident bordereau?
Site accumulation on a personal accident bordereau is checked by summing death and disablement sums insured for every life linked to one site, then comparing the total with cat cover.
How much personal data does a PA bordereau really need?
A PA bordereau needs only the personal data required for pricing, matching and claims. UK GDPR data minimisation requires data that is adequate, relevant and limited to what is necessary.

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 →