Policies
A Policy defines which payout-related actions must be validated before they become final. In other words, when someone creates, updates, or deletes a payout setup item, the system checks the Policy first. If the Policy is active, it triggers the related Workflow so the action goes through approval steps.
You can configure policies for different elements, including:
Beneficiary
Beneficiary Account
Execution Day
Execution Mode
Execution Time Slot
Payout
Each policy can trigger a workflow process. This means that when a policy is matched (for example, when a beneficiary account is updated), the related workflow will start to ensure the action is validated and approved before continuing.
Validation
Every change is validated according to your business requirements.
Approval
Sensitive operations (like updating accounts or execution rules) go through approval steps.
Consistency
Payouts follow a consistent and secure process.
Navigate to Policies Configuration And Workflow
Go to Setup → Policies and workflow → Click on +Create Policy.
Fill the below information
Policy section
Name
The title of the policy.
Description
A short explanation of what this policy does.
Setup section
Operations
The action that will trigger this policy. Create, Update, or Delete.
Policy
This dropdown lists the available policy classes (for example, Create Policy, Update Policy, Delete Policy). Pick the one that matches the operation you want to control, and Ottu will use its built-in logic to decide whether that operation requires approval
Resource
Select the payout area that this policy will control. The list shows all available resources in the system (auto-populated), and you choose the one you want to apply the policy to, such as Beneficiary, Beneficiary Account, Execution Rules/Schedule, or Payout.
Is active
Controls whether the policy is enforced immediately. Turn ON to apply it now, or keep OFF to save it without enforcing.
Saving the Policy
Save the created Policy
Last updated