INTEGRATIONS · BILL.COM

Bill.com, with the Invoice Built on the Claim

A service invoice is the work on a claim, priced. It has a client, that client's rate or fee schedule, and a list of hours and expenses, and every line of it already exists on the claim before anyone opens a billing screen.

VCA Software exports the service invoices it builds from each claim to Bill.com, so nobody keys the same hours and expenses into two systems.

VCA CLAIMSCOREWhere the invoiceis builtTHE PARTNER SYSTEMBill.comWhere finance works the invoiceThe Service InvoiceWITHOUT IT, THE SAME WORK GOESThe Same ClaimHours and expenses keyed twiceAn Invoice Rebuilt by Hand
  • Out: The Service Invoice, to Bill.com. Finance rules stay in Bill.com.
  • Without it: hours and expenses are keyed twice, and the invoice is rebuilt by hand.
The service invoice leaves the claim built from its time and expenses. Finance works it in Bill.com, under the rules finance set there. An illustration of the export to Bill.com.

IN THE CLAIM

One Invoice, Followed End to End

Take a week of adjuster time and a mileage expense on a single claim. Here is where they go, who touches them, and which part of that belongs to claims rather than to finance.

ONE INVOICE, FOUR STAGES

  1. The Work Is Logged on the ClaimTime and expenses are entered on the claim, under activity codes and billable expenses that can be set up for each client.
  2. The Claim Builds the InvoiceVCA applies the client's rate or fee schedule and any co-insurer split, so nobody recalculates it.
  3. It Goes to Bill.comThe invoice is exported to Bill.com, where finance works it.
  4. The Claim Keeps the RecordThe entries behind each invoice line, who made them and when, stay on the claim, for anyone who has to answer for the invoice later.

WHAT MOVES

The invoice travels, the claim stays

Finance keeps its own rules in Bill.com, enforced in the system that owns them. ClaimsCore is the claims layer beside the systems you already run, so Bill.com stays where it is, and so does every rule inside it.

WhatWhich WayWhere It Lands
Service InvoicesOut of the claimBill.com, built from the time and expenses already recorded on the claim.
The Claim RecordStays in ClaimsCoreThe time and expense entries, who made each one and when, the documents, and who did what and when.
Finance's RulesStay in Bill.comConfigured by finance, enforced by finance.

WHO FEELS IT

Felt First in Finance

Finance buys a billing connection and feels it at month end. Firms that bill many clients feel it hardest, because each client can have its own fee schedule.

  • Accounts ReceivableStops keying hours and expenses that already exist on a claim, and can answer a question about any invoice line with the claim behind it.
  • The ControllerGets invoices built from the claim's own entries, with each client's rate or fee schedule already applied.
  • The AdjusterLogs time and expenses once, on the claim, and never keys them again for billing.

OFF THE DESK

What Stops Living in Email

Most of what this connection removes is not work anybody was asked to do. It accumulated because the work was logged in one system and billed from another.

  • Entering the same hours and expenses a second time, in a second system.
  • The billing thread that lives in email and cannot be produced when a client queries an invoice.
  • Hunting for the entries behind an invoice line when someone questions it months later.
  • Recalculating fee schedules and co-insurer splits by hand at the end of the month.

THE BOUNDARY

Claims records the work. Finance runs the books.

Claims records what was done on the claim, by whom and when. Finance decides how the business accounts for it.

It also answers the question a client's audit team asks: each invoice line traces to the work recorded on the claim.

Start the Connectivity ConversationHow Implementation Runs →

WHAT TO BRING TO THE CONNECTIVITY CONVERSATION

Your clients' fee schedules and a sample invoice as your clients receive it today, plus whoever administers billing. Discovery maps it before anything is configured.

Questions About Claims Invoicing

Where is the invoice built?

On the claim. VCA ClaimsCore builds the service invoice from the time and expenses logged against the claim, with the client's rate or fee schedule and any co-insurer split applied, and records who entered each item and when.

Does this change how finance works in Bill.com?

No. The invoice is exported to Bill.com and finance works it there as it does today. VCA stays the claims layer: its goal is not to replace your accounting system.

What stays on the claim once the invoice leaves?

Everything behind it. The time and expense entries, who entered each one and when, the documents and the record of who did what and when all stay in ClaimsCore.

Is this the same as ClaimsPay?

No. ClaimsPay is the VCA add-on for issuing claim payments from the claim itself. The Bill.com connection carries the service invoices your operation bills its clients for.

Which accounting systems take the same export?

Intuit QuickBooks and Sage take the same service invoice export. Claim transactions are stored on the claim and reachable through VCA's APIs, so a custom API connection can link VCA to another accounting system.

Who benefits most from this one?

The billing team first, then the controller. Invoices arrive built from the claim's own entries, and the same invoices are the basis for adjuster payout reports.

Bring us a claim where the promise was hard to keep

Bring an invoice your operation sent this month and watch it rebuild from the claim's own time and expenses. Nothing else needs testing.

Request a Demo