AT-C section 320 is the part of the AICPA's clarified attestation standards under which every SOC 1 examination is performed. It defines what management's description of the system must contain, how control objectives are specified, and what the service auditor's opinion covers.
Full title: “Reporting on an Examination of Controls at a Service Organization Relevant to User Entities’ Internal Control Over Financial Reporting” — introduced by SSAE 18, effective May 1, 2017, and still the operative SOC 1 section today.
Plain-English explainer · Cites the AICPA attestation standards · Last reviewed July 2026
AT-C section 320 is the AICPA attestation section that governs SOC 1 examinations. It was created when SSAE 18 recodified the US attestation standards into “AT-C” sections in 2017, and it is still the operative section for SOC 1 today — later standards (SSAE 21, SSAE 23) amended the layers underneath it without replacing it. “AT-C” simply distinguishes the clarified sections from the older “AT” codification. A SOC 1 engagement never runs on AT-C 320 alone: it sits on top of AT-C 105 (concepts common to all attestation engagements) and AT-C 205 (assertion-based examinations), with AT-C 320 adding the service-organization-specific requirements. Its international sibling is ISAE 3402 — reports issued outside the US are frequently dual-badged “SSAE 18 / ISAE 3402”.
Key Takeaways
- AT-C 320 is the SOC 1-specific section of the AICPA attestation standards, introduced by SSAE 18 (effective May 1, 2017) and still current.
- A SOC 1 exam runs on three layers: AT-C 105 (common concepts) + AT-C 205 (assertion-based examinations, revised by SSAE 21) + AT-C 320 (SOC 1 subject matter).
- Control objectives in a SOC 1 are specified by management — reasonable, complete, and relevant to user entities’ ICFR — not prescribed by the AICPA (unlike SOC 2’s Trust Services Criteria).
- AT-C 320 prescribes the minimum contents of management’s system description — the nine elements listed on this page — and requires a written management assertion.
- A Type 1 opinion covers fairness of the description and suitability of control design at a point in time, while a Type 2 adds operating effectiveness over a period (and a description of the auditor’s tests).
The Three-Layer Architecture
The clarified attestation standards are modular. Understanding the layers explains why “is SSAE 18 still current?” has a subtler answer than yes or no — amendments land layer by layer.
AT-C 105 — Concepts Common to All Attestation Engagements
The foundation layer: independence, professional skepticism, engagement acceptance, and quality requirements that apply to every attestation engagement. Amended most recently by SSAE 23 (effective December 2025) to align with the AICPA’s quality-management standards.
AT-C 205 — Assertion-Based Examination Engagements
The examination layer: how a CPA examines subject matter against criteria when management provides a written assertion. SSAE 21 (effective June 2022) superseded the original SSAE 18 version of this section. SOC 1 and SOC 2 are both assertion-based examinations.
AT-C 320 — Controls at a Service Organization Relevant to ICFR
The SOC 1-specific layer: subject-matter requirements for examining controls relevant to user entities’ internal control over financial reporting — the system description, management-defined control objectives, and the form of the service auditor’s report.
SOC 2, by contrast, uses AT-C 105 + AT-C 205 plus the AICPA’s Trust Services Criteria and the DC section 200 description criteria — there is no “AT-C 320 for SOC 2”. That asymmetry is why SOC 1 has no separate description-criteria document: its description requirements live inside AT-C 320 itself.
What Management’s Description Must Contain
AT-C 320 (paragraphs .16–.17) sets the minimum elements of management’s description of the service organization’s system — the criteria the service auditor evaluates the description against. Paraphrased, the description must cover:
- The types of services provided, including, as appropriate, the classes of transactions processed.
- The procedures — automated and manual — by which services are provided, from transaction initiation and authorization through recording, processing, correction, and reporting.
- The related accounting records and supporting information involved in initiating, recording, processing, and reporting transactions.
- How the system captures and addresses significant events and conditions other than transactions (for example, system failures or data-conversion events).
- The process used to prepare reports and other information for user entities.
- The services performed by subservice organizations, and whether they are treated under the carve-out or the inclusive method.
- The specified control objectives and the controls designed to achieve them.
- Complementary user entity controls (CUECs) — and, where a carve-out applies, the complementary subservice organization controls (CSOCs) — assumed in the design of the controls.
- Other relevant aspects of the control environment, risk assessment process, information and communications, control activities, and monitoring that support the stated control objectives.
For a Type 2 report, the description must also cover relevant changes to the system during the examination period. The description doesn’t have to disclose every procedural detail — but it must not omit or distort information relevant to the user entities’ financial-reporting controls it serves.
Management Defines, the Auditor Opines
The most misunderstood feature of SOC 1: the control objectives are specified by management, not prescribed by the AICPA. There is no master checklist. Management states objectives that are reasonable, complete, and relevant to the ways its services affect user entities’ internal control over financial reporting — typically spanning transaction processing, logical access, change management, data integrity, and monitoring — and the service auditor evaluates whether those objectives are suitable before testing anything. This is the opposite of SOC 2, where the AICPA’s Trust Services Criteria are fixed and management maps controls to them.
AT-C 320 also requires a written management assertion — management asserting that the description is fairly presented, the controls were suitably designed, and (for Type 2) operated effectively. Without the assertion, the CPA cannot issue the report. The resulting opinion covers: (1) whether the description is fairly presented, (2) whether controls were suitably designed to achieve the stated objectives, and for a Type 2, (3) whether they operated effectively over the period, with the auditor’s tests and results described. SOC 1 reports are restricted-use: written for user entities, their financial-statement auditors, and management — not for public distribution.
AT-C 320 — Common Questions
How the standard behind SOC 1 actually works.
What is AT-C section 320?
Is AT-C 320 the same as SSAE 18?
What sections do a SOC 1 examination actually follow?
What must the SOC 1 system description include under AT-C 320?
Who defines the control objectives in a SOC 1?
What is the difference between AT-C 320 and ISAE 3402?
Related reading: the Learn hub, SSAE 18 vs SSAE 21 (which standard is current), CUECs & CSOCs, SOC 1 description criteria, and our SOC 1 services guide. More terms in the compliance glossary.
Related Reading
SOC 1 Description Criteria
Why SOC 1 has no DC 200 — its description requirements live in AT-C 320.
Read moreSSAE 18 vs SSAE 21
The SSAE lineage with effective dates — which standard is current.
Read moreCUECs & CSOCs Explained
The controls a SOC report assumes of you and of carved-out vendors.
Read moreICFR Controls Guide
The six ICFR control categories auditors test in a SOC 1 examination.
Read moreSOC 1 Knowledge Hub
Every SOC 1 guide — Type I vs II, ICFR controls, timelines, costs — in one place.
Read moreTypes of SOC Reports
SOC 1 vs SOC 2 vs SOC 3 — audiences, criteria, and which one buyers ask for.
Read more