Explore why internal control deviations matter in the audit process, how auditors determine their severity, and how deviations influence overall risk assessment and substantive testing approaches.
As part of testing and evaluating internal controls (discussed in Chapter 9), auditors often encounter instances where controls do not operate as intended. These lapses are called “deviations.” Understanding how to identify, investigate, classify, and respond to deviations is essential to refining the overall audit strategy. This section explores the significance of control deviations, how auditors weigh their severity, and how deviations ultimately shape the assessment of audit risk.
A “deviation” arises when a control procedure is not performed or is improperly executed. At the most basic level, if a process requires dual authorization but only one signature is observed, this is a clear deviation. Deviations can take many forms:
• Missing approvals or insufficient documentation.
• Incomplete data fields during transaction processing.
• Manual overrides of key system controls.
• Evidence that certain control steps are consistently skipped (e.g., no timely reconciliations).
These deviations can be isolated or occur repeatedly. An isolated instance might reflect a minor oversight, whereas multiple deviations in a small sample may indicate systemic weaknesses. Regardless of scope, each identified deviation compels the auditor to question whether the tested control is truly effective.
Consider an auditor reviewing a sample of 30 purchase orders (POs) to test proper authorization. Suppose the auditor discovers three POs missing the required signature of the approving manager. This shortfall indicates some level of control deficiency. The auditor must investigate whether this is a frequent occurrence, who is responsible, and whether any fundamental process or training gap exists.
The severity of a deviation is shaped by both its qualitative and quantitative characteristics. Certain deviations may appear minor at first glance yet signal deeper control challenges when combined with additional evidence.
Quantitative Factors (Frequency and Volume)
– A single missing authorization in 30 transactions might be less concerning than five missing authorizations within the same sample size.
– High frequency or large error amounts suggest a higher level of control risk.
Qualitative Factors (Nature and Circumstances)
– Deviations involving management overrides can suggest a serious ethical or cultural concern.
– Repeated system overrides or consistent “workarounds” to bypass controls indicate potential pervasive issues.
– One instance of missing “review” in a large dataset might indicate a simple oversight, but multiple repeated lapses may reflect a systemic training or monitoring deficiency.
Potential Impact on Financial Statements
– If the deviated control is designed to prevent material misstatements in high-risk areas (e.g., revenue recognition), even a single failure could be significant.
– Conversely, if the control relates to a relatively low-risk process, a deviation may be less material.
It is critical to discern whether the deviation is an isolated error due to human oversight or an inherent flaw in the control system. For instance, discovering one incorrectly recorded sales transaction could be clerical; however, if multiple employees have bypassed the sales approval step to speed up shipments at month-end, the issue is systemic and signals a broader compliance or cultural problem within the organization.
Some deviations arise because employees do not follow instructions accurately or are insufficiently trained. For instance, staff might not understand the importance of uploading all required supporting documents into the system. Such issues often point to a need for additional training or improved documentation.
In certain cases, software errors lead to incorrect or incomplete data capture. If a system fails to require a password re-entry for high-value transactions, the control is effectively circumvented. Identifying such an IT-related deviation triggers both deeper IT testing and potential remediation steps by the client’s IT department.
These deviations are the most concerning. When management personnel override established controls—for instance, bypassing an approval process for personal gain—the potential for fraud elevates. Such overriding signals a breakdown in the control environment and often warrants significant additional audit work, including extended substantive testing.
Auditing standards emphasize that risk assessment is an ongoing process. When deviations surface or their severity increases, the auditor must re-evaluate and potentially revise the planned approach.
Revising the Audit Plan
– The auditor may need to increase the extent of substantive testing if controls appear less reliable than initially anticipated.
– The timing of testing may change: More interim testing or year-end testing might be required.
– Testing might expand to additional locations or business units if the deviation is suspected to be widespread.
Discussing With Management and Governance
– Material or pervasive control failures often require communication with senior management and those charged with governance (such as the audit committee).
– These discussions may prompt management to reinforce training, adjust control procedures, or implement technology solutions.
Entity-Level Impact
– Certain deviations could reflect a broader organizational issue, such as a weak control environment or lax tone at the top.
– Auditors should consider how these deficiencies may affect other aspects of financial reporting, raising the overall assessment of engagement risk.
Below is a simple mermaid diagram illustrating how control deviations feed into the iterative risk assessment process:
flowchart LR A[Identify Deviations] --> B{Evaluate Severity} B --> C[Assess Frequency, Nature, Potential Fraud] C --> D[Revise Risk Assessment?] D --> E[Adjust Substantive Procedures] D --> F[Communicate with Management & Governance]
As shown, the process is not a one-time event. Any time deviations are discovered, the auditor evaluates them and decides if risk assessments need updating. This may lead to expanded testing, changes in audit approach, and more rigorous communication protocols.
• Deviation: An instance where the expected control procedure was not performed, was bypassed, or did not operate as designed.
• Systemic Failure: A control deficiency indicating widespread issues, potentially affecting numerous transactions or departments.
• Isolated Failure: A situation in which a small number of deviations appear unique or infrequent.
• Iteration of Risk Assessment: The recognition that reevaluating risk is a continuous activity that evolves as new evidence emerges during the audit.
• AU-C Section 265 – Communicating Internal Control Related Matters Identified in an Audit.
• PCAOB inspection reports often highlight frequent control shortcomings related to authorization, documentation, and IT controls. Reviewing these reports can help auditors anticipate common pitfalls and develop robust testing strategies.
Auditing & Attestation CPA Mock Exams (AUD): Comprehensive Prep
• Tackle full-length mock exams designed to mirror real AUD questions—from risk assessment and ethics to internal control and substantive procedures.
• Refine your exam-day strategies with detailed, step-by-step solutions for every scenario.
• Explore in-depth rationales that reinforce understanding of higher-level concepts, giving you a decisive edge on test day.
• Boost confidence and reduce exam anxiety by building mastery of the wide-ranging AUD blueprint.
Disclaimer: This course is not endorsed by or affiliated with the AICPA, NASBA, or any official CPA Examination authority. All content is created solely for educational and preparatory purposes.