AUD · Assessing Risk and Developing a Planned Response · 6 practice questions
Control Environment vs. Process Controls: AUD Classification
Governance and management's ethical tone belong to the control environment; controls over specific revenue steps belong to the business process. Sort alternative observations about Harbor Co.'s revenue controls, judging each fact on its own.
Try one first
Hint
Focus on which observation relates to governance, oversight, and tone at the top (affecting the whole entity) versus problems that are specific to a transaction cycle.
Answer D. Weak governance and a deficient tone at the top, such as an inactive board and an ineffective audit committee, are core elements of the control environment and can affect controls across the entire entity. The other observations describe control failures confined to specific transaction cycles (sales, inventory, accounts payable), which are process-level weaknesses.
Why not A: This is a vendor-master and payment-process control weakness that could enable fraud (e.g., redirected payments), but it is localized to accounts payable procedures rather than reflecting weak overall governance or tone at the top.
Why not B: This describes a breakdown in controls over the sales/order-entry process (segregation of duties and approval controls) that increases revenue misstatement risk but is confined to that transaction cycle rather than indicating pervasive governance failure.
Why not C: This is a segregation-of-duties and monitoring issue within the inventory cycle that could lead to inventory misstatements, but it is a process-level weakness rather than an entity-level control environment deficiency.
Sort it
Does the fact address board oversight, companywide ethics, or management's attitude toward controls?
Does the fact describe a specific revenue-processing step or a missing control over that step?
| Item | Goes to |
|---|---|
| The independent audit committee regularly challenges management's revenue recognition judgments. | Control environmentIndependent challenge of management is governance oversight, not a step in processing sales. |
| The controller approves each manual revenue journal entry before posting. | Process-level control or reviewApproving individual revenue entries is an authorization control, even when a senior accounting officer performs it. |
| The CEO repeatedly directs staff to bypass customer credit holds to meet sales targets. | Control environmentThe key fact is management's willingness to override controls for reported results, not merely a failed credit check. |
| The sales system blocks invoicing until the related shipment is recorded. | Process-level control or reviewThe system enforces a specific billing step within the revenue process. |
| Written sales procedures require supervisor approval before releasing orders that exceed customer credit limits. | Process-level control or reviewThese instructions govern transaction authorization. Being written does not make them a control-environment item. |
| The board approves a companywide code of conduct, and employees acknowledge it annually. | Control environmentThe code establishes companywide ethical expectations rather than instructions for processing a particular sale. |
| Sales managers share an override password that releases orders blocked by credit-limit checks. | Process-level control or reviewThe stated weakness concerns access and authorization within order processing, not senior management's ethical attitude. |
| The board consists mainly of the founder's family and rarely challenges management's accounting decisions. | Control environmentThe fact identifies weak governance and ineffective oversight of management. |
| The controller reviews weekly exception reports for shipments that have not been invoiced. | Process-level control or reviewThe review detects exceptions within the revenue process; it does not provide governance oversight. |
| The CEO discourages employees from questioning management's revenue accounting judgments. | Control environmentManagement's response to challenge reveals its attitude toward ethics and internal control. |
| The controller reconciles the accounts receivable subledger to the general ledger each month. | Process-level control or reviewThe reconciliation checks agreement between accounting records within a specific business process. |
| Sales staff grant nonstandard return rights by email, with no required accounting review of those terms. | Process-level control or reviewThe gap concerns review and communication of specific sales terms, not broad governance or ethics. |
Key points
- Remember: A controller approving a sales entry is a process control; a CEO encouraging bypasses is control environment.
- Both categories can contain strengths or weaknesses; classification does not determine whether a control works.
- Strong governance does not repair a revenue-process gap, and effective process controls do not cancel out management override.
How the exam traps you
- Treating every written policy as a control-environment item. A companywide ethics code addresses the control environment. Written credit-approval steps address the revenue process.
- Calling every controller review a control-environment control. Look at the task. Approving entries and reviewing revenue exception reports are process-level procedures.
- Letting invoice-shipment matching outweigh the CEO's override instructions. Classify the matching as a process control and the CEO's attitude as a control-environment weakness.
Question 2
Hint
Focus on whether the facts describe the company's tone at the top or the operation of a specific control process.
Answer B. The facts describe management's attitude, integrity, ethical values, and willingness to override controls, core elements of the control environment. The control environment sets the tone at the top and strongly influences whether other controls are effective. Even with formal procedures in place, a poor tone at the top increases the risk of material misstatement.
Why not A: This distractor is tempting because accounting judgments and personnel behavior are mentioned, but the scenario does not focus on how transactions are initiated, recorded, or communicated. The primary issue is management behavior, not the design or operation of the information system.
Why not C: Control activities include approval policies that are being overridden, so this is a plausible choice. However, the stem emphasizes management's willingness to bypass controls and pressure staff, a broader tone-at-the-top issue that is part of the control environment rather than the specific control activities themselves.
Why not D: Monitoring concerns ongoing evaluation of controls and corrective actions. While poor oversight could be related, the facts center on leadership behavior and ethical tone, which points more directly to the control environment than to monitoring.
Question 3
Hint
Separate entity-level control environment issues from transaction-level control activities, then decide which one carries more weight in the fact pattern.
Answer D. Management override of controls and a culture that discourages questioning indicate a weak control environment. Entity-level weaknesses like these can undermine the effectiveness of transaction-level controls because employees may not consistently follow procedures when management signals exceptions are acceptable. The auditor should consider this when assessing risks of material misstatement and planning further procedures.
Why not A: Even when transaction-level controls operate, tone at the top is a core element of the control environment. Conflicting facts (presence of overrides and a discouraged questioning culture) increase the need to evaluate entity-level controls and may require more emphasis on professional skepticism and testing.
Why not B: This distractor is tempting because bank reconciliations and three-way matching are effective transaction controls. However, such controls do not automatically neutralize an adverse control environment, management override can reduce the reliability of detailed controls.
Why not C: Candidates may associate override primarily with fraud, but management override is also central to the control environment and affects the auditor's overall assessment of internal control and risks of material misstatement, not just fraud-focused work.
Question 4
Hint
Separate entity-level control environment strengths from process-level points where a material misstatement could still enter the financial reporting system.
Answer C. A strong control environment does not remove a process-level design gap that allows contract terms affecting revenue to be initiated and communicated outside the normal system flow. Here, there is no control requiring accounting or legal review of nonstandard, quarter-end terms, so misstatements in revenue recognition assertions (accuracy, completeness, cutoff) are possible. The auditor should therefore treat this as an assertion-level risk in the revenue process rather than concluding a pervasive financial-statement-level failure.
Why not A: Tempting because indicators such as an active audit committee and low turnover suggest a strong control environment. It is wrong because even infrequent, quarter-end side arrangements can produce material misstatements and the facts identify a process gap that could permit misstatements to enter the accounting records.
Why not B: Tempting because out-of-system term changes and quarter-end pressure can signal broad control problems. It is wrong because the evidence points to a specific revenue-process communication/approval gap, not a pervasive breakdown across all transaction cycles.
Why not D: Tempting because the ERP is central to the sales cycle and the issue involves terms not captured in the system. It is wrong because the primary deficiency is a business-process control (identification/approval of nonstandard terms), not an IT general control like access or change management.
Question 5
Hint
Focus on who can initiate, record, and authorize transactions, and whether management oversight directly addresses that risk.
Answer B. One person controls vendor setup, records invoices, and approves payments without direct oversight of those specific activities, creating incompatible duties and increasing the risk of improper payments. This is both a process-level weakness and a control-environment concern because management is not monitoring a high-risk cycle. The auditor should recognize the increased risk and plan additional procedures or recommend compensating controls.
Why not A: This is tempting because documentation is important, but controls can operate informally in smaller entities. The core problem here is the concentration of duties and lack of oversight, not the absence of a formal manual.
Why not C: Owner-level monthly reviews are high-level and do not directly detect unauthorized vendor additions or individual disbursements. Such reviews are too indirect to fully compensate for one person performing initiation, recording, and authorization.
Why not D: Size and employee experience do not eliminate segregation-of-duties risk. Small entities still need compensating oversight (e.g., independent review of vendor changes and payments) because one-person control of the cycle creates a significant fraud risk.
Question 6
Hint
Focus on whether the fact describes the organization’s overall tone, governance, and commitment to integrity, or instead describes a control embedded in a specific transaction or closing process.
Answer D. This scenario reflects tone at the top, management bias in financial reporting, and weak governance oversight, core elements of the control environment. It is pervasive and affects the entity broadly rather than being confined to a single transaction stream or control activity.
Why not A: Segregation-of-duties and vendor-add/authorization weaknesses are serious but are rooted in the purchasing/accounts-payable process; they represent process-level control design or operating deficiencies, not an overarching tone or governance failure.
Why not B: Password sharing and inappropriate overrides concern access controls and authorization within the revenue/order process. While they can enable misstatement, they are process/IT control issues rather than evidence of entity-level ethical or governance breakdown.
Why not C: An inadequate reconciliation review is an ineffective control in the close/cash process. Although the monthly close affects reporting, the deficiency as stated is a process-level review weakness, not a pervasive indicator of management's integrity or board oversight.
Common questions
Is a code of conduct part of the control environment?
A board-approved, companywide ethics code is a control-environment item. Its existence alone does not prove an effective control environment when management discourages questions or directs employees to bypass controls.
Are reconciliations part of the control environment or control activities?
Reconciling the accounts receivable subledger to the general ledger is a process-level control activity. Having the controller perform it does not make it part of the control environment.
Is overriding a credit limit always a control-environment weakness?
No. A shared sales override password is a revenue-process weakness. The CEO directing staff to bypass credit holds for sales targets is a control-environment concern.
Watch it solved
A full CPA AUD task-based simulation on Understanding an Entity's Control Environment and Business Processes, worked step by step.
Control Deficiencies and Audit Response | CPA AUD Simulation (TBS) on YouTube
Practice AUD like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Understanding an Entity's Control Environment and Business Processes
- Management Override Risk: Tone at the Top in AUD
- AUD Walkthroughs When You Do Not Rely on Controls
- When to Update Audit Understanding After an ERP Change
- Weak AP Controls and ITGCs: How to Change the Audit Plan
All Understanding an Entity's Control Environment and Business Processes practice →
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.