SAS 115 is an American Institute of Certified Public Accountants (AICPA) auditing standard, issued in October 2008, that tells auditors how to classify and report weaknesses in a client’s internal controls over financial reporting.1UC Irvine Accounting & Fiscal Services. Statement of Auditing Standards (SAS) 115 It sorts deficiencies into three tiers, requires written communication to management and those charged with governance when the more serious tiers are involved, and aligned private-company audit definitions with those the PCAOB already used for public companies. The AICPA has since recodified it as AU-C Section 265 under the Clarity Project, and the framework carried over largely unchanged.2AICPA. AU-C Section 265 – Communicating Internal Control Related Matters Identified in an Audit
The Three Tiers of Deficiency
Every internal control weakness the auditor identifies has to be placed in one of three categories. The category decides who has to be told and how formally.
Control Deficiency
A control deficiency exists when the design or operation of a control doesn’t let employees prevent or detect errors on a timely basis. That covers missing controls and poorly designed ones alike.3Public Company Accounting Oversight Board. AU Section 325 – Communications About Control Deficiencies in an Audit of Financial Statements A plain control deficiency does not require written communication to the board. The auditor may raise it with management verbally or in writing.
Significant Deficiency
A significant deficiency is serious enough that the people responsible for financial reporting oversight need to hear about it, though it hasn’t reached the top severity. It can be one flaw on its own or several smaller weaknesses combining to reach the threshold.3Public Company Accounting Oversight Board. AU Section 325 – Communications About Control Deficiencies in an Audit of Financial Statements There is no bright line. The auditor weighs likelihood and potential size, then decides whether the weakness deserves board-level attention.
Material Weakness
A material weakness is the most severe classification. It means there is a reasonable possibility that a material misstatement in the financial statements will not be prevented or detected on a timely basis. Under AU-C 265, “reasonable possibility” means more than remote, which is a lower bar than many people assume.2AICPA. AU-C Section 265 – Communicating Internal Control Related Matters Identified in an Audit A material weakness doesn’t require that an error actually happened. It requires only that the controls are weak enough that a large one plausibly could, with no one catching it.
How Auditors Decide Which Tier Applies
Classification is not mechanical. The auditor weighs two things: the likelihood that the gap could produce a misstatement, and how large that misstatement could be. A weakness that could only cause a small error in an immaterial account is different from one that could distort revenue recognition. The analysis looks forward at what could happen, not backward at what did. Zero actual errors during the audit period does not save a poorly designed control from being a material weakness if the exposure is large enough.
Compensating Controls
A weak control is not automatically a severe finding when another control effectively covers the gap.4Public Company Accounting Oversight Board. Communications About Control Deficiencies in an Audit of Financial Statements The standard’s illustration: a company may lack proper security over its inventory warehouse, but regular, effective physical counts can still prevent a financial statement misstatement even though the preventive control failed.2AICPA. AU-C Section 265 – Communicating Internal Control Related Matters Identified in an Audit Note the word effectively. The auditor cannot just point to the backup control; they have to test that it works.
Aggregation
Individually minor deficiencies affecting the same account, disclosure, or process can combine into a significant deficiency or a material weakness. Three small weaknesses in the revenue cycle may amount to nothing on their own but together create a real risk that revenue is misstated.2AICPA. AU-C Section 265 – Communicating Internal Control Related Matters Identified in an Audit Auditors are expected to consider this at the point each deficiency is identified, not only at year-end.
What the Written Communication Must Contain
When the auditor identifies a significant deficiency or material weakness, the finding goes into a formal written communication addressed to management and those charged with governance, usually the board or audit committee. The standard requires specific elements:3Public Company Accounting Oversight Board. AU Section 325 – Communications About Control Deficiencies in an Audit of Financial Statements
- Definitions of material weakness and significant deficiency, with a clear indication of which category each reported issue falls into.
- A statement that the audit’s objective was to opine on the financial statements, not to provide assurance on the effectiveness of internal controls.
- A restriction stating the communication is intended solely for management, governance, and others within the organization, not external parties.
- A description of each deficiency in enough detail for the reader to understand the nature of the problem and its potential consequences.
The auditor is not required to include management’s response or verify that any proposed fix will actually work. Management is free to prepare its own separate response.
When It Has to Be Delivered
Under AU-C Section 265, the written communication must be delivered no later than 60 days after the report release date of the financial statements.2AICPA. AU-C Section 265 – Communicating Internal Control Related Matters Identified in an Audit When a deficiency is serious enough that waiting could cause harm, the auditor is expected to raise it during the engagement rather than hold it for the letter. The standard explicitly contemplates mid-audit communication when timely action matters.
Lesser Deficiencies and Repeat Findings
Deficiencies that don’t rise to a significant deficiency or material weakness may be communicated to management either in writing or verbally. Which lesser deficiencies deserve mention is a judgment call, using the same likelihood-and-magnitude analysis.2AICPA. AU-C Section 265 – Communicating Internal Control Related Matters Identified in an Audit Verbal communication during fieldwork counts, but the auditor has to document that the conversation happened.
If management was told about a minor deficiency in a prior year and did not fix it, the auditor does not have to repeat the communication. But if the unresolved issue has worsened or now fits a pattern, it can escalate into a significant deficiency requiring formal reporting.2AICPA. AU-C Section 265 – Communicating Internal Control Related Matters Identified in an Audit Significant deficiencies and material weaknesses reported in prior years that remain unresolved must be reported again in the current period’s written communication.5National Indian Gaming Commission. Bulletin 2009-1 – Relationship of SAS 112 and SAS 115 The standard gives the auditor no room to quietly drop an issue on the grounds that everyone already knows about it. Until the weakness is fixed, the board sees it in writing each year.
SAS 115, AU-C 265, and the PCAOB Standard
The AICPA’s Clarity Project recodified SAS 115 as AU-C Section 265, which is the current standard for nonpublic entities. The definitions of significant deficiency and material weakness carried over with minor wording refinements, and AU-C 265 added the explicit 60-day deadline along with more detailed application guidance, including the inventory example above.2AICPA. AU-C Section 265 – Communicating Internal Control Related Matters Identified in an Audit For public company audits, the equivalent is PCAOB AS 1305, which requires the communication before the auditor’s report is released rather than up to 60 days after.6Public Company Accounting Oversight Board. Communications About Control Deficiencies in an Audit of Financial Statements Anyone researching SAS 115 for a current nonpublic engagement is working under AU-C 265, and the classification framework, evaluation criteria, and reporting obligations are functionally the same.