Access Rights and Segregation of Duties in Your ERP
In many ERPs, a handful of users can do almost everything. That is convenient until something goes wrong. Segregation of duties is how you keep control without slowing the business down.

When a new ERP (enterprise resource planning) system goes live, the pressure is to get people working. Users report that they cannot post an invoice or approve an order, and the quickest fix is to give them more rights. A year later, several people can create suppliers, raise purchase orders, approve them and release payments, all on their own. Nobody planned it. It just accumulated.
What segregation of duties means in practice
Segregation of duties is a simple idea: no single person should be able to carry out every step of a sensitive transaction alone. Splitting key steps between people means that errors are more likely to be caught, and that fraud would require two people to cooperate rather than one acting quietly.
Segregation does not imply distrust of individual employees. Most problems that segregation prevents are honest mistakes: a duplicate supplier, a payment to the wrong account, a price entered with an extra zero. A second person in the chain catches these. It also protects staff, because a well-designed control means nobody can be suspected of something the system would not have allowed them to do alone.
The duty combinations that matter most
Not every combination of rights is risky. Focus on the ones where one person could create a transaction and also approve, pay or hide it. The table below lists the conflicts most organisations should look at first.
| Duties held by the same person | What could go wrong |
|---|---|
| Create or edit suppliers, and release payments | Payments to a fake or altered supplier account, including changed bank details |
| Raise purchase orders, and approve them | Purchases outside policy, from preferred suppliers or at inflated prices |
| Record goods received, and approve supplier invoices | Paying for goods that never arrived in full |
| Create customers or credit limits, and approve sales orders | Sales to risky customers beyond what finance would accept |
| Issue credit notes, and receive customer payments | Payments diverted and covered by unjustified credit notes |
| Post journal entries, and approve or review them | Errors or adjustments in the ledger that nobody else sees |
| Adjust stock, and count stock | Losses hidden through adjustments |
| Manage user accounts, and process transactions | Granting oneself any of the above rights |
Supplier master data deserves extra attention. A change to a supplier’s bank account details is a common route for payment fraud, including through emails impersonating a real supplier. Changes to bank details should always need a second person to approve, and ideally a call back to the supplier on a number you already hold.
Designing roles instead of granting rights one by one
Most access problems start with rights being granted to individuals, one request at a time. The cleaner approach is to define roles based on jobs, such as purchasing officer, storekeeper, accounts payable clerk or finance manager, and assign each role a set of rights. People then receive roles, not individual permissions.
Modern ERP systems, including Odoo, SAP Business One and Microsoft Dynamics, all support role-based access in some form, though the level of detail varies. Good role design follows a few principles:
- Least privilege. Each role has the rights needed for the job and no more. Read access to a report is different from the right to change the data behind it.
- Conflicts checked at design time. Before a role is approved, check it against the conflict list above. A role that combines conflicting duties should be split.
- Named accounts only. Shared logins such as “warehouse” or “accounts” make it impossible to know who did what. Every user has their own account.
- Few administrators. System administrator rights belong to a very small number of people, ideally not people who also process daily transactions, and their activity should be logged.
- Owned by the business. IT sets up the roles, but a business owner, usually finance, approves what each role can do and who receives it.
What smaller teams can do when full separation is impossible
In a company with a finance team of three, perfect segregation is often impossible. Someone has to cover when a colleague is away, and there may simply not be enough people to split every duty. That is a normal situation, and there are sensible ways to manage it.
A family-owned food manufacturer near Amman, with a chief accountant, one accounts assistant and a part-time cashier, is a typical case. The chief accountant needs broad rights. Instead of pretending the duties are separated, the company introduces compensating controls: the owner reviews a weekly system report of new suppliers, changed bank details and payments above a set amount; bank payments above a threshold need a second signatory in the banking portal; and the external accountant reviews manual journals each quarter.
Compensating controls like these work when they are regular, documented and done by someone independent of the transactions. A review that happens only when someone remembers is not a control.
Keeping access under control after go-live
Access rights decay over time unless someone looks after them. A short routine keeps them in shape:
- Joiners: new users receive a standard role based on their job, approved by their manager and the role owner.
- Movers: when someone changes job, their old role is removed when the new one is added. Movers often collect rights from every job they have held.
- Leavers: accounts are disabled on the last working day, triggered by HR (human resources), not by IT happening to notice.
- Quarterly or half-yearly review: each department head receives a list of their team’s access and confirms it is still correct.
- Annual conflict check: run the conflict list against current users and roles, and resolve or document anything found.
Your external auditors will usually ask about user access and segregation as part of their work. Having roles, reviews and compensating controls documented makes that conversation short and straightforward.
Control that fits the way you work
Good access design protects the business, protects staff and gives management confidence in the numbers, without forcing every transaction through unnecessary approvals. It is easiest to design before go-live, but an existing system can be reviewed and corrected at any point.
Our Enterprise Systems service includes reviewing and redesigning ERP roles, mapping them to real jobs and putting the review routines in place. Because access rights follow ownership, this work often goes hand in hand with the role clarity part of our Operations Transformation service.



