- Home
- Compliance
- SOC 2 Compliance
- SOC 1 subservice organizations
SOC 1
The vendors behind your service, seen by a client's auditor.
If a bank moves your clients' payroll funds or a data centre hosts your billing system, part of the control chain sits outside your walls. A SOC 1 must say how those subservice organizations are treated, and a client's auditor will follow the chain to see whether it holds for their year.
Back to SOC 2 services01 · Who counts
Which vendors count in a SOC 1
A vendor counts when its work is likely relevant to clients' financial reporting.
The general test for a subservice organization, and how it is named in a description, is covered on the SOC 2 subservice guide. In a SOC 1 the filter is narrower: a vendor counts when its services or controls bear on your control objectives, and so on the figures clients record. A payment bank, a payroll tax filing agent or the host of your processing system usually does. A design agency does not.
02 · Carve-out or inclusive
A decision table for the method
The mechanics of both methods are on the carve-out guide. Here is how the choice usually falls in a SOC 1.
| Situation (illustrative) | Usual method | Why |
|---|---|---|
| Large cloud host with its own SOC 1 or SOC 2 | Carve-out | The vendor will not join your examination, and its own report covers its controls |
| Bank executing payments for your clients | Carve-out | Banks rarely take part in a customer's examination |
| A related company in your group runs part of the process | Often inclusive | Shared management makes a joint examination practical |
| A small specialist vendor with no report | Carve-out, with stronger monitoring | Inclusive needs the vendor's cooperation and assertion |
| Vendor performs controls that clients' auditors cannot get evidence of any other way | Consider inclusive | Saves each client's auditor from chasing the vendor separately |
03 · Monitoring
Monitoring controls over vendors
Under carve-out you still owe controls that show you watch the vendor.
- VM.1Obtain and review the vendor's reportEach year, get the vendor's SOC report, check its period, scope, opinion and exceptions, and record the review.
- VM.2Map the vendor's user controlsList the CUECs the vendor's report places on you, and show that you perform each one.
- VM.3Reconcile vendor outputsAgree bank confirmations, settlement files or processing totals from the vendor to your own records.
- VM.4Track service issuesLog incidents and failures reported by the vendor and assess their effect on your objectives.
- VM.5Review the relationshipPeriodic review of the contract, service levels and any change in what the vendor does for you.
04 · The vendor's report
Getting the vendor's SOC 1 or SOC 2
A SOC 1 from the vendor fits best. A SOC 2 can help, with care.
Vendor SOC 1
Built for this purpose
- Control objectives framed around financial reporting
- Clients' auditors can use it directly alongside yours
- Check its CUECs against what you do
Vendor SOC 2
Useful, but read across
- Security, availability or processing integrity criteria may cover what you need
- Does not address financial reporting objectives as such
- You may need extra monitoring to cover the gap
If the vendor has no report at all, monitoring has to carry more weight: direct confirmations, reconciliations and contractual rights to information.
05 · Closing gaps
Bridging gaps in vendor coverage
The vendor's report rarely lines up perfectly with yours.
- Period mismatch. The vendor's period ends months before yours. Ask for their bridge letter and note it in your review.
- Scope mismatch. The vendor's report covers a different product or region. Confirm what it actually covers before relying on it.
- Exceptions in their report. Assess whether each one affects your objectives, and record any compensating step you took.
- No report this year. Increase reconciliation and confirmation work, and say what you did.
06 · Effect on the opinion
How the method shows up in the opinion
Carve-out narrows what the opinion covers; it does not hide the vendor.
Under carve-out, the opinion says that some control objectives are achieved only if the vendor's complementary subservice organization controls operate as assumed, and the vendor's controls are not tested. A client's auditor then looks for evidence about the vendor separately. Under the inclusive method, the vendor's controls are tested and covered, which needs the vendor's cooperation and its own written assertion.
Neither method is a weakness in itself. What harms the opinion is a relevant vendor left out of the description altogether.
07 · Payroll with a bank
Illustrative: a payroll provider and its bank
One provider, one bank, carve-out.
- The provider calculates net pay and sends a payment file to its bank, which pays employees.
- The description names the bank, its role in disbursing pay, and the carve-out method.
- It states the controls assumed of the bank: payments executed as instructed and on the value date, and rejected items reported back.
- The provider's monitoring control: each run, it reconciles the bank's payment confirmation to the payroll register and follows up rejects.
- A client's auditor reads this, confirms the client reviews its own pay register, and decides whether further evidence about the bank is needed.
Sources: AICPA SSAE No. 18, AT-C section 320; AICPA SOC 1 guide; PCAOB AS 2601 for the carve-out and inclusive terms. Vendors, situations and the payroll scenario are illustrative.
Questions about SOC 1 subservice organizations
Is our cloud provider always a subservice organization?
Usually, if it hosts the system that processes clients' transactions.
If the provider's controls over infrastructure bear on your IT objectives, it is relevant. A cloud tool used only for internal email usually is not.
Can we choose different methods for different vendors?
Yes.
Each relevant vendor is presented by its own method. Many reports carve out a cloud host and a bank while including a group company.
The vendor's report has exceptions. Does that taint ours?
Not automatically, but you must assess them.
Under carve-out, the vendor's controls are outside your opinion. Your monitoring should show you read the exceptions and judged their effect. A client's auditor will ask.
Do we need to share the vendor's report with clients?
Often their auditors ask for it.
Under carve-out, clients' auditors may need evidence about the vendor. Point them to how they can obtain the vendor's report, subject to the vendor's own sharing terms.
Related guides
- Carve-out or inclusive: how vendors appear in your reportTwo ways to present a vendor, and what each does to your report.
- Subservice organizations: vendors inside your reportWho counts, how they're monitored, and what the report must say.
- User entity controls in a SOC 1What clients must do for your controls to work.
Present every vendor in the chain.
We help you identify relevant subservice organizations, choose a method and build monitoring a CPA firm can test.