Scoping decides the workload
Over-scoping costs more than it protects. A risk and control matrix with 400 controls is harder to run and test than one with 80 well-chosen key controls, and auditors do not reward volume. We scope from materiality and risk, then ask of every proposed control: if this failed, could a material misstatement go undetected? If the answer is no, it is not a key control, and it does not belong in the matrix as one.
Entity-level controls carry weight
The COSO framework, and the auditors who apply it, start with the control environment: board oversight, the code of conduct, the whistleblower channel, the fraud risk assessment and how management monitors its own controls. At a private company these are often the least documented. We build them early, because they are hard to evidence after the fact. If no fraud risk assessment exists, our fraud risk assessment addresses COSO principle 8, which asks the company to consider the potential for fraud when it assesses risk.
IT general controls need early attention
Automated controls and system reports are only reliable if access to the system is restricted and changes to it are controlled. At a company that grew on NetSuite or Sage Intacct with three administrators and no change log, IT general controls are the slowest fixes, so we document them in the first weeks. Where access needs a deeper redesign, the segregation of duties project handles it alongside readiness.
Spreadsheets behind entries need controls
A revenue waterfall, a commission calculation or a reserve model is a control in its own right when a journal entry depends on it. We list each one, record who can change it, and add a review step that checks inputs and formulas, not only the total. A locked, versioned file with a named reviewer and a dated sign-off is usually enough at this stage.
Close automation belongs in scope
If an AI tool drafts reconciliations or codes invoices, the control that reviews its output becomes the key control, and the tool's access belongs in IT general control scope. COSO's 2026 guidance on internal control over generative AI is a useful reference for documenting both. The internal controls checklist for growing companies is a quick way to see which basics are already in place before scoping begins.
