QuickBooks Online Bank Rules: Setup and Best Practices

TL;DR Bank rules in QuickBooks Online look at transactions waiting for review, whether they came from a bank feed or an uploaded file, and fill in details such as the payee and category when the conditions match. A good rule is narrow: it applies to one direction (money in or money out), one or a few accounts, and matches on a distinctive piece of the description, not a generic word. Order matters because only one rule applies to a transaction, so put specific rules above broad ones. Use automatic adding sparingly, only for transactions that are always the same, and review a sample of auto-added items each month. Rules are only as good as the descriptions they read, so clean, consistent imports make them much more reliable.

If you import bank transactions into QuickBooks Online, either through a bank feed or by uploading statement files, you'll quickly find yourself categorising the same things over and over: the same software subscription, the same rent, the same card processor deposits. Bank rules exist to do that work for you.

Used well, rules turn a monthly categorising session into a quick review. Used badly, they quietly put transactions in the wrong accounts, and you only find out when your profit and loss looks odd at year end. This guide explains how rules work, how to design them, the settings that cause trouble, a worked set of rules for a small business, and how to keep them healthy over time. QuickBooks changes its screens and menu names fairly often, so we describe features rather than exact click paths.

How bank rules work

When transactions arrive in QuickBooks Online through a bank connection or a file upload, they wait in a review list before they become part of your books. Bank rules run against that list.

Each rule has three parts:

1. Scope: whether it applies to money in or money out, and which bank or card accounts it covers.
2. Conditions: tests on the transaction, typically on the description or bank text and the amount, such as "description contains" a word or "amount is greater than" a value. You can usually require all conditions or any condition.
3. Actions: what to fill in when it matches, such as the transaction type, payee, category, and, on plans that support them, class or location. You can often split a transaction across categories by percentage or amount, and add a memo.

There's also an option to have matching transactions added to your books automatically, rather than just pre-filled for you to confirm.

Two behaviours are worth remembering:

• Only one rule applies to a transaction. If two rules match, the one higher in the list wins. Rule order is effectively priority.
• Rules apply to transactions waiting for review. Changing a rule doesn't go back and fix transactions you've already added to your books.

Before you write rules: get clean descriptions

Rules match text. If the same supplier appears with three different descriptions, you'll need three conditions, or the rule will miss some.

Bank feed descriptions are whatever the bank sends. Uploaded files are whatever your CSV or converted statement contains. If you upload converted PDF statements, keep descriptions exactly as they appear on the statement rather than shortening them by hand, because a rule written against the original text should keep matching month after month.

A few things help:

• Consistent imports. If you sometimes upload a CSV and sometimes rely on the feed, check that descriptions look similar in both. Our guide to QuickBooks Online CSV import errors covers the file format side.
• No duplicates. Rules will happily categorise a duplicated transaction twice. Choose a cut-over date between uploads and the feed. Our guide to QuickBooks duplicate transactions after import explains the clean-up.
• A look at the raw text. Before writing a rule, filter the review list for the supplier and read several descriptions. Pick the part that's stable, such as the merchant name, and ignore parts that change, such as reference numbers or dates.

If you're converting PDF statements for upload, SheetStatement keeps the original description text and checks balances before export, so the file you upload is complete. The free plan covers 3 pages a month.

Designing good rules

Make conditions specific

"Description contains AMAZON" sounds sensible, but Amazon purchases could be office supplies, stock, software, personal items or a marketplace payout coming in. A broad rule will put all of them in one account.

Better options:

• Split by direction: one rule for money out, a different one for money in.
• Add an amount condition when a supplier charges a fixed price, for example a subscription that's always the same amount.
• Match on a more distinctive part of the text if the bank provides one, such as a specific service name.
• Leave genuinely mixed suppliers without a rule, and categorise them by hand with the receipt in front of you.

Limit the accounts

If a rule is meant for your business checking account, don't let it apply to every account. A rule written for a card might misfire on a savings account with a similar description.

Set a payee

Filling in the payee as well as the category makes reports much more useful. You can see spending by vendor, and it helps when you later need to check contractor payments or vendor totals.

Use splits carefully

Some costs genuinely need splitting, such as a phone bill that's partly business, or a loan payment that's part principal and part interest. Splits by percentage are convenient for fixed allocations. For loan payments, the interest portion usually changes every month, so a fixed split will drift away from the lender's statement. It's often better to categorise the payment to the loan account and record interest from the lender's statement separately, or to adjust the split monthly. Ask your accountant how they want loans handled.

Automatic adding: when to use it

The option to add matching transactions automatically saves time, but it removes your chance to look at each one.

Reasonable candidates:

• A fixed monthly rent payment to the same landlord for the same amount.
• Bank service charges with a consistent description.
• A software subscription at a fixed price.

Poor candidates:

• Anything where the category depends on what was bought.
• Transfers between your own accounts, which need matching on both sides rather than a category.
• Deposits from payment processors, which usually need to be broken into gross sales and fees. See our guides to reconciling Stripe payouts and Square payouts.
• Owner draws and contributions, where getting the account wrong affects equity.

Even for good candidates, include an amount condition where you can. If the rent goes up, a rule with an exact amount stops matching, and the transaction lands in review for you to notice, which is what you want.

Rule order and conflicts

Because only one rule applies, order matters. Keep specific rules above general ones. For example:

1. Money out, description contains "PAYROLL FEE", category Payroll fees.
2. Money out, description contains "PAYROLL", category Wages (or better, matched to payroll entries).

If these were the other way round, the fee would be categorised as wages.

When you create a rule, ask yourself whether any existing rule could also match. A quick test is to search the review list for the condition text and see what else it catches.

Rules versus matching existing entries

Rules are for transactions that don't already exist in your books. Many bank transactions do already exist in some form: an invoice you sent and the customer paid, a bill you entered and then paid, a cheque you wrote, or a payroll run recorded by a payroll app. For those, the right action in the review list is to match the bank line to the existing entry, not to categorise it again.

This matters because a rule that categorises a customer payment directly to income creates a second record of the same sale. The invoice stays open, accounts receivable stays too high, and income is counted twice. The same happens on the expense side if a rule categorises a payment that should settle an existing bill.

A practical way to think about it:

• Use matching when you created the transaction in QuickBooks first: invoices, bills, cheques, recorded payments, and entries made by connected apps such as payroll or sales platforms.
• Use rules for transactions that only exist because they hit the bank: bank fees, card subscriptions, direct debits you don't enter as bills, and small recurring purchases.
• Categorise by hand anything that's genuinely mixed, unusual or large.

If your business enters bills for most suppliers, you may need very few expense rules. If you run everything from the bank feed, rules will do much more of the work. Either approach can be fine, as long as each transaction is recorded once. If you're unsure which way your books are set up, look at whether accounts payable and accounts receivable have balances; if they do, matching is part of your workflow.

Transfers and credit card payments

Rules aren't a good fit for transfers between your own accounts. A transfer from checking to savings, or a payment from checking to a business credit card, should be recorded once as a transfer, matched to the corresponding entry on the other account. If a rule categorises the checking side as an expense, your expenses are overstated and the card account won't reconcile.

In the review list, treat transfers by matching or recording them as transfers, and leave them out of your rules. Our guide to importing credit card transactions into QuickBooks Online shows how card accounts and payments fit together.

A worked example: rules for a small design studio

A two-person design studio imports transactions from a business checking account and a business credit card. After reviewing three months of descriptions, the bookkeeper sets up these rules, listed in priority order:

Notes on the choices:

• Rules 1 and 3 have exact amounts and auto-add. If the lease or software price changes, the transaction falls into review instead of being added at the old amount.
• Rule 4 has no amount because storage costs vary with usage, so it pre-fills but doesn't auto-add.
• Rule 6 doesn't categorise client payments at all, because those should be matched to open invoices, not booked straight to income. It's there only to remind the reviewer. Some bookkeepers wouldn't create it.
• There's no Amazon rule. The studio buys both office supplies and props for shoots, so those are categorised by hand.

Each month, the bookkeeper scans the auto-added transactions for the period, a quick filter by payee, to confirm nothing unexpected went through.

Testing a rule before trusting it

When you create a new rule, don't switch on auto-add straight away:

1. Create it without automatic adding.
2. Look at which transactions in the review list it pre-fills.
3. Check a few against receipts.
4. After a month or two of correct matches, consider auto-add if it's a fixed transaction.

If a rule is matching things it shouldn't, tighten the conditions rather than deleting it. Add the direction, an account limit, or a more specific text match.

Keeping rules healthy

Rules collect over time, and old ones can cause trouble. Every quarter, or at year end:

• Review the list. Delete rules for suppliers you no longer use.
• Check auto-add rules. Make sure the amounts and payees are still right.
• Look at your profit and loss by account for anything surprising. A category that suddenly doubled may have a rule pulling in transactions it shouldn't.
• Reconcile every account. Rules don't replace reconciliation. Our guide to reconciling a bank statement in Excel explains the principle, and QuickBooks has its own reconcile tool for each account.

If you work for several clients, keep a simple document of each client's rules and why they exist. Some versions of QuickBooks Online let you export and import rules, which can help when setting up similar clients, but always review imported rules against the new client's accounts.

Fixing transactions a rule got wrong

Because rules only affect transactions in review, fixing a bad rule doesn't fix what it already added. To clean up:

1. Correct the rule first, so the problem stops.
2. Find affected transactions, for example by filtering the account register by payee or searching for the description.
3. Change the category on each, or undo them from the reviewed list so they go back for review, depending on what your version allows.
4. Re-check the bank reconciliation for the affected months if any were already reconciled.

If a large number of transactions are affected across a period, talk to your accountant before mass changes, especially if the period has already been reported.

Common problems

A rule isn't applying. Check the direction, the account list and the exact text. Banks sometimes add extra spaces or change capitalisation. Also check whether a higher rule is matching first.

Transactions are going to the wrong category. A broader rule above a specific one is the usual cause. Reorder them.

Auto-added duplicates. If the same transactions arrived twice, from a feed and an upload, rules will add both. Fix the import overlap, then remove duplicates. See our guide to QuickBooks bank feed missing transactions for when the feed has gaps.

Rules on uploaded files behave differently. Descriptions in a CSV can differ from feed descriptions. Write rules against whatever source you use most, or include both variations.

Get clean statement data into QuickBooks

If you're uploading older months from PDF statements, convert them with SheetStatement, check the balances, and export a file QuickBooks can import. The free plan covers 3 pages a month; paid plans are $9, $19 and $39 a month. Then let your bank rules do the routine categorising.

FAQ

Do QuickBooks Online bank rules work on uploaded files?

Rules apply to transactions waiting for review, which includes transactions brought in by uploading a file as well as those from a bank feed. Descriptions may differ between the two, so check your conditions match.

Can two rules apply to the same transaction?

No. Only one rule applies, and the one higher in the list takes priority. Put specific rules above general ones.

Should I use automatic adding?

Only for transactions that are always the same, ideally with an exact amount condition. Review auto-added transactions regularly.

Does editing a rule fix past transactions?

No. Rules affect transactions in review. Transactions already added need to be corrected separately.

Should I create rules for transfers?

Generally not. Transfers between your own accounts and credit card payments should be matched or recorded as transfers so both accounts stay correct.

How much does SheetStatement cost?

The free plan includes 3 pages a month. Paid plans are Starter at $9 a month, Pro at $19 and Business at $39.