Audit Evidence, Procedures and Documentation

Introduction and context

An audit opinion is persuasive only when it is supported by sufficient appropriate audit evidence and by documentation that enables an experienced auditor, having no previous connection with the engagement, to understand what was done, when it was done, who performed and reviewed the work, and how the conclusions were reached. Audit evidence is therefore not simply a collection of invoices or schedules. It is the information used by the auditor to reach conclusions on which the opinion is based.

This chapter examines the professional judgment involved in obtaining and evaluating evidence. It links the assertions made by management to audit risks, audit procedures, sampling decisions, evidence quality and documentation. The central challenge is to obtain evidence that is both persuasive and proportionate: too little evidence creates an unacceptable risk of an inappropriate opinion, while poorly designed or excessive work reduces efficiency without necessarily improving audit quality.

The discussion is consistent with the principles commonly expressed in International Standards on Auditing (ISAs), especially ISA 230, Audit Documentation; ISA 330, The Auditor’s Responses to Assessed Risks; ISA 500, Audit Evidence; ISA 505, External Confirmations; ISA 520, Analytical Procedures; ISA 530, Audit Sampling; and ISA 580, Written Representations. Applicable law, regulation, ethical requirements and the adopted auditing standards in the relevant jurisdiction must always take precedence.

Learning objectives

By the end of this chapter, a reader should be able to:

• explain the nature, purpose and characteristics of audit evidence;
• distinguish sufficiency from appropriateness and evaluate evidence reliability;
• connect financial statement assertions with tests of controls and substantive procedures;
• select and apply inspection, observation, confirmation, recalculation, reperformance, inquiry and analytical procedures;
• design evidence in response to assessed risks, including risks of fraud and management bias;
• apply professional judgment to sampling and the evaluation of misstatements;
• prepare clear, complete and defensible audit documentation; and
• evaluate the effects of technology, data analytics and artificial intelligence on audit evidence.

1. The nature and purpose of audit evidence

Audit evidence comprises information used by the auditor in arriving at the conclusions on which the audit opinion is based. It includes information contained in the accounting records and other information, such as confirmations, contracts, minutes, external correspondence, physical observations and data obtained through audit technology.

Evidence serves several related purposes. It supports conclusions about management’s assertions, assists in identifying and responding to risks, provides a basis for review and supervision, and establishes accountability for professional judgments. Evidence may support or contradict management’s representations. Contradictory evidence is particularly important: it may indicate an error, fraud, an unreliable source, an ineffective control or an inappropriate accounting treatment.

Audit evidence is not the same as proof in a mathematical or legal sense. Financial reporting involves estimates, judgment and uncertainty. The auditor ordinarily seeks reasonable assurance, not absolute assurance. The persuasiveness of evidence depends on its relevance to the assertion, its reliability, the risk of material misstatement and the extent to which different items of evidence corroborate one another.

Assertions as the bridge between risk and evidence

Assertions are representations, explicit or otherwise, embodied in management’s financial statements. They provide a disciplined basis for designing audit procedures.

Some frameworks separate existence from occurrence and valuation from accuracy; the exact terminology should follow the applicable auditing standard. The important point is that a procedure must be connected to the assertion it is capable of testing.

For example, vouching recorded sales invoices to dispatch documentation primarily addresses occurrence. It does not, by itself, provide strong evidence about completeness because a transaction omitted from the sales ledger cannot be selected for vouching from that ledger. Testing dispatch records forward to the sales ledger is more directly relevant to completeness.

2. Sufficiency, appropriateness and reliability

Sufficiency

Sufficiency is the measure of the quantity of audit evidence. The required quantity is influenced by:

• the assessed risk of material misstatement;
• the materiality of the item or assertion;
• the quality and reliability of available evidence;
• the degree of judgment or estimation uncertainty;
• the effectiveness of relevant controls; and
• the results of previous procedures and identified exceptions.

Higher risk generally requires more persuasive evidence, a larger or more targeted sample, or procedures performed closer to the reporting date. Quantity cannot compensate indefinitely for poor quality. A large volume of internally generated documents may be less persuasive than a small number of reliable, independent confirmations.

Appropriateness

Appropriateness is the measure of the quality of audit evidence—its relevance and reliability. Relevance concerns whether evidence addresses the assertion under examination. Reliability concerns the source, nature and circumstances in which the evidence was obtained.

Evidence is generally more reliable when it is:

1. obtained from an independent external source rather than solely from management;
2. generated directly by the auditor rather than merely reported by an employee;
3. documented or recorded rather than based only on oral explanation;
4. obtained from effective controls or reliable systems; and
5. original rather than copied, altered or reproduced without adequate safeguards.

These are useful generalizations, not automatic rules. An external confirmation may be unreliable if the auditor does not control the confirmation process or if the respondent lacks relevant knowledge. An internally generated report may be persuasive when the related information system and controls have been tested and found reliable. Reliability is contextual and requires professional judgment.

Sufficiency and appropriateness together

The auditor evaluates quantity and quality together. For a high-risk, judgmental valuation, a single management schedule is unlikely to be sufficient or appropriate. The auditor may combine inspection of contracts, independent market data, recalculation, retrospective review and consultation with a specialist. Conversely, for a low-risk, routine balance supported by effective controls, a smaller amount of high-quality evidence may be adequate.

The auditor should also consider contradictory evidence. A confirmation that agrees with the ledger does not eliminate the need to investigate a subsequent cash return, unusual side agreement or evidence that goods were not delivered. Evidence must be evaluated as a body, not as isolated documents.

3. Designing audit procedures from assessed risk

Audit planning follows a risk-response logic:

Financial statement assertion
          ↓
Risk of material misstatement
          ↓
Relevant control and/or substantive response
          ↓
Evidence obtained
          ↓
Evaluation, conclusion and documentation

The assessed risk may arise from inherent risk, control risk, or both. Inherent risk is the susceptibility of an assertion to misstatement before considering related controls. Control risk is the risk that a misstatement will not be prevented, or detected and corrected, by internal control. The auditor’s procedures must respond to the assessed risks rather than merely repeat prior-year programs.

Tests of controls

A test of controls evaluates whether a control operated effectively during the period. It is appropriate when the auditor intends to rely on the control, when substantive procedures alone cannot provide sufficient appropriate evidence, or when understanding control operation is necessary to assess risk.

A well-designed test specifies:

• the control objective;
• the population and period;
• the control owner or performer;
• the evidence that the control operated;
• the nature, timing and extent of testing; and
• the criteria for deviations.

For example, if purchase orders above a threshold require approval by an authorized manager, the auditor may inspect a sample of purchase orders for evidence of approval, verify that the approver had appropriate authority and determine whether the control operated throughout the relevant period. Inquiry alone is normally insufficient because employees may describe an expected process rather than actual operation. Inquiry should be combined with inspection, observation or reperformance.

If deviations are identified, the auditor considers their frequency, nature and effect. A single deviation may be isolated, or it may reveal that the control was not consistently applied. The auditor may increase testing, revise the assessed control risk, or design additional substantive procedures.

Substantive procedures

Substantive procedures are designed to detect material misstatements at the assertion level. They include tests of details and substantive analytical procedures.

Tests of details examine transactions, balances or disclosures directly. Examples include agreeing a receivable balance to a confirmation, inspecting title documents for property, recalculating interest and examining post-year-end payments for unrecorded liabilities.

Substantive analytical procedures evaluate plausible relationships among financial and non-financial data. They are particularly effective where relationships are predictable and data are reliable. They may be used as the primary substantive response for some assertions, but detailed testing is usually necessary where risk is high, relationships are unstable or disaggregation is insufficient.

Direction of testing and completeness

The direction of selection should reflect the assertion. From the accounting records to supporting evidence is commonly called vouching and is useful for occurrence or existence. From source documents to the accounting records is commonly called tracing and is useful for completeness.

This distinction is not absolute. The source document must itself be appropriate for the relevant assertion, and the procedure must be designed to detect the specific type of misstatement being considered.

4. Principal audit procedures

Inspection

Inspection involves examining records, documents or tangible assets. Documentary inspection may address authorization, terms, ownership, timing and accounting treatment. Physical inspection can provide evidence about existence and condition, but it may not establish ownership or value. For example, observing machinery does not prove that the entity owns it; title documents and lease agreements may also be required.

The auditor should consider whether documents are original, whether they could have been altered, who prepared them and whether they are consistent with other evidence. Electronic records require attention to access rights, audit trails, version histories and system-generated changes.

Observation

Observation involves watching a process or procedure being performed, such as an inventory count or control activity. It provides evidence about performance at a particular time. Its limitation is that people may behave differently when observed, and observation does not demonstrate consistent operation throughout the year. Consequently, observation is generally supplemented by inspection or testing of transactions from other dates.

During an inventory count, the auditor may observe count instructions, test counts, damaged goods, movement controls and the treatment of count sheets. The auditor should also reconcile final inventory records to the count results and investigate differences.

External confirmation

Confirmation is audit evidence obtained by a direct written response from a third party. It may address bank balances, receivables, legal terms, inventory held by custodians or loan conditions. Positive confirmation requests ask the respondent to reply whether or not the information agrees. Negative confirmations request a response only when the respondent disagrees and are appropriate only in limited, low-risk circumstances where specified conditions are met.

The auditor should maintain control over selecting recipients, preparing requests, sending them and receiving responses. Non-responses are not confirmations. Alternative procedures might include inspecting subsequent cash receipts, shipping documents or executed contracts, depending on the assertion. A response from an apparently valid email address is not automatically reliable; the auditor may need to verify the respondent’s identity and investigate unusual routing or content.

Recalculation

Recalculation means checking the mathematical accuracy of documents or records. Examples include recalculating payroll, depreciation, interest, tax, discounts and provisions. Recalculation tests arithmetic, not necessarily the reasonableness of assumptions. A correct multiplication of an incorrect useful life does not establish that depreciation is appropriate.

Reperformance

Reperformance is the auditor’s independent execution of procedures or controls originally performed as part of the entity’s internal control. For example, the auditor may independently reperform a bank reconciliation, re-run an automated exception report or recalculate a three-way match between purchase order, goods received note and invoice. Reperformance can be highly persuasive because it is generated directly by the auditor, but it is limited to the item or process reperformed and must consider whether the auditor used complete and accurate inputs.

Inquiry

Inquiry seeks information from knowledgeable persons inside or outside the entity. It is indispensable for understanding processes, litigation, estimates and unusual transactions. However, inquiry alone ordinarily provides less persuasive evidence than inspection, confirmation or reperformance. Responses should be corroborated, especially when they concern fraud risk, management bias, related parties or significant estimates.

Analytical procedures

Analytical procedures involve evaluating financial information through analysis of plausible relationships among financial and non-financial data and investigation of identified fluctuations or relationships that are inconsistent with other relevant information or expected values.

An analytical procedure normally involves four stages:

1. develop an expectation independently of the recorded amount;
2. determine whether the data used are reliable and sufficiently precise;
3. establish an acceptable difference or investigation threshold; and
4. investigate significant differences and obtain corroborating evidence.

A simple expectation may be:

The formula assumes that employee numbers and average cost are relevant drivers, that the period is comparable, and that the underlying data are sufficiently reliable. If 120 employees are expected to cost an average of 4,000 currency units each for the year, expected payroll is 480,000 currency units. If the recorded amount is 525,000, the difference is 45,000 currency units. The auditor must determine whether that difference is material or otherwise significant, and investigate causes such as salary increases, bonuses, new hires or errors. The calculation itself does not prove that either the expectation or the recorded amount is correct.

Analytical procedures may use trend analysis, ratio analysis, reasonableness testing, regression or disaggregation by location, product, month or customer class. Sophisticated methods do not eliminate the need to understand data quality and business context.

5. Sampling and evaluating misstatements

Audit sampling involves applying audit procedures to less than 100% of a population so that every sampling unit has a chance of selection sufficient to provide a reasonable basis for conclusions about the population. The auditor may use statistical or non-statistical sampling, but the design must address the audit objective and sampling risk.

Important design decisions include defining the population, identifying the sampling unit, specifying the deviation or misstatement condition, selecting a method, determining sample size and evaluating results. Monetary-unit sampling may be useful where overstatement risk is important; random selection may provide representative coverage; systematic selection can be efficient if the population has no hidden periodic pattern.

Sample size is not determined by a universal formula. It depends on risk, tolerable misstatement or deviation, expected error, population characteristics and the planned reliance on the procedure. If the auditor expects more errors or permits less error, a larger sample may be necessary. A sample is not automatically representative because it is large; inappropriate population definition or biased selection can invalidate the conclusion.

When a misstatement is found, the auditor determines whether it is isolated, projects it where appropriate, considers its qualitative significance and evaluates its effect individually and in aggregate. Misstatements that are quantitatively small may be qualitatively material if they conceal a change from loss to profit, affect compliance with a covenant, mask unlawful transactions or influence executive remuneration.

6. Evidence in areas requiring significant judgment

Accounting estimates

Estimates create special evidence challenges because the auditor assesses both historical information and forward-looking assumptions. Procedures may include:

• testing how management made the estimate and the mathematical model used;
• evaluating the reasonableness of assumptions and data;
• developing an independent point estimate or range;
• examining subsequent events that provide evidence about conditions at the reporting date; and
• assessing management bias and the adequacy of disclosures.

For expected credit losses, for example, the auditor may test the completeness and accuracy of receivables data, evaluate default assumptions, compare historical loss experience with current conditions and perform sensitivity analysis. A sensitivity analysis does not establish a single correct amount, but it can reveal whether a small change in an assumption would materially alter the conclusion.

Related parties, unusual transactions and fraud

Evidence concerning related parties and unusual transactions often requires procedures beyond routine sampling. The auditor may inspect minutes, contracts and correspondence; inquire of management and those charged with governance; review general ledger accounts for unusual entries; examine connected parties in corporate records; and assess whether transactions have a genuine business rationale.

Fraud risk increases the importance of unpredictability, professional skepticism and corroboration. Management representations are not a substitute for evidence. Journal-entry testing, review of accounting estimates for bias and investigation of significant unusual transactions should be tailored to the assessed risks.

Written representations

Written representations are information provided by management to confirm matters relevant to the audit. They are necessary in many audits, including representations that management has fulfilled responsibilities for preparing the financial statements and providing complete information. They are important but generally less persuasive than independent evidence. If a representation contradicts other evidence or management refuses to provide an appropriate representation, the auditor must investigate the implications and consider the effect on the opinion and on management integrity.

7. Audit documentation

Audit documentation is the record of audit procedures performed, relevant evidence obtained and conclusions reached. It is often called the working papers, although modern documentation is predominantly electronic. Its purposes include:

• demonstrating that the audit complied with professional standards and legal requirements;
• supporting the audit opinion;
• enabling effective supervision, review and quality control;
• assisting continuity on recurring engagements; and
• providing a record for inspections, consultations, litigation or professional accountability.

Documentation should be sufficient to enable an experienced auditor, with no previous connection to the audit, to understand the nature, timing and extent of procedures; the results and evidence obtained; significant matters; judgments; and the conclusions reached. Documentation is not a substitute for performing work. A conclusion written without evidence is not evidence.

Characteristics of defensible documentation

Good documentation is:

• complete: it addresses the audit objective and records exceptions;
• clear: another reviewer can follow the logic without oral explanation;
• contemporaneous: prepared promptly, not reconstructed after the event;
• accurate: names the population, dates, amounts and sources correctly;
• specific: identifies the item tested and the person responsible;
• linked: connects risks, assertions, procedures, results and conclusions; and
• secure: protected against unauthorized access, alteration or deletion.

A workpaper should normally state the objective, source and population, selection method, procedures performed, results, exceptions, resolution, preparer and date, and reviewer and date. Tick marks and abbreviations should be defined. If a reviewer raises a question, the final file should show how it was resolved, not merely that a discussion occurred.

Documentation should distinguish facts from judgments. For example, “three invoices lacked evidence of approval” is a factual result; “control not operating effectively” is a conclusion requiring consideration of the population, deviation rate and control objective.

Assembly, retention and subsequent changes

The audit file should be assembled within the period required by applicable standards and law. After final assembly, documentation should not be deleted or altered casually. If a change is necessary, the auditor should document the reason, the person making the change, the date and the effect of the change. Local retention periods and confidentiality requirements must be observed.

Audit files contain sensitive personal, commercial and financial information. Access controls, encryption, secure transfer, identity management and a documented retention policy are governance requirements, not merely technical preferences.

8. Technology, data analytics and artificial intelligence

Computer-assisted audit techniques can test large populations, identify unusual journal entries, compare datasets and perform continuous or near-continuous monitoring. Data analytics can improve risk assessment and enable disaggregation that would be impractical manually. Examples include duplicate-payment detection, Benford-style screening used cautiously as an indicator, network analysis of related parties and analysis of transactions posted outside normal business hours.

The principal audit issue is not the sophistication of the tool but the reliability and completeness of its inputs and the validity of its logic. The auditor should establish data lineage, reconcile extracted data to the underlying ledger, test interfaces and access controls, document parameters and retain reproducible outputs. An exception report is not evidence of a misstatement until the exception is investigated.

Artificial intelligence may assist with document classification, contract comparison, anomaly detection and summarization. It can also introduce hallucinated explanations, hidden model assumptions, confidentiality risks, automation bias and difficulties in reproducing results. Professional judgment cannot be delegated to an opaque system. The auditor remains responsible for evaluating evidence, validating outputs and documenting how technology informed the conclusion.

9. Illustrative case: Northstar Components Ltd

Background

Northstar Components Ltd manufactures industrial parts and reports a substantial year-end inventory balance. Inventory is held at the company’s factory and at two third-party warehouses. Management’s bonus depends partly on gross profit, creating a possible incentive to overstate inventory or understate cost of sales.

Problem

The preliminary risk assessment identifies existence, condition and cut-off as significant assertions. The company’s perpetual inventory system includes manual adjustments, and one warehouse changed its software during the year. Management provides a year-end inventory listing and states that all goods are owned by Northstar.

Analysis and approach

The audit team designs procedures that respond to the specific risks:

1. It attends the factory and warehouse counts, observes count instructions and performs independent test counts.
2. It records the serial numbers of selected high-value items and later reconciles them to the final listing.
3. It traces selected items from the listing to physical locations to test existence, and traces items observed during the count to the listing to test completeness.
4. It inspects purchase contracts and warehouse agreements to assess ownership, consignment terms and rights of access.
5. It examines goods received notes and dispatch records immediately before and after year-end to test cut-off.
6. It tests inventory adjustments, focusing on manual entries, unusual users and entries posted near year-end.
7. It obtains a confirmation from each warehouse concerning quantities held and the terms under which goods are stored.
8. It tests subsequent sales and reviews ageing reports for evidence of obsolescence.
9. It compares gross margins by product and period and investigates an unusual year-end increase.

The team finds that 8% of a selected product category is obsolete, although management’s provision covers only 2%. It also finds goods held on consignment from a supplier that were included in Northstar’s inventory. A warehouse confirmation initially fails to respond; alternative procedures identify a quantity difference. The difference is projected and evaluated with other identified misstatements.

Outcome

Management records an additional obsolescence provision and removes consigned goods from inventory. The auditor expands testing because the exceptions indicate that controls over inventory adjustments and ownership classification were not consistently effective. The audit documentation records the risk, assertion, population, selection method, test results, consultations, corrected and uncorrected misstatements, and the final conclusion.

Learning points

The case demonstrates that attendance at a count is not sufficient by itself. Existence, completeness, rights, valuation and cut-off require different procedures. It also illustrates the value of combining physical observation, inspection, confirmation, analytical procedures and subsequent-event evidence. Most importantly, exceptions should change the audit response rather than being treated as isolated administrative issues.

10. Challenges, ethics and professional judgment

Evidence decisions involve unavoidable judgment. Time pressure may encourage overreliance on management explanations, standardized programs or prior-year work. Familiarity with management can reduce skepticism, while excessive skepticism without proportionality can make an audit inefficient and adversarial.

Ethical requirements require integrity, objectivity, professional competence and due care, confidentiality and professional behavior. Independence threats are particularly relevant where the auditor prepares evidence, performs management functions, has financial interests or relies excessively on an internal or external specialist. The auditor should identify, evaluate and address threats in accordance with the applicable ethical code.

Governance bodies should receive clear communication about significant difficulties, uncorrected misstatements, control deficiencies, management bias and limitations on evidence. A documentation file that conceals uncertainty is not a high-quality file. Good auditing makes uncertainty visible, explains how it was evaluated and shows why the conclusion remains justified.

Best-practice framework

A practical evidence strategy can be summarized as follows:

1. Start with assertions, not with a predetermined list of documents.
2. Assess inherent and control risks, including fraud and estimation uncertainty.
3. Select procedures that directly address the identified assertion and risk.
4. Prefer independent, direct and corroborated evidence where risk is high.
5. Control the confirmation, data-extraction and sampling processes.
6. Investigate exceptions and contradictory evidence promptly.
7. Evaluate misstatements individually and in aggregate, including qualitative effects.
8. Document the reasoning, not merely the conclusion.
9. Use technology only when data quality, logic, security and reproducibility are controlled.
10. Review the completed file from the perspective of an informed auditor with no prior connection to the engagement.

Chapter Summary

Audit evidence is the information on which the auditor’s opinion is based. Its sufficiency concerns quantity, while its appropriateness concerns relevance and reliability. The required evidence depends on assessed risk, materiality, control effectiveness, estimation uncertainty and the quality of available sources.

Assertions connect management’s financial statements to audit procedures. Tests of controls assess whether controls operated effectively; substantive procedures detect material misstatements through tests of details and analytical procedures. Inspection, observation, confirmation, recalculation, reperformance and inquiry each provide different forms of evidence and have distinct limitations. Analytical procedures require a reliable expectation, sufficiently precise data and investigation of significant differences.

Sampling must be aligned with the audit objective and population, and identified misstatements must be evaluated individually and in aggregate. Estimates, related parties, fraud risks and written representations require heightened skepticism and corroboration. Audit documentation should clearly record the risk, assertion, procedure, evidence, result, judgment and conclusion. Technology can expand audit coverage, but it does not remove the auditor’s responsibility to validate data, logic and outputs. Ethical conduct, independence, confidentiality and professional skepticism underpin every evidence decision.

Key Terms

Audit evidence: Information used by the auditor in reaching conclusions on which the audit opinion is based.

Assertion: A representation by management embodied in the financial statements.

Sufficiency: The measure of the quantity of audit evidence.

Appropriateness: The measure of the quality of evidence, including relevance and reliability.

Relevance: The connection between evidence and the assertion or audit objective.

Reliability: The degree to which evidence can be trusted for audit purposes.

Test of controls: A procedure designed to evaluate whether a control operated effectively.

Substantive procedure: A procedure designed to detect material misstatements at the assertion level.

Test of details: Direct examination of transactions, balances or disclosures.

Analytical procedure: Evaluation of plausible relationships among financial and non-financial data.

Inspection: Examination of records, documents or tangible assets.

Observation: Watching a process or procedure being performed.

External confirmation: Evidence obtained through a direct response from a third party.

Recalculation: Checking the mathematical accuracy of records or documents.

Reperformance: Independent execution of a procedure or control by the auditor.

Inquiry: Seeking information from knowledgeable persons.

Audit sampling: Applying procedures to less than 100% of a population to draw conclusions about that population.

Audit documentation: The record of procedures performed, evidence obtained and conclusions reached.

Professional skepticism: An attitude that includes a questioning mind and critical assessment of evidence.

Written representation: A written statement provided by management to confirm matters relevant to the audit.

Review Questions

Short Answer Questions

1. Distinguish sufficiency from appropriateness of audit evidence.
2. Why is inquiry alone usually insufficient to test the operating effectiveness of a control?
3. Explain the difference between vouching and tracing.
4. State two limitations of observing an inventory count.
5. What information should a defensible audit workpaper normally contain?

Long Answer Questions

1. Explain how assertions, assessed risks and audit procedures are connected in a risk-based audit.
2. Compare inspection, observation, confirmation, recalculation, reperformance, inquiry and analytical procedures, including their principal strengths and limitations.
3. Discuss the factors that influence the sufficiency and appropriateness of evidence in auditing accounting estimates.
4. Explain the role of sampling in audit testing and the factors that influence sample design and evaluation.
5. Discuss the purposes and characteristics of high-quality audit documentation, including requirements relating to subsequent changes and confidentiality.

Analytical / Application Questions

1. A company’s receivables confirmation rate is low, and management claims that all customers agree with the ledger. Design alternative procedures and explain how you would evaluate their persuasiveness.
2. During an inventory count, the auditor finds goods physically present but absent from the inventory listing, and goods listed that are held on consignment. Identify the affected assertions and propose an appropriate audit response.
3. An AI-generated journal-entry exception report identifies unusual postings, but the data extraction has not been reconciled to the general ledger. Explain the risks and specify the steps required before relying on the report.

Multiple Choice Questions with Answers

Question 1

Which characteristic primarily concerns the quantity of audit evidence?

A. Sufficiency

B. Appropriateness

C. Relevance

D. Reliability

Correct Answer: A. Sufficiency

Question 2

Tracing goods received notes to the purchase ledger most directly addresses which assertion?

A. Occurrence

B. Completeness

C. Rights and obligations

D. Classification

Correct Answer: B. Completeness

Question 3

Which procedure generally provides the most direct evidence that a control was actually performed?

A. Inquiry of the control operator

B. Reading the policy manual

C. Reperformance by the auditor

D. Reviewing management’s budget

Correct Answer: C. Reperformance by the auditor

Question 4

A physical inspection of machinery primarily provides evidence about which matter?

A. Existence

B. Ownership

C. Valuation

D. Completeness of liabilities

Correct Answer: A. Existence

Question 5

Why is inquiry alone usually less persuasive than reperformance?

A. Inquiry cannot be documented

B. Inquiry may describe intended rather than actual practice

C. Reperformance is always external evidence

D. Inquiry is prohibited by auditing standards

Correct Answer: B. Inquiry may describe intended rather than actual practice

Question 6

In a substantive analytical procedure, what should the auditor do after developing an expectation?

A. Ignore differences below zero

B. Determine data reliability and an investigation threshold

C. Replace all tests of details

D. Obtain only a management representation

Correct Answer: B. Determine data reliability and an investigation threshold

Question 7

Which procedure is most directly designed to test the mathematical accuracy of a depreciation schedule?

A. Observation

B. Confirmation

C. Recalculation

D. Inquiry

Correct Answer: C. Recalculation

Question 8

A positive confirmation request asks the recipient to:

A. Reply only if the balance is wrong

B. Reply whether or not the information agrees

C. Confirm only the entity’s legal ownership

D. Provide an oral response to management

Correct Answer: B. Reply whether or not the information agrees

Question 9

Which feature is essential to defensible audit documentation?

A. It records conclusions without procedures

B. It is prepared only after the audit report is issued

C. It links risks, procedures, results and conclusions

D. It excludes contradictory evidence

Correct Answer: C. It links risks, procedures, results and conclusions

Question 10

What is a key risk when using an AI-generated audit exception report?

A. The report automatically becomes external evidence

B. The auditor no longer has responsibility for the conclusion

C. The underlying data or model logic may be incomplete or unreliable

D. AI tools cannot process accounting data

Correct Answer: C. The underlying data or model logic may be incomplete or unreliable