A SOC 2 report does not expire. There is no AICPA rule that retires it after a set number of months, and there is no certificate with an expiry date on it. What ends is your customers' willingness to accept it — and that is a commercial threshold, not an accounting one.
The distinction that matters: the observation period is what the CPA firm tested. Commercial usability is how long buyers keep accepting the result. They are different lengths, and confusing them is how teams get caught mid-sales-cycle without current assurance.
Plain-English explainer · AT-C 205 examination · Last reviewed August 2026
A SOC 2 Type 2 report is a historical report covering one stated period — for example, 1 May 2026 to 31 July 2026. It says what the auditor tested and what they found during that window, and nothing about any date after it. That is why the question “when does it expire?” has no technical answer. The AICPA sets no expiry, and a SOC 2 is an attestation performed under AT-C 205, not a certification with a validity term. Anyone who tells you a SOC 2 “certificate” is “valid for one year” is describing a document that does not exist. What does exist is a well-established market convention about staleness — and that convention is what your sales cycle actually runs into.
Key Takeaways
- No AICPA rule makes a SOC 2 report expire. It reports on a stated period and says nothing about the time after it.
- There is no SOC 2 certificate and no expiry date — SOC 2 is an attestation, not a certification. Buyers asking for your "certificate expiry" are using ISO vocabulary for a different kind of engagement.
- In practice most enterprise buyers work on an annual refresh: comfortable to about six months past the period end, bridge-letter territory from six to twelve, and treated as lapsed beyond twelve.
- A short observation period ages faster. Three months of tested evidence read eight months later leaves the reader with three months of assurance and eight months of silence.
- The fix is continuous coverage, not a longer shelf life: start the next observation period the day after the last one ends, so consecutive reports abut instead of leaving a gap.
What people mean when they say “valid”
Almost every argument about SOC 2 validity is really a collision between three different dates printed in or around the same report.
Observation period
The window the CPA firm actually tested — say 1 May to 31 July 2026. This is the only period the opinion covers. A Type 1 has no observation period at all. It is a point-in-time view of control design.
Report date
The date the service auditor signed the opinion, usually a few weeks after the period closed. Useful for knowing how promptly the work was completed, but it does not extend the coverage.
Commercial usability
How long your customers keep accepting the report before asking for something newer. Set by their vendor-risk policy, not by the AICPA, and the only one of the three that behaves like an expiry date.
How buyers actually age a report
Measured from the end of the observation period — not from the report date, and not from when you sent it. This is market practice observed across enterprise vendor-risk reviews, not an AICPA requirement. Individual customers set their own thresholds and some are stricter.
| 0–3 months | Accepted without comment | The report is current by any reasonable standard. Procurement and security reviewers take it at face value and move to the substance — the opinion, the exceptions, and the CUECs assigned to them. |
| 3–6 months | Accepted, with a question | Still normal. Stricter reviewers begin asking whether the next examination is underway and when the period closes. Having a scheduled next period is usually the whole answer. |
| 6–12 months | Bridge letter territory | Enterprise vendor-risk teams commonly ask for a bridge letter confirming nothing material has changed since the period ended. Some will ask for interim evidence on specific controls. |
| 12+ months | Treated as lapsed | Most enterprise programmes operate on an annual refresh cycle. Past twelve months from the period end, expect the report to be treated as out of date regardless of what it says, and expect the request to become “send us the current one”. |
A 3-month report ages faster
Many organisations run a short first Type 2 — often three months — to get a report into sales conversations quickly. That is a reasonable trade, and the report is entirely legitimate. But the freshness ladder above is not the whole story for a short window, because a reader is weighing two things at once: how long ago the testing stopped, and how much testing there was.
“You have given us three months of tested operating effectiveness, and that tested period ended eight months ago.”
— the objection a short first Type 2 eventually meets
A twelve-month report read eight months later still shows a full year of operating evidence. A three-month report read at the same remove shows a quarter of testing followed by two-thirds of a year with no coverage at all. Both are “eight months old”, but they are not equally persuasive. This is why we advise clients not to describe a three-month Type 2 to customers as simply “valid for twelve months” — it invites a challenge the report cannot answer. Describe what it is: a completed examination of a stated period, with the next period already scheduled.
Closing the gap permanently
The durable answer to “how long is it valid” is to stop having a gap. Consecutive observation periods should abut: the next one begins the day after the last one ends, so every calendar month is eventually covered by some report.
| Report 1 | 1 May – 31 July 2026 | Short first Type 2 — gets assurance into the sales cycle quickly. |
| Report 2 | 1 Aug 2026 – 31 July 2027 | Twelve-month period starting the day after Report 1 closed. No uncovered month. |
| Report 3 | 1 Aug 2027 – 31 July 2028 | Annual cadence from here. Each report lands before the previous one goes stale. |
A six-month second period is also a common choice where the control set is still settling — it reaches a full annual rhythm one cycle later but keeps the evidence burden lighter. What matters is that the periods touch. See choosing your observation period for how to pick the length.
Frequently Asked Questions
Does a SOC 2 report expire?
Is a SOC 2 report valid for 12 months?
My observation period was only 3 months. How long is my report good for?
What is the difference between the observation period and the report validity?
Can a bridge letter extend how long my SOC 2 report is valid?
How soon should we start the next SOC 2 audit?
Does a SOC 2 Type 1 report have the same shelf life?
Related reading: SOC 2 bridge letters, choosing your observation period, Type 1 vs Type 2, how to read a SOC 2 report, opinions and exceptions, and the SOC 2 hub.
Related Reading
SOC 2 Bridge Letters
Management signs it, not the CPA. What it can credibly say, and what it cannot.
Read moreSOC 2 Observation Period: 3, 6 or 12 Months?
No AICPA minimum. Why short windows leave low-frequency controls untested.
Read moreType 1 vs Type 2
Which report to get first, and when to go straight to Type 2.
Read moreHow to Read a SOC 2 Report
All five sections annotated, an 8-step reviewer checklist, and the red flags.
Read moreSOC 2 Knowledge Hub
Every SOC 2 guide: Type 1 vs Type 2, criteria, timelines and audit prep.
Read moreSOC 2 Overview
The AICPA attestation US and global enterprise buyers ask for.
Read more