What are the options for getting card transactions into CosmoLex?
CosmoLex does not publish a public API, so there is no direct programmatic sync for an expense platform to push transactions in. That leaves three realistic paths: manual entry of each transaction, importing a raw file from your card provider and cleaning it up inside CosmoLex, or importing a file that arrives already structured and coded. The third path is the one that scales, and it is the one Vergo is built for.
Why is a raw bank export not enough?
A raw card statement export gives you dates, amounts, and merchant strings — nothing else. Someone still has to attach receipts, decide the expense category, and tie spend to the right matter where it is billable. That cleanup is the actual work, and doing it in a spreadsheet after the fact means chasing cardholders weeks after the purchase.
How does the Vergo-to-CosmoLex import work?
Vergo moves the coding upstream to the moment of spend. Cardholders snap receipts and code transactions as they happen; admins see everything in one place. When it is time to book the activity, Vergo generates a custom-built CSV export matched to CosmoLex's import format — columns arranged the way CosmoLex, a hosted cloud platform, expects to receive them. Your bookkeeper imports that file and the card activity lands coded, with the receipt trail kept in Vergo.
What does the workflow look like step by step?
1. Team members spend on Vergo cards and attach receipts from their phones. 2. Transactions get coded in Vergo — by the cardholder or by policy. 3. On your close cadence, Vergo produces the CSV export built for your CosmoLex setup. 4. The bookkeeper imports the file into CosmoLex. 5. Reconciliation is a check, not a data-entry project, because the imported data already matches the card program.
Is the import format generic or matched to CosmoLex?
Matched. The export is custom-built for CosmoLex's import format rather than a one-size-fits-all template, which is what makes the import a single clean step instead of a column-mapping exercise every month.
Can card transactions sync into CosmoLex automatically?
Not over an API — CosmoLex does not publish one. The working automation path is a structured file import, which Vergo generates matched to CosmoLex's format.
What file format does Vergo produce for CosmoLex?
A custom-built CSV export matched to CosmoLex's import format, so the file imports cleanly without re-mapping columns.
Where do receipts live in this workflow?
Cardholders attach receipts in Vergo at the time of purchase; the receipt trail stays in Vergo while the coded transactions import into CosmoLex.
How often should we import card activity into CosmoLex?
Whatever matches your close cadence — weekly or monthly are common. Vergo generates the export on demand, so the cadence is your choice.
