For accountants
Run your practice on TaxChad.
The software does the bookkeeping at scale. You stay the trusted human, with your name on the file.
Already a partner practice? Sign in to your firm portal
Where it stands today
- Per-firm data isolation, row level security
- UK hosted and encrypted
- No client money ever held
- Built for Making Tax Digital
- A CIMA-regulated practice already running on it
Built around the work a practice actually does.
Not a small business tool with a partner login bolted on. The firm portal, the client books and the audit trail are the same system.
Client onboarding and migration
Bring a client across without rekeying a year of history. The QuickBooks and Limebooks migration wizards import the ledger, the chart of accounts and the opening position, then reconcile the trial balance before you go live. Onboarding, KYC, AML and engagement letters are tracked per client alongside the books.
MTD across the whole book
VAT nine-box returns prepared from the ledger and filed to HMRC under Making Tax Digital, with obligations and deadlines tracked across every client rather than in a spreadsheet. MTD for Income Tax is being built out against the same ledger.
One master chart of accounts
Maintain a firm-wide chart and push it to any client's books, so classifications stay consistent across the portfolio and your reporting pack means the same thing for every client.
Jobs and workflow
Practice Manager gives you the job list by client, by deadline and by owner. You can see what is blocked, what is with the client and what is ready for partner review.
Staff access scoping
Seats are scoped. Staff see the clients and the areas of the product you allow, partners see everything, and privileged actions are recorded whoever performs them.
The client portal
Your client works in the same books you do. They answer queries, approve a VAT return and upload the missing receipt in one place, with your firm's name on it.
The audit trail
Real double-entry underneath, FRS 102 multi-currency with period close, journals and prior-period adjustments, and a data access log that records who read what and when.
You are putting your practising certificate behind this.
That is the real question, so here is the answer without the marketing. Three things carry the risk: the data cannot leak between firms, every action on a client's books is recoverable after the fact, and the security work is independently verifiable. None of it has been externally tested yet. We say so below, and a formal penetration test is planned.
If something is not built yet, it is on the roadmap page in future tense with no date attached. We would rather lose a demo than have you find out later.
Data isolation
Every table holding client data is protected by row level security enforced in the database, not in application code. A firm can only reach its own clients, and a staff seat can only reach the clients you scope it to. A bug in the app cannot widen that.
The August 2026 security audit
A full internal audit of the source code and the database: isolation between firms and clients, access control, server code, secrets handling and the integrity of the numbers. Every finding was fixed, verified and covered by a test that now runs on every change. It was our own work, not a third-party audit or a penetration test, and we will not describe it as one. A formal external penetration test is planned.
The audit trail
Journals must balance, statutory records are uniquely constrained, and posted history cannot be quietly edited. A data access log records who read which client and when, and privileged actions are written to an immutable log you can review.
On the roadmap
- A payments revenue share for practices, once Pay by Bank is live. Future tense, no date quoted.
- MTD for Income Tax quarterly updates across the client book, built against the same ledger.
See it against one of your own clients.
Thirty minutes, a real ledger, and an honest answer on anything that is not built yet.