What makes AP automation AI-native?
AI-native AP automation reads an invoice as a document, not a template. Vergo reads every line of a supplier invoice bound for BQE Core and infers the coding from the line descriptions and from how your team has coded that supplier and similar purchases before. An invoice in a layout nobody has mapped, from a supplier nobody has set up in BQE Core, is coded on first sight instead of falling into an exception queue, and the approver sees why each line was coded the way it was.
How does Vergo work with BQE Core?
Vergo connects directly through the public BQE Core API with OAuth 2.0 — self-serve, with nothing needed from your team or from BQE — and reads your accounts, projects, expense items and vendors. Confirmed invoices post into BQE Core as bills against the vendor, with each expense line coded to account and project, ready for the payment process your firm already runs. New vendors, accounts and projects appear in Vergo as they are created in BQE Core, so nobody codes against a stale list. The full specification lives on the BQE Core integration page.
What does BQE Core need on each supplier invoice?
- Vendor: matched to your Core vendor list.
- Expense account: on every expense line of the bill.
- Project: where the cost belongs, so it reaches project profitability.
- Reference number and dates: read from the document.
What does this look like day to day?
A geotechnical subconsultant sends an invoice for borings on a project. Vergo reads it, matches the vendor, proposes the consultant expense account and the project, and routes it to the project manager. Once approved, the bill is in BQE Core with the cost on the project, where it counts against project profitability from the day it is approved.
Does Vergo pay the invoice too?
No. Vergo captures, codes and routes each invoice for approval, then hands it to BQE Core; it does not pay suppliers. Payment stays on the rails your business already uses — your bank, your existing payment run, your current payment provider. Approvals are optional and fit how you already control spend: route by GL account, by amount or by project, or skip approval flows and let policy flags catch only what breaks a rule before it reaches BQE Core.
What changes at month end in BQE Core?
The work moves from the end of the month to the moment of spend. Because coding happens when the receipt or invoice arrives, close in BQE Core becomes a review of exceptions rather than a pile of unkeyed supplier invoices. Card spend, employee reimbursements and AP invoices run through one coding model — same coding, same review, one reconciliation against the BQE Core structure — and payment stays on the rails you already use.
Where should you go next?
- Vergo's BQE Core integration
- AP automation for engineering firms on BQE Core
- See Vergo run AP automation with BQE Core
Who runs BQE Core?
BQE Core is cloud practice-management and project-accounting software built for architecture, engineering and consulting firms. Expense entries in Core are recorded against a project and an expense item, and they carry flags for whether the cost is billable to the client and reimbursable to the employee. If your finance team lives in BQE Core, the AP automation layer should adapt to it, not the other way round.
Does Vergo do AP automation for BQE Core?
Yes. Vergo captures, codes and routes supplier invoices, then creates them in BQE Core as bills.
Does Vergo replace BQE Core?
No. BQE Core stays the system of record. Vergo sits in front of it, capturing, coding and reviewing spend before it reaches the ledger.
How is BQE Core connected?
Vergo connects directly through the public BQE Core API with OAuth 2.0 — self-serve, with nothing needed from your team or from BQE — and reads your accounts, projects, expense items and vendors.
Does Vergo pay suppliers?
No. Vergo captures, codes, approves and syncs invoices; payment stays on the rails the business already uses.
