Does Harris ERP CitySuite publish a public API?
No. Harris ERP CitySuite has no public API documentation. Whatever integration tooling exists for CitySuite lives behind the login-gated Harris Customer Hub, available to Harris customers rather than to outside software vendors. From the standpoint of a third-party platform, that is the operative fact: there is no published interface to build a standard CitySuite connection on.
CitySuite typically runs on-premise in the municipality's own environment, which reinforces the point — even beyond the absence of public documentation, there is no hosted endpoint a cloud platform could reach.
What does that mean for automating card expenses?
It means no expense platform can honestly claim a live API sync with CitySuite. Card transactions cannot post into the general ledger through a programmatic connection, because none is published. The route into an on-premise CitySuite environment is the one municipal finance offices already use for other data: file import.
That does not make automation impossible — it moves the automation upstream. The expensive part of a municipal card program is not the import click; it is coding every charge to the right fund, department, and account, collecting receipts for the audit trail, and re-shaping bank data into something the system accepts. All of that can be automated outside CitySuite.
How does Vergo work with CitySuite without an API?
Vergo issues corporate cards and captures each transaction as it happens. Cardholders attach receipts; the finance office applies fund, department, and account coding in Vergo, with rules handling recurring vendors. Vergo then produces a custom-built CSV export matched to the import format your CitySuite installation expects — your columns, your chart of accounts — so the file imports without rework.
The finance office keeps the final step: import, review, post. For many government finance teams that checkpoint is a feature, not a limitation — entries reach the ledger on the office's schedule, after review.
Is file-based integration reliable enough for a municipality?
File import is a routine, well-understood mechanism in municipal accounting, and a matched export removes its usual failure mode: format drift and hand-edited spreadsheets. Because Vergo maintains the export format against your import layout, the file that worked in January still works in December. The audit trail — receipt, approver, coding history — stays attached to every transaction in Vergo.
Could a direct connection exist someday?
Only Harris can answer that, and Vergo does not build on unpublished or speculative interfaces. Today, custom-matched CSV export is the working automation path for CitySuite, and it delivers the outcome that matters: card spend arrives in the ledger coded, documented, and without manual entry.
Does Harris ERP CitySuite have a public API?
No. CitySuite publishes no public API documentation; integration detail is behind the login-gated Harris Customer Hub. Outside platforms have no published interface to connect to.
Can Vergo integrate with Harris ERP CitySuite?
Yes, through files. Vergo provides custom-built CSV exports matched to the import format CitySuite expects, so coded card transactions can be imported without re-entry.
Can expense software post directly into CitySuite's general ledger?
No — with no public API, no platform can post into CitySuite directly. The working path is a formatted import file, which Vergo prepares and the finance office imports and reviews.
Does CitySuite being on-premise change the workflow?
Not much. The import file downloads from Vergo and is imported inside the municipality's environment, so nothing external needs to reach the on-premise system.
