What Is an SSAE 16 Report? SOC Types, Uses, and How to Read One

An SSAE 16 report was an independent auditor’s report on the internal controls at a service organization — a company that handles an outsourced business function such as payroll processing, data hosting, loan servicing, or claims administration. Statement on Standards for Attestation Engagements No. 16 governed these reports for audit periods ending on or after June 15, 2011, replacing the older SAS 70. It is no longer the governing standard. The AICPA replaced SSAE 16 with SSAE 18 in 2017 and revised the attestation framework again with SSAE 21 in 2022. The reports themselves are now called System and Organization Controls (SOC) reports, and if a vendor, auditor, or contract still asks for an “SSAE 16 report,” what they actually need today is a SOC 1 or SOC 2 issued under the current standard.

Why You Still Hear “SSAE 16” Years After It Was Retired

The lineage helps explain why the old label sticks. Statement on Auditing Standards No. 70, issued in 1992, first gave auditors a way to examine and report on the controls of outsourced service providers. Over time, organizations began using SAS 70 reports as a general-purpose marketing tool for their control environments, which the standard was never designed to support.

SSAE 16 succeeded SAS 70 for audit periods ending on or after June 15, 2011. It tightened accountability by requiring a formal written assertion from service organization management about the design and operating effectiveness of controls. Under SAS 70, management’s role had been less explicit, which left room for ambiguity about who was responsible for the accuracy of the system description.

SSAE 18 then took effect for periods ending on or after May 1, 2017. It harmonized the various types of attestation engagements under one framework, required service organizations to identify and monitor risks created by their own third-party vendors (subservice organizations), and formalized the SOC 1, SOC 2, and SOC 3 taxonomy that is used today.1AICPA & CIMA. AICPA Auditing Standards Board Approves Revisions to Attestation Standards

SSAE 21 took effect for reports dated on or after June 15, 2022. The revision refined examination engagement standards, particularly around assertion-based engagements. The SOC report types and Trust Services Criteria did not change, but any SOC report issued today falls under SSAE 21. References to “SSAE 16 reports” or “SSAE 18 reports” are historical labels for what the industry now simply calls SOC reports.

What the Report Covers: SOC 1, SOC 2, and SOC 3

The old SSAE 16 label covered what is now the SOC 1 report. SOC 2 and SOC 3 came later as the framework matured. Which one you need depends on why you are looking at the service organization in the first place.

SOC 1: Controls That Affect Financial Reporting

A SOC 1 report covers controls at a service organization that could affect a client’s financial statements. The scope is narrow by design: it evaluates only controls relevant to the user entity’s internal control over financial reporting.2AICPA & CIMA. SOC 1 – SOC for Service Organizations: ICFR If a service provider processes transactions that flow into your general ledger, a SOC 1 report is what your external auditor uses to decide how much reliance to place on that provider’s controls.

Common candidates for SOC 1 examinations include third-party payroll processors, loan servicing companies, medical claims administrators, and investment custodians. A control deficiency found in a SOC 1 can ripple into the user entity’s own audit, potentially triggering a material weakness finding in the client’s financial reporting controls. SOC 1 reports are restricted-use documents, limited to the service organization’s management, the user entities it serves, and those user entities’ auditors.

SOC 2: Security, Availability, Confidentiality, and More

A SOC 2 report evaluates controls that go beyond financial reporting. It uses the AICPA’s Trust Services Criteria, which organize controls into five categories: security, availability, processing integrity, confidentiality, and privacy.3AICPA & CIMA. SOC 2 – SOC for Service Organizations: Trust Services Criteria4AICPA & CIMA. 2017 Trust Services Criteria (With Revised Points of Focus – 2022)

Security is the foundation of every SOC 2 because the Common Criteria (logical access, system monitoring, risk management) map to that category and underpin the other four. A service organization then adds whichever additional categories apply to what it does. A cloud hosting company would almost certainly include Availability and Processing Integrity. A company handling sensitive personal data would add Confidentiality and Privacy.

SOC 2 has become the standard due diligence document in business-to-business technology transactions. When evaluating a SaaS vendor, a managed IT provider, or a data center, the SOC 2 report is where you find evidence that systems are protected against unauthorized access, that data is processed accurately, and that services can stay running. Like SOC 1, it is a restricted-use document, and recipients typically sign a non-disclosure agreement before gaining access.

SOC 3: The Public-Facing Version

A SOC 3 report covers the same Trust Services Criteria as a SOC 2 but strips out detailed control descriptions and test results. The AICPA describes it as a general-use report that can be freely distributed or posted on a company’s website.5AICPA & CIMA. SOC 3 – SOC for Service Organizations: Trust Services Criteria for General Use Report SOC 3 reports are only available as Type 2 assessments. They work for marketing and for prospects who want basic assurance without the full technical detail, but procurement and security teams doing real vendor due diligence still ask for the SOC 2.

Type 1 vs. Type 2

The SOC 1, 2, or 3 designation tells you what was examined. The Type 1 or Type 2 designation tells you how deeply and over what timeframe. Both SOC 1 and SOC 2 examinations can produce either type, and the difference in assurance is significant.

Type 1: A Point-in-Time Snapshot

A Type 1 report evaluates whether the controls are suitably designed as of a single specified date. The auditor reviews the system description and the control design, then offers an opinion on whether those controls, if operated as described, could achieve the stated objectives. There is no testing of whether controls actually worked. A Type 1 tells you the blueprint looks sound, not that the building stayed standing.

Organizations usually pursue a Type 1 during their first SOC examination, before they have the track record for a Type 2. Most user entities and their auditors treat it as a stepping stone.

Type 2: Operating Effectiveness Over a Period

A Type 2 report includes everything in a Type 1 and adds testing of whether controls actually functioned as intended over a defined review period, typically three to twelve months. A twelve-month window is generally considered the gold standard for recurring reports because it aligns with financial reporting cycles.

The auditor performs detailed testing throughout the observation window and documents the results, including any exceptions where a control did not operate as designed. An exception does not automatically make the report useless, but the user entity has to evaluate whether that failure creates a gap in its own risk environment. Financial statement auditors almost universally require a Type 2 report before they will place reliance on a service organization’s controls.

How to Read the Report You Receive

Whether the cover page says SSAE 16, SSAE 18, or SSAE 21, the sections you actually need to read are the same.

Start With the Auditor’s Opinion

The independent CPA firm — only a licensed CPA firm can issue a SOC report — states its conclusion about the system description and controls. Four opinions are possible:

  • Unqualified. Controls were fairly presented and, for Type 2 reports, operated effectively. This is what you want to see.
  • Qualified. The auditor found a specific issue that was not pervasive enough to undermine the entire report.
  • Adverse. Controls were not designed or operating effectively. A serious red flag.
  • Disclaimer. The auditor could not gather sufficient evidence to form any opinion at all.

For high-reliance services, an unqualified opinion is the baseline expectation. Anything else warrants a conversation with the service organization about what went wrong and what they are doing about it.

Read the System Description and Management Assertion

The system description outlines the services provided, the boundaries of the system, the control objectives or Trust Services Criteria in scope, and any complementary user entity controls. The management assertion is the service organization’s formal statement that the description is fairly presented and controls are suitably designed (and, for Type 2, operating effectively). That assertion, first required under SSAE 16, is what puts management’s name on the line rather than leaving accountability with the auditor.

Check the scope against what you actually buy from the vendor. A SOC report that examines the vendor’s hosting platform does you no good if the service you use is a separate product not covered in the description.

Work Through the Exceptions

In a Type 2 report, the tests of controls section is where the real detail lives. The auditor lists each control tested, the testing procedure, and the result. Exceptions are not unusual; what matters is their nature and severity. A single late access review in a twelve-month period is very different from a systematic failure to revoke terminated employees’ credentials. If an exception touches a control you depend on and you have no compensating control on your side, escalate it internally.

Do Not Skip the Complementary User Entity Controls

Complementary user entity controls (CUECs) are controls the service organization assumes you are operating on your end. A common example: the service organization performs nightly data backups, but the report specifies that the client is responsible for testing the restore process. Skip that testing and you have created a gap the report explicitly flagged as yours.

Check for Subservice Organizations

A subservice organization is a vendor the service organization itself relies on to deliver part of the service. A payroll company that uses a third-party tax filing service is using one. Under the more common carve-out method, the report describes what the subservice organization does but excludes its controls from testing, so you may need to obtain a separate SOC report from that vendor. Under the inclusive method, the subservice organization’s controls are tested inside the main report.

Covering the Gap Between Reports: Bridge Letters

SOC reports cover a defined period, and there is almost always a gap between when one report ends and the next is issued. If your SOC 2 covers January through December and the next report will not be ready until April, you have three months with no formal assurance. A bridge letter (sometimes called a gap letter) is a written statement from the service organization’s management confirming that controls continued to operate effectively during that gap. Bridge letters generally cover a period of up to three months. They do not carry the weight of a full SOC report because no independent auditor is testing controls, but they provide continuity for user entities that need to demonstrate ongoing vendor oversight. Build the request into your vendor management process rather than waiting for your own auditor to ask.

What to Ask a Vendor For Today

If a checklist, contract clause, or prospect is asking you for an “SSAE 16 report,” translate before you respond. Ask what the report will be used for. If the answer involves the user’s financial statement audit, the current equivalent is a SOC 1 Type 2. If the answer involves information security, vendor risk, or data protection due diligence, the current equivalent is a SOC 2 Type 2. If someone wants a document they can post publicly, that is a SOC 3. All of them are now issued under SSAE 21, and any reputable service organization will provide the correct current report on request under the appropriate confidentiality terms.