In my first year in audit, a senior glanced at a trial balance for about four seconds and said "that debtors figure doesn't move like that." Nobody had opened a single schedule yet. She was right, and it took two days of testing to prove why.
That moment did more for my cloud practice than any certification I hold.
TL;DR: Xero Advisor, QuickBooks ProAdvisor and the Dext badges test whether you can drive a product. They don't test whether you can feel that a number is wrong before you can say why. Audit drilled three instincts into me - materiality, directional expectation, and documentation discipline - and I use all three every day. None of them appears in a software syllabus.
What Do Cloud Certifications Actually Test?
They test navigation. Can you set up a bank rule, run a VAT return, map a chart of accounts, reconcile a feed. Useful, necessary, and I hold most of them. But every one assumes the numbers in front of you are roughly right and the job is to process them correctly.
Audit assumes the opposite. The whole discipline starts from "this might be wrong, prove it isn't." That single inversion is the gap between someone who is fluent in a platform and someone who can tell when the platform is being fed nonsense. Making Tax Digital already forces almost every VAT-registered business onto digital records, with MTD for income tax arriving from April 2026 for sole traders and landlords over £50,000. More files than ever are being kept on software that quietly tells people they are doing fine.
Why Is Materiality the Skill I Use Most?
Because not everything on a page deserves equal attention, and knowing where to look is most of the job. Materiality, in the audit standard, is any misstatement that "could reasonably be expected to influence the economic decisions of users" (ISA 320). In plain terms: would this number change what someone does.
That trains two reflexes. First, you stop treating a £40 miscoding the same as a £40,000 one. Second, and more usefully, you build a directional expectation - you know roughly what a figure should be before you open it. When a client's gross margin jumps eight points with no change in the business, I notice in seconds, because audit taught me to carry the expected number in my head. A five-minute read of the bank reconciliation catches most of the rest. The dashboard never flags any of this. It shows you what is there, confidently, whether or not it is true.
The Documentation Habit That Survives Into Cloud Practice
The rule audit beats into you is blunt: if you didn't write it down, you didn't do it. Oral explanation alone is not evidence (ISA 230). The test is whether a stranger could pick up your file and follow your reasoning without you in the room.
I carry that straight into a one-person practice, where the stranger is usually HMRC two years later, or me, having forgotten why I made a call. Every judgment that isn't obvious gets a file note - why I treated a cost as capital, why a provision is the size it is, why a chart of accounts got cut back the way it did. It is the same discipline that now matters under the tighter judgment rules landing on sole practices. The cloud tools log what changed. They don't log why, and the why is the part that has to defend itself.
Should a Cloud Accountant Spend Six Months in Audit?
If you can, yes - and not for the credential. The number of registered audit firms fell 6.9% in 2024 (ICAEW), and mid-tier firms are planning roughly 40% fewer graduate hires while raising school-leaver intake by about 49% (ICAEW). Fewer people now pass through a proper audit room at all.
The FRC found 86% of Tier 1 audits needed no more than limited improvement last year, against just 38% at smaller firms (FRC). The pattern recognition I rely on came from repetition under someone who had seen it before. AI can draft, reconcile, and flag. It cannot yet tell you a clean-looking file feels wrong, because that instinct is built, not installed.
Frequently Asked Questions
What skills does audit experience give you that cloud accounting doesn't?
Three I use constantly: materiality (knowing which numbers matter and which don't), directional expectation (knowing roughly what a figure should be before you check it), and documentation discipline (writing down the reasoning, not just the result). Software certifications teach you to operate a tool. None of these is on the syllabus.
Is it worth doing audit before moving into cloud accounting?
For the pattern recognition, yes. A spell in audit teaches you to start from "prove this is right" rather than "process this." That scepticism is hard to learn later and it transfers directly to spotting a bodged Xero or QuickBooks file. The credential matters far less than the months of repetition.
What do cloud-only accountants tend to miss?
The instinct that something is wrong before they can articulate why. When you have only ever processed numbers the software presented as correct, you trust the presentation. Audit trains you to distrust it until tested, and that habit catches the errors a clean dashboard hides.
If you have inherited a file that looks tidy but doesn't quite sit right, get in touch. Happy to run an audit-style first look over it and tell you whether the instinct is worth acting on.