Does NewViews publish a public API?
No. NewViews, the on-premise accounting system from Q.W. Page Associates, does not publish a public API. Its manual describes exporting and importing data through the program's own interface — there is no documented developer endpoint, no API reference, and no published integration toolkit for third-party software to connect to programmatically.
That is not unusual for on-premise accounting software. NewViews keeps its data local, and the supported way to move data in and out is through the file export and import functions built into the product itself.
What does no API mean for expense automation?
It means no expense platform — Vergo included — can claim a live, real-time sync into NewViews. Any vendor implying an automatic API connection to NewViews is overstating what the system allows. The honest picture: transactions have to reach NewViews as files, in the structure NewViews accepts on import.
The practical cost of doing that by hand is familiar to anyone closing the books on NewViews today: downloading card statements, retyping or reshaping them into an importable layout, and keying account distributions line by line. The bottleneck is not NewViews — it is preparing clean, coded data for it.
How does Vergo work with NewViews without an API?
Vergo takes the file-based path and automates everything up to the import step. Vergo issues the corporate cards, so every transaction is captured at the point of spend — with the receipt, the account coding, and the cardholder attached. Vergo then generates a custom-built CSV export matched to the import format NewViews expects, so the file loads through NewViews' own import routine without manual reshaping.
Your team's workflow becomes: spend happens on Vergo cards, coding happens in Vergo as it occurs, and at close you export a file that NewViews accepts as-is. No retyping, no reformatting, no chasing receipts at month-end.
Is a CSV workflow reliable enough for month-end close?
Yes, when the file is built for the target system rather than as a generic dump. A generic card-statement download still needs manual rework; a purpose-built export does not. Because Vergo's export is matched to NewViews' import structure, the file is the finished product — every line already carries its coding, and the import is a load step, not a data-entry step.
For an on-premise system like NewViews, this is also the architecture-appropriate answer: your ledger stays local and under your control, and the only thing that moves is a clean file you review before importing.
Does NewViews have a public API for integrations?
No. NewViews does not publish a public API. Its documentation covers GUI-driven export and import only, so third-party software cannot connect to it programmatically.
How does Vergo connect to NewViews?
Vergo provides custom-built CSV exports matched to the import format NewViews expects. Card transactions are captured and coded in Vergo, then exported as a file that loads through NewViews' own import routine.
Can card transactions sync to NewViews automatically?
Not via an API — NewViews does not offer one. The working automation path is a file-based one: Vergo automates the capture, coding, and export, and NewViews imports the finished file.
Does the CSV workflow change how NewViews is deployed?
No. NewViews runs on-premise and stays that way. Nothing connects into your NewViews installation; you import a file you have reviewed, keeping the ledger fully under your control.
