skill
Audit Support
Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
About
# Audit Support
**Important**: This skill assists with SOX compliance workflows but does not provide audit or legal advice. All testing workpapers and assessments should be reviewed by qualified financial professionals. While "significance" and "materiality" are context-specific concepts that are ultimately assessed by auditors, this skill is intended to assist professionals in the creation and evaluation of effective internal controls and documentation for audits.
SOX 404 control testing methodology, sample selection approaches, testing documentation standards, control deficiency classification, and common control types.
## SOX 404 Control Testing Methodology
### Overview
SOX Section 404 requires management to assess the effectiveness of internal controls over financial reporting (ICFR). This involves:
1. **Scoping:** Identify significant accounts and relevant assertions 2. **Risk assessment:** Evaluate the risk of material misstatement for each significant account 3. **Control identification:** Document the controls that address each risk 4. **Testing:** Test the design and operating effectiveness of key controls 5. **Evaluation:** Assess whether any deficiencies exist and their severity 6. **Reporting:** Document the assessment and any material weaknesses
### Scoping Significant Accounts
An account is significant if there is more than a remote likelihood that it could contain a misstatement that is material (individually or in aggregate).
**Quantitative factors:** - Account balance exceeds materiality threshold (typically 3-5% of a key benchmark) - Transaction volume is high, increasing the risk of error - Account is subject to significant estimates or judgment
**Qualitative factors:** - Account involves complex accounting (revenue recognition, derivatives, pensions) - Account is susceptible to fraud (cash, revenue, related-party transactions) - Account has had prior misstatements or audit adjustments - Account involves significant management judgment or estimates - New account or significantly changed process
### Relevant Assertions by Account Type
| Account Type | Key Assertions | |-------------|---------------| | Revenue | Occurrence, Completeness, Accuracy, Cut-off | | Accounts Receivable | Existence, Valuation (allowance), Rights | | Inventory | Existence, Valuation, Completeness | | Fixed Assets | Existence, Valuation, Completeness, Rights | | Accounts Payable | Completeness, Accuracy, Existence | | Accrued Liabilities | Completeness, Valuation, Accuracy | | Equity | Completeness, Accuracy, Presentation | | Financial Close/Reporting | Presentation, Accuracy, Completeness |
### Design Effectiveness vs Operating Effectiveness
**Design effectiveness:** Is the control properly designed to prevent or detect a material misstatement in the relevant assertion? - Evaluated through walkthroughs (trace a transaction end-to-end through the process) - Confirm the control is placed at the right point in the process - Confirm the control addresses the identified risk - Performed at least annually, or when processes change
**Operating effectiveness:** Did the control actually operate as designed throughout the testing period? - Evaluated through testing (inspection, observation, re-performance, inquiry) - Requires sufficient sample sizes to support a conclusion - Must cover the full period of reliance
## Sample Selection Approaches
### Random Selection
**When to use:** Default method for transaction-level controls with large populations.
**Method:** 1. Define the population (all transactions subject to the control during the period) 2. Number each item in the population sequentially 3. Use a random number generator to select sample items 4. Ensure no bias in selection (all items have equal probability)
**Advantages:** Statistically valid, defensible, no selection bias **Disadvantages:** May miss high-risk items, requires complete population listing
### Targeted (Judgmental) Selection
**When to use:** Supplement to random selection for risk-based testing; primary method when population is small or highly varied.
**Method:** 1. Identify items with specific risk characteristics: - High dollar amount (above a defined threshold) - Unusual or non-standard transactions - Period-end transactions (cut-off risk) - Related-party transactions - Manual or override transactions - New vendor/customer transactions 2. Select items matching risk criteria 3. Document rationale for each targeted selection
**Advantages:** Focuses on highest-risk items, efficient use of testing effort **Disadvantages:** Not statistically representative, may over-represent certain risks
### Haphazard Selection
**When to use:** When random selection is impractical (no sequential population listing) and population is relatively homogeneous.
**Method:** 1. Select items without any specific pattern or bias 2. Ensure selections are spread across the full population period 3. Avoid unconscious bias (don't always p
Install
Run this command
git clone https://github.com/anthropics/knowledge-work-plugins && cp -r knowledge-work-plugins/finance/skills/audit-support ~/.claude/skills/Works with
Manual steps
Clone the repository and copy the `finance/skills/audit-support` folder into your Claude skills directory. Compatible with Claude Code, Cursor, Codex, and any Agent Skills-compatible agent.
Related assets
More curated picks in Finance & Accounting.
git clone https://github.com/anthropics/knowledge-work-plugins && cp -r knowledge-work-plugins/finance/skills/journal-entry-prep ~/.claude/skills/
git clone https://github.com/anthropics/knowledge-work-plugins && cp -r knowledge-work-plugins/finance/skills/variance-analysis ~/.claude/skills/
git clone https://github.com/anthropics/knowledge-work-plugins && cp -r knowledge-work-plugins/finance/skills/financial-statements ~/.claude/skills/
git clone https://github.com/anthropics/knowledge-work-plugins && cp -r knowledge-work-plugins/finance/skills/reconciliation ~/.claude/skills/
git clone https://github.com/anthropics/knowledge-work-plugins && cp -r knowledge-work-plugins/finance/skills/sox-testing ~/.claude/skills/
git clone https://github.com/anthropics/knowledge-work-plugins && cp -r knowledge-work-plugins/finance/skills/journal-entry ~/.claude/skills/
Audit before you install
Run any source through our checks - AI visibility, security, performance, and stack detection.
Automated Web Security Scan
security
PageSpeed Analyzer
performance
AI Content Quality Test
arabic content
AI Agent / MCP Server Tester
ai testing
Site Stack Detector
migration
AI SEO / AEO / GEO Audit
ai visibility
llms.txt Generator
ai visibility
Readability Score
arabic content
Schema / JSON-LD Builder
ai visibility
AI Cost Calculator
ai testing
Headline Analyzer
arabic content