Reinsurance

Treaty-Level Bordereaux Dashboard for Reinsurers: KPI Spec

On this page

Last reviewed: November 2026

The monthly pack said 94% of bordereaux were received. Nobody could say which treaties made up the missing 6%.

One of them was a casualty excess of loss treaty whose claims file had failed validation twice since August.

A treaty-level bordereaux dashboard for reinsurers shows, per treaty, which files were expected, received, validated and booked.

It also shows how late the missing files are and how often submissions fail.

It matters because a portfolio-wide percentage hides the treaty where the reserve or settlement risk actually sits.

This guide gives you seven metric definitions with formulas and tests, RAG rules, a six-treaty view and a before/after record.

Key Takeaways

  • Define before you chart. Each metric needs one formula and one test.
  • Freeze the as-of date. Re-running last month's view must give last month's numbers.
  • Count files, not rows. Rejection rate is about submissions.
  • Rate by the worst metric. One red metric makes the treaty red.

What Is a Treaty-Level Bordereaux Dashboard for Reinsurers?

A treaty-level bordereaux dashboard for reinsurers is a status view with one row per treaty and bordereau type.

The RAA glossary describes a bordereau as a report the ceding company provides periodically. The dashboard tracks that periodic promise.

Lloyd's delegated-authority procedure splits handling into submission, transformation, assignment and approval roles.

Treaty teams can mirror that: received, validated, booked.

Which Metrics Belong on a Treaty-Level Bordereaux Dashboard?

Metrics that belong on a treaty-level bordereaux dashboard are the seven below, defined once and tested every run.

MetricFormulaFormatValid valuesTypical errorTest
ExpectedCount of (treaty, type, period) due on or before the as-of dateInteger≥0Run-off treaties or wrong frequency left outTies to treaty register schedule
ReceivedDistinct (treaty, type, period) with a logged fileInteger≤ Expected plus unscheduledResubmissions counted as newDistinct keys = count
ValidatedReceived keys whose latest version passed checksInteger≤ ReceivedOld version's pass carried forwardValidated keys within Received
BookedValidated keys posted to the ledgerInteger≤ ValidatedPosting before validationBooked keys within Validated
Days overdueAs-of date minus due date, for missing keysInteger days≥0; blank if receivedTODAY() used, so history movesRecompute with stored as-of date
Rejection rateRejected submissions / submissions received in window% to 1 dp0 to 100%Rows counted, or Expected used as baseNumerator ≤ denominator
Receipt to bookingBooking date minus receipt dateInteger days≥0Back-dated bookings go negativeMinimum ≥0

Due date is the period end plus the reporting days in the treaty. Store it per key; see bordereaux cut-off dates.

How should days overdue be calculated for a missing bordereau?

Days overdue for a missing bordereau should be counted from the due date to a stored as-of date, never to today.

Due date     = Period end + Reporting days (from treaty)
Days overdue = IF(Received date is blank,
                  MAX(0, As-of date - Due date), blank)
Excel        = IF([@Received]="", MAX(0, AsOf-[@Due]), "")

Illustrative: August period, 30 reporting days, due 30 September 2026. As at 30 October 2026, it is 30 days overdue.

Late files that did arrive need a separate "days late at receipt" field, or they vanish from the history.

How is the bordereaux rejection rate defined per treaty?

The bordereaux rejection rate per treaty is rejected submissions divided by all submissions for that treaty in the window.

Rejection rate = Rejected submissions / All submissions received
Excel          = IFERROR(COUNTIFS(Treaty,[@Treaty],Status,"Rejected")
                 / COUNTIFS(Treaty,[@Treaty]), 0)

Every resubmission is a new submission in the denominator. How resubmitted files are logged is covered in bordereau resubmission handling.

What RAG Rules Should Flag a Treaty's Bordereaux Status?

RAG rules should flag a treaty's bordereaux status per metric, then rate the treaty by its worst metric. Bands are illustrative.

MetricGreenAmberRed
Received / Expected100%80% to 99%Below 80%
Maximum days overdue01 to 15Over 15
Validated / Received95% or more80% to 94%Below 80%
Booked / Validated100%90% to 99%Below 90%
Rejection rateUp to 10%10.1% to 25%Over 25%

Where Expected is zero, show "none due" in grey. A green 100% on zero files is a false comfort.

What Does a Six-Treaty Bordereaux View Look Like?

A six-treaty bordereaux view, illustrated below, covers files due from 1 July to 30 October 2026, as at Friday 30 October.

TreatyExpectedReceivedValidatedBookedMax days overdueRejection rateRAG and reason
Property QS (monthly P and C)888800.0% (0/8)Green
Motor QS (monthly P and C)8877011.1% (1/9)Amber: validation 87.5%
Engineering QS (quarterly P and C)222200.0% (0/2)Green
Marine cargo QS (monthly P only)4333300.0% (0/3)Red: August file missing
Casualty XoL (quarterly C)1100066.7% (2/3)Red: no valid version
Property cat XoL0000NoneNoneGrey: none due

The portfolio received 22 of 23 files, 95.7%. Two treaties are still red.

A queue of files waiting behind that view is a reinsurance bordereaux backlog, which needs its own clearance plan.

What does one bordereau status record look like before and after the spec?

One bordereau status record, before the spec, is a free-text tracker row that cannot feed any metric.

BEFORE  Motor QS | Sep | got it 28/10 | ok?? | booked?

AFTER   treaty_id          : MQS-2026
        bordereau_type     : premium
        period             : 2026-09
        due_date           : 2026-10-30
        latest_version     : 2 (v1 rejected 2026-10-21)
        received_date      : 2026-10-28
        status             : validated 2026-10-29
        booked_date        : 2026-10-30
        submissions        : 2; rejected: 1
        days_overdue       : blank (received)

What Data Errors Make a Bordereaux Dashboard Misleading?

Data errors make a bordereaux dashboard misleading when the metric logic is right but the inputs are not.

  • Resubmissions counted twice. Received exceeds Expected and looks like over-delivery.
  • Today's date as as-of. Last month's pack changes every time it is opened.
  • Run-off treaties missing. Claims files for old years drop out of Expected.
  • Wrong reporting frequency. A quarterly treaty set up as monthly shows false misses.
  • Booked before validated. The ledger moves ahead of the checks.
  • Claims lag hidden. Claims files arrive later than premium; see claims bordereaux lag.

Does Insurnest Provide a Treaty-Level Bordereaux Dashboard?

Insurnest does not provide a treaty-level bordereaux dashboard; build the view above in your own reporting tool.

Reinsurance Bordereaux Reconciliation works at the checking step.

It calculates each reinsurer's premium share and claim liability from configured participation.

It then compares those values with bordereaux, master and settlement records.

Each reinsurer position is shown as either matched or awaiting review. Your team can use that outcome when it sets the "validated" status.

It does not track receipts, send alerts or validate file formats. Teams still investigate each difference.

Key Terms

  • As-of date: The fixed date a dashboard is calculated at, stored so results can be repeated.
  • Due date: Period end plus the reporting days a treaty allows.
  • Rejection rate: Rejected submissions as a share of all submissions in the window.

Sources

Frequently Asked Questions

What is a treaty-level bordereaux dashboard for reinsurers?

A treaty-level bordereaux dashboard for reinsurers is one row per treaty showing how many bordereaux were expected, received, validated and booked, how late the missing ones are, and how often files fail.

Which metrics belong on a treaty-level bordereaux dashboard?

Metrics that belong on a treaty-level bordereaux dashboard are expected, received, validated, booked, days overdue, rejection rate and receipt-to-booking days, each with a fixed formula and test.

How should days overdue be calculated for a missing bordereau?

Days overdue for a missing bordereau should be the fixed as-of date minus the due date, floored at zero, where due date is period end plus the treaty's reporting days.

How is the bordereaux rejection rate defined per treaty?

The bordereaux rejection rate per treaty is rejected submissions divided by all submissions received for that treaty in the window, counting files, not rows, and including resubmissions.

What RAG rules should flag a treaty's bordereaux status?

RAG rules for a treaty's bordereaux status set green, amber and red bands per metric, such as red above 15 days overdue, then rate the treaty by its worst metric.

What does a six-treaty bordereaux view look like?

A six-treaty bordereaux view, illustrated as at 30 October 2026, shows two green treaties, one amber, two red and one with no bordereaux due, each explained by its worst metric.

What data errors make a bordereaux dashboard misleading?

Data errors that make a bordereaux dashboard misleading include counting resubmissions as new files, using today's date, missing run-off treaties, booking before validation and dividing by expected files.

Does Insurnest provide a treaty-level bordereaux dashboard?

Insurnest does not provide a treaty-level bordereaux dashboard. Its Bordereaux Reconciliation product calculates reinsurer shares and shows which positions match or need review, which can inform your validated status.

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

Reinsurance Bordereaux Backlog: Triage, Capacity & Controls

reinsurance bordereaux backlog plan: a triage matrix by value, age and cedent, a worked capacity calculation for 180 files and the booking shortcuts to avoid.

Read more
Reinsurance

Bordereaux Cut-Off Dates: Stop Late Data Breaking Month-End

Bordereaux cut-off dates decide which data makes each month-end. Get a working-day close calendar, treaty tiering rules and a method for late bordereaux.

Read more
Reinsurance

Claims Bordereaux Lag: Building Earlier Reserve and Cash Forecasts

Claims bordereaux lag delays reserving and cash forecasting. Learn how reinsurers can build earlier reserve estimates and liquidity forecasts despite incomplete and late-arriving claims data.

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.