Uncategorized Transactions in QuickBooks Online: Cost Guide

Every bookkeeper knows the month-end pile: a few dozen lines in Uncategorized Expense or Ask My Accountant, each one waiting on a client who hasn't answered "what was this?" The categorizing takes minutes. Getting the answer takes weeks.

There are several ways to ask, and they cost very different amounts. This post lays out four of them with prices from each vendor's own page, checked in October 2026. The per-firm totals are illustrative arithmetic for a made-up two-person firm with 25 monthly clients, not measurements from a real firm.

Option 1: QuickBooks Online's built-in request feature

Start here, because you may already have it. QuickBooks Online lets you request more information on a transaction straight from the bank feed. According to Intuit's help page (updated October 27, 2026):

It's on every QuickBooks Online plan except Solopreneur.
From the bank transactions screen, you can ask for more info or a receipt, then add the request to your Requests list, or post the transaction and add the request at the same time.
You send requests by email or with a copied link, and clients reply in a client portal. Clients without a QuickBooks login sign in with a free Intuit account.
Intuit's AI (Intuit Intelligence) reviews replies and can ask follow-up questions, and you can turn that follow-up off.
Clients only get a weekly reminder unless you send them a notification from the Inbox.
Requests move through New, In progress and Complete.

Extra cost: $0 on top of the client's QuickBooks subscription.

The trade-offs are that requests live inside each client's QuickBooks company, and the conversation lives there rather than in your practice-management tool. For many firms, that's fine.

Option 2: TaxDome's Bookkeeping hub

If your firm already runs on TaxDome, its Bookkeeping hub covers the same ground. TaxDome's pricing page says the hub is included in the Pro and Business plans and lets you reclassify transactions, send them to clients for clarification and sync back to QuickBooks Online. Pro includes 120 hub connections. Business has no limit.

Cost, per seat, billed upfront:

Plan	1-year term	2-year term	Hub
Essentials (solo only)	$800/yr	$750/yr	Not included
Pro	$1,000/yr	$950/yr	120 connections
Business	$1,200/yr	$1,150/yr	Unlimited

For our illustrative two-person firm, Pro on a one-year term is $2,000 a year. That buys a whole practice-management platform, not just this feature, so it only makes sense to compare if you'd use the rest.

Option 3: Karbon, with or without automation

Karbon is a practice-management tool rather than a transaction-question tool, but a lot of firms run their client communication through it, so it often comes up. Karbon's pricing page lists Team at $59 per user per month billed annually ($79 monthly, for teams of four or more) and Business at $89 billed annually ($99 monthly). Karbon's plan cards list automatic client reminders among Business's additions over Team, but its feature table also gives per-plan reminder limits, so check the table for the plan you're considering. Karbon's API, which you need if you want an outside workflow to add notes to client records, requires Business or Enterprise.

Cost for the illustrative two-person firm on Business, billed annually: $89 × 2 × 12 = $2,136 a year.

Option 4: A self-hosted workflow

Our uncategorized transactions recipe is an n8n workflow. Every Monday it reads each client's QuickBooks Online company for expenses and deposits from the last 45 days that sit in Uncategorized Expense, Uncategorized Income or Ask My Accountant. It sends the client one plain-English list with a short answer form behind a signed link, so no login is needed. Answers go to the bookkeeper by email and, if you use Karbon, as a note on the client. It never changes anything in QuickBooks. A transaction is asked about at most three times, then the bookkeeper is told instead of the client getting a fourth email.

Cost:

QuickBooks API: Intuit's free Builder tier allows 500,000 CorePlus calls a month (CorePlus covers most reads, like the queries this recipe runs). According to Intuit's platform service fees article, calls past that cap are blocked until the next month, not billed. The recipe page estimates about 300 reads a month for 25 clients.
Email: about 200 a month for 25 clients, which fits Resend's free plan (it also has a 100-a-day cap).
n8n: the Community Edition is free if you self-host, so you pay only for the server. n8n Cloud starts at €20 a month billed annually.
Karbon: optional, and only matters if you want the note on the client record.

So for the illustrative firm, roughly $0 a month plus your server, or about €240 a year on n8n's starter cloud plan. The real cost is setup time and the fact that someone at your firm now maintains a workflow, and that won't show up in a pricing table.

The four side by side

	Built into QBO	TaxDome Pro	Karbon Business	n8n workflow
Extra cost, illustrative firm	$0	$2,000/yr	$2,136/yr	Server, or ~€240/yr cloud
Where the client answers	Intuit link or account	TaxDome portal	Karbon reminders	Signed form, no login
Writes back to QBO	Through the bank feed	Syncs to QBO	No	Never; the bookkeeper categorizes
AI involved	Yes, can be turned off	Not covered here	Not covered here	No
Main catch	Not on Solopreneur	You're buying the whole platform	Not a transaction tool by itself	You maintain it

How we tested the workflow

Our testing notes describe the setup for every recipe. We imported it into n8n 2.45.4 and ran it against a local mock server built from Intuit's, Karbon's and Resend's API documentation. The mock expires the QuickBooks token, rate-limits a call and records every request. Clients and transactions are invented, and nothing went to a real QuickBooks company or inbox. There's no AI model; every decision is a written rule. The last run passed 6 of 6 scenarios:

Q1, a Monday run. n8n refreshed an expired QuickBooks token, a rate-limited call was retried, and the paged queries produced one client email with five lines. A split transaction showed only its uncategorized line, an old transaction was left out, and a card number in a bank memo was masked.
Q2, the same week again. Nothing sent.
Q3, the form link. A tampered link got a 403. The real link showed the five questions, with the bank memo safely escaped.
Q4, the client answers three of five. The bookkeeper got an email, a Karbon note was added, the client saw a thank-you page, and QuickBooks wasn't touched. Submitting twice didn't send twice.
Q5, the next Monday. Only the two unanswered transactions and one new one were asked about.
Q6, cleanup. Lines the bookkeeper had recategorized dropped out, and after three unanswered asks the bookkeeper was told instead of the client being nagged again.

Two things broke while we built it. Our first design made the QuickBooks calls from an n8n Code node, and those can't use n8n's stored OAuth credentials. We moved the calls to HTTP Request nodes with an OAuth2 credential, which also lets n8n handle QuickBooks' one-hour access tokens and rotating refresh tokens. Then, in a full test run across our recipes, the setting BOOKKEEPER_EMAIL collided with a law-firm recipe that used the same name. It's now A2_BOOKKEEPER_EMAIL.

The workflow's node list, since we don't have screenshots yet: Mondays 8:00 (plus a manual/test tick), Clock + lookback, QBO: suspense accounts, QBO: expenses since, QBO: deposits since, Questions to ask, Emails, Send email. The answer form is a second branch: Form (GET), Render form, Send page, and Form (POST), Save answers, Answer emails, Email bookkeeper, Page only, Send result page.

Limits worth knowing

It reads expenses and deposits only, not journal entries, transfers or bank-feed items you haven't added yet.
It doesn't suggest categories.
It needs one copy per client company, because a QuickBooks credential connects to one company.

Client data

Bank memos and client answers are customer financial information. Tax preparers are covered by the FTC Safeguards Rule, and any tool in this chain, including n8n, its server, the email sender and Karbon or TaxDome, is a service provider your written information security plan should cover. The recipe masks numbers that look like Social Security or account numbers before they go into an email or note, but n8n's own execution log keeps the raw data, so that's a safety net, not a guarantee. Our post on building a WISP for a small firm goes through the rule in more detail. This is general information, not legal or professional-standards advice.

What it costs to clear uncategorized transactions in QBO