How to automate expense management in QuickBooks Desktop

Key takeaways

• QuickBooks Desktop brings card transactions in through Bank Feeds (Direct Connect or Web Connect) and matches them to entries or creates new ones.
• Receipt Management, in Plus, Accountant and Enterprise editions, accepts receipts by email; the mobile app uploads, and matching happens on the desktop.
• A credit card charge carries an account on the Expenses tab and, for job costing, a customer:job on each line.
• Vergo proposes those values from your history, chases receipts by text and writes credit card charges through the Desktop SDK.

Where should you go next?

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

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

1. Connect QuickBooks Desktop. Vergo connects through Intuit's public QuickBooks Desktop SDK, reads your chart of accounts, and writes each coded card transaction as a credit card charge.
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 line. Vergo proposes the expense account and, where you job cost, the customer:job for each receipt line.
5. Write to QuickBooks. Confirmed transactions become credit card charges, so Bank Feeds finds a match instead of creating a blank entry.

What does QuickBooks Desktop need on each card transaction?

• Credit card account: the card the charge belongs to.
• Expense account: on the Expenses tab.
• Customer:job: Intuit's job costing guidance is to assign every expense line to a customer or job so job reports are complete.
• Memo and receipt: for the audit trail.

Where do Bank Feeds stop and automation start?

Bank Feeds bring the transactions in and rules can rename and categorise them by payee. Receipt Management reads the vendor, amount and card details from an emailed receipt. Neither decides which job a purchase belongs to, and neither splits one receipt across two accounts. Vergo reads the receipt itself, line by line, and predicts the coding from what was actually bought — the expense account and customer:job — not just the vendor name on the header.

A note on QuickBooks Desktop editions

Intuit has stopped selling new subscriptions to QuickBooks Desktop Pro Plus, Premier Plus and Mac Plus in the US, while existing subscribers can keep renewing. QuickBooks Enterprise is not affected. Vergo works with the Desktop products through the same SDK, so the answer does not change if you move to Enterprise, and it would not change if you moved to QuickBooks Online either.

A practical example

A landscaping company's crew lead buys mulch and a trimmer head on one card at a garden centre. Vergo texts for the receipt, proposes the materials account with the customer's job for the mulch and the equipment repairs account for the trimmer head, and explains the split from earlier purchases. The office manager confirms, and a credit card charge with two lines is written to QuickBooks Desktop.

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. In QuickBooks Desktop, that history is your past credit card charges and the customer:jobs they carried. 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, by amount, or by project — or skip approval flows entirely and let policy flags catch only what breaks a rule.