Working Money skill
Design a financial control
Design a proportionate preventive or detective control with clear evidence and ownership.
Procedure
- Define the risk statement, process boundary, population, frequency, materiality, and accountable owner.
- Identify the failure or misuse to prevent, detect, correct, or recover from.
- Select control type, timing, performer, reviewer, threshold, evidence, and escalation.
- Apply separation of duties and least privilege without creating an unworkable process.
- Define complete and accurate source data plus handling of missing, duplicate, late, and exceptional items.
- Walk through normal, boundary, failure, override, and absent-owner scenarios.
- Pilot the control and measure coverage, timeliness, false results, bypasses, and effort.
- Document operation, evidence retention, exception approval, testing, and review triggers.
Guardrails
- Do not call policy text a control unless it reliably changes or detects action.
- Never let the same person initiate, approve, execute, and conceal a consequential transaction.
- Use qualified finance, audit, legal, and system owners for specialist conclusions.
--- name: design-a-financial-control category: money description: Design a proportionate preventive or detective control with clear evidence and ownership. Use when a financial risk needs a reliable check rather than an informal reminder. --- # design-a-financial-control ## Procedure 1. Define the risk statement, process boundary, population, frequency, materiality, and accountable owner. 2. Identify the failure or misuse to prevent, detect, correct, or recover from. 3. Select control type, timing, performer, reviewer, threshold, evidence, and escalation. 4. Apply separation of duties and least privilege without creating an unworkable process. 5. Define complete and accurate source data plus handling of missing, duplicate, late, and exceptional items. 6. Walk through normal, boundary, failure, override, and absent-owner scenarios. 7. Pilot the control and measure coverage, timeliness, false results, bypasses, and effort. 8. Document operation, evidence retention, exception approval, testing, and review triggers. ## Guardrails - Do not call policy text a control unless it reliably changes or detects action. - Never let the same person initiate, approve, execute, and conceal a consequential transaction. - Use qualified finance, audit, legal, and system owners for specialist conclusions. ## Done - A control design links risk, population, action, owner, threshold, evidence, and escalation - Walkthrough and pilot records demonstrate normal, failure, override, and exception behavior - Operating ownership, testing cadence, and remediation actions are approved