Guide to Using International Standards on Auditing in - IFAC

Guide to Using International Standards on Auditing in - IFAC Guide to Using International Standards on Auditing in - IFAC

17.03.2014 Views

216 ong>Guideong> ong>toong> ong>Usingong> ong>Internationalong> ong>Standardsong> on Auditing in the Audits of Small- and Medium-Sized Entities Volume 1—Core Concepts • Engagement team members can share file documents by using electronic check-in and check-out ong>toong>ols; • Certain documents can be password-protected for enhanced security; and • Access ong>toong> files can be restricted ong>toong> authorized personnel. ong>Usingong> Electronic Tools in Working Papers There are three important principles ong>toong> note when using electronic ong>toong>ols in working-paper preparation: • All the requirements of the ISAs still apply; • Electronic files require electronic document management. This addresses matters such as accessibility (such as password access), data security, application management (including training), back-up routines, edit rights, song>toong>rage locations, review procedures, and decisions on what changes ong>toong> files will be tracked ong>toong> provide the necessary audit trail; and • Final documents (all documents that are required ong>toong> be maintained ong>toong> support the audit opinion) must be retained and be accessible in accordance with the firm’s file retention policies. 16.7 File Completion Paragraph # Relevant Extracts from ISAs 230.13 If, in exceptional circumstances, the audiong>toong>r performs new or additional audit procedures or draws new conclusions after the date of the audiong>toong>r’s report, the audiong>toong>r shall document: (Ref: Para. A20) (a) The circumstances encountered; (b) The new or additional audit procedures performed, audit evidence obtained, and conclusions reached, and their effect on the audiong>toong>r’s report; and (c) When and by whom the resulting changes ong>toong> audit documentation were made and reviewed. 230.14 The audiong>toong>r shall assemble the audit documentation in an audit file and complete the administrative process of assembling the final audit file on a timely basis after the date of the audiong>toong>r’s report. (Ref: Para. A21-A22) 230.15 After the assembly of the final audit file has been completed, the audiong>toong>r shall not delete or discard audit documentation of any nature before the end of its retention period. (Ref: Para. A23) 230.16 In circumstances other than those envisaged in paragraph 13 where the audiong>toong>r finds it necessary ong>toong> modify existing audit documentation or add new audit documentation after the assembly of the final audit file has been completed, the audiong>toong>r shall, regardless of the nature of the modifications or additions, document: (Ref: Para. A24) (a) The specific reasons for making them; and (b) When and by whom they were made and reviewed. The dating of the audiong>toong>r’s report signifies that the audit work is complete. After that date, there is no continuing responsibility ong>toong> seek further audit evidence. After the audit report date, the final assembly of audit files should take place on a timely basis. An appropriate time limit within which ong>toong> complete the assembly of the final audit file is ordinarily not more than 60 days after the date of the audiong>toong>r’s report. This is illustrated in the following exhibit. Refer ong>toong> ISQC 1 and ISA 230 for more details.

217 ong>Guideong> ong>toong> ong>Usingong> ong>Internationalong> ong>Standardsong> on Auditing in the Audits of Small- and Medium-Sized Entities Volume 1—Core Concepts Exhibit 16.7-1 Making Changes ong>toong> the Audit File The requirements when making changes ong>toong> audit file are as follows. Exhibit 16.7-2 Period Dates Requirements 1 BETWEEN the Audit Report Date and Documentation Completion Date 2 AFTER the Documentation Completion Date For administrative changes: • Document the nature of audit evidence obtained, who prepared and reviewed each document, and any additional memos ong>toong> file that may be required; • Delete or discard superseded documentation; • Sort, collate, and cross-reference working papers; and • Sign off any completion checklists relating ong>toong> the file assembly process. For changes in the audit evidence or conclusions reached, additional documentation should be prepared that addresses three key questions: • When and by whom such additions were made and (where applicable) reviewed; • The specific reasons for the additions; and • The effect, if any, of the additions on the audit conclusions. NO documentation should be deleted or discarded from the audit file until the firm’s file retention period has expired. Where it is necessary ong>toong> make additions (including amendments) ong>toong> audit documentation after the documentation completion date, the three key questions about changes in audit evidence, outlined in Period 1 above, should be answered, regardless of the nature of the additions.

216<br />

<str<strong>on</strong>g>Guide</str<strong>on</strong>g> <str<strong>on</strong>g>to</str<strong>on</strong>g> <str<strong>on</strong>g>Us<strong>in</strong>g</str<strong>on</strong>g> <str<strong>on</strong>g>Internati<strong>on</strong>al</str<strong>on</strong>g> <str<strong>on</strong>g>Standards</str<strong>on</strong>g> <strong>on</strong> <strong>Audit<strong>in</strong>g</strong> <strong>in</strong> the Audits of Small- and Medium-Sized Entities Volume 1—Core C<strong>on</strong>cepts<br />

• Engagement team members can share file documents by us<strong>in</strong>g electr<strong>on</strong>ic check-<strong>in</strong> and check-out <str<strong>on</strong>g>to</str<strong>on</strong>g>ols;<br />

• Certa<strong>in</strong> documents can be password-protected for enhanced security; and<br />

• Access <str<strong>on</strong>g>to</str<strong>on</strong>g> files can be restricted <str<strong>on</strong>g>to</str<strong>on</strong>g> authorized pers<strong>on</strong>nel.<br />

<str<strong>on</strong>g>Us<strong>in</strong>g</str<strong>on</strong>g> Electr<strong>on</strong>ic Tools <strong>in</strong> Work<strong>in</strong>g Papers<br />

There are three important pr<strong>in</strong>ciples <str<strong>on</strong>g>to</str<strong>on</strong>g> note when us<strong>in</strong>g electr<strong>on</strong>ic <str<strong>on</strong>g>to</str<strong>on</strong>g>ols <strong>in</strong> work<strong>in</strong>g-paper preparati<strong>on</strong>:<br />

• All the requirements of the ISAs still apply;<br />

• Electr<strong>on</strong>ic files require electr<strong>on</strong>ic document management. This addresses matters such as accessibility<br />

(such as password access), data security, applicati<strong>on</strong> management (<strong>in</strong>clud<strong>in</strong>g tra<strong>in</strong><strong>in</strong>g), back-up rout<strong>in</strong>es,<br />

edit rights, s<str<strong>on</strong>g>to</str<strong>on</strong>g>rage locati<strong>on</strong>s, review procedures, and decisi<strong>on</strong>s <strong>on</strong> what changes <str<strong>on</strong>g>to</str<strong>on</strong>g> files will be tracked<br />

<str<strong>on</strong>g>to</str<strong>on</strong>g> provide the necessary audit trail; and<br />

• F<strong>in</strong>al documents (all documents that are required <str<strong>on</strong>g>to</str<strong>on</strong>g> be ma<strong>in</strong>ta<strong>in</strong>ed <str<strong>on</strong>g>to</str<strong>on</strong>g> support the audit op<strong>in</strong>i<strong>on</strong>) must<br />

be reta<strong>in</strong>ed and be accessible <strong>in</strong> accordance with the firm’s file retenti<strong>on</strong> policies.<br />

16.7 File Completi<strong>on</strong><br />

Paragraph #<br />

Relevant Extracts from ISAs<br />

230.13 If, <strong>in</strong> excepti<strong>on</strong>al circumstances, the audi<str<strong>on</strong>g>to</str<strong>on</strong>g>r performs new or additi<strong>on</strong>al audit procedures or draws<br />

new c<strong>on</strong>clusi<strong>on</strong>s after the date of the audi<str<strong>on</strong>g>to</str<strong>on</strong>g>r’s report, the audi<str<strong>on</strong>g>to</str<strong>on</strong>g>r shall document: (Ref: Para. A20)<br />

(a) The circumstances encountered;<br />

(b) The new or additi<strong>on</strong>al audit procedures performed, audit evidence obta<strong>in</strong>ed, and<br />

c<strong>on</strong>clusi<strong>on</strong>s reached, and their effect <strong>on</strong> the audi<str<strong>on</strong>g>to</str<strong>on</strong>g>r’s report; and<br />

(c) When and by whom the result<strong>in</strong>g changes <str<strong>on</strong>g>to</str<strong>on</strong>g> audit documentati<strong>on</strong> were made and<br />

reviewed.<br />

230.14 The audi<str<strong>on</strong>g>to</str<strong>on</strong>g>r shall assemble the audit documentati<strong>on</strong> <strong>in</strong> an audit file and complete the<br />

adm<strong>in</strong>istrative process of assembl<strong>in</strong>g the f<strong>in</strong>al audit file <strong>on</strong> a timely basis after the date of the<br />

audi<str<strong>on</strong>g>to</str<strong>on</strong>g>r’s report. (Ref: Para. A21-A22)<br />

230.15 After the assembly of the f<strong>in</strong>al audit file has been completed, the audi<str<strong>on</strong>g>to</str<strong>on</strong>g>r shall not delete or<br />

discard audit documentati<strong>on</strong> of any nature before the end of its retenti<strong>on</strong> period. (Ref: Para. A23)<br />

230.16 In circumstances other than those envisaged <strong>in</strong> paragraph 13 where the audi<str<strong>on</strong>g>to</str<strong>on</strong>g>r f<strong>in</strong>ds it<br />

necessary <str<strong>on</strong>g>to</str<strong>on</strong>g> modify exist<strong>in</strong>g audit documentati<strong>on</strong> or add new audit documentati<strong>on</strong> after the<br />

assembly of the f<strong>in</strong>al audit file has been completed, the audi<str<strong>on</strong>g>to</str<strong>on</strong>g>r shall, regardless of the nature<br />

of the modificati<strong>on</strong>s or additi<strong>on</strong>s, document: (Ref: Para. A24)<br />

(a) The specific reas<strong>on</strong>s for mak<strong>in</strong>g them; and<br />

(b) When and by whom they were made and reviewed.<br />

The dat<strong>in</strong>g of the audi<str<strong>on</strong>g>to</str<strong>on</strong>g>r’s report signifies that the audit work is complete. After that date, there is no<br />

c<strong>on</strong>t<strong>in</strong>u<strong>in</strong>g resp<strong>on</strong>sibility <str<strong>on</strong>g>to</str<strong>on</strong>g> seek further audit evidence.<br />

After the audit report date, the f<strong>in</strong>al assembly of audit files should take place <strong>on</strong> a timely basis. An appropriate<br />

time limit with<strong>in</strong> which <str<strong>on</strong>g>to</str<strong>on</strong>g> complete the assembly of the f<strong>in</strong>al audit file is ord<strong>in</strong>arily not more than 60 days<br />

after the date of the audi<str<strong>on</strong>g>to</str<strong>on</strong>g>r’s report. This is illustrated <strong>in</strong> the follow<strong>in</strong>g exhibit. Refer <str<strong>on</strong>g>to</str<strong>on</strong>g> ISQC 1 and ISA 230 for<br />

more details.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!