A SOC 1 report is for service organizations whose work affects a customer’s financial statements, such as payroll, billing, claims or fulfillment. Customers’ auditors rely on it.
Why customers ask for a SOC 1
When a company outsources a process that feeds its financial reporting, its auditors need comfort that your controls work. Without a SOC 1 report, each customer’s auditor may ask to test your controls directly, which means repeated requests, extra fees and disruption on both sides. One independent report from your CPA replaces all of that and is often a requirement for winning and keeping customers, especially those subject to Sarbanes-Oxley (SOX) requirements.
Report types
- Type 1: design of controls at a point in time
- Type 2: design and operating effectiveness over a period
A Type 1 report is a practical first step when a customer needs something quickly. Most customers and their auditors ultimately want a Type 2, because it shows your controls operating consistently over time, typically across a period of several months to a year.
Who needs a SOC 1
- Payroll and benefits administrators
- Billing, collections and payment processors
- Claims, loan and policy administrators
- Printing, mail and statement fulfillment providers
- Managed service and IT outsourcing providers that host or run financial applications
- Any outsourced service where errors could flow into a customer’s financial statements
What a SOC 1 report includes
- The auditor’s opinion on whether the control objectives were met
- Management’s assertion about the fairness of the system description and the design and operation of controls
- A description of your system, covering the services, processes, people, systems and data relevant to your customers’ financial reporting
- Control objectives and controls, along with, for a Type 2, the tests performed and the results
Unlike a SOC 2, which is measured against the Trust Services Criteria, a SOC 1 is built around control objectives that you define based on the services you provide and what your customers need. That makes scoping the most important early decision.
What customers and their auditors look for
- Scope. Does the report cover the specific services the customer uses?
- Report period. Does it cover the customer’s fiscal year, or enough of it to rely on?
- The opinion and any exceptions. Exceptions are reviewed for significance and how management responded.
- Subservice organizations. If you rely on a data center or another vendor, the report should state whether their controls are included or carved out.
- Complementary user entity controls. These are controls the customer is expected to perform on their side.
Reports are restricted-use
A SOC 1 report is intended for your management, your customers and your customers’ financial statement auditors. It is not meant for general distribution. If you also need something you can share publicly, a SOC 3 is available for security-related criteria.
SOC 1 or SOC 2?
The two answer different questions. A SOC 1 addresses controls relevant to your customers’ financial reporting. A SOC 2 addresses security and related criteria, such as availability and confidentiality. Many service organizations, including those that process financial data and also host customer information, end up needing both. We can help you decide, and can coordinate the two examinations to reduce duplicated work.
How we work
- Fixed scope and schedule agreed up front
- One point of contact through fieldwork
- Plain-language findings and a clear path to a clean report
If this is your first examination, a SOC readiness assessment helps identify gaps in controls and documentation before the auditor begins. Book a meeting and we will talk through your services, your customers’ requirements and the right timeline.
