What is the import path into BEAMS?
BEAMS publishes no public API, so card transactions cannot be pushed in programmatically by any platform. The system's supported route for outside data is its import capability: BEAMS accepts imports of Creditor, Debtor, and General Journal invoices. Card spend therefore enters BEAMS as an import file, and the job is producing that file cleanly.
Why does a raw card statement fall short?
A card statement download has no job coding, no account distribution, and no receipts behind the lines. For a builder, that means the office codes every fuel, hardware, and subcontractor-adjacent charge by hand before anything can be imported — the exact month-end grind a card program should remove.
How does Vergo build the import file?
Vergo issues the cards for site and office staff. Receipts are photographed at the point of purchase, and coding rules apply the accounts and job coding your BEAMS setup uses as transactions land. Approvals happen in Vergo before export. At your close cadence, Vergo produces a custom-built CSV matched to BEAMS' import format, aligned with the Creditor or General Journal import path your workflow uses. The mapping is set up once, then every export follows it.
What does the routine look like?
Through the month: staff spend, snap receipts, and the coding accumulates in Vergo. At close: export the coded file and run the BEAMS import inside your on-premise environment. Entries arrive coded to jobs, so reconciliation is a check rather than a rebuild, and the receipt and approval trail stays in Vergo for audit.
What should be verified at setup?
Match the export layout to your BEAMS import screen, and align the account and job values in Vergo with your BEAMS lists. Both are one-time steps; after that, the file format is stable cycle to cycle.
What does this replace?
For most builders on BEAMS, the current process is a monthly statement reconciliation: the office collects whatever receipts made it back from site, matches them to the card statement, codes each line to a job, and keys or reshapes the lot for entry. Vergo moves all of that to the moment of purchase — the tradesperson photographs the receipt at the counter, the coding applies as the charge lands, and approval happens in the app. By the time the month closes, the work is already done; what remains is a file export and a BEAMS import measured in minutes, with job cost reports that reflect card spend without the lag.
Can Vergo post transactions straight into BEAMS?
No — BEAMS has no public API. Vergo produces custom CSV exports matched to BEAMS' import format, which your team imports.
Which BEAMS import does the file use?
BEAMS accepts Creditor, Debtor, and General Journal invoice imports; Vergo's export is matched at setup to the path your workflow uses.
Is job coding included in the file?
Yes — transactions are coded in Vergo to your accounts and job coding before export, so the entries import ready-coded.
How long does the import take each cycle?
Minutes. Once the format is mapped, export from Vergo and import into BEAMS is a short, repeatable close step.
