Expense management that works with Smokeball

Key takeaways

• Vergo reads clients and matters from Smokeball, codes transactions to them automatically, and syncs coded entries back so nothing arrives as an uncoded lump at month end.
• You do not need to change cards — Vergo connects to the corporate cards, fuel cards and personal cards your business already holds.
• AI inference codes new vendors on first sight, including assignment to the correct client and matter, without building rule libraries or keyword lists.
• Card spend, employee reimbursements and AP invoices are all coded by the same model and sync to Smokeball the same way.

How the Smokeball sync works

Vergo reads clients and matters from Smokeball, codes every expense to the right client and matter, and pushes coded entries back — so nothing arrives as an uncoded lump at month end. Transactions are ready to code the moment they happen, not when they clear, which means you see what needs attention in real time. Once transactions clear, the coded entries sync into Smokeball automatically. This structure keeps your matter-based billing accurate without manual re-entry or end-of-month reconciliation sprints. The sync handles all three payment types — card spend, reimbursements and invoices — through the same channel, so every expense that belongs to a client or matter arrives in Smokeball already assigned.

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 — and connecting your existing cards involves no card applications, no re-issuing and no banking change. This card-agnostic design means your existing banking relationships, credit limits and reward programs stay intact. If your team already carries cards that work, Vergo layers expense coding and approval on top of them without disrupting the payment rails themselves. You also avoid the onboarding friction of applying for new cards, waiting for approvals, redistributing plastic and retraining employees on new spending mechanics.

What AI-native expense management means for matter-based billing

Rules engines match text patterns; when a transaction does not match, a person codes it by hand. Vergo 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. That inference extends to clients and matters: a lunch near the courthouse on the day of a hearing gets proposed to the right matter without you having written a rule for that restaurant. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. This approach eliminates the setup tax that rules engines impose on small finance teams and keeps coding accurate even as your caseload and vendor mix change week to week.

A practical example

A paralegal uses a personal card to pay a filing fee in a new county you have never worked in before. Vergo reads the transaction description, recognizes the county clerk from context, infers the correct client and matter from the paralegal's recent activity and calendar, and proposes the coding with an explanation. The reviewer sees the reasoning, confirms it in seconds, and the expense syncs to Smokeball already attached to the matter. No rule was written for that clerk, no keyword was added to a list, and the reimbursement does not sit in a queue waiting for someone to figure out which case it belongs to. The same inference works for card spend and AP invoices.

Who runs Smokeball

Smokeball is run by small and mid-sized businesses in legal. If your finance team lives in it, the expense layer should adapt to it — not the other way round. Matter-based billing creates a specific coding burden: every expense needs a client and matter assignment, not just a GL account, and that assignment needs to happen fast enough that billing is accurate and timely. Generic expense tools treat matter coding as a custom field or an afterthought, which pushes the reconciliation work back onto your team. An expense system built to work with Smokeball treats clients and matters as first-class structure, not optional metadata.

Do reimbursements and AP invoices work with Smokeball too?

Yes — the same coding model handles card spend, employee reimbursements and AP invoices, and all three sync to Smokeball 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. Vergo captures, codes and approves invoices — payment itself stays on the rails you already use. A court reporter invoice, a paralegal mileage reimbursement and a card charge at the same expert witness service all get proposed to the correct matter by the same inference engine, reviewed in the same queue, and synced to Smokeball in the same format.

How Vergo handles this

Vergo 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. Transactions are ready to code the moment they happen — no waiting for clearing — and once they clear, they sync into your accounting or ERP software. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project — or skip approval flows entirely and let policy flags catch only what breaks a rule. 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. 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. Connecting your existing cards involves no card applications, no re-issuing and no banking change, and Vergo integrates with every ERP and accounting software.

Related questions