Wiley Practitioner's Guide to GAAS 2017. Flood Joanne M.
Чтение книги онлайн.
Читать онлайн книгу Wiley Practitioner's Guide to GAAS 2017 - Flood Joanne M. страница 10
Название: Wiley Practitioner's Guide to GAAS 2017
Автор: Flood Joanne M.
Издательство: Автор
Жанр: Зарубежная образовательная литература
isbn: 9781119373698
isbn:
Sufficiency of Audit Documentation
Audit documentation should include:
● Who reviewed specific audit work and the date the work was completed
● Who performed the audit documentation and the date of such review
● Identifying characteristics of specific items tested
(AU-C 230.09)
Audit documentation should also include abstracts or copies of significant contracts or agreements that involved audit procedure. (AU-C 230.10)
Documentation of Significant Findings
The auditor should document significant audit findings or issues, actions taken to address them (including additional evidence obtained), and the basis of the conclusions reached. Significant audit findings or issues include:
● Matters that are both significant and involve the appropriate selection, application, and consistency of accounting principles with regard to the financial statements, including related disclosures. Such matters often relate to (1) accounting for complex or unusual transactions or (2) estimates and uncertainties, and the related management assumptions, if applicable.
● Results of auditing procedures that indicate that the financial statements or disclosures could be materially misstated or that the auditing procedures need to be significantly modified.
● Circumstances that cause significant difficulty in applying necessary auditing procedures.
● Other findings that could result in a modified auditor's report.
The auditor should document discussions with management and those charged with governance, including when and with whom, about significant findings. (AU-C 230.11)
Departures from a Relevant Requirement
The auditor may find it necessary to not perform a required procedure. If so, the auditor should document the reason for the departure and how alternative procedures enabled the auditor to fulfill the objectives of the audit. (AU-C 230.13)
This documentation is required only if the required procedure is relevant to the audit. For example, if the entity does not have an internal audit function, procedures in AU-C 610 would not be relevant.
Factors to Consider in Determining the Nature and Extent of Audit Documentation
The auditor should consider the following factors in determining the nature and extent of the documentation for an audit area or auditing procedure:
● What is the risk of material misstatement associated with the assertion, or account or class of transactions?
● What is the extent of judgment involved in performing the work and evaluating results?
● What is the nature of the auditing procedure?
● What is the significance of evidence obtained to the tested assertion?
● What is the nature and extent of identified exceptions?
● Is there a need to document a conclusion or basis for a conclusion not readily determinable from the documentation of the work performed?
● What are the methodologies or tools used?
(AU-C 230.A4)
Documentation of Report Release Date and Revisions
The auditor should document the report release date and complete the assembly of the final audit file on a timely basis, but no later than 60 days following the report release date. (AU-C 230.15-.16) After this date, the auditor must not delete or discard existing audit documentation before the end of the specified retention period, not less than five years. If changes are made to the audit documentation after this date, the auditor should document the change, when and by whom the changes were made, the specific reasons for the change, and the effect of the changes, if any, on the auditor's previous conclusions. (AU-C 230.14 and .18)
Ownership and Confidentiality
The auditor owns the audit documentation, but his or her ownership rights are limited by ethical and legal rules on confidential relationships with clients. The auditor should adopt reasonable procedures to protect the confidentiality of client information. (AU-C 230.15-19) The auditor should also adopt reasonable procedures to prevent unauthorized access to the audit documentation. Sometimes audit documentation may serve as a source of reference for the client, but it should not be considered as a part of, or a substitute for, the client's accounting records.
Standardization of Audit Documentation
Audit documentation should be designed for the specific engagement; however, audit documentation supporting certain accounting records may be standardized.
The auditor should analyze the nature of his or her clients and the complexity of their accounting systems. This analysis will indicate accounts for which audit documentation may be standardized. An auditor ordinarily may be able to standardize audit documentation for a small-business client as follows:
1. Cash, including cash on hand
2. Short-term investments
3. Trade accounts receivable
4. Notes receivable
5. Other receivables
6. Prepaid expenses
7. Property, plant, and equipment
8. Long-term investments
9. Intangible assets
10. Deposits
11. Accrued expenses
12. Taxes payable
13. Long-term debt
14. Stockholders' equity accounts
Preparation of Audit Documentation
All audit documentation should have certain basic information, such as the following:
1. Heading
a. Name of client
b. Description of audit documentation, such as:
i. Proof of cash – Fishkill Bank & Trust Company
ii. Accounts receivable – confirmation statistics
c. Period covered by engagement
i. For the year ended…
2. An index number
a. All audit documentation should be numbered for easy reference. Audit documentation is identified using various systems, such as the following:
i. Alphabetical
ii. Numbers
iii. Roman numerals
iv. СКАЧАТЬ