DORA
Organize ICT risk, incident reporting, resilience testing and third-party oversight for EU financial entities.
System and Organization Controls 1 · Internal control over financial reporting
Give customers’ financial auditors evidence about the controls your service operates for them.
Service organizations with processes relevant to user entities’ internal control over financial reporting, such as payroll or transaction processing.
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.
Report reconciliation failures, missing transaction populations, overdue fixes and changes that affect customer close cycles.
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.
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.
Understand how your customer might use the service auditor’s report.
Review the different scope of a security-focused examination.
Checklist, instructions and 12 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Identify financial reporting impact | Finance controls lead | Before scope approval | Set a start date | Process narratives; System boundary; Customer control dependencies | Open |
| Define objectives and assign controls | Finance + service auditor | Before the report date or period | Set a start date | Control objectives; Risk-control matrix; System description draft | Open |
| Collect records and support testing | Control owners + independent CPA | During the Type 2 period and fieldwork | Set a start date | Evidence index; Sampling populations; Exception log | Open |
| Issue and distribute securely | Management + independent CPA | After examination | Set a start date | Management assertion; Final report; Distribution log | Open |
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.
Trace relevant transactions from initiation through reporting, including subservice organizations, and identify user auditor needs.
Service agreements, process maps, sample transaction files and reports customers use at close.
The narrative shows who corrects a rejected transaction and how the customer learns about it.
Escalate unknown or undocumented customer reliance before control objectives are set.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Align objectives to the financial processes. Assign owners, define evidence and document complementary user entity controls.
Approved process narratives, customer risk scenarios and current manual and automated controls.
A daily reconciliation control links expected file totals to processed totals, explains differences and records reviewer approval.
Raise reports that users rely on when nobody can explain how totals were generated or validated.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Preserve transaction populations, exception handling and approvals. Support walkthroughs and tests over the agreed period when applicable.
Evidence request list, defined Type 2 period when relevant, operational logs, job runs and issue tickets.
A sampled broken interface includes the failure log, correction, rerun totals, approval and customer communication when applicable.
Escalate missing populations, unreviewed overrides and issues that could affect a customer’s close.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Reconcile findings, sign required representations and deliver the restricted-use report to entitled recipients.
Final system description, exception analysis, management assertion draft and engagement terms.
The approved delivery record captures report version, recipient and access date.
Bring unresolved exception language or unapproved recipients to management before release.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
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)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)