How do card transactions get into BusinessCraft?
BusinessCraft publishes no public API, so no card platform can post charges into it directly — in the cloud or on-premise. Transactions get in by hand or by file import. For a building firm with steady card volume, the import is the step worth automating.
What does keying them in cost?
Every charge entered with its job, cost centre, and account; every receipt chased from site staff and matched by hand. It lands on the accounts team at the busiest point of the month, and rushed coding is how spend ends up against the wrong job.
Why won't the bank's export file work?
The bank CSV carries date, merchant, and amount — no job, no cost centre, no account, and not in the layout BusinessCraft's import expects. Every line still needs coding and the file still needs reshaping before it can load.
What does the Vergo workflow look like?
1. Spend on Vergo cards. Site and office staff use their cards as normal.
2. Code in Vergo. Each charge is coded to its job, cost centre, and account, with the receipt captured at purchase — from the ute, not the shoebox.
3. Export. On your close cadence, run the export. Vergo produces a custom-built CSV matched to BusinessCraft's import format.
4. Import. Load the file into your BusinessCraft environment, cloud or on-premise. The layout matches, so no remapping.
What arrives in BusinessCraft?
Fully coded entries — each card transaction with the job, cost centre, and account assignments made in Vergo — so job cost reporting picks up card spend at the same detail as any keyed entry. Receipts stay attached in Vergo as the per-charge audit trail.
Who codes each charge?
Either the cardholder at purchase — from site, on their phone — or the accounts team reviewing charges in Vergo before export. Coding happens once, near the spend, and gets reviewed before the file is built rather than reconstructed from a statement at close.
What keeps the file loading cleanly?
Vergo's coding lists mirror your BusinessCraft jobs, cost centres, and accounts, and the export layout is built once against the system's import format. When jobs or the chart change, the lists change with them, so each month's export loads without a remapping step.
How much time does it save?
The export-import cycle takes minutes. The bigger win is upstream: coding at the point of purchase and receipts captured on the spot, so month end is one file instead of a statement's worth of re-keying.
Can transactions post into BusinessCraft automatically?
No. BusinessCraft has no public API, so direct posting is impossible. File import — automated by Vergo's matched export — is the working route.
What does the export file contain?
Each card transaction with its job, cost centre, and account coding, structured as a CSV matched to BusinessCraft's import format.
Does this work for on-premise BusinessCraft?
Yes. The workflow is the same for cloud and on-premise — export from Vergo, import into your environment.
Where do receipts live?
In Vergo, attached to each transaction. The coded amounts flow into BusinessCraft via the import; the receipt trail stays in Vergo for audit.
