AUD · Ethics and Professional Responsibilities and General Principles · 6 practice questions
AU-C 230 Audit Documentation: Experienced-Auditor Test
Audit documentation must let an experienced auditor with no prior connection understand the work, evidence, and significant judgments. Use the steps below to check a revenue cutoff file before finalizing it.
Try one first
Hint
Apply the documentation sufficiency benchmark: what must the assembled file enable an experienced auditor with no prior involvement to understand?
Answer B. AU-C 230 establishes that audit documentation should be sufficient to enable an experienced auditor, having no previous connection to the engagement, to understand the nature, timing, and extent of procedures performed, the evidence obtained, significant findings, and the conclusions reached. Oral recollection or materials kept outside the assembled engagement file generally do not substitute for documentation that should be in the file; because the documentation completion date has passed and the emails were not included or cross-referenced, the assembled file is deficient.
Why not A: This is tempting because engagement personnel often can recall events and supporting emails may exist, but the sufficiency test focuses on what the assembled file conveys to an independent experienced auditor; memory and archives outside the file do not substitute for required documentation after the documentation completion date.
Why not C: Materiality influences audit focus, but when exceptions or significant findings are identified auditors must document the procedures performed, evidence obtained, and conclusions reached; omitted details cannot be excused solely because the final opinion was unchanged.
Why not D: Retention requirements determine how long documentation must be kept, not whether the assembled documentation is sufficient; being within a retention period does not make an incomplete or deficient assembled file adequate.
Step by step
- Start with the incomplete file
Harbor Co.'s nonissuer audit file contains shipping documents and a conclusion that a revenue cutoff exception was isolated and not material. It lacks testing details, the significant judgment supporting that conclusion, and preparer and reviewer information.
- Document the testing
Record the nature, timing, and extent of cutoff procedures, including the items selected. Shipping documents alone do not show what the auditor tested.
- Record evidence and results
Link the selected shipments to the evidence examined and record the testing results. Include the cutoff exception rather than reporting only the final conclusion.
- Explain the exception's resolution
Document the additional procedures, supporting evidence, and significant judgments behind the conclusion that the exception was isolated and not material. That reasoning requires documentation even if the audit opinion is unchanged.
- Identify preparation and review
Record who performed the cutoff work, its completion date, who reviewed it, and the date and extent of review. A review sign-off does not replace the missing analysis.
- Apply the experienced-auditor test
Ask whether an experienced auditor with no previous connection can follow the cutoff work and significant judgments from the file. Oral explanations may clarify the record but cannot supply missing documentation.
Key points
- Remember: A reviewer should be able to trace the cutoff conclusion without calling the audit team.
- A reasonable cutoff conclusion can still sit in a deficient file.
- Evidence of review and support for the conclusion serve different purposes.
How the exam traps you
- The senior remembers the missing analysis. Document the analysis. Oral explanations may clarify existing documentation, not replace it.
- Shipping documents and a final conclusion are enough. Show the procedures, results, and reasoning that connect the evidence to the conclusion.
- Preparer and reviewer information is merely administrative. Identify who performed and reviewed the work, with the required dates and review extent.
Question 2
Hint
Focus on AU-C 230: would the timing and complexity of judgments or the dollar size more often dictate more detailed documentation?
Answer A. AU-C 230 states that the form, content, and extent of audit documentation depend on factors including the nature of procedures performed and matters requiring significant professional judgment. A late change in an estimation method and the need for several significant auditor judgments to conclude reasonableness typically require more detailed documentation, even if the dollar amount is below overall materiality. Routine confirmation work with no exceptions generally requires less narrative explanation of judgments and conclusions.
Why not B: Tempting because materiality and account size are important audit considerations. It fails because AU-C 230 emphasizes documenting significant professional judgments and the basis for conclusions; size alone does not override the need to document complex or judgmental matters.
Why not C: Tempting because confirmations are persuasive and often documented carefully. It fails here because the confirmations had no exceptions and were routine; the warranty reserve involved a late-method change and significant auditor judgment, which typically requires more detailed documentation than routine confirmation evidence.
Why not D: Tempting because GAAS does require documentation for significant matters. It fails because AU-C 230 permits variation in the extent of documentation: factors such as complexity, timing, exceptions, and significant professional judgment normally result in more detailed documentation for that specific area rather than identical documentation for all significant areas.
Question 3
Hint
Focus on what the engagement file must allow an experienced accountant with no prior connection to understand, and remember the limited role of later oral explanations.
Answer C. Documentation for a review should be sufficient to enable an experienced accountant with no prior connection to the engagement to understand significant issues identified and the basis for conclusions reached. Because going concern was treated as a significant issue, the accountant should document that issue and the basis for the conclusion in the engagement file; oral explanations cannot substitute for absent documentation.
Why not A: This is tempting because candidates sometimes recall that oral explanations can clarify documentation, but oral explanations may only supplement or clarify existing records and do not replace missing documentation of significant issues and conclusions.
Why not B: This distractor relies on the incorrect notion that documentation depends on whether the report is modified. In fact, documentation requirements apply to significant issues encountered and the basis for conclusions reached regardless of whether the report is modified.
Why not D: This confuses review and audit standards. Encountering a significant issue in a review does not automatically convert the engagement into an audit; the problem here is the lack of documentation within the review file, not a failure to change the engagement type.
Question 4
Hint
Focus on what the file must show to someone who was not part of the engagement, not on what the staff auditor remembers afterward.
Answer D. Audit documentation must be sufficient to enable an experienced auditor with no prior connection to the engagement to understand what was done, the evidence obtained, and the conclusions reached. Oral explanations may clarify documentation but cannot substitute for documented procedures, test selections, and results. Because the workpapers lack those details, the documentation is not sufficient.
Why not A: Tempting because a knowledgeable team member remembers the work, but standards require that the file itself provide the documented basis for conclusions; oral explanations alone do not meet documentation requirements.
Why not B: Client-prepared count sheets are evidence, but the auditor must also document what procedures were performed, which test counts were observed, and the results that support the auditor's conclusion, information not provided here.
Why not C: This appeals to a materiality shortcut, but documentation standards are not limited to items that would change the opinion; the workpapers must still document the work performed and the basis for conclusions regardless of whether the opinion would change.
Question 5
Hint
Separate the rule about when the file may be completed from the rule that defines what makes documentation sufficient.
Answer D. Under AICPA GAAS, documentation is sufficient if it enables an experienced auditor with no prior connection to the engagement to understand the work performed, the evidence obtained, and significant professional judgments and conclusions. Oral explanations may help clarify or supplement existing workpapers but cannot by themselves substitute for required written documentation of significant judgments. Being within the 60-day assembly period does not change the governing benchmark for whether the documentation, as currently written, is adequate.
Why not A: Tempting because reviewers often ask team members to explain their reasoning, but GAAS requires written documentation that stands on its own; oral explanation alone is not an adequate substitute.
Why not B: Outcome and materiality influence audit evaluation, yet a substantively reasonable result does not eliminate the requirement to document significant judgments and how contrary evidence was addressed; good results do not cure inadequate documentation.
Why not C: Attractive since the 60-day assembly rule governs when documentation may be completed, but that deadline addresses permissible completion, not the test for whether the file as currently documented is adequate without reliance on oral explanation.
Question 6
Hint
Focus on what audit documentation must show about the work itself, not just the audit conclusion.
Answer C. Under U.S. GAAS (AU-C 230, Audit Documentation), audit documentation should include the identity of the auditor who performed the work and the date the work was completed, as well as who reviewed the work and the date of the review. A clear conclusion does not substitute for these required documentation elements, and oral explanations cannot replace missing documentation.
Why not A: Oral explanations may supplement documentation but do not replace required written documentation identifying the preparer, reviewer, and relevant dates under AU-C 230.
Why not B: Cross-referencing is helpful for organization, but the requirement to document who performed and reviewed the work and the dates is separate; omission of that information is a documentation deficiency regardless of cross-references.
Why not D: While stating the conclusion is necessary, GAAS also requires documentation of who performed and reviewed the work and when; the conclusion alone does not satisfy those documentation requirements.
Common questions
What is the experienced-auditor standard under AU-C 230?
An experienced auditor with no previous connection must be able to understand the documented work, evidence, results, and significant judgments. For the cutoff exception, the file must explain how the team reached its conclusion.
Must audit documentation identify the preparer, reviewer, and dates?
Yes. Document who performed the work and when it was completed, plus who reviewed it and the date and extent of review.
Can oral explanations replace missing audit documentation?
No. The senior may clarify the documented cutoff analysis orally, but cannot use memory instead of documenting the procedures or significant judgments.
Practice AUD like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Requirements for Engagements Documentation
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.