ToolDoxTemplates

Insurance template

Claims Bordereaux Template

A claims bordereaux CSV template for claim references, policy references, loss dates, status, paid, reserve, incurred, currency, and core claim fields.

Download CSV templateUse in workflowAll templates

Who it is for

Delegated authority teams, coverholders, brokers, MGAs, claims analysts, and bordereaux operations teams.

Best use cases

  • Claims bordereaux collection
  • Delegated authority reporting
  • Loss-run preparation
  • Claims dashboard inputs
  • Data validation

Related workflow

Used in: Claims and Loss Run Review Workflow

Use this template to collect claims data before reviewing frequency, severity, reserves, and renewal talking points.

Feeds into tools

Claims Analytics Dashboard
Turn completed claims rows into frequency, severity, reserve, and loss driver views.
Loss Run Analyzer
Identify large losses, open reserves, and recurring causes.

Template fields and structure

The starter structure is designed to work in Excel, Google Sheets, Power BI, insurer portals, internal trackers, or client-facing documents.

claim_referencepolicy_referenceloss_dateclaim_statuspaidreserveincurredcurrency

Copyable CSV / spreadsheet structure

claim_reference,policy_reference,loss_date,claim_status,paid,reserve,incurred,currency
CLM-24017,GL-2026-001,2026-03-14,Open,18000,42000,60000,GBP

Example filled row

Use the example as a quality benchmark for how specific each row should be before the file is used in a workflow or tool.

claim_referencepolicy_referenceloss_dateclaim_statuspaidreserveincurredcurrency
CLM-24017GL-2026-0012026-03-14Open180004200060000GBP

How to use it

  1. Add one row per claim or claim transaction depending on your reporting basis.
  2. Keep paid, reserve, and incurred definitions consistent.
  3. Check that loss dates, claim statuses, and references are populated.
  4. Validate the completed file before sending it to market or a carrier.

What a completed version should prove

OKPaid, reserve, incurred, status, and loss dates are complete and consistently defined.
OKOpen claims, large losses, and unusual reserve movements can be identified quickly.
OKThe file can feed validation, loss run analysis, and claims dashboard views without manual cleanup.

Common mistakes to avoid

!Mixing transaction-level and claim-level rows without saying which basis is used.
!Leaving incurred blank or using paid as a substitute for total expected cost.
!Combining currencies or claim statuses without normalising them first.

Use this with

Related guides

Frequently asked questions

Should incurred equal paid plus reserve?

Often yes, but some organisations handle fees, recoveries, and expense fields separately. Define the basis before comparing totals.

Can this be used as a loss run?

It can be a starter claims extract, but a full loss run may need additional fields such as claimant, cause, location, and claim narrative.