Does VT Transaction+ have a public API?
No. VT Software, the independent UK developer behind VT Transaction+, does not publish a public API for the product. VT Transaction+ is on-premise desktop software, and the supported way to bring external data in is file import — most notably the Universal Input Sheet, a structured spreadsheet format VT Transaction+ can ingest.
That means there is no endpoint for a spend management platform to authenticate against, no developer documentation to build to, and no direct sync any vendor can honestly claim. If a card platform tells you it connects to VT Transaction+ over an API, ask to see the documentation — VT Software has not published any.
What does no API mean for expense automation?
It rules out one specific thing: real-time, hands-off posting of card transactions into your VT Transaction+ books. Everything else about expense automation still works — cards can enforce limits, capture receipts, and collect coding at the point of spend. The only step an API would have automated is the last one: moving the finished entries into VT Transaction+.
Without an API, that last step is a file import. The practical question becomes whether the file arrives in a format VT Transaction+ accepts as-is, or whether someone on your team has to rework a generic export every month.
How does Vergo work with VT Transaction+ without an API?
Through structured CSV exports custom-built to match the import format VT Transaction+ expects. Card transactions are captured on Vergo cards, coded with the receipt attached, and then exported as a file shaped for VT Transaction+'s import — not a generic bank-style CSV you have to remap by hand.
Because VT Transaction+ runs on-premise, the import happens on the machine where your books live: download the export from Vergo, run the import, and the period's card spend lands as entries in your ledger. There is no API sync with VT Transaction+ to claim, because none exists — the custom export is the honest, working automation path.
Is a CSV import workflow good enough?
For most VT Transaction+ users, yes. The time sink in card expenses is not the import itself — it is chasing receipts, coding transactions after the fact, and reworking exports that do not match the import template. When coding and receipts are captured up front and the export already matches what VT Transaction+ ingests, the import is a short, predictable step at whatever cadence suits your close.
Does VT Transaction+ have a public API?
No. VT Software does not publish a public API for VT Transaction+. The supported route for external data is file import, including the Universal Input Sheet format.
Can any expense platform sync directly with VT Transaction+?
No platform can honestly claim a direct API sync, because there is no published API to build against. Working integrations for VT Transaction+ are file-based.
How does Vergo integrate with VT Transaction+?
Vergo generates custom-built CSV exports matched to the import format VT Transaction+ expects. You export coded card transactions from Vergo and import the file into VT Transaction+.
Does the on-premise deployment change anything?
Only where the import runs. VT Transaction+ is desktop software, so you run the file import on the machine that holds your books; Vergo prepares the file so the import itself is a single step.
