Controls
Design internal controls for "$ARGUMENTS". Establish preventive and detective controls to safeguard assets, ensure accuracy, and maintain compliance.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"accounting-controls","workflow":"accounting","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}.
Compute with code. Perform every calculation (totals, balances, ratios, variances, projections) with a script — Bash, Python or a spreadsheet formula written to a file — and include the computation alongside the result. Never do arithmetic mentally.
Prerequisites
None — utility skill, run anytime. Most effective after Phase 1 (analyze) to understand the entity's operations and risk areas.
Process
Assess control environment:
- What processes handle cash, inventory, payroll, and financial reporting?
- Where are the highest-risk areas for errors or fraud?
- What controls currently exist (if any)?
- What is the entity's size and complexity?
Design preventive controls:
- Segregation of duties — separate authorization, custody, and recording
- Authorization controls — approval limits and signing authority
- Physical controls — locks, safes, restricted access, inventory counts
- IT controls — access permissions, password policies, audit logs
- Documentation — standardized forms, sequential numbering, required fields
Design detective controls:
- Reconciliations — bank reconciliation, intercompany, sub-ledger to GL
- Reviews — management review of reports, exception reports
- Audits — internal audit schedule, surprise counts
- Variance analysis — budget vs. actual monitoring
Map controls to risks:
- For each identified risk, assign one or more controls
- Classify controls by type (preventive/detective) and frequency (daily/weekly/monthly/annual)
- Identify any gaps where risks lack adequate controls
Write the artifact to .singularskills/accounting/<project>/controls.md with sections:
- Control Environment Assessment — current state and risk areas
- Control Matrix — risks mapped to controls with type, frequency, and owner
- Implementation Plan — priority order for implementing new or improved controls
- Monitoring — how to verify controls are operating effectively
Output
The controls design written to .singularskills/accounting/<project>/controls.md. Present a summary highlighting:
- Number of controls designed by type
- Highest-risk areas and their mitigating controls
- Implementation priorities
End the artifact with this paragraph, verbatim:
Not financial or tax advice. This artifact is generated analysis for review by a qualified accountant or financial professional before any filing, reporting or decision relies on it.
1---2name: accounting-controls3description: Design internal controls — segregation of duties, approvals, reconciliations, reviews — mapped to the entity's error and fraud risks in a control matrix with owners. Use when the user worries about errors or fraud in cash, payroll or reporting and wants controls to prevent or catch them. Not for assessing SOX, FINRA or SEC compliance; see /compliance-financial-compliance.4metadata:5 source: https://skillmd.com/skills/bromso/accounting-controls6 argument-hint: "[project] [--skip-checks]"7---89# Controls1011Design internal controls for "$ARGUMENTS". Establish preventive and detective controls to safeguard assets, ensure accuracy, and maintain compliance.1213**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"accounting-controls","workflow":"accounting","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}`.1415**Compute with code.** Perform every calculation (totals, balances, ratios, variances, projections) with a script — Bash, Python or a spreadsheet formula written to a file — and include the computation alongside the result. Never do arithmetic mentally.1617## Prerequisites1819None — utility skill, run anytime. Most effective after Phase 1 (analyze) to understand the entity's operations and risk areas.2021## Process22231. **Assess control environment:**24 - What processes handle cash, inventory, payroll, and financial reporting?25 - Where are the highest-risk areas for errors or fraud?26 - What controls currently exist (if any)?27 - What is the entity's size and complexity?28292. **Design preventive controls:**30 - **Segregation of duties** — separate authorization, custody, and recording31 - **Authorization controls** — approval limits and signing authority32 - **Physical controls** — locks, safes, restricted access, inventory counts33 - **IT controls** — access permissions, password policies, audit logs34 - **Documentation** — standardized forms, sequential numbering, required fields35363. **Design detective controls:**37 - **Reconciliations** — bank reconciliation, intercompany, sub-ledger to GL38 - **Reviews** — management review of reports, exception reports39 - **Audits** — internal audit schedule, surprise counts40 - **Variance analysis** — budget vs. actual monitoring41424. **Map controls to risks:**43 - For each identified risk, assign one or more controls44 - Classify controls by type (preventive/detective) and frequency (daily/weekly/monthly/annual)45 - Identify any gaps where risks lack adequate controls46475. **Write the artifact** to `.singularskills/accounting/<project>/controls.md` with sections:48 - **Control Environment Assessment** — current state and risk areas49 - **Control Matrix** — risks mapped to controls with type, frequency, and owner50 - **Implementation Plan** — priority order for implementing new or improved controls51 - **Monitoring** — how to verify controls are operating effectively5253## Output5455The controls design written to `.singularskills/accounting/<project>/controls.md`. Present a summary highlighting:56- Number of controls designed by type57- Highest-risk areas and their mitigating controls58- Implementation priorities5960End the artifact with this paragraph, verbatim:6162> **Not financial or tax advice.** This artifact is generated analysis for review by a qualified accountant or financial professional before any filing, reporting or decision relies on it.