Back to Skills

sox-testing

Generate SOX sample selections, testing workpapers, and control assessments. Use when planning quarterly or annual SOX 404 testing, pulling a sample for a control (revenue, P2P, ITGC, close), building a testing workpaper template, or evaluating and classifying a control deficiency.

22,462stars2,638forksUpdated 7/8/2026

Security Assessment

Safe(100/100)
Security Score100/100

About sox-testing

Assists with SOX 404 testing of internal controls over financial reporting by generating sample selections, testing workpapers, and control-deficiency assessments. It is invoked with a control area and a testing period and is aimed at quarterly or annual testing cycles. Supported control areas include revenue recognition, procure-to-pay, payroll, financial close, treasury, fixed assets, inventory, ITGC, entity-level, and journal entries, as well as any specific control ID. An explicit disclaimer states it does not provide audit or legal advice and that all workpapers and assessments should be reviewed by qualified financial professionals before use.

The workflow first identifies the key controls for the area and presents a control matrix capturing control type (automated, manual, or IT-dependent manual), frequency, key or non-key status, risk, and the relevant CEAVOP assertions (Completeness, Existence/Occurrence, Accuracy, Valuation, Obligations/Rights, and Presentation/Disclosure). It then determines sample size from control frequency, scaling from a single instance for annual controls up to 25 to 60 for per-transaction controls, adjusted for risk level, prior-year results, and external-auditor reliance.

Samples are drawn using random, systematic, or targeted selection and presented with dates, references, amounts, and selection basis. A structured testing workpaper template is generated with the test objective, procedures, expected evidence, a results grid, an exceptions log, and a conclusion that classifies the control as effective, effective with exceptions, a deficiency, a significant deficiency, or a material weakness. Pre-built test-step templates are provided per control area, covering activities such as approval authorization, three-way match, and reconciliation review.

FAQ

Which control areas can it test?

Revenue recognition, procure-to-pay, payroll, financial close, treasury, fixed assets, inventory, ITGC, entity-level, and journal entries, plus any specific control ID or name you supply.

How are sample sizes determined?

By control frequency, ranging from a single instance for annual controls up to roughly 25 to 60 items for per-transaction controls, then adjusted for risk level, prior-year deficiencies, and external-auditor reliance.

What are the CEAVOP assertions?

Completeness, Existence/Occurrence, Accuracy, Valuation, Obligations/Rights, and Presentation/Disclosure. The control matrix maps each control to its relevant assertions.

How does it classify the outcome of a control test?

As effective, effective with exceptions, a deficiency, a significant deficiency, or a material weakness, based on whether and how severely the control failed to operate.

Does it replace professional audit judgment?

No. It assists with SOX workflows but explicitly does not provide audit or legal advice, and all workpapers should be reviewed by qualified financial professionals before use in audit documentation.

Install sox-testing

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill