Why is file import the route into Multiview?
Multiview publishes no public API documentation, and its on-premise deployment means each installation sits behind the customer's own infrastructure. No outside card platform can push transactions in directly, so transactions arrive the way Multiview supports: as an imported file. The work is producing a file its importer accepts cleanly.
What does the manual workflow look like?
Without tooling, month-end means downloading the card statement, coding each charge in a spreadsheet to the right account and department, chasing receipts by email, reshaping columns to match Multiview's importer, uploading, and correcting rejects. Every mismatch between the statement layout and the importer layout is another round of cleanup.
How does Vergo automate the import?
Vergo removes every step except the final upload. Spend on Vergo cards is captured in real time; cardholders code each transaction — account, department or class, category — from their phone and attach the receipt at purchase. Vergo then generates a custom-built CSV export matched to Multiview's import format: the columns and values its importer expects, not a generic bank download. Your accountant downloads the file and imports it into Multiview. No re-keying, no mapping session — and no claim of an API sync, because Multiview publishes none and the matched file does not need one.
What lands in the ledger?
Each transaction arrives as an importable line — date, amount, vendor, and the coding applied in Vergo — while receipts remain attached to the transaction in Vergo as the audit trail. The general ledger ends up exactly where it should, from an upload that takes minutes.
What does setup look like?
Setup is one-time. Vergo matches its export to the import format your Multiview installation expects, and your account structure — departments, classes, categories — is mirrored in Vergo so cardholders code spend against names your ledger already uses. Because Multiview runs on-premise and publishes no API, nothing is installed on your infrastructure and nothing is needed from Multiview: the file is the whole interface. From then on the rhythm is fixed — spend on Vergo cards, coding and receipts captured at purchase, matched CSV downloaded and imported on your cadence. Reconcile the first import line by line; once the file shape is proven against your importer, the card-statement portion of month-end collapses to a few minutes of upload and review.
The end state is a repeatable close: every card charge arrives in Multiview coded and receipt-backed, and the only remaining manual step — the upload — is one your team controls and can verify in minutes.
Can I connect a card feed directly to Multiview?
No — Multiview publishes no public API. Card transactions come in by file import, and Vergo's custom CSV exports are matched to Multiview's import format.
Do transactions arrive already coded?
Yes. Coding happens in Vergo at the point of spend, so the export carries finished entries — account, department, category — rather than raw statement lines.
How often should we import?
Whenever fits your close — weekly or month-end are typical. The export is available on demand and the import itself takes minutes.
Where do receipts live?
Attached to each transaction in Vergo, searchable for audit, while the CSV carries the transaction data into Multiview.
