What are your options for card transactions in AccuBuild?
AccuBuild is an on-premise construction accounting system with no public API documentation, so credit card activity gets in one of two ways: manual entry or file import. Most AccuBuild shops run the manual version — statements arrive, the office chases receipts across job sites, and each charge is coded to a job, phase, and cost code before someone types it in. A month of card activity is days of entry, and the job cost reports run behind the actual spend the whole time.
The import route removes the typing, but a raw bank export does not get you there: it carries no jobs, no cost codes, and its columns are not in AccuBuild's layout. Someone still has to code every line and reshape the file.
How does the Vergo import workflow work?
1. Field staff code at the point of spend. When a charge hits a Vergo card, the cardholder tags the job, cost code, and account in the app and photographs the receipt. Coding happens on site, the day of the purchase, by the person who made it.
2. Vergo generates the matched export. Vergo produces a custom-built CSV export in the import format AccuBuild expects — columns, layout, and cost coding arranged the way the system wants, ready to load.
3. Accounting imports and reviews. The accounting team pulls the file from Vergo, imports it into AccuBuild, and reviews the batch like any other import. Rekeying and receipt-chasing drop out of the month-end routine.
Why does coding at the point of spend matter?
Because on a job-cost system, the coding is the work. A superintendent knows which job a lumber run belongs to on the day it happens; three weeks later, the bookkeeper staring at a statement line does not. Moving the coding to the cardholder makes the data better and makes month end shorter — the file that reaches accounting is already correct, with receipts attached in Vergo if anything needs checking.
Does anything post to AccuBuild automatically?
No. AccuBuild publishes no API for outside software to post through, and Vergo does not pretend otherwise. Nothing enters AccuBuild until your accounting team imports the batch, so the ledger stays under the team's control while the collection and entry work goes away.
Can Vergo sync with AccuBuild through an API?
No — AccuBuild publishes no public API documentation, so no expense platform can offer a supported direct sync. Vergo integrates through custom CSV exports matched to AccuBuild's import format.
Who codes charges to jobs and cost codes?
The cardholders in the field, in Vergo, at the time of purchase — with receipts photographed and attached before the file reaches accounting.
What does month end look like with this workflow?
The accounting team pulls the coded CSV export from Vergo, imports it into AccuBuild, and reviews the batch. No statement reconciliation marathon, no receipt chase.
Can we review spend before it's imported?
Yes. Approvals and coding review happen in Vergo before the export is generated, and the team controls when the file is loaded into AccuBuild.
