Does BS&A have an API?

Does BS&A have a public API?

No. BS&A Software does not publish a public API for its government accounting suite. There is no developer portal and no documented endpoints that a third-party application can build against.

What BS&A does support is third-party file import — the system accepts structured import files in a defined layout. That distinction matters: no API means no live sync, but a documented import layout means file-based automation is a real, supported path rather than a hack.

What does no API mean for expense automation?

Card and spend platforms that advertise an accounting sync are describing an API connection. With BS&A, that connection does not exist to be built. Any card program a municipality or agency runs alongside BS&A therefore ends in one of two places: staff re-keying transactions into the system, or a file import.

Re-keying is where finance staff time goes at month end — every charge typed in with its fund and account coding, receipts chased separately. A matched file import removes that step.

How does Vergo work with BS&A without an API?

Vergo provides custom-built CSV exports matched to BS&A's import format. Card transactions are captured in Vergo and coded there — fund, department, account, receipt attached — then exported as a file structured the way BS&A's import expects. Your team imports it into your hosted BS&A environment on whatever cadence you close.

The result is that no transaction is typed twice. The coding work happens once, in Vergo, close to the purchase; the import moves it into BS&A in minutes.

Is file import a second-class integration?

For BS&A, it is the integration. The system's supported route for outside data is the import layout, and building to that layout is more dependable than pretending an API exists. The costly part of card administration — coding each charge correctly and collecting receipts — is handled in Vergo either way; the import step itself is small.

What should a finance office check before buying spend software?

Ask the vendor one direct question: how, specifically, does your product get transactions into BS&A? If the answer implies an API sync, it is describing a connection BS&A does not offer. The credible answer names the import layout and shows the file. That is the standard Vergo builds to — an export matched to the format your BS&A environment already accepts.

Will BS&A publish an API?

BS&A Software has not published developer documentation, and we do not speculate on their roadmap. Today, matched file import is the working path, and it is the one Vergo builds to.