Does Adminsoft Accounts publish a public API?
No. Adminsoft Accounts has no public API. It is an on-premise application built on Visual FoxPro, and even its underlying DBF database structure is not openly published — documentation for it is sold rather than posted. What Adminsoft does support is file import: CSV, TXT, XLS, and ODS formats, plus an import for Sage Line 50 data.
That import capability is the honest integration surface. Any tool that wants to move data into Adminsoft does it through files, not through an API connection.
What does that mean for expense automation?
It means no card or expense platform can offer a live API sync with Adminsoft Accounts, and any claim of one should be treated with suspicion. The realistic division of labor is: an expense platform automates everything up to the file — capturing card transactions, matching receipts, coding each line to the right nominal account — and Adminsoft's import brings the finished file into the books.
For a small business running Adminsoft, the pain this removes is the retyping. Card statements do not code themselves; someone has to enter each line and decide where it posts. When that work happens at the point of spend instead, the bookkeeping side of card activity shrinks to running an import.
How does Vergo work with Adminsoft Accounts?
Vergo issues corporate cards and captures every transaction as it happens, with the receipt attached by the cardholder and the coding applied in Vergo. Vergo then provides custom-built CSV exports matched to Adminsoft's import format, so the file loads through Adminsoft's standard import without column re-mapping or spreadsheet cleanup first.
Because Adminsoft runs on-premise, this file-based approach also fits how the system is actually deployed: the import runs on the machine where Adminsoft lives, on the schedule the bookkeeper chooses. There is no API sync to configure because there is no API — and Vergo does not pretend otherwise.
Which import format should you use?
Adminsoft accepts several file types — CSV, TXT, XLS, ODS — and CSV is the dependable choice for transaction data: plain, unambiguous, and matched exactly by Vergo's export. The result is a repeatable monthly routine: export from Vergo, import into Adminsoft, check the batch total, post.
Does Adminsoft Accounts have an API for integrations?
No. Adminsoft Accounts publishes no public API. Its integration surface is file import — CSV, TXT, XLS, and ODS formats, plus a Sage Line 50 import.
How does Vergo get card transactions into Adminsoft?
Vergo provides custom-built CSV exports matched to Adminsoft's import format. Transactions are captured, receipt-matched, and coded in Vergo, then loaded through Adminsoft's standard file import.
Can I connect Adminsoft Accounts to a bank or card feed directly?
Adminsoft does not offer an API for live feeds. File import is the supported route, which is why Vergo automates the capture and coding and delivers an import-ready file.
Does the on-premise deployment cause problems for this workflow?
No. File import suits on-premise software well: the export is generated in Vergo and imported on the machine running Adminsoft, on whatever schedule the bookkeeper prefers.
