AU-C Section 330: Performing Audit Procedures

AU-C Section 330 tells the auditor how to turn assessed risks into actual audit procedures. It requires overall responses to risks at the financial statement level, further audit procedures at the assertion level whose nature, timing, and extent are tied to those risks, and an evaluation of whether the resulting evidence is sufficient and appropriate. The standard is the connective tissue between the risk assessment performed under AU-C Section 315 and the fieldwork that follows: every audit procedure should trace back to a specific identified risk, and AU-C 330 is what enforces that linkage.

Overall Responses to Financial Statement-Level Risks

Before designing procedures for individual accounts or transaction classes, the auditor addresses risks that pervade the financial statements as a whole. These responses are not aimed at any single assertion. They shape the audit’s overall posture and reinforce professional skepticism across the engagement team.

Typical overall responses include assigning more experienced personnel or specialists, increasing supervision, and modifying the overall audit strategy. When the control environment is weak or management’s integrity is in question, the auditor may shift work toward or near the balance sheet date instead of relying on interim procedures, increase sample sizes, or change the mix of procedures to draw more heavily on external evidence.

Incorporating Unpredictability

The standard requires the auditor to build unpredictability into the engagement. The purpose is to keep management from anticipating and working around the audit, which is primarily a fraud-prevention measure. Unpredictability can be introduced by substantively testing accounts not otherwise selected on materiality or risk grounds, changing the timing of procedures from what the client expects, using different sampling methods, or performing procedures at locations without advance notice.

In practice that might mean lowering the threshold for the search for unrecorded liabilities well below prior years, confirming an immaterial bank account that has never been confirmed, testing a mid-year bank reconciliation rather than only year-end, or verifying the existence of randomly selected vendors to catch fictitious payees. These procedures need to change from engagement to engagement. An “unpredictable” test performed the same way every year is no longer unpredictable.

Nature, Timing, and Extent at the Assertion Level

At the assertion level, AU-C 330 requires further audit procedures whose nature, timing, and extent respond to the assessed risk of material misstatement. The three dimensions work together, and higher assessed risk calls for more persuasive evidence across all of them.

Nature covers both the purpose of a procedure (test of controls or substantive procedure) and its type: inspection, observation, external confirmation, recalculation, reperformance, analytical procedure, or inquiry. A higher-risk assertion warrants procedure types that produce inherently more reliable evidence. External confirmation from a third party, for example, is stronger than inspection of internally generated documents.

Timing refers to when the procedure is performed, either at an interim date or at period-end. Higher-risk assertions push testing toward the balance sheet date, where the evidence more directly addresses the reported balance. Interim testing creates an obligation to cover the remaining period.

Extent is the quantity of testing, most often expressed as sample size. Higher risk means larger samples or more thorough analytical procedures. Increasing extent alone, without adjusting nature or timing, will not necessarily produce persuasive enough evidence for a high-risk area.

The design is not formulaic. Two assertions with the same risk rating can call for very different procedure combinations depending on the account’s characteristics, the control environment, and the evidence available. What matters is that the auditor can explain, specifically, why each procedure addresses the risk it targets. “We tested revenue because revenue is material” misses the requirement. “We confirmed key receivable balances because the risk of fictitious revenue near year-end is elevated by the sales incentive structure” meets it.

Tests of Controls

The auditor designs and performs tests of controls in two situations. The first is when the risk assessment assumes controls are operating effectively and the auditor plans to reduce substantive testing on that basis. The second is when substantive procedures alone cannot provide sufficient appropriate evidence for a given assertion. The second case arises more often than expected, especially in highly automated processes where the volume of transactions makes item-by-item substantive testing impractical and the real risk lies in whether the system’s controls work.

Testing a control’s operating effectiveness involves procedures such as reperformance (independently executing the control to see whether you reach the same result), inspection of documentary evidence that the control was applied, and observation of the control in action. The control must be tested across the entire period of intended reliance. Evidence that a control worked in March says nothing about September.

Relying on Prior Period Evidence

The standard allows use of evidence about a control’s effectiveness from a prior audit, but only within limits. The control must not have changed since the prior assessment, and the auditor must still test at least some controls each year. Factors to consider include whether the control environment has shifted, whether the control is manual or automated, and how strong the prior testing results were. Significant changes in the control or in the related risk require retesting in the current period regardless of prior results. Automated controls sitting inside IT systems with effective general IT controls generally warrant less frequent retesting than manual controls that turn on human judgment.

Control Deviations

When testing surfaces a deviation, the auditor cannot simply log the exception and move on. The standard requires additional inquiry to understand the deviation’s nature and possible consequences. A single deviation in a sample may indicate a one-off error, or it may signal a systemic breakdown. The auditor must decide whether the original risk assessment still holds. If it does not, planned substantive procedures must be modified to compensate for the reduced control reliance.

Substantive Procedures

Regardless of the assessed level of risk and regardless of how well controls performed in testing, AU-C 330 requires substantive procedures for each material class of transactions, account balance, and disclosure. This is a floor, not a ceiling. Even when tested controls are operating effectively, substantive testing of a material account cannot be skipped altogether. Substantive procedures fall into two categories: tests of details and substantive analytical procedures.

Substantive analytical procedures work best for large volumes of predictable, stable transactions where the auditor can build a reliable expectation. Payroll expense for a company with steady headcount and pay rates is a natural candidate. For assertions tied to significant risks the standard raises the bar: when the response to a significant risk consists only of substantive procedures, those procedures must include tests of details rather than relying solely on analytics.

The Financial Statement Closing Process

AU-C 330 specifically requires substantive procedures over the financial statement closing process. That includes evaluating journal entries recorded during the close, testing the consolidation and aggregation of financial data, and examining adjustments made in preparation of the financial statements. The closing process is where many misstatements land, because it involves significant management judgment and manual intervention outside the normal transaction-processing controls.

Responding to Management Override

Management override of controls is treated as a significant risk in every audit. Because management can manipulate records by overriding controls that otherwise function properly, the auditor cannot rely on controls alone to address this risk. Required responses include examining journal entries and other adjustments for evidence of possible material misstatement due to fraud, reviewing accounting estimates for bias, and evaluating whether the business rationale for significant unusual transactions suggests they were entered into for fraudulent purposes.1Public Company Accounting Oversight Board. AS 2401 Consideration of Fraud in a Financial Statement Audit

Journal entry testing deserves particular attention. The auditor needs to understand the entity’s financial reporting process, identify and select entries for testing (focusing on entries made at unusual times, by unexpected individuals, or to unusual accounts), and inquire of people involved in the reporting process about any inappropriate activity. A retrospective review of prior-year accounting estimates against actual results can also reveal patterns of management bias that would not be visible in any single period.1Public Company Accounting Oversight Board. AS 2401 Consideration of Fraud in a Financial Statement Audit

Interim Testing and the Remaining Period

When substantive procedures are performed at an interim date, the auditor must cover the period between that date and the balance sheet date. This can be done through additional substantive procedures, through a combination of substantive procedures and tests of controls, or, in some cases, by performing substantive procedures at period-end when extending the interim conclusion would not be reliable.

The decision is not routine. The auditor considers whether interim procedures revealed unexpected misstatements, whether period-end balances are reasonably predictable, and whether controls over the remaining period are effective. If unexpected misstatements come up at the interim date, the auditor must reevaluate the related risk assessment and consider whether the planned nature, timing, or extent of procedures for the remaining period should change.

For significant risks, the standard effectively discourages heavy reliance on interim testing. Substantive procedures should be performed at or near period-end for those assertions, because the consequences of missing a misstatement in a high-risk area are too severe to bridge with rollforward procedures alone.

Evaluating Whether the Evidence Is Sufficient and Appropriate

After performing the planned procedures, the auditor steps back and evaluates whether the evidence is enough. Sufficiency is the quantity of evidence. Appropriateness is its quality, meaning its relevance to the assertion being tested and its reliability given the source and circumstances. The two dimensions interact: higher-quality evidence means less of it is needed, and lower-quality evidence has to be compensated for with more volume.

This evaluation runs throughout the engagement rather than sitting at the end of fieldwork. Evidence gathered during testing may contradict the initial risk assessment, reveal risks that were not previously identified, or raise doubts about whether other planned procedures are still adequate. When that happens, the auditor must revise the risk assessment and modify the remaining procedures. A material misstatement discovered in accounts receivable should prompt reconsideration of whether the revenue procedures already completed are still sufficient.

Several factors shape how much evidence is enough: the complexity of the account, the reliability of the sources, the effectiveness of internal controls, and the results of the procedures themselves. Evidence from independent external sources is generally more reliable than internally generated evidence. Evidence obtained directly by the auditor is more reliable than evidence obtained indirectly. Original documents beat photocopies or oral representations.

When Evidence Falls Short

If the auditor cannot obtain sufficient appropriate evidence for a material assertion after exhausting reasonable avenues, the consequences are direct. The auditor must first try alternative procedures. If those also fail, the result is a scope limitation that affects the audit opinion. Depending on the magnitude and pervasiveness of the limitation, the opinion is either qualified (when the possible effects are material but not pervasive) or disclaimed (when the possible effects are both material and pervasive).

Documentation

AU-C 330 requires documentation of the overall responses to risks at the financial statement level, the nature, timing, and extent of further audit procedures performed, the linkage between those procedures and the assessed risks at the assertion level, and the results of the procedures. The documentation must also include the auditor’s conclusion about whether sufficient appropriate audit evidence has been obtained.

The linkage requirement is the one that most often trips up engagement teams. Documenting what was done is not enough. The file must show why each procedure was selected and which specific risk it addresses. Peer reviewers routinely flag engagements where the risk assessment identifies elevated risks but the audit program looks identical to what the firm would run for a low-risk client. The documentation should make it plain that procedures were tailored to the assessed risks rather than lifted from a template.