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 and your finance systems.
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
VCA's API Framework
Partner, finance and policy-system connectivity
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 invoice 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: Carriers · MGAs and Programs | PolicyConnect | INTO THE CLAIMfrom your policy system | Through VCA's API. |
| Claims Data for Your Warehouse Add-OnTypical for: Carriers · MGAs and Programs · TPAs | DataBridge | OUT OF THE CLAIMone way, to your own warehouse | Incremental extracts on a schedule you set, as often as hourly. |
| Finance and Accounting | Intuit QuickBooks, Sage, Bill.com | OUT OF THE CLAIMto your accounting system | Service invoices built from the time and expenses on each claim export to QuickBooks, Sage or 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 | INTO THE CLAIMon assignment | XactAnalysis: claims are created in VCA on assignment, a feature turned on by request. Symbility: assigned claims are imported into VCA from the unassigned claims list, and for those claims, file notes are sent to Symbility and files received from it through the claim's Actions menu. |
| Property Data | Hover, Encircle | OUT AND BACKonto the same claim | Hover, roof and exterior measurements, and Encircle, field documentation: sent from the claim's Actions menu, where the integration is turned on. |
| Partner Systems | VCA's API Framework | BETWEEN SYSTEMSto and from the claim | Policy-system, partner and finance connectivity. |
| 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. Claim transactions are stored on the claim and reachable through VCA's APIs, so a custom API connection can link the claim to your ERP.
Your finance team keeps the system it knows, your claims team gets software built for claims, and a custom connection can keep 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. What a connection carries is worked out with your controller.
Bring the controller and the person who administers the ERP day to day, with a sample invoice, the fields your ERP expects, 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 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. 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 connects with ten named systems today: seven partner integrations, and Microsoft 365, SendGrid and Amazon S3 as the infrastructure underneath the claim. Intuit QuickBooks, Sage and Bill.com receive the service invoices VCA builds from claim data. XactAnalysis and Symbility bring assigned claims into VCA. Hover supplies the roof and exterior measurements, and Encircle the field documentation.
Does the data move by API or by file?
It depends on the system. Service invoices export to QuickBooks, Sage or Bill.com, and claim transactions are reachable through VCA's APIs for a custom link to your ERP. DataBridge delivers scheduled extracts, as often as hourly. Claims assigned through XactAnalysis are created in VCA on assignment, and Symbility's assigned claims are imported into VCA. Hover and Encircle are sent from the claim's Actions menu.
Does DataBridge send data both ways?
No. DataBridge, an add-on, moves claims data one way, out of VCA into your own data warehouse. Policy data comes in through PolicyConnect, and partner systems connect 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