Skip to main content

Analysis

SOC 1 vs SOC 2: What Each Report Actually Covers

SOC 1 covers financial reporting; SOC 2 covers security. See how many vendors publish each, and why a SOC 1 certificate has nothing to verify.

Solomon AmosPublished 14 Nov 20269 min read

A procurement request lands in a vendor's inbox asking for 'the SOC 1 certificate.' The security team pauses, because there is no such document. SOC 1 and SOC 2 are both reports issued under the same American Institute of CPAs attestation standard, AT-C section 320, but they examine completely different things. SOC 1 looks at controls relevant to a user entity's financial statements. SOC 2 looks at controls relevant to security, availability, confidentiality, processing integrity and privacy. Buyers running vendor reviews regularly ask for the wrong one, or assume the two are interchangeable proof of 'being secure'. Neither is a certification, and only one of them is usually relevant to a software security review.

What a SOC 1 report actually tests

A SOC 1 report, formally a Report on Controls at a Service Organization Relevant to User Entities' Internal Control over Financial Reporting, exists because an auditor reviewing a company's financial statements needs assurance over any outsourced process that touches those numbers. If a vendor runs payroll calculations, processes transactions that flow into a client's general ledger, or manages a fund administration platform, its SOC 1 report tells the client's own financial auditor that the relevant controls were designed properly (Type I) or operated effectively over a period (Type II). The audience is narrow by design: a client's controller, finance team and external auditor. It is not written for a security reviewer and it says very little about encryption, access control or incident response unless those controls happen to bear on financial reporting.

You can see which vendors in the index have a stated SOC 1 report on /frameworks/soc-1. The list is short relative to SOC 2, and that gap is the whole point of this article.

What a SOC 2 report actually tests

SOC 2 reports examine controls against the AICPA's Trust Services Criteria: security is mandatory, and availability, confidentiality, processing integrity and privacy are added at the vendor's discretion depending on what it wants to demonstrate. This is the report buyers actually mean when they say they want proof a vendor takes security seriously. It covers access management, change control, vulnerability management, monitoring and incident response, the controls that matter for a SaaS vendor handling customer data. A Type I report confirms controls were designed suitably at a point in time. A Type II report confirms they operated effectively across a review period, usually six or twelve months, which is the version most buyers should actually ask for. The difference between the two types is covered in full in SOC 2 Type I vs Type II: what each one proves to a buyer, and how to read a SOC 2 report in 20 minutes walks through the sections that matter once you have the document in hand.

SOC 1SOC 2
Subject matterInternal control over financial reportingSecurity and related Trust Services Criteria
Mandatory criterionNone, scope is negotiated with the user auditorSecurity
Optional criteriaNot applicableAvailability, confidentiality, processing integrity, privacy
Typical use casePayroll, payments, fund administration, billing platformsAny SaaS vendor handling customer or employee data
Who reads itThe client's financial auditor and controllerSecurity, procurement and risk teams
TypesType I (design), Type II (operating effectiveness)Type I (design), Type II (operating effectiveness)
Public evidenceRestricted distribution, named parties onlyRestricted distribution, named parties only, but widely referenced on trust centres

Both reports are restricted-use documents under AICPA rules. Neither is published openly, but one is relevant to far more buyers.

Side by side diagram showing SOC 1 scoped to financial reporting controls and SOC 2 scoped to the five Trust Services Criteria
SOC 1 and SOC 2 share an audit standard but examine different subject matter.

How many vendors actually publish each

The gap between the two reports shows up clearly once you look across a large set of vendor pages rather than one company at a time. SOC 2 is the default security attestation referenced on trust centres across the index. SOC 1 shows up almost exclusively among payroll processors, payment platforms and a handful of fintech infrastructure vendors where financial reporting genuinely touches their product.

SOC 2
the report most vendor trust centres reference as a stated security attestation
in the CertReports index on 2026-11-14
SOC 1
reported almost only by payroll, payments and fund administration vendors
in the CertReports index on 2026-11-14
0
SOC 1 certificates recorded anywhere in the index
SOC 1 is a restricted-use report issued to named user entities, not a certificate, so there is nothing for a registry to show
Where SOC 1 shows up versus SOC 2, by vendor category
  • General SaaS and platform vendors4%SOC 1 rarely applies unless billing or payroll logic sits inside the product
  • Payroll and HR platforms62%financial reporting controls are core to the product
  • Payment processors and fintech infrastructure58%transaction processing flows directly into client ledgers
  • Fund administration and trust services71%the clearest case for a SOC 1 engagement

Why a SOC 1 certificate request has nothing to verify against

Security reviewers sometimes ask for a vendor's 'SOC 1 certificate' when what they actually need is a SOC 2 report, or occasionally the reverse happens when a finance team asks a SaaS vendor for 'the SOC 2 certificate' to satisfy an auditor who really needed SOC 1. Both requests fail for the same reason the phrase "SOC 2 certified" fails: SOC reports are attestations issued to named parties by an independent CPA firm, not certificates issued by an accreditation body. There is no registry anyone can check, no serial number to validate, and no public database equivalent to the FedRAMP Marketplace or the Visa Global Registry of Service Providers. If a vendor cannot produce the report itself, or a bridge letter covering the gap since the last report period ended, there is no public evidence to fall back on. There is no such thing as 'SOC 2 certified' covers the SOC 2 side of this in detail, and the same logic applies even more strictly to SOC 1, because far fewer vendors have one to show at all.

This matters for scoping a request correctly. Asking a project management tool or a marketing analytics platform for a SOC 1 report is asking for a document that almost certainly does not exist, because the vendor has no financial reporting process embedded in its product. Asking a payroll vendor for only a SOC 2 report, meanwhile, misses the control area that actually matters to the client's auditor. Knowing which one applies to a given vendor category before the request goes out saves a round trip.

Paylocity is a useful illustration because it operates in the category where both reports genuinely apply: it processes payroll data that flows into client financial statements, and it also runs a SaaS platform that holds employee personal data. Its trust centre states both a SOC 1 Type II and a SOC 2 Type II report with the report type specified, which is the detail a buyer should look for rather than a bare mention of 'SOC compliance'. Look at whether the report type is named, whether a period is given, and whether both attestations are present rather than just one standing in for the other.

Paylocity logo

Paylocity · Trust report

Finance and accounting · Public evidence as of 16 Nov 2026

Framework overview

CertReports state for each framework with public evidence: 1 verified, 3 vendor-stated.

3Documents and agreements

Legal and review documents Paylocity publishes or offers, as of 30 Sep 2026.

1Security practices

Public statements from Paylocity, shown as statements, not attestations, as of 30 Sep 2026.

  • Penetration testing · report available
Paylocity states both a SOC 1 Type II and a SOC 2 Type II report, the pairing expected of a payroll platform. Every line is a dated public record from the Data Privacy Framework list and Paylocity's trust centre. A framework not shown means no public evidence was found, not that Paylocity lacks it.CertReports

What to ask for instead of a certificate

  1. 1

    Identify which report actually applies

    If the vendor's product touches financial reporting, payroll, billing or fund movement for your organisation, SOC 1 is relevant. If the review is about data security, access control and operational resilience, ask for SOC 2.

  2. 2

    Request the report, not a certificate

    Both SOC 1 and SOC 2 are restricted-use documents. Ask the vendor directly, through its trust centre, or under NDA. There is no public certificate number to quote back to them.

  3. 3

    Check the type and period

    A Type II report covering six to twelve months carries more weight than a Type I snapshot. Confirm the audit period end date and compare it against today's date.

  4. 4

    Ask for a bridge letter if the period has lapsed

    If the report period ended more than a few months ago, request a bridge letter covering the gap. What is a bridge letter, and how much should a buyer trust one? explains what that letter can and cannot promise.
  5. 5

    Read the exceptions section

    Both report types list any exceptions the auditor noted. A clean report with no exceptions is the baseline; qualified opinions or noted exceptions need follow-up questions, not automatic rejection.

Bar chart comparing the share of vendor categories that state a SOC 1 report against those that state a SOC 2 report
SOC 1 concentrates in payroll, payments and fund administration. SOC 2 is broad across general SaaS.

Type I, Type II, and the question buyers actually need answered

Both report families share the same Type I versus Type II split, and buyers conflate the two axes more often than you would expect. A vendor can hold a SOC 1 Type I and a SOC 2 Type II at the same time, or the reverse, and each pairing means something different about what has actually been tested and for how long. The reasoning behind why a Type II covering a full operating period is the stronger evidence for a security review carries over from SOC 2 to SOC 1 whenever financial reporting controls are in scope. Neither report, regardless of type, is something a vendor can be "certified" against, and neither appears in a public registry the way an ISO 27001 certificate or a FedRAMP authorisation does.

SOC 1 reports are specifically intended to meet the needs of entities that use service organizations and the CPAs that audit the user entities' financial statements.

If a vendor mentions SOC without naming the type

A trust centre line that just says 'SOC compliant' or lists 'SOC 1 and SOC 2' without report type or period is not giving you enough to work with. Ask which type, which criteria were in scope for SOC 2, and when the period ended. Do not accept the summary at face value until those details are confirmed.

Which one should you actually ask for

For most software security reviews, SOC 2 is the correct ask, and it is the report the index tracks against /frameworks/soc-2 for exactly that reason. SOC 1 only becomes relevant when the vendor's product sits inside your financial reporting chain, payroll processing, transaction settlement, fund administration, or billing systems that feed your general ledger. If you are unsure which applies, check what the vendor's product actually does before the request goes out, run it through the bulk vendor security check tool, and compare the vendor's stated reports against similar vendors using the compare tool. Neither report is a substitute for the other, and asking for the wrong one just delays the review by a cycle.

People also ask

What is soc 1?

SOC 1 is a Report on Controls at a Service Organization Relevant to User Entities' Internal Control over Financial Reporting. It is issued by an independent CPA firm under AICPA attestation standards and is read mainly by a client's financial auditor, not a security reviewer. It applies to vendors whose services touch payroll, payments, billing or other processes that feed a client's financial statements. It is not a certificate and is not published in any public registry.

What is soc 1 vs soc 2?

SOC 1 examines controls relevant to financial reporting, while SOC 2 examines controls against the Trust Services Criteria: security, and optionally availability, confidentiality, processing integrity and privacy. Both are restricted-use AICPA attestation reports and both come in Type I and Type II versions. A payroll or payments vendor may need both; a typical SaaS tool handling customer data usually only needs SOC 2.

Is soc 1 or soc 2 better?

Neither is 'better', they answer different questions. SOC 1 tells a client's financial auditor that financial reporting controls work. SOC 2 tells a security reviewer that data handling controls work. For a vendor security review, SOC 2 is almost always the relevant document; SOC 1 only matters if the vendor's service affects your financial statements.

Is soc 1 a certification?

No. SOC 1 is an attestation report produced by a CPA firm for named user entities and their auditors, not a certificate issued by an accreditation body. There is no public registry to check a SOC 1 report against, unlike FedRAMP's Marketplace or the Visa PCI registry. If someone asks a vendor for a 'SOC 1 certificate', the correct response is to provide the actual report, or explain that no SOC 1 engagement applies to the service in question.
SOC 1SOC 2financial reporting controlsvendor evidenceaudit reports
S

Solomon Amos · Founder, CertReports

Solomon builds CertReports, the public evidence index for vendor security reviews. PhD in machine learning and cybersecurity, two years embedded at HMRC digital programmes, founder of TapTax. He writes about what registries, trust centres and auditors actually publish, and how buyers can use it before the questionnaire goes out.

You might also like