Original Pronouncements | Statements on Auditing Standards (SASs) 1, 29, 98, and 103. |
Effective Date | These statements currently are effective. |
Applicability | Audits of financial statements in accordance with generally accepted auditing standards (GAAS). |
SAS No. 122, Codification of Auditing Standards and Procedures, is effective for audits of financial statements with periods ending on or after December 15, 2012.
The clarified SAS combines the requirements and guidance from extant AU Section 530, AU Section 560, AU Section 561, and paragraphs .71–.73 of AU Section 508. The clarified SAS does not change or expand these extant AU sections in any significant respect.
Date of auditor’s report. The date on which the auditor has obtained sufficient appropriate audit evidence to support the opinion.
Dual-dated report. Auditor’s report with different dates: (1) the date of completion of fieldwork, and (2) the date a specific event occurred after completion of the fieldwork but before issuance of the auditor’s report.
Reissued report. Auditor’s report issued subsequent to the date the original report was issued.
Report release date. The date the auditor grants the entity permission to use the auditor’s report in connection with the financial statements. Usually this date wilxl be the date the auditor delivers the audit report to the entity.
Subsequent events. For purposes of this section, events occurring after the date of the auditor’s report but before issuance of the related financial statements that require adjustment of or disclosure in the financial statements (see Section 560, Subsequent Events).
Date of the auditor’s report. The date that the auditor dates the report on the financial statements, in accordance with Section 700 (Ref: par. .A14)
Date of the financial statements. The date of the end of the latest period covered by the financial statements.
Subsequent events. Events occurring between the date of the financial statements and the date of the auditor’s report.
Subsequently discovered facts. Facts that become known to the auditor after the date of the auditor’s report that, had they been known to the auditor at that date, may have caused the auditor to revise the auditor’s report.
This section tells the auditor how to date the report in the following circumstances:
SAS 29 (see Section 551, Reporting on Financial Information Accompanying the Basic Financial Statements in Auditor-Submitted Documents) created a difference in responsibilities for types of reissued reports. If the client is furnished with additional copies of a previously issued report, the auditor has no responsibility to perform any procedures prior to reprinting the report unless the auditor has become aware of the need to adjust or make disclosure in the financial statements. In the case of a predecessor auditor consenting to reuse a previous report, additional procedures are always required (see Section 508, Reports on Audited Financial Statements).
AU-C Section 560 states that:
. . . the objectives of the auditor are to
Under ordinary conditions, the auditor should date his or her report as of the date of completion of fieldwork. The auditor does not have to make inquiries or apply other auditing procedures after the date of his or her report under ordinary conditions. However, additional procedures might be required (see the sections titled “Reissuance of Report” and “Unusual Conditions”).
Some events that require adjustment might be made without disclosure, but some events require additional disclosure to be understood.
Some subsequent events only require disclosure of information in the notes to the financial statements.
A subsequent events review is the auditor’s review of transactions and events occurring after the date of the balance sheet and up to the date of the auditor’s report. Its purpose is to determine whether the financial statements being reported on require adjustment or additional disclosures (see Section 560).
If the auditor dates the report as of the date of the subsequent event rather than dual dating the report, he or she should extend the subsequent events review to that date (see Section 560).
When the auditor reissues the report and uses the original report date, he or she does not have to investigate or inquire about events affecting the financial statements reported on that may have occurred between the original date and the reissuance date.
The auditor may be aware of an event that occurred between the original report date and the reissuance date that affects the financial statements reported on. This event may require disclosure to prevent the financial statements from being misleading. Events occurring between the original report date and the reissuance date do not require adjustment of the financial statements unless the adjustment results in the correction of an error (see Section 560).
When the auditor reissues the report and the financial statements have been adjusted or events have been disclosed in the notes, he or she should dual date the report or date it as of the date of the event responsible for the adjustment or the disclosure.
An event that requires disclosure only may be disclosed in a note to the financial statements marked “unaudited.” In these circumstances, the auditor’s report would have the original date. An example of the heading to use for this type of note follows:
Event (Unaudited) Subsequent to the Date of the Report of the Independent Auditor.
Under ordinary conditions, the auditor has no responsibility to make any inquiry or carry out any procedures for the period after the date of his or her report. An exception might arise if the audit report is reissued as explained previously. An exception might also arise in either of the following circumstances.
If, subsequent to the date of the report, the auditor becomes aware of facts that may have existed at that date which might have affected the report, additional procedures are required (see Section 561, Subsequent Discovery of Facts Existing at the Date of the Auditor’s Report).
If the financial statements subsequently are incorporated in a filing under the Securities Act of 1933, additional procedures are required (see Section 711, Filings under Federal Securities Statutes).
There are no interpretations for this section.
There is no authoritative pronouncement that provides guidance on how to determine the date of completion of fieldwork. The date is usually the same as the date of the management representation letter (see Section 333, Management Representations) and the date up to which lawyers are asked to respond (see Section 337, Inquiry of a Client’s Lawyer Concerning Litigation, Claims, and Assessments) concerning litigation, claims, and assessments.
Ordinarily, the date of completion of the fieldwork is the date on which the auditor in charge of the engagement and the client’s chief financial officer agree on the form and content of the financial statements. The auditor and the client may arrange for a formal closing conference to review the financial statements. The conclusion of this conference may be considered the date of completion of the fieldwork. If there is no formal closing conference, the date of completion of the fieldwork may be considered to be the date the audit staff finally leaves the client’s premises, provided no significant adjustments are expected after that date.
If any procedures that are necessary to the expression of an opinion are performed after the audit staff leaves the client’s premises, the substantial completion of those procedures is the completion of fieldwork. Additional advice on issues concerning dating of the audit report is presented in the “Techniques for Application” section of the chapter on Section 560, Subsequent Events.
Ordinarily, there is a lapse of two to three weeks between the date of the auditor’s report (the date of completion of the fieldwork) and its issuance. During this period, the auditor might review the audit documentation a final time to make certain there are no open items, put the audit documentation in a form suitable to be filed, and prepare the final audit report and financial statements. During this period, the auditor is not required to apply any procedures unless information about subsequent events comes to the attention of the auditor (see Section 530, Dating of the Independent Auditor’s Report).
If the period between the date of the auditor’s report and the issuance of the financial statements exceeds approximately three weeks, it would be prudent for the auditor to call the client and inquire about subsequent events. If the delay is unusually long, it may be advisable to extend the subsequent events review and redate the report.
When an event that requires disclosure or adjustment of financial statements occurs between the date of the auditor’s report and the issuance of the financial statements, or between the date of issuance and the date of reissuance, the auditor may dual date the report or extend the date of the report and the subsequent events review to the date of the event. Because extending the date of the report extends the auditor’s responsibility, the auditor is acting prudently in always dual dating reports requiring disclosure of subsequent events.
An example of the dual dating of an auditor’s report is as follows:
February 16, 20X1, except for Note X as to which the date is February 25, 20X1.
1 This section is affected by the Public Company Accounting Oversight Board’s (PCAOB’s) Standard, Conforming Amendments to PCAOB Interim Standards Resulting from the Adoption of PCAOB Auditing Standard No. 5, An Audit of Internal Control over Financial Reporting That Is Integrated with an Audit of Financial Statements.
3.142.12.207