Controls & Audit
Abbreviation
SoD
Also known as
Separation of duties
Definition
Related terms
Key Control
A control relied upon to prevent or detect a material misstatement in a specific financial statement assertion. Key controls are tested every cycle; the design question for any automated process is which key controls it performs, replaces, or newly depends upon.
Delegation of Authority (DoA)
The formal policy defining who may approve what, at what value, under what conditions. The DoA is the source of the approval routing rules embedded in requisition and invoice workflows and is a primary SOX control artifact.
Ghost Vendor
A fabricated supplier record created to divert payments, usually by someone with vendor master write access. Detection relies on segregation of duties between master data maintenance and payment release, plus periodic review of low-activity and recently created records.
More in
Controls & Audit
Audit Trail
The complete, tamper-evident record of what happened to a transaction: who or what acted, when, on what input, under what rule, and what changed. For automated and agentic finance processes this is the load-bearing artifact — it is what makes the process auditable, and in outcome-based commercial models it is the contractual source of truth for attribution.
Control Deficiency
A control that does not allow management or employees to prevent or detect misstatements on a timely basis in the normal course of their duties. The base level of the severity taxonomy, below significant deficiency and material weakness.
Control Testing
Evaluating whether a control was designed appropriately and operated effectively over the period, using inquiry, observation, inspection, and re-performance against a selected sample. Automated controls are typically tested once plus general IT controls, which is why ITGC quality matters disproportionately.
COSO Framework
The reference framework for internal control, structured around control environment, risk assessment, control activities, information and communication, and monitoring. The framework against which most SOX programs are designed and evaluated.
Internal Control over Financial Reporting (ICFR)
The system of processes designed to provide reasonable assurance about the reliability of financial reporting. ICFR is the object of SOX 404 assessment and the framework within which any automated finance process must be designed, documented, and tested.
IT General Controls (ITGC)
Controls over access, change management, and operations of the systems supporting financial reporting. When an automated control is relied upon, its effectiveness rests entirely on the ITGCs around it — which makes ITGC deficiencies capable of invalidating a whole control set at once.
Low-risk start
Watch it run on your real documents and your own systems, before you commit to anything.