Categorising bank transactions with a rule engine instead of manually.
Every modern bookkeeping package (Yuki, Moneybird, Exact, Twinfield, Snelstart) has rule-based categorisation. The win is in good rules, not the most rules.
Try this first
- 1Inventory your top 20 vendors in transactions, rules on these 20 cover 60-80 percent of volume in our experience.
- 2Create a rule per vendor on IBAN or a unique part of the description, not on amount (which changes).
- 3Test the rule against a historical month, not just new entries, false positives show up immediately.
- 4Limit catch-all rules to small amounts or clear categories (parking, fuel), otherwise too much lands on the wrong account.
- 5Plan a quarterly review, vendors change IBAN or description and rules quietly become useless.
When to bring us in
For a rule set tuned to your sector and vendors, we can set it up in one session.
See also
- Switching from Exact Online to Yuki, open items and history do not matchPackage migrations stumble on ledger mapping and open AR/AP. Without a mapping table you lose context.
- Twinfield to Exact, dimensions and cost centres go missingTwinfield uses dimensions, Exact uses cost centres and projects. The mapping is not one-to-one.
- Accountant asks for RGS mapping, your ledger does not follow RGSRGS is the Dutch standard chart that SBR filings and accountant software expect. Without mapping, every year-end is manual.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.