From Lloyd's MRC to Italian certificate: the coverholder workflow in 6 steps

Operating as a Lloyd's coverholder means moving on two regulatory and linguistic planes simultaneously: in London the MRC (Market Reform Contract) speaks, in Italy IVASS speaks. The coverholder's PAS is the bridge between the two worlds. This article describes the operational workflow in 6 steps, from receiving the London MRC to generating quarterly bordereaux, with the points where errors and inefficiencies typically concentrate.

Context: coverholder, binder, MRC

A coverholder is an intermediary approved by Lloyd's (via Atlas process) to underwrite risks and/or issue policy documents on behalf of Lloyd's syndicates under a binding authority (binder). The binder is the contract between the syndicate (or a group of syndicates) and the coverholder: defines delegated risk classes, underwriting limits (per policy, per aggregate exposure), geographic territory, premiums and commissions, bordereau cadence.

The MRC (Market Reform Contract) is the standardised contractual document defining the binder: it contains Risk Details, Information, Subscription Agreement, Fiscal & Regulatory section, Broker Remuneration. It is the "master contract" — every single policy issued by the coverholder is an instance inheriting terms from the MRC.

Step 1 — Reading and ingesting the London MRC

The annual binder arrives from the London broker (Aon, Marsh, Howden or equivalent) in structured MRC PDF format, sometimes accompanied by Excel templates for structured data. The PAS must extract:

• UMR (Unique Market Reference): numeric binder identifier valid at Lloyd's and aligned markets.
• Participating syndicates and shares: each syndicate has a participation percentage (e.g. 30% Syndicate 33, 25% Syndicate 1414, 20% Syndicate 4444, etc.). The sum must be 100%.
• Delegated risk classes: Lloyd's codes (e.g. PD for Property Damage, MO for Motor, FI for Financial Institutions) with possible sub-codings.
• Underwriting limits: per-policy limit, aggregate exposure limit, per-geographic-area sub-limits.
• Premiums and commissions: reference tariff, coverholder commission, ceding commission to the syndicate, broker fee.
• Period of cover: binder start date, end date (typically annual), grace period.
• Bordereau cadence: cadence of premium and claims BDX (monthly, quarterly).

The vertical PAS supports semi-automated extraction via parsing of known templates + manual back-office review. For year-on-year repeat binders, the delta from the previous year accelerates the ingest.

Step 2 — Mapping MRC → local data schema

The binder defines terms in Lloyd's language; the Italian PAS works with a local data schema (IVASS classes, Italian tax IDs, contracting-authority names, etc.). Mapping is not trivial.

Examples of mapping that the vertical PAS handles natively:

• Lloyd's classes → IVASS lines. A "PD - Property" policy on a Lloyd's binder becomes "ramo 8 - fire and natural elements" on the IVASS-compliant certificate. Classes are not always in 1:1 correspondence (an IVASS line may aggregate 2-3 Lloyd's classes).
• Currency and exchange rate. Binder limits are in GBP, local policies in EUR. The PAS handles conversion at the issuance-day rate (ECB), blocks when the portfolio approaches the GBP limit, accounting entries.
• Slip clauses → Italian text. MRC-specific clauses (e.g. LMA5018 War Exclusion, LMA5390 Pandemic Exclusion) must appear in certificates with consistent translation. The AI translation module helps generate bilingual versions but the prevailing legal text normally remains English.
• Aggregate limits. If the binder says "USD 50M aggregate exposure per Italian Central Seismic Zone", the PAS must track exposure on issued policies in real time, block new issuances exceeding threshold, alert the broker.

Step 3 — Issuing the IVASS-compliant certificate

The single-certificate issuance is the point where the coverholder differentiates between "traditional Italian insurer" and "bridge to Lloyd's". The certificate must be:

• IVASS-compliant: Italian language, mandatory structure (frontispiece, general conditions, particular conditions, IPID informational annex for non-motor non-life, etc.), Italian regulatory references (IVASS Reg. 40/2018 for distribution, correct IVASS line).
• Binder-traceable: the certificate carries the UMR, any syndicate leader reference, a note that the policy is issued under Lloyd's delegated authority.
• MRC-consistent: terms, exclusions, sub-limits must align with the binder. Discrepancies surface at claim time and create disputes.
• Signed and time-stamped: FEQ + TSA timestamp for certain date.

Step 4 — ACORD premium bordereau to the syndicate

At the cadence defined in the binder, the coverholder produces the premium BDX: statement of policies issued in the period with structured data for syndicate consumption. The BDX management module automates:

• Data extraction: all policies with issuance date in the period, grouped by binder and syndicate.
• Validation: mandatory fields populated, correct UMR, MRC cross-references, balanced totals.
• Generation: in standard format (structured CSV, Excel template, or ACORD XML depending on syndicate preference).
• Exception report: anomalous entries requiring manual review before sending (e.g. premium out of tariff range, non-delegated class, policy issued out of territory).
• Transmission: upload to PPL, send to syndicate portals, FTP/SFTP per agreements.

BDX error is the error that really matters for the Lloyd's relationship: a bad BDX propagates into syndicate bookkeeping, complicates reconciliation, calls into question coverholder compliance. BDX quality is one of the main KPIs in periodic reviews with the leading syndicate.

Step 5 — Claims handling and claims BDX

The claims BDX is the twin of the premium BDX but for claims: statement of opened, reserved, paid claims in the period, with reference to the policy and originating binder.

Coverholder authority on claims varies by binder:

• Full claims authority: the coverholder handles the claim end-to-end (opening, reserve, payment) within defined amount limits. Common for retail lines (cargo, travel).
• Limited loss-adjustment authority: the coverholder opens and maintains the file but settlement decisions above threshold go to the syndicate or designated TPA. Common for specialty (marine hull, aviation).
• Notification only: the coverholder notifies claims but doesn't handle them. Rare in modern binders.

The PAS must reflect these authorities in the workflow: automatic block on above-threshold payments, escalation to the syndicate claims handler, generation of legal documentation required by the syndicate.

Step 6 — Atlas, oversight, binder renewal

Atlas is the Lloyd's system for coverholder and binding-authority management: onboarding workflow (for new coverholders), periodic due diligence, assessment of operational standards. For existing coverholders, Atlas means:

• Annual review: yearly review of the coverholder by the leading syndicate, based on delivered BDX, error rate, document quality, financial standing.
• Compliance audits: periodic inspections (every 2-3 years) by Lloyd's or the syndicate, end-to-end process verification.
• Performance metrics: shared KPIs (per-binder loss ratio, BDX timeliness, exception rate).

Binder annual renewal depends on the trend of these KPIs. A coverholder keeping loss ratio on target, BDX on time, and processes documented has near-automatic renewal; a coverholder with systemic issues risks non-renewal or capacity reduction.

In summary

The added value of a vertical PAS for Lloyd's coverholders is measured not on the single issued certificate, but on the full cycle MRC → certificate → BDX → claims → renewal. A generalist PAS can handle local issuance; a vertical one handles the operational translation between Lloyd's world and IVASS world, automating the steps that otherwise consume back-office time and generate errors.