What are your options for getting card transactions into JobView?
A-Systems JobView is an on-premise job-cost accounting system with no public API, so there are only two realistic paths: manual entry or file import. Most JobView shops start with manual entry — statements come in, the bookkeeper chases receipts, and each charge is coded to a job, cost code, and account before being typed in. On a busy month of card activity, that is days of work, and coding accuracy depends on memory of what each charge was for.
The file-import path replaces the typing but traditionally not the coding: you still had to build a spreadsheet in the exact layout JobView accepts. That formatting step is where generic bank exports fall down — a raw card statement export does not carry jobs or cost codes at all.
How does the Vergo import workflow work?
Vergo automates both halves — the coding and the file.
1. Cardholders code at the point of spend. When a charge hits a Vergo card, the cardholder tags it with the job, cost code, and account, and snaps the receipt from their phone. Coding happens while the purchase is fresh, not at month end.
2. Vergo assembles the import file. Vergo produces a custom-built CSV export matched to the import format JobView expects — columns, layout, and coding fields arranged the way the system wants them, not a generic bank export you have to rework.
3. The accounting team imports and reviews. Instead of rekeying every transaction, the team pulls the export from Vergo and loads it into JobView, then reviews the batch the same way they would review any imported entries.
Why not just export from the bank?
A bank export gives you dates, merchants, and amounts — none of the job costing. Every line still needs a job and cost code added by hand, and the columns still need rearranging into JobView's layout. The work moves from typing into JobView to typing into a spreadsheet, which is not much of a saving. The Vergo file arrives already coded because the cardholders did that part upfront.
What about JobView's ODBC module?
JobView offers an optional ODBC module, but it is read-only — it lets reporting tools query the database. It cannot be used to write credit card transactions in, so it is not an import path. File import remains the supported way to bring outside transactions into JobView.
Can Vergo sync with JobView through an API?
No — JobView does not publish a public API, so no expense platform can offer a true API sync. Vergo integrates through custom CSV exports matched to JobView's import format.
Who codes the transactions to jobs and cost codes?
Cardholders do, in Vergo, at the time of purchase. Each charge is tagged with a job, cost code, and account and paired with its receipt before it ever reaches the import file.
What does the accounting team have to do at month end?
Pull the CSV export from Vergo and import it into JobView, then review the batch. The rekeying and receipt-chasing steps go away because coding happened at the point of spend.
Is the export a generic bank file?
No. Vergo's export is custom-built to the format JobView expects, with the coding fields included, so it loads without manual reformatting.
