QuickBooks for Bookkeepers: The 2026 Workflow Guide

1. The bookkeeper's receipt problem at scale

Ask any bookkeeper running more than a handful of QuickBooks Online clients what eats their week and the answer is always the same: chasing documents. Practice-management surveys of small bookkeeping firms (OnboardMap and similar industry studies) put the cost somewhere between 10 and 30+ hours per month on document chase alone — missing receipts, unlabelled bank feed transactions, clients who forward five invoices and forget the other fifteen, and the endless Slack and email back-and-forth that follows.

The math is painful even when the exact numbers vary by firm. Standard bookkeeping engagements reserve a meaningful weekly block for transaction coding, reconciliation, reporting, and client follow-up. When hours leak into chasing receipts, you lose capacity that could have gone to higher-value close work or additional client capacity.

Intuit's accountant tools are very good at the parts of the workflow you can see inside QBO: the client list, the books, the reports, the close. What they do not solve by themselves is getting source documents in from messy client inboxes in the first place. That is the problem this guide is about.

2. QuickBooks Online Accountant in 2026

If you are a bookkeeper and you are not already using Intuit's accountant tools, start here. Current Intuit pages emphasize Intuit Accountant Suite Core as the free accountant offering, while QuickBooks Online Accountant is still referenced as the accountant portal many firms know. You only pay Intuit when you resell QuickBooks Online subscriptions to clients or add paid tax, payroll, or firm products. US ProAdvisor bundles and international accountant bundles can change, so confirm the exact current bundle on Intuit's sign-up page.

Here is what you actually get in 2026, and what is worth knowing:

3. Client permissions and access patterns

When a client invites you to their QBO file, do not assume every engagement needs the same access level. Some firms operate with a firm lead as primary admin; others use standard or custom roles because the client keeps ownership of subscription and user management. Primary admin is a lot of power — you can add and remove users, change subscription details, and manage sensitive settings — so it should be an intentional choice.

A few patterns we see working:

• Solo bookkeeper, full-service: Consider primary admin or a broad custom role when you are running the close, reconciling every account, coordinating with the tax preparer, and the client wants you to own the books operationally.
• Firm with junior staff: Give the firm lead the access needed for the engagement, then use RBAC to assign junior bookkeepers to the exact permission areas they need — transactions, bank feeds, reports — without giving them access to payroll or user management.
• Tax-prep-only engagement: Downgrade to standard accountant user or use QuickBooks Ledger. You don't need primary admin to run Prep for Taxes and pull workpapers — you just need the data.

Whatever permission model you pick inside QBO, remember that the receipt capture question is separate. Being admin on a client's QuickBooks file doesn't give you access to their inbox, and that is where most of the source documents actually live.

4. The 5 methods bookkeepers use to collect receipts

Across QBO-focused bookkeeping firms, receipt collection tends to fall into one of five patterns. Most firms use two or three at once, and the mix is usually driven by which clients will cooperate with which method.

For a deeper side-by-side of every capture pathway, see every receipt capture method compared.

5. The month-end receipt chase and why it breaks

Here is what month-end actually looks like for a bookkeeper with a dozen QBO clients. You open the first client's file, pull the bank feed, and start reconciling. Every uncoded transaction over some threshold needs a source document. The bank feed says $428.17 — AMZN Mktp US and you have no idea which of seven possible expense categories that is.

So you open Slack. “Hey, can you send me the Amazon receipt from March 14 for $428.17?” The client replies two days later with a screenshot of an order confirmation email that is missing the actual PDF invoice. You ask again. They forward the invoice from a personal Gmail that was never registered as a sender on their QBO file. QuickBooks bounces it. You give up and code it to “Uncategorized Expense” to keep moving.

Multiply that by 12 clients and the entire month-end window — what should be a tight 2 to 6 hours of close work per simple, bank-feed-heavy client — stretches into days of Slack archaeology. Complex clients can run two to three times that baseline. Receipts are the bottleneck, not the coding.

The fix is not “work harder at chasing.” The fix is to change the collection model so source documents flow in continuously instead of being chased at month-end — which is what the next two sections are about.

6. Workflow A: Manual email forwarding rules (the hard way)

The free, no-extra-tools version of continuous receipt capture is: set up Gmail or Outlook filters inside each client's inbox that forward invoice emails to the client's QuickBooks forwarding address. This sounds clean on a whiteboard. In practice it needs constant maintenance for four specific reasons.

7. Workflow B: Dext, Hubdoc, and Expensent compared

The alternative to manual filters is a dedicated capture tool that handles extraction and publishing. The three names you will hear most often in QBO bookkeeping circles are Dext, Hubdoc, and — in the last year or so — Expensent. They solve overlapping problems in different ways.

How to read this table. Dext and Hubdoc are the incumbent publishers: they take source documents, OCR them, and write transactions into QBO with the source attached. They are excellent at the publish step and mature. Their weakness is the collectionstep — they both depend on the client remembering to upload or forward, and firms generally rate Hubdoc's OCR below Dext's.

Expensent sits upstream. Instead of asking the client to upload receipts, you connect their inbox via OAuth and invoices Expensent identifies are surfaced in a dashboard, grouped by next action (ready to forward, sitting on a vendor portal waiting to be downloaded, ambiguous, or false positive). You approve what you want, one click forwards it to the client's QuickBooks forwarding address, and you can create a rule so future matching invoices are forwarded when the rule fires. Because forwarding happens through the connected mailbox, you are not maintaining Gmail keyword filters; the connected sender still needs to be enabled in QuickBooks Manage forwarding email. Expensent supports multiple connected inboxes per account, so a single client engagement can pull from both an accounts@ alias and a personal owner mailbox.

Expensent does not currently offer a firm-level console. The model for bookkeepers is one Expensent account per client engagement — either billed to the client, or consolidated under one account when the bookkeeper is an authorized user on the client's mailbox. Dext and Hubdoc are still the right call if a single multi-client firm console is the top requirement. If continuous inbox-level capture with 5-minute setup and one-click forwarding to QBO is the top requirement, Expensent is the cleaner fit.

Full side-by-side: Hubdoc alternatives for QBO. If you want a pure automation walkthrough for a single client file, see the full QuickBooks bill automation guide.

8. Recommended workflow for 10+ QBO clients

Here is the opinionated stack we would run today if we were a solo bookkeeper or small firm managing 10 or more QBO clients. It is designed to keep source documents flowing in continuously and to push as much repetitive work to software as possible so your billable hours go to judgement-heavy close work, not chasing.

9. Frequently Asked Questions