Coverholder & MGA — delegated authority management
Multi-insurer issuance under binding authority, automatic BDX generation, audit trail for Lloyd's coverholder audit and IVASS.
The 5 headaches of a coverholder operating with N insurers
Monthly BDX in Excel
5 days of copy-paste between insurer statements and internal sheets. Manual reconciliation with commission payouts. Frequent errors on adjustment rows.
Dual data entry
Policy issued in the delegating insurer's system + re-typed into internal Excel for controlling and BDX. Time lost + transcription errors.
Lloyd's audit = panic
The annual auditor asks for traceability of BDX delivered in the last 36 months, logs of activated/revoked delegations, evidence of anti-fraud controls. Without platform: long manual reconstruction.
Disorganised sub-broker network
Sub-brokers sending policies via email/WhatsApp, duplicated customer master data, manually-calculated commissions, payout delays.
Insurer asks for data you don't have
The insurer requests consolidated exposure per customer, geographic breakdown, loss ratio per line. The data is spread across 4 different Excels. Reconstruction = 2 days.
Same work, done differently
| Activity | Status quo (Excel + insurers' systems) | With NewPicass 14.Net |
|---|---|---|
| Monthly BDX | 5 days Excel + manual check | Auto-generated on schedule + 30-min sign-off |
| Sync with insurer | Re-typing + periodic import/export | Real-time bidirectional < 3s |
| Annual Lloyd's audit | Weeks of reconstruction | Audit package generated in 1 hour |
| Sub-broker management | Email + commission Excel | Dedicated portal + automatic multi-level commissions |
| On-demand insurer reporting | 2 days with Excel consolidation | Pre-configured dashboards, real-time PDF/Excel export |
| Atlas / IVASS compliance | Paper documentation + hoping for benign auditor | Native audit trail + embedded controls |
How the platform fits your role
Regulations a coverholder must address
NewPicass 14.Net is designed on the requirements IVASS, Lloyd's and DORA expect from a coverholder. Below the main regulations: the platform natively covers the IT requirements, leaving only corporate-policy aspects to the customer.
What changes, in numbers, on a mid-size Italian coverholder
Frequently asked questions from coverholders
What does a coverholder do exactly, and why is dedicated software needed?
A coverholder is a company authorised by an insurer (or a Lloyd's syndicate) to issue policies in their name and on their behalf, within predefined limits called binding authority. Dedicated software is needed because the coverholder must simultaneously operate on delegating insurers' systems and maintain their own internal portfolio, periodically report via BDX, manage multi-level commissions, sustain annual Lloyd's audits. Without a vertical platform: dual data entry + monthly Excel + audit-failure risk.
Can multiple delegating insurers be managed at the same time?
Yes — this is the main use case of NewPicass 14.Net as a coverholder platform. Each binding-authority agreement is configured separately: covered line, sum-insured limits, exclusions, BDX format required by the carrier, reporting frequency, commissions. The same coverholder can operate with 5+ insurers and generate 5 different monthly BDX, in respective ACORD/Lloyd's/custom formats, without manual intervention.
How does sync with the delegating insurer work?
Near-real-time bidirectional sync (< 3 seconds cross-tenant). Every policy issued by the coverholder is propagated to the delegating insurer's system; every modification made by the insurer (e.g. exposure variation, loss-ratio alert) flows back to the coverholder. At-least-once pattern with message idempotency key: no policy lost, no duplicates on retry.
I'm subject to annual Lloyd's coverholder audit — is the platform ready?
Yes. Immutable audit trail with 10-year retention covers Atlas traceability requirements. Automatic audit-package generation: delivered BDX extract, issuance logs, claims logs, active delegations logs, anti-fraud checks (e.g. blockchain hashes). Typical Lloyd's audit preparation time drops from weeks to days. See also the dedicated page Lloyd's coverholder.
How long does NewPicass 14.Net onboarding take for a coverholder?
Typical mid-size coverholder starting from Excel: 60-90 days from kick-off to go-live. Of which: ~30 days technical setup (binding authority, BDX templates, customer master data migrated), ~30-60 days parallel run with customer sign-off before cutover. For coverholders already using dedicated software: even 30-45 days.
Which modules matter most for a coverholder?
Four core modules: (1) Surety bond back-office for the lifecycle; (2) BDX management for automatic reporting to delegating insurers; (3) Distribution network for the sub-broker network reporting to the coverholder; (4) eIDAS signing for end-customer contracting.
See NewPicass 14.Net as it would work for a coverholder
45 minutes with one of our engineers. We show you concretely how the platform fits the specific workflows of your role — not a generic product demo.