How do card transactions get into BSA Software?
BSA Software publishes no public API, so nothing can post transactions into it directly. Card spend gets in either by staff typing it in or by file import. For any card program beyond a handful of charges a month, the import is the route worth automating.
What's wrong with manual entry?
It works, at a cost. A clerk takes the card statement and keys each charge into the ledger with its fund and account coding, then reconciles receipts separately. It is slow, it lands at the busiest point of the close, and it is where coding mistakes creep in.
Why can't I import the bank's CSV?
The bank file carries date, merchant, and amount — no fund, no account, no receipt reference, and not in the layout the system's import expects. Every line still needs coding and the file still needs reshaping, so the raw export saves little.
How does the Vergo workflow run?
1. Spend on Vergo cards. Staff use their cards as normal.
2. Code in Vergo. Each charge is coded with your fund and account structure, and the receipt is captured at purchase — not hunted down at month end.
3. Export. On your close cadence, run the export. Vergo produces a custom-built CSV matched to BSA Software's import format.
4. Import. Load the file into BSA Software. Because the layout matches, it goes in without remapping or cleanup.
What lands in the ledger?
Fully coded entries: each card transaction with the fund and account assignments made in Vergo. Receipts remain attached to their transactions in Vergo, giving the finance office a per-charge audit trail without paper.
Who does the coding?
Whoever your process assigns — the cardholder at purchase, or the finance office reviewing charges in Vergo before export. Either way the coding is done once, in one place, and reviewed before the file is built, instead of being reconstructed from a statement weeks later.
What keeps the file matching the system?
The coding lists in Vergo are set up to mirror your ledger's fund and account structure, and the export layout is built once against BSA Software's import format. When your structure changes, the lists change with it, so each export continues to load cleanly — there is no per-month remapping step.
How much time does this save?
The import itself takes minutes. The larger saving is upstream — coding at the point of purchase instead of at close, and receipts captured when the charge happens. The month-end task shrinks from re-keying a statement to running one export and one import.
Can transactions post into BSA Software automatically?
No. The vendor publishes no public API, so direct posting is impossible. File import is the supported route, and Vergo's matched export automates it.
What does Vergo's export file contain?
Each card transaction with its fund and account coding, structured as a CSV matched to BSA Software's import format.
How often should the import run?
On your close cadence — weekly or monthly both work. The export-import cycle takes minutes either way.
Do receipts import into BSA Software?
Receipts stay in Vergo, attached to each transaction as the audit trail. The coded amounts are what flow into BSA Software through the import.
