FOR MGAs AND PROGRAMS

Claims Software for MGAs, Program by Program

VCA ClaimsCore runs every program you write in one platform, each configured to its own paper, and builds each program's reporting from the claims as they are handled, whether your desk or a TPA does the work. A Lloyd's binder and domestic paper run on the same ClaimsCore, without a second system.

A TYPICAL MGA PACKAGE

ClaimsCore, and What an MGA Adds to It

Every program runs on ClaimsCore. A typical MGA package adds PolicyConnect for the program's policy detail, ClaimsPay for payments, VCA Insights for reporting across programs, DataBridge for your claims data in your own data warehouse, and LloydsConnect where capacity is Lloyd's. ClaimsPay connects to Vitesse, so a payment approved in VCA is issued without re-keying. ClientPortal is added where a program needs it.

YOUR PROGRAMS

WHAT GOES UP FOR EACH

VCA CLAIMSCORE

One Set of Claims, Every Program on Its Own Terms

  • Workflows, Rules and Reporting, Set per Program
  • Authority Limits, Set per User

PROGRAM A

Domestic Carrier Paper

Worked by your desk

Program Reports to the Carrier

In ClaimsCore

PROGRAM B

A Lloyd's Binder

UMR set up once

The Lloyd's Report Set

LloydsConnect, an add-on

PROGRAM C

Handling Placed with a TPA

Worked from the TPA's own seat

The Capacity Provider's Own Login

ClientPortal, an add-on

Each program keeps its own configuration and its own reporting, drawn from one set of claims.
Vicky, VCA's guide

ADD-ON: CLAIMSAI

ClaimsAI by VCA, Inside the Claim

ClaimsAI by VCA works inside one claim at a time, with four capabilities: Documents, Chat, Standing Checks and First Notice. It reads what is on the claim, summarizes what matters and drafts for review. It never sets a reserve, approves a payment or decides a claim.

ClaimsAI does not update anything in the claim. What it drafts reaches the claim only when a person copies it there. How ClaimsAI Works →

THE PROBLEM IT SOLVES

Several programs, several capacity providers, some of the handling placed with TPAs, and each capacity provider expects its own book reported on its own schedule. Pieced together from extracts, the numbers you send up and the numbers you manage against drift apart.

PER-PROGRAM CONTROL

Every Program on Its Own Terms, Every Movement on the Record

Each program is configured to what its paper requires. What its capacity provider asks to see is attached to the program, so the reporting obligation travels with the claims that owe it, and reserve movements, recoveries and AI drafts are each recorded on the claim.

  • Workflows and RulesThe steps a claim takes and the rules that fire on it, set per program.
  • Authority Limits per UserSet for each user and tracked alongside the reporting requirements attached to them. A reserve above a handler's limit waits under Pending Approvals. Once approved, it moves into the active list; until then the new reserve is not in place on the claim.
  • Transactional Reserve HistoryEach reserve movement is recorded with the date, who made it and the reason given.
  • A Profile for Each CarrierEach carrier you write for has a profile holding its contracts and SLAs, and its rates, protocols and instructional documents carry into every claim handled for it.
  • Recoveries Netted on the ClaimSubrogation and salvage recoveries post against the reserve they offset, with amounts filed, funds received and the net shown on the claim.
  • Every AI Draft, Reviewed by a PersonWhen ClaimsAI by VCA™ drafts inside a program's claim, it does not update anything in the claim. The handler reads the draft and copies what they can use. Your handlers decide.

WHEN THE BOOK GROWS

You add programs, not systems

Program business rewards the MGA that can take on a new program and show control over it from the first claim.

A new program is configured inside the platform you already run, with its own workflows, rules and reporting, and your desk works it in the same ClaimsCore as every other program. Part of setting up a program is knowing what to leave out: configure what matches its work, skip the rest, and add more as the program grows. Programs can run on every property and casualty line, but not workers' compensation or health benefits.

How a Lloyd's DCA Runs Program Business →

ACCELERANT MARKETPLACE

VCA is part of the Accelerant Marketplace, where Accelerant Members find trusted partners for their programs.

Request a Demo

WHEN A TPA HANDLES THE CLAIMS

Place the handling, keep the claims

Capacity holds you to account for claims a TPA may be handling and you can't always see. With VCA, each program's claims sit in an environment you govern, whoever works them.

WHAT THE MGA GETS

Your TPA's Choice of System, Your Program View

Your TPA can work in your VCA environment or stay in its own system, connected to yours by API. Each firm works from its own seat.

What This Looks Like From the TPA's Side →

WHEN A CLAIM CROSSES YOUR AUTHORITY

Above a Handler's Authority

When your TPA works in your VCA environment, a reserve above its handler's limit is submitted for approval and routed to a chosen approver, with a note written to the claim. When your TPA keeps its own system, VCA maps that handoff in discovery, before anything is configured.

Claims Oversight When Someone Else Does the Handling →

YOUR DATA, IN AND OUT

Can your actuaries query the claims in your own warehouse?

Your actuary asks for current numbers on a Tuesday afternoon. The answer should be the book as it stands that day.

DataBridge, an add-on to ClaimsCore, delivers claims data into your own data warehouse on a schedule you set, as often as hourly. Only changes are pushed, so the figures your actuaries and program managers work from stay current with the book.

See the Integration List →

Out to Your Warehouse

Your team combines the claims data with policy, actuarial and financial data in infrastructure you own.

DataBridge →

Linked to Your ERP or General Ledger

Claim transactions are stored on the claim and reachable through VCA's APIs, so a custom connection can link them to your ERP. The ERP keeps the books; VCA keeps the claims.

In From Your Policy System

PolicyConnect brings policy and coverage detail from your policy or underwriting system onto the claim, with fields, sync cadence and validation rules set per program.

PolicyConnect →

DOMESTIC CAPACITY AND LLOYD'S CAPACITY

One Claims Operation, Domestic Paper and Lloyd's

An MGA that writes on domestic paper and is also a Lloyd's coverholder runs both books in one ClaimsCore. From those claims, LloydsConnect produces the Lloyd's report set:

  • Lloyd's Standard Bordereau
  • Standard Bordereau with Certificate Allocation
  • Lloyd's Management Information report
  • Lloyd's Solvency report

VCA serves the DCA and coverholder side of the Lloyd's market, where reporting is graded, audited and evidenced with data, and a platform that clears that bar has no trouble with a domestic capacity provider's report.

How LloydsConnect Produces the Report Set →

IF SOME OF YOUR PAPER IS LLOYD'S

Since January 1, 2026, Lloyd's Principle 4, claims management, has been a hurdle Principle. The Principles bind managing agents (MAs), and a DCA or coverholder handling claims under a binder carries it through the managing agent's oversight, audit, and reporting requirements. It arrives as a question from the party you report to, and the answer is expected to be evidenced rather than asserted.

What Principle 4 Asks of the Delegated Side →

WHY VCA

Why MGAs Choose VCA

VCA has been building claims software for more than 20 years, and several client relationships are longer than ten. Program business is judged on control, on speed, and on what the claims system costs to run beside the ones you have.

  • Depth of Claims ExpertiseWe know claims from every seat we work with, the MGA's included: per-program authority, reporting up to capacity, and the TPA on the other end.Why VCA →
  • Speed of ImplementationDiscovery comes first, so ClaimsCore is configured to how your programs actually run, against a published range you can plan around.
  • Capital EfficiencyThe claims layer beside the policy system and ledger you already run, so none of the spend goes on replacing a suite. Each program you add is set up on that layer.Build vs. Buy Claims Management Software: The Real Cost →

Questions MGAs Ask

Does VCA replace our TPA's claims system?

No. A TPA can work your program inside your own VCA environment, or keep the system it already runs. Which claims data reaches your account, and how, is mapped with your TPA in discovery, before anything is configured. Either way, each firm works from its own seat, and what you report to a capacity provider comes from the claims you govern.

Can VCA produce bordereaux for our capacity providers?

For Lloyd's business, yes. LloydsConnect, an add-on to VCA ClaimsCore, produces the Lloyd's report set, including the Lloyd's Standard Bordereau. Set up the Unique Market Reference once and the bordereau populates from each claim, for individual-risk and subscription market business alike. For every program, VCA Insights sends scheduled reports and branded dashboards to the carriers and partners behind it, drawn from the claims. VCA produces the claims bordereau. A premium or risk bordereau reports what was written and the money due on it, and comes from the system that writes the business.

Do we have to be in the Lloyd's market to use VCA?

No. VCA ClaimsCore runs claims on domestic paper and is complete on its own. LloydsConnect is an add-on for Lloyd's business, added to the ClaimsCore you already run if you take a Lloyd's binder.

How long does implementation take?

Every implementation starts with discovery: VCA maps how your programs' claims move, from intake sources and authority levels to the reporting each capacity provider expects and the handoffs to your TPAs, before anything is configured. Which band you land in is scoped at quote. Several programs configured side by side, with integrations and migrated claim history, is an Enterprise License build: 8 to 16 weeks. An operation whose handling already runs close to ClaimsCore's defaults can go live on a Standard License, configured to your workflows, in 3 to 4 weeks. Data migration is its own phase: open and historical claims move into ClaimsCore and are checked against the source before go-live.

What does our team have to do, and what happens after go-live?

Your side's part starts in discovery, where VCA maps how your programs' claims actually move before anything is configured. Training is short: file handlers typically need 30 to 60 minutes of training. Once your claims are live, client services is reachable at clientservices@vcasoftware.com.

Can we get our claims data out?

Yes, with DataBridge, an add-on to VCA ClaimsCore: a current extract of your claims data lands in a data warehouse you own, on a schedule you set, with no custom API connectors for your team to build or maintain. What happens to your data at the end of an agreement, in what format, by when and at what cost, belongs in the agreement itself. Ask us for it in writing, as you should of any claims vendor.

How does VCA handle catastrophe claims?

Each claim records a Cat Code and Treaty Year in its loss details. A CAT claim team takes surge assignment, and assignment rules route claims by loss location and adjuster workload.

Does VCA take on claims work itself?

No. VCA makes claims management software and only claims management software, with no adjusting arm, no TPA division and no claims services business. Being a pure claims company, with no services arm competing with the people it serves, lets VCA stay on their side of the table.

Bring us a claim where the promise was hard to keep

Tell us which programs you write, who provides the capacity and what each one asks to see. We'll walk a claim from its program's setup to the report that goes up, using your programs as the example.

Request a Demo

How to Evaluate Claims Software →