Moving off Excel costs a firm the total flexibility of a blank spreadsheet and the comfort of a tool every staff member already knows, and gains it a single current version of every working paper, an enforced review and sign-off trail, and checks that run the same way on every file instead of depending on who built the formula. The honest first-engagement timeline is slower than the old process for several weeks before it is faster, and firms that expect otherwise read early friction as a failure rather than a normal cost of switching.
What Excel is actually good at
Excel's advantage is not something a firm should talk itself out of valuing. A spreadsheet can be shaped into whatever a specific engagement needs, with no configuration step and no vendor involved. Every staff member already knows the tool, so there is no training cost. For a one-off schedule or an unusual client, this flexibility is real and audit software does not fully replace it.
What Excel does not do on its own is enforce anything. It does not know which version of a file is current, does not require a reviewer to sign off before a figure is treated as final, and does not stop two people from editing two copies of the same schedule at the same time. Those gaps are invisible on a small file reviewed by one person. They are where almost all Excel-related audit problems actually happen, and they get worse as the file, the team and the review chain grow.
The version-control problem, specifically
A typical engagement file passes through a preparer, a reviewer, sometimes a second reviewer, and the partner, often over several weeks and several rounds of changes. In Excel, each pass usually means a new copy of the file, saved with a new name or date, emailed or dropped into a shared folder. Nothing in the tool enforces which copy is the one the opinion is based on.
| Situation | What goes wrong |
|---|---|
| A reviewer comments on a copy, the preparer is mid-edit on a different copy | The review comments apply to a version that no longer exists, and resolving them means reconstructing what changed |
| Two team members update different tabs of the same workbook independently | Whichever save happens last silently overwrites the other's work, with no warning and no record of what was lost |
| A figure is corrected after the reviewer has already signed off | The sign-off now sits against a version of the figure that no longer exists in the file, and nothing flags the mismatch |
| The file is reopened a year later for a regulatory query | Reconstructing exactly which version supported the final opinion, out of a folder of similarly named files, becomes archaeology |
The failure mode here is rarely a dramatic one. It is a reviewer who signed off on a schedule that was later quietly edited, with no trace of the edit in the file itself. Nobody acted in bad faith. The tool simply never recorded which version the sign-off actually attached to.
What a firm gains, specifically
- One current version of each working paper, with a record of what changed, when, and by whom.
- A sign-off that attaches to a specific, identifiable state of the file, not to whichever copy happened to be open at the time.
- Checks — matching, totals, reconciliations — that run the same way on every file, rather than depending on whether the specific preparer built a correct formula.
- A structure that makes the prior year's working papers a starting point for the next engagement, rather than a folder to be searched by hand.
What a firm loses, honestly
- The ability to build an unusual schedule from scratch in five minutes, exactly shaped to one client's quirks, with no configuration step.
- The zero training cost of a tool every new hire already knows from school or a prior job.
- Full control over formatting and layout, which audit software deliberately constrains in exchange for consistency across the firm.
A realistic timeline for the first engagement
Firms that expect the new system to be faster from week one are the ones most likely to abandon it after a bad first season. A more realistic shape for the first engagement looks like this.
- 01Weeks 1-2: visibly slower than ExcelStaff are learning where things live in the new structure while still thinking in spreadsheet terms. Expect the same work to take noticeably longer than it would have on the old process.
- 02Weeks 3-4: roughly evenThe team stops fighting the tool's structure and starts using its built-in checks instead of rebuilding them. Speed on routine sections catches up to the old process.
- 03Week 5 onward: faster on repeatable sectionsSections that followed a fixed procedure in Excel — matching, reconciliations, standard checklists — start running faster than the manual equivalent, because the check itself is now built in rather than rebuilt each time.
- 04The following engagement: the real comparison starts hereThe first engagement on new software is partly a training exercise. The second and third are where the honest comparison against the old process should be made.
Common practice, not a requirement
Running the very first engagement on a new system for a client with a tight deadline is a common and avoidable mistake. The slower first weeks described above are easiest to absorb on a file with runway to spare, not on the one the firm can least afford to run late.
How we think about this
Excel is not the problem. The problem is that nothing in a spreadsheet records which version an opinion was actually based on, or who checked what before signing it. Lekhya's working papers exist specifically to close that gap — a single current version, a visible history of what changed, and a sign-off that attaches to a defined state of the file — while leaving the judgement that goes into the file exactly where it has always belonged, with the auditor.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- Technology, data & AI in auditAudit software implementation: a firm's checklistThe sequence that works: migrate data deliberately, pilot on one engagement before rolling out firm-wide, and configure methodology before anyone's deadline depends on it.
- Technology, data & AI in auditAudit software ROI for small CA firms: how to think about itA worksheet a firm fills in with its own numbers: hours on repetitive matching, the value of partner time, and what that adds up to before and after.
- Technology, data & AI in auditContinuous audit vs periodic audit: which fits a firmWhat actually changes for staffing and client relationships when testing moves off the year-end crunch, and where a year-end wrap-up is still unavoidable.
- Audit workflow & automationEvaluating audit software for an Indian CA firmWhat to test before buying: Indian data and calendar, evidence traceability, review and sign-off, data handling, and the questions vendors find hardest.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.