Audit evidence is the information the auditor uses to reach conclusions and support the audit opinion. Under ICAI SA 500, it includes both the accounting records underlying the financial statements and information obtained from other sources. That sounds simple, but most audit disputes arise from a harder question: not whether some evidence exists, but whether the evidence obtained is sufficient, appropriate, and linked to the assertion actually being tested.
For Indian audit work, the core reference point is SA 500, Audit Evidence. It works alongside SA 230 on audit documentation, SA 505 on external confirmations, and SA 530 on audit sampling.
Why audit evidence matters
An audit opinion is not based on management explanation alone. SA 500 requires the auditor to design and perform procedures that obtain sufficient appropriate audit evidence so that reasonable conclusions can be drawn. If the evidence is weak, inconsistent, incomplete, or unrelated to the relevant assertion, the audit conclusion is weak even if the file is bulky.
That is why audit evidence matters in three ways:
- It connects audit procedures to the opinion.
- It determines whether a conclusion is defensible under professional standards.
- It affects whether the working papers show a clear basis for review, quality control, and regulatory inspection.
The two tests: sufficiency and appropriateness
Audit evidence is judged on two dimensions.
Sufficiency
Sufficiency is the quantity of evidence. Higher assessed risk usually requires more evidence. Better quality evidence may reduce how much is needed, but more low-quality evidence does not cure a quality problem.
Appropriateness
Appropriateness is the quality of evidence. Under SA 500, this is mainly a question of relevance and reliability.
- Relevance: Does the evidence address the assertion being tested, such as existence, completeness, valuation, rights and obligations, cut-off, or presentation?
- Reliability: Is the source dependable, and is the form of evidence persuasive in the circumstances?
A common audit failure is using relevant but unreliable evidence, or reliable evidence that addresses the wrong assertion.
How reliability usually changes from one source to another
SA 500 does not create a rigid ranking that applies in every case, but its guidance supports some durable professional patterns.
| Evidence source or form | Why it is often stronger | Important limit |
|---|---|---|
| Direct auditor observation or recalculation | The auditor obtains it directly | It may prove only what existed or happened at that point in time |
| External confirmation from an independent third party | Independent source outside the entity usually improves reliability | Non-response, restrictive wording, or confirmation risk can reduce value |
| Externally generated documents held by the entity | Source is outside the entity | Authenticity and completeness still matter |
| Internally generated reports tested for accuracy and completeness | Can be useful when underlying controls and data are reliable | Cannot be used safely without evaluating how the report was produced |
| Management inquiry | Helpful for understanding context and identifying leads | Inquiry alone is ordinarily not enough to prove absence of material misstatement or operating effectiveness of controls |
| Written representation | Can confirm oral statements or management intent | It supplements other evidence; it is not a substitute for procedures that should have been performed |
The practical lesson is straightforward: the best evidence is usually evidence that is relevant to the assertion, obtained from a reliable source, and corroborated by another source or procedure.
What counts as audit evidence in day-to-day work
In real engagements, audit evidence is usually built from a combination of procedures rather than a single document. SA 500 discusses the main procedures used to obtain it:
- Inspection: examining records, documents, or physical assets.
- Observation: watching a process or control being performed.
- External confirmation: obtaining direct written responses from third parties.
- Recalculation: checking mathematical accuracy.
- Reperformance: independently executing a procedure or control.
- Analytical procedures: evaluating plausible relationships among financial and non-financial data.
- Inquiry: seeking information from knowledgeable persons inside or outside the entity.
No single procedure is universally sufficient. For example, a receivable balance supported only by the ledger is usually weak. The same balance supported by the ledger, post year-end receipt testing, customer confirmation, and a review of disputes is much more persuasive.
Assertion-led thinking is more useful than document-led thinking
Junior teams often ask, “What document should I collect?” A better question is, “Which assertion am I trying to prove?” The same document can be useful for one assertion and weak for another.
| Area | Assertion | Evidence that helps | What it may not prove by itself |
|---|---|---|---|
| Inventory | Existence | Physical count observation, count sheets, reconciliation | Ownership or valuation |
| Trade receivables | Existence | Customer confirmation, subsequent receipts, invoices | Expected credit loss adequacy |
| Revenue | Cut-off | Dispatch records, e-way data where relevant, invoices near year end, contract terms | Whether the sale is collectible |
| Fixed assets | Existence | Physical verification, asset tags, purchase records | Useful life or impairment |
| Provisions | Valuation | Underlying assumptions, management expert work, subsequent events, legal correspondence | Completeness of all obligations if search procedures were weak |
When internal information can still be good evidence
Internal data is not automatically weak. SA 500 specifically requires the auditor, when using information produced by the entity, to evaluate whether it is sufficiently reliable. That includes testing its accuracy and completeness and assessing whether it is precise enough for the audit purpose.
Example: suppose the auditor uses an ageing report to test receivables and expected credit loss.
- If the report is generated from the ERP, tied to the ledger, tested for completeness, and reviewed against subsequent collections, it may be strong evidence.
- If the report is a manually edited spreadsheet with no version control and unexplained overrides, it may be too unreliable to support the conclusion without further work.
Management experts and specialist inputs
Some balances depend on expertise outside accounting or auditing, such as actuarial valuations, legal estimates, environmental obligations, or technical asset valuation. SA 500 requires the auditor, where information has been prepared using a management expert, to evaluate the expert's competence, capabilities and objectivity, understand the work performed, and assess whether that work is appropriate audit evidence for the relevant assertion.
Using an expert's report is therefore not a shortcut. The auditor still has to evaluate whether the assumptions, scope, data used, and conclusions fit the financial reporting issue being audited.
How auditors choose items for testing
SA 500 explains three broad ways to select items for testing:
- Testing all items in a population or stratum.
- Selecting specific items.
- Using audit sampling.
Each serves a different purpose. Testing all items may be suitable where the population has a small number of large-value items or where risk is significant. Selecting specific items may be efficient for unusual or high-risk transactions, but the result cannot be projected to the entire population. If the auditor wants a conclusion about the whole population, audit sampling under SA 530 becomes relevant.
Practical examples with explicit assumptions
Example 1: Trade receivables at year end
Assumptions: A manufacturing company has trade receivables of Rs. 4 crore as at March 31. The top 12 customers make up 70% of the balance. There is no major system change during the year.
A stronger evidence mix could include customer confirmations for major balances, testing of collections received after year end, examination of invoices and dispatch records for year-end sales, review of credit notes issued after year end, and testing the ageing report used for impairment analysis.
What this resolves:
- Existence is supported by confirmations and subsequent receipts.
- Cut-off is supported by dispatch and invoicing evidence around year end.
- Valuation is addressed through ageing reliability, dispute review, and collection history.
What would be weak by itself: a debtor schedule printed from the ERP plus management explanation that all balances are recoverable.
Example 2: Inventory at multiple locations
Assumptions: A trader carries inventory at a head warehouse and three third-party depots. Inventory is material to the financial statements.
A stronger evidence mix could include attendance at physical count where feasible, test counts, reconciliation to stock records, cut-off testing for goods received and dispatched near year end, and confirmations or statements from third-party custodians for depot stock.
What this resolves:
- Existence is supported by count observation and third-party confirmations.
- Completeness is supported by reconciliation and cut-off testing.
- Rights and obligations may need depot agreements or other title evidence; physical count alone does not prove ownership.
What to do when evidence conflicts
SA 500 requires the auditor to respond when evidence from one source is inconsistent with evidence from another, or when there are doubts about reliability. The answer is not to choose the more convenient document. The auditor should modify or add procedures until the inconsistency is resolved, and consider whether the issue affects other parts of the audit.
For example, if management says a balance is undisputed but external confirmation shows a customer dispute, the issue is not limited to that one debtor. It may also affect revenue cut-off, allowance for expected credit loss, and possible control deficiencies in the sales cycle.
Documentation: when evidence becomes audit-ready
Evidence that is not properly documented may be difficult to defend later. Under SA 230, documentation should be sufficient for an experienced auditor with no previous connection to the engagement to understand the procedures performed, the results, the evidence obtained, and the significant judgments and conclusions reached.
That means a good working paper usually shows:
- The assertion and audit objective.
- The population and how items were selected.
- The exact procedure performed.
- The source of evidence and why it is reliable enough in the circumstances.
- The result of the procedure.
- The conclusion reached and any follow-up required.
If contradictory information was identified on a significant matter, SA 230 also requires documentation of how the inconsistency was addressed.
Common misunderstandings
- More papers always mean better evidence. Volume does not compensate for weak relevance or poor reliability.
- Management representation can replace substantive work. It cannot replace procedures required by the circumstances.
- Physical verification proves everything. It may prove existence, but not necessarily ownership, completeness, or valuation.
- A system report is enough because it came from the ERP. Reports still need testing for accuracy, completeness, and suitability for the audit purpose.
- Specific item testing is the same as sampling. It is not; results from selected items cannot automatically be projected to the population.
A short decision framework for practice
- Start with the assertion, not the document.
- Ask what could go wrong in that balance, class of transactions, or disclosure.
- Select procedures that directly address that risk.
- Prefer corroboration from another source or another type of procedure where risk is higher.
- Test internally generated information before relying on it.
- Resolve inconsistencies rather than filing them away.
- Document the conclusion so that another experienced auditor can follow the reasoning.
When understood this way, audit evidence is not just a file requirement. It is the discipline that converts audit work into a supportable professional opinion.
