By Manvinder Sidhu, Co-founder, Ezyiah
Short answer: Ezyiah doesn't depend on bank rules. Rules match text and fire the same way every time, which works for stable, repeated transactions but quietly miscodes when descriptions, amounts or GST treatment change. Ezyiah categorises each transaction from its context, remembers how you've coded the business with AI Memory, and lets you fix a pattern everywhere with Scan Similar Transactions. Everything happens in Ezyiah's own ledger, and you review and approve before lodgement.
What are bank rules good at?
Bank rules automate repetition. When the same merchant appears with the same description, a rule codes it instantly. For a fixed rent payment or a monthly software bill, that's useful.
Where do bank rules break?
Real bank data isn't stable. Descriptions change, payment processors appear, suppliers restructure, CSV exports truncate fields, and feeds re-sync. Then a rule either stops firing, which is obvious, or fires incorrectly, which isn't. A rule that codes a supplier as GST-inclusive keeps doing it after the supplier changes what it sells. The error looks consistent, so nobody questions it until BAS review, when it's already in months of history. See Xero bank rules that quietly miscode transactions and director loans in bank feeds: why rules miss them.
How does Ezyiah categorise without rules?
- Context, not string matching. "BNGS WHSE", "Bunnings" and "Bunnings Warehouse" are recognised as the same merchant, and amount and pattern are taken into account.
- AI Memory. When you correct a category or GST code, Ezyiah remembers it for that business next time. You don't write or maintain rules.
- Scan Similar Transactions. Fix one transaction and apply the same correction to similar ones across the file.
- Transaction splitting. Split mixed transactions across accounts, for example for private and business use.
- Visible and editable. Every line shows its account and GST treatment and can be changed. The Ezyiah Assistant panel keeps an activity trail.
Why does this make BAS easier?
There are fewer silent errors to unwind. Corrections made during the quarter carry forward automatically, so the last week before lodgement is a review, not a rebuild. Your accountant reviews and approves the BAS before it's lodged.
See how it works for business owners and accounting firms, or compare Ezyiah vs Xero.
Frequently asked questions
Do I need to set up bank rules in Ezyiah?
No. Ezyiah categorises with AI and learns from your corrections with AI Memory.
What happens if Ezyiah gets a category wrong?
Change it on the line. Ezyiah remembers the correction, and you can apply it to similar transactions in one step.
Is AI categorisation better than bank rules?
For changing or messy data, usually. For perfectly stable repeated transactions, both work. The difference is that AI adapts when the data changes and rules don't.
