What is the import path into Banyon?
Banyon Data Fund Accounting publishes no public API, and its documented connectivity is file-based — the system's add-ons include purchase-card imports and ACH files. So the route for card activity is the one Banyon designed: a purchase-card file import. The work is in producing a clean file, coded the way your fund accounting requires.
Why is a raw card statement not import-ready?
A statement download from your card provider carries none of the coding a government ledger requires — no fund, no department, no account distribution — and no receipts or approvals behind the lines. Turning it into an importable file means touching every transaction, which is the month-end burden a card program should be eliminating.
How does Vergo prepare the file?
Vergo issues the cards and captures each transaction as it happens. Staff attach receipts from their phones, and coding rules apply the fund, department, and account values that mirror your Banyon chart. Approvals are recorded in Vergo before anything is exported. When you run your cycle, Vergo produces a custom-built CSV matched to Banyon's import format — mapped to your layout once at setup, then repeatable every time.
What does the month-to-month routine look like?
Cardholders spend and capture receipts; approvers clear transactions in Vergo. At close, you export the coded file and import it into Banyon on-premise, the same controlled way other files enter the system. Entries arrive coded, so reconciliation is a review rather than data entry, and the receipts and approval history remain in Vergo as the audit trail behind every line.
What should you verify at setup?
Two things: the file layout against your Banyon import screen, and the fund, department, and account values in Vergo against your Banyon lists. Both are one-time checks — after that, the export format does not drift.
How does this compare with the old process?
Most offices moving to Vergo are replacing one of two routines: keying card charges into Banyon by hand from a paper statement, or maintaining a spreadsheet that reshapes the bank download every month. Both put the coding work at month end, after the details have gone cold. With Vergo, the coding happens when the purchase happens — the person who spent the money attaches the receipt and the transaction lands against the right fund and account while it is fresh. Month end shrinks to exporting a file that is already finished and running the import Banyon was designed to accept.
Does Banyon accept card transaction imports?
Yes — purchase-card imports are among Banyon's documented file-based add-ons, and Vergo's export is built to match that import format.
Can Vergo write directly into Banyon?
No. Banyon has no public API, so no platform can write in directly. Vergo produces the import file instead.
Who runs the import?
Your team, inside your on-premise Banyon environment — a short, controlled step once the coded file is exported from Vergo.
How is audit documentation handled?
Receipts, coding history, and approvals stay attached to each transaction in Vergo, giving auditors a trail behind every imported line.
