What are the options for getting card spend into Capium?
Capium supports bank feeds for bank accounts and file import for transaction data. Because Capium publishes no public API, those are the only routes — no expense platform can push card transactions straight into the ledger. For corporate or credit card spend that isn't covered by a feed, the practical route is importing a transaction file into the relevant client's bookkeeping records.
Why is the raw card statement painful to import?
Card providers export statements in their own layout: their date formats, their column order, their merchant descriptions, no nominal coding. Getting that into Capium means reshaping the file each month — reordering columns, fixing dates, adding coding — and doing it per client if you run a practice. It works, but it is exactly the kind of repetitive cleanup that eats a bookkeeping team's time and invites errors.
How does Vergo make the import clean?
Vergo is a corporate card and expense platform, so the transaction data starts life structured: every card transaction arrives with date, merchant, amount, the coding your team applies, and a captured receipt. When it is time to update Capium, Vergo generates a custom-built CSV export matched to the import format Capium expects. You download the file and import it — no remapping, no manual reshaping.
The workflow each period looks like this:
- Team members spend on Vergo cards; receipts and coding are captured in Vergo as they go.
- At close, review and approve the period's transactions in Vergo.
- Download the Capium-matched CSV export.
- Import the file into Capium and reconcile as usual.
Is this the same as an integration?
It is a file-based integration — the honest kind for a system with no public API. Nothing flows automatically into Capium, and no vendor can truthfully promise that it does. What Vergo removes is the manual labour between the card and the books: the coding happens once, at the point of spend, and the export lands in Capium's format every time. For a cloud-hosted system like Capium, that keeps month-end a short, repeatable routine rather than a data-entry job.
What changes for the practice month to month?
The first month is setup: cards issued through Vergo, coding conventions agreed so exports line up with each client's chart, and one test import into Capium to confirm the format lands cleanly. Every month after that is repetition — approve, download, import, reconcile. Because cardholders code and attach receipts at the point of spend, the bookkeeping team stops chasing paperwork after the fact, and queries about a transaction are answered by opening it in Vergo rather than emailing the cardholder.
Can Vergo sync automatically with Capium?
No — Capium publishes no public API, so no platform can sync into it automatically. Vergo provides custom CSV exports matched to Capium's import format as the working path.
What does the Vergo export file contain?
The period's approved card transactions — dates, merchants, amounts, and the coding applied in Vergo — arranged in the format Capium's import expects.
How often should I import?
Most teams import once per period as part of month-end close, though the export can be run whenever transactions have been approved in Vergo.
Do receipts come across in the file?
The CSV carries transaction data. Receipts stay stored against each transaction in Vergo, available whenever you need to evidence a cost.
