Separation of duties (SoD) means no single person should be able to complete every step of a financial process on their own. When one person holds two roles that together let them start and finish the same transaction, there is a risk of fraud or error that nobody would catch. SoD controls prevent that by keeping incompatible roles with different people.
A simple example
If one person can enter a supplier invoice and create the payment for it, they could pay an invoice that should never have been approved. Splitting those two steps between two people means each step is checked by someone else.
Step 1
Enter the supplier invoice
Person A
Step 2
Create the payment
Person B
How SoD affects an access request
Conflicts are checked at the role level.
It does not matter which FRUs or projects the roles apply to. If a person holds, or is requesting, two roles that conflict, we flag it.
It applies across systems.
OFC, Jaggaer, Concur and TOE roles are all considered.
The request is paused, not denied.
We note the conflict on the ticket and ask which role the person should keep. We allow up to 3 business days for a reply before the request is closed.
Tip: Before you submit, compare the roles you plan to request, including any the person already has, against the lists below. If two roles conflict, decide which one the person needs most, or have a second person take on the other duty.
Common conflicts in Oracle Financial Cloud (OFC)
OFC checks combinations of functions grouped by business process. These are the kinds of pairings that cannot be held by the same person.
| Business process | Functions that cannot be combined | What could go wrong |
|---|---|---|
| Procure to Pay |
| A person could create a fictitious supplier, purchase or invoice and pay it. |
| Invoice to Cash |
| A person could inflate revenue, post into a closed period or hide a manipulated receipt. |
| Projects and Grants |
| A person could inflate asset values or project revenue. |
| Record to Report |
| A person could post unreviewed entries, change a closed period or manipulate the cash position. |
| Information Technology |
| A person could change configuration and then process transactions that rely on it. In practice, roles with "Setup" in the name and transactional roles are not combined without additional review. |
Jaggaer role combinations that cannot be held together
Jaggaer conflicts are listed in the Gateway Roles Matrix (Google Sheet, opens in a new tab). In summary:
| Jaggaer role | Cannot be combined with |
|---|---|
| Requestor |
|
| Department Analyst |
|
| FRU Approver (LV1 to LV4) |
|
| Allocator |
|
| Department Invoice Approver |
|
| Department Flexcard Administrator |
|
| Flexcard Holder |
|
| Project Analyst |
|
| Project Manager |
|
| Advanced Shopper | Any other Jaggaer role |
The Flexcard Holder combinations matter most because they would let a person approve their own FlexCard purchases.