Reinsurance

Embedded Insurance Bordereaux for Reinsurers: Control Guide

On this page

Last reviewed: November 2026

The September file from the device-cover programme arrived as 2.4 million rows. Nobody on the bordereaux team could open it in Excel.

The cedent's covering email said the total "ties to the partners". Which partners, and how, it did not say.

Embedded insurance bordereaux for reinsurers are partner-sold policy and claim reports, often millions of tiny rows.

They must reconcile to the treaty without anyone reading each row, so a sampling plan and hybrid reporting do the work.

Get the reporting model and controls right, and ceded premium can be trusted at partner level, not just at programme total.

This guide gives you a reporting model comparison, a control total set, a sampling formula and a worked partner reconciliation.

Key Takeaways

  • Volume changes the method. You test totals and samples, not every row.
  • Hybrid usually wins. Partner summaries monthly, row-level files on request.
  • Sample with a formula. 299 clean rows give 95% confidence of under 1% error.
  • Reconcile per partner. Programme totals can net two errors into a small one.

What Makes Embedded Insurance Bordereaux Different for Reinsurers?

Embedded insurance bordereaux differ for reinsurers because cover is sold at checkout by retailers, platforms or lenders.

That produces millions of policies with premiums of a few pounds each, plus heavy cancellation and refund traffic.

Each distribution partner also runs its own sales system, so the cedent's bordereau is a merge of several feeds.

For warranty-style cover, see extended warranty bordereaux for reinsurers.

Why can't a spreadsheet hold an embedded insurance bordereau?

A spreadsheet can't hold a large embedded insurance bordereau because Excel's specifications cap a worksheet at 1,048,576 rows.

Opening a bigger CSV in Excel loads only the rows that fit. A warning appears once, but the sheet still looks complete.

Load files into a database or data tool, and keep Excel for the summaries.

Which Reporting Model Suits Embedded Insurance Bordereaux: Row-Level, Summary or Hybrid?

The reporting model that suits embedded insurance bordereaux depends on what the reinsurer must prove: premium totals, row accuracy, or both.

FactorRow-level bordereauAggregated summaryHybrid
What arrivesEvery policy and transactionTotals by partner, product, monthSummaries monthly, rows on request
Typical sizeMillions of rowsTens of rowsTens of rows, plus sample extracts
Reinsurer can testAny row, any fieldTotals onlyTotals, plus sampled rows
Claim linkagePolicy ID on claim rowsNot possibleOn sampled rows
Personal data heldMostLeastLimited to samples
Main riskUnprocessed backlogWrong totals go unseenPartner refuses extracts
Fits whenNew partner, large share, audit issueSmall, stable, clean partnerMost mature programmes

For field names, borrow from Lloyd's coverholder reporting standards, version 5.2, which span premium and claims data.

Row-level files carry the most personal data; see personal data in bordereaux.

What decision rule picks the reporting model for an embedded programme?

The reporting model for an embedded programme should be picked partner by partner, using maturity and share of ceded premium.

Set the thresholds in the treaty's reporting schedule. The figures below are illustrative.

If the partner…Then require
Has traded under 12 monthsRow-level monthly
Exceeds 25% of ceded premiumRow-level monthly
Failed a sample in the last 2 quartersRow-level until 2 clean quarters
Is stable, small and cleanSummary monthly, sample quarterly
Changes its sales systemRow-level for 3 months after go-live

What Control Totals Should Every Embedded Insurance Bordereau Carry?

Every embedded insurance bordereau should carry control totals per partner, product and month, so the file proves its own completeness.

Control totalFormulaTolerance (illustrative)
Row countCount of transaction rowsExact
New policiesCount where type = newExact
CancellationsCount where type = cancelExact
Gross written premiumSum of new premium0.1%
RefundsSum of cancellation premium0.1%
Net premiumGross minus refunds0.1%
Partner commissionSum of commission column0.1%
Ceded premiumNet premium × quota shareExact to rounding
Claims paidCount and amountExact

Recompute each total from the rows on load. A total that cannot be rebuilt from the rows means a missing or duplicated batch.

Agree the field layout once with each partner; bordereau template mapping covers how.

How Should Reinsurers Sample Millions of Embedded Insurance Rows?

Reinsurers should sample millions of embedded insurance rows with a zero-error attribute plan, sized by formula rather than habit.

SAMPLE SIZE, ZERO ERRORS ALLOWED
n = ln(1 - C) / ln(1 - p)
C = confidence wanted        p = tolerable error rate

C = 95%, p = 1.0%   ->  n = ln(0.05)/ln(0.99)   = 298.1 -> 299 rows
C = 95%, p = 0.5%   ->  n = ln(0.05)/ln(0.995)  = 597.7 -> 598 rows
C = 90%, p = 1.0%   ->  n = ln(0.10)/ln(0.99)   = 229.1 -> 230 rows

If all 299 rows pass, you can say with 95% confidence that the error rate is below 1%. Population size barely matters at this scale.

If one row fails, the conclusion fails. Do not quietly add rows; record the error and widen the test for that partner.

Split the sample across partners in proportion to ceded premium, with a floor of 30 rows each. Test each row for:

  1. Cover start and end dates inside the treaty period.
  2. Premium equal to the partner's rate card for that product.
  3. Cancellation refund matching the pro rata or stated refund rule.
  4. Claim dates inside the policy's cover dates.

For rows that change between months, run a reinsurance bordereaux period comparison.

How Does Partner-Level Reconciliation Work for Embedded Insurance Bordereaux?

Partner-level reconciliation for embedded insurance bordereaux compares each partner's bordereau net premium with that partner's own sales report.

This illustrative month uses a 40% quota share across three partners, in GBP.

PartnerRowsBordereau net premiumPartner sales reportVarianceCeded effect at 40%
A, electronics retailer1,240,0003,100,0003,100,00000
B, travel platform860,0002,050,0002,150,000-100,000-40,000
C, phone network310,000720,000690,000+30,000+12,000
Total2,410,0005,870,0005,940,000-70,000-28,000

At programme level, the gap looks like a modest 1.2%. Per partner, there are two separate faults.

Partner B's refunds were deducted twice: once as negative rows, once in a cancellation file.

Partner C's file included sales the partner books next month.

Netting them hides both, and next month's cut-off will flip C's figure. Set common bordereaux cut-off dates for all partners.

What should a partner reconciliation record keep?

A partner reconciliation record should keep, for each partner and month, the three sources compared and the cause of any variance.

PARTNER RECONCILIATION RECORD
Programme / treaty   : [name] / [treaty ref]
Partner / month      : [partner] / [MMM YYYY]
Bordereau net prem.  : [amount]   Rows: [count]
Partner sales report : [amount]   Report date: [date]
Cash received        : [amount]   Value date: [date]
Variance / %         : [amount] / [%]
Cause                : [double refund | cut-off | rate | missing batch]
Corrected in month   : [MMM YYYY]
Checked by / date    : [name] / [date]

How Does Insurnest Support Embedded Insurance Bordereaux Reconciliation?

Reinsurance Bordereaux Reconciliation works on the money side of this problem.

From the participation you configure, it calculates each reinsurer's premium share, claim liability and net position.

It then checks those figures against bordereaux, premium, claim and settlement records, and shows which positions match and which need review.

It does not open raw partner files, validate fields, draw samples or route rows to treaties. Your team still finds the cause of each variance.

Key Terms

  • Embedded insurance: Cover sold inside another purchase, such as a phone, trip or loan, at the point of sale.
  • Control total: A count or sum sent with a file so the receiver can prove nothing was lost or doubled.
  • Attribute sample: A sample where each item simply passes or fails a test.

Sources

Frequently Asked Questions

What makes embedded insurance bordereaux different for reinsurers?

Embedded insurance bordereaux differ because cover is sold at checkout by many partners, so files carry millions of low-premium rows with frequent cancellations and refunds.

Why can't a spreadsheet hold an embedded insurance bordereau?

A spreadsheet can't hold a large embedded insurance bordereau because an Excel worksheet stops at 1,048,576 rows, and busy programmes send more than that each month.

Which reporting model suits embedded insurance bordereaux: row-level, summary or hybrid?

For embedded insurance bordereaux, a hybrid model usually suits reinsurers best: monthly partner summaries with control totals, plus row-level files on request for sampling.

What decision rule picks the reporting model for an embedded programme?

The reporting model for an embedded programme should follow partner maturity and share of ceded premium: new or large partners report row-level, stable small ones by summary.

What control totals should every embedded insurance bordereau carry?

Every embedded insurance bordereau should carry, per partner and month, row count, new and cancelled policies, gross premium, refunds, net premium, commission, ceded premium and claims.

How should reinsurers sample millions of embedded insurance rows?

Reinsurers should sample embedded insurance rows with a zero-error attribute plan. At 95% confidence and a 1% tolerable error rate, 299 clean rows support the conclusion.

How does partner-level reconciliation work for embedded insurance bordereaux?

Partner-level reconciliation for embedded insurance bordereaux compares each partner's bordereau net premium with its own sales report and cash, because programme totals hide offsetting errors.

How does Insurnest support embedded insurance bordereaux reconciliation?

Insurnest supports embedded insurance bordereaux reconciliation by calculating reinsurer shares from configured participation and flagging variances. It does not validate file formats or sample rows.

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

Extended Warranty Bordereaux for Reinsurers: Retailer Cases

extended warranty bordereaux for reinsurers: four retailer cases on deferred earning, refunds, product mix and claim frequency, a summary table and a process.

Read more
Reinsurance

Reinsurance Bordereaux Period Comparison: Metrics & Example

reinsurance bordereaux period comparison: a metrics table with variance thresholds, a worked premium +40% vs policies +5% case and the checks to run first.

Read more
Reinsurance

Bordereau Template Mapping: Onboard New Cedent Formats Fast

Bordereau template mapping as a reusable specification: header, field map, code tables, control totals and change log, so new cedent formats onboard cleanly.

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.