How to Categorise Transactions in Sage
Sage Accounting and Sage 50 use the same nominal-code-plus-T-code logic, but the workflow differs. Here is the step-by-step for both, the T-code rules that catch people out, and where pattern-learning earns its keep.
Quick answer
In Sage Accounting (cloud), go to Banking, click into the bank account, then click each unreconciled bank line. Choose Other Receipt or Other Payment, pick the contact, set the nominal code (4000s sales, 5000s materials, 7000s overheads), and choose the T-code for VAT (T0 zero, T1 standard 20%, T2 exempt, T9 outside scope). In Sage 50 the equivalent is the Bank Feeds tab with the same nominal-and-T-code logic. Sage’s automation (recurring entries, Memorise feature) is lighter than Xero or QuickBooks, so high-volume practices typically pair Sage with a pattern-learning tool. CodeIQ connects to Sage via API, learns the chart of accounts, runs an eight-phase coding pipeline, and posts results back as draft transactions for review.
Sage 50 vs Sage Accounting: pick the right walkthrough
Sage sells two related but distinct products in the UK. The categorisation logic is shared (nominal codes plus T-codes), but the screens and shortcuts are very different.
| Aspect | Sage 50 (desktop) | Sage Accounting (cloud) |
|---|---|---|
| Deployment | Installed Windows app, local SQL/Pervasive database | Browser-based with mobile apps |
| Bank feed | Bank Feeds tab (added in v24+) | Native Open Banking feed integration |
| Bank rules | Limited; via Bank Feeds rules screen | Yes; auto-categorisation rules |
| Recurring entries | Memorise transaction list (long-standing) | Recurring Income / Recurring Expense |
| VAT engine | Same T-codes; full UK MTD support | Same T-codes; full UK MTD support |
| Multi-user | Per-machine install, network DB | Subscription per user, online |
| Typical practice | Established firms with legacy data, complex stock or job costing | Newer practices, simpler businesses, anywhere-access teams |
Sage Accounting: the Banking workflow
Where everything happens
Open Sage Accounting. Click Banking in the top navigation. The Banking dashboard shows each linked bank account with its current balance and the count of unreconciled transactions. Click into the relevant bank account. The transaction list shows each line, with a coloured indicator on the left (green for matched, amber for unmatched, grey for in-progress).
What “doing it properly” looks like per line
Click the unmatched line
A panel opens with the bank narrative, reference, and amount. Sage offers four classification options: Other Receipt, Other Payment, Sale (creates an invoice), Purchase (creates a bill), and Bank Transfer.
Pick the right entry type
Most bank lines that need categorising are Other Payment or Other Receipt. Use Sale or Purchase only when you want Sage to also raise an invoice or bill at the same time. Bank Transfer for moves between your own accounts.
Choose the contact
Type the contact name. Sage suggests existing contacts; if a new one is needed, you can create it inline. Keep names consistent (“British Gas” not “BRITISH GAS BUSINESS LTD”) to avoid duplicate ledger entries.
Pick the nominal code
Sage uses a fixed UK chart of accounts as the default. Type the four-digit code (e.g. 7100 for Rent, 7500 for Printing) or search by name. Sage filters as you type.
Set the T-code (VAT)
Choose from T0, T1, T2, T5, T9, T20, etc. Sage auto-selects a default based on the nominal code, but always check; the T-code drives the MTD VAT return.
Save
Click Save. The bank line moves to matched, the entry posts to the nominal ledger and VAT control, and the suggestion engine remembers the contact and nominal code for next month.
Sage 50: the Bank Feeds tab
Sage 50 desktop reached parity with cloud bank feeds in version 24. The Bank Feeds tab on each bank account shows incoming bank lines with the same options: New Customer Receipt, New Supplier Payment, New Bank Receipt, New Bank Payment, plus an Existing Transaction match for invoices already in the ledger.
The Sage 50 muscle memory
Sage 50 users tend to come at this from the desktop “Bank” module habit: opening Bank, clicking the bank account, then either Customer Receipt, Supplier Payment, or Bank Payment from the toolbar. The Bank Feeds tab now provides the same buttons in context, but most existing Sage 50 users still raise transactions from the legacy Bank module and reconcile separately.
Sage nominal codes: the standard UK chart
Unlike Xero or QuickBooks, Sage ships with a comprehensive fixed UK chart of accounts. The structure is rigid (and inherited from the desktop product) but it covers most UK SME use cases without customisation.
| Range | Category | Example codes |
|---|---|---|
| 0xxx | Fixed assets | 0010 Freehold property, 0030 Office equipment, 0050 Motor vehicles |
| 1xxx | Current assets | 1100 Debtors control, 1200 Bank current account, 1230 Petty cash, 1250 Credit card |
| 2xxx | Current liabilities | 2100 Creditors control, 2200 VAT on Sales, 2201 VAT on Purchases, 2202 VAT liability |
| 3xxx | Capital and reserves | 3100 Ordinary shares, 3200 P&L Account |
| 4xxx | Sales | 4000 Sales Type A, 4001 Sales Type B, 4900 Other income |
| 5xxx | Purchases / direct costs | 5000 Materials, 5100 Carriage, 5200 Discounts allowed |
| 6xxx | Direct expenses | 6000 Productive labour, 6201 Sales commission |
| 7xxx | Overheads | 7000 Gross wages, 7100 Rent, 7200 Electricity, 7500 Printing & stationery, 7600 Legal fees, 7900 Bank charges |
| 8xxx | Depreciation, sundries | 8000 Depreciation, 8100 Bad debts, 8204 Insurance |
| 9xxx | Suspense, holding | 9998 Suspense, 9999 Mispostings holding |
Customising the Sage chart of accounts
You can add codes within the Sage ranges (e.g. 4002 Sales Type C, 7505 Print collateral), but rearranging the structure is risky: report templates assume the standard ranges. Most practices add codes within ranges rather than redesigning the chart.
T-codes: Sage’s VAT classification system
Sage T-codes are the way VAT treatment is signalled per transaction. They feed directly into the MTD VAT return.
| T-code | Meaning | Example transactions |
|---|---|---|
| T0 | Zero rated | Books, children’s clothes, basic food, public transport sales |
| T1 | Standard rated 20% | Most UK sales and purchases of goods/services |
| T2 | Exempt | Insurance premiums, postage stamps, financial services, education |
| T5 | Reduced rate 5% | Energy-saving materials, women’s sanitary products, children’s car seats |
| T9 | Outside scope of VAT | Wages, dividends, MOT fees, statutory fines, internal transfers, drawings |
| T20 | Domestic reverse charge | CIS construction services, mobile phones & computer chips above £5k |
| T22 | EU sales (post-Brexit) | Goods sold to EU business customers from GB |
| T24 | Import VAT (PVA) | Imports under postponed VAT accounting from outside UK |
T9 vs T2: the most common mistake
T9 means outside the scope of VAT (wages, dividends, MOT fees). The transaction does not appear on the VAT return at all. T2 means exempt (insurance, postage stamps). The transaction appears in Box 7 (net purchases) but contributes no VAT. Pick T9 for a genuinely exempt purchase and Box 7 is understated. HMRC’s partial-exemption review reconciles Box 7 against the underlying ledger; mismatches surface.
Recurring entries and the Memorise feature
Sage’s headline automation is recurring entries. In Sage Accounting, raise an entry once and tick “Make recurring” before saving. Set the frequency (monthly, quarterly, annually). Sage posts the entry automatically on the schedule. Suitable for rent, subscriptions, fixed retainers, payroll batches.
In Sage 50 desktop, the equivalent is Memorise Transaction: open a transaction, click Memorise, save the template. Recall it from the Memorise list whenever needed. Less automatic than recurring entries, but more flexible since each recall is a manual posting that you can adjust before saving.
Bank rules: capable but lighter than Xero
Sage Accounting introduced auto-categorisation rules in 2023 onwards. Each rule matches on bank narrative or reference and applies a contact, nominal code, and T-code. Rules are evaluated in order, first match wins.
Where Sage rules work
- Rent, subscriptions, payroll deposits with consistent narrative
- Direct debits to known suppliers
- Card processor settlements with templated reference text
- Internal transfers (matching pairs)
Where they fall short
- No multi-line / split rules (cannot split rent into rent + service charge)
- No tracking categories on rules
- Cannot set a custom VAT amount on the rule (uses T-code default)
- Rules do not transfer between Sage organisations: each new client is a fresh rule build
When manual coding stops scaling
Sage’s automation ceiling is the lowest of the four major UK platforms. For simple businesses with steady-state transaction volumes, recurring entries plus a handful of rules cover most of the work. For higher-volume businesses or practices managing 10+ Sage clients, manual reconciliation tends to bottleneck somewhere between 200 and 300 transactions per month per client.
Practical signs to watch
- Quarterly VAT review surfaces multiple T-code errors per client
- The same merchant gets different nominal codes in successive months because of staff variation
- Junior staff guess at nominal codes when faced with an unfamiliar payment
- The Bank Feeds tab fills up faster than it clears down
- Period close drifts week by week
Pattern-learning automation (CodeIQ)
CodeIQ supports Sage as one of its four platform integrations (alongside Pandle, Xero, and QuickBooks). Connect via API, and CodeIQ reads your Sage chart of accounts, T-code list, supplier and customer contacts, and outstanding invoices. Then it learns from your existing Sage general-ledger history.
The eight-phase pipeline applied to Sage
- Transfer detection » recognises matching internal moves and posts them as bank transfers, not as expenses or income.
- Invoice matching » links bank receipts and payments to outstanding Sage invoices and bills, with adjustments for partial payments and bank charges.
- Historical pattern » learns how you have coded each merchant in your Sage ledger before, and applies the same nominal code and T-code automatically.
- Universal pattern » applies anonymised patterns built from thousands of UK practices: a new Sage org benefits from collective learning without writing a single rule.
- MCC category » uses card merchant category codes where available to give a category floor.
- Semantic analysis » for transactions that fall through the rule-based phases, an embedding model classifies the transaction against your account names.
- User learning » corrections you have made stick: the next time the same merchant arrives, the right code is applied automatically.
- VAT classification » the universal codes (NV, ST, EX, RR, ZR) are mapped to your Sage T-codes (T9, T1, T2, T5, T0) automatically.
CodeIQ posts the coded results back to Sage as draft transactions, ready for your review. Same audit trail, same VAT compliance, a fraction of the manual reconciliation time.
Try CodeIQ free with Sage Accounting
Connect Sage via API, upload a bank statement, and see how an eight-phase pipeline compares to the Banking screen. Two minutes per client, not two hours.
Try CodeIQ freeFrequently asked questions
How do I categorise transactions in Sage Accounting?
Go to Banking, click into the bank account, then click each unreconciled bank line. Choose Other Receipt or Other Payment, pick the contact, set the nominal code (4000s sales, 5000s materials, 7000s overheads), and choose the T-code for VAT. Click Save. In Sage 50 desktop, the same logic applies through the Bank Feeds tab.
What are Sage T-codes for VAT?
T0 zero-rated, T1 standard 20%, T2 exempt, T5 reduced 5%, T9 outside the scope of VAT, T20 domestic reverse charge, T22 EU sales (post-Brexit), T24 import VAT under postponed VAT accounting.
What does T9 mean in Sage?
T9 means outside the scope of VAT. Use T9 for transactions that are not part of the VAT system: wages, PAYE/NI payments, dividends, owner drawings, internal transfers, statutory fines, MOT fees. T9 is different from T2 (exempt). T9 transactions do not appear on the VAT return at all; T2 transactions appear in Box 7 of the VAT return.
What is the difference between Sage 50 and Sage Accounting?
Sage 50 is the desktop product (installed on Windows, local database). Sage Accounting is the cloud product (browser-based with mobile apps). Categorisation logic is shared (nominal codes plus T-codes), but the workflows differ significantly. Most new UK practices choose Sage Accounting; many established firms still run Sage 50 because of legacy data depth.
Can I automate transaction categorisation in Sage?
Sage Accounting supports recurring entries and basic auto-categorisation rules, but the automation is the lightest among major UK platforms. Pattern-learning tools like CodeIQ connect via API, learn from your general ledger history, and code transactions through an eight-phase pipeline before posting back to Sage as draft transactions for review.