BDX Management — premium, claims & risk bordereaux
Automatic bordereaux generation toward delegating insurers, Lloyd's managing agents and reinsurers.
What is BDX management and why is a dedicated module needed?
BDX management is the module that automates bordereaux generation and delivery — the periodic statements a coverholder, MGA or cedent must send to the delegating insurer, Lloyd's managing agent or reinsurer. NewPicass 14.Net generates three BDX types (premium, claims, risk) in the required formats (ACORD AL3, Lloyd's templates, custom CSV/XML), auto-reconciles with bank statements, tracks retroactive corrections with dedicated audit trail, and maintains the UMR/Risk Code mapping required by the Lloyd's market. On an average Italian coverholder it reduces by −80% the time to prepare the monthly BDX vs a manually maintained Excel spreadsheet.
Who needs to prepare bordereaux periodically
What the BDX module does
- Premium BDX, claims BDX, risk BDX separated or consolidated
- Formats: CSV, XML, Excel, ACORD AL3, Lloyd's Risk Code mapping
- Managing-agent templates configurable without development
- Multi-binder: one coverholder to N managing agents
- Automatic schedule (weekly, bi-weekly, monthly)
- Retroactive generation for historical reconstructions
- UMR (Unique Market Reference) mapping and validation
- Lloyd's Risk Code per row
- Adjustment rows for post-issuance modifications
- Complete audit trail across the reporting chain
- Internal sign-off before send to carrier
- Pass-through compliance for the annual Lloyd's coverholder audit
From reference period to delivered BDX
Binding-authority setup
Per binder: managing agent, template format, frequency, UMR & Risk Code mapping, recipient master data. One-time setup during coverholder onboarding.
Automatic row accumulation
Every policy issued or modified under the binder automatically enters the current period's BDX "staging", labelled with managing agent, type (new/adjustment) and Risk Code.
Pre-generation QC
On the scheduled date: formal validation (mandatory fields, UMR format, premium-collection sum check), anomaly highlighting and proposed corrections.
Operator sign-off
Preview of the final BDX + key-metric dashboard (policy count, total premium, total commissions). Operator approves or requests manual review.
Automatic delivery
Sent to managing agent via encrypted email, SFTP, or API (depending on carrier). Receipt tracking and acceptance confirmation.
Accounting reconciliation
When the commission payout arrives from the carrier, automatic matching with the generated BDX. Alerts on misalignments for investigation.
Technical stack
Real impact on a medium-sized coverholder
Frequently asked questions about BDX management
What is a premium bordereau (premium BDX)?
A premium bordereau is the periodic statement a coverholder or MGA sends to the delegating insurer listing, line by line, the policies issued under binding authority during the reference period. It contains, for each policy: number, principal, effective/expiry dates, gross premium, commissions, taxes, and risk share. For Lloyd's coverholders the format and frequency are set by the managing agent.
Which BDX formats does NewPicass 14.Net generate?
The platform generates BDX in CSV, XML, managing-agent-specific Excel templates, ACORD AL3, and Lloyd's Risk Code mapping. For each binding authority the required format is configured during onboarding. Custom (carrier-specific) templates are supported without client-side development.
How often should bordereaux be delivered?
Frequency is set contractually in the binding authority. Market standard is monthly, but some managing agents require weekly for high-volume lines or bi-weekly for specialty lines. NewPicass 14.Net configures the cadence per binder and generates automatically on the scheduled date, with operator notification.
How are corrections and retroactive BDX handled?
When an already-reported policy is modified (endorsement, cancellation, master-data correction), the system automatically marks the BDX row as "adjustment" and includes it in the next BDX with reference to the original number and period. Full audit trail across the reporting chain.
What is UMR (Unique Market Reference) and how is it managed?
UMR is the unique code assigned by the Lloyd's market to each contract/slip. NewPicass 14.Net maps the UMR to the binding authority and automatically includes it in every BDX as well as in policy certificates. The UMR structure (broker code / year / unique sequence) is validated on input.
Can I issue separate BDX for different managing agents?
Yes. The platform is natively multi-binder: every policy is labelled with its own binding authority and managing agent. BDX are generated separately for each binder: a coverholder working with 5 managing agents gets 5 distinct monthly premium BDX, each in the respective carrier's format.
Continue exploring the platform
Want to see BDX Management — premium, claims & risk bordereaux in action on your real flows?
45 minutes with one of our engineers, no sales script. You show us your current process and we show you concretely how this module would solve the critical points.