To categorise an SME's bank transactions, the first step is a short two-level list of categories designed around the decisions management needs to make. Next come rules for the transactions that repeat every month, leaving only what the rules miss to be reviewed by hand. Every correction made in that review should become a rule, so that the manual work shrinks from one month to the next.
Without categories, a bank statement shows how much went out but not where it went. The cash flow report, the treasury forecast and the conversation with the accountant all depend on knowing how much went to suppliers, salaries or taxes. This article covers how to design the categories, how to write rules, what to do with the exceptions and how the routine looks in a practical example.
What does categorising bank transactions mean, and why does it matter?
Categorising a bank transaction means giving it a category that explains its nature, such as a sale, a supplier payment, a salary, a tax or a transfer between accounts. The bank records the amount, the date and a short description. The category adds the meaning management needs to read the month.
Treasury categories are not the accountant's chart of accounts. The chart of accounts follows accounting standards and is used for the entries and the returns. Treasury categories help management see where money comes from and where it goes, and they can be simpler. Where the two views need to meet, each category can carry an accounting code agreed with the accountant.
Good categorisation answers three questions every month.
- How much came in, and where did it come from?
- How much went out, and under which headings?
- Which headings are growing faster than sales?
How should the categories be designed?
The most common mistake is creating too many categories. A list with dozens of narrow headings forces a decision on every line and ends up being filled in differently by each person. Two levels are enough for most SMEs, with a few groups at the first level and subcategories only where management wants the detail.
| Group | Example subcategories |
|---|---|
| Sales and other income | Customer receipts, grants, interest received |
| Suppliers and external services | Goods, subcontractors, software, consultancy |
| Staff | Salaries, social security contributions, employee insurance, training |
| Taxes | VAT, withholding tax, corporate income tax |
| Premises and running costs | Rent, energy, telecoms, insurance |
| Financing | Loan repayments, leasing, bank charges |
| Transfers between accounts | Transfers between the company's own accounts |
The last group is the one most often forgotten. A transfer from one of the company's banks to another shows up as money out of one account and money into the other. If it is categorised as a sale or as an expense, the cash flow is inflated on both sides.
Before settling the list, it is worth showing it to the accountant. They know which splits the accounts need, such as keeping VAT apart from other outgoings or staff insurance apart from other insurance.
How do you create rules for recurring transactions?
In an SME, a large share of transactions repeats every month with the same description, or nearly. Those are the ones to handle with rules. A rule says that a transaction with certain features goes to a category, for example that a debit whose description contains "SOC SEC" goes to Staff, social security contributions.
- Start with the most frequent transactions. Sorting a month of statements by description reveals the recurring patterns, such as salaries, rent, energy, telecoms, loan repayments and bank charges.
- Use the direction of the transaction. The same word can appear in money in and money out. Limiting a rule to debits or to credits avoids mix-ups.
- Use amount limits where they help. A supplier that charges a fixed monthly subscription and, now and then, a larger service can have two rules, one for each range of amounts.
- Set priorities. When two rules fit the same transaction, the more specific one should win.
- Test before applying. Running a rule over months already imported shows which transactions it would catch and avoids surprises.
What should happen to transactions no rule catches?
There will always be transactions without a rule, such as a new supplier, a one-off payment or an unclear description. They should sit in a separate list, waiting to be categorised, rather than in a catch-all category such as "Other", which hides the problem.
- Review the list regularly, once a week or, at the very least, before sending the month to the accountant.
- Turn each correction into a rule whenever the transaction is likely to repeat.
- Use the invoice or receipt to decide when the bank description is not enough. This is why reconciliation helps categorisation.
- Confirm automatic suggestions, whether from rules or from artificial intelligence, before treating them as settled, especially in the first months.
With this routine, the list of uncategorised transactions gets shorter every month. The article on how to prepare the month-end close for the accountant shows where this step fits in the close.
How does EngiFinance categorise transactions?
EngiFinance is an online treasury management application for SMEs. It imports the company's bank statements and documents, categorises and reconciles the transactions, shows the cash flow and prepares the monthly export for the accountant. Its categorisation follows the order described in this article, with rules before artificial intelligence.
- Two-level categories, with an optional accounting code, preconfigured and editable.
- Rules with seven comparison types, priority, amount limits and direction, which can be tested before being applied. In the import preview, new transactions already show the categories assigned by the rules.
- Corrections that become rules. When a transaction is corrected, the correction can be saved as a rule.
- Artificial intelligence only for the rest. Transactions without a rule can be categorised in batches by AI, applied only above the minimum confidence the organisation sets. Each categorisation can be confirmed or corrected.
- Cash flow by category. The monthly cash flow map shows inflows and outflows by category, with the balance at the end of each month and the transactions behind each line.
Statements come in by file, in CSV, Excel, CAMT.053 or MT940, and PDF statements are read by artificial intelligence, with no access to the bank accounts. AI categorisation uses tokens from a monthly quota included in every plan. When the quota runs out, imports are paused until the following month, at no extra cost.
A practical example
Imagine an engineering services company with 12 people, two bank accounts and around 180 transactions a month. Until now, categorisation was done at the end of each quarter in a spreadsheet, and half the lines ended up as "Sundry".
In the first month, the office manager cuts the list down to seven groups, as in the table above, and agrees the code for each subcategory with the accountant. She then creates rules for the most frequent patterns.
- Salaries, social security and withholding tax, by the description text and only on debits.
- Rent, energy, telecoms and insurance, by each supplier's name.
- Transfers between the two accounts, to Transfers between accounts.
- Customer receipts, by credits with the customer's name in the description.
With these rules, most transactions are categorised on import. The rest go to the list waiting to be categorised, and every correction likely to repeat becomes a rule. After a few months the list is short, and the cash flow map shows that external services have grown faster than sales. That map is what management now uses to decide, and it is the starting point for the 12-month cash flow forecast.
Frequently asked questions
What is the difference between treasury categories and a chart of accounts?
The chart of accounts belongs to the accountant and follows accounting standards. Treasury categories serve management and show where money comes from and where it goes. An accounting code on each category connects the two views.
How many categories should an SME have?
There is no right number. Two levels, with a few groups at the first level and subcategories only where management wants the detail, are enough for most SMEs. If the team often hesitates between two categories, there are too many.
How should transfers between the company's own accounts be categorised?
In a category of their own, separate from sales and expenses. Otherwise the same transfer counts as money out of one account and money into the other, and the cash flow is inflated.
Can artificial intelligence categorise transactions on its own?
It can propose a category for the transactions the rules do not handle, but each result should be open to confirmation or correction. In EngiFinance, AI is applied only above the minimum confidence the organisation sets.
Does EngiFinance come with predefined categories?
Yes. Categories come preconfigured in two levels, with an optional accounting code, and can be edited.