Why is there no direct card feed into Evolution Mx?
Because Evolution Mx does not publish a public API. Integrity Software's construction accounting system takes data in through the application or through file imports — there is no endpoint a card platform can post transactions to. So every credit card programme run alongside Evolution Mx ultimately comes down to the same question: how do coded card transactions get into the ledger as a batch?
What does the manual workflow look like?
Without tooling, the month-end routine is familiar to any Evolution Mx bookkeeper: download the card statement, chase cardholders for receipts, work out which contract and cost code each line belongs to, and key the entries into Evolution Mx one at a time. On a busy card programme that is hours of re-keying, and the job costing quality depends on whoever is doing the typing remembering what a three-week-old fuel charge was for.
How does the import work with Vergo?
Vergo moves the coding upstream and turns the entry step into a single file import:
1. Capture. Card transactions appear in Vergo as they happen, and cardholders attach receipts from their phone at the point of purchase.
2. Code. Each transaction is coded in Vergo to the job and cost code it belongs to, while the purchase is still fresh — not at month end.
3. Export. Vergo produces a custom-built CSV export matched to the import format Evolution Mx expects, with your coding carried through on every line.
4. Import. Your bookkeeper loads the file into Evolution Mx as a batch. One import replaces the line-by-line keying, and the costing arrives already allocated.
Is a file import as good as an API sync?
For Evolution Mx the comparison is theoretical — no API sync exists to choose. Judged on its own terms, a structured batch import does the job well: the expensive part of card admin is the coding and re-keying, and both of those are handled before the file is ever generated. The import itself takes minutes, and it works the same whether your Evolution Mx runs in the cloud or on-premise.
Can I connect a credit card feed directly to Evolution Mx?
No. Evolution Mx publishes no public API, so there is no direct feed for any card platform to connect to. Transactions arrive by file import.
What file format does Vergo produce for Evolution Mx?
A custom-built CSV export matched to the import format Evolution Mx expects, with each transaction carrying the job and cost code coding applied in Vergo.
Who does the job costing — Vergo or Evolution Mx?
Coding happens in Vergo, close to the purchase: cardholders and your finance team allocate each transaction to a job and cost code, and that allocation travels into Evolution Mx on the import file.
How often should I run the import?
As often as suits your close routine — weekly or monthly are common. Because coding is already done in Vergo, the import step itself is quick regardless of batch size.
