Xero Bank Rules: The Complete Setup Guide for Australian Small Business

What Xero Bank Rules Actually Do

Xero bank rules are pattern-matching shortcuts that tell Xero how to handle a recurring bank transaction automatically. When a transaction comes through the bank feed that matches the conditions you set, Xero suggests the contact, the account code, the GST treatment, and any tracking categories before you click reconcile. You still confirm the match, but the keystrokes drop from a dozen to one.

If your business has even modest transaction volume, bank rules are the single biggest lever you have inside Xero for shrinking reconciliation time. A small business processing 200 bank transactions a month can typically rule-match 60 to 80 percent of them with a properly built rule set. That turns a half-day monthly bookkeeping task into a 30-minute one.

The catch is that bank rules also encode your assumptions about GST, account codes, and contacts. A bad rule will silently miscategorise dozens of transactions before anyone notices. This guide covers how to set rules up properly, what each rule type does, and where automation needs to stop.

The Three Types of Bank Rules in Xero

Xero supports three rule types. Pick the right one for the transaction pattern you are trying to automate.

Spend Money Rules

For money going out of your account that is not paying an existing bill. Use these for direct debits, subscription charges, bank fees, merchant fees, fuel cards, and most operating expenses where you do not raise a supplier bill first. This is the most common rule type for most small businesses.

Receive Money Rules

For money coming into your account that is not paying an existing invoice. Use these for interest received, rebates, government grants, ATO refunds, and platform payouts like Stripe, Square, or Shopify gross deposits where the platform fees come out separately.

Transfer Money Rules

For movements between your own accounts. Use these for transfers between trading and savings accounts, credit card payments from your operating account, or sweeps to a tax savings account. These rules do not affect your P&L, but getting them right keeps your cash position clean.

How to Create a Bank Rule in Xero

The cleanest way to build a rule is from an actual transaction in your bank feed. The workflow:

1. Open your bank account in Xero and find a representative transaction on the reconcile screen.
2. Click the Options menu next to the transaction and select Create Rule.
3. Xero pre-fills the conditions from the transaction. Tighten or loosen them as needed.
4. Choose the contact (an existing contact or a new one Xero will create).
5. Choose the account code and GST treatment.
6. Set any tracking categories if you use them.
7. Decide whether the rule should match automatically or only suggest.
8. Save the rule and run it against the current bank feed.

The rule will then apply to any future transaction that matches the conditions, plus any unreconciled historical transactions if you choose to apply it retrospectively.

Designing Conditions That Match Reliably

The most common reason rules misfire is conditions that are either too loose or too tight. A rule that matches any text containing "Optus" will catch your mobile bill, but it will also catch a refund or a different Optus product line. A rule that matches the exact text "OPTUS MOBILE 123456 04 APR" will not match next month when the reference number changes.

The sweet spot is usually two or three conditions that lock in the merchant and the rough amount range, while leaving date and reference flexible.

Useful condition patterns:

• Contains for merchant names that always include a stable keyword (for example "STRIPE", "AMAZON AWS", "GOOGLE WORKSPACE")
• Starts with for transactions that always lead with the same payment processor prefix (for example "EFT", "DIRECT DEBIT")
• Equals only when the description is genuinely identical every time, which is rare
• Amount range for fees that vary slightly each month (for example merchant fees that scale with sales)

Always test the rule against your last three months of bank data before you let it run automatically. The Xero rule editor lets you preview matches before saving.

Automatic Match Versus Suggestion

When you create a rule, you can set it to either suggest the match (which still requires you to click reconcile) or apply automatically. The right choice depends on the transaction.

Automatic matching is appropriate for:

• Bank fees and merchant fees that are always the same code and GST treatment
• Recurring subscriptions with fixed amounts (Xero, Slack, Adobe, Microsoft 365)
• Internal transfers between your own accounts
• Interest received on savings accounts

Suggestion-only matching is safer for:

• Any transaction where the GST treatment can vary (a "STRIPE" deposit could be domestic GST-applicable revenue or GST-free international revenue)
• Transactions with mixed account codes (an "OFFICEWORKS" charge could be stationery, computer equipment over the depreciation threshold, or staff amenities)
• Any merchant where you sometimes get a refund (the rule catches the spend pattern but should not auto-categorise the refund the same way)

A good rule of thumb: if the rule could ever silently miscategorise the transaction, leave it on suggestion only.

Common Mistakes to Avoid

• Building rules before chart of accounts cleanup: If your account codes are still messy, your rules will lock the mess in. Clean the chart first, then build rules.
• One rule per merchant when the merchant has multiple transaction types: Stripe payouts, Stripe fees, and Stripe refunds need separate rules with different conditions.
• Forgetting GST on insurance and government charges: Insurance premiums often include both GST and stamp duty (which is GST-free). A blanket rule will overclaim GST.
• Auto-matching capital purchases: A "BUNNINGS" rule that codes everything to repairs and maintenance will quietly send a $4,000 tool purchase to the P&L instead of fixed assets.
• Never reviewing rules: Suppliers change names, processors change reference formats, and your business changes its supplier mix. Review your rules every six months and retire any that have not matched in 90 days.

Where SortBooks Fits

SortBooks layers on top of Xero and watches every rule-matched transaction for anomalies. If a "STRIPE" rule normally codes to domestic sales but a payout pattern looks like an international refund, we flag it before it locks into your BAS. If a "BUNNINGS" rule has been quietly absorbing capital purchases, we surface it ahead of year-end.

For most Australian small businesses on Xero, the right setup in 2026 is a well-built bank rule set for the high-volume recurring transactions, plus an AI bookkeeper like SortBooks to catch the edge cases the rules cannot reason about. You get fast reconciliation and accurate BAS without giving up control.

If you would like to see what your bank rules look like through SortBooks, you can connect a free trial in under five minutes.