How do card transactions get into Black Mountain?
Black Mountain Software publishes no public API — no developer or integration documentation exists at all — so card transactions cannot be pushed into the system programmatically. They enter through Black Mountain's own import capability, as a file. The choice a finance office actually faces is between building that file by hand each month and having it produced automatically, already coded.
Why not work from the card statement?
A statement download is a flat list of bank lines: no fund, no account distribution, no receipts, no approvals. Every line needs handling before it can enter a government ledger correctly. That manual conversion is where card programs quietly cost hours — and where errors creep into fund accounting.
How does Vergo produce the import file?
Vergo issues the cards and captures transactions in real time. Staff attach receipts from their phones at the point of purchase; coding rules apply the fund and account values that mirror your Black Mountain chart; approvers clear each transaction in Vergo. At close, Vergo generates a custom-built CSV matched to Black Mountain's import format. The layout is mapped to your import once at setup and stays stable from cycle to cycle.
What does the close routine look like?
Export the coded file from Vergo, review it, and import it into your on-premise Black Mountain environment like any other controlled file. Entries land coded, reconciliation becomes verification, and the receipt and approval history remains in Vergo as the audit trail behind every imported line.
What needs checking before the first run?
Confirm the export layout against your Black Mountain import screen, and confirm the fund and account values in Vergo match your Black Mountain lists exactly. Both are one-time setup checks — after that, the process is repeatable in minutes.
What does this replace for the office?
Typically, a month-end routine built around a paper or PDF statement: chasing staff for receipts, matching lines, penciling fund codes into the margin, and keying entries into Black Mountain one at a time. Vergo moves each of those steps to the moment of purchase — receipt photographed at the register, fund and account applied as the charge lands, approval recorded in the app. When the cycle closes, the finance office is reviewing a finished file rather than assembling one, and the ledger reflects card activity with a complete audit trail standing behind it in Vergo.
Can transactions post into Black Mountain automatically?
No — Black Mountain publishes no public API, so direct posting is impossible. Vergo's custom CSV export, matched to the import format, is the working path.
What coding does the file carry?
The fund and account values your team applied in Vergo, mirroring your Black Mountain chart, along with date, amount, and vendor for each line.
Who performs the import?
Your finance office, inside your on-premise Black Mountain environment — a short, reviewable step each cycle.
Where is the supporting documentation?
Receipts, coding history, and approvals stay attached to each transaction in Vergo, available for audit behind every imported entry.
