Services · Streamline & Outsource

Segregation of duties (SoD) audit

Find access conflicts before they create unnecessary risk. A segregation of duties audit compares actual user and role permissions with your approved conflict matrix, then ranks each issue by severity. Every finding includes supporting evidence and a practical recommendation for remediation or a compensating control.

Conflicts, evidencedMatrix-screened, ranked
The problem

Access risk often comes from the combination of permissions

Creating a supplier and approving its payment, preparing a journal and posting it, or changing a price and issuing a credit are all valid tasks. The risk appears when one person can complete both sides of the same process without independent review. A segregation of duties audit compares your conflict matrix with the permissions actually assigned to roles and users. It identifies risky combinations and gives your control owners clear findings they can review and act on.

What we run

How we audit segregation of duties in NetSuite

Senior consultants oversee the work, and you can see progress as it happens. Approvals and decisions stay with your team.

  • Conflict matrix setupYour existing rules are reviewed and confirmed before testing begins. If no matrix exists, one is developed with your finance team using recognised conflict categories, creating a clear standard for the audit.
  • Permission-truth extractionEffective access is assembled at user level, with roles, global permissions and overlaps resolved, assisted by SuiteQL where the UI does not show the answer.
  • Permission combination screeningThe conflict matrix is compared with the access users actually hold. Each finding identifies the conflicting permissions, the affected roles or users and the supporting evidence.
  • Risk-based prioritisationEach finding is ranked according to the exposure it creates. Active access that could affect payments or financial records takes priority over conflicts that exist only within an unused role, directing attention to the risks that matter most.
  • Remediation and compensating controlsWhere practical, conflicts are removed by redesigning roles or permissions. If the business requires someone to retain conflicting access, an appropriate compensating control is agreed and documented. Both outcomes are recorded clearly for future review and audit.
  • Ongoing access screeningPermission checks run on an agreed schedule and whenever roles change, helping to identify new conflicts before the next formal audit.

One person able to run the whole cycle?

We audit segregation of duties and map the conflicts with their fixes. Talk it through with a senior consultant. It’s free, it takes 30 minutes and there’s no sales pitch.

The payoff

What handing it over buys you

Conflicting access is clearly identified

The screening highlights combinations such as creating a supplier and approving its payment, then shows exactly which users hold both permissions.

Findings rank by real exposure

Weighted results fix the live conflict before the theoretical one is debated.

Small-team reality gets governed

Documented compensating controls keep the unavoidable conflict watched instead of ignored.

Auditors meet a running control

Recurring screens with evidence answer the SoD question before it is asked.

How handover works

From hidden combinations to a running screen

  1. Confirm the conflict matrix – Existing rules are reviewed and agreed. If no matrix exists, one is developed with your team during a structured workshop.

  2. Extract & screen – effective permissions are run against the matrix.

  3. Rank & route – findings go to owners with remediation options attached.

  4. Recur – the screen runs on calendar, so drift is caught early.

Good to know

What to know before you hand it over

  • !Your finance team defines the conflict rules. Finance and audit stakeholders decide which permission combinations create unacceptable risk. Once approved, those rules form the standard used for every access screening.
  • !Small teams may need compensating controls. Limited headcount can make complete separation of duties impractical. In those cases, a clear review or approval control is documented to manage the risk, rather than creating an artificial role split that does not reflect how the work is actually done.
  • !The audit examines each user’s effective access. Global permissions and multiple assigned roles can create access that is not obvious from a single role. The screening combines these layers to show what each user can actually do, with the method clearly documented so every finding can be verified.
Straight answers

Segregation of Duties (SoD) Audit FAQs

Which permission conflicts appear most often?
The most common risks arise when one user can initiate and complete the same financial process. This might mean creating suppliers and approving their payments, preparing and approving journals, changing prices and issuing credits, or recording receipts and reconciling the account. The workshop uses these recognised conflict groups as a starting point, then adapts them to your business.
What if a conflict can’t be removed?
A compensating control is put in place: a documented, evidenced review over the risky activity, designed with your owner and filed for the auditor.
Do we need an existing segregation of duties matrix?
No. If you already have one, it’s reviewed and confirmed before the audit begins. If you don’t, it’s created with your finance team during the initial workshop. The discussion starts with common conflict areas, such as creating suppliers and approving payments, preparing and approving journals, or changing prices and issuing credits. These rules are then tailored to your roles, processes and approval structure, giving the audit a clear standard to test against.
Is this only relevant for SOX businesses?
No. SOX businesses often need formal segregation-of-duties testing, and UK subsidiaries of US-listed groups may inherit those requirements. But the underlying risks don’t depend on listing status. Private companies face the same exposure when one person can create a supplier and approve its payment, for example. For organisations within SOX scope, the audit can provide useful control evidence. For everyone else, it’s a practical way to reduce fraud risk and show that access is being governed properly.
How often should segregation-of-duties screening run?
Quarterly screening is common, with an additional check whenever a significant role or permission change is made. This helps identify new conflicts early, while they can still be traced to a recent change.

Last reviewed: 9 November 2026 · Written by the Suite Generation team

Ready to hand this one over?

Tell us your user counts and the problems you are seeing, and we will scope the parallel run.

Scoping Call — Sitewide

We reply within 24 hours.

or email hello@suitegeneration.net

Suite Generation is an independent, senior-led NetSuite consultancy. Every project is designed and delivered by consultants at or close to solution-architect level. We don’t resell licences or carry partner targets. Our advice is ours, whether you’re implementing NetSuite, rescuing a stalled project or fixing a system that never delivered.

Independent – no licence resellingSenior-led – solution-architect levelTrusted to fix failed implementations
Talk to a solution architect