Crofter/Sectors/Accountancy & Tax
Accountancy & Tax.
Repetitive reasoning over structured evidence, under a regulator's eye. The work has the same shape from client to client; the numbers and documents do not. That is the shape AI-augmented software suits best, and it is where margin has leaked most visibly since the April 2025 cost rises.
The firms
Mid-sized practices - 50 to 300 people across audit, tax advisory and accountancy - run a back office saturated with form-heavy, document-heavy, decision-heavy process. Partner attention is rationed. Paralegal and junior time is the constraint on throughput. What is missing is software that is explicit about the regulatory tests it applies, cites its sources, and sits inside the stack the firm already pays for.
Workflows we build here
One at a time, each wired into the systems the firm already runs.
- HMRC investigation document pack
- For enquiries, COP8 and COP9 matters: disorganised client history in; a dated, privilege-aware case timeline out, with a partner pre-brief and a list of the questions HMRC is likely to ask, all cited back to source pages.
- IR35 status determination
- A rules engine with the status tests codified - control, substitution, mutuality of obligation, financial risk, part and parcel - and a language model reading the contract and the working-practices statement. Clear cases move on; edge cases go to a paralegal queue.
- R&D claim preparation
- A structured interview with the technical lead, evidence captured against the tests for the relief, and a draft technical narrative and costing worksheet for senior review. Built to keep a claim defensible under HMRC scrutiny.
- Client onboarding and AML intake
- Self-serve onboarding with guided form completion, identity checks through a specialist vendor and risk-rated routing. Practice management and Sage kept in step; signature and filing automated.
The cover sheet a Build of this kind would put on its output, with each field described rather than filled in.
Code of Practice 9 enquiry: partner pre-brief
- Enquiry
- The notice, and the code of practice it falls under
- Client history
- Everything the client sent, ingested from the document store, dated and cited to its source page
- Timeline
- Dated events across the tax years in question
- Likely questions
- What HMRC tends to ask in enquiries of this shape, drawn from the firm's own past cases
- Evidence gaps
- What is missing, flagged for a follow-up with the client
- Sign-off
- The supervising partner. Correspondence with HMRC goes through the partner's queue and is never sent automatically.
A specimen, not a real matter. Nothing here comes from a live deployment.
Case studies
No published case study in accountancy and tax yet.
When there is one it will name the firm and carry measured numbers, with the firm's sign-off. Until then this page describes the work, not its results. If your firm would like to be the first, write to crofter@nullhex.io.
The rules we build around
The general posture is on How we work.
- Standards
- The ICAEW and ACCA codes of ethics, and HMRC's Standard for Agents.
- Anti-money laundering
- The Money Laundering Regulations 2017, with the firm's own risk assessment built into intake.
- Data
- UK GDPR. Client ledger data stays in the UK region.
- Models
- Enterprise endpoints, zero-training terms, and an audit log of every query.
Nearby: Recruitment, Law. Or all five sectors.