Accounting & professional services

Who Categorizes the Transactions Bank Rules Can't?

Bank rules handle repeat payees, AI suggestions get batch review, and a person owns the rest, with deposits resolved before Washington's excise return is due.

In this guide

If your firm keeps the books for Seattle-area and Washington clients, bank rules and your accounting platform's own suggestions can code the repeatable majority of each client's bank and card transactions. The work that actually takes judgment is the uncertain remainder: the transactions whose correct account depends on a fact the bank feed never carries. A useful categorization setup is not the tool that touches the most lines; it is the one that sends those judgment calls to a named person with the client context, keeps an audit trail, and never posts a client's books without review.

This guide is for firms doing write-up and monthly books for many clients. It compares deterministic bank rules, the platform's learned suggestions, and a third-party AI categorization layer. It is a decision method, not a ranked product list; where a claim comes from a vendor, we say so. For Washington clients, the deposit lines also feed an excise tax return that monthly filers owe by the 25th, which changes what gets resolved first.

What bank rules do well, and where they stop

Bank rules are deterministic: they act only when a transaction matches conditions you wrote, so they are predictable and auditable. In QuickBooks Online a rule matches on the transaction description or bank text and the amount, for money in or money out, with up to five conditions per rule, and you can create up to 2,000 rules.

Get help designing a client-bookkeeping categorization workflow for your firm

Two settings decide how much review you keep. A rule can auto-add a matching transaction, which Intuit describes as QuickBooks applying the rule and posting it immediately, or it can leave the transaction in the For Review list with a RULE badge so a person confirms it. Intuit cautions that with auto-add on you will not get a chance to review transactions before QuickBooks adds them to your books. For client work that caution is the whole point: leave rules on suggest, not auto-post.

Rules also run in order, and QuickBooks applies only one rule per transaction, so a specific rule has to sit above a general one. A rule can split one transaction across categories by percentage or amount, which handles a predictable blended charge. Xero and other platforms offer an equivalent mechanism, so the method below is platform-independent. But rules cannot decide anything that varies by facts outside the transaction line: a hardware-store charge is a repair one month and a capitalized asset the next.

Where the platform's own suggestions fit

Between rigid rules and human judgment sits the platform's own suggestion engine. QuickBooks suggests a category for each downloaded transaction as it arrives, based on how you have categorized similar transactions before, and holds it in the For Review list for you to accept or change before anything posts.

This is the probable middle: transactions that look like past ones but have no rule. Confirm them in a batch rather than auto-accept, because the suggestion is a memory of your past coding, not a verification that this month's charge is the same kind of expense. Promote a reliably correct suggestion to a rule; a payee whose suggestion is often wrong needs a human. QuickBooks can also match a downloaded transaction to one you already entered, such as a recorded bill, which is a match to confirm rather than a category to assign.

What an AI categorization layer adds, and what it still can't decide

AI categorization tools add pattern-matching that is less brittle than a single rule and broader than one platform's suggestions. Booke AI, which connects to QuickBooks Online and Xero, advertises that it learns from a client's historical categorization data to find the right category automatically and leaves uncertain items for review, and it claims transactions are categorized 80% faster. Treat those as advertised capabilities, not tested results: the vendor measures the figure, and marketing is not an independent benchmark.

Vendor comparison guides deserve the same caution. A widely linked list of the best categorization tools is published by one of the vendors it ranks, places its own product first, and repeats an unsourced claim that accounting teams lose 8 to 12 hours per week to manual categorization. Use it for feature vocabulary; it is not evidence of time saved at your firm.

What no categorizer can decide is the treatment that depends on facts the feed does not contain, such as whether a transfer is an owner draw or a loan repayment. Those need the client's answer or a written policy.

A worked example: one client's month

Here is a labeled, illustrative scenario, not a measured benchmark or a promise for any client, to show where the work concentrates. Suppose a client posts 320 bank and card transactions in a month. In a mature file, deterministic rules confidently handle the recurring, same-treatment payees, say 60% or 192 lines: rent, utilities, software subscriptions, payroll funding, and merchant fees. The platform's suggestions cover another 25% or 80 lines that resemble past coding and that a reviewer confirms in a batch. That leaves 15% or 48 lines that need a human judgment call, and of those a handful, here 9, cannot be finished until the client answers a question.

The proportions are illustrative; the shape is the point. Automation clears the volume, and the small judgment remainder is the actual work.

Illustrative exceptions from the month's 48 judgment lines
Bank line (amount)Candidate categoriesThe fact that decides itWho resolves it
AMZN Mktp US ($214.36)Office supplies, inventory (COGS), or owner personalWhat was bought and for whomBookkeeper checks the receipt; if none on file, ask the client
HOME DEPOT #1234 ($4,230.00)Repairs and maintenance, or a fixed asset to capitalizeRepair versus improvement, against the client's capitalization thresholdBookkeeper applies the client's policy; escalate if the scope is unclear
Transfer to CHK 8820 ($3,000.00)Owner draw, loan repayment, or inter-account transferThe relationship between the two accountsConfirm with the client; code to equity or the loan
SQ GREENLEAF deposit ($1,480.00)Sales income, or a transfer of owner fundsWhether it is a customer payout or the owner moving moneyMatch to the invoice or merchant statement
DD DOORDASH ($62.10)Meals, or owner personalThe business purpose of the chargeAsk the client; if personal, code to owner draw

A judgment line is done when it is coded to the right account with a memo explaining why and, where needed, a linked receipt or the client's recorded answer, not when it merely disappears from the For Review list. The nine client-question items stay in a visible ask-the-client state and must be resolved before the period closes; if an answer is still outstanding at close, the close notes the open item rather than guessing.

In Washington, the deposit lines feed the excise tax return

For Washington clients, the judgment lines on the income side carry a deadline. The Department of Revenue assigns each business a filing frequency, and monthly returns are due on the 25th of the following month; quarterly returns are due at the end of the month after the quarter and annual returns on April 15. The return reports gross income by B&O tax classification, and the department's tax classifications for common business activities note that a business with more than one activity may report under more than one; catering, for example, is listed under retailing B&O, retail sales tax and wholesaling B&O.

That changes the review order for a monthly filer. This review order is our proposed method, not a department rule. The SQ GREENLEAF deposit in the exception table cannot sit in the ask-the-client state past the 25th if it turns out to be sales income, because it belongs on that month's return; if it is a processor payout net of fees, take gross sales from the merchant statement and book the fees as an expense. Map each income account to the classification it reports under, so a bank rule that codes a recurring deposit also lands it on the right line. Clear unresolved deposits before the filing date, and keep the owner-transfer and loan questions, which do not change gross income, on the normal close schedule.

The state date is the same for a Seattle client as for any other Washington client, but many cities levy their own B&O tax, which the department does not collect. For a client that owes city B&O tax, check that city's return due dates and calendar them beside the 25th.

In Chicago, the retail return is due on the 20th

An Illinois retail client files Form ST-1, and the Illinois Department of Revenue's instructions make the return and payment due by the 20th of the month after the reporting period. For a monthly filer, the same review order therefore clears a Chicago retail client's unresolved deposits five days earlier.

How the four approaches compare

Four ways to handle categorization, and the limit of each
ApproachStrengthWhat it can't decideBest for
Manual codingFull judgment on every lineSlow, and inconsistent across staffLow volume or a messy new client
Bank rules (deterministic)Fast, consistent, auditable for repeat payeesAnything whose treatment varies by facts not in the feedRecurring, same-treatment payees
Platform suggestionsLearn from your history with no setupConfidence varies; still needs a per-line confirmThe probable middle you confirm in a batch
AI categorization layerLearns patterns across a client and flags uncertain itemsJudgment calls needing client facts; advertised accuracy is unprovenHigh-volume files, once you have verified the claims

Put the four together in order: rules on suggest for payees always coded the same way, suggestions confirmed in a batch and promoted to rules when reliable, an AI layer only when volume justifies it and its claims hold on your own files, and a person on every judgment line and client question. For where this sits among a firm's other first AI projects, see where CPA firms should start with AI.

Quick answers

Should I turn on auto-add for bank rules?

Not for client books. Auto-add posts a matching transaction immediately, so no one reviews it first. Keep rules set to suggest and confirm them in the For Review list.

Do I still need rules if the platform already suggests categories?

Yes, for payees that are always coded the same way, because a rule is deterministic and auditable. Suggestions are a memory of past coding that you confirm; promote the reliable ones to rules.

Which client transactions should a Seattle firm resolve first?

For a Washington client that files monthly, unresolved deposits that may be sales income, because the excise tax return reporting gross income by B&O classification is due on the 25th of the following month.

Are the "80% faster" and "8 to 12 hours a week" figures real?

Those are vendor figures, not independent benchmarks. Measure the time on your own files before relying on them.

Sources

Revision note · October 6, 2026: Headline simplified; the article body is unchanged.

How we research and review these guides

AI transformation with Clairvance

Put the ideas to work in your business.

We provide AI consulting and implementation for accounting and professional services firms. Bring us the process that is slowing your team down and the systems involved. We can assess the problem with you and discuss a practical implementation.

Discuss your project →

Still exploring? Explore the Workflow Opportunity Workbook →