ToolDoxTemplates

Insurance template

Premium Bordereaux Template

A premium bordereaux CSV template for policy, insured, risk, transaction, premium, country, class, currency, inception, and expiry fields.

Download CSV templateUse in workflowAll templates

Who it is for

Delegated authority teams, coverholders, MGAs, brokers, binder managers, and insurance operations analysts.

Best use cases

  • Premium bordereaux reporting
  • Binder data collection
  • Policy transaction validation
  • Market submissions
  • Premium reconciliation

Related workflow

Used in: Underwriter Submission Readiness Workflow

Use this template to structure premium data before validation and submission readiness checks.

Feeds into tools

Bordereaux Validator
Validate dates, premium values, references, and required reporting fields.
Submission Readiness Score
Use the cleaned bordereaux as part of a market-ready pack.

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.

policy_referenceinsured_namecountryinception_dateexpiry_datetransaction_dategross_premiumcurrency

Copyable CSV / spreadsheet structure

policy_reference,insured_name,country,inception_date,expiry_date,transaction_date,gross_premium,currency
POL-2026-441,Harbour Retail Group,UK,2026-01-01,2026-12-31,2026-01-01,125000,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.

policy_referenceinsured_namecountryinception_dateexpiry_datetransaction_dategross_premiumcurrency
POL-2026-441Harbour Retail GroupUK2026-01-012026-12-312026-01-01125000GBP

How to use it

  1. Add one row per policy, certificate, or premium transaction.
  2. Keep dates and currency formats consistent.
  3. Use clear transaction types such as new business, renewal, endorsement, or cancellation.
  4. Validate required fields before submitting to a carrier, MGA, or Lloyds workflow.

What a completed version should prove

OKEach premium row has policy, insured, dates, transaction, premium, country, class, and currency context.
OKTotals can reconcile back to binder, MGA, broker, or carrier reporting expectations.
OKField definitions are clear enough for validation and downstream dashboard use.

Common mistakes to avoid

!Omitting transaction type or using inconsistent inception and transaction dates.
!Combining gross, net, tax, and commission figures without naming the basis.
!Changing field names without keeping a field mapping for reporting teams.

Use this with

Related guides

Frequently asked questions

What is a premium bordereaux?

It is a structured report of premium, policy, insured, risk, and transaction data, often used in delegated authority and binder reporting.

Can I change the column names?

Yes, but keep a field mapping so validators, carriers, and reporting teams know exactly what each column means.