INTEGRATIONS
What VCA Connects to, and Which Way the Data Moves
VCA ClaimsCore is the claims layer beside the policy system, ledger and warehouse you already run. Policy data comes in through PolicyConnect, claims data goes out to your own warehouse through DataBridge, and VCA's API framework connects your partners, your finance systems and the other firms on a claim.
INTO THE CLAIM
OUT AND BACK
VCA CLAIMSCORE
Where the Claim Is Worked
Complete on its own, with add-ons for specific jobs.
OUT OF THE CLAIM
BETWEEN SYSTEMS AND FIRMS
VCA's API Framework
Partner, finance and policy-system connectivity, and other firms' VCA accounts on the same claim, each firm in its own seat
UNDERNEATH THE CLAIMMicrosoft 365 · SendGrid · Amazon S3
THE PROBLEM IT SOLVES
Every system a claim touches is a place a number can be keyed twice: the payment in the ledger, the estimate in an inbox, the policy detail taken down on the first call. Each connection below exists so it is keyed once, on the claim.
WHAT CONNECTS
Every Connection, by the Job It Does
Each row names the job, the systems that do it, which way the data moves and how it connects.
| The Job | The Systems | Which Way It Moves | How It Connects |
|---|---|---|---|
| Policy and Coverage Data Add-OnTypical for: MGAs and Programs · Carriers · Coverholders | PolicyConnect | INTO THE CLAIMfrom your policy system | REST APIs and webhooks for modern policy systems; scheduled batch, flat file or secure file transfer for legacy ones. |
| Claims Data for Your Warehouse Add-OnTypical for: Captives and Self-Insureds · Syndicates and Managing Agents | DataBridge | OUT OF THE CLAIMone way, to your own warehouse or BI tool | Incremental extracts on a schedule you set, as often as hourly. |
| Finance and Accounting | Intuit QuickBooks, Sage, Bill.com | OUT OF THE CLAIMto your ledger | Claim financials post to your ledger, each entry carrying the claim it belongs to: accounting entries in QuickBooks and Sage, claim payables in Bill.com. |
| Claim Payments Add-On | ClaimsPay | OUT OF THE CLAIMto the payee | Payments issued from the claim. VCA's payment partner is Vitesse. |
| Assignment and Estimating | XactAnalysis, Symbility | OUT AND BACKonto the same claim | XactAnalysis, the assignment and reporting network: mapped to your setup in discovery. Symbility, the field estimate: sent from the claim's Actions menu. |
| Property Data | CoreLogic, Hover, Encircle | OUT AND BACKonto the same claim | CoreLogic, the property record: mapped to your setup in discovery. Hover, roof and exterior measurements, and Encircle, field documentation: sent from the claim's Actions menu, where the integration is turned on. |
| Partners and Other Firms | VCA's API Framework | BETWEEN SYSTEMS AND FIRMSto and from the claim | Policy-system, partner and finance connectivity. When several firms play a role in the same claim, each in its own VCA account, the API framework moves the data between them. |
| Infrastructure | Microsoft 365, SendGrid, Amazon S3 | UNDERNEATH THE CLAIMoutside the claims workflow | Email, outbound notices and document storage. How the Platform Is Secured → |
DUE DILIGENCE
Settle three things before you sign
Ask VCA these, and ask the same of every vendor you compare. Get each answer in writing.
- Connections Mapped Before Anything Is ConfiguredEvery VCA implementation starts with discovery, on every band: we map how your claims move, including the handoffs to your policy system, ledger and partners. A Standard License goes live in 3 to 4 weeks, an Enterprise License in 8 to 16 weeks and a Carrier License in 12 weeks to 6 months.How Implementation Runs →
- What Happens to Your Data at the EndFor the end of an agreement, ask for the format, the timeline and the cost of returning your claims data, in writing.What to Get in Writing →
- What the Quote CoversPolicyConnect, DataBridge and ClaimsPay are add-ons to VCA ClaimsCore. Ask which connections your quote includes, which would take build work, and who maintains each connection after go-live.What a Quote Should Itemize →
THE ERP QUESTION
We run our finances in an ERP. Is that a conflict?
No. An ERP like Oracle NetSuite is a finance system, and VCA is designed to work alongside it. VCA runs the claims layer and posts clean, insurance-ready financials to your ERP or general ledger via API.
Your finance team keeps the system it knows, your claims team gets software built for claims, and the integration keeps the two layers in agreement. An ERP on the other side of the table is a reason to add VCA, not a conflict.
WHAT TO BRING TO THE CONNECTIVITY CALL
Each ledger keeps its own chart of accounts. Which accounts receive claim activity, and how often it posts, is worked out with your controller.
Bring the controller and the person who administers the ERP day to day, with a sample journal entry, the fields your ledger expects on a posting, and your current claim-payment approval path.
For PolicyConnect, the name of your policy administration system and how it exports today, by API or by file. For DataBridge, where your warehouse or BI tool lives and who administers it.
For the API, the systems on the other side and who on your team will own each connection.
Questions About Integrations
Does VCA ClaimsCore have an API?
Yes. VCA provides an API framework for policy-system, partner and finance connectivity. It is also how data moves between firms' VCA accounts when several firms play a role in the same claim, each working from its own seat. Policy data can also come in through PolicyConnect, and claims data can go out to your own warehouse through DataBridge, both add-ons.
Which integrations does VCA name publicly?
VCA names eleven integrations publicly: eight partner integrations, and Microsoft 365, SendGrid and Amazon S3 as the infrastructure underneath the claim. Intuit QuickBooks, Sage and Bill.com receive claim financials. XactAnalysis routes the assignment out and brings the completed estimate back, and Symbility covers the field estimate. CoreLogic supplies the property record, Hover the roof and exterior measurements, and Encircle the field documentation.
Does the data move by API or by file?
Both, depending on the system. PolicyConnect brings policy data in through REST APIs and webhooks for modern policy systems, and through scheduled batch, flat-file or secure file transfer for legacy ones. Claim financials post to your ERP or general ledger via API. DataBridge delivers scheduled extracts, as often as hourly. Symbility, Hover and Encircle are sent from the claim's Actions menu, and XactAnalysis and CoreLogic are mapped to your setup in discovery.
Does DataBridge send data both ways?
No. DataBridge, an add-on, moves claims data one way, out of VCA into your own data warehouse or BI tool. Policy data comes in through PolicyConnect, and data between firms' VCA accounts, or from partner systems, moves through VCA's API framework.
A system we need is not on the list. Is that a dead end?
No. It starts as a conversation about the API framework. Tell us what sits on the other side of your claims, whether that is your policy system, your clients' systems or your capacity providers' reporting, and we will tell you plainly what connects today and what would take work.
Bring us a claim where the promise was hard to keep
Start with the list of systems your claims touch. VCA implementations complete in weeks, not years.
Request a Demo