Payments and billing providers
If you process transactions or invoices for customers, their auditors need comfort over accuracy and completeness.
Customers whose financial statements depend on your systems will ask for a SOC 1 report so their auditors can rely on your controls. Sumrite gets you ready with gap analysis, testing evidence and a board-ready report.
SOC 1 is an attestation report on the controls at a service organisation that are relevant to your customers' financial reporting. It is issued by a licensed CPA firm under SSAE 18 in the United States, or under ISAE 3402 internationally. The aim is simple: let a customer's auditor rely on your controls instead of testing them one customer at a time.
Unlike SOC 2, where the criteria are fixed, a SOC 1 starts with control objectives you define for the services you provide, such as "payments are processed completely and accurately". The auditor tests the controls that meet those objectives, plus the IT general controls (ITGCs) underneath them: access, change management and operations.
A Type I report covers design on a single date. A Type II report also tests whether controls operated effectively across a period, which is what most customers' auditors want. The report is restricted to your management, your customers and their auditors, and it lists complementary user entity controls (CUECs), the things your customers must do on their side for the control objectives to hold.
A SOC 1 has no fixed checklist. The control objectives are yours to define and the auditor tests against them. These are the building blocks that most reports contain.
You and the auditor agree what could go wrong for a customer's financial statements, then write objectives that cover it. Good objectives are specific to your service, not generic.
Auditors check that only the right people can reach systems and data that affect customer transactions, and that privileged access is limited and reviewed.
Changes to applications, databases and infrastructure should be requested, tested, approved and released in a controlled way, so a calculation cannot be altered unnoticed.
Jobs run, backups complete and incidents are handled. Auditors look for monitoring that shows failures are noticed and fixed.
These are the controls closest to the numbers: input checks, reconciliations, approvals and report review. They are usually where customers' auditors focus first.
If you process transactions or invoices for customers, their auditors need comfort over accuracy and completeness.
Payroll runs feed customers' ledgers directly, so auditors ask how calculations and changes are controlled.
When a customer's ERP or ledger runs on your infrastructure, access and change controls come under review.
Valuation, cash movement and reporting for investors and borrowers are classic SOC 1 territory.
The work is technical. The consequences of getting SOC 1 wrong show up in revenue, liability and reputation, which is why we report on it in the language of the boardroom first.
Finance-adjacent customers often make a SOC 1 report a condition of onboarding or renewal. Without it, their auditors may need to test you directly, which slows deals.
Errors in financial processing can flow into your customers' statements. Well-defined, tested controls reduce the chance of disputes over who was responsible.
Customers' auditors talk to each other. A clean, well-organised report makes you easy to rely on, and exceptions handled openly build trust.
The reporting period drives the calendar. Someone senior needs to own scope, evidence and the date customers expect the report.
Timelines are typical ranges, not promises. Yours depends on scope, team size and how much is already in place.
Confirm the services, systems and customer financial processes in scope, and draft control objectives with your auditor in mind.
Compare existing controls with the objectives and ITGC expectations, then fix what is missing so controls leave evidence by default: tickets, approvals, review sign-offs and logs.
Test the controls as an auditor would, and run penetration testing on in-scope systems so access weaknesses are fixed before the period starts.
For Type II, controls must run consistently for the whole period. Keep evidence organised as you go.
The CPA firm tests samples, raises questions and issues the report with its opinion.
SOC 1 does not prescribe penetration testing. It does expect strong logical access and change controls over systems that process financial data, and an expert-led test is a practical way to show those controls hold up against a real attacker.
Testing shows whether authentication, authorisation and privilege boundaries on in-scope applications can be bypassed.
Findings from testing feed the change process, and a retest proves fixes were released and verified.
Business-logic testing checks whether a user can approve, alter or replay a transaction they should not.
A clear report, remediation log and retest give the examiner something concrete to read alongside your own control evidence.
Generic objectives are hard to test and do not help customers' auditors. Tie each one to a financial process you actually run.
If your customers do not operate the controls you rely on, the objectives may not be met. State them clearly and tell customers early.
SOC 1 is about financial reporting. If buyers ask about security, availability or confidentiality, SOC 2 is usually the report they mean.
If a cloud or processing vendor supports your service, decide whether to carve it out or include it, and manage the controls you depend on.
SOC 1 is a team effort between your people, your auditor and your customers. We take the weight off all three.
From the first question about SOC 1 to the final report, you deal with one accountable team and one timeline.
We have taken more than 250 clients through SOC 2 and similar audits, so we know what reviewers ask for and what they accept.
We explain what SOC 1 means for your business, your roadmap and your customers before any technical work starts.
Where a third party issues the report or certificate, we route that step through local partner firms so you never have to manage a second vendor.
One accountable team takes you from scoping to retest. The people who test your systems are the people who explain the findings to your leadership.
A clear view of your controls against the objectives and ITGC expectations, with owners and a prioritised fix list.
Expert-led testing of in-scope applications and infrastructure, focused on access and transaction integrity.
We test your controls the way an examiner would, so weaknesses surface before the period starts.
Organised, dated evidence mapped to each control so the examination runs smoothly.
Guidance while your team fixes findings, then a retest to confirm they are closed.
A plain-English summary of status, risks and decisions for executives, with technical detail behind it.
Every engagement ends with material written for two audiences: a plain-language view for executives and the board, and full technical detail for the engineers who fix things.
Name the processes whose errors would change a customer's numbers. That defines scope.
Every control needs a named owner who will produce evidence, not just a policy.
Complementary user entity controls only work if customers know about them.
Decide how cloud and processing vendors are treated and what evidence you hold.
Do not start a Type II period until controls run reliably; exceptions inside the period are permanent.
A SOC 1 report is an attestation by a licensed CPA firm on controls at a service organisation that are relevant to its customers' financial reporting. Customers' auditors use it to rely on your controls.
SOC 1 covers controls relevant to financial reporting, against control objectives you define. SOC 2 covers security, availability, processing integrity, confidentiality and privacy against fixed AICPA criteria. Many providers need both.
Type I looks at whether controls are suitably designed on one date. Type II also tests whether they operated effectively over a period, commonly six to twelve months for a first report.
IT general controls are the access, change management and operations controls that support the systems producing financial data. Auditors test them because weak ITGCs undermine every automated control above them.
They are controls your customers must perform for your control objectives to be achieved, such as reviewing user access to your platform. The report lists them so customers and their auditors know their part.
They are closely aligned. SSAE 18 is the US standard and ISAE 3402 is the international one, and a single examination can often be reported under both.
No. Penetration testing is not named as a requirement, but many service organisations use it as supporting evidence for logical access and change controls over in-scope systems.
We run the full engagement for you and route the formal attestation through our network of licensed CPA partner firms, so you deal with one team from scoping to report.
Browse all 23 security and compliance frameworks or see our penetration testing services.
Tell us your scope, your deadline and who is asking. You get a fixed-scope quote and a named lead from day one.
Get a Quote →