# What AI in accounting actually delivers in practice Source: https://getstartedwithai.net/blog/what-ai-in-accounting-actually-delivers Site: Get Started With AI Tagline: Build AI automations that actually run your business. Audience: solo professionals, freelancers, consultants and AI implementers in training Contact: hello@getstartedwithai.co.uk This Markdown companion is generated from the prerendered page for AI crawlers. # What AI in accounting actually delivers in practice AI in accounting (UK) delivers about six to ten hours a week saved per fee earner across four use cases (bank reconciliation triage, client document chasing, standard client letters, month-end checklists), at a build cost of roughly £3,000 plus £30 a month in tooling, and a payback inside a quarter for any practice with at least four fee earners. AI does not deliver replacement of qualified judgement, sign-off on regulated work, or a sustainable substitute for junior staff. Software vendors have over-marketed AI in accounting for two years; the actual numbers in practices that adopted AI in 2025 sit in a narrower band than the vendor case studies suggest. After watching twenty UK practices ship and run AI builds during 2025, the patterns are consistent enough to write down. This post is the honest version with the numbers, the four use cases, the ICAEW-shaped audit risk angle that vendor blogs miss, and what AI does not deliver. ## What AI in accounting actually does In a small or mid-sized UK practice, AI does four things well in 2026. Bank reconciliation triage against a chart of accounts, where the model proposes the right ledger code and the bookkeeper confirms or corrects. Client document chasing for the routine cases, where an automation reads the client portal status and sends a templated chaser to clients with overdue submissions. Drafting standard client letters in the firm voice, where the model produces a first draft from a structured input (client name, year-end date, fee proposal) and the partner signs the final version. Month-end checklist generation, where the model produces a tailored checklist from the client engagement letter and the bookkeeper works through it. None of those four replace qualified judgement; all four remove hours of repeated low-judgement work. ## The numbers from twenty UK practices - Reconciliation hit rate after a fortnight of corrections: 90 to 95 percent on transactions inside the chart of accounts the practice already uses. - Hours saved per fee earner per week, across all four uses combined: 6 to 10. The mid-range is closer to 8. - Build cost across the four uses: roughly £3,000 in setup time plus £30 a month in tooling for a 5-fee-earner practice. - Payback period: under a quarter for any practice with at least four fee earners on the standard rate card. - Adoption rate of the deployed builds at month six: 75 to 90 percent in practices with a named ops lead, 30 to 50 percent in practices without one. - Time-to-first-build inside a typical engagement: three weeks from the audit to a deployed Custom GPT or Make scenario. ## What AI does not do in an accounting practice AI does not produce a final-form client letter without review. It does not handle numerical accuracy as the source of truth; the books remain the source of truth and AI describes them. It does not do regulated work that needs a qualified signature. It does not replace junior staff in a sustainable way; the time it frees gets reinvested in higher-value advisory work that the practice could not previously sell. It does not handle complex tax judgement, complex VAT positions, or any work that requires interpreting case law or HMRC guidance against a specific set of facts. It does not substitute for the ICAEW or ACCA continuing professional development obligation. The boundary is sharp and matters: the work AI does well is the work that does not need a qualified signature. ## The audit risk angle that vendor blogs miss For practices conducting statutory audits, AI use creates a specific category of risk that the Sage and Xero blogs do not cover. The ICAEW Audit and Assurance Faculty position in 2025 was that AI tools used in audit work are subject to the same documentation, testing and review standards as any other audit procedure. That means AI-generated reconciliations need a documented testing approach, the prompts and inputs need to be retained as part of the audit file, and the practice principal carries the qualified signature regardless of whether AI produced the underlying analysis. Practices that adopted AI in audit work without addressing the documentation question landed in the regulators sights in two of the cases I am aware of. The audit-specific work is not where the easy savings are; the easy savings are in non-audit work like bookkeeping triage and advisory drafting. ## Implementation cost realism for a 5-15 person UK practice A 5-person practice ships the four use cases above for about £3,000 in setup time and £30 a month in tooling. A 15-person practice spends about £6,000 in setup time and £60 a month in tooling, mostly because the four use cases need to be deployed across more team members and the prompt calibration needs to cover more of the firms voice. Above 15 people the cost flattens; the same four builds serve a 30-person practice for not much more than a 15-person one, because the marginal user does not add to the build cost. The savings scale linearly with headcount. A 5-person practice saves about 30 to 50 hours a week across the team. A 30-person practice saves 180 to 300 hours a week. The fee-earner-equivalent saving is what makes the case to the partners, not the headline cost figure. ## Three anonymised UK practice examples Practice A, a 6-person Manchester practice. Shipped reconciliation triage in February 2025. Hit rate after fortnight of corrections: 92 percent. Hours saved per fee earner per week: 7. Build cost: £2,800. Practice B, a 14-person London practice with a small audit book. Shipped client letters and document chasing in March 2025. Hours saved per fee earner per week: 6. Skipped audit-side AI use because the partner team chose not to take the documentation risk. Practice C, a 22-person regional practice with a strong advisory side. Shipped all four use cases plus a fifth (advisory paper drafting) in summer 2025. Hours saved per fee earner per week: 9. The advisory drafting was the surprise high-value use case; the practice grew its advisory revenue by about 20 percent in the six months after the build because the partners had time to sell the work. ## When the math does not work For sole practitioners with under three hours a week of repeated manual work, the build cost is hard to recover. The right answer is the free Starter Kit and a 30-minute Time Tax conversation before any tool is bought. For practices that have not yet documented their processes, the audit step alone takes longer than the build, and the right move is a paid documentation engagement first, then the AI build. For practices in heavily audit-led work without a clear plan for the documentation risk, the right move is to pause the audit-side AI use and ship the non-audit side first. The math does not work for everybody; honesty about that is itself a trust signal that the vendor blogs cannot match. ## What changes for the practice in year two Year one is the build year. Year two is when the practice realises that the time saved was the easy half of the value. The harder half is what the partners do with the reclaimed time. Practices that reinvested the time in advisory work grew non-statutory revenue by 15 to 30 percent in year two. Practices that did not reinvest saw the time absorbed back into the operational layer with no compounding benefit. The Embed step of the WIRE Method covers the named owner and the review cadence; the year-two question is about the partner-level decision on what to do with the time. AI is the multiplier; what gets multiplied is the partner judgement about where to spend the freed-up hours. ## Build your first AI system live with Richard A 60-minute live build with Richard Batt. Bring one repeatable task. Leave with a mapped automation, success metrics and a deploy plan you can test the next morning. Free seat, no upsell. ### Live build session The next live session covers the WIRE Method end to end on a real audience build. [Join the next session](/webinar) ## Questions people ask before they start ### undefined undefined ### undefined undefined ### undefined undefined ### undefined undefined ### undefined undefined ### undefined undefined