Choosing accounting software starts with the records and reporting your business actually needs, including VAT or MTD compatibility where relevant. Compare workflows, access, exports and support before selecting a product from a feature list or introductory price.
Use representative transactions to test the fit: refunds, mixed payments, cash receipts and accountant access. Confirm the full recurring cost and how records can be recovered if you leave.
Describe the work before comparing products
Write down how the business invoices, receives money, buys supplies and reports tax. Include cash, card processors, foreign currency, stock or project tracking where relevant. Identify who will use the system and what each person needs to do. A small consultancy and a retailer can have similar turnover but very different bookkeeping workflows, so a feature count alone is a poor basis for choosing between products.
For MTD for Income Tax, check the current HMRC software guidance and finder for the functions and income sources required. Compatibility for one tax service does not establish compatibility for another. HMRC recognition also does not amount to a recommendation of a product. Treat the official listing as one eligibility check within a broader assessment of the business's practical reporting and record needs. [1]
Test representative transactions
Prepare anonymised examples covering a normal sale, customer refund, supplier credit, split payment and owner transfer. Add one unusual transaction that regularly causes difficulty. Ask the provider to show how each is recorded, corrected and traced to its supporting evidence. A polished demonstration using only a clean invoice and matching bank receipt may not reveal the work involved in the business's actual monthly records.
Check how the system deals with transactions already entered through another channel. For example, determine whether a bank-feed receipt matches an existing sales invoice or creates new income. Review the steps needed to correct a mistaken match without losing the audit trail. The best fit is a process the intended users can operate consistently, not merely a product that can theoretically perform the task with extensive manual workarounds.
Confirm the whole reporting workflow
Identify which product will maintain the records, send updates and complete the relevant annual return or other tax submission. If more than one tool is involved, explain how they connect and who owns each stage. Check support for all relevant activities and other income needed for the return. Do not discover at year end that the chosen package handles quarterly figures but cannot complete the required final reporting without another component.
Ask the accountant to confirm the proposed workflow before the business commits to a long subscription. Their preferred software can be useful, but it should still fit the client's records and access needs. Record any manual steps or additional fees. A clear responsibility map helps prevent the owner assuming that an accountant invitation automatically includes bookkeeping review or submission approval.
Compare costs, access and exit terms
Calculate the recurring cost after introductory offers, including users, transactions, receipt capture, payroll, integrations and support where charged separately. Identify the features needed now and those only relevant if the business grows. Avoid paying for a complex package solely because a future feature sounds useful, while also checking that a low-cost tier does not impose a limit the business will exceed immediately.
Review who controls the subscription and administrator access, how records can be exported and what remains accessible after cancellation. Test an export of transactions and attachments if a trial allows it. The ability to leave with usable records is a practical requirement, especially when the accountant holds the subscription. A summary report alone may not preserve the evidence needed to explain individual transactions later.
Decide with a short written comparison
Score the shortlisted options against the business's essential workflows and note any unresolved question. Distinguish a confirmed feature from a provider's planned release. Record the decision, assumptions and implementation tasks so the setup starts from an agreed scope. The comparison need not be elaborate; a concise table showing evidence, limitations and total cost is often more useful than a long list of marketing claims.
Use Checking software compatibility with HMRC services for checking the exact HMRC compatibility and Cloud bookkeeping setup to discuss software selection alongside bookkeeping requirements. Describe the business activities, reporting obligations and current pain points. A focused review can then identify the features that matter without implying that one package is automatically best for every UK small business.
Before switching fully, agree a cutover date and a small migration plan. Keep the old records available until opening balances, outstanding invoices and the first reconciliation have been checked. Buying a suitable product is only the beginning; a controlled setup is what allows its features to support reliable day-to-day accounting.
Illustrative scenario
A retailer tests two systems using a card settlement with fees and a returned item. The comparison exposes a reconciliation problem that a simple invoice demonstration would not reveal.
Preparation checklist
- List required workflows
- Test realistic transactions
- Check HMRC compatibility
- Review costs and exit options
Frequently asked questions
Does an HMRC listing mean a product is recommended for my business?
No. It indicates the relevant recognition, not a personalised recommendation. Check the exact functions and practical fit for your records and reporting.
Should I compare only the advertised monthly price?
No. Include additional users, transaction limits, integrations, support and the price after introductory offers, together with any separate submission component.
Can several products form the reporting workflow?
Potentially, if they meet the applicable requirements and work together properly. Identify which product handles each task and confirm the complete submission process.
What should be tested during a trial?
Use realistic anonymised transactions, corrections, matching and exports. Include the awkward cases that currently consume time, not only a straightforward invoice.
Official sources
Sources checked: 8 September 2026. Check the linked guidance for subsequent changes.
General information only. The appropriate action depends on your circumstances and the applicable jurisdiction.
Report a correction