Bordereau Template Mapping: Onboard New Cedent Formats Fast
On this page
- What Is Bordereau Template Mapping?
- What Does a Bordereau Mapping Specification Contain?
- How Do You Onboard a New Cedent Format With the Specification?
- How Do You Keep Mapping Specifications Current?
- Which Market Standards Reduce Mapping Work?
- Where Does Bordereaux Reconciliation Fit in Bordereau Template Mapping?
- What Should Operations Standardise Before the Next Cedent Goes Live?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
Every new cedent sends its bordereau in a new layout, with new column names, codes and units.
Operations teams rebuild the same spreadsheet logic again, and the first reconciliation still fails.
Bordereau template mapping links every cedent column and code to your own data dictionary through a written mapping specification.
With one reusable specification format, a new cedent becomes a configuration task instead of a spreadsheet rebuild.
What Is Bordereau Template Mapping?
Bordereau template mapping is the process of translating a cedent's bordereau layout into the reinsurer's standard fields.
The output is a mapping specification. It is the artefact this guide shows field by field.
Why does each new cedent format cost so much?
Each new cedent format costs so much because the meaning sits outside the columns. Units, code lists and date formats differ by cedent.
Without a specification, those rules live in formulas and in one analyst's memory. Our guide to bordereaux processing automation covers the wider workflow.
What Does a Bordereau Mapping Specification Contain?
A bordereau mapping specification contains five parts: a header block, a field mapping table, value translation tables, validation rules and a change log.
The examples below are illustrative for a premium bordereau from a hypothetical "Cedent A".
What goes in the header block?
The header block identifies exactly which file, treaty and version the specification covers.
| Header field | Purpose | Illustrative value |
|---|---|---|
| Specification ID | Unique reference for audit | MAP-CEDA-PREM |
| Cedent | Who sends the file | Cedent A |
| Treaty references | Which contracts the file covers | QS-2026-014 |
| Bordereau type | Premium or claims | Premium |
| File pattern and format | How to recognise the file | CedentA_Prem_YYYYMM.xlsx |
| Frequency | When it should arrive | Monthly, by working day 10 |
| Version and effective date | Which rules apply to which files | v1.2 from 1 Jan 2026 |
| Data dictionary version | Which target fields are used | DD v3.0 |
| Owner and approver | Who maintains and signs off | Ops analyst; Head of Reinsurance Ops |
What goes in the field mapping table?
The field mapping table links each target field to its source column, with the transformation and validation applied.
| Target field | Source column | Format | Transformation | Mandatory | Validation rule |
|---|---|---|---|---|---|
| Treaty reference | Contract No | Text | Trim, upper case | Yes | Exists in treaty master data |
| Policy number | Pol Ref | Text | None | Yes | Not blank |
| Transaction type | Trans Type | Code | Translate via table T1 | Yes | Value in allowed list |
| Inception date | Start Dt | Date | Read as day/month/year | Yes | Within treaty period |
| Expiry date | End Dt | Date | Read as day/month/year | Yes | After inception date |
| Currency | Ccy | Code | Translate to ISO 4217 | Yes | Valid ISO code |
| Gross premium | Gross Prem (000s) | Number | Multiply by 1,000 | Yes | Numeric, not blank |
| Class of business | LOB | Code | Translate via table T2 | Yes | Mapped value found |
| Country | Country | Code | Translate to ISO 3166 | No | Valid code if present |
| Ceded share | Not in file | Percentage | Taken from treaty master data | Yes | Matches signed share |
Two rows deserve attention. Gross premium arrives in thousands, and ceded share is never taken from the cedent's file.
What goes in the value translation tables?
The value translation tables convert each cedent's codes into your standard values. They hold most of the hidden meaning.
| Table | Cedent value | Standard value |
|---|---|---|
| T1 Transaction type | NB | New business |
| T1 Transaction type | END | Endorsement |
| T1 Transaction type | CAN | Cancellation |
| T2 Class of business | PROP-COM | Commercial property |
| T2 Class of business | PROP-RES | Residential property |
| Currency | US$ | USD |
Every unmapped value should stop the row, not default silently. Silent defaults are where misallocations start.
What goes in the validation and control totals section?
The validation and control totals section proves that nothing was lost or changed during mapping.
- Row count in the file equals rows loaded plus rows rejected.
- Total gross premium equals the cedent's stated total.
- Mapped premium agrees with the premium register for the period.
- Ceded premium agrees with the statement of account.
- No duplicate transactions on policy, transaction type and date.
- Rejected rows are returned with a reason code.
How Do You Onboard a New Cedent Format With the Specification?
You onboard a new cedent format by filling in the specification in a fixed sequence. The sequence matters more than the tool.
- Request a sample file with known totals. Ask for a recent period the cedent has already reconciled.
- Profile every column. Record data types, blanks, units and distinct code values.
- Complete the header and field mapping. Map to the data dictionary, not to another cedent's sheet.
- Build translation tables. Cover every distinct code found in the sample.
- Write validation rules. Include control totals from the cedent's own figures.
- Test, fix and sign off. Then set the version and effective date.
Treat this as part of cedent onboarding, not a task left until the first file arrives.
How do you test a new mapping before go-live?
You test a new mapping before go-live by running at least one full historical period through it and reconciling every control total.
Then deliberately test edge cases: a cancellation, a negative premium, a new currency and an unknown code. Each should behave as the specification says.
How Do You Keep Mapping Specifications Current?
You keep mapping specifications current with versioning and a change log. Cedents change their files without warning.
| Version | Date | Change | Trigger | Approved by |
|---|---|---|---|---|
| v1.0 | Jan 2026 | Initial specification | New treaty | Head of Reinsurance Ops |
| v1.1 | Apr 2026 | Added code PROP-AGR to T2 | Unmapped value rejected | Ops lead |
| v1.2 | Jul 2026 | Premium column now in whole currency | Cedent layout change | Head of Reinsurance Ops |
Each file should record which specification version processed it. That keeps reinsurance data lineage intact.
What should trigger a mapping change?
A mapping change should be triggered by evidence, not habit. Four triggers cover most cases.
- A new or renewed treaty with different terms or classes.
- A cedent layout, unit or code change.
- Rejected rows caused by unmapped values.
- A reconciliation break traced back to mapping.
Which Market Standards Reduce Mapping Work?
Market standards reduce mapping work by giving cedents and reinsurers a shared structure to start from.
Lloyd's coverholder reporting standards aim to establish a standardised core data set for risk, premium and claims reporting.
They come with premium and claims reporting templates. Where a cedent uses them, your specification maps one known layout.
The ACORD Ruschlikon initiative uses ACORD reinsurance standards for placing, technical accounting, claims and settlement.
Its stated aim includes replacing paper statements with structured data messages. Many cedents still send their own spreadsheets, so mapping remains necessary.
Where Does Bordereaux Reconciliation Fit in Bordereau Template Mapping?
Bordereaux reconciliation fits after bordereau template mapping. Mapping makes figures comparable, and reconciliation checks they are right.
Insurnest Bordereaux Calculation and Reconciliation works with bordereaux statements in .xlsx, whose layouts vary.
It also uses master data on participation shares, premium and claim registers and settlement advice.
It calculates premium and claim allocation per reinsurer, reconciles them against those records and shows mismatches in one variance view.
Reinsurer-level status, such as three of four positions matched, shows where to look first.
Our guide to manual bordereaux reconciliation across cedents explains why this matters.
What does the operations team still own?
The operations team still owns the mapping specification and the cause of each variance. The product detects mismatches but does not explain them.
Results depend on the quality of inputs. A clean, versioned specification is what keeps those inputs trustworthy.
What Should Operations Standardise Before the Next Cedent Goes Live?
Operations should standardise five things before the next cedent goes live, so onboarding becomes repeatable.
- One specification template with the five parts above.
- One data dictionary that every specification maps into.
- Shared translation tables for currency and country codes.
- Mandatory control totals for every file.
- A change log and version stamp on every processed file.
Key Terms
- Mapping specification: The written document linking a cedent's bordereau layout to your data dictionary.
- Data dictionary: The fixed list of internal fields every bordereau is mapped into.
- Translation table: A list converting cedent codes into standard values.
- Control total: A figure, such as total premium, used to prove that no data was lost.
- Change log: A dated record of every change to a specification and why it was made.
Sources
- Lloyd's: Reporting standards (Coverholder Reporting Standards)
- ACORD: Ruschlikon
- Insurnest: Bordereaux Calculation and Reconciliation
Frequently Asked Questions
What is bordereau template mapping?
Bordereau template mapping is the process of linking each column and code in a cedent's bordereau to a field in the reinsurer's own data dictionary. A written mapping specification records the source columns, target fields, transformations, code translations and validation rules, so any cedent layout lands in one consistent structure.
What should a bordereau mapping specification include?
A bordereau mapping specification should include a header block identifying the cedent, treaty, bordereau type and version, a field mapping table, value translation tables for codes, validation rules with control totals, and a change log. Together these let anyone reproduce how a figure was derived.
How do you map a new cedent bordereau?
To map a new cedent bordereau, request a sample file with known totals, profile every column, match columns to the data dictionary, build code translation tables and write validation rules. Then run the sample through the mapping, reconcile the control totals, fix gaps and obtain sign-off before live use.
Why do new cedent bordereau formats take so long to onboard?
New cedent bordereau formats take long to onboard because each cedent uses its own columns, codes, units and date formats. Without a standard specification, teams rebuild spreadsheet formulas for every cedent, and hidden assumptions such as amounts in thousands or local class codes are only discovered when totals fail.
Who should own bordereau mapping specifications?
Bordereau mapping specifications should be owned by reinsurance operations, with a named analyst responsible for each cedent. Reinsurance accounting approves control totals, data or IT teams maintain the technical mapping, and the head of reinsurance operations signs off new specifications and material changes before they go live.
How often should bordereau mappings be reviewed?
Bordereau mappings should be reviewed at every treaty renewal, whenever a cedent changes its file layout or codes, and after any reconciliation break traced to mapping. A short quarterly check of unmapped values and rejected rows also shows early whether a cedent format has drifted.
Do market standards remove the need for bordereau mapping?
Market standards reduce bordereau mapping work but rarely remove it. Lloyd's coverholder reporting templates and ACORD reinsurance standards give common structures, yet many cedents still send their own layouts, so a reinsurer needs a mapping specification that brings every format into its own data dictionary.
How does mapping quality affect bordereaux reconciliation?
Mapping quality affects bordereaux reconciliation directly, because reconciliation compares mapped bordereau figures with premium, claim and settlement records. A wrong unit, currency or code mapping creates false variances or hides real ones, so clean mapping is the first control in a reliable reconciliation process.

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 →