How do credit card transactions get into TrustBooks?
Through spreadsheet import. TrustBooks does not publish a public API — its knowledge base has no API documentation — so there is no direct card feed or API sync to set up. The supported route for outside transaction data is TrustBooks' spreadsheet import, and the work is in preparing a file it will accept.
What does the manual version of this look like?
Without automation, someone at the firm downloads a card statement, opens it in a spreadsheet, deletes and reorders columns, fixes date formats, adds descriptions and categories line by line, and then uploads the result. Every mismatch means a failed import or, worse, transactions that land wrong and have to be corrected inside TrustBooks.
How does Vergo automate the import?
Vergo replaces the statement-wrangling with a purpose-built export:
1. Spend happens on Vergo corporate cards, and each transaction is captured with merchant, date, amount, and category at the point of purchase.
2. Cardholders attach receipts and coding from their phone, so the data is complete before month-end.
3. Vergo generates a custom-built CSV export matched to the import format TrustBooks expects — columns, order, and formats aligned to the spreadsheet import, no manual reshaping.
4. Your bookkeeper downloads the file and runs TrustBooks' standard spreadsheet import. The transactions load cleanly.
How often should you import?
Whatever cadence your reconciliation runs on — weekly or monthly both work. Because Vergo's export is generated on demand, you can pull a file for any date range and import it when you close, rather than batching a quarter's worth of cleanup.
Why not just wait for a TrustBooks API?
Nothing is published today, and file import is the path TrustBooks itself supports. A clean CSV workflow gets a firm the practical benefit of automation — no re-keying, complete receipts, consistent coding — without depending on an integration that does not exist.
Can I connect a card feed directly to TrustBooks?
No. TrustBooks does not publish a public API, so there is no direct card feed for third parties to build on. Transactions come in through its spreadsheet import.
What format does the import file need?
The file must match the column layout TrustBooks' spreadsheet import expects. Vergo generates its CSV exports custom-matched to that format, so the file uploads without manual editing.
Do receipts come across with the transactions?
Receipts and coding are captured in Vergo at the point of spend, so the imported transactions are already documented. TrustBooks receives the transaction data via the CSV; the receipt archive lives in Vergo.
How long does the monthly import take?
With the export pre-matched to TrustBooks' format, the import itself is minutes: download the file from Vergo, upload it through TrustBooks' spreadsheet import, and review.
