What are the ways to get card transactions into Databuild?
Databuild does not publish a public API, so a direct feed from a card program is off the table. That leaves manual entry, cleaning up a raw bank export, or importing a file that arrives already structured and coded to jobs. For a builder running multiple jobs with several cardholders, only the third option keeps cost reporting current without burying the office in data entry.
Why does the raw statement approach fall behind?
A card statement export carries no job coding and no receipts — just merchant strings and amounts. The office ends up querying site staff about purchases weeks old, and until that guesswork finishes, job cost reports in Databuild understate actual spend. Estimating feedback suffers too: if committed costs land late, the next tender is priced off stale numbers.
How does the Vergo-to-Databuild workflow run?
Vergo issues the cards and captures each transaction as it happens. The cardholder attaches the receipt and codes the purchase to its job from their phone, on site. When you are ready to book the activity, Vergo generates a custom-built CSV export matched to Databuild's import format — structured for your setup so it imports without column re-mapping. The bookkeeper brings in one file and the spend lands job-coded.
What are the steps each cycle?
1. Cardholders spend and capture receipts at the point of purchase. 2. Purchases are coded to jobs in Vergo. 3. Admins review and approve. 4. Vergo produces the Databuild-matched CSV on your cadence. 5. Import into Databuild and reconcile — totals already agree with the card program.
Does this replace Databuild's own cost reporting?
No — it feeds it. Databuild remains the system of record for job costs; Vergo's role is getting card spend there coded, receipted, and on time, through the import format Databuild expects.
Can Vergo push transactions into Databuild automatically?
No tool can — Databuild publishes no public API. Vergo instead generates custom CSV exports matched to Databuild's import format for a clean file import.
Who does the job coding, and when?
Cardholders code purchases to jobs in Vergo at the time of spend, so coding happens on site rather than being reconstructed by the office at month end.
What does the bookkeeper do each cycle?
Generate the export in Vergo, import the file into Databuild, and reconcile. Receipt-chasing and re-keying are already handled upstream.
Does this suit Australian builders on Databuild?
Yes — Databuild's market is Australian construction, and the file-based workflow fits it: coding captured on site, one structured import into Databuild on your close cadence.
