What are a firm's options for card spend in Insight Legal?
Insight Legal does not publish a public API, so there is no direct feed from any card platform into the system. That leaves manual entry — the cashier keying each card payment from statements, chasing fee earners for what each one was — or a batch import from a file. The import is clearly the better path; the question is who does the work of making the file importable.
Why does a bank's card export not import cleanly?
Because Insight Legal needs to know things a statement cannot say: which matter a court fee or search belongs to, whether a payment is a disbursement or office expenditure, which nominal an office cost posts to, and the VAT treatment. A raw export is merchant names and amounts. Turning it into a compliant posting batch is exactly the month-end spreadsheet-and-email exercise firms are trying to escape.
How does the Vergo workflow reach Insight Legal?
1. Spend on Vergo cards. Fee earners and staff use firm cards; every transaction appears in Vergo when it settles, and the cardholder is prompted for the receipt from their phone.
2. Tag at the point of purchase. The cardholder tags spend as they go — to a matter where it is a disbursement, or to the correct nominal where it is an office expense. Recurring suppliers are coded automatically by rules.
3. Vergo generates the import file. The CSV export is custom-built to match the import format your Insight Legal system expects, so it loads without remapping or rework.
4. The cashier imports the batch. Accounts staff review the coded batch and run the import in Insight Legal like any other posting routine. Control over what posts, and when, stays with your accounts team.
What does this change at month-end?
The reconstruction work disappears. Matter attribution, receipts, and coding were captured during the month at the point of spend, so month-end is a review and a single import rather than an investigation. Disbursements reach the right matters while they can still be billed on, instead of surfacing weeks later.
Is this an API integration with Insight Legal?
No — Insight Legal publishes no public API, and we will not imply a sync that does not exist. This is a file-based integration in which the file is built for Insight Legal specifically, which is what makes it automation rather than admin.
Can Vergo post directly into Insight Legal?
No platform can — Insight Legal publishes no public API. Vergo generates a custom-built CSV export matched to your Insight Legal import format, and your accounts team posts it as a standard batch import.
How are disbursements handled?
Cardholders tag disbursements to their matter at the point of purchase in Vergo, so the import batch arrives with matter attribution already in place — ready to bill on rather than reconstructed at month-end.
What does the cashier have to do each month?
Review the coded batch in Vergo, export the CSV, and run the import in Insight Legal. Because coding and receipts were captured during the month, this is minutes of work, with full control retained over posting.
Does this require anything from Insight Legal or Dye & Durham?
No. The workflow uses Insight Legal's normal import capability — no vendor project, no API access, nothing to be provisioned by the software supplier.
