TPA · DOMESTIC MARKET

From Field Adjusting to a Full-Service TPA

A regional field adjusting firm moved into third-party administration for the E&S market, and needed one system that could carry dozens of client contracts, each with its own rules for money and compliance.

AT A GLANCE

THE CLIENT, NAMED

Peninsula Insurance Bureau (PIB), third-party administration in the E&S market

THE SEAT

TPAs

THE OPERATION

A TPA with Dozens of Rulebooks

Peninsula Insurance Bureau has handled claims since 1990. It began as a regional field adjusting firm and moved into third-party administration for carriers, syndicates and coverholders in the excess and surplus market.

The move changes what the software has to hold. A field firm reports on the assignment. A TPA answers to every client it handles claims for, and PIB carries dozens of Lloyd's and TPA contracts, each with its own financial tracking and compliance standards.

It runs all of it with a fully remote team of more than 150, so the claims system is also the office.

Every Contract, Its Own Standards

Financial tracking and compliance rules differ from client to client, and one fixed workflow cannot carry them all.

Hundreds of Client Bank Accounts

Money moves on behalf of many clients at once, and every account has to stand up to an audit on its own.

A Team That Works From Anywhere

A remote workforce needs one place where every claim, document and payment is visible and auditable.

WHAT CHANGED

One Environment, Configured Client by Client

PIB started with a few features and moved, over time, to running its whole TPA operation on VCA, with each client's requirements configured into it.

THE ARC OF THE STORY

  1. The ConditionClaims setup, data extraction and reporting done by hand, and workflows that could not change from one client to the next, while the client list grew.
  2. The ChangeClaims, documents and financials in one environment, with client-specific templates, compliance workflows and custom data fields.
  3. What It LeftMemos and billing automated, clients reading live claims data through API integrations, and new staff onboarded within days when a catastrophe hits.

Configure what the work needs, and add the rest when it needs it. How Implementation Works →

THE RESULT ON THE RECORD

What the Record Shows

Two results sit on the public record: a figure from the case study, and what PIB did next.

THE FIGURE

PIB cut administrative work by 40% by automating manual memos and billing.

From the PIB case study, under "time savings through automation".

In a fast-moving environment, we needed flexibility, VCA enabled us to serve clients with unique requirements while keeping everything organized, auditable, and efficient.
PIB's CIO and Analyst ProgrammerFrom the PIB case study

The Second Result: A Renewal

In 2026 PIB renewed its partnership with VCA.

The Renewal Record →

INSIDE VCA CLAIMSCORE

What ClaimsCore Takes off the Desk

The case study names three parts of the platform PIB set up client by client, in one environment with the claims, documents and financials they govern.

  • Client-Specific TemplatesEach client PIB administers claims for has its own templates, rather than one set reshaped contract by contract.
  • Compliance WorkflowsEach contract's compliance standards run as workflows on the claim, set per client rather than as one fixed path.
  • Custom Data FieldsThe data each client asks for is captured in fields added for it, on the same claim as the documents and financials.

Everything ClaimsCore Does on Its Own →

HOW THIS STORY IS PUBLISHED

Named, From PIB's Own Record

PIB is named on this page because its case study and its 2026 renewal both name it, and the page uses the name for the work those references cover.

The figure is the case study's own, in its terms, with nothing converted to hours or attached to a claim count.

All Case StudiesVCA for TPAs →

WHAT THE SOURCE DOES NOT SAY

The case study gives no implementation duration and no module list, so this page gives neither. Which add-ons beyond ClaimsCore PIB runs is not on the public record.

How long a deployment takes depends on its band, and every band starts with discovery.

Deployment Bands and Timelines →

TAKE THIS STORY WITH YOU

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

Download the PDF(2 Pages)

Questions About Running a TPA on VCA

What did PIB need from a claims system?

Peninsula Insurance Bureau (PIB) began as a regional field adjusting firm and moved into third-party administration in the E&S market, and needed one system that could carry dozens of client contracts, each with its own rules for money and compliance. It runs all of it with a fully remote team of more than 150, so the claims system is also the office.

What does PIB run on VCA?

PIB runs its whole TPA operation on VCA, with claims, documents and financials in one environment and each client's requirements configured into it: client-specific templates, compliance workflows and custom data fields.

What changed for PIB after go-live?

PIB cut administrative work by 40% by automating manual memos and billing. Its clients read live claims data through API integrations, new staff are onboarded within days when a catastrophe hits, and in 2026 PIB renewed its partnership with VCA.

Bring us a claim where the promise was hard to keep

Bring the client contracts you administer today, and we'll show you how ClaimsCore carries each one's rules on the claim.

Request a Demo