Hello! Welcome to your final lesson in the Audit Evidence and Documentation module.
In our previous lessons, we've built a comprehensive understanding of audit documentation, from its fundamental purpose to the detailed requirements for recording significant matters and professional judgments under SA 230. You've learned what to document and why it's crucial for demonstrating the quality of your audit work.
Today, we'll cover the final, critical administrative steps that ensure the integrity and longevity of that documentation. This lesson addresses the practical, rule-based procedures that happen after the audit opinion is signed. These rules, primarily from SA 230 and Standard on Quality Control (SQC) 1, are precise and frequently tested in exams through MCQs and case studies. Mastering them is key to providing the exact technical answers ICAI expects.
By the end of this 60-minute lesson, you will be able to explain the requirements for assembly and retention of the final audit file.
1. From Raw Data to a Coherent "Audit File"
During your articleship, you and your team members likely generated a large volume of working papers, checklists, and evidence for different audit areas. SA 230 makes a distinction between this collection of "audit documentation" and the final, organized "audit file."
An audit file is defined as one or more folders or other storage media (physical or electronic) containing the records that comprise the audit documentation for a specific engagement. The process of turning scattered documentation into this organised file is called "assembly."
To understand this distinction and the logic behind the assembly process, let's watch a short video.
CA Inter audit revision series (Eng) | Audit Documentation and Evidence | New Scheme | CA Mahamood
This clip from CA Mahamood Shaik clearly explains the conceptual difference between the raw 'audit documentation' gathered during an audit and the organized, final 'audit file'.
Watch the video from 00:58:02 to 01:01:25. Focus on the practical example of different team members holding documentation for different areas (purchases, sales, etc.) and the need to compile them into a single, organised file.
As the video explains, the assembly of the final audit file is the process of organising the various pieces of documentation into a coherent, structured record. It's about creating a single, complete, and final set of documents that supports the auditor's report.
2. The Assembly Process: Rules and Timelines
The assembly of the audit file is not an open-ended task. SQC 1 provides strict rules on the timing and nature of this process.
a) The 60-Day Window
The primary rule is about the timeline. The administrative process of assembling the final audit file must be completed on a timely basis after the date of the auditor’s report.
[PDF] Implementation Guide to Standard on Auditing (SA) 230 Audit ...
The ICAI's Implementation Guide to SA 230 provides the exact wording on the timeline. Knowing this specific detail is crucial for your exams.
Please read Question 32 (Q32) titled 'When should the auditor complete the administrative process of assembling the final audit file?'. Note the specific time limit mentioned.
As stated in the guide and SQC 1, the time limit to complete the assembly of the final audit file is ordinarily not more than 60 days after the date of the auditor's report.
This 60-day period is an absolute key takeaway for your exams.
b) An Administrative Process
It is critical to understand that this assembly process is purely administrative. It does not involve:
- Performing new audit procedures.
- Drawing new conclusions.
The audit work is finished by the date of the auditor's report. The 60-day window is simply for housekeeping—organising the evidence and conclusions that have already been gathered and reached.
So, what changes are permissible during this administrative process? Let's turn back to the ICAI's guide for a definitive list.
[PDF] Implementation Guide to Standard on Auditing (SA) 230 Audit ...
Question 33 of the Implementation Guide lists examples of permissible administrative changes. This directly answers the type of 'what-if' scenarios you might see in exam questions.
Read the answer to Question 33 (A33), focusing on the bulleted examples of administrative changes.
Examples of permissible administrative changes within the 60-day window include:
- Deleting or discarding superseded documentation (e.g., old drafts).
- Sorting, collating, and cross-referencing working papers.
- Signing off on completion checklists related to the file assembly process.
- Documenting audit evidence that was obtained, discussed, and agreed with the team before the date of the auditor's report.
3. Retention of the Audit File: Safeguarding the Evidence
Once the audit file is assembled, the auditor has a responsibility to safeguard it for a specific period. This is not just a firm policy; it's a requirement of SQC 1.
The following video explains both the assembly timeline and the subsequent retention period.
Ch. 6 - Audit Documentation Full | SA 230 | CA Inter Audit | ICAI Module | May 26/ Sept 26/ Jan 27
This segment by CA Krupen Y. Hathi clearly lays out the two critical time-based rules from SQC 1: the 60-day assembly window and the 7-year retention period.
Watch the video from 00:33:54 to 00:40:32. Pay close attention to: The 60-day timeline for assembly from the date of the auditor's report. The minimum retention period of 7 years. The starting point for the 7-year period, especially the distinction for group audits.
a) The 7-Year Rule
As per SQC 1, the retention period for audit engagements is ordinarily no shorter than seven years from the date of the auditor's report.
A crucial nuance for you as a CA Final student is the condition: "...or, if later, the date of the group auditor's report." This means if you audit a subsidiary component, and the consolidated (group) audit report is issued later, the seven-year clock for your audit file starts from that later date.
b) Post-Assembly Modifications
After the 60-day assembly is complete, the rules become even stricter. The auditor shall not delete or discard any audit documentation before the end of the 7-year retention period.
But what if you discover a reason to modify existing documentation or add new documentation after the file has been assembled? This is a serious situation that requires specific documentation.
[PDF] Implementation Guide to Standard on Auditing (SA) 230 Audit ...
The ICAI guide provides clear instructions for this exceptional circumstance. Understanding this procedure demonstrates a deep knowledge of the standard.
Read the answer to Question 35 (A35). Focus on the two key things that must be documented when modifying a file post-assembly.
If you find it necessary to modify or add to the audit file after assembly, you must document:
- The specific reasons for making the changes.
- When and by whom the changes were made and reviewed.
This creates a transparent record of any changes made to the finalized file, ensuring the integrity of the original audit documentation is not compromised.
4. Application: A Case Study
Let's see how these rules apply in a scenario that directly mirrors an ICAI exam question.
Ch. 6 - Audit Documentation Full | SA 230 | CA Inter Audit | ICAI Module | May 26/ Sept 26/ Jan 27
This case study involves a CA who fails to assemble the audit file even after six months. The presenter analyzes the situation based on the rules we've just discussed.
Watch the case study discussion from 00:51:51 to 00:53:50. This will help you connect the theoretical rules to a practical breach of SA 230 and SQC 1.
The CA in this scenario has violated the standards in two ways:
- She failed to complete the assembly of the audit file within the 60-day period.
- She added new working papers with a current date, long after the audit report was issued. This wrongly implies that audit work was performed recently, which is misleading and questions the quality of the original audit.
This example highlights that the assembly and retention rules are not mere suggestions; they are enforceable requirements designed to uphold the quality and integrity of the audit.
Conclusion
This lesson concludes our journey through audit documentation. We've covered the final, yet fundamentally important, administrative procedures that lock in the audit record. While they may seem like formalities, the rules for assembly and retention are the bedrock of quality control, ensuring that the audit evidence is properly organized, complete, and preserved for future reference and inspection.
Key Takeaways:
- Assembly Window: The final audit file must be assembled within 60 days of the date of the auditor's report.
- Administrative Process: Assembly is for organising existing documentation, not for performing new work or drawing new conclusions. Permissible changes include deleting drafts, sorting papers, and signing off checklists.
- Retention Period: The audit file must be retained for a minimum of 7 years from the date of the auditor's report (or group auditor's report, if later).
- Post-Assembly Integrity: No documentation can be deleted after assembly. Any necessary modifications or additions must be formally documented with reasons, dates, and names.
Preview of the Next Lesson
You have now completed the module on Audit Evidence and Documentation. You've built a solid foundation from obtaining sufficient appropriate evidence (SA 500 series) to documenting it correctly (SA 230).
In our next lesson, we will begin a new module, Group Audits and Using the Work of Others. We'll start with SA 600, exploring the unique responsibilities of a group engagement partner—a topic you've highlighted as a key area of interest.