Segregation of Duties Coming soon
No one person should hold the whole cycle.
Most internal losses are not hacks — they happen because one person could request, approve and pay. seg-audit builds the SoD matrix from your actual system permissions and names who holds conflicting duties.
Reports in this section
Who holds two permissions that should never sit with one person?
- Each user’s system permissions
- The standard conflict matrix
- Assigned functional roles
A matrix showing every live conflict by name and permission, ranked by severity.
Owner — the fastest page for spotting where the risk sits.
Can one employee raise a purchase, approve it, and pay for it?
- Purchase order creation and approval rights
- Supplier bill entry rights
- Payment execution rights
A list of users holding all or most of the chain, with the value of transactions they touched.
Owner — the single most dangerous and costly conflict.
Is the person who sells also the one granting discounts, credit limits and write-offs?
- Sales order and pricing rights
- Discount and credit limit rights
- Credit note issuance rights
A list of sales-cycle conflicts, with discount and credit-note value issued by each user.
Owner and sales director — protecting revenue from silent erosion.
Is the person receiving goods also the one counting them and clearing the variance?
- Warehouse receipt and issue rights
- Stock count and variance adjustment rights
- Item master edit rights
A list of who can hide a stock shortfall with an adjustment they sign themselves.
Owner and operations — a shortfall cleared internally never surfaces.
Who was granted an exception, who approved it, and is it still live?
- Permissions granted outside the assigned role
- Grant date and duration
- Actual activity under the exception
A list of live exceptions, whether they were actually used, and whether they should be revoked.
Owner — a forgotten temporary exception becomes a permanent hole.