Xero Guides / Xero Bank Rules

Xero Bank Rules: Reduce Repetitive Coding Without Losing Control

If the same rent, software subscription, bank charge or payment-platform fee is being coded manually every time, the business is spending time on work that may be partly automated.

Xero bank rules can help speed up reconciliation by suggesting how regular bank transactions should be recorded.

But bank rules are only useful when they are set up carefully. A poorly designed rule can repeat the same mistake faster and make the reports look more reliable than they really are.

What Are Xero Bank Rules?

Xero bank rules allow you to create instructions for bank transactions that follow a recognisable pattern.

The rule may use information such as the transaction description, payee or amount to suggest how the transaction should be recorded during reconciliation.

This can reduce the need to enter the same coding details repeatedly for regular transactions.

The rule does not remove the need for review. The user should still confirm that the suggested treatment is appropriate before completing the reconciliation.

Which Transactions Are Suitable For Bank Rules?

Bank rules are most useful for transactions that are regular, predictable and treated consistently.

Possible examples include:

• Recurring software subscriptions.
• Regular bank fees and charges.
• Fixed rent or utility payments.
• Payment-gateway and merchant-service fees.
• Regular loan repayments.
• Repeated payments to the same supplier.
• Consistent deposits from known payment channels.

Not every repeated transaction needs a rule. The transaction should be sufficiently consistent for the rule to work without forcing different situations into the same accounting treatment.

When A Bank Rule Should Not Be Used

Some transactions require more judgment and should not be automated too broadly.

Be careful with transactions where:

• The GST treatment may change.
• The payment may relate to different expense accounts.
• The amount includes several different items.
• The supplier provides both capital and operating items.
• The description is vague or commonly used by several merchants.
• The payment may sometimes be personal or non-business.
• The transaction needs supporting documents before coding.

When the facts vary, manual review is usually safer than a broad rule.

Why Broad Rules Create Problems

A rule may appear efficient because it matches many transactions. But a rule that is too broad may also match transactions it was never intended to handle.

For example, a rule based on one common word in the bank description may capture several unrelated suppliers.

This can result in transactions being coded to the wrong account, contact or GST treatment.

The problem may not be noticed immediately because the reconciliation screen clears quickly. The error only becomes visible later when the reports no longer make sense.

What To Check When Creating A Rule

Before saving a bank rule, check that the matching conditions are specific enough.

Review:

• The wording used in the bank transaction description.
• Whether the rule could match another supplier or payment type.
• The account code selected.
• The contact or payee used.
• The GST treatment.
• Whether the transaction should be split across more than one account.
• Whether the amount or description changes regularly.

It is better to create a narrow rule that handles one clear pattern than a broad rule that creates uncertainty.

Review The First Few Matches Carefully

After creating a new rule, review the first few transactions it matches.

This helps confirm that the rule is behaving as expected before it is used repeatedly.

Check whether:

• The correct transaction was selected.
• The coding is appropriate.
• The GST treatment is still correct.
• The description is useful.
• The rule is not matching unrelated transactions.

If the same correction is required repeatedly, update or remove the rule instead of correcting each transaction manually forever.

Bank Rules Need Ongoing Maintenance

A rule that worked last year may no longer be suitable today.

Suppliers change names. Subscription prices change. GST treatment may change. The business may also update its chart of accounts or begin using a different payment provider.

Review bank rules when:

• A supplier or service changes.
• A recurring transaction starts being coded differently.
• The same mistake appears more than once.
• A new account is added to the chart of accounts.
• Reports show an unexpected movement.
• The business changes its GST treatment or structure.

Old or duplicate rules should be removed so the reconciliation process remains easier to understand.

Operational Review And Monthly Money Day

Bank rules are part of the bookkeeping workflow, so they should be monitored while reconciliation is being completed.

The person handling the records should watch for rules that match incorrectly, produce unusual coding or need repeated adjustments.

The owner does not need to inspect every bank rule personally during Money Day.

During the monthly Money Day, the owner should instead review whether the resulting reports are sufficiently reliable for business decisions.

For example:

• Are major costs appearing in the correct categories?
• Has an expense increased unexpectedly?
• Are platform or bank fees being captured properly?
• Do the reports match what happened operationally?
• Are repeated coding issues affecting confidence in the numbers?

If something looks wrong, the finance team can then investigate whether a bank rule contributed to the issue.

How Bank Rules Affect Reporting

Bank rules are not only a time-saving feature. They also affect the consistency of the financial information.

When recurring transactions are coded consistently, it becomes easier to compare expenses between periods and identify unusual changes.

When rules are inconsistent or incorrect, costs may appear in the wrong place and weaken the usefulness of the reports.

The aim is not to automate as much as possible. It is to automate the simple, predictable work while keeping human review for exceptions.

Common Bank-Rule Mistakes

• Creating a rule after reviewing only one transaction.
• Using descriptions that are too broad.
• Ignoring the GST treatment.
• Creating several rules that overlap.
• Using a rule for transactions that require different coding.
• Never reviewing rules after the business changes.
• Accepting every suggestion without checking it.

A small number of well-designed rules is usually more useful than a long list nobody understands.