Expense management that works with Wave

Key takeaways

• Vergo connects to Wave and codes expenses to the right account, department and class by inference from your existing accounting structure.
• You keep the credit cards your business already holds — Vergo connects to them without card applications, re-issuing or banking changes.
• Card spend, employee reimbursements and AP invoices flow through one coding model and sync to Wave the same way.
• Transactions are ready to code the moment they happen, and sync into Wave once they clear.

How the Wave sync works

Vergo reads your chart of accounts from Wave and codes every expense to the right account, department and class, so entries arrive in Wave coded and ready to post. Transactions are ready to code the moment they happen — no waiting for clearing — and once they clear, they sync into Wave. The coding model infers the right classification from your own accounting structure and history, so new vendors are coded on first sight without manual setup. Each coding shows why it was chosen, making review faster than re-coding by hand.

Do you have to change cards?

No. Vergo does not issue cards and never asks you to switch. It connects to the cards your business already holds — corporate cards, fuel cards, personal cards used for reimbursement. Connecting your existing cards involves no card applications, no re-issuing and no banking change. This card-agnostic design means the expense management layer adapts to your existing banking relationships and workflows, not the other way around.

Who runs Wave?

Wave is run by very small businesses across industries. If your finance team lives in it, the expense layer should adapt to it — not the other way round. Small businesses often lack the capacity to manage rule libraries or keyword lists for expense coding, and they need tools that work with their existing banking setup rather than forcing platform switches or card changes.

Do reimbursements and AP invoices work with Wave too?

Yes — the same coding model handles card spend, employee reimbursements and AP invoices, and all three sync to Wave the same way. Most tools treat these as separate products with separate coding setups; the same vendor coded two different ways is a reconciliation problem you inherit. When card spend, reimbursements and invoices flow through one coding model, they use the same account structure, the same inference logic and the same review process, so reconciliation happens once instead of three times.

How Vergo handles this

Vergo integrates with Wave and every other ERP and accounting software. It reads your Wave chart of accounts and proposes the coding by inference from your own accounting structure and history — no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Card spend, employee reimbursements and AP invoices run through one coding model — same coding, same review, one reconciliation — and payment stays on the rails you already use. Transactions are ready to code the moment they happen — no waiting for clearing — and once they clear, they sync into Wave. Connecting your existing cards involves no card applications, no re-issuing and no banking change. Employees handle everything by text message — no app to download, no portal login — and Vergo chases missing receipts itself instead of waiting for a report. Approval workflows are optional and fit how you already control spend: route by GL account or by amount — or skip approval flows entirely and let policy flags catch only what breaks a rule.