How do credit card transactions get into TurboCASH?
By file import. TurboCASH publishes no public API and no schema documentation, so there is no card feed or direct sync to configure. The supported route for outside data is TurboCASH's import routine, which means the real work is producing a file in the layout it accepts.
What does the manual workflow look like?
Without automation: download a card statement, open it in a spreadsheet, rearrange columns to match what TurboCASH's import expects, correct date and amount formats, add account allocations line by line, then import and fix whatever rejects. On an on-premise system every failed import is time at the machine where TurboCASH is installed.
How does Vergo automate this?
1. Spend happens on Vergo corporate cards; each transaction is captured with merchant, date, amount, and category as it occurs.
2. Cardholders attach receipts and coding from their phone, so transactions are fully documented before you reconcile.
3. Vergo generates a custom-built CSV export matched to the import format TurboCASH expects — no column surgery in a spreadsheet.
4. You download the file and run TurboCASH's import. The batch loads cleanly, allocated and ready to reconcile.
How often should you run the import?
On your reconciliation cadence — most TurboCASH users run it monthly, some weekly. Vergo's export covers any date range on demand, so the import always matches the period you are closing.
Why is a file better than waiting for an integration?
Because there is nothing to wait for: TurboCASH has never published an API, and its on-premise deployment makes unofficial connections risky and unsupported. A pre-matched CSV delivers the practical win — zero re-keying, complete receipts, consistent allocations — through the import tooling TurboCASH actually ships.
Can I set up a direct card feed into TurboCASH?
No. TurboCASH publishes no public API, so no card platform can feed it directly. Transactions come in through its file import routine.
What file format does TurboCASH need?
A file matching the column layout its import routine expects. Vergo's CSV exports are custom-matched to that format, so they load without manual editing.
Where do receipts live in this workflow?
Receipts are captured in Vergo at the point of spend and stored there. The CSV carries the transaction data into TurboCASH; the receipt archive stays searchable in Vergo.
Does this work with an on-premise TurboCASH install?
Yes — that is the point. A CSV file works regardless of where TurboCASH runs, with no connection to the local installation required.
