3
A key/legend at the bottom of the audit documentation or in the tickmark sheet will explain the meaning of any symbols or highlighting used. Even if a symbol/highlighting seem obvious (such as “^” symbol to show that the numbers add up correctly) you need to explain what it means. You should ask your field senior if there any common symbols that you should use. Click on the link (by holding down the Ctrl key) to be taken to Referencing and Symbol Illustration . Referencing the work performed. All work performed should be cross referenced to and from any other audit documentation that it supports, or is supported by. o Referencing is a top-down approach. o First, reference from the general ledger (top) to the leadsheet (down). It is essential that the leadsheet matches the general ledger because, as auditors, we provide an opinion on the financial statements produced from the general ledger. o Then, reference from the leadsheet (top) to the audit documentation (down) where we are performing our audit procedures. The audit documentation where we document our testing should be referenced, finally, to any supporting documentation included in the audit file. o Referencing and cross referencing should be done in red so that it is clear to see. Manual (i.e., hard copies of audit documentation or working papers) should be denoted with an “M.” Cross-reference all audit documentation. Wherever you have referenced to, that audit documentation should show a reference from, bringing you back to the original audit documentation. This means that whatever 1

Preparing Audit Documentation Pt 2

Embed Size (px)

DESCRIPTION

Preparing Audit Documentation Pt 2

Citation preview

Page 1: Preparing Audit Documentation Pt 2

• A key/legend at the bottom of the audit documentation or in the tickmark sheet will explain the meaning of any symbols or highlighting used. Even if a symbol/highlighting seem obvious (such as “^” symbol to show that the numbers add up correctly) you need to explain what it means. You should ask your field senior if there any common symbols that you should use.

• Click on the link (by holding down the Ctrl key) to be taken to Referencing and Symbol Illustration.

• Referencing the work performed. All work performed should be cross referenced to and from any other audit documentation that it supports, or is supported by.

o Referencing is a top-down approach.

o First, reference from the general ledger (top) to the leadsheet (down). It is essential

that the leadsheet matches the general ledger because, as auditors, we provide an opinion on the financial statements produced from the general ledger.

o Then, reference from the leadsheet (top) to the audit documentation (down) where we

are performing our audit procedures. The audit documentation where we document our testing should be referenced, finally, to any supporting documentation included in the audit file.

o Referencing and cross referencing should be done in red so that it is clear to see.

• Manual (i.e., hard copies of audit documentation or working papers) should be denoted with an “M.”

• Cross-reference all audit documentation.

• Wherever you have referenced to, that audit documentation should show a reference from, bringing you back to the original audit documentation. This means that whatever audit documentation the field senior reviews, they will be able to find all of the linked documentation.

• For example: If the Nat West bank reconciliation is put on file and is given 5114 as its audit documentation reference number, the period-end balance should be referenced TO the cash leadsheet on audit documentation 5110. Likewise, the Nat West balance listed on the cash leadsheet (audit documentation 5110) must also show a reference FROM the Nat West bank reconciliation audit documentation 5114. This way, whether looking at the bank reconciliation or at the cash leadsheet, the reviewer will be able to find the other piece of information.

• As mentioned above, you must also fill in the relevant SAS documents (e.g., MAP) for the tests performed and reference to the audit documentation where you have documented the audit work performed to address the risks.

1

Page 2: Preparing Audit Documentation Pt 2

• Click on the link (by holding down the Ctrl key) to be taken to Referencing and Symbol Illustration.

• Link the audit documentation where you have performed testing of risks to further information needed to support the work performed.

• If there is too much information to put on the face of a working paper then it should be put in a tickmark. Tickmarks are used to provide additional context and/or support for information contained in a Working Paper or within an engagement item. A tickmark is a reference to a separate worksheet within the audit documentation where more details are given. This is to prevent the leadsheet and document, where testing is performed, from becoming too crowded with information, allowing the reviewer to see all of the pertinent information on the main working paper, such as what work was done and the results of the testing to address the risks of material misstatement. The reviewer can then go to the tickmark worksheet to see further details; usually found as the last worksheet within the audit documentation.

• A tickmark reference should be put next to the information that needs further explanation. This clearly identifies what work was performed relative to the specific information, prevents reviewer confusion of what the tickmark is referring to, and allows for clean, easy-to-read audit documentation.

• Some member firms have guidelines for the type of information that should or should not be included in a tickmark, such as, details of errors found. Some member firms prefer to have this documented in the working paper so they can easily identify errors found. Check with your member firm on preferences in documentation.

o Click on the link (by holding down the Ctrl key) to be taken to Tickmark Worksheet

Illustration.

Each field senior may have different preferences for how work is documented and therefore it is important to check with your field senior before starting any work.

For additional guidance on what needs to be documented, refer to the following:

• Performance Support–Using the Model Audit Program

• Performance Support–Working with

• AAM - P020: Prepare and Control Audit Documentation and P040: Review of Audit Documentation

2