SOC report review template
One worksheet per report: what it covers, what the auditor found, which controls the report expects your bank to run, and what you will follow up.
The 2024 community bank guide lists System and Organization Controls (SOC) reports among the documents a bank may review in due diligence to assess a third party’s operational risk management and internal controls, and again in ongoing monitoring to confirm its control environment remains sound [1]. The Board’s 2026 proposal for community banks names SSAE 18 SOC reports first among the independent assessments a bank may rely on for the matters they cover [2]. The AICPA sets the professional standards for SOC engagements [3]; a SOC 1 report examines controls at a service organization that are likely to be relevant to its customers’ internal control over financial reporting [4].
A SOC report only helps if someone reads past the opinion. This worksheet walks a reviewer through the parts that most often change the conclusion: whether the report covers the service you use, for the period you need, and what it leaves for your bank to do.
How to use it
- Fill in one copy per report, per vendor. Keep it with the report in the vendor’s file.
- Work down the rows in order. The “Where to look” column says where the information usually sits; section names and order vary between audit firms.
- Anything that leaves a question open goes in “Follow-up” with an owner and a date, and stays open until it is answered.
- The reviewer signs the conclusion; a second person approves it if your policy asks for one.
The template
Download as CSV Opens in Excel, Numbers or Google Sheets. To print, use your browser’s Print command.
| Item | What to record | Where to look | Finding | Notes and follow-up |
|---|---|---|---|---|
| The report | ||||
| Service organization | The vendor's legal name, and the name of the system or service the report describes. | Cover page; management's assertion | ||
| Report type | SOC 1 (controls relevant to your financial reporting) or SOC 2 (controls over security and the other trust services categories in scope). | Title page; auditor's report | ||
| Type 1 or Type 2 | Type 1 reports on the vendor's description of its system and the design of its controls as of a specified date; Type 2 also reports on whether the controls operated effectively throughout a specified period, with the auditor's tests and results. Record which, and whether that is what your policy expects for this vendor's tier. | Title page; auditor's report | ||
| Period or date | The as-of date (Type 1) or the start and end of the period tested (Type 2). | Auditor's report; management's assertion | ||
| Service auditor | The CPA firm that signed the report, and the report date. | Auditor's report | ||
| Scope | ||||
| Services covered | Whether the services, applications and locations your bank uses are inside the system description. If not, the report does not speak to them. | System description | ||
| Trust services categories (SOC 2) | Which categories are in scope: security, availability, processing integrity, confidentiality, privacy. Compare with what matters for this relationship. | Auditor's report; system description | ||
| Control objectives (SOC 1) | Whether the control objectives cover the processing your financial reporting relies on. | System description; control objectives | ||
| Results | ||||
| Opinion | Unmodified, qualified, adverse or a disclaimer of opinion. Anything other than unmodified needs a written explanation of what it means for your use. | Auditor's report | ||
| Exceptions | Each control the auditor found did not operate as described: the control, the exception, management's response, and whether it touches a control you rely on. | Tests of controls and results | ||
| Changes during the period | System changes, incidents or control changes the report describes, and whether they affect your service. | System description | ||
| What the report leaves to others | ||||
| Subservice organizations | Other companies the vendor relies on (a hosting provider, for example), and whether their controls are excluded from the description and the audit (the carve-out method) or included in them (the inclusive method). For each carved-out one that matters, how you will get comfort: its own report or another source. | System description; auditor's report | ||
| Complementary user entity controls | The controls the vendor's management assumed, in designing its system, that user entities such as your bank would operate, and that are needed for the report's controls to achieve their objectives (for example, reviewing user access or reconciling outputs). For each one: who at the bank does it, and the evidence that it is done. | System description, usually near the end | ||
| Gap to today | The months between the end of the period and today. If the gap matters for this vendor, request a bridge letter from the vendor and note the date received. | Report period; bridge letter from the vendor | ||
| Conclusion | ||||
| Follow-up items | Each open question or concern, with an owner and a due date. | This worksheet | ||
| Conclusion | Whether the report, with any follow-up, supports continuing the relationship as it is, and why. | This worksheet | ||
| Sign-off | Reviewer name and date; approver name and date if your policy requires one. | This worksheet | ||
The reviewer decides whether the report is enough for your bank’s use of the service. This worksheet records that decision and the reasons for it; it does not make it.
The terms for type 1 and type 2 reports, the carve-out and inclusive methods and complementary user entity controls follow the definitions in AT-C section 320, paragraph .08; the opinion types follow AT-C section 205, paragraph .04 (a modified opinion is a qualified opinion, an adverse opinion or a disclaimer of opinion) [5].
This is general information, not legal advice. For what a rule requires of your organization, read the rule itself or ask your counsel.