What are the options for getting card transactions into CitySuite?
Harris ERP CitySuite publishes no public API, so there is no direct feed from a card program into the ledger. A municipal finance office has two real options: key transactions in manually from monthly statements, or bring them in through CitySuite's file import routines. At any meaningful card volume, the import route is the only sustainable one.
Why not just use the bank's statement export?
Because it is built for the bank. A statement download has the bank's columns, raw merchant strings, and none of the fund, department, or account coding a government ledger requires. Turning it into an importable file means re-shaping the spreadsheet, deciding coding for every line, matching receipts for the audit file, and fixing rows the import rejects — a recurring month-end project that lands on the finance office at close.
What does the import workflow look like step by step?
1. Capture transactions. Every charge is recorded with merchant, date, and amount, and a receipt image is attached for audit documentation.
2. Code each charge. Each transaction gets its fund, department, and account. Coding at transaction time — by the cardholder or approver who knows the purchase — beats reconstructing intent from a month-old statement line.
3. Build the import file. Coded transactions are arranged into the exact layout your CitySuite import routine accepts, using your chart of accounts.
4. Import into CitySuite. Inside the municipality's environment, run the import, review, and post. With a correctly formatted file, this takes minutes.
How does Vergo automate the preparation?
Vergo handles steps 1 through 3. Its corporate cards capture spend in real time; cardholders snap receipts; coding happens in Vergo with rules auto-coding recurring vendors; and approvals are recorded per transaction. Vergo then produces a custom-built CSV export matched to the import format your CitySuite installation expects. The finance office downloads a file that is already importable — no spreadsheet rework, no re-keying.
Because CitySuite runs on-premise, this file-based handoff also fits the environment: nothing external needs access to the municipal system. The import runs inside your walls, on your schedule.
What should the finance office confirm during setup?
Which CitySuite import routine and field layout your installation uses for this transaction data, and that the fund, department, and account structure in Vergo mirrors your chart. Vergo matches the export once and maintains it, so the format does not drift.
Can card transactions feed CitySuite automatically?
Not by API — CitySuite does not publish one. The automated path is a structured import file, which Vergo prepares matched to your CitySuite format; the finance office imports and posts on its own schedule.
What layout does the import file need?
The layout your CitySuite installation's import routine expects, with your actual account codes. Vergo builds the export custom to that layout so files import without rework.
Where does fund and department coding happen?
In Vergo, at the transaction level, before export. The coding — plus receipt and approval history — travels with each transaction into the file CitySuite imports.
Does on-premise deployment complicate the integration?
No. The file downloads from Vergo and imports inside the municipality's own environment, so the on-premise system never needs an external connection.
