Start hereIdentify financial reporting impact
~160 days leftOpen step
Guide library
Audit report Global

SOC 1

System and Organization Controls 1 · Internal control over financial reporting

Give customers’ financial auditors evidence about the controls your service operates for them.

Who it applies to

Service organizations with processes relevant to user entities’ internal control over financial reporting, such as payroll or transaction processing.

What you’ll produce

Restricted-use service auditor’s report for user entities and their auditors.

Start with customer financial reporting risks and relevant transaction flows. A SOC 1 control objective is different from a SOC 2 Trust Services criterion.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which customer close processes depend on our service?
Obtain examples from customer controllers. Record the reports, transactions and handoffs those customers use in financial reporting before agreeing objectives with the CPA firm.
What report and period will customers need?
Confirm Type 1 or Type 2, entities in scope, use of subservice organizations, delivery and customer year-end coverage with the firm and commercial team.
Who controls the reporting evidence?
Assign a financial process owner and a system owner. Budget for report reconciliation, access and change evidence, exceptions, fieldwork and secure report distribution.

How to spend the first week

  1. Bring a real customer reporting cycle, sample financial output and contract. Trace from transaction intake through processing and delivery.
  2. Ask the system team to identify upstream feeds, job failures, manual overrides and dependency on customer approvals.
  3. Agree control objectives and readiness milestones with management and the CPA firm. Document customer responsibilities in the system description.

What to review each week

Report reconciliation failures, missing transaction populations, overdue fixes and changes that affect customer close cycles.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

SOC 1 kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Identify financial reporting impact · Finance controls lead [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Bring a real customer reporting cycle, sample financial output and contract. Trace from transaction intake through processing and delivery.
2. Ask the system team to identify upstream feeds, job failures, manual overrides and dependency on customer approvals.
3. Agree control objectives and readiness milestones with management and the CPA firm. Document customer responsibilities in the system description.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Which service transactions can affect a customer’s financial statements?
  • Which controls belong to the service provider and which stay with the customer?

Worked scenario

A payroll processor maps employee changes, pay calculations and customer-approved transfers. The team records which reports feed the customer’s ledger and which approvals the customer still performs.

What to read next

  • SOX Section 404

    Understand how your customer might use the service auditor’s report.

  • SOC 2

    Review the different scope of a security-focused examination.

The whole journeyabout 160 days across 4 steps
  1. 01Identify financial reporting impactFinance controls lead · ~14 days
  2. 02Define objectives and assign controlsFinance + service auditor · ~28 days
  3. 03Collect records and support testingControl owners + independent CPA · ~90 days
  4. 04Issue and distribute securelyManagement + independent CPA · ~28 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 12 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Identify financial reporting impactFinance controls leadBefore scope approvalSet a start dateProcess narratives; System boundary; Customer control dependenciesOpen
Define objectives and assign controlsFinance + service auditorBefore the report date or periodSet a start dateControl objectives; Risk-control matrix; System description draftOpen
Collect records and support testingControl owners + independent CPADuring the Type 2 period and fieldworkSet a start dateEvidence index; Sampling populations; Exception logOpen
Issue and distribute securelyManagement + independent CPAAfter examinationSet a start dateManagement assertion; Final report; Distribution logOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. This estimate assumes a Type 2 report. Check official dates and agree real durations with your team.

  1. 01

    Identify financial reporting impact

    Who Finance controls lead When Before scope approval

    Trace relevant transactions from initiation through reporting, including subservice organizations, and identify user auditor needs.

    How to do this step

    Before you start

    Service agreements, process maps, sample transaction files and reports customers use at close.

    1. Trace one transaction from customer input to the report delivered. Mark interface reconciliations, error handling and manual adjustments.
    2. Link failures to customer financial reporting risks such as incomplete postings, duplicate transactions or incorrect cut-off.
    3. List system, vendor and customer responsibilities, and validate the boundaries with customer-facing and financial process owners.

    What a reviewer should see

    The narrative shows who corrects a rejected transaction and how the customer learns about it.

    When to escalate

    Escalate unknown or undocumented customer reliance before control objectives are set.

    What to produce

    Process narrativesMemo

    Gather first

    • Approved system boundary
    • Architecture, data flows, controls and service commitments
    • Current reporting instructions or system plan template

    How to prepare it

    1. Explain who uses the system, the commitments it supports and how people, processes, software, infrastructure and data fit together.
    2. Walk through actual transactions or requests and identify the relevant controls and shared responsibilities. Cover dependencies and any criteria or requirements in the agreed template.
    3. Validate each section with the technical owner against live architecture, procedures and evidence. Lock the approved version and reconcile it to diagrams and control records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Service and objective
    Hosted invoice service receives orders, calculates amounts and sends PDF receipts.
    Boundary and inputs
    Accepted production order events, account identifiers and billing records
    How it works
    Payment result updates invoice status. Release pipeline deploys code with approval.
    Shared roles
    Customer controls user configuration. Hosting vendor manages physical infrastructure.
    Evidence and review
    Architecture v3, deployment records and service-owner review

    Check before handing it over

    The written description, diagrams and control records agree. A reviewer can understand end-to-end operation.

    Send the approved draft to management and the independent evaluator. Transfer it to the prescribed system plan or report template when needed.

    System boundaryMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

    Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

    Customer control dependenciesMemo

    Gather first

    • Named roles, on-call contacts and authority
    • Realistic use cases and deadlines
    • Service and vendor dependencies

    How to prepare it

    1. Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
    2. Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
    3. Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Event or activity
    Unusual activity detected in support export portal
    First action and owner
    On-call engineer opens a restricted incident case and preserves logs.
    Decision owner and backup
    Privacy lead or legal duty contact will determine reporting.
    Handoff and clock
    Send incident ID, UTC timestamp and known scope immediately.
    Validation
    Exercise completed and backup contact reached.

    Check before handing it over

    Every decision has one accountable person, a backup and a practical route to reach them.

    Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.

  2. 02

    Define objectives and assign controls

    Who Finance + service auditor When Before the report date or period

    Align objectives to the financial processes. Assign owners, define evidence and document complementary user entity controls.

    How to do this step

    Before you start

    Approved process narratives, customer risk scenarios and current manual and automated controls.

    1. Translate each financial reporting risk into a control objective and link it to named controls and operating frequency.
    2. For each key report, define the period, source query, parameters and checks for completeness and accuracy.
    3. Reperform a reconciliation with the owner. Capture the exact records, difference threshold, approval and evidence of follow-up.

    What a reviewer should see

    A daily reconciliation control links expected file totals to processed totals, explains differences and records reviewer approval.

    When to escalate

    Raise reports that users rely on when nobody can explain how totals were generated or validated.

    What to produce

    Control objectivesSpreadsheet

    Gather first

    • Applicable criteria, requirements or risk decisions
    • Current procedures and configurations
    • Names of people operating or reviewing each control

    How to prepare it

    1. Give each requirement and implemented control an ID. Write a short control statement naming who does what, when and in which system.
    2. Record the evidence the control produces and how it could be tested. For a shared or inherited control, state who owns each part.
    3. Walk through one control with its operator. Check a real recent run, record gaps and obtain approval for exclusions or alternate controls.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement
    Production access is reviewed periodically.
    Control ID
    AC-04
    Control activity
    IAM team exports administrator roles every quarter. System owners approve or revoke each assignment.
    Owner and frequency
    IAM lead, quarterly
    Evidence
    Export with filters, annotated review and removal tickets
    Test and status
    Reconcile export to current roles. Inspect approvals. Operating.

    Check before handing it over

    A different person can operate the control or test it using the matrix and its evidence links.

    Give the baseline to control owners and the assessor before walkthroughs or sampling.

    Risk-control matrixSpreadsheet

    Gather first

    • Applicable criteria, requirements or risk decisions
    • Current procedures and configurations
    • Names of people operating or reviewing each control

    How to prepare it

    1. Give each requirement and implemented control an ID. Write a short control statement naming who does what, when and in which system.
    2. Record the evidence the control produces and how it could be tested. For a shared or inherited control, state who owns each part.
    3. Walk through one control with its operator. Check a real recent run, record gaps and obtain approval for exclusions or alternate controls.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement
    Production access is reviewed periodically.
    Control ID
    AC-04
    Control activity
    IAM team exports administrator roles every quarter. System owners approve or revoke each assignment.
    Owner and frequency
    IAM lead, quarterly
    Evidence
    Export with filters, annotated review and removal tickets
    Test and status
    Reconcile export to current roles. Inspect approvals. Operating.

    Check before handing it over

    A different person can operate the control or test it using the matrix and its evidence links.

    Give the baseline to control owners and the assessor before walkthroughs or sampling.

    System description draftMemo

    Gather first

    • Approved system boundary
    • Architecture, data flows, controls and service commitments
    • Current reporting instructions or system plan template

    How to prepare it

    1. Explain who uses the system, the commitments it supports and how people, processes, software, infrastructure and data fit together.
    2. Walk through actual transactions or requests and identify the relevant controls and shared responsibilities. Cover dependencies and any criteria or requirements in the agreed template.
    3. Validate each section with the technical owner against live architecture, procedures and evidence. Lock the approved version and reconcile it to diagrams and control records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Service and objective
    Hosted invoice service receives orders, calculates amounts and sends PDF receipts.
    Boundary and inputs
    Accepted production order events, account identifiers and billing records
    How it works
    Payment result updates invoice status. Release pipeline deploys code with approval.
    Shared roles
    Customer controls user configuration. Hosting vendor manages physical infrastructure.
    Evidence and review
    Architecture v3, deployment records and service-owner review

    Check before handing it over

    The written description, diagrams and control records agree. A reviewer can understand end-to-end operation.

    Send the approved draft to management and the independent evaluator. Transfer it to the prescribed system plan or report template when needed.

  3. 03

    Collect records and support testing

    Who Control owners + independent CPA When During the Type 2 period and fieldwork

    Preserve transaction populations, exception handling and approvals. Support walkthroughs and tests over the agreed period when applicable.

    How to do this step

    Before you start

    Evidence request list, defined Type 2 period when relevant, operational logs, job runs and issue tickets.

    1. Document each population source and reconcile counts to the source system. Let the CPA firm select its testing items.
    2. Provide sampled records with source data, approvals and timely follow-up. Keep exception history if a transaction was corrected later.
    3. Explain corrections and their customer impact to the process owner and firm. Track responses and retain original evidence.

    What a reviewer should see

    A sampled broken interface includes the failure log, correction, rerun totals, approval and customer communication when applicable.

    When to escalate

    Escalate missing populations, unreviewed overrides and issues that could affect a customer’s close.

    What to produce

    Evidence indexSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

    Sampling populationsSpreadsheet

    Gather first

    • Authoritative ticket, event or transaction system
    • Exact scope, time zone and date window
    • Auditor’s population and sampling request

    How to prepare it

    1. Define what counts as one row and agree start and end cutoffs with the auditor. Export all in-scope activity, including failed or cancelled records when relevant.
    2. Save the query and export timestamp. Keep stable source IDs and reconcile totals to an independent report. Explain any legitimate exclusions.
    3. Give the full population to the auditor before sampling. Link selected items to underlying records as requested.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    CHG-0742
    Occurred at
    2026-09-22 15:08 UTC
    System and event
    Billing API, production deploy
    State
    Completed
    Evidence key
    Release job 7242, linked approval PR-881
    Population filter
    Production deploys, Jul through Sep 2026 UTC

    Check before handing it over

    The reviewer can reproduce the count and trace any selected item back to the original system.

    Transfer the export, query, reconciliation and any exclusions to the independent tester.

    Exception logMemo

    Gather first

    • Agenda or decision request
    • Current performance measures and findings
    • Proposed actions and participants

    How to prepare it

    1. Write what decision is needed and list the reports or records the decision maker reviewed. Capture the date, people and decision authority.
    2. Record the decision, alternatives considered, any remaining risk and exactly who will do what by when.
    3. Send notes for factual review. File the approved record and add actions to the working tracker so progress reaches the next review.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Item
    Approve a fix for the missing access-removal retry.
    Inputs reviewed
    September test results and IAM incident root-cause notes.
    Decision
    Approve automatic retry plus daily reconciliation.
    Action and due date
    Platform lead to ship and test by 2026-11-28.
    Residual risk and follow-up
    Manual review remains until rollout. Check at December meeting.

    Check before handing it over

    The minutes identify the person who approved each action and the date the decision will be revisited.

    Give owners the actions and add the approved record to the relevant audit or governance file.

  4. 04

    Issue and distribute securely

    Who Management + independent CPA When After examination

    Reconcile findings, sign required representations and deliver the restricted-use report to entitled recipients.

    How to do this step

    Before you start

    Final system description, exception analysis, management assertion draft and engagement terms.

    1. Confirm customer control responsibilities and vendor treatment read consistently with service agreements and actual operation.
    2. Have management review the report period and exceptions before signing its assertion. Capture the final issued report.
    3. Set approved distribution and explain any period gap and relevant customer responsibilities to the account team.

    What a reviewer should see

    The approved delivery record captures report version, recipient and access date.

    When to escalate

    Bring unresolved exception language or unapproved recipients to management before release.

    What to produce

    Management assertionMemo

    Gather first

    • Applicable form or requirements
    • Approved scope and supporting records
    • Named signatory and approval route

    How to prepare it

    1. Identify which person can sign and what they must confirm. Gather supporting evidence, dates, responsibility and any required issuer wording.
    2. Draft a signed-document checklist or brief in your organization’s approved format. Reconcile every factual claim against the source evidence and route the draft for review.
    3. Use the applicable official wording or format for the real signed document. File the executed copy with its date, applicable scope and supporting evidence.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document owner
    Accountable executive or authorized signatory
    Scope and date
    Agreed service scope, as of 2026-10-31
    Supporting documents
    Scope v3, final control testing and open issue review
    Review and approval
    Legal and responsibility owner review before signature
    Filed record
    Signed copy plus evidence references

    Check before handing it over

    The signer can explain the basis for each statement and the record reflects the required scope and period.

    Give the executed document to the relevant recipient under the engagement or regulation. Use the worksheet to organize review.

    Final reportIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

    Distribution logSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    Every open item has a next action and closed items have a verifiable record of closure or delivery.

    Use the log at case reviews and provide a restricted copy only where the engagement requires it.

Common questions

When would a customer need SOC 1?

A customer may need SOC 1 when a service affects its internal control over financial reporting. Start by tracing the transactions and reports that feed the customer’s financial statements, then confirm the report scope with the customer and its auditor.

AICPA · SOC suite of services (opens in a new tab)

What does the service organization give the auditor?

Provide the system description, control objectives and control procedures. For Type 2, preserve complete transaction or event populations and the records needed to test operating effectiveness during the period.

AICPA · SOC suite of services (opens in a new tab)
PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes