Does Harris Local Government MSI publish a public API?
No. Harris Local Government MSI, a municipal fund accounting system from Harris (a Constellation Software company), has no published public API. There is no developer subdomain and no public API documentation for MSI. If any interface exists for specific partner arrangements, it is not published — which, for a third-party platform deciding what it can honestly offer a municipality, amounts to the same thing: no standard programmatic connection to MSI is available.
What does that mean for card expense automation?
No expense platform can post transactions into MSI directly or claim a live sync with it. MSI typically runs on-premise in the municipality's own environment, and the way data enters it from outside is the way municipal finance offices already move data: file import.
The automation question therefore shifts upstream. In a fund accounting environment, the real workload of a card program is coding every charge to the right fund, department, and account, collecting receipts for the audit file, and turning bank data into a file the system will accept. All of that can be automated before MSI is ever involved.
How does Vergo work with MSI without an API?
Vergo issues corporate cards and captures every transaction as it happens. Cardholders attach receipts from their phones; the finance office applies fund, department, and account coding inside Vergo, with rules covering recurring vendors. Vergo then produces a custom-built CSV export matched to the import format your MSI installation expects — its columns, your chart of accounts — so the finance office imports a file that is already correct rather than rebuilding a statement spreadsheet each month.
The final step stays with the finance office: import, review, post. Entries reach the ledger after review and on the office's schedule, which suits how most government finance teams want their books to work.
Is a file-based path a real integration?
It is the only honest one for MSI, and it delivers the outcome an integration is for: card spend arrives in the ledger coded and documented, without manual entry. Because Vergo maintains the export format against your import layout, the process does not degrade into hand-edited spreadsheets over time.
Could MSI open an API later?
Nothing published indicates that, and Vergo does not build on unpublished interfaces or vendor speculation. Today, custom-matched CSV export is the working automation path for Harris Local Government MSI.
Does Harris Local Government MSI have a public API?
No. MSI has no published public API — no developer portal and no public integration documentation for outside software to build against.
Can Vergo integrate with Harris Local Government MSI?
Yes, through files. Vergo provides custom-built CSV exports matched to the import format MSI expects, so coded card transactions can be imported into the ledger without re-entry.
Can card spend post into MSI automatically?
No platform can post into MSI directly, because there is no public API to post through. The automated path is a correctly formatted import file — Vergo prepares it, and the finance office runs the import.
How is fund and department coding handled?
Inside Vergo, at the transaction level. Each charge is coded to its fund, department, and account before export, and the coding travels with the transaction into the MSI import file.
