How do card transactions get into Denovo CaseLoad?
By file import. Denovo CaseLoad publishes no public API, so there is no live bank-feed-style connection a card program can push transactions through. The working path is the one CaseLoad supports: a structured file, prepared in the format the system expects, imported by the cashroom.
Done by hand, that path is slow. Someone downloads a card statement, matches receipts, works out which client or matter each outlay belongs to, and either keys entries individually or reshapes a bank CSV into something CaseLoad will accept. Vergo's job is to remove that manual stage.
What is the manual process without any tooling?
- Collect receipts from every cardholder at month end.
- Download the card statement from the bank portal.
- Code each line to the right client, matter, or office expense.
- Re-key entries into CaseLoad, or hand-edit a spreadsheet into an importable shape.
- Chase the lines nobody can explain.
Every step is a chance for a miscoded outlay or a missing receipt, and it all lands on the cashroom in one batch.
How does Vergo automate the import?
Vergo issues the cards and captures the data at the point of spend, then produces the import file for you:
- Capture: each card transaction arrives in Vergo in real time; the spender attaches the receipt and codes it from their phone.
- Coding: transactions carry the references your CaseLoad import needs — date, amount, narrative, and the client or matter reference — before the file is ever generated.
- Export: Vergo generates a custom-built CSV matched to CaseLoad's import format. You import that file into CaseLoad rather than building it yourself.
The integration is file-based by design — Vergo does not claim an API sync with CaseLoad, because none is publicly available. What changes is who does the formatting and coding work: the software, not the cashroom.
How often should you run the import?
As often as your cashroom closes card activity — weekly and monthly are both common. Because coding happens continuously in Vergo rather than in a month-end scramble, the export is ready whenever you are, and each import is a short, reviewable batch instead of a backlog.
What about receipts and audit trail?
Receipts live against each transaction in Vergo, so the imported entries in CaseLoad trace back to a documented card transaction with the spender, receipt, and coding attached. That is the record you want when a client questions an outlay or an auditor samples expenses.
Can Vergo push transactions into CaseLoad automatically?
No — CaseLoad has no public API, so nothing can push into it live. Vergo generates a custom CSV matched to CaseLoad's import format, and your team runs the import.
What does the export file contain?
Each card transaction with date, amount, narrative, and the coding your team applied in Vergo — including client or matter references — arranged in the format CaseLoad expects on import.
Who codes transactions to matters?
Cardholders code their own spend in Vergo, and finance reviews before export. The cashroom stops re-keying and starts reviewing.
Does this replace keying card entries by hand?
Yes. The import file replaces manual entry; the remaining work is reviewing the batch and running CaseLoad's import.
