Does BEAMS publish a public API?
No. BEAMS does not publish a public API. There are no developer pages or published endpoints for third-party software to connect to — the only material integration surface BEAMS documents is its import/export capability. What the system does support is file import: Creditor, Debtor, and General Journal invoices are importable into BEAMS.
What does that mean for expense automation on a building job?
No card or expense platform can claim a live API sync with BEAMS. Card activity enters BEAMS the way the system accepts outside data — as an import. For an Australian builder, the practical question is whether that import file shows up already coded to jobs and cost structures, or whether the office rebuilds it from a raw card statement each month.
How does Vergo work with BEAMS without an API?
Vergo provides custom-built CSV exports matched to BEAMS' import format. Site and office spend on Vergo cards is captured as it happens; receipts are photographed at the point of purchase, and each transaction is coded in Vergo to the accounts and job coding your BEAMS setup uses. The export is mapped to your import layout once, then produced the same way every cycle — aligned with the Creditor and General Journal import paths BEAMS supports.
Is a file import good enough for a construction accounts team?
Yes, because the import was never the bottleneck. The time sinks are chasing receipts from site, coding each charge to the right job, and reconciling statements. Vergo does that work upstream, so the BEAMS import becomes a few minutes of controlled routine on an on-premise system built around exactly this kind of file handling. Since BEAMS publishes no API, an import-ready file is the honest ceiling of automation for any platform — Vergo's difference is that the file arrives finished.
Could BEAMS release an API later?
If BEAMS ever publishes a public API, Vergo can evaluate it. Until then, treat any claim of a direct BEAMS sync with caution — the vendor documents an import/export surface, not developer access. The workable automation today follows the paths BEAMS actually supports: Creditor, Debtor, and General Journal invoice imports. Vergo's role is everything upstream of that import — issuing the cards, capturing receipts on site, applying job coding as spend lands, and recording approvals — so the file your accounts team brings into BEAMS is complete on arrival.
Does BEAMS have a public API?
No. BEAMS publishes no public API or developer documentation; its documented integration surface is file import and export.
What can be imported into BEAMS?
BEAMS supports importing Creditor, Debtor, and General Journal invoices — the file paths Vergo's custom CSV exports are matched to.
Can card spend be coded to jobs before import?
Yes. Transactions are coded in Vergo to your accounts and job coding first, so the file arrives ready for BEAMS.
Does BEAMS being on-premise matter?
No — the import runs in your BEAMS environment as usual. Vergo produces the file; your accounts team imports it.
