Implementing a SOX 404 program

Sarbanes-Oxley (SOX) compliance can be a heavy burden that falls on the shoulders of many stakeholders, departments, processes, and systems. By creating a properly structured SOX 404 program, the right controls and process changes can be far more automated when it comes time to roll-up the reports. In this article, we discuss how to implement a SOX 404 program using the Projects, Frameworks, and Reports apps.

This article illustrates how to manage a SOX compliance program using COSO® Internal Control Framework 2013, an integrated framework that enables organizations to effectively and efficiently develop systems of internal control.

However, the same workflow can also be applied to other frameworks that support SOX compliance requirements, such as:

  • the COBIT® 5 Framework
  • security frameworks published by the Information Technology Governance Institute (ITGI)
  • auditing standards developed by the Public Company Accounting Oversight Board (PCAOB)
  • regulations applying to government or higher-education, including OMB Circular A-123, Uniform Grant Guidance, or GreenBook

What is SOX compliance?

In 2002, the SOX Act legislation ushered in a renewed focus on corporate compliance by requiring that organizations provide quarterly and annual reports certifying the accuracy of their financial statements. The SOX Act was designed to increase transparency in financial reporting and standardize a system of internal checks and balances.

SOX Section 404 requires organizations to have an external audit performed to assess and report on the effectiveness of internal controls.

Where do I implement a SOX 404 program?

You can implement a SOX 404 program using the Projects and Reports apps.

The big picture

  • Frameworks are used to centrally capture the master relationship between requirements and controls, manage changes in an evolving regulatory and business environment, and build individual projects.
  • Projects are used to test the design and operational effectiveness of the control, and capture issues. If you created the control in a framework, you can sync changes back up to that framework from a project for use in other projects as well.
  • Report templates can be copied and modified to easily generate reports based on data from the Diligent One apps, and reports can be broadcasted to recipients on a recurring schedule.

Within a framework, you can track assurance and testing results associated with operational risks and controls in multiple projects to develop a dashboard of risk and project outcomes. As you test controls, Projects automatically aggregates testing results from the projects associated with the framework, and calculates assurance in real-time. At any point, you can generate reports to send to the appropriate recipients.

Steps

Ready for a tour?

Let's take a closer look at these features in the context.

1. Set up the program

The first step is understanding the best method to set up data in the system so that you can report out appropriately.

You can create frameworks to manage a structured set of information and use frameworks to build multiple projects. You can also customize the terms and labels in the projects according to your organization's standards. Tagging structures can also be set up to map objectives, risks, and controls to relevant contextual data points (assets, owners, entities, etc.) and enable risk and control reporting on those dimensions.

Tip

The Projects app offers several risk and control libraries (project templates) that contain pre-populated content for specific workflows, such as SOX compliance. There are two project templates that align with SOX 404 requirements and are typically used to jumpstart SOX compliance projects and create re-usable templates:

  • Sarbanes-Oxley (SOX) Audit Template (COSO 2013 Framework)
  • IT General Controls Review (SOX Content)

Configure project terminology

Terminology can vary widely between different types of projects, and also between organizations performing the same types of projects. Organizations can configure different project types so that the terminology used by each team is reflected in the relevant projects.

Set up projects and frameworks

Frameworks are helpful for reducing manual efforts involved in setting up projects, and can be used to centrally manage information in evolving regulatory and business environments. A common practice for many organizations is to segment SOX 404 requirements by process and sub-process in their projects and frameworks.

Model your organizational entity structure

Organizations are comprised of different business units, departments, locations, regions, and legal entities – all of which have controls that impact financial statement reporting. You can model your business and legal entity structure in your SOX management process to enable reporting on testing status and issue management to executives.

2. Document objectives, risks, and controls

Using frameworks as a centralized repository of information, you can work with process and control owners to draft process narratives, capture risk and control attributes in different attestation projects, and request further documentation, as required. Specific user roles can be leveraged to prescribe the right access and the right responsibility to process and control owners.

Plan projects

Every project begins with a planning phase. Planning a project involves preparing and consolidating planning information in a project, including the project background, purpose, scope, and relevant planning files. Planning files can include a variety of different documents, such as scoping information, engagement letters, SOX sampling methodology documentation, and even details about project team structures.

Document narratives

Narratives are a framework for understanding how your organization's internal controls fit into a business process. Many organizations rely on flowcharts as a primary method to visualize and show the detailed workflow within a given area. Any audio or visual content can be attached to support narrative documentation, and you can associate controls for referencing purposes.

Define risks and controls

Defining risks and controls results in the production of a risk control matrix (RCM). A RCM is a combination of identified risks and corresponding controls (the measures or courses of action for how the risk will be mitigated).

Tip

Once risks and controls are defined, process owners can set up a schedule in Projects to assure that control activities are being performed consistently.

Manage requests

You can request documentation from business owners and stakeholders and store relevant discussions in Projects. You can also send recurring reminders to people that are responsible for fulfilling requests, and consolidate multiple requests into a single email.

3. Evaluate control design and effectiveness

Many SOX compliance functions look to the business to take on some of the responsibilities of evaluating control design and effectiveness. Simple tasks, such as updating a control walkthrough and documenting control effectiveness test steps, are accessible by the owners themselves. This allows for the assessment of those controls to be truly owned by the business. Evaluating control design and effectiveness allows you to benchmark how well your organization is doing in managing compliance risk and requirements.

Tip

Inspirations, a catalog of risk scenarios and tests collected from Diligent initiatives worldwide, offers a series of analytic testing ideas by process that cover all financial operations. For more information, see Tools & Templates.

Evaluate control design

You can perform a walkthrough to evaluate the design of the control. Control owners can also help to evaluate the design of a control through attestation and / or attachment of evidence, define action plans to implement missing controls to address instances of non-compliance, or explain why a control is not necessary.

Tip

Frontline staff in an organization can use the Mission Control app to manage the controls they have access to, outside of the Projects app. Mission Control is an app that presents control information from Projects in a simplified and centralized view.

Define test plans

Test plans identify how you will test the control. You can define test plans to specify the testing method, the total sample size (split amongst testing rounds), and test steps that need to be performed to test the control.

Evaluate control effectiveness

Evaluating control effectiveness involves documenting detailed testing results, and specifying whether or not the control passed or failed. Once you have finished evaluating the effectiveness of the control, you can markup portions of text and link to evidence, such as policy or procedure manuals, regulations, SLAs/SLSs, and contracts.

Tip

To avoid manual scoring of control effectiveness, you can use Assessment Drivers to automate different control assessments. You can link a metric created in the Results app to a control assessment in Projects in order to inform the assessment, and auto-populate inherent risk scores based on pre-defined metric ranges.

Capture deficiencies and actions

You can capture and assign flagged deficiencies for remediation throughout the compliance review process, and delegate deficiencies to control or issue owners to update the status and related action plans. You can also assign actions to any stakeholder for easy tracking, evidence capture, and resolution.

4. Report on internal controls

Reporting on internal controls is important to the executive branch of the business and often results in critical demand from Controllers, VPs, and even the CFO. At any time during the project cycle, you can generate reports to provide information to executives and the board for regulatory reporting purposes. You can also broadcast custom reports on a scheduled basis to track remediation and lagging indicators.

Tip

There is a variety of default one-click reports available to download in the Projects app that evolve automatically as the project progresses. For example, the Test Plan report can be downloaded to determine whether a project is supported by valid sampling methodology, identify heavy manual testing, and create efficiency gain opportunities. For more customized reporting options, organizations can use the Reports app.

What's next? 

Learn how to automate a SOX 302 certification program

The Projects and Results apps can be used to efficiently conduct self-assessments, deploy 302 certification requests, and ensure fair distribution of responsibility across internal control stakeholders.

To find out more, see Automating a SOX 302 certification program.