Does Black Mountain Software publish a public API?
No. Black Mountain Software does not publish a public API. A full enumeration of the vendor's site turns up no API, developer, integration, or interface page of any kind — there is simply no published surface for third-party software to connect to. Black Mountain is an on-premise system serving US local governments, and outside data enters it through the product's own import capability, not through a programmatic connection.
What does that mean for a city or district finance office?
It means no expense or card platform can truthfully claim a direct sync with Black Mountain. Card activity has to reach your books as a file import, and the real variable is the state of that file. A raw card statement carries no fund or account coding and no documentation behind the lines; an import-ready file carries all of it.
How does Vergo work with Black Mountain without an API?
Vergo provides custom-built CSV exports matched to Black Mountain's import format. Card transactions are captured in Vergo as they happen; staff attach receipts from their phones, and coding rules apply the fund and account values that mirror your Black Mountain chart. Approvals are recorded before export. The export layout is mapped to your import once at setup, and every cycle's file follows it.
Is a file workflow acceptable in a government environment?
It is often preferable. On-premise government accounting runs on controlled, reviewable file imports, and a coded CSV gives your office a checkpoint before anything touches the ledger. Vergo's role is to make sure the file arrives finished — every line coded, every receipt captured, approvals complete — so the Black Mountain import is minutes of routine rather than a re-keying project. With no public API in existence, this is the strongest automation any vendor can honestly offer Black Mountain users.
What if Black Mountain publishes an API later?
Then the picture changes, and Vergo can evaluate connecting to it. Until that happens, the accurate statement is that no interface exists, and any product describing a live Black Mountain integration is describing something the vendor has not published. What exists today, and what works, is a controlled file import fed by a finished file — one where the receipt capture, fund coding, and approvals happened upstream in Vergo, before the finance office ever opens the import screen.
Does Black Mountain Software have an API?
No. The vendor publishes no API, developer, integration, or interface documentation anywhere on its site.
Can any platform sync directly with Black Mountain?
No — with no public API, a direct sync is not possible. The working path is a file import, and Vergo builds custom CSV exports matched to Black Mountain's format.
How does fund coding get applied?
In Vergo, before export: coding rules apply the fund and account values that mirror your Black Mountain chart, so imported entries arrive coded.
Does the import work with an on-premise install?
Yes — your team runs the import inside your own environment, the same way other files enter Black Mountain.
