What Is AICPA SOC 1? Report Types, Contents, and Users

An AICPA SOC 1 report is an independent CPA audit of a service organization’s internal controls over financial reporting, produced so that the organization’s clients — and their auditors — can trust the outsourced processes that feed their financial statements. It is governed by the Statement on Standards for Attestation Engagements (SSAE) No. 18, specifically AT-C Section 320.1AICPA & CIMA. AICPA SSAEs – Currently Effective If your company outsources payroll, loan servicing, claims management, or any function that touches numbers on a financial statement, the SOC 1 is the mechanism your external auditor uses to rely on those outsourced controls without testing them from scratch.

Who Needs a SOC 1 and Who Reads It

Any organization that processes, stores, or handles financial data on behalf of other companies is a candidate. Payroll processors, insurance claims administrators, loan servicers, accounting service providers, cloud-based accounts receivable platforms, banking service firms, and software providers that manage financial data all commonly issue SOC 1 reports. The common thread is work that feeds directly into a client’s financial statements.

Three parties are involved. The service organization provides the outsourced service and undergoes the audit. The service auditor is an independent CPA firm that examines the controls and issues an opinion. The user entity is the client company whose auditor needs assurance that those outsourced controls actually work. In practice, the user entity’s external auditor is the primary reader, because a good SOC 1 lets that auditor reduce the scope of their own testing during the annual financial statement audit.

Type 1 vs. Type 2 Reports

SOC 1 reports come in two varieties, and the distinction changes how much assurance the report actually provides.

A Type 1 report is a snapshot. The service auditor evaluates whether the system description fairly presents the organization’s system as of a single specified date, and whether the controls are suitably designed to achieve their stated objectives on that date.2AICPA & CIMA. U.S. Attestation Standards – AICPA (Clarified) AT-C Sections 100-320 A Type 1 confirms the control environment looks right on paper. It does not tell you whether those controls actually worked over time.

A Type 2 report covers a defined period rather than a single date. The auditor evaluates everything in a Type 1 and also tests whether the controls operated effectively throughout that period, with the tests performed and the results documented in the report.2AICPA & CIMA. U.S. Attestation Standards – AICPA (Clarified) AT-C Sections 100-320 Most Type 2 reports cover twelve months. The standard sets no required minimum length, but common industry guidance is that the report should overlap at least six months of the user entity’s fiscal year to give the user auditor enough coverage to rely on.

User entity auditors strongly prefer Type 2 reports. Evidence of operating effectiveness lets them reduce their own substantive testing of the outsourced function. Without a Type 2, they will likely need to test the outsourced transactions independently. Type 1 reports are typically used only during a service organization’s first audit cycle or when a client needs a report on short notice before committing to the longer Type 2 process.

How SOC 1 Differs from SOC 2

Both reports fall under SSAE 18, but they answer different questions. A SOC 1 focuses exclusively on controls relevant to user entities’ financial statements. The service organization and its auditor identify custom control objectives tied to financial reporting risks, and the auditor tests controls against those objectives.2AICPA & CIMA. U.S. Attestation Standards – AICPA (Clarified) AT-C Sections 100-320

A SOC 2 report, governed by AT-C Section 205, evaluates controls against the AICPA’s Trust Services Criteria: security (always required), plus optional categories of availability, processing integrity, confidentiality, and privacy. A SOC 2 fits when a service organization handles sensitive data but does not directly process financial transactions. A cloud hosting provider that stores customer data without calculating payroll figures, for example, would typically undergo a SOC 2 rather than a SOC 1. Some organizations need both.

What’s Inside a SOC 1 Report

The report is organized into four sections, each with a distinct role for the reader.

  • Section I, the service auditor’s opinion. The CPA firm’s formal opinion on whether the system description is fairly presented and whether the controls are suitably designed (Type 1) or suitably designed and operating effectively (Type 2). This is the first thing a user auditor reads.
  • Section II, management’s assertion. A written statement from the service organization’s management affirming that the system description is accurate and that the controls were designed and, for a Type 2, operated effectively throughout the period.
  • Section III, the description of the system. A detailed narrative of the services provided, how transactions are initiated, processed, and reported, the boundaries of the system, and the specific controls in place.
  • Section IV, control objectives, testing, and results (Type 2 only). Each control objective is listed alongside the controls designed to achieve it, the tests the auditor performed, and the results. Any control exceptions appear here.

AT-C Section 320 specifies what the system description must include: the types of services and classes of transactions processed, how transactions flow through the system, how the organization captures significant events beyond routine transactions, the process for preparing reports to user entities, any subservice organizations and the method used to address them, the control objectives and related controls, and complementary controls assumed to exist at user entities.2AICPA & CIMA. U.S. Attestation Standards – AICPA (Clarified) AT-C Sections 100-320

Control Objectives and What User Entities Must Do

The scope of a SOC 1 covers only controls that could affect user entities’ financial reporting, not general operational quality or unrelated regulatory compliance. Within that scope, the service organization identifies its control objectives: statements describing what its controls are designed to accomplish for financial reporting integrity. A payroll processor might state an objective like “payroll transactions are completely and accurately calculated and recorded.” Beneath each objective sit the specific control activities: the approvals, reconciliations, and system configurations that make the objective achievable.

Most SOC 1 reports also include IT general controls that underpin the business process controls: access management, change management, system operations, and governance. If the IT environment is compromised, the application-level controls do not save the report.

Here is where many user entities get tripped up. SOC 1 reports include Complementary User Entity Controls, or CUECs. These are controls the service organization assumes its clients have in place for its own controls to work as intended.2AICPA & CIMA. U.S. Attestation Standards – AICPA (Clarified) AT-C Sections 100-320 If a payroll provider calculates gross pay but relies on the client to approve new hire salary rates, that approval step is a CUEC. If you never implement that control at your own company, the service organization’s controls alone will not prevent a misstatement. Review the CUEC section carefully and confirm your organization is meeting those responsibilities. It is one of the most overlooked parts of the report.

Subservice Organizations: Carve-Out vs. Inclusive

Service organizations frequently rely on other vendors. A payroll processor might use a separate data center; a claims administrator might outsource check printing. These downstream vendors are subservice organizations, and how they are handled in the SOC 1 matters.3Public Company Accounting Oversight Board. AI 18 – Consideration of an Entity’s Use of a Service Organization

AT-C Section 320 provides two methods. Under the carve-out method, the service organization acknowledges the subservice organization in its system description but excludes the subservice organization’s controls from the examination’s scope. The service organization is still responsible for monitoring that vendor, typically by reviewing its SOC report or maintaining internal oversight. Under the inclusive method, the subservice organization’s controls are folded into the system description and examination, and the service auditor tests them as part of the engagement. This requires deeper coordination and more documentation.

The carve-out method is far more common because it is simpler. But if the carve-out method was used, your auditor may need to obtain the subservice organization’s own SOC report separately to get full coverage of the controls affecting your financial reporting.

Reading the Auditor’s Opinion

The service auditor’s opinion is the most consequential piece of the report. It tells the user auditor how much weight to give everything else.

  • Unqualified (clean) opinion. The controls were suitably designed and, for a Type 2, operating effectively in all material respects. This is what every service organization wants and what user auditors expect to see.
  • Qualified opinion. The controls were generally effective except for specific identified issues. The problem is limited in scope and does not pervade the environment. User auditors need to check whether the qualification touches controls relevant to their client.
  • Adverse opinion. The auditor found severe deficiencies that materially and pervasively affect the control environment. A user auditor cannot rely on the report and will likely need to perform extensive independent testing.
  • Disclaimer of opinion. The auditor was unable to obtain enough evidence to form any opinion, typically because access or scope was too limited.

Any opinion other than unqualified creates work for the user auditor. The practical impact depends on whether the failures touch the transactions you outsource. A qualification irrelevant to your outsourced function may have no effect on your audit. A qualification squarely within the payroll processing controls you depend on means your auditor needs a fallback plan.

Note that when the auditor finds a control that did not operate as designed, the exception is reported regardless of whether the service organization later fixed it. The report describes the environment as it existed during the audit period. A midperiod remediation appears in the report alongside the original failure.

Bridge Letters and Reporting Gaps

A common timing problem arises when the SOC 1 report period does not align with the user entity’s fiscal year. If a Type 2 covers January through September but your fiscal year ends December 31, three months have no auditor-tested coverage.

Service organizations address this with a bridge letter (sometimes called a gap letter): a written representation from management asserting that no material changes have occurred to the control environment since the SOC 1 report date. The service auditor does not sign or attest to the bridge letter and performs no testing for the gap period. It is management’s word, not an auditor’s assurance. User auditors accept bridge letters as supplementary evidence, but they carry less weight than tested controls. If the gap is long or the risk is high, your auditor may need to perform independent procedures to cover the uncovered period.

Who Can Receive the Report

A SOC 1 is a restricted-use document, unlike a SOC 3, which is designed for general distribution. The standard service auditor opinion limits distribution to three groups: the service organization itself, user entities that used the system during the period covered by the report, and the auditors of those user entities. Indirect user entities of the service organization’s subservice organizations may also be included when the relevant controls affect their financial reporting.

This restriction means a SOC 1 cannot be posted on a website, used in marketing, or handed to prospects without an existing service relationship during the audit period. Service organizations typically require a non-disclosure agreement before releasing the report. If you are evaluating a potential vendor and ask for their SOC 1, expect pushback or a summary rather than the full document until you are a customer.