BusinessSAP

SAP S/4HANA Finance Access Controls: 10 SoD Checks for Financial Controllers

A practical controller’s guide to SAP S/4HANA Finance access governance, segregation of duties, role design, privileged access, user lifecycle controls and audit-ready evidence.

SAP S/4HANA can enforce detailed permissions, but a technically valid role design does not automatically create a sound finance control environment. A user may accumulate access through several roles, retain permissions after changing jobs, or receive a broad template role that exposes functions well beyond the person’s daily responsibilities. In finance, those combinations can enable unauthorized journal postings, changes to accounting master data, payment processing, or manipulation of reporting outputs.

The controller does not need to configure every authorization object. The controller does need to define the finance risks, approve the business access model, challenge conflicts, and ensure that evidence shows controls are operating. This guide sets out ten practical checks for SAP S/4HANA Finance teams. Exact apps, role concepts and configuration steps vary by deployment model and release.

1. Start with finance processes and risk scenarios

Build the access-control design from the processes that affect financial reporting and the assets the company needs to protect. Map who can initiate, change, approve, post, release, reconcile and monitor each critical activity. Include the general ledger, accounts payable, accounts receivable, fixed assets, inventory, treasury, cost accounting, consolidation and period-end reporting.

For each process, ask what could go wrong if one person had too much access. Examples include creating a supplier and changing its bank details before a payment run; entering and approving the same journal; changing account determination and posting the resulting transactions; or maintaining a financial reporting rule and approving the output without independent review.

Use a risk-based approach rather than trying to document every possible permission combination. The SEC’s Release 33-8810, issued June 20, 2007 and effective June 27, 2007, describes a top-down, risk-based approach to management’s ICFR evaluation. COSO’s Internal Control—Integrated Framework, refreshed in 2013, provides a broader structure for control environment, risk assessment, control activities, information and communication, and monitoring.

2. Design roles around real jobs, not individual requests

Define role families around stable job responsibilities such as GL accountant, AP processor, AP approver, fixed-asset accountant, cost accountant, financial reporting analyst and finance systems administrator. Document the business purpose, permitted activities, organizational scope, owner and approver for each role.

A role should grant only the access required for its defined tasks. Avoid building a special role for every employee or granting broad access because it is faster during onboarding. Where duties legitimately overlap in a small finance team, identify the residual risk and design a compensating review rather than pretending the conflict does not exist.

3. Tailor SAP-delivered roles before production use

SAP’s S/4HANA Cloud Public Edition authorization model uses business catalogs, IAM apps, business roles and restrictions to assemble and scope user permissions. SAP cautions that assigning standard business-role templates directly in production can grant unnecessary apps and critical or overlapping authorizations. Use templates as design inputs, then tailor roles to the organization’s actual workplaces and processes.

SAP is also introducing an IAM role concept in Cloud Public Edition, with business roles supported during the transition. For on-premise S/4HANA, role administration commonly uses PFCG roles and authorization profiles. Do not assume that a procedure or role template for one edition applies unchanged to another. Refer to the release-specific SAP Cloud authorization model, authorization concept, and the on-premise Managing Users, Roles and Authorizations documentation.

4. Maintain a finance segregation-of-duties matrix

Define incompatible activities by process and risk. A practical starting matrix might include:

Process Access combination to assess Risk
Accounts payable Maintain supplier payment data + enter invoices + release payments Fraudulent or diverted payments
General ledger Create or change journals + independently approve or post them Unauthorized or unsupported entries
Financial master data Change G/L or account-determination settings + post transactions affected by the change Misclassification or concealment
Fixed assets Create or change asset master data + approve acquisitions, transfers or disposals Unauthorized capitalization or disposal
Banking Prepare payment files + release the files or alter bank signatories Unauthorized cash movement

Adapt the matrix to the actual SAP functions, workflows, interfaces and approval limits in use. A conflict is a risk indicator, not proof of misconduct; a clean report is not proof that the role design is complete. Validate the rule set against the business process and update it when workflows or system functionality change.

5. Restrict access by company code and organizational scope

Functional access is only half the design. A GL accountant may need posting rights but only for assigned company codes; a plant accountant may need access limited to specified plants; a purchasing role may be limited by purchasing organization. SAP Cloud documentation describes restrictions on organizational values such as company code, plant and sales organization.

For a multi-entity group, test whether users can view or change data across entities beyond their responsibilities. Consider shared service centers, regional finance teams, acquisitions and temporary project assignments. Review the effective access after all roles are combined, not just each role in isolation.

6. Control privileged and emergency access

Identify administrators, security teams, developers, integration owners and users with broad posting or configuration rights. Keep privileged accounts separate from ordinary daily-use accounts where the architecture supports it. Limit assignment to named individuals, document the business need, and require independent approval.

Emergency access should be time-bound, activated only for a documented incident or approved task, and logged. A reviewer independent of the user should inspect the activity promptly, confirm that the actions were appropriate, and follow up on any configuration or financial postings. Do not treat a generic shared administrator ID as a compensating control.

7. Integrate joiner, mover and leaver controls with HR events

Access should change when employment or job responsibilities change—not weeks later when someone notices an old role. Establish a documented feed or notification from HR to the SAP access administrator for new hires, transfers, leaves, terminations and contractor end dates.

For each event, define who requests access, who approves it, who provisions it and who confirms completion. A transfer should trigger removal of incompatible prior roles as well as assignment of new ones. Termination controls should include disabling access promptly and addressing connected identity, remote access and privileged credentials under the organization’s security procedures.

8. Govern role changes, transports and emergency configuration

Changes to roles, catalogs, IAM apps, authorization values, restrictions and user assignments can alter financial control design. Require a ticket or change record, business owner approval, technical review, testing and production deployment evidence. Separate development from production administration where feasible.

For on-premise environments, SAP documentation explains that PFCG role authorization profiles must be generated after relevant authorization changes before the updated profile is assigned and used. For Cloud Public Edition, use the role and transport lifecycle applicable to the release. In both cases, retain before-and-after evidence and verify the effective permissions after deployment.

9. Include interfaces, bots and technical users

Finance transactions often arrive through bank interfaces, procurement platforms, expense tools, payroll systems, data loads and automation. Inventory each technical user or service identity, its owner, connected system, permitted actions, credential or certificate management, and business purpose.

Grant only the interfaces and actions required. Prevent technical identities from becoming convenient shared human accounts. Review inactive or obsolete connections, restrict changes to interface configuration, monitor failed and unusual processing, and reconcile interface totals to source and target records. Where a service provider operates part of the process, understand which access controls the provider operates and which controls remain the company’s responsibility.

10. Recertify access and monitor exceptions

Run periodic access reviews at a frequency aligned to risk. Finance owners should confirm that users still need each role, that organizational restrictions remain appropriate, and that conflicts are either removed or formally mitigated. Include dormant users, contractors, privileged users, emergency IDs, technical accounts and users with access across multiple entities.

Monitor changes and exceptions between formal reviews. Useful indicators include new privileged assignments, role changes near period-end, emergency access use, failed authorization checks, terminated users still enabled, unresolved SoD conflicts and unusual posting activity. Escalate overdue reviews and require evidence of remediation rather than relying on an email saying “reviewed.”

How to evidence the control for audit

Keep a coherent evidence pack: approved role catalogue, finance SoD matrix, risk analysis results, role-owner approvals, user access extracts, joiner/mover/leaver tickets, privileged-access logs, change records, recertification sign-offs, exception approvals and proof of remediation. Evidence should identify the population reviewed, review date, reviewer, exceptions found and how each exception was resolved.

For US issuers subject to SOX, the SEC management guidance and the applicable ICFR framework are relevant to management’s evaluation; PCAOB AS 2201 addresses the auditor’s integrated ICFR audit. The PCAOB page states that amendments to paragraph .09 and new paragraph .99 are scheduled to become effective December 15, 2026; as of November 15, 2026, that date is still in the future. Canadian reporting issuers should consider National Instrument 52-109; the Alberta Securities Commission lists its consolidated version as amended September 19, 2025. NI 52-109 certification requirements are not interchangeable with US SOX requirements, and applicability and exemptions should be assessed for the issuer.

Controller’s SAP finance access checklist

  • Finance processes, risks and role owners are documented.
  • Roles reflect actual job duties and are tailored before production assignment.
  • SoD conflicts cover high-risk create, change, approve, post and release combinations.
  • Company-code and other organizational restrictions are tested across combined roles.
  • Privileged and emergency access is limited, logged and independently reviewed.
  • HR events trigger timely provisioning, modification and deactivation.
  • Role and authorization changes are approved, tested and traceable.
  • Interfaces and technical users have named owners and least-privilege access.
  • Access recertification includes users, roles, conflicts, service accounts and exceptions.
  • Audit evidence demonstrates the population, review, decisions and remediation.

Conclusion

Effective SAP finance access control is a business control, not simply an IT administration task. Controllers should own the finance risk scenarios, define incompatible duties, approve the business role model and challenge exceptions. When access is designed around real responsibilities, restricted to the right entities, changed promptly and reviewed with evidence, the organization strengthens financial reporting integrity without making routine work unnecessarily difficult.

Informational only: this article provides general control guidance, not a legal or audit opinion. Confirm requirements against the organization’s SAP edition and release, applicable securities rules, control framework and system configuration.

Sources and further reading

Shares: