On this page Jump to section
A bank rule in QuickBooks Online can post a transaction before anyone on the bookkeeping team sees it. That speed is useful for a recurring software subscription and dangerous for a client whose bank description also matches a loan payment. The review below treats every rule as a small automation with an owner, a scope, and an audit trail. It is written for a VA preparing or inheriting rules in a client file, not for a business owner experimenting in a trial company.
Why a bank rule needs review before it runs
QuickBooks Online applies a bank rule when a downloaded transaction meets the conditions in the rule. The application can assign a category, payee, class, location, or split, and it can post the transaction automatically when auto-add is on. Intuit's help page for bank rules warns that auto-add removes the chance to review a transaction before it enters the books. A rule that looked correct in a test can still misclassify a new vendor whose bank text shares a word with an existing payee. The review exists to catch that before the posting, not after the client's profit and loss report changes.
The risk is not only a wrong account. A rule can attach a class that belongs to another service line, assign a customer that distorts job costing, or split an amount across categories the client never approved. Those errors survive a bank reconciliation because the bank side still matches. They surface later in a sales tax report, a project margin review, or a tax preparer's questions. A VA who reviews the rule itself, rather than only the transactions, catches the problem at the source.
Read the match conditions as a scope statement
The conditions decide which transactions the rule can touch. Start with the direction, money in or money out, and the bank and credit card accounts the rule applies to. Then read each condition for description or bank text and for amount, because a condition broader than the client's actual pattern will pull in unrelated activity. Write the intended population in one sentence before you approve the rule. If you cannot state the population, the conditions are not ready.
Test the narrowest condition first. A rule that matches a vendor name should not also match a generic word such as transfer, fee, or payment unless the client has confirmed that every such transaction belongs in the same place. Check whether the condition uses contains, does not contain, or an amount comparison, and confirm the logic with a transaction that should fail. A rule that cannot reject a near match is a rule that will eventually mispost one.
Check the posting action and the auto-add decision
The action is where a rule becomes an accounting entry. Confirm the transaction type, the category or account, and any payee, class, location, or customer the rule will attach. If the rule splits a transaction, verify that the percentages or amounts add to the full transaction and that each line uses an account the client expects. Read the split against a real invoice or receipt before enabling the rule, because a split that balances arithmetically can still be wrong in substance.
Auto-add deserves a separate decision. With auto-add on, the rule posts a downloaded transaction without review, which is appropriate only for a stable, low-risk pattern the client has explicitly accepted. Keep auto-add off during the first cycle and compare the rule's suggestions with a manual review. Record who approved auto-add, for which rule, and on what date. When the pattern changes, turn auto-add off before editing anything else.
Check rule order and overlapping coverage
QuickBooks Online applies only one rule to a transaction and uses the order in the rules list to decide which one wins. That makes priority part of the control, not a cosmetic setting. Two rules that both match a coffee shop purchase will produce different categories depending on which sits higher. Review the full list in order and look for conditions that overlap on the same bank text or amount range.
A conflict review is easier when each rule has a short purpose statement in its name. Names such as "Client A software subscriptions, auto-add off" tell the next reviewer what the rule is for and what it may do. When two rules overlap, either narrow the conditions or disable the lower one until the client decides. Do not leave the order unexplained, because the next person to edit the list may reverse the outcome without touching either rule.
Test against unreviewed transactions and record the result
The Test Rule control shows which unreviewed transactions the current conditions would catch. Use it before saving a new rule and again after any edit to the conditions. Save a screenshot or export of the test result with the date, the rule name, and the person who ran it. If the test returns nothing and the client expects matches, fix the conditions instead of assuming the bank feed is clean. A rule that has never matched anything has not been tested.
After the rule runs, sample the posted transactions rather than trusting the count. Open several and confirm the account, class, payee, and split match the source document. Note any transaction the rule skipped that should have matched, because a false negative leaves manual work and can hide a missing rule. Keep the sample and the notes with the client's rule-change record. The evidence should let a second reviewer reach the same conclusion without asking you.
Record approval and set a review cadence
A rule change is a change to how the client's books are produced, so it needs an owner and an approval. Record the client's request, the rule name, the conditions, the action, the auto-add setting, and the date the change took effect. If the client approved by email, file the message with the rule record. A verbal approval is still approval, but write it down the same day so the record does not depend on memory.
Review rules on a schedule that matches the client's activity. A business with frequent new vendors needs a monthly check, while a stable service business may need only a quarterly one. Add a review after any bank account change, chart of accounts update, or migration, because old conditions may point at accounts that no longer exist. Link the rule record to the bank feed rules review and the bank rule conflict audit so the next reviewer follows the same standard. The goal is a rule set the team can explain, not a longer list of automations.
Intuit's bank rules help article is the primary reference for how conditions, priority, and auto-add behave in the product. Read it before a client conversation so the review describes the actual setting rather than a habit carried over from another file. The article also confirms that QuickBooks applies one rule per transaction, which is the reason a priority review belongs in every rule change. Keep the reference link in the workpaper so the client can see the product behavior the review relied on.
Related resources
Compare the service fit on the QuickBooks VA services page, then use the free consultation form to map the first handoff. For platform context, review QuickBooks Online.


