Beyond Compliance: Turning SOX Insights Into Better Ways of Working

Auditing | November 19, 2026

Beyond Compliance: Turning SOX Insights Into Better Ways of Working

Recurring control deficiencies should be treated not merely as compliance issues to document and remediate, but as an opportunity to strengthen the broader risk and control environment.

Brad Niedzielski, Will Gullette

More than two decades after the passage of the Sarbanes-Oxley Act (SOX), many organizations continue to identify the same control deficiencies year after year. The problem is more common in organizations that have not modernized their SOX programs and are operating outdated controls that no longer address key risks or keep pace with industry standards and technology. Recurring deficiencies can be a valuable signal: they suggest the issue extends beyond an isolated control failure and may point to a need for broader organizational change.

Recurring deficiencies should be treated not merely as compliance issues to document and remediate, but as an opportunity to strengthen the broader risk and control environment.

The control failure may be one visible symptom, but the underlying cause often lies in broader weaknesses in accountability and governance, talent, processes, or technology. The goal is not simply to close findings, but to improve how the organization operates.

Address the root cause, not just the control failure

A control can fail because it was poorly designed, but it may also break down if the owners and operators lack capacity or the appropriate skillset; the process relies heavily on manual work; or the underlying technology is unreliable and/or not configured correctly.

These causes matter. Rewriting a control usually won’t solve a staffing problem. Organizations will likely need to distinguish between the control that failed and what caused it to fail. If there is no central governance or compliance team in the company to establish the gold standards for how controls should be designed and operated, then first line control owners are often left to fend for themselves—contributing to lack of controls consistency across the organization, or worse, the risk that controls don’t appropriately address the risk.

That distinction is important. If management addresses only the documented failure, the remediation may appear complete while the conditions that created the deficiency remain unchanged.

The result is often a familiar cycle: remediation, retesting, recurrence, and renewed management attention—all of which usually increases the cost of compliance and diverts important resources from strategic business objectives. The appearance of progress is often muddled with manual workarounds and backstop processes that tend to burden the business or technology.

A proper risk assessment and root cause analysis can lay the groundwork for progress

Risk assessments too often become periodic compliance exercises and can often become viewed as an annual roll-forward event, rather than a dynamic, continuous process.

Mature remediation often starts with two disciplines working together. A risk assessment can show where to focus. A root cause analysis can show what to fix. Without both, organizations tend to remediate symptoms, not causes.

A useful risk assessment should show:

  • Where the risk of material misstatement is highest;
  • What has changed since the prior assessment;
  • Where fraud and management override risk sits; and
  • Where management attention and investment are most needed.

Root cause analysis asks why a deficiency occurred, not just what failed. It connects findings that appear unrelated. Repeated access issues, reconciliation discrepancies, and report inaccuracies may all trace back to a single source: controls were not prioritized during a system implementation. Fixing each one separately can address three symptoms. Fixing the root cause can address all three while reducing the likelihood of future recurrence.

When organizations identify connections, they can address systemic weaknesses instead of treating every deficiency as a standalone event.

Ownership requires more than assigning a name

Clear ownership means more than attaching someone’s name to a control. The person responsible needs to understand why it matters, have the time and authority to operate it effectively, and know when—and how—to escalate a problem. Accountability for controls should extend beyond individual control owners and be reinforced at every level of leadership. Senior leaders set the tone and build a culture where controls are embedded in how the organization operates.

This is especially important during seasons of business transformation, such as leadership changes or system implementations. During these periods, handoffs may be weakened and controls can continue to exist on paper even after the operating model has changed.

Training and awareness can contribute to sustainable remediation. In a Deloitte survey, 81% of respondents identified training and awareness as an effective remediation strategy, compared with 30% who cited revised procedures and documentation.

The contrast suggests that lasting improvement usually depends less on rewriting instructions and more on confirming that people understand how controls work in practice—and have the appropriate support from their leadership to make SOX a priority. Effective training should explain not only what must be done, but also why the control matters, what evidence is required, what exceptions look like, and when escalation is necessary.

Technology matters, but people make the difference

Manual processes tend to make it easier for issues to remain hidden until testing begins. New technologies that allow for continuous monitoring and centralized remediation tracking can help organizations identify problems sooner and understand where deficiencies are accumulating.

But technology is not a substitute for clear accountability. Automating a poorly understood process can simply allow the organization to repeat the same mistake more efficiently.

Technology works when:

  • Controls are purpose-built and implemented during a system’s design phase.
  • Theres is clearly defined ownership, including division of responsibilities between the business and IT.
  • Reliable reporting and transparent audit trails that support audit-readiness.

Strong technology investments are grounded in process clarity. Before automating a control, organizations should understand its objective, identify the decisions that require human judgment, and confirm that the underlying data and system dependencies are reliable.

Making remediation last

The goal isn’t simply to close a deficiency, it’s to understand why it happened and address the conditions that allowed it. That typically means stepping back from an individual control and examining how people, processes, and technology work together.

When organizations treat recurring findings as signals of broader governance issues, not isolated compliance failures, they can strengthen oversight, improve processes across the business, and reduce the likelihood of the same problems recurring. Effective remediation doesn’t just satisfy the auditors; it can help improve how the organization operates.

ABOUT THE AUTHORS:

Brad Niedzielski is an audit and assurance partner at Deloitte.

Will Gullette is a senior manager at Deloitte.

Disclaimer: This document contains general information only and Deloitte is not, by means of this document, rendering accounting, business, financial, investment, legal, tax, or other professional advice or services. This document is not a substitute for such professional advice or services, nor should it be used as a basis for any decision or action that may affect your business. Before making any decision or taking any action that may affect your business, you should consult a qualified professional advisor.

Deloitte shall not be responsible for any loss sustained by any person who relies on this document.

As used in this document, “Deloitte” means Deloitte & Touche LLP, a subsidiary of Deloitte LLP. Please see www.deloitte.com/us/about for a detailed description of our legal structure. Certain services may not be available to attest clients under the rules and regulations of public accounting.

Copyright © 2026 Deloitte Development LLC. All rights reserved.

Sign in to get access to this free resource, and all of our whitepapers and reports.

Download this content today!

Register to get free access to this content, as well as newsletters, continuing education, podcasts, and more…
MindBridge Launches New MCP Capability

Technology November 9, 2026 

MindBridge Launches New MCP Capability

MindBridge MCP is a new capability that connects the platform's AI-powered financial intelligence directly to supported AI assistants, including Claude, Microsoft Copilot, and Cursor.

Leave a Reply