SOX 404 Testing Lifecycle
End-to-End Phases
- Scoping: Determine which accounts and processes carry enough risk to warrant control coverage
- Risk evaluation: Assess the probability and magnitude of potential misstatement for each in-scope account
- Control mapping: Document the specific controls that mitigate each identified risk
- Effectiveness testing: Evaluate whether controls are properly engineered (design) and consistently executed (operation)
- Deficiency assessment: Judge the severity of any control gaps uncovered during testing
- Management reporting: Formalize the overall ICFR assessment and disclose any material weaknesses
Determining Which Accounts Are In Scope
An account enters scope when it carries a non-remote probability of containing a misstatement that is material on its own or in combination with others.
Size-based indicators:
- The balance surpasses the quantitative materiality benchmark (commonly 3-5% of a reference figure such as revenue, assets, or pre-tax income)
- High transaction throughput increases the statistical likelihood of error
- The balance depends heavily on estimates or management judgment
Risk-based indicators:
- The accounting is inherently complex (multi-element revenue arrangements, derivative instruments, pension obligations)
- The account is a common fraud target (cash, revenue, related-party activity)
- Historical audit adjustments or prior restatements have affected the account
- Significant management estimates or subjective assumptions underlie the balance
- The account or process is new, or has undergone material change
Financial Statement Assertions by Account Category
| Account Category |
Primary Assertions to Address |
| Revenue |
Occurrence, Completeness, Measurement, Period allocation |
| Trade receivables |
Existence, Valuation (reserve adequacy), Ownership rights |
| Inventory |
Existence, Valuation, Completeness |
| Property & equipment |
Existence, Valuation, Completeness, Ownership rights |
| Trade payables |
Completeness, Measurement, Existence |
| Accrued obligations |
Completeness, Valuation, Measurement |
| Shareholders' equity |
Completeness, Measurement, Presentation |
| Close & reporting process |
Presentation, Measurement, Completeness |
Design vs. Operating Effectiveness
Design effectiveness asks: Is the control architected to intercept or surface a material misstatement in the targeted assertion?
- Assessed via end-to-end walkthroughs (trace a representative transaction through the full process)
- Confirm the control sits at the correct process juncture
- Confirm the control directly addresses the specified risk
- Re-evaluate at least annually, or whenever the process changes
Operating effectiveness asks: Has the control actually functioned as intended across the entire period under review?
- Assessed via inspection, observation, recalculation, or inquiry (with corroboration)
- Requires sample sizes large enough to support a reliable conclusion
- Must span the full reliance period (not just a single point in time)
Sampling Methodologies
Statistical Random Sampling
Applicability: Standard approach for high-volume, transaction-level controls.
Steps:
- Define the universe: every transaction subject to the control during the test period
- Assign a sequential identifier to each population item
- Apply a random-number generator to draw the sample
- Confirm every item had an equal selection probability (no systematic exclusion)
Strengths: Statistically defensible, free of selection bias
Limitations: May not capture high-risk outliers; requires a complete population listing
Risk-Directed (Judgmental) Sampling
Applicability: Complements random sampling by targeting items with elevated risk characteristics; serves as the primary method for small or heterogeneous populations.
Targeting criteria:
- Transactions above a defined dollar threshold
- Atypical or non-standard entries
- Activity near the period boundary (cut-off exposure)
- Related-party transactions
- Manual overrides or exception-processed items
- First-time vendors or customers
Strengths: Focuses testing effort on highest-risk items
Limitations: Not statistically representative; must document the selection rationale
Unstructured (Haphazard) Sampling
Applicability: Situations where a numbered population is unavailable and items are relatively uniform.
Steps:
- Select items without a deliberate pattern
- Distribute selections across the entire test period
- Guard against unconscious tendencies (gravitating toward top-of-list, round figures, etc.)
Strengths: Simple, requires no tooling
Limitations: Not statistically valid; vulnerable to unintentional bias
Interval-Based (Systematic) Sampling
Applicability: Sequential populations where uniform period coverage is desired.
Steps:
- Compute the selection interval: total population count divided by target sample size
- Pick a random starting point within the first interval
- Select every Nth item from that starting point forward
Illustration: 1,000-item population, 25-item sample -> interval of 40. Random start at item 12. Selections: 12, 52, 92, 132 ...
Strengths: Guarantees even distribution across the population
Limitations: Periodic patterns in the data could skew results
Sample Size Reference Table
| Control Cadence |
Approximate Population |
Lower-Risk Sample |
Moderate-Risk Sample |
Higher-Risk Sample |
| Annual |
1 |
1 |
1 |
1 |
| Quarterly |
4 |
2 |
2 |
3 |
| Monthly |
12 |
2 |
3 |
4 |
| Weekly |
~52 |
5 |
8 |
15 |
| Daily |
~250 |
20 |
30 |
40 |
| Per-transaction (under 250) |
< 250 |
20 |
30 |
40 |
| Per-transaction (250+) |
250+ |
25 |
40 |
60 |
Conditions that warrant larger samples:
- Elevated inherent risk in the account or process
- The control is the only safeguard for a significant risk (no backup control)
- A deficiency was noted in a prior testing cycle
- The control is newly implemented and untested historically
- External auditors plan to rely on management's testing results
Workpaper & Evidence Standards
Required Workpaper Sections
Control profile:
- Unique control identifier
- Narrative description (who does what, how frequently)
- Classification (manual, automated, IT-dependent manual)
- Execution frequency
- Targeted risk and assertion
Test blueprint:
- Stated objective of the test
- Detailed procedural steps
- Description of expected evidence when the control is working
- Sampling method and rationale for approach chosen
Execution record:
- Population description and total count
- Sample items selected (method and specific identifiers)
- Item-by-item results (pass/fail with the specific evidence inspected)
- Full narrative for every exception observed
Overall conclusion:
- Effectiveness rating (effective / deficiency / significant deficiency / material weakness)
- Reasoning supporting the conclusion
- Magnitude assessment for any exceptions
- Compensating controls evaluated, if relevant
Accountability:
- Tester signature and date
- Reviewer signature and date
What Constitutes Adequate Evidence
Acceptable:
- System screenshots capturing enforced controls or configurations
- Documents bearing a signature, initials, or electronic approval stamp
- Email trails with an identifiable approver and a discernible date
- Application audit logs recording the actor, action, and timestamp
- Independent recalculations that reproduce the recorded result
- Written observation notes specifying date, location, and observer
Not sufficient on its own:
- Oral statements without corroboration
- Documents lacking a date
- Evidence with no identifiable performer or approver
- System-generated output missing date/time metadata
- Notes reading "per conversation with [name]" absent supporting documentation
File Organization Convention
ICFR Testing/
[Fiscal Year]/
Scoping & Risk Assessment/
Revenue Process/
Control Matrix
Walkthrough Narrative
Individual Test Workpapers
Evidence Attachments
Purchase-to-Pay Process/
Payroll Process/
Financial Close Process/
Treasury Process/
Capital Assets Process/
IT General Controls/
Organization-Level Controls/
Aggregation & Conclusions/
Deficiency Evaluation Workpaper
Management ICFR Assessment
Deficiency Severity Framework
Simple Deficiency
A gap exists when a control's design or execution does not enable personnel to prevent or detect misstatements in the ordinary course of their responsibilities.
Evaluation dimensions:
- How likely is it that the gap could produce a misstatement?
- How large could the resulting misstatement be?
- Does a compensating control reduce the residual exposure?
Significant Deficiency
A deficiency (or cluster of deficiencies) that falls short of material-weakness severity but is consequential enough to require governance-body attention.
Hallmarks:
- Could produce a misstatement that is more than trivial but less than material
- Probability of material misstatement is above remote but below reasonably possible
- Involves a key control where compensating measures do not fully offset the gap
- Several individually minor gaps that, taken together, raise substantive concern
Material Weakness
A deficiency (or cluster of deficiencies) creating a reasonable possibility that a material financial-statement misstatement will escape prevention or detection.
Strong indicators:
- Senior management fraud of any dollar magnitude
- Restatement of previously filed financials to correct a material error
- Auditor detection of a material misstatement that the entity's own controls missed
- Breakdown in audit-committee oversight of the financial reporting process
- Failure of a pervasive control (organization-level or IT general) with downstream impact across multiple cycles
Aggregation Analysis
Individually minor gaps may be severe in combination:
- Collect all deficiencies affecting the same process or assertion
- Evaluate whether their combined effect could permit a material misstatement
- Consider whether a weakness in a compensating control amplifies other gaps
- Document the aggregation logic and the resulting severity classification
Remediation Protocol
For every identified gap:
- Root-cause diagnosis: Determine why the control failed (design flaw, execution lapse, resource constraint, training gap, system limitation)
- Corrective action plan: Define specific steps to restore effectiveness (redesign, additional staffing, enhanced training, system configuration change, added review layer)
- Target completion date: Set a realistic but firm deadline
- Accountable owner: Assign a named individual responsible for execution
- Validation procedure: Specify how and when the remediated control will be re-tested to confirm it is operating effectively
Control Taxonomy
IT General Controls (ITGCs)
Infrastructure-level controls ensuring that application controls and automated processes function reliably.
Logical access governance:
- New-user provisioning requires documented, pre-implementation approval
- Terminated-user accounts are disabled within a defined SLA
- Privileged/administrator access is restricted and subject to enhanced monitoring
- Periodic recertification reviews validate that access remains appropriate
- Password standards enforce complexity, rotation, and lockout thresholds
- Conflicting duties are systematically prevented through role-based access design
Change governance:
- Every change request is documented and approved prior to deployment
- Changes are validated in a non-production environment before promotion
- Development and production environments are logically or physically separated
- Emergency changes follow a defined expedited path with post-implementation sign-off
- Post-deployment reviews confirm changes behave as intended
Operational continuity:
- Automated job scheduling is monitored with exception alerting
- Backups execute on schedule and restore procedures are periodically tested
- System uptime and performance are tracked against defined SLAs
- Incident response and escalation procedures are documented and rehearsed
- Disaster recovery plans are maintained and tested at defined intervals
Manual (Human-Performed) Controls
Controls relying on individual judgment, typically involving review, approval, or verification activities.
Representative controls:
- Leadership review of financial results and operating metrics
- Supervisory sign-off on journal entries exceeding a dollar threshold
- Three-way matching of purchase order, goods receipt, and vendor invoice
- Preparation and independent review of account reconciliations
- Physical observation and counting of inventory
- Authorization of vendor or customer master-data changes
- Credit-limit approval for new or expanded customer relationships
Attributes to verify during testing:
- The control was performed by someone with proper authority
- Execution occurred within the prescribed time window
- Observable evidence of the review exists (signature, initials, system notation, email)
- The reviewer had access to sufficient supporting information
- Identified exceptions were investigated and appropriately resolved
Automated (System-Enforced) Controls
Controls embedded in application logic that execute without human intervention.
Representative controls:
- Workflow engines that block progression without required approvals
- Automated three-way match that withholds payment when PO, receipt, and invoice disagree
- Duplicate-detection algorithms that flag or reject repeated invoice submissions
- Credit-limit enforcement that prevents order entry beyond the approved threshold
- System-calculated depreciation, amortization, interest, and tax computations
- Role-based access configurations that prevent users from holding conflicting privileges
- Field-level validations (mandatory fields, format masks, range constraints)
- Automated transaction-matching within reconciliation modules
Testing approach:
- Confirm the system configuration enforces the control as specified (design test)
- For unchanged configurations, a single successful test typically covers the period (operating effectiveness), provided change-management ITGCs are also effective
- If the configuration was modified during the period, re-test post-change
IT-Dependent Manual Controls
Manual review or approval activities that depend on the completeness and accuracy of system-produced data.
Representative controls:
- Management review of a system-generated exception or outlier report
- Reserve estimation based on a system-generated aging analysis
- Account reconciliation performed using system-extracted trial balance data
- Transaction approvals triggered by system-generated workflow notifications
Testing approach:
- Test the human element (review quality, follow-up on exceptions, evidence of approval)
- Separately validate the information produced by the entity (IPE) — confirm the underlying report or data extract is complete and accurate
- IPE testing ensures the reviewer's conclusions rest on reliable inputs
Organization-Level Controls
Broad governance mechanisms that set the tone and operating environment for the entire control framework.
Representative controls:
- Executive tone and ethical standards (code of conduct, leadership messaging)
- Enterprise risk assessment process
- Audit committee oversight of external and internal reporting
- Internal audit charter, scope, and activities
- Fraud risk assessment and anti-fraud programs
- Ethics hotline / whistleblower mechanism
- Management's ongoing monitoring of control health
- Financial reporting competency standards (hiring qualifications, continuing education)
- Period-end reporting procedures (close governance, GAAP compliance checkpoints)
Significance in evaluation:
- Organization-level controls can supplement but generally cannot substitute for process-level controls
- Failures in tone-at-the-top or audit-committee oversight are potent indicators of material weakness
- Robust organization-level controls may justify reduced sample sizes or narrower scope at the process level
1---
2name: audit-readiness
3description: Prepare audit workpapers, control tests, samples, evidence, deficiencies, and remediation tracking.
4metadata:
5 source: https://skillmd.com/skills/vm0-ai/audit-readiness
6---
7
8## SOX 404 Testing Lifecycle
9
10### End-to-End Phases
11
121. **Scoping:** Determine which accounts and processes carry enough risk to warrant control coverage
132. **Risk evaluation:** Assess the probability and magnitude of potential misstatement for each in-scope account
143. **Control mapping:** Document the specific controls that mitigate each identified risk
154. **Effectiveness testing:** Evaluate whether controls are properly engineered (design) and consistently executed (operation)
165. **Deficiency assessment:** Judge the severity of any control gaps uncovered during testing
176. **Management reporting:** Formalize the overall ICFR assessment and disclose any material weaknesses
18
19### Determining Which Accounts Are In Scope
20
21An account enters scope when it carries a non-remote probability of containing a misstatement that is material on its own or in combination with others.
22
23**Size-based indicators:**
24- The balance surpasses the quantitative materiality benchmark (commonly 3-5% of a reference figure such as revenue, assets, or pre-tax income)
25- High transaction throughput increases the statistical likelihood of error
26- The balance depends heavily on estimates or management judgment
27
28**Risk-based indicators:**
29- The accounting is inherently complex (multi-element revenue arrangements, derivative instruments, pension obligations)
30- The account is a common fraud target (cash, revenue, related-party activity)
31- Historical audit adjustments or prior restatements have affected the account
32- Significant management estimates or subjective assumptions underlie the balance
33- The account or process is new, or has undergone material change
34
35### Financial Statement Assertions by Account Category
36
37| Account Category | Primary Assertions to Address |
38|---|---|
39| Revenue | Occurrence, Completeness, Measurement, Period allocation |
40| Trade receivables | Existence, Valuation (reserve adequacy), Ownership rights |
41| Inventory | Existence, Valuation, Completeness |
42| Property & equipment | Existence, Valuation, Completeness, Ownership rights |
43| Trade payables | Completeness, Measurement, Existence |
44| Accrued obligations | Completeness, Valuation, Measurement |
45| Shareholders' equity | Completeness, Measurement, Presentation |
46| Close & reporting process | Presentation, Measurement, Completeness |
47
48### Design vs. Operating Effectiveness
49
50**Design effectiveness** asks: Is the control architected to intercept or surface a material misstatement in the targeted assertion?
51- Assessed via end-to-end walkthroughs (trace a representative transaction through the full process)
52- Confirm the control sits at the correct process juncture
53- Confirm the control directly addresses the specified risk
54- Re-evaluate at least annually, or whenever the process changes
55
56**Operating effectiveness** asks: Has the control actually functioned as intended across the entire period under review?
57- Assessed via inspection, observation, recalculation, or inquiry (with corroboration)
58- Requires sample sizes large enough to support a reliable conclusion
59- Must span the full reliance period (not just a single point in time)
60
61## Sampling Methodologies
62
63### Statistical Random Sampling
64
65**Applicability:** Standard approach for high-volume, transaction-level controls.
66
67**Steps:**
681. Define the universe: every transaction subject to the control during the test period
692. Assign a sequential identifier to each population item
703. Apply a random-number generator to draw the sample
714. Confirm every item had an equal selection probability (no systematic exclusion)
72
73**Strengths:** Statistically defensible, free of selection bias
74**Limitations:** May not capture high-risk outliers; requires a complete population listing
75
76### Risk-Directed (Judgmental) Sampling
77
78**Applicability:** Complements random sampling by targeting items with elevated risk characteristics; serves as the primary method for small or heterogeneous populations.
79
80**Targeting criteria:**
81- Transactions above a defined dollar threshold
82- Atypical or non-standard entries
83- Activity near the period boundary (cut-off exposure)
84- Related-party transactions
85- Manual overrides or exception-processed items
86- First-time vendors or customers
87
88**Strengths:** Focuses testing effort on highest-risk items
89**Limitations:** Not statistically representative; must document the selection rationale
90
91### Unstructured (Haphazard) Sampling
92
93**Applicability:** Situations where a numbered population is unavailable and items are relatively uniform.
94
95**Steps:**
961. Select items without a deliberate pattern
972. Distribute selections across the entire test period
983. Guard against unconscious tendencies (gravitating toward top-of-list, round figures, etc.)
99
100**Strengths:** Simple, requires no tooling
101**Limitations:** Not statistically valid; vulnerable to unintentional bias
102
103### Interval-Based (Systematic) Sampling
104
105**Applicability:** Sequential populations where uniform period coverage is desired.
106
107**Steps:**
1081. Compute the selection interval: total population count divided by target sample size
1092. Pick a random starting point within the first interval
1103. Select every Nth item from that starting point forward
111
112**Illustration:** 1,000-item population, 25-item sample -> interval of 40. Random start at item 12. Selections: 12, 52, 92, 132 ...
113
114**Strengths:** Guarantees even distribution across the population
115**Limitations:** Periodic patterns in the data could skew results
116
117### Sample Size Reference Table
118
119| Control Cadence | Approximate Population | Lower-Risk Sample | Moderate-Risk Sample | Higher-Risk Sample |
120|---|---|---|---|---|
121| Annual | 1 | 1 | 1 | 1 |
122| Quarterly | 4 | 2 | 2 | 3 |
123| Monthly | 12 | 2 | 3 | 4 |
124| Weekly | ~52 | 5 | 8 | 15 |
125| Daily | ~250 | 20 | 30 | 40 |
126| Per-transaction (under 250) | < 250 | 20 | 30 | 40 |
127| Per-transaction (250+) | 250+ | 25 | 40 | 60 |
128
129**Conditions that warrant larger samples:**
130- Elevated inherent risk in the account or process
131- The control is the only safeguard for a significant risk (no backup control)
132- A deficiency was noted in a prior testing cycle
133- The control is newly implemented and untested historically
134- External auditors plan to rely on management's testing results
135
136## Workpaper & Evidence Standards
137
138### Required Workpaper Sections
139
1401. **Control profile:**
141 - Unique control identifier
142 - Narrative description (who does what, how frequently)
143 - Classification (manual, automated, IT-dependent manual)
144 - Execution frequency
145 - Targeted risk and assertion
146
1472. **Test blueprint:**
148 - Stated objective of the test
149 - Detailed procedural steps
150 - Description of expected evidence when the control is working
151 - Sampling method and rationale for approach chosen
152
1533. **Execution record:**
154 - Population description and total count
155 - Sample items selected (method and specific identifiers)
156 - Item-by-item results (pass/fail with the specific evidence inspected)
157 - Full narrative for every exception observed
158
1594. **Overall conclusion:**
160 - Effectiveness rating (effective / deficiency / significant deficiency / material weakness)
161 - Reasoning supporting the conclusion
162 - Magnitude assessment for any exceptions
163 - Compensating controls evaluated, if relevant
164
1655. **Accountability:**
166 - Tester signature and date
167 - Reviewer signature and date
168
169### What Constitutes Adequate Evidence
170
171**Acceptable:**
172- System screenshots capturing enforced controls or configurations
173- Documents bearing a signature, initials, or electronic approval stamp
174- Email trails with an identifiable approver and a discernible date
175- Application audit logs recording the actor, action, and timestamp
176- Independent recalculations that reproduce the recorded result
177- Written observation notes specifying date, location, and observer
178
179**Not sufficient on its own:**
180- Oral statements without corroboration
181- Documents lacking a date
182- Evidence with no identifiable performer or approver
183- System-generated output missing date/time metadata
184- Notes reading "per conversation with [name]" absent supporting documentation
185
186### File Organization Convention
187
188```
189ICFR Testing/
190 [Fiscal Year]/
191 Scoping & Risk Assessment/
192 Revenue Process/
193 Control Matrix
194 Walkthrough Narrative
195 Individual Test Workpapers
196 Evidence Attachments
197 Purchase-to-Pay Process/
198 Payroll Process/
199 Financial Close Process/
200 Treasury Process/
201 Capital Assets Process/
202 IT General Controls/
203 Organization-Level Controls/
204 Aggregation & Conclusions/
205 Deficiency Evaluation Workpaper
206 Management ICFR Assessment
207```
208
209## Deficiency Severity Framework
210
211### Simple Deficiency
212
213A gap exists when a control's design or execution does not enable personnel to prevent or detect misstatements in the ordinary course of their responsibilities.
214
215**Evaluation dimensions:**
216- How likely is it that the gap could produce a misstatement?
217- How large could the resulting misstatement be?
218- Does a compensating control reduce the residual exposure?
219
220### Significant Deficiency
221
222A deficiency (or cluster of deficiencies) that falls short of material-weakness severity but is consequential enough to require governance-body attention.
223
224**Hallmarks:**
225- Could produce a misstatement that is more than trivial but less than material
226- Probability of material misstatement is above remote but below reasonably possible
227- Involves a key control where compensating measures do not fully offset the gap
228- Several individually minor gaps that, taken together, raise substantive concern
229
230### Material Weakness
231
232A deficiency (or cluster of deficiencies) creating a reasonable possibility that a material financial-statement misstatement will escape prevention or detection.
233
234**Strong indicators:**
235- Senior management fraud of any dollar magnitude
236- Restatement of previously filed financials to correct a material error
237- Auditor detection of a material misstatement that the entity's own controls missed
238- Breakdown in audit-committee oversight of the financial reporting process
239- Failure of a pervasive control (organization-level or IT general) with downstream impact across multiple cycles
240
241### Aggregation Analysis
242
243Individually minor gaps may be severe in combination:
244
2451. Collect all deficiencies affecting the same process or assertion
2462. Evaluate whether their combined effect could permit a material misstatement
2473. Consider whether a weakness in a compensating control amplifies other gaps
2484. Document the aggregation logic and the resulting severity classification
249
250### Remediation Protocol
251
252For every identified gap:
253
2541. **Root-cause diagnosis:** Determine why the control failed (design flaw, execution lapse, resource constraint, training gap, system limitation)
2552. **Corrective action plan:** Define specific steps to restore effectiveness (redesign, additional staffing, enhanced training, system configuration change, added review layer)
2563. **Target completion date:** Set a realistic but firm deadline
2574. **Accountable owner:** Assign a named individual responsible for execution
2585. **Validation procedure:** Specify how and when the remediated control will be re-tested to confirm it is operating effectively
259
260## Control Taxonomy
261
262### IT General Controls (ITGCs)
263
264Infrastructure-level controls ensuring that application controls and automated processes function reliably.
265
266**Logical access governance:**
267- New-user provisioning requires documented, pre-implementation approval
268- Terminated-user accounts are disabled within a defined SLA
269- Privileged/administrator access is restricted and subject to enhanced monitoring
270- Periodic recertification reviews validate that access remains appropriate
271- Password standards enforce complexity, rotation, and lockout thresholds
272- Conflicting duties are systematically prevented through role-based access design
273
274**Change governance:**
275- Every change request is documented and approved prior to deployment
276- Changes are validated in a non-production environment before promotion
277- Development and production environments are logically or physically separated
278- Emergency changes follow a defined expedited path with post-implementation sign-off
279- Post-deployment reviews confirm changes behave as intended
280
281**Operational continuity:**
282- Automated job scheduling is monitored with exception alerting
283- Backups execute on schedule and restore procedures are periodically tested
284- System uptime and performance are tracked against defined SLAs
285- Incident response and escalation procedures are documented and rehearsed
286- Disaster recovery plans are maintained and tested at defined intervals
287
288### Manual (Human-Performed) Controls
289
290Controls relying on individual judgment, typically involving review, approval, or verification activities.
291
292**Representative controls:**
293- Leadership review of financial results and operating metrics
294- Supervisory sign-off on journal entries exceeding a dollar threshold
295- Three-way matching of purchase order, goods receipt, and vendor invoice
296- Preparation and independent review of account reconciliations
297- Physical observation and counting of inventory
298- Authorization of vendor or customer master-data changes
299- Credit-limit approval for new or expanded customer relationships
300
301**Attributes to verify during testing:**
302- The control was performed by someone with proper authority
303- Execution occurred within the prescribed time window
304- Observable evidence of the review exists (signature, initials, system notation, email)
305- The reviewer had access to sufficient supporting information
306- Identified exceptions were investigated and appropriately resolved
307
308### Automated (System-Enforced) Controls
309
310Controls embedded in application logic that execute without human intervention.
311
312**Representative controls:**
313- Workflow engines that block progression without required approvals
314- Automated three-way match that withholds payment when PO, receipt, and invoice disagree
315- Duplicate-detection algorithms that flag or reject repeated invoice submissions
316- Credit-limit enforcement that prevents order entry beyond the approved threshold
317- System-calculated depreciation, amortization, interest, and tax computations
318- Role-based access configurations that prevent users from holding conflicting privileges
319- Field-level validations (mandatory fields, format masks, range constraints)
320- Automated transaction-matching within reconciliation modules
321
322**Testing approach:**
323- Confirm the system configuration enforces the control as specified (design test)
324- For unchanged configurations, a single successful test typically covers the period (operating effectiveness), provided change-management ITGCs are also effective
325- If the configuration was modified during the period, re-test post-change
326
327### IT-Dependent Manual Controls
328
329Manual review or approval activities that depend on the completeness and accuracy of system-produced data.
330
331**Representative controls:**
332- Management review of a system-generated exception or outlier report
333- Reserve estimation based on a system-generated aging analysis
334- Account reconciliation performed using system-extracted trial balance data
335- Transaction approvals triggered by system-generated workflow notifications
336
337**Testing approach:**
338- Test the human element (review quality, follow-up on exceptions, evidence of approval)
339- Separately validate the information produced by the entity (IPE) — confirm the underlying report or data extract is complete and accurate
340- IPE testing ensures the reviewer's conclusions rest on reliable inputs
341
342### Organization-Level Controls
343
344Broad governance mechanisms that set the tone and operating environment for the entire control framework.
345
346**Representative controls:**
347- Executive tone and ethical standards (code of conduct, leadership messaging)
348- Enterprise risk assessment process
349- Audit committee oversight of external and internal reporting
350- Internal audit charter, scope, and activities
351- Fraud risk assessment and anti-fraud programs
352- Ethics hotline / whistleblower mechanism
353- Management's ongoing monitoring of control health
354- Financial reporting competency standards (hiring qualifications, continuing education)
355- Period-end reporting procedures (close governance, GAAP compliance checkpoints)
356
357**Significance in evaluation:**
358- Organization-level controls can supplement but generally cannot substitute for process-level controls
359- Failures in tone-at-the-top or audit-committee oversight are potent indicators of material weakness
360- Robust organization-level controls may justify reduced sample sizes or narrower scope at the process level