How to automate expense management in QuickBooks Online

Key takeaways

• QuickBooks Online captures receipts on every plan, and bank rules can set category, class and location for downloaded transactions.
• Rules match on bank text, so a new merchant, a split purchase or a one-off project cost still needs a person.
• Employee expense claims are an Advanced-plan feature; classes and locations need Plus (40 of them) or Advanced (unlimited).
• Vergo proposes the coding from your own history, texts for receipts and posts credit card purchases with receipts attached.

Where should you go next?

• Vergo's QuickBooks Online integration
• Get started with Vergo

How do you automate expense management in QuickBooks Online, step by step?

1. Connect QuickBooks Online. Sign in once; Vergo reads your chart of accounts through Intuit's public API. Nothing else is needed from your team.
2. Connect your existing cards. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
3. Collect receipts by text. 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.
4. Code each purchase. Vergo reads the receipt itself, line by line, and predicts the GL account from what was actually bought, not just the vendor name on the header. The reviewer sees the reason and confirms.
5. Post to QuickBooks. Each confirmed transaction posts as a credit card purchase with the receipt attached, so the bank feed match is already done.

What does QuickBooks Online need on each card purchase?

• Category: the expense account.
• Payee: the vendor.
• Class and location: on Plus and Advanced, if you track departments or sites. Whether class is set per line or per transaction is a company setting.
• Customer or project: for costs you bill back or measure by project.
• Receipt: attached to the transaction.

Where do bank rules stop and automation start?

Bank rules are the built-in automation, and they work on what the bank sends: a description and an amount. A rule can say every charge from a phone carrier goes to telephone expense. It cannot tell that one hardware store receipt is shop supplies and the next is a customer's repair parts, because it never reads the receipt. Receipt capture exists on every plan, but a captured receipt is still matched and categorised by a person. 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.

A practical example

A property services company's technician buys a water heater element and a box of fittings on one card swipe. The bank feed shows one line from the supply store. Vergo texts the technician for the receipt, reads both lines, proposes the repairs and maintenance category for the element and the supplies category for the fittings, and explains that the last four purchases from that store were split the same way. The bookkeeper confirms, and one credit card purchase with two lines and the receipt posts to QuickBooks Online.

How Vergo handles this

Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. 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. 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.