LLOYD'S DCA · LLOYD'S MARKET

London Reporting, Without the Rework

A delegated claims administrator (DCA) reporting into the Lloyd's market stopped checking and rechecking its own data once its bordereaux were produced from the claims themselves.

AT A GLANCE

THE CLIENT, NOT NAMED

Delegated claims administration in the UK market

THE OPERATION

Judged Twice on Every Claim

A delegated claims administrator (DCA) in the UK market, on the DCA and coverholder side of the Lloyd's market.

Claims are handled under delegated authority and reported back to London, which means the operation is judged twice: once on how it handles claims, and once on how it evidences that handling to the people who delegated the authority.

Bordereau production is where the second judgment lands.

Reporting Assembled Outside the System

Pull the claims, shape them into the expected format, reconcile what does not tie out, then check the whole thing again, every cycle.

Two Versions of the Same Data

Anything transcribed into a reporting layer becomes a second copy, and a second copy has to be reconciled before anyone can trust it.

Errors the Market Finds First

A reporting error is the kind somebody else notices, which is why the checking expands until it costs more than the reporting.

WHAT CHANGED

Reporting moved into the claim

The DCA works its claims in VCA ClaimsCore, and the reporting London expects now comes from those same claims instead of a copy made for the purpose.

THE ARC OF THE STORY

  1. The ConditionEvery reporting cycle rebuilt outside the claims system, and then checked twice because nobody could see where the two versions differed.
  2. The ChangeBordereau production moved onto the claim record. Each claim populates the reports it belongs to, so there is no separate reporting layer to keep in step.
  3. What It LeftThe same monthly reporting without the rounds of checking. The output was no longer a separate artifact, so there was no second version of the data to check the first against.

THE RESULT ON THE RECORD

Hours the Reporting Gave Back

One figure belongs to this operation. A second belongs to a different client, is published under that client's own name, and is kept apart from it here.

THIS OPERATION

76 hours a month saved on reporting.

From VCA's published case study of this DCA's reporting work.

A SEPARATE CLIENT, NAMED

Vanguard Claims, another Lloyd's DCA, reduced manual data handling by approximately 40%.

Vanguard's own figure for its own work. It is not part of this operation's result. Vanguard's own story →

How Proof Gets Published Here →

HOW THE REPORTING RUNS

What produces the bordereau?

The contract is set up once, the reports run from the claims each period, and the scope stays on the claims side of the market.

  • Set Up Once, at the UMRThe Unique Market Reference is set up once, and bordereaux populate per claim from the claims themselves, for both individual-risk and subscription market business.Bordereau Reporting →
  • The Lloyd's Report SetLloydsConnect produces the Lloyd's Standard Bordereau, the Standard Bordereau with Certificate Allocation, the Lloyd's MI report, and the Lloyd's Solvency report.LloydsConnect →
  • The Claims BordereauVCA produces the claims bordereau. The premium or risk bordereau reports what was written and the money due on it, and comes from the system that writes the business.

WHY IT MATTERS NOW

Evidence is part of the job now

As of January 1, 2026, Lloyd's made Claims Management a hurdle Principle (Principle 4). The Principles bind managing agents (MAs); coverholders and delegated claims administrators (DCAs) carry it through the managing agent's oversight, audit, and reporting requirements.

A reporting routine held together by a person and a spreadsheet is harder to evidence in that conversation than one that is a product of the claim record.

Principle 4 and the Delegated Claim →

On the Evidence Question

The three-part series "Proof, Not Attestation" by Chief Product Officer Ilda Cairns covers what Principle 4 requires and how to evidence compliance.

Read the Series →

HOW THIS STORY IS PUBLISHED

Described by Its Work, Not Its Name

The DCA is not named on this page, and nothing here points to it beyond the market it reports into. It is described by the work it does, which is the part you need to tell whether its story is yours.

Its figure comes from VCA's published case study of its reporting work. Vanguard Claims is named once, for its own figure, which stays apart from this operation's result.

All Case StudiesVCA for DCAs →

WHAT THE PAGE LEAVES OUT

The DCA's name, its offices and its people. None of them changes what the story shows.

TAKE THIS STORY WITH YOU

The same story on two pages, ready to forward or print.

Download the PDF(2 Pages)

Questions About Reporting From the Claim

What did the DCA need from a claims system?

The operation is a UK delegated claims administrator (DCA) in the Lloyd's market. Its claims are handled under delegated authority and reported back to London, which means the operation is judged twice: once on how it handles claims, and once on how it evidences that handling to the people who delegated the authority. Every reporting cycle was rebuilt outside the claims system, and then checked twice because nobody could see where the two versions differed.

What does the DCA run on VCA?

The DCA works its claims in VCA ClaimsCore, and the reporting London expects now comes from those same claims instead of a copy made for the purpose. The Unique Market Reference is set up once, and bordereaux populate per claim from the claims themselves, for both individual-risk and subscription market business. LloydsConnect produces the Lloyd's Standard Bordereau, the Standard Bordereau with Certificate Allocation, the Lloyd's MI report, and the Lloyd's Solvency report.

What changed after go-live?

The DCA saves 76 hours a month on reporting, by VCA's published case study of its reporting work. The same monthly reporting runs without the rounds of checking: the output is no longer a separate artifact, so there is no second version of the data to check the first against.

Bring us a claim where the promise was hard to keep

VCA goes deep in claims, down to the report London reads each month. See a bordereau produced from the claim record rather than assembled in a spreadsheet.

Request a Demo

How Implementation Works →All Case Studies →