Does Vadim-iCity publish a public API?
No. Vadim-iCity is an on-premise financial system serving Canadian municipalities, now held under CentralSquare, and there is no published API documentation for it. CentralSquare does run a developer portal, but the product lines documented there are not Vadim. Searching the vendor site for Vadim technical reference returns nothing usable. Anything claiming a Vadim integration on record traces back to resellers rather than to vendor documentation.
Why does on-premise deployment matter here?
Vadim-iCity typically runs inside the municipality's own environment. Even where an interface exists for a specific project, it is not something a cloud expense platform can connect to as a product — it is an IT project with the town's own network and change-control process attached. That is a large reason file import remains the standard route for this class of system.
What does this mean for a municipal card program?
No card platform can offer Vadim-iCity a supported live sync. Purchasing-card charges reach the ledger keyed by finance staff against funds, departments and account codes, or loaded from a file in a layout the system accepts. The manual version puts all of that coding work on the finance office at the end of the cycle, working from a statement and email threads.
How does Vergo work with Vadim-iCity?
Vergo pushes the coding out to the people making the purchases. A public works or recreation employee taps their card, codes the purchase to the fund, department and account in the app, and photographs the receipt. Approvals route to the department head and finance inside Vergo. At close, Vergo generates a custom-built CSV export matched to the import format Vadim-iCity expects, and finance loads one reviewed batch.
Vergo does not claim an API sync with Vadim-iCity, because no such interface is published. What it provides is the file path with the manual work removed from it.
What should a municipality assume when evaluating tools?
Assume file-based integration and evaluate on that basis. Ask any vendor claiming a Vadim sync to show the vendor documentation behind it. If CentralSquare publishes developer documentation covering Vadim in future, the position is worth rechecking; today it does not.
What does this cost a finance office today?
Time, and timeliness. Coding a month of purchasing-card activity by hand means the general ledger reflects card spend weeks after it happened, so department heads review budget-to-actual reports that are missing recent purchases. It also concentrates knowledge in one or two staff members who can decode the statement, which is a continuity risk for a small municipal finance office.
What does a defensible p-card file look like?
Each transaction should carry the fund, department and account coding, the business purpose, the receipt image, and the name and timestamp of the approver. When all of that is captured at the point of purchase and travels with the batch into Vadim-iCity, an audit sample is answered from the record rather than from memory. Reconstructing it later is where public-sector card programs tend to fail review.
How does Vergo handle multiple departments?
Cards, limits and approval routes are set per department while the export remains a single reviewed batch for the finance office. Departments keep control over their own spending decisions without producing several separate month-end processes.
Does Vadim-iCity have a documented API?
No. No API documentation is published for Vadim-iCity. CentralSquare's developer portal covers other product lines, and the vendor site carries no Vadim technical reference.
Does Vadim-iCity run on-premise?
Yes, it is typically deployed inside the municipality's own environment, which is another reason file import rather than a cloud sync is the standard route.
How does Vergo get p-card spend into Vadim-iCity?
Staff code purchases to fund, department and account code in Vergo with receipts attached, and Vergo produces a CSV export matched to the system's import format for finance to load.
Is there an audit trail for each transaction?
Yes. Coding, receipt image, approver and timestamps are recorded in Vergo and carried with the batch that finance imports.
