XBert Type: Standard
Accounting Software: Xero
Country Restriction: All supported countries
Risk Type: Financial Reporting Risk
Business Function: Purchases
Overview
This XBert checks whether a supplier's expense (spend money) transaction has been coded to a different account than the one you always use for that supplier. A single out-of-pattern coding is often a simple mistake, and catching it early keeps your reports and tax codes accurate.
What it does
For each supplier, this XBert:
Looks at how that supplier's past expense transactions have been coded.
Identifies suppliers you have coded consistently to one account every time.
Flags a new transaction for that supplier when it has been coded somewhere different, and shows you the account it would usually go to.
How it works
The XBert only raises an alert when it is confident the coding is genuinely odd. It fires when all of the following are true:
The supplier has a strong, settled pattern: it has been coded at least eight times in the past, and every single one of those went to the same account.
This latest transaction has been coded to a different account from that usual one.
The transaction is worth more than five dollars, so trivial amounts are ignored.
It also recognises intentional changes, so it does not nag you about reclassifications you meant to make. If several different suppliers all move from the same old account to the same new account around the same time, it treats that as an intentional restructure of your chart of accounts and stays quiet. Likewise, if you bulk re-code many transactions for one supplier to a new account in the same update, it recognises that as a deliberate change rather than many mistakes. It also stays quiet if the supplier's usual account has been archived or renamed, and it never alerts on transactions that have not yet been coded.
Example/Use Case
Priya runs a small design studio. Every month her coffee supplier, Bean & Bar, is coded to "Staff Amenities" and has been for over a year. One week her new bookkeeper codes a $240 Bean & Bar invoice to "Entertainment" instead. The XBert spots that this single transaction breaks the supplier's settled pattern and shows that it would normally go to "Staff Amenities." Priya checks, agrees it was a slip, recodes it back to "Staff Amenities", and her expense reporting and tax treatment stay correct.
Accounting software
This XBert is available for:
Xero
Which countries it supports
All supported countries. The check compares your own coding history, so it works the same way wherever your business is based.
Processes
This XBert falls under the Purchases (AP) business area. To resolve it:
Open the flagged expense transaction and look at the account it has been coded to.
Compare it with the usual account shown by the XBert for that supplier.
If the coding is wrong, recode the transaction to the correct account.
If the new account is actually correct, for example because you have genuinely changed how you categorise this supplier, leave it as is.
Once the transaction is correct, mark the XBert as resolved.