What are the options for getting card transactions into Ibcos Gold?
Ibcos Gold does not publish a public API, so there is no direct feed a card platform can push transactions through. That leaves two realistic paths: keying card spend into Gold by hand, or importing a file. Manual entry means someone retypes every line — date, supplier, nominal code, VAT — from statements and a folder of receipts. A file import does the same posting in one batch, and the real question becomes how good the file is before it reaches Gold.
Why do generic card exports fail in Gold?
A raw statement export from a bank or generic card provider is not an Ibcos Gold import file. It has no nominal coding, no VAT treatment, and columns Gold does not recognise, so your accounts team ends up rebuilding it in a spreadsheet every month — which is manual entry with extra steps. Because Gold runs on-premise at the dealership, there is also no cloud shortcut around the import; the file has to be right.
How does the Vergo-to-Gold workflow run?
Vergo moves all the work upstream of the import:
1. Spend happens on Vergo cards. Each transaction appears in Vergo the moment it settles, and the cardholder is prompted for the receipt from their phone.
2. Coding happens in Vergo, not in a spreadsheet. Transactions are coded to the structure your Gold setup uses — supplier, nominal code, department or depot as your chart is organised — with rules doing the repetitive lines automatically.
3. Vergo generates the import file. This is the key difference: the CSV export is custom-built to match the import format your Ibcos Gold system expects, not a generic template you have to rework.
4. Your team imports the batch into Gold. The file loads like any other batch import, on your schedule, on your server. Reconciliation is a review, not a data-entry job.
How long does month-end take this way?
The parts that used to consume days — chasing receipts, coding lines, reshaping files — happen continuously during the month at the point of spend. What remains at month-end is generating the export and running one import in Gold, which takes minutes. The dealership keeps full control of what posts and when, which suits on-premise Gold sites well.
Is this an API integration?
No, and we will not describe it as one. Ibcos Gold has no public API, so any working automation is file-based. Vergo's approach is simply to make the file-based path genuinely automatic everywhere except the final import click.
Can Vergo push transactions into Ibcos Gold automatically?
Not via an API — Gold does not publish one. Vergo instead generates a custom-built CSV export matched to your Gold system's import format, and your team loads it as a standard batch import. Everything before that step is automatic.
What does the import file contain?
Coded card transactions: date, supplier, amount, VAT treatment, and the nominal coding your Gold chart uses — captured and coded in Vergo during the month, so the file needs no rework before import.
Does this work with an on-premise Gold installation?
Yes. Because the workflow ends in a file your team imports locally, it works regardless of where Gold runs. On-premise deployment is exactly why file import is the right path for Gold.
How is this better than importing a bank statement export?
A bank export is uncoded and in the wrong shape, so someone rebuilds it every month. Vergo's export arrives already coded and already in the format Gold expects — the spreadsheet step disappears.
