What are the options for getting card transactions into NewViews?
NewViews is an on-premise accounting system with no public API, so there is no bank-feed-style connection to switch on. Card activity reaches the ledger one of two ways: keyed in manually as transactions, or brought in as a file through NewViews' import function. For any meaningful card volume, the file route is the one that scales.
The quality of that route depends entirely on the file. A raw statement download from a card provider is not import-ready — it lacks account distributions, uses the bank's column layout, and mixes in rows NewViews has no use for. Someone has to turn it into the structure NewViews accepts, and that reshaping is where month-end time goes.
How does the manual file workflow look?
Without automation, the cycle each close is: download the card statement, open it in a spreadsheet, map each line to the right account, add any job or department detail your books require, reorder and rename columns to match your import layout, save, and run the import in NewViews. Then reconcile against receipts collected separately. Every step is repeated every month, and every step is a chance for a keying error that surfaces later as a reconciliation break.
How does Vergo automate the import?
Vergo replaces the preparation work rather than the import itself. It works like this:
1. Spend happens on Vergo cards. Vergo issues the corporate cards, so every transaction is captured the moment it occurs — no waiting for a statement.
2. Coding happens at the point of spend. Cardholders attach receipts and coding from their phone; controllers set rules so recurring spend codes itself. By close, the data is already clean.
3. Vergo generates the import file. Vergo produces a custom-built CSV export matched to the import format NewViews expects — your column layout, your account structure — so the file loads without manual reshaping.
4. You import and review in NewViews. The file runs through NewViews' own import routine. Because you review the file before loading it, nothing touches your books that you have not seen.
Why match the export to NewViews specifically?
Generic exports move the work; matched exports remove it. If the file out of your expense platform still needs a spreadsheet session before NewViews will take it, you have automated only the download. Vergo's export is built against the structure NewViews imports, which makes the monthly cycle a two-step: export from Vergo, import into NewViews. For an on-premise system, that is also the right trust model — your ledger stays local, and the file is the only thing that moves.
Can NewViews pull a live credit card feed?
No. NewViews has no public API, so there is no live card feed to connect. Card transactions come in through NewViews' file import function, and Vergo automates preparing that file.
What does Vergo's export file for NewViews contain?
Coded card transactions — each line with its amount, date, merchant, and the account coding applied in Vergo — structured in the import format NewViews expects, so it loads without reformatting.
Do I still have to code transactions in NewViews after importing?
No. Coding happens in Vergo at the point of spend, with rules for recurring merchants. The file arrives in NewViews already distributed to the right accounts.
Does this work with an on-premise NewViews installation?
Yes. Nothing connects into your installation. Vergo produces a file, you review it, and you import it through NewViews as usual — the ledger stays entirely on your systems.
