QuickBooks Online bank rules: how to auto-categorize correctly.
Bank rules are the automation layer on top of the bank feed in QuickBooks Online: set conditions — bank text, amount, money-in or money-out — and a rule auto-categorizes matching transactions as they arrive in the For Review queue, and can optionally auto-add them straight to the books. Used well, rules are the single biggest time-saver a feed offers. Set carelessly, they miscategorize at scale, and an auto-add rule does it silently. Below: what rules actually do, how to set them up so they help instead of hurt, and when a ProAdvisor should design them — or untangle the ones that went wrong.
QuickBooks Online bank rules automatically categorize the transactions your bank feed imports, so recurring charges are already coded to the right account when you open the For Review queue.
A rule is a set of conditions — the bank’s description text contains or is a phrase, the amount equals or falls in a range, the transaction is money-in or money-out — plus the category, payee, and class to apply when a transaction matches. Rules run in a priority order from top to bottom, and the first match wins, so ordering specific rules above broad ones matters. A rule can simply pre-fill a category for you to accept, or it can auto-add the transaction straight into the books. Rules are the biggest time-saver a feed offers — but a mis-set rule miscategorizes every matching transaction, and an auto-add rule does it silently. Keep conditions specific, order them deliberately, prove a rule before trusting auto-add, and keep reviewing the queue.
What QuickBooks Online bank rules do.
The moving parts of the feature, in the order you meet them — from the category a rule applies through to the limit of what a rule can promise.
Part 01 · Rules auto-categorize imported transactions
A bank rule tells QuickBooks Online how to code transactions the feed brings into the For Review queue. Instead of categorizing a recurring vendor charge by hand every time, a rule assigns the right account — and optionally a payee and class — the moment a matching transaction arrives. This is where most of a feed’s time savings come from: the routine transactions are already handled before you open the queue.
Part 02 · Conditions decide what a rule matches
Every rule is built from conditions you set. You choose whether the rule applies to money-in or money-out, then add conditions on the bank’s description text (contains or is a phrase) and on the amount (equals, or within a range). You also decide whether a transaction must meet all conditions or any of them. Specific conditions are the difference between a rule that catches exactly what you intend and one that over-reaches.
Part 03 · Rules run in a priority order
Rules apply from top to bottom in a priority list, and the first rule that matches an imported transaction is the one that wins. When more than one rule could apply, order decides the outcome. Putting narrow, specific rules above broad catch-all rules keeps a general rule from claiming a transaction a precise rule was meant to handle — the order is part of the design, not an afterthought.
Part 04 · Rules can categorize, or auto-add
A rule can do one of two things to a matching transaction. It can categorize it — pre-fill the account so the transaction sits in For Review already coded, waiting for you to accept it. Or it can auto-add it — post it straight into the register with no review. Categorize keeps a human in the loop; auto-add trades that review for speed, which is safe only when the rule is genuinely reliable.
Part 05 · Rules act on the For Review queue
Bank rules operate on transactions imported by the feed into For Review — they don’t reach back and re-code history, and they don’t fire on transactions you key in manually. A new or edited rule applies going forward as fresh transactions arrive; QuickBooks can also re-apply rules to items already sitting in For Review. Rules are a feed companion: no feed, nothing for the rules to act on.
The limit · What rules do not do: replace review
A bank rule speeds categorization — it does not guarantee the categorization is right. A rule applies exactly the logic you gave it, including any mistake in that logic, to every matching transaction. A mis-set rule miscategorizes at scale, and an auto-add rule does it silently, with nothing in For Review to flag it. Treat rules as fast defaults you still verify, not as a substitute for reviewing the books.
How to set up bank rules that work.
Six steps, in order. The first three build a rule that matches what you intend; the rest are the discipline that keeps a rule set accurate instead of letting it quietly drift.
- 1
Start from a transaction you actually have
The cleanest way to build a rule is from a real imported transaction in For Review: open it, choose to create a rule, and QuickBooks pre-fills the bank text and amount for you. Starting from a transaction you can see — rather than guessing the bank’s description from memory — means the conditions match how the charge really appears in the feed.
- 2
Make conditions specific, not loose
Set conditions tight enough to catch only what you mean. Use a distinctive part of the bank’s description with contains, pin the money-in or money-out direction, and add an amount condition where the charge is consistent. A rule keyed on a generic word will grab unrelated transactions; a rule keyed on the vendor’s unique text won’t. Specific is safe; loose is how a rule quietly miscategorizes.
- 3
Order rules from specific to general
Because the first matching rule wins, put your narrow, exception rules above your broad ones. If a specific vendor charge needs a particular category but a general rule would otherwise sweep it into a catch-all, the specific rule has to sit higher in priority. Review the order whenever you add a rule, so a new broad rule doesn’t start out-ranking the precise ones below it.
- 4
Enable auto-add only when a rule is proven
Leave new rules on categorize, not auto-add, at first. Watch the rule handle real transactions in For Review for a while; once you’re confident it matches only what it should and codes it correctly, you can switch reliable ones to auto-add. Reserve auto-add for predictable, unambiguous charges — never for anything where a wrong category would matter and you’d want a chance to catch it.
- 5
Revisit rules when bank text changes
Banks change how they describe transactions — a processor rebrands, a card reissues, a description format shifts — and a rule keyed on the old text silently stops matching. If a vendor you had a rule for suddenly shows up uncategorized in For Review, check whether the bank text changed and update the rule’s conditions. Rules aren’t set-and-forget; they need a look when the feed’s data shifts.
- 6
Keep reviewing the queue and the register
Rules speed the work; they don’t end it. Keep working For Review so you catch transactions a rule miscoded or one no rule covered, and periodically scan the register for categories that look wrong — especially in accounts an auto-add rule feeds. A rule applying the wrong category to dozens of transactions is far cheaper to catch early than to untangle after a quarter of bad data.
When a ProAdvisor should help.
Designing rules across many vendors and accounts
A few simple rules are easy; a rule set that stays accurate across dozens of vendors, multiple accounts, and a real priority order takes judgment — specific enough to be safe, broad enough to be useful, ordered so nothing collides. Getting that architecture right from the start is exactly what a ProAdvisor sets up cleanly, and it’s far cheaper than rebuilding it after rules have tangled.
Untangling a miscategorized backlog
When mis-set rules — especially auto-add rules — have coded transactions wrong across weeks or months, the cleanup is real work: finding what was miscategorized, re-coding it correctly without creating duplicates, and then fixing the rules so it stops recurring. Sorting that out by hand, in the right order, is precisely where a ProAdvisor saves you the most time and prevents the most downstream damage.
When rules feed a file that’s already behind
If rules have been running into a file that’s already miscategorized, unreconciled, or full of duplicates, the rules aren’t the first thing to fix — the books are. That’s a file review and a fixed-fee cleanup, after which the rules are rebuilt properly so the file stays clean. A rule that simply won’t fire or apply is a separate troubleshooting matter — see the help page below.
A QuickBooks ProAdvisor designs the rules inside your own books.
Building one rule takes a minute; building a rule set that stays accurate across many vendors and accounts is the real work. A QuickBooks ProAdvisor designs rules from your real transactions, keeps the conditions specific enough to be safe, orders them by priority so a broad rule never steals what a precise one should handle, and decides which are reliable enough to auto-add. Where mis-set rules have miscategorized transactions across weeks or months, we untangle the backlog, re-code what’s wrong without creating duplicates, and rebuild the rules so it stops recurring — against a written scope, inside your own QuickBooks Online file.
What people ask about QuickBooks Online bank rules.
How do bank rules work in QuickBooks Online?
A bank rule is a set of conditions plus the action to take when an imported transaction matches them. You set whether the rule applies to money-in or money-out, add conditions on the bank’s description text and the amount, then choose the category, payee, and class to apply. When a transaction in For Review meets the conditions, the rule either pre-fills its category for you to accept or, if set to auto-add, posts it straight into the register.
What conditions can a QuickBooks Online bank rule use?
A rule matches on the bank’s description text — whether it contains or is a phrase — on the amount (equals or within a range), and on the transaction direction (money-in or money-out). You decide whether a transaction must meet all of the conditions or any of them. Keeping conditions specific is what stops a rule from catching transactions it was never meant to.
What does rule priority mean, and why does the order matter?
Bank rules run from top to bottom, and the first rule that matches an imported transaction is the one applied — later rules don’t get a turn at it. So if a broad rule sits above a specific one, the broad rule can grab a transaction the specific rule was meant to handle. Ordering rules from most specific to most general keeps each transaction handled by the rule you actually intended.
Should I let bank rules auto-add transactions automatically?
Only for rules you’ve proven. Auto-add posts matching transactions into the books without review, which saves real time on predictable, unambiguous charges — but it removes the step that catches anomalies, and a too-broad auto-add rule miscategorizes at scale and posts those errors silently. Leave new rules on categorize, confirm they behave for a while, and switch only reliable ones to auto-add while still checking the register.
A bank rule isn’t firing or is miscategorizing — is that covered here?
Not on this page. This is a feature explainer for how bank rules work and how to set them up well. If a rule won’t fire, applies the wrong category, or stopped matching after the bank changed its description text, that’s a troubleshooting problem — our separate bank rules not working reference covers the likely causes in order and a step-by-step self-fix.
Can you set up bank rules in my QuickBooks Online file?
Yes — that’s operational work we do inside your own books: designing rules from your real transactions, setting specific conditions, ordering them by priority so nothing collides, and deciding which are safe to auto-add. We start with a free file review, then a focused rule build is one fixed fee, scoped in writing, or a bookkeeping cleanup ($1,200–$15,000+) if mis-set rules have already miscategorized the books. An Intuit account or login issue stays with Intuit.
Can a bad bank rule mess up my books?
Yes — that’s the real risk. A rule applies exactly the logic you gave it to every matching transaction, so a wrong category or a too-broad condition gets repeated at scale, and an auto-add rule does it silently with nothing in For Review to flag it. That’s why you keep new rules on categorize until proven, order them specific-to-general, and keep reviewing the queue and register rather than trusting that the rules caught everything correctly.