the audit documentation, this should be noted. Person who checked papers also should be identified.Identification of person who reviewed the audit documentation and date of review.4 Explanation of symbolsSymbols used in the audit documentation should be explained. Symbols indicate matters such as the following:Columns were footed.Columns were cross-footed.Data were traced to original sources.
5 Source of informationThe audit documentation should indicate source of information:Client recordsClient personnel
Related Accounts
One page of audit documentation may provide documentation for more than one account. Many balance sheet accounts are related to income statement accounts. In these circumstances, the audit work on the accounts should be documented in one page of audit documentation. Examples of related accounts are the following:
Notes receivable and interest income
Depreciable assets, depreciation expense, and accumulated depreciation
Prepaid expenses and the related income statement expenses, such as insurance, interest, and supplies
Long-term debt and interest expense
Deferred income taxes and income tax expense
Client Preparation of Audit Documentation
It is advisable to have the client’s employees prepare as much as possible of the auditor’s audit documentation. This increases the efficiency of the audit. The auditor should identify the audit documentation as “Prepared by the Client” (PBC) and note the auditor who reviewed the client-prepared audit documentation. The preparation of audit documentation by the client does not impair the auditor’s independence. However, the auditor should test the information in client-prepared audit documentation.
Quality of Audit Documentation
Audit documentation aids the execution and supervision of the current year’s engagement. Also, such documentation helps the auditor in planning and executing the following year’s audit. In addition, audit documentation serves as the auditor’s reference for answering questions from the client. For example, a bank or a credit agency may want information that the auditor can provide to the client for submission to the third party from the audit documentation.
In case of litigation against the client, the auditor’s audit documentation may be subpoenaed. In litigation against the auditor, the audit documentation will be used as evidence. Therefore, audit documentation should be accurate, complete, and understandable. After audit documentation is reviewed, additional work, if any, is done, and modifications are made to the audit documentation, superseded drafts, corrected documents, duplicate documents, review notes, and all to-do points should be discarded because the issues they addressed have been appropriately responded to in the audit documentation. (AU-C 230.A6)
Likewise, miscellaneous notes, memoranda, e-mails, and other communications among members of the audit engagement team created during the audit should be included or summarized in the audit documentation when needed to identify issues or support audit conclusions; otherwise, they should be discarded. Any information added after completion of fieldwork should be dated at the date added.
Oral Explanations
Oral explanations on their own do not represent sufficient support for the work the auditor performed or conclusions the auditor reached but may be used by the auditor to clarify or explain information contained in the audit documentation. (AU-C 230.A7)
NOTE: For example, if the auditing standards state that the auditor should obtain an understanding of the entity’s control environment, but there is no evidence that he or she obtained such an understanding, then the auditor cannot make a plausible claim that the understanding was obtained but just not documented.
Audit Documentation Deficiencies
Some of the more common audit documentation deficiencies are failure to:
Express a conclusion on the account being analyzed.
Explain exceptions noted.
Obtain sufficient information for note disclosure.
Reference information.
Update and revise permanent file.
Post adjusting and reclassification journal entries to appropriate audit documentation.
Indicate source of information.
Promptly review audit documentation prepared by assistants.
Sign or date audit documentation.
Foot client-prepared schedules.
Explain tick marks.
Documentation Requirements in Other Sections
Certain other sections require documentation of specific matters. These requirements are presented in Illustration 4 at the end of this chapter. In addition, other standards, such as government auditing standards, laws, or regulations, may also contain specific documentation requirements.
INTERPRETATIONS
Providing Access to or Copies of Audit Documentation to a Regulator
A regulator may request access to an auditor’s audit documentation to fulfill a quality review requirement or to assist in establishing the scope of a regulatory examination. In making the request, the regulator may ask to make photocopies and may also make such copies available to others. (AU-C 9230.01) When regulators make a request for access, the auditor should:
Consider advising the client about the request and indicating that he or she intends to comply. In some cases the auditor may wish or be required to confirm in writing the requirements to provide access (see Illustration 1).
Make arrangements with the regulator for the review.
Maintain control over the original audit documentation.
Consider submitting a letter to the regulator (see Illustration 2).
(AU-C 9230.02)
Obtain the client’s consent, preferably in writing, to provide access when not required to provide access (see Illustration 3).
NOTE: The guidance in this interpretation applies to requests from regulators, specifically federal, state, and local government officials with legal oversight authority over the entity. The guidance does not apply to requests from:
The IRS,
Practice
