How Bank Rules Work and Why They Go Wrong

Xero bank rules automate reconciliation by applying a predefined account code, GST treatment, and contact name to any transaction that matches a set condition, usually based on keywords in the bank narration. Once a rule triggers, the transaction is suggested for reconciliation with one click. For recurring, predictable transactions this is genuinely useful. The problem is that rules do not update themselves when the business changes.

A rule created three years ago for a supplier coded to advertising expense still runs today. If that supplier now provides IT services, every transaction from them is going to the wrong account. A rule set up with GST-free coding for an overseas subscription still applies that treatment even if the supplier has since registered for GST in Australia and now charges it. A rule built on a keyword like "BP" to capture fuel expenses will also catch any transaction from a business whose name starts with those letters, including ones that have nothing to do with fuel.

The issue is that these errors do not look like errors in the day-to-day reconciliation view. The transaction is matched and cleared. The bank account shows no outstanding items. The GST code sitting behind it is wrong, and that wrong code feeds directly into the BAS figures at the end of the quarter. By the time the GST report is run, the error has been replicated across every matching transaction for the past three months.

The Specific Problems That Compound Fastest

Wrong GST treatment is the highest-risk outcome from an outdated bank rule. If a rule applies GST-free coding to a taxable purchase, the input tax credit is not being claimed. If it applies GST-on-expenses to a purchase from a supplier who is not registered for GST, a credit is being claimed that the firm is not entitled to. Both create BAS errors that are invisible until a GST audit report is run with actual transaction-level review.

Account miscoding creates a different problem. If transactions are flowing to the wrong expense category, the client's P&L is wrong. Decisions the client makes based on their management reports are based on inaccurate data. At year-end, the accountant preparing the tax return has to recode a volume of transactions that should never have been miscoded in the first place.

A third issue specific to Xero is that rules with loose conditions match too broadly. A condition built around a partial word or a short string of characters will catch transactions it was never intended for. The rule runs silently in the background, coding unrelated transactions to the same account, and nobody notices until the account balance looks wrong at quarter end.

A Quarterly Review That Takes Twenty Minutes

The fix is not to remove bank rules. It is to review them regularly. Going to Accounting, then Bank Accounts, then Bank Rules in Xero shows every active rule in the file. A quarterly review of the top 10 to 15 most active rules takes about twenty minutes and catches most problems before they reach the BAS.

For each rule, three things are worth checking. First, does the supplier or payee still do what the rule expects? If the business relationship has changed, the account code or GST treatment likely needs to change too. Second, is the GST code still correct? If the supplier has changed their GST registration status, or if the nature of the expense has shifted, the coding needs to be updated and any affected transactions from the current quarter corrected before lodgement. Third, is the condition specific enough? A rule matching on a single two-letter string is a flag for review. Tightening the condition to a longer or more unique narration string prevents the rule from catching transactions it should not.

The Takeaway

Bank rules are a tool for efficiency, not a set-and-forget system. A rule that was correct when it was created can be wrong eighteen months later without anyone touching it. Building a brief quarterly rule review into the BAS preparation process costs less time than untangling the miscoding errors that compound when the review does not happen. For firms managing large client books in Xero, this is one of the highest-return twenty minutes in the quarterly workflow.