If your platform runs payroll, moves money, bills customers, processes claims or administers funds, your clients' financial auditors will want to know that your controls work. A SOC 1 report is how you show them. This guide explains when fintech, payroll and payments companies need SOC 1, what it covers, Type 1 vs Type 2 and how it differs from SOC 2. For hands-on help, see our SOC 1 readiness consulting page.
What is a SOC 1 report?
A SOC 1 report is an examination by a licensed CPA firm of a service organisation's controls that are relevant to its clients' internal control over financial reporting (ICFR). Your clients' financial auditors use it to decide how far they can rely on your processing, instead of testing your systems themselves.
The examination is performed under the SSAE 18 attestation standard. A SOC 1 report contains a description of your system, the control objectives you define, the controls that meet them and the CPA firm's opinion. A Type 2 report also includes the auditor's tests and results. Because one report can serve many clients, it saves you from answering the same audit questions again and again from each client's auditor.
Which fintech, payroll and payments companies need SOC 1?
You need SOC 1 when what you do for clients flows into their financial statements. Payroll providers, payment processors, billing and invoicing platforms, claims processors and fund administrators are typical examples. The clearest signal is a request from a client's finance team or external auditor, often during their year-end audit or a vendor review.
| Business | Why client auditors care | Example processes in scope |
|---|---|---|
| Payroll | Salaries, taxes and deductions drive the client's expenses and liabilities | Payroll inputs, pay calculations, statutory deductions, payment files |
| Payments | Receipts and settlements affect the client's cash and revenue | Transaction processing, settlement, reconciliation, refunds |
| Billing and invoicing | Invoices drive the client's revenue and receivables | Pricing and rate changes, invoice generation, credit notes |
| Claims processing | Claims drive expenses and liabilities | Claim intake, adjudication, payment, reporting |
| Fund administration | Valuations and investor balances appear in financial statements | Pricing, net asset value calculation, investor transactions |
Requests come most often from clients whose own controls are audited closely, such as public companies subject to SOX. If no client's auditor has asked yet, but your largest prospects are finance-heavy businesses, it is worth planning ahead.
What does a SOC 1 report cover?
A SOC 1 report covers the business processes and IT general controls that affect your clients' financial data. You define control objectives, such as payroll calculations being complete and accurate, and the controls that meet them. The CPA firm then reports on your description, the design of those controls and, for Type 2, whether they operated.
Two kinds of control sit underneath the objectives:
- Business process controls, such as approvals, reconciliations and reviews of calculations.
- IT general controls (ITGCs) over the systems that process client data: logical access, change management and computer operations. Our ITGC page explains these in more detail.
The example below shows how objectives and controls might look for a payroll provider. It is an illustration only; your objectives depend on the services you provide and what your clients' auditors rely on.
| Example control objective | Example controls |
|---|---|
| Client payroll inputs are authorised and recorded completely and accurately | Client approval workflow; validation of uploaded files; reconciliation of submitted files to processed batches |
| Pay calculations are accurate | Tax tables and pay rates changed only through approved changes; independent review of calculation changes |
| Payments are processed completely, accurately and on time | Approval of payment batches; reconciliation of bank files to payroll registers |
| Logical access to payroll systems is restricted to authorised users | Approved access requests; quarterly access reviews; access removed when staff leave |
| Changes to payroll applications are authorised and tested | Change tickets; testing records; approval before release |
| Processing errors are identified and resolved | Job monitoring; exception queues with resolution records |
Should you get SOC 1 Type 1 or Type 2?
Type 1 reports on whether your controls were suitably designed at a point in time. Type 2 also tests whether they operated effectively over an observation period, usually 3 to 12 months. Client auditors generally rely on Type 2, so many companies start with Type 1 to show progress and move to Type 2 next.
When you plan a Type 2, think about your clients' financial years. Their auditors want coverage of as much of the year as possible, so align your period with the year ends your clients have in common, for example 31 March or 31 December. Where your period ends before a client's year end, management can provide a bridge letter covering the gap. Our SOC 1 Type 1 vs Type 2 guide covers the report structure in more depth.
How is SOC 1 different from SOC 2?
SOC 1 is about controls that affect your clients' financial reporting and is read by their financial auditors. SOC 2 is about security and the other Trust Services Criteria and is read by their security and procurement teams. Fintech and payments companies are often asked for both, because they handle client money and sensitive data.
| SOC 1 | SOC 2 | |
|---|---|---|
| Question it answers | Can client auditors rely on your processing of their financial data? | Do your controls protect the system and data? |
| Framework | Control objectives you define | AICPA Trust Services Criteria: Security (CC1 to CC9) always, plus optional criteria |
| Main readers | Clients' finance teams and external auditors | Clients' security, risk and procurement teams |
| Types | Type 1 and Type 2 | Type 1 and Type 2 |
For a fuller comparison, read SOC 1 vs SOC 2 vs SOC 3.
Can you do SOC 1 and SOC 2 together?
Yes. Many fintech and payroll companies run both reports from one programme. Access, change management and operations controls serve both, so you build and evidence them once. The observation periods can be aligned, while the reports stay separate because they answer different questions for different readers. CyberWave GRC maps shared controls so nothing is built twice.
Running both together usually means one set of policies, one access review cycle and one change process, tested by the CPA firm for each report. The SOC 1 work adds control objectives for your financial processing, and the SOC 2 work adds the security criteria your customers ask for. See our SOC 2 consulting page for that side.
What are complementary user entity controls?
Complementary user entity controls, or CUECs, are controls your clients must operate for your controls to work as described. For a payroll provider, that might mean the client approving payroll inputs before submission and reviewing payroll reports afterwards. They are listed in the report so client auditors can test them at the client.
Write CUECs precisely. A vague CUEC such as "clients maintain appropriate controls" helps no one, while a clear one tells the client's auditor exactly what to test. Do not use CUECs to push your own responsibilities onto clients; auditors and clients notice.
How to prepare for a SOC 1 examination
- Confirm what clients need. Ask which services their auditors rely on and which report type they expect.
- Map your services. Identify the processes and systems that touch clients' financial data.
- Define control objectives and controls. Keep objectives clear and tied to financial reporting.
- Run a readiness assessment. Test design, fix gaps and document process narratives.
- Choose the type and period. Align a Type 2 period with your clients' year ends.
- Prepare evidence. Make sure each control leaves a dated record every time it runs.
- Support the examination. The CPA firm tests controls and issues the report.
- Plan renewals. Keep periods back to back and plan bridge letters for any gaps.
Common causes of exceptions
- Reconciliations skipped in busy months, or done without a record of review.
- Rate, tax table or pricing changes made without the approval the control requires.
- Access not removed promptly when staff leave.
- Emergency changes released without approval afterwards.
- Client inputs processed without the validation step the report describes.
How CyberWave GRC helps
We scope your services and control objectives, write process narratives, run a readiness assessment, fix gaps and prepare evidence for your CPA firm's SOC 1 Type 1 or Type 2 examination. If you also need SOC 2, we map shared controls so you build them once. A licensed CPA firm issues the report; we never issue SOC reports ourselves. Our fee is fixed and quoted after a free scoping call; the CPA firm's examination fee is separate and set by the CPA firm.


