Good audit work is only as strong as the evidence and documentation behind it. When auditing revenue, technical knowledge matters, but so does demonstrating clearly how you identified risks, responded to them, and reached your conclusions.

Revenue remains one of the most scrutinised areas of an audit. It carries a presumed fraud risk, involves significant judgement, and often requires auditors to bring together analytical procedures, substantive testing and professional scepticism.

In Auditing the Revenue Cycle, Lungi Sepotokele gives the practical lessons that matter most when auditing the revenue cycle.

Start with a thorough risk assessment

Before any testing begins, your planning documentation should clearly explain why revenue represents a higher-risk area for the engagement.

For most audits, revenue carries:

• High inherent risk
• High control risk
• A presumed fraud risk under ISA 240

Rather than simply stating these risks, your planning memo should explain how they apply to the client. Factors such as an owner-managed business, significant cash transactions or limited segregation of duties all influence the assessment.

The key objective is to demonstrate that your audit response is tailored to the entity rather than copied from a previous file.

Understand the client's revenue system

An effective revenue audit begins with understanding how revenue flows through the business.

That means documenting:

• How sales are generated
• Which systems process transactions
• How revenue reaches the accounting records
• The controls operating throughout the process

Revenue should never be viewed in isolation. Cash controls, management reporting, system access and reconciliation processes all contribute to your understanding of the overall control environment.

A well-documented walkthrough often provides valuable evidence later in the audit.

Analytical review should drive your audit

Analytical procedures are far more than a planning exercise.

Before selecting any samples, perform detailed analysis of the revenue population. Depending on the business, this may include:

• Month-by-month sales trends
• Product or service mix
• Price movements
• Sales volumes
• Gross margin analysis
• Comparison with industry expectations

The purpose is not simply to produce graphs. It is to identify unusual movements, generate meaningful audit questions and support your overall risk assessment.

Strong analytical work can also justify adjustments to your sampling approach where appropriate.

Set materiality carefully

Materiality affects almost every decision throughout the audit.

When establishing materiality:

• Use an appropriate benchmark for the engagement.
• Document why that benchmark was selected.
• Record performance materiality and trivial misstatement thresholds.
• Reassess the benchmark if significant business changes make the previous year's figures less representative.

Equally important is documenting the rationale behind these decisions so that a reviewer can follow your thinking.

Make sampling decisions defensible

One of the most common documentation weaknesses is unexplained sample selection.

If your methodology suggests one sample size but professional judgement leads you to reduce it, record why.

Similarly, if particular months or transactions are selected for testing, explain the rationale.

Examples may include:

• Significant seasonal trading
• Unusual monthly fluctuations
• Higher-risk periods
• Results identified during analytical review

Professional judgement is entirely appropriate, provided it is properly documented.

Test completeness from several angles

Completeness is one of the most challenging revenue assertions.

No single procedure provides complete assurance, so auditors often combine multiple approaches, including:

• Reconciliation of sales reports to accounting records
• Comparison with VAT returns
• Till or point-of-sale reconciliations
• Cash receipt testing
• Cut-off testing around the year end
• Trend and ratio analysis

The objective is to build a body of evidence that supports the conclusion rather than relying on one procedure alone.

Don't overlook cut-off testing

Revenue cut-off frequently becomes an afterthought because it is often performed alongside cash, bank or debtor testing.

Nevertheless, it remains a key audit procedure.

Rather than selecting an arbitrary number of transactions, document why the selected period or sample provides appropriate coverage of year-end transactions.

The focus should be on demonstrating that revenue has been recognised in the correct accounting period.

Conclude every stage of your work

One weakness often found during file reviews is the absence of clear conclusions.

Each section of testing should answer a simple question:

What did the work show?

Whether you are completing analytical procedures, reconciliations, sample testing or disclosure reviews, conclude each section with a clear summary of your findings.

Your final analytical review should also explain whether the overall movements in revenue remain consistent with your understanding of the business and the evidence gathered during the audit.

Common documentation weaknesses to avoid

Several recurring issues appear during audit file reviews:

• Generic documentation that does not reflect the client's business.
• Unexplained sample selection.
• Insufficient supporting evidence.
• Weak or missing cut-off testing.
• Incomplete documentation of completeness testing.
• Missing conclusions after testing.
• Failure to complete final analytical review procedures.

Most of these issues do not arise because the testing was inadequate. They arise because the documentation does not demonstrate what work was actually performed.

Final thoughts

Auditing revenue is about more than completing an audit programme.

A well-executed audit demonstrates a clear understanding of the business, applies professional judgement consistently and produces documentation that allows another experienced auditor to understand the work performed and the conclusions reached.

When planning, analytical review, substantive testing and documentation all support one another, your audit file becomes significantly stronger.

The contents of this article are meant as a guide only and are not a substitute for professional advice. The authors accept no responsibility for any action taken, or refrained from, as a result of the material contained in this document. Specific advice should be obtained before acting or refraining from acting, in connection with the matters dealt with in this article.