What are the options for getting card transactions into VT Transaction+?
VT Transaction+ is on-premise desktop accounting software from VT Software, and it does not publish a public API. That leaves two real routes for card spend: key transactions in by hand, or import them from a file. VT Transaction+ supports structured file import — including the Universal Input Sheet, a spreadsheet layout it can ingest directly — which is the practical path for any monthly card statement of real size.
Why do generic bank exports cause rework?
A raw CSV downloaded from a bank or card portal is not shaped the way VT Transaction+ wants it. Columns are in the wrong order, dates are in the wrong format, and — most importantly — the file carries no coding: no account, no analysis, no VAT treatment. Someone has to open the file, restructure it to match the import layout, and code every line before VT Transaction+ will accept it. That rework, repeated every month, is where card-expense admin time actually goes.
How does the import work with Vergo?
Vergo replaces the rework with a custom-built export. The workflow:
1. Spend happens on Vergo cards. Each transaction is captured as it occurs, and the cardholder attaches the receipt and coding from their phone — so the data is complete before month-end, not reconstructed after it.
2. Review the period's transactions in Vergo. Finance sees every card transaction with its receipt and coding in one place and resolves anything outstanding before export.
3. Export the custom CSV. Vergo generates a structured CSV matched to the import format VT Transaction+ expects — not a generic export you have to remap. This is a deliberate design: since VT Transaction+ offers no API, the file is the integration, so Vergo builds the file properly.
4. Import into VT Transaction+. On the machine where VT Transaction+ runs, use its import routine to bring the file in. The period's card spend lands as coded entries in your books.
Is this a real integration if there's no API?
It is the only honest one. No platform can sync with VT Transaction+ over an API, because VT Software has not published one — any vendor implying otherwise is overstating. A file-based integration done properly, where the export already matches the import format and every line arrives coded with its receipt captured, removes the same manual work an API sync would. The difference is a short import step you run at your own cadence.
Can card transactions sync into VT Transaction+ automatically?
Not over an API — VT Software publishes no public API for VT Transaction+. Transactions come in by file import, which Vergo automates by generating the file in the format VT Transaction+ expects.
What file format does the Vergo export use?
A structured CSV custom-built to match VT Transaction+'s import layout, with each transaction already coded, so the import runs without remapping columns or keying data.
Do cardholders still need to keep paper receipts?
Receipts are captured digitally in Vergo at the point of spend and attached to each transaction, so coding and documentation are complete before you export.
How often should the import run?
At whatever cadence suits your close — weekly or monthly are common. Because transactions arrive in Vergo coded as they happen, the export is ready whenever you are.
