A statutory audit runs through eight stages: acceptance and independence, planning and risk assessment, evidence collection, testing, exception resolution, working paper preparation, review, and completion and reporting. The stages are sequential in principle and heavily overlapped in practice. In a mid-market Indian engagement the largest share of elapsed time is spent in evidence collection, waiting for the client, and the largest share of chargeable hours is spent in testing, most of which is mechanical matching.

The eight stages

What each stage produces, and what it depends on
Stage	Produces	Blocked by
Acceptance and independence	Engagement letter, independence confirmations, continuance decision	Nothing, usually. This stage is cheap and is often compressed to the point of being a formality.
Planning and risk assessment	Understanding of the entity, identified risks, materiality, the audit programme	The prior year's file, and last year's signed accounts. Also by a temptation to roll forward the programme unchanged.
Evidence collection	Trial balance, ledgers, registers, statements, confirmations, contracts, management schedules	The client. This is where elapsed time goes and where the deadline pressure originates.
Testing	Completed procedures with results	Incomplete or inconsistent data. A register that does not tie sends this stage back to the previous one.
Exception resolution	Each exception investigated and disposed of	The client again, for explanations and documents, and by whoever has to decide what an exception means.
Working papers	A paper per procedure with a written conclusion	In principle nothing, since the paper should be written as the work is done. In practice, by being left until the end.
Review	Review points, their clearance, and sign-off	Reviewer availability, which is concentrated at exactly the time every engagement needs it.
Completion and reporting	Summary of misstatements, representations, the report and the statutory reporting annexures	Unresolved judgements, and anything that should have gone to the partner four weeks earlier.

What each stage produces, and what it depends on

Where the time actually goes

Firms tend to plan as though testing dominates. Elapsed time is dominated by waiting, and chargeable time by the mechanical part of testing. That gap between the two is the reason audit season feels the way it does: teams are idle waiting for one client and overloaded on another, often in the same week.

Evidence collection consumes the most calendar. A request list sent once, followed up by email, with no shared view of what is outstanding, produces weeks of unproductive elapsed time.
Testing consumes the most hours, and within testing the largest single activity is matching one document to another: invoice to ledger, register to statement, balance to confirmation.
Exception resolution is the most interruptible work. Each exception needs a small piece of information from someone else, and the waiting is what makes it expensive rather than the thinking.
Review is the most concentrated, because it can only be done by the few people qualified to do it, all of whom are reviewing everything at once.

The four points where engagements stall

01The data does not tie, and nobody notices until week threeThe purchase register does not agree to the ledger, or the opening balances do not agree to last year's signed accounts. Both are detectable on day one and both invalidate work already done if found later. Reconcile the population before starting anything.
02Document chasing has no shared stateThe team does not know what has been received, the client does not know what is outstanding, and the same document is requested three times. This is an information problem, not a diligence problem, and it is solved by a single list both sides can see.
03Exceptions accumulate without dispositionFifty exceptions are raised in week two and are still open in week six because each needs a client answer and nobody owns the follow-up. Assign each one an owner and a date at the moment it is raised.
04Review happens once, at the endEvery review point arrives when there is no time to clear it properly, so clearances are thin and some points are cleared by agreement rather than by evidence. Reviewing sections as they complete costs the same hours and produces a better file.

Three of these four are failures of coordination rather than of audit skill. They are also the three that a firm can fix without hiring anyone, which makes them the highest-return changes available to most practices.

The Indian statutory calendar makes this worse

Statutory audit, tax audit and GST annual filings cluster into a small number of months, and the same people do all three. A firm's capacity problem is not an average-utilisation problem; it is a peak problem, and averages conceal it entirely.

The practical response is to move whatever can be moved out of the peak. Input credit reconciliation done monthly is the clearest example: the same work, performed through the year, arrives at the audit already complete. Interim testing of transaction cycles is another. Neither reduces the total hours; both reduce the hours that have to happen in the worst eight weeks.

Common practice, not a requirement

Statutory filing deadlines change from year to year, including through extensions granted close to the date. Plan against the firm's own internal deadlines rather than the statutory ones, and confirm the current dates from the relevant authority rather than from last year's plan.

What a well-run engagement looks like from the inside

Two engagements, same client, same team
	Poorly sequenced	Well sequenced
Week 1	Request list sent. Team starts on whatever data has arrived.	Request list sent with a shared status view. Population reconciliations run on whatever has arrived, and gaps reported the same week.
Week 2–3	Testing on an unreconciled register. Exceptions accumulate in a spreadsheet.	Population agreed. Testing runs. Each exception gets an owner and a date as it is raised.
Week 4	Register turns out not to tie. Some testing is redone.	First sections go to review. Points raised while there is time to clear them.
Week 5–6	Working papers written retrospectively from notes.	Papers already exist, having been written as the work was done. Judgement areas already with the partner.
Final week	Everything reviewed at once. Points cleared thinly. Timestamps cluster.	Completion documents, the summary of misstatements, and a report signed on evidence rather than on time pressure.

Two engagements, same client, same team

The difference between the two columns is not effort or skill. It is the order in which things were done, and whether the state of the engagement was visible to everyone working on it.

What to fix first

Reconcile the population in week one, always, before any testing begins.
Give the client a single view of what is outstanding, rather than a chain of emails.
Give every exception an owner and a date at the moment it is raised.
Review sections as they complete, and put judgement areas in front of the partner early.
Write the working paper as the work is done, not from notes afterwards.
Move recurring compliance work out of the peak, so the peak contains only what has to be there.

How we think about this

Lekhya is built around the observation that most of what makes audit season painful is not the difficult part of auditing. It is matching, chasing and coordinating. Automating those does not make the judgement easier and is not meant to: it moves the hours out of the mechanical half so there are more of them left for the half that requires an 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.

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.

The statutory audit workflow, from evidence collection to sign-off