CLAIM PAYMENTS · ADDED TO VCA CLAIMSCORE
ClaimsPay
ClaimsPay is the add-on to VCA ClaimsCore that issues claim payments from the claim they belong to, so each payment stays beside the reserve it draws on and the decision behind it.
TYPICAL FOR
Domestic MarketTPAsMGAs and ProgramsBrokersCarriersPublic Entities and Government
Lloyd's MarketDelegated Claims Administrators (DCAs)Coverholders
RECORDED IN CLAIMSCORE
- The Reserve and Its History
- Authority Limits by Client or Program
- Each Payment Against Its Reserve
ClaimsCore keeps this record on its own, with or without ClaimsPay
CLAIMSPAY
Issued From the Claim
Every payment logged and timestamped on its claim
WHO IT PAYS
- Policyholders
- Contractors
- Medical Providers
- Attorneys
Each payment names its payee and its reserve
THE PROBLEM IT SOLVES
Payment usually happens somewhere other than the claim. The money goes out in a separate payment run while the reason for it stays on the claim, and an audit is where someone has to match the two.
THE COMPANY BEHIND CLAIMSPAY
WHAT IT DOES
What does ClaimsPay do on a claim?
Handlers pay from the claim they are working, and the people you authorize approve each payment there.
Pay From the Claim
Handlers start a payment on the claim it belongs to and pick the reserve it draws on, with the balance left on each reserve in view.
Many Payees, One Claim
Policyholders, contractors, medical providers and attorneys can each be paid, and every payment names its payee.
Approval on the Claim
Payments are approved on the claim by the people you authorize. Until then, a payment waits on the claim as pending.
Payment History
Each payment shows its payee, amount, reserve, date, reference and status on the claim, logged and timestamped, and a supporting document can be attached.
WHY IT MATTERS
What Changes When Payments Start on the Claim
The payment travels with the decision behind it, so whoever checks it later finds both in one place.
A person authorizes it
A claims professional you authorize approves each payment before it is issued. ClaimsAI by VCA™, where you add it, never approves or issues one. ClaimsAI arrives by the end of 2026.
Audits find one trail
The approval, the payment and the reserve it drew on sit together on the claim, so an auditor reads one trail instead of matching two.
Finance sees the source
The reserve history records each movement, who made it and which fund account it came from, so finance can see the account behind every reserve movement.
Payee calls get answered
Whoever takes the payee's call can see where the payment stands without leaving the claim.
HOW IT FITS
How does a payment move?
Each step of a claim payment has one owner, so no one has to guess which system holds the answer.
- Recorded in ClaimsCoreEvery payment is recorded against the reserve it draws on, and the reserve's history shows each movement and who made it. ClaimsCore does this on its own, with or without ClaimsPay.Reserves and Payments in ClaimsCore →
- Issued Through ClaimsPayOnce a payment is approved on the claim, ClaimsPay issues it to the payee without re-keying payment details between systems, and the payment stays on the claim it was issued from.
Vitesse partnership announced September 16, 2026
- Posted to Your LedgerInsurance-ready financials go from the claim to Intuit QuickBooks, Sage or Bill.com, or through VCA's API to your own ERP or general ledger. Finance keeps the system it already runs.What VCA Connects To →
WHY VCA
Why Claims and Finance Teams Choose VCA
Finance keeps the ledger. VCA goes deep in claims, so each payment is approved on the claim it belongs to.
- Depth of Claims ExpertiseBuilt from the claim up, by an adjuster, for the people who work the claim, so a payment starts where the adjuster makes the call.Why VCA →
- Speed of ImplementationDiscovery maps your authority levels and the handoffs between claims, finance and partners first. ClaimsCore then goes live in 3 to 4 weeks on a Standard License, 8 to 16 weeks on an Enterprise License, and 12 weeks to 6 months on a Carrier License.
- Capital EfficiencyVCA is the claims layer beside the ERP or ledger finance already runs, and each payment's financials post to it. ClaimsPay is added when paying from the claim is worth it to your team, never as the price of running ClaimsCore.
Questions About ClaimsPay
What is ClaimsPay?
ClaimsPay is an add-on to VCA ClaimsCore that issues claim payments from the claim they belong to. A payment approved on the claim by the people you authorize goes out to the payee without anyone keying its details into a second system, and ClaimsCore records it against the reserve it draws on.
Can we run ClaimsCore without ClaimsPay and add it later?
Yes. VCA ClaimsCore is complete on its own: it records every payment against the reserve it draws on, and the reserve history shows each movement and who made it. ClaimsPay adds issuing the payment from the claim, and it can be added whenever your team is ready to pay from there.
Which payment partner does ClaimsPay work with?
VCA Software and Vitesse announced a strategic partnership on September 16, 2026, connecting claims management and insurance payments so a payment approved in VCA is issued without re-keying payment details between systems. Ask VCA which payment methods and countries are live for your payees today.
How do claim payments reach our ledger?
Intuit QuickBooks, Sage and Bill.com receive claim financials from the claim. Any other ERP or general ledger receives them through VCA's API framework, so finance keeps the system it already runs. An ERP such as Oracle NetSuite is not a claims system, and VCA runs the claims layer beside it.
Can we get our payment data out?
The payment's financials post to your own ERP or general ledger, so those entries live in a system you own. DataBridge, added to ClaimsCore, delivers your claims data to your own data warehouse or BI tool on a schedule you set, as often as hourly. Ask VCA in writing for the format, timeline and cost of returning your data at the end of the agreement, and put the same question to every vendor you compare.
Who uses ClaimsPay?
Claims handlers and admins start payments on the claim, and the people you authorize approve them there. Finance teams and controllers work from the posted entries and the payment log behind them. In a typical package, TPAs, MGAs, brokers, carriers and public entities add ClaimsPay to VCA ClaimsCore, and so do DCAs and coverholders in the Lloyd's market.
What should finance ask any claim-payment vendor?
Claim payments carry obligations of their own: information reporting on reportable payments, sanctions screening of payees, and unclaimed property reporting on uncashed claim checks. Before you sign with any vendor, VCA included, get four answers in writing: which of these obligations the product handles and which stay with your team, who holds and moves the funds, what each payment costs and who bills it, and which payment methods and countries are live today. Every VCA implementation starts with discovery, which maps your reporting obligations and the handoffs between your teams and partners before anything is configured.
What audit reports does VCA hold?
VCA holds SOC 1 and SOC 2 reports, each Type 1 and Type 2, examined by Prescient Assurance. On the claim, each payment is logged and timestamped.
Bring us a claim where the promise was hard to keep
Bring your claims lead and your controller to the same conversation, with the kinds of payments your team makes today.
Request a Demo