We use cookies to understand which pages and tools are useful, nothing more — no ad tracking across other sites. You can change this later from the footer.

Skip to content
Lekhya.in

Explainer6 min readPublished

Continuous audit vs periodic audit: which fits a firm

The practical difference between testing throughout the year as transactions occur and the traditional year-end crunch: what changes for staffing and client relationships, and where continuous testing still needs a year-end wrap-up.

A periodic audit concentrates testing into a block of weeks after the year end, once the full year's data is available. A continuous audit tests transactions and controls throughout the year as they occur, so that by year end much of the routine testing is already done and what remains is review, confirmation of balances that only exist at year end, and forming the opinion. Neither removes the need for year-end work; continuous testing shrinks it and changes its shape, from first discovery of problems to confirmation of what has already been tracked.

What each actually looks like

A periodic audit's defining feature is not that it happens once a year, it is that the team sees the full year's data for the first time only after the year has closed. Every control and substantive test for the whole twelve months is performed in a compressed window, against a population that has already finished changing.

A continuous audit tests in smaller slices throughout the year — monthly or quarterly reconciliations reviewed as they are produced, exceptions from ongoing checks surfaced when they happen rather than discovered months later, interim testing of controls on a rolling basis. The year-end phase inherits a population that has already been substantially tested, with a shorter list of open items.

The same work, differently timed
AspectPeriodic auditContinuous audit
When an error is foundMonths after it occurred, often close to or after the reporting deadlineWithin the period it occurred, closer to when it can still be corrected
Staffing shapeA sharp peak of demand concentrated around year endSpread more evenly, with smaller, more frequent commitments through the year
Client interactionConcentrated contact during the audit window, limited contact otherwiseRegular contact throughout the year, closer to an ongoing relationship
What's left at year endNearly everythingBalance confirmations, period-end-only procedures, and forming the final opinion
The same work, differently timed

What changes for staffing

The year-end staffing crunch in most firms is not really about the total hours an audit takes. It is about all those hours landing in the same six-to-eight week window across every client simultaneously. Continuous testing does not reduce the total work by any figure worth stating here — that depends entirely on the firm and the engagement — but it changes when the work happens, which is often the more pressing constraint in practice.

  • Staff work in smaller, steadier blocks through the year rather than one long concentrated push, which can reduce the extreme overtime that clusters around traditional deadlines.
  • Staff assigned to continuous testing need to be available in smaller increments spread across the year, which changes how a firm schedules leave, training and bench time.
  • Knowledge of a client accumulates gradually across the year instead of being relearned from scratch each audit season, which can make year-end review faster because less is unfamiliar.
  • A firm running some clients continuously and others periodically needs two different staffing rhythms running at once, which is its own coordination cost.

What changes for the client relationship

A periodic audit relationship is often concentrated: intense contact during the audit window, little contact the rest of the year. Continuous testing means the auditor is in the client's data and raising questions throughout the year, which changes the relationship from an annual event to something closer to ongoing oversight.

This has a real upside: a control weakness or an unusual transaction surfaces while the client can still do something about it, rather than as a year-end finding after the period it relates to has closed. It also has a real cost: client staff who were used to one intense season now field audit queries on a rolling basis, which some clients experience as ongoing scrutiny rather than a defined, bounded engagement.

Common practice, not a requirement

Clients who value the relationship benefit — early warning, fewer year-end surprises — tend to be the better fit for continuous testing. Clients who specifically value a bounded, predictable audit window with minimal contact outside it may experience continuous testing as an intrusion rather than a service improvement, regardless of its technical merits.

Where a year-end wrap-up is still unavoidable

Continuous testing shrinks the year-end phase. It does not eliminate it, and treating it as if it did is where firms run into trouble.

  • Balances that only exist at a point in time — the year-end cash balance, the year-end receivables ageing, closing inventory — have to be tested as of that date regardless of how much was tested during the year.
  • Transactions in the final days or weeks of the year, including anything processed in the gap between the last interim test and the year end, still need coverage.
  • The opinion itself is formed at year end, on the full year's evidence taken together, not assembled piecemeal as each interim test is completed.
  • Events after the year end that bear on the financial statements still need to be considered, and this review only happens once the year has actually closed.

A firm that treats strong interim testing results as a reason to scale back year-end procedures is making an assumption that the period between the last interim test and the year end behaved the same way as the rest of the year. That gap is exactly where problems introduced late, or control changes made near the deadline, tend to hide.

Which fits a firm

Continuous testing suits clients with a steady volume of transactions through the year, reasonably stable systems, and a willingness to engage with the auditor outside the traditional audit window. It suits firms with the staffing flexibility to work in smaller, spread-out blocks rather than one concentrated push. It is a weaker fit for clients with highly seasonal activity concentrated near year end, or for firms structured entirely around a single annual engagement rhythm, where the coordination cost of running one client continuously alongside others periodically may outweigh the benefit for just that one relationship.

How we think about this

The appeal of continuous testing is not that it is more thorough in some abstract sense. It is that finding a problem in month four, while it can still be fixed, is more useful to everyone than finding the same problem in month fourteen, when the year it occurred in has already closed. Lekhya is built so the same checks a firm runs at year end can be run on data as it arrives through the year, without building two separate processes for the same testing.

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.