AUD · Ethics and Professional Responsibilities and General Principles · 8 practice questions
AU-C 230: What Can Change During Final File Assembly?
AU-C 230 permits administrative file assembly before the documentation completion date, but prohibits deletion afterward until the retention period ends. Below, follow one nonissuer audit file through timely cleanup and a proposed post-completion deletion.
Try one first
Hint
Think about what the standards allow during the post-report administrative assembly period and whether the date in the fact pattern falls within that window.
Answer C. Under AICPA auditing standards for nonissuers, the auditor may complete the administrative assembly of the final audit file on a timely basis after the report release date; the customary limit is no later than 60 days after the report release date. Removing duplicate documents and superseded drafts during that assembly is generally appropriate as long as the final file retains the documentation supporting the procedures performed, evidence obtained, and conclusions reached. Because April 10 is within 60 days of the March 1 report release, the team's actions are allowable.
Why not A: Candidates may confuse client records with the auditor's working papers. Audit documentation is the auditor's property, and management approval is not required to remove redundant or superseded items from the auditor's file when the auditor complies with documentation standards.
Why not B: This option plays on the correct idea that documentation shouldn't be improperly altered after issuance, but it overstates the rule. AICPA standards allow timely administrative assembly activities after the report date, so some removal of duplicates or superseded drafts is permitted.
Why not D: This distractor misapplies retention requirements. The standards require preserving the final audit documentation for the retention period, but they do not require keeping every duplicate or superseded draft that was properly removed during administrative assembly.
Step by step
- Set the audit timeline
Green & Co.'s nonissuer audit report is dated February 20, Year 2, and released March 1, Year 2. The firm's documentation completion date is April 30, Year 2.
- Start with report release
AU-C 230 ordinarily requires final assembly within 60 days after report release, not the report date. Here, count from March 1, not February 20.
- Classify the April 10 cleanup
On April 10, the team removes duplicate inventory pricing schedules and clearly superseded drafts, retaining final documentation supporting the procedures, evidence, and conclusions. This is permitted administrative assembly before April 30.
- Test the April 25 alternative
If the same cleanup occurs on April 25 instead of April 10, it remains permissible before the April 30 completion date. Incorrectly counting 60 days from February 20 would put the cutoff before April 25 and incorrectly prohibit the cleanup.
- Finish administrative assembly
Before April 30, finalize indexing and cross-references for the inventory pricing schedules. These organize existing evidence; they do not involve performing new audit procedures.
- Add the omitted memo
The team may also add an omitted inventory pricing memo prepared and reviewed before March 1. Adding it before April 30 completes the file without new procedures or conclusions.
- Apply the deletion cutoff
If that same cleanup is instead proposed for May 10, do not delete the documents. After April 30, even superseded drafts still in the file must remain until the retention period ends.
Key points
- Remember: The documentation completion date, not report release, stops cleanup deletions.
- Administrative assembly organizes completed audit work; it is not time to perform missing audit procedures.
- After completion, existing audit documentation, including superseded drafts still in the file, must remain until the retention period ends.
How the exam traps you
- Rejecting April 25 cleanup by counting 60 days from the February 20 report date. Count from March 1 release; April 25 is before the April 30 completion date.
- Deleting a superseded draft after completion because the final version remains. Keep existing audit documentation until the retention period ends, even if it is superseded.
- Rejecting an omitted memo because the report has already been released. Add it during timely assembly if it documents work already performed and conclusions already reached.
Question 2
Hint
Focus on whether the audit file is still within the permitted documentation completion (final assembly) period and whether documentation added then may be backdated.
Answer D. AICPA auditing guidance permits completion and assembly of the final audit file for up to 60 days after the report release date. Because the omission was discovered within that permitted assembly period and no additional procedures are needed, the memo should be added now as part of final assembly and show the actual preparation and review dates (do not backdate).
Why not A: Tempting as a conservative approach to ensure an explanatory trail, but incorrect here because the omission was discovered within the permitted assembly period. Waiting would create an after-the-fact addition that would require a late-addition explanation.
Why not B: Tempting because the underlying testing occurred before the report date, but incorrect because backdating would misrepresent when the memo was prepared and reviewed. Documentation added during assembly must reflect actual preparation and review dates.
Why not C: Tempting if one believes the file is frozen at report release, but incorrect because the final audit file can be completed and supplemented during the permitted 60-day assembly period. Relevant documentation should be included in the assembled file, not left only in separate working papers.
Question 3
Hint
First determine whether each change occurs within or after the file-assembly window, then ask what extra documentation is required for later changes.
Answer B. Under AICPA AU-C 230, auditors may complete the final assembly of audit documentation for a limited period after the report release date (generally no later than 60 days). Administrative assembly steps such as removing superseded drafts, adding cross-references, and completing file-assembly checklists (Situation 1 on April 5) are generally acceptable within that window. Changes after the documentation completion date (Situation 2 on June 15) require documentation of the reason for the addition, the date, and who made and reviewed it, and existing documentation should not be deleted or discarded.
Why not A: Tempting because the underlying work was performed before the report, but this answer ignores the timing of the file changes themselves. After the documentation completion date, unrecorded additions and deletions are not permitted without documenting the reason, timing, and responsible reviewer, and original documentation should not be removed.
Why not C: This overstates the rule by treating the file as frozen at report release. AU-C 230 allows a limited post-report assembly period for administrative completion, so Situation 1 can be acceptable; Situation 2 is still improper because it occurs after the completion window and lacks the required documentation and removes existing notes.
Why not D: Partner approval is not the controlling rule for ordinary final assembly steps, and merely noting that the retention period has not expired does not permit unrecorded replacements or deletions after the completion date, such changes must be documented and original documentation preserved.
Question 4
Hint
Distinguish what is permitted during the ordinary final-file assembly period from what is prohibited after the documentation completion date.
Answer A. Under AU-C 230 the auditor may complete assembly of the final engagement file after report release, ordinarily within 60 days, so a memorandum prepared and reviewed before report release may be added during that assembly period. However, once the documentation completion date has passed the auditor must not delete or discard audit documentation; the documentation must be retained for the applicable retention period (under AICPA standards ordinarily at least five years from the report release date), absent a litigation hold or other legal/regulatory requirement.
Why not B: Tempting because it recognizes that administrative assembly after report release is allowed. It is incorrect because AU-C 230 prohibits deleting or discarding audit documentation after the documentation completion date even if a later workpaper summarizes the matter.
Why not C: This misstates the rule: documents prepared and reviewed before report release can be added during the permitted assembly period. Replacing or removing documentation after the documentation completion date remains prohibited.
Why not D: Overstates the prohibition: administrative final-file assembly is permitted within the ordinary assembly period (ordinarily up to 60 days). The stricter prohibition applies after the documentation completion date with respect to deleting or discarding documentation.
Question 5
Hint
Focus on the deadline for completing the final audit file after report release and whether any new information appeared after the report was issued.
Answer B. AU-C 230 establishes the documentation completion date as the controlling cutoff for adding workpapers after report release; for nonissuers the final audit file is ordinarily completed within 60 days of the report release. Because the missing fraud‑brainstorming documentation was discovered on March 20 (within 60 days of the March 1 release) and no new information has arisen, timing relative to the documentation completion date governs whether it may be added now.
Why not A: This option tempts because fraud‑brainstorming is a planning matter and seems to require contemporaneous documentation; however, the standards permit adding missing planning documentation during final assembly if done before the documentation completion date, so the timing cutoff, not simply the item's classification, is the direct governing factor.
Why not C: This is tempting because newly discovered information would prevent simply appending documentation without further work and could affect the report; but the stem states no new information has arisen, and the immediate question is governed by the documentation completion date.
Why not D: This distractor is plausible since changing the report date is necessary when new procedures are performed or new information arises, but merely adding documentation of work already performed within the allowed assembly window does not by itself require changing the report date.
Question 6
Hint
Identify the date on which the engagement file must be finally assembled, then evaluate each action separately based on whether it occurs before or after that date.
Answer C. For a nonissuer audit under AICPA standards the engagement file must be finally assembled no later than 60 days after the report release date (March 1 + 60 days = April 30). An omitted memo added on April 20 is within that assembly period and is permissible to include. The May 10 proposed removal is after the documentation completion date and deleting or discarding audit documentation after that date is not permitted, even if the documents are superseded.
Why not A: Tempting because the underlying audit conclusions weren't altered, but documentation rules are not opinion-dependent: deletions after the documentation completion date are prohibited regardless of whether the opinion would change.
Why not B: This reverses the correct timing rule. The cutoff for final assembly is the documentation completion date (no later than 60 days after report release for nonissuers), not the report release date itself; April 20 is within the allowed assembly period while May 10 is after it.
Why not D: Incorrect, while audit documentation should support the report by the release date, the standards allow a post-release assembly period (up to 60 days for nonissuers) during which additions to the file are permitted; the file is not locked on the release date.
Question 7
Hint
Decide separately whether each action occurred before or after the documentation completion date and recall what AU-C 230 permits during administrative assembly.
Answer C. AU-C 230 permits administrative assembly of the engagement file, including removing duplicate copies and superseded drafts, up to the documentation completion date. Because the March 25 deletions occurred before the April 30 documentation completion date, they were appropriate. After the documentation completion date, the auditor should not delete or discard audit documentation until the required retention period ends; therefore the May 10 removal was not appropriate.
Why not A: This distractor tempts by focusing on relevance, removing irrelevant or duplicative items seems reasonable. It fails because it ignores the timing rule: GAAS (AU-C 230) allows such removals only during assembly before the documentation completion date; deletions after that date (May 10) are prohibited.
Why not B: This choice tempts by confusing the auditor's report release with the documentation completion date. It fails because AU-C 230 permits administrative assembly through the documentation completion date even if the report has been issued; the improper action here is the May 10 removal (after the documentation completion date), not the March 25 deletions.
Why not D: This distractor tempts by adopting an overly conservative 'keep everything' approach. It fails because AU-C 230 allows removal of duplicate copies and superseded drafts during timely assembly of the final file; thus the March 25 deletions were permitted even though some materials must be retained through the retention period.
Question 8
Hint
First decide whether the 60-day assembly period starts on the report date or the report release date, then determine whether the memo documents work completed before the release.
Answer B. AU-C 230 states that for a nonissuer the auditor ordinarily should complete the final assembly of the audit file not more than 60 days after the report release date. The report was released on February 10, 20X6, so April 5, 20X6 falls within the 60-day assembly period. Because the memo documents work completed before release and no existing documentation will be deleted or altered, adding the omitted memo is appropriate.
Why not A: This is tempting if a candidate measures the 60-day period from the report date. It fails because AU-C 230 measures the 60-day documentation completion period from the report release date (February 10) for nonissuers, so April 5 is still within the allowed window.
Why not C: This choice appeals to the correct notion that substantive changes to conclusions after issuance can require reissuance or dual-dating. It is incorrect here because the memo documents work completed before the report was released and is being added during the permitted 60-day assembly period, so dual-dating or reissuing is not required.
Why not D: This distractor is tempting because many believe post-release additions always require formal justification or report revision. It fails here because AU-C 230 permits additions made within the 60-day assembly period when they document work performed before release and do not delete or alter existing documentation.
Common questions
When does the AU-C 230 60-day period start?
The ordinary 60-day assembly period runs from report release, not the report date. Here, March 1 controls, making April 25 cleanup timely.
Can you add an omitted memo during final audit file assembly?
Yes. The omitted inventory pricing memo may be added before April 30 because it documents work completed and conclusions reached before report release.
Can superseded drafts be deleted after the documentation completion date?
No. Even superseded drafts still in the file must remain until the retention period ends, so keeping the final version does not permit the May 10 deletion.
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.