CA INTER · AUDITING AND ETHICS3. Audit Documentation
10 independently written descriptive cases · 10 marks each
Includes audit documentation in your grouped practice structure. This is 10/30 descriptive, 0/30 practice MCQ and 0/30 separate test MCQ, not the full group pack.
Answers include indicative practice marking. These are not ICAI questions, official suggested answers or an official examiner marking scheme. Equivalent correct wording earns credit when it expresses the required idea and applies it accurately. Do not award the same point twice.
AUD-G03-D001 ·10 marksA conclusion without its audit trail
Arbor Kitchens' audit file contains a final memorandum saying that the balances are reasonable and the audit opinion is supported. It includes copies of financial statements and several client spreadsheets, but says little about the procedures performed, the evidence actually obtained or how the team reached its conclusions. The manager argues that the final signed opinion is itself enough documentation of the audit.
A new reviewer who did not work on the engagement cannot understand which spreadsheets were tested or whether the team considered conflicting information. The assistants recall doing useful work but did not record much of it. The partner asks them to explain the difference between holding client papers and having a sufficient audit record.
The task is not to decide whether a particular balance is wrong or to invent procedures that were never performed. Explain the basic meaning and objective of audit documentation and the record required. A favourable final sentence does not describe the work behind it, while a client's spreadsheet may be useful evidence without itself showing the auditor's analysis. Do not treat documentation as a substitute for carrying out the audit.
Required:
Explain five documentation points for this file. (10 marks)
Worked answer and point-wise marks
Indicative practice rubric: 10 marks. Each row separates the credited idea from its case application. Each row states the split between principle/explanation and case application/conclusion. Award proportionately within the stated principle marks for its distinct required ideas. A bare keyword is not automatically full credit.
Common non-credit errors
- A signed opinion alone is not the whole audit trail.
- Client records alone do not explain every auditor conclusion.
- Do not invent work that was never performed.
The experienced reviewer has never met the client
Beacon Systems' file uses shorthand familiar to its original team. One page says "usual checks done, okay", with no description of timing or extent. Another lists an estimate as acceptable but records neither the evidence evaluated nor the significant judgements behind that conclusion. The team says everyone who worked on the audit understands these notes.
An experienced auditor with no previous connection to the engagement is asked to review the file. She cannot tell what the procedures involved, their results or how a difficult estimate issue was addressed. The manager offers to explain orally, but does not propose completing the record. He believes familiarity within the original team is the standard against which documentation should be judged.
Evaluate this approach using the relevant documentation benchmark. There is no need to write a complete estimate valuation or prescribe a particular software package. Focus on what the independent experienced reviewer should be able to understand from the record. The problem is not that shorthand is always forbidden, but that these notes do not explain the actual work, evidence and significant conclusions. Do not assume the estimate is misstated merely because its documentation is poor.
Required:
Explain the documentation benchmark and four content requirements. (10 marks)
Worked answer and point-wise marks
Indicative practice rubric: 10 marks. Each row separates the credited idea from its case application. Each row states the split between principle/explanation and case application/conclusion. Award proportionately within the stated principle marks for its distinct required ideas. A bare keyword is not automatically full credit.
Common non-credit errors
- The benchmark is not only the original team's memory.
- Do not equate poor documentation with a proven misstatement.
- No credit for prescribing arbitrary software instead of sufficient content.
Who tested which items, and who reviewed the work?
Canyon Repairs' purchase-testing paper lists a total value and a tick showing completion. It does not identify the transactions tested. Work was originally assigned to one assistant, but another actually performed it after a staffing change. The paper still names only the original assignee and has no completion date.
The manager reviewed part of the work on one occasion and the remaining part later, but the file contains only a generic "reviewed" stamp. The partner cannot trace who did the testing, when it was completed or what the review covered. The assistants say the staffing change is unimportant because both were members of the engagement team.
Explain the record needed for procedures, performance and review. The question does not prohibit reassignment within a team or demand a universal format for identifying transactions. It requires enough identifying information to understand the specific items tested and an accurate trail of who actually worked and reviewed. Do not fill the gaps by inventing dates, transaction numbers or a review that did not occur. Distinguish the planned assignment from actual execution.
Required:
Explain five necessary documentation improvements. (10 marks)
Worked answer and point-wise marks
Indicative practice rubric: 10 marks. Each row separates the credited idea from its case application. Each row states the split between principle/explanation and case application/conclusion. Award proportionately within the stated principle marks for its distinct required ideas. A bare keyword is not automatically full credit.
Common non-credit errors
- Planned responsibility is not proof of actual performance.
- No credit for backdating or inventing identifiers.
- A staffing change is permitted but the record must remain accurate.
A resolved significant discussion still belongs in the file
Dune Energy's team discusses a significant estimate issue with the finance director and later with those charged with governance. The issue is resolved after additional evidence and a revised management explanation. The working paper records only the final balance, because the manager says a resolved issue is no longer significant.
The file does not identify the nature of the discussion, who attended or when either meeting occurred. A review partner wants to understand why the original concern was closed. The audit team offers a recollection that "management agreed", without connecting it to the revised explanation or other evidence.
Discuss the documentation requirements for these significant discussions and the resulting conclusion. The case does not require disclosure of private information outside the authorised engagement workflow, and it does not establish a reporting modification. The question is about the internal audit record. Resolution can affect the conclusion but does not erase the significance of how the issue was addressed. Avoid a blanket rule that every casual conversation in an audit must have the same detailed record as a significant matter.
Required:
Explain five points required in documenting this issue. (10 marks)
Worked answer and point-wise marks
Indicative practice rubric: 10 marks. Each row separates the credited idea from its case application. Each row states the split between principle/explanation and case application/conclusion. Award proportionately within the stated principle marks for its distinct required ideas. A bare keyword is not automatically full credit.
Common non-credit errors
- Resolved does not mean undocumented.
- Do not treat management agreement alone as every required piece of evidence.
- Do not invent meeting dates or impose the same requirement on every casual conversation.
Conflicting information cannot be hidden by a final sentence
Estuary Tools initially obtains information supporting a significant balance. Later, another source gives information inconsistent with the conclusion the team ultimately reaches. The auditor investigates and decides that the final conclusion is justified, but the working paper contains only the favourable source and the final sentence.
The manager removes the inconsistent information from the description because he believes keeping it would confuse reviewers. The partner asks how the auditor addressed the difference and which evidence or reasoning supported the final decision. The assistant says the conclusion should be trusted because the team considered the issue, although its treatment was not recorded.
Explain the documentation needed for inconsistent information on a significant matter. You are not asked to decide that either source is true, to assume a fraud or to select a modified report. The supplied fact is that relevant inconsistent information existed and the team reached a conclusion after work. The record must explain how the inconsistency was addressed, rather than falsely suggest that no conflict arose. Do not recommend retaining every duplicate or preliminary draft as a substitute for that explanation.
Required:
Explain five documentation considerations in the case. (10 marks)
Worked answer and point-wise marks
Indicative practice rubric: 10 marks. Each row separates the credited idea from its case application. Each row states the split between principle/explanation and case application/conclusion. Award proportionately within the stated principle marks for its distinct required ideas. A bare keyword is not automatically full credit.
Common non-credit errors
- Inconsistent information is not automatically proof of fraud.
- No credit for suppressing the conflict to make the file look simple.
- Do not confuse keeping duplicates with explaining the inconsistency.
Documentation needs vary with the engagement and findings
Foxtail Analytics audits two areas. One is a simple routine account with consistent evidence. The other involves a complex estimate, several exceptions and a conclusion requiring substantial judgement. Both are documented on identical one-line checklist boxes because the manager wants every area to use the same amount of space.
The team uses electronic tools, and the manager believes that the software's completion icon automatically determines sufficient documentation. A reviewer cannot understand the complex conclusion from the one-line entry. The manager argues that adding explanation only to that area would make the file inconsistent, and that all evidence should have the same documentation regardless of significance.
Explain factors affecting the form, content and extent of documentation. The task does not require the largest possible file for every audit or reject electronic tools. It requires sufficient records in the circumstances. Connect the complexity, procedure type, risks, evidence, exceptions and hard-to-infer conclusion to the needed detail. A uniform form may help organisation but cannot determine whether the record is adequate for each actual area.
Required:
Explain five relevant factors or combined considerations. (10 marks)
Worked answer and point-wise marks
Indicative practice rubric: 10 marks. Each row separates the credited idea from its case application. Each row states the split between principle/explanation and case application/conclusion. Award proportionately within the stated principle marks for its distinct required ideas. A bare keyword is not automatically full credit.
Common non-credit errors
- No credit for saying every audit needs the same volume of documentation.
- Electronic tools are not prohibited.
- A software completion icon is not itself the required audit reasoning.
Sorting the file is not a second audit after report dating
Garnet Rentals has dated its auditor's report. The audit procedures and conclusions supporting it were completed before that date. The firm is now assembling the final file. An assistant proposes sorting and cross-referencing papers, removing superseded duplicates and signing the file-assembly checklist.
The manager also proposes performing a new procedure on a significant balance and drawing a new conclusion while calling it routine assembly. He says the assembly period is extra time to finish whatever audit work was omitted before report dating. Another assistant wants to document evidence already obtained, discussed and agreed with the relevant team members before the report date, but is told that no note can be written during assembly.
Evaluate these proposals in the ordinary final-file assembly process described in the study material. The question does not provide facts for a special post-report event workflow, so do not use routine assembly to disguise a new substantive procedure. Equally, do not prohibit genuine administrative completion. Separate organising an existing audit record from performing new work or making a new judgement after reporting.
Required:
Explain five assembly points applied to the proposals. (10 marks)
Worked answer and point-wise marks
Indicative practice rubric: 10 marks. Each row separates the credited idea from its case application. Each row states the split between principle/explanation and case application/conclusion. Award proportionately within the stated principle marks for its distinct required ideas. A bare keyword is not automatically full credit.
Common non-credit errors
- The assembly period is not an automatic extension for omitted audit work.
- Do not prohibit all administrative changes after report dating.
- Do not falsely backdate evidence or a new procedure.
Final assembly and retention have different clocks
Harbour Glass dates its auditor's report on 10 May. It is not a group audit. The firm intends to assemble the final file four months later because there is no inspection scheduled. After assembly, it proposes deleting a useful working paper six months after the report date to reduce storage costs. No longer statutory retention period is specified in this case.
A manager says that the ordinary sixty-day assembly period is also the retention period. Another says the period ordinarily mentioned for audit-engagement retention is measured from the client's financial year-end rather than report dating. The partner asks for the relevant ordinary time frames and what restrictions apply once assembly is completed.
Explain the concepts without calculating a weekday or a particular calendar deadline. Use the ordinary benchmarks in the official module, preserving their qualifiers and the possibility of other legal requirements. The question is not permission to destroy any specific record. Assembly concerns timely administrative completion; retention concerns how long the documentation must remain. A quiet inspection timetable and storage inconvenience do not make those two requirements interchangeable.
Required:
Explain five points on assembly and retention. (10 marks)
Worked answer and point-wise marks
Indicative practice rubric: 10 marks. Each row separates the credited idea from its case application. Each row states the split between principle/explanation and case application/conclusion. Award proportionately within the stated principle marks for its distinct required ideas. A bare keyword is not automatically full credit.
Common non-credit errors
- Do not equate the assembly limit with permission to delete records.
- Do not replace report dating with year-end as the stated retention reference.
- No credit for dropping ordinary/minimum qualifiers or inventing authority to destroy.
Ownership does not turn working papers into client books
Indigo Hotels asks its auditor to give it the complete audit file because it paid the audit fee. Management also wants to stop maintaining its own supporting records and use the auditor's papers as the accounting record instead. No law or regulation transferring ownership of the documentation is specified.
The partner considers whether a limited extract might be provided at discretion to help the client understand a matter, provided it does not undermine the validity of the work or the auditor's independence. An assistant says ownership means the auditor may publish all client information freely. Another says an auditor can never make any portion available to a client under any circumstances.
Explain the module's ownership and client-access principles and the relationship to entity records. The question does not grant permission for an actual disclosure or settle every legal right of access. It asks for a conceptual answer under the stated facts. Paying for an audit is not the same as owning the auditor's documentation, while ownership does not justify indiscriminate disclosure. Distinguish a permissible discretionary extract from a compulsory transfer of the entire file.
Required:
Explain five relevant ownership/access points. (10 marks)
Worked answer and point-wise marks
Indicative practice rubric: 10 marks. Each row separates the credited idea from its case application. Each row states the split between principle/explanation and case application/conclusion. Award proportionately within the stated principle marks for its distinct required ideas. A bare keyword is not automatically full credit.
Common non-credit errors
- A paid fee does not itself transfer working-paper ownership.
- Do not state that every client extract is always forbidden.
- Ownership does not authorise public disclosure of confidential client information.
A completion memorandum is a map, not the whole file
Jasper Networks has a large audit file spread across electronic folders. Several significant matters were investigated and addressed, including a difficult estimate and access problems affecting a procedure. The underlying working papers exist, but a reviewer spends considerable time finding where each issue was discussed and what conclusion was reached.
The manager proposes a completion memorandum summarising significant matters and linking their treatment to the relevant working papers. A senior instead proposes keeping only the summary and deleting all supporting work to reduce file size. Another team member says a summary has no purpose because documentation is useful only during fieldwork, not for review or future audits.
Evaluate the proposed memorandum and the wider purposes of documentation. The question does not make a completion memorandum compulsory in every engagement or authorise deletion of retained papers. Explain how a useful summary may help a large or complex file, while preserving the sufficient underlying record. Also address review, accountability and matters of continuing significance. A short summary should help readers understand the actual audit, not hide unresolved issues or replace the evidence supporting conclusions.
Required:
Explain five points on the summary and documentation purposes. (10 marks)
Worked answer and point-wise marks
Indicative practice rubric: 10 marks. Each row separates the credited idea from its case application. Each row states the split between principle/explanation and case application/conclusion. Award proportionately within the stated principle marks for its distinct required ideas. A bare keyword is not automatically full credit.
Common non-credit errors
- Do not claim a completion memorandum is compulsory for every engagement.
- A summary does not itself replace supporting evidence.
- Do not authorise destruction merely to reduce file size.