What are the routes for card transactions into Nomi?
Nomi is a hosted UK accounting platform with no public API documentation, so there is no supported programmatic feed for a third-party card platform to push transactions through. Card activity reaches the books either keyed in manually or imported as a file in the structure Nomi accepts. At any real card volume, the file route is the workable one — the question is who prepares the file.
What does preparing the file manually involve?
The unautomated cycle each period: download the card statement, open it in a spreadsheet, delete the rows that do not belong, assign each transaction its category, match receipts collected separately from cardholders, rename and reorder columns to the layout your Nomi import expects, save, and import. Every step repeats every period, every retyped line is a potential reconciliation break, and the receipt chase alone can stretch the close by days.
How does Vergo automate the import into Nomi?
Vergo replaces the preparation, leaving a load-and-review step:
1. Spend happens on Vergo cards. Vergo issues the corporate cards, so every transaction is captured the moment it happens — no waiting for a statement to find out what was spent.
2. Coding happens at the point of spend. Cardholders attach receipts and coding from their phone; rules code recurring merchants automatically. By period-end the data is already clean.
3. Vergo generates the file. Vergo produces a custom-built CSV export matched to the import format Nomi expects — so it loads without a spreadsheet session first.
4. You import into Nomi. The file runs through Nomi's own import routine. You review it before loading, so nothing enters the books unseen.
Why does matching the export to Nomi matter?
Because an unmatched export only automates the download. If the file from your card provider still needs reshaping before Nomi accepts it, the manual work has been relocated, not removed. Vergo's export is built against the structure Nomi imports, which collapses the period-end cycle to two steps: export from Vergo, import into Nomi. Receipts and coding travelled with each transaction from the moment it happened, so the file is the finished product.
There is a control gain alongside the time saved. The export is reviewed before it loads, so nothing enters Nomi unseen — a checkpoint the manual statement scramble never reliably had. And because spend is visible in Vergo the day it happens rather than at statement time, whoever owns the books stops discovering surprises at period-end and starts catching them week by week, while there is still time to query a cardholder who remembers the purchase.
Can Nomi pull card transactions automatically from a card provider?
Not from third-party expense platforms via an API — Nomi publishes no public API documentation. Transactions come in through Nomi's file import, and Vergo automates preparing that file.
What does Vergo's export for Nomi contain?
Each card transaction with its date, merchant, amount, and the coding applied in Vergo, structured to match the import format Nomi expects so it loads without reformatting.
Do I still categorise transactions inside Nomi?
No. Categorisation happens in Vergo at the point of spend, with rules for recurring merchants, so lines arrive in Nomi already coded.
How often can the import run?
Whenever you choose — weekly, monthly, or ahead of VAT and reporting deadlines. Vergo generates the export on demand and you control when it loads into Nomi.
