@Huma Selot CU200816...
to satisfy SOX ITGC logical access requirements this is a genuine SoD conflict ,the user entering sales orders must not be able to override credit limits or release credit holds. Here is the exact configuration to isolate these permissions:
Step 1 — Strip credit override privileges from the Order Processor role
Navigate to System administration > Security > Security configuration — locate your Order Processor role , expand duties and privileges , remove any privilege that allows releasing credit holds, overriding credit limits, or modifying customer master credit limit fields (CreditMax). Do not leave these in the role even with read access.
Step 2 — Assign credit release privileges to a segregated role only
If using D365 Credit Management .Credit and collections > Credit management setup ,the ability to release orders from the credit holds workspace must sit exclusively in a separate Credit Manager or Collections Manager role. No overlap with order entry roles.
Step 3 — Restrict Customer Master credit limit field
Ensure the Order Processor's privileges do not grant write access to the CreditMax field on CustTable. Use field-level permissions or a separate privilege structure in Visual Studio to restrict CreditMax modification to Finance Controllers only — order processors get Read or No Access on financial exposure fields.
Step 4 — Validate for auditors
Run a test with an Order Processor user against a customer over credit limit — attempt a manual override. The system must throw a security exception or grey out the release action entirely forcing the transaction into the Credit Management hold queue for an independent reviewer.
Document this test with screenshots ,it is your audit evidence that the SoD control is operating effectively.
If it helps , Mark verify
