Risk Bordereaux
Every monthly bordereau checked row by row against the binder, with breaches flagged before the month closes.
Why it matters
Each coverholder sends its bordereau in its own layout; analysts re-key columns and check a sample, so risks bound outside authority surface months later at audit.
How the solution handles it
Five agents read each bordereau in any layout, map it to the Lloyd’s coverholder reporting standard, test every row against the binder’s limits, classes, territories and dates, and reconcile premium, tax and commission to cash. Each breach becomes a cited query; the delegated authority manager decides and signs off the month.
How a bordereau moves
Five specialist agents read, map, check and reconcile every bordereau; a delegated authority manager signs off each month.
What it reads, and what it hands back.
What goes in
- Monthly risk bordereau
- Premium bordereau
- Binding authority agreement
- Cash and settlement statements
What comes out
- Checked, standardised bordereau
- Authority breach log
- Premium, tax and commission reconciliation
- Signed month-end pack
Who uses it
The difference, in numbers.
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
Source: Lloyd’s Coverholder Reporting Standards v5.2 · “Target” = design goal, measured in the live solution · “Estimated” = our estimate · agents = the live solution’s configuration
5 specialist agents. One person decides.
More in this division.
Every TPA claims bordereau checked against authority and reserves, with leakage flagged each month.
Authority AuditCoverholder audits that test every bound risk against the binder, with a cited draft report in days.
Coverholder OnboardingNew MGAs and coverholders vetted against your standard in days, every answer tied to its evidence.
Build this
for your team.
We’ll show Risk Bordereaux running on your own documents.