Xero bank rules automatically code recurring bank statement lines so you do not have to touch them during reconciliation. There are three types: Spend Money, Receive Money, and Transfer, each handling a different direction of cash flow. Build a rule for any payment or deposit that repeats with a predictable pattern, and reconcile one-off or variable transactions by hand.
TL;DR:
- Use All conditions match when multiple fields identify a transaction, because Xero applies the first matching rule and supports up to 16 conditions per rule.
- Reserve rules for fixed rent, subscriptions, and loan payments; JAX can suggest matches for changing amounts, but a person should verify suggestions before accepting them.
- Test new or edited rules on upcoming statement lines, since changes affect future transactions only; deleted rules cannot be restored and must be rebuilt.
- DIY setup suits predictable, low volume activity, while multiple accounts, grant or location tracking, or audit exposure may warrant a Xero bookkeeper.
Table of Contents
- What Xero bank rules are and how matching works
- Step-by-step: create a bank rule from the Reconcile screen
- Best practices and optimization to avoid rule bloat
- Manage, edit, and delete rules safely
- How bank rules interact with Xero’s AI (JAX) and other reconciliation methods
- Practical examples and ready-to-use rule templates
- When to DIY and when to hire a Xero-focused bookkeeper
- Get your Xero bank rules set up right the first time
- FAQ
- Sources
What Xero bank rules are and how matching works
A bank rule watches for statement lines that match conditions you set, then applies the account code, tax rate, and contact automatically. Xero’s bank rules cover recurring or similar statement lines, which cuts down on repetitive manual entry for things like rent, loan payments, or subscription charges.
When you set conditions, you choose between “Any” and “All.” Any applies the rule when one condition matches, which is faster to set up but riskier. All requires every condition to match, and Xero recommends All for better precision.
Rule order matters because Xero checks rules from top to bottom and applies the first match it finds.
- Place narrow, specific rules above broad, general ones.
- Set conditions to “All conditions match” whenever more than one data point identifies the transaction.
- Keep in mind the technical ceiling of 16 conditions per rule, noted in Xero’s product ideas community, and split complex matching logic into separate rules once you approach it.
Step-by-step: create a bank rule from the Reconcile screen
Building a rule directly from a real transaction keeps the conditions grounded in actual bank data instead of guesswork. Here is the process Xero Central lays out:
- Open the Reconcile tab for the bank account you want to automate.
- Find a transaction that represents the pattern you want to capture, then click Options and select Create bank rule.
- Choose the rule type: Spend Money, Receive Money, or Transfer.
- Add conditions using fields like reference, amount, contact name, or narrative text.
- Decide between “Any” and “All.” Choose All when you need two or more fields to line up before the rule fires, such as a vendor name plus a fixed dollar range.
- Assign the account code, tax rate, and contact that should apply automatically.
- Set tracking categories if your chart of accounts uses them.
- Decide how to handle the remainder: allocate any leftover amount to a specific account, or leave it for manual review.
- Name the rule clearly, then save it.
- Test the rule against a handful of upcoming statement lines before trusting it broadly.
- Check where the new rule sits in your rule list and reorder it above or below others so specific conditions get checked first.
Running a quick test on real lines before moving on catches a misconfigured condition early, while the fix is still simple.
Best practices and optimization to avoid rule bloat
Rules multiply fast once you start automating, and a cluttered list becomes harder to trust. A few habits keep things manageable.
- Favor narrow conditions over broad ones. A rule that matches three specific fields is safer than one that matches a single loose keyword.
- Default to “All conditions match” whenever more than one data point can confirm the transaction. Community feedback on Xero’s product ideas forum argues that All produces safer results than the looser Any setting.
- Name every rule in a way that describes what it catches, such as “Spend: AT&T Internet $89 range,” rather than a generic label.
- Split a complicated match into two or three focused rules instead of stacking many conditions onto one.
- Keep specific rules ranked above general ones so a narrow match fires before a catch-all rule grabs the transaction.
- Review your rule list on a schedule, not just when something breaks.
Pro Tip: Pull a sample of recent reconciled transactions each quarter and check that each one was coded by the rule you expected, not a broader rule sitting above it.
Rule bloat sneaks in quietly: a business owner adds a quick rule to handle one odd transaction, forgets to name it well, and six months later nobody remembers what it was for. Periodic review is the only real fix.
Manage, edit, and delete rules safely
Editing or deleting a rule only affects transactions going forward. Xero Central confirms that changes do not retroactively alter transactions already reconciled, so fixing a rule will not reopen or recode last quarter’s books.
- Edit a rule from the Reconcile screen by selecting the transaction it applied to, or go to Accounting, then Bank accounts, then Bank Rules for a full list.
- Make your changes, test on a few upcoming lines, and recheck the rule’s position in the order.
- Delete a rule only when you are certain it is no longer needed. Deleted rules cannot be restored, so recreate one from scratch if you change your mind.
- After any edit, run a small reconciliation batch to confirm the new behavior matches what you expected.
How bank rules interact with Xero’s AI (JAX) and other reconciliation methods
Xero’s reconciliation engine, known as JAX, uses four methods: Rule, Match, Memory, and Prediction. Rules are deterministic and get applied first, before JAX suggests anything based on history or pattern recognition.
- Rely on rules for anything predictable: rent, fixed subscriptions, recurring loan payments.
- Let JAX suggest matches for transactions that vary slightly each time, such as a vendor whose invoice amount changes monthly.
- Treat JAX suggestions as a prompt to verify, not an automatic accept, since auto-reconciliation only happens when the system has high confidence.
Bank rules remain the more reliable choice for repetitive transactions because you know in advance exactly how they will be coded, while AI suggestions still need a human glance.
Practical examples and ready-to-use rule templates
A few condition patterns cover most of what shows up in a typical small business bank feed.
- Utilities: match reference contains the provider name plus an amount range, since utility bills fluctuate monthly.
- Subscription services: match reference contains the vendor name and a fixed or narrow amount, since most subscriptions charge the same fee every cycle.
- Merchant processing fees: match contact or narrative contains the processor name, since these fees post automatically and rarely need manual review.
- Payroll service fees: match reference contains your payroll provider’s name and route to the correct expense account. If you use an outside provider like Glendale Payroll Inc. for processing and tax filing, the service fee line typically posts on a predictable schedule, which makes it a clean rule candidate.
- Loan payments: match contact name plus a fixed amount, and split the remainder between principal and interest accounts if your lender reports a combined figure.
Use remainder allocation when one line needs to split across two accounts, such as a loan payment covering both principal and interest, or a bundled utility bill covering two cost centers.
When to DIY and when to hire a Xero-focused bookkeeper

Setting up rules yourself works fine when your transaction volume is low and the patterns are predictable: a handful of subscriptions, one loan payment, a consistent merchant fee. Complexity changes the math. Multiple bank accounts, tracking categories tied to grants or locations, or any exposure to an IRS audit raise the cost of a miscoded rule.
A Xero-focused bookkeeping engagement typically cleans up rule order, removes bloated or conflicting rules, and builds mappings that hold up if the books ever get reviewed. That kind of cleanup is where a bookkeeping and Xero cash coding review earns its cost back quickly.
— Tolliver Team
Get your Xero bank rules set up right the first time
We work exclusively in Xero and handle migrations, which means your rule setup starts clean instead of inheriting old QuickBooks habits. We coordinate bookkeeping and tax services closely, helping prevent miscoded rules from causing surprises at year-end.

| What we handle | Why it matters |
|---|---|
| Xero migration | No cost, so nothing blocks a clean rule setup |
| Bank rule cleanup | Fixes ordering, bloat, and conflicting matches |
| Monthly bookkeeping | Keeps rules audit-ready between filings |
If your reconciliation already feels unreliable, a bookkeeping cleanup sorts out the rule mess before it compounds. Visit our bookkeeping services page to book a consult and get your Xero setup working the way it should.
FAQ
How do you set up bank rules in Xero?
Open the Reconcile tab for your bank account, select a transaction, click Options, then Create bank rule. From there you choose the rule type, add conditions, decide between Any or All, and assign the account code and tax rate before saving, as detailed in Xero Central’s setup guide.
How do you perform a bank reconciliation?
Bank reconciliation means comparing your bank statement lines against your Xero records and confirming each one is coded correctly, either through a matching rule, a JAX suggestion, or manual entry. Our step-by-step reconciliation guide walks through the full workflow for small business owners.
How do you do a statement reconciliation in Xero specifically?
In Xero, you work through the Reconcile tab line by line, confirming each bank statement entry against a matched transaction, rule, or manual entry until the account balance ties out. Rules handle the predictable lines automatically, which leaves you to review only what’s new or unusual.
Which banks does Xero support for direct feeds?
Xero connects to a wide range of financial institutions through direct bank feeds, though exact coverage varies by bank and region. Check your specific bank’s feed availability directly within Xero when setting up a new account connection.
What is the maximum number of conditions per bank rule?
Xero’s community has reported a ceiling of 16 conditions per rule, based on discussion in the Xero product ideas forum. When a match needs more conditions than that, split the logic into two or more narrower rules instead.