Does BSA Software have a public API?
No. BSA Software, the Michigan-based vendor of municipal financial software, does not publish a public API. There is no developer portal and no documented endpoints, so third-party applications have no sanctioned way to read from or write to the system directly.
What does that mean for expense automation?
Spend platforms that promise a live accounting sync are describing an API connection — and with BSA Software there is no API to connect to. For a municipality running a card program alongside BSA Software, transactions end up in the system one of two ways: staff re-keying them, or a file import.
Re-keying is the default and the cost: every charge typed in with its coding, every receipt chased separately, all of it at month end. File import removes the typing — if the file is shaped the way the system's import expects.
How does Vergo work with BSA Software?
Vergo provides custom-built CSV exports matched to BSA Software's import format. Card transactions are captured and coded in Vergo — with the fund and account structure your ledger uses, receipts attached at purchase — and exported as a file ready to import. No transaction is typed twice.
Is that a real integration?
It is the integration the system supports. We state it plainly rather than dressing a file import up as a sync: BSA Software publishes no API, so a matched file import is the honest, dependable automation path. The expensive part of card administration — coding and receipts — is handled in Vergo either way, and the import itself takes minutes.
What should a municipality ask a spend vendor?
One direct question: how, exactly, do transactions get from your platform into our ledger? If the answer implies a live sync with BSA Software, it is describing a connection the vendor does not offer. The credible answer names a file, describes its layout, and shows how the coding — fund and account — gets onto every line before the file is built. That is what Vergo's matched export does.
What does the month look like in practice?
Staff spend on Vergo cards; charges are coded as they happen, receipts captured at purchase. At close, the finance office runs one export from Vergo and one import into BSA Software. The statement re-keying that used to fill the close is gone, and the ledger carries the same coded detail it would if every line had been typed by hand.
Could this change?
If BSA Software publishes developer documentation in the future, an API connection would become possible. We do not speculate on vendor roadmaps; today, matched CSV import is the working path.
Does BSA Software publish an API?
No. There is no public API, developer portal, or documented endpoints for BSA Software's municipal financial products.
How does Vergo integrate with BSA Software?
Through custom-built CSV exports matched to the system's import format. Transactions are coded in Vergo and imported into BSA Software as a file.
Can card spend sync into BSA Software in real time?
No — real-time sync requires an API the vendor does not expose. File import on your close cadence is the supported path.
Who is BSA Software for?
BSA Software serves municipal finance offices, primarily in Michigan. Vergo's export is built to carry municipal coding — fund and account — into the import file.
