Oracle Cloud 25B: Enabling Approvals for Employee External Bank Account Creation and Modification
Introduction
A long-standing control gap in Oracle HCM and Payroll has been the lack of approval workflows for employee bank account changes. Organizations have consistently raised concerns about allowing employees to create or modify external bank accounts without validation or oversight.
With Oracle Cloud 25B, Oracle has introduced the ability to enforce approvals specifically for Employee External Bank Account creation and modification, adding a critical governance layer to payroll processing.
Business Context
Employee external bank accounts directly impact salary disbursement. Any incorrect or unauthorized change can lead to:
- Payments being routed to incorrect accounts
- Payroll failures and rework
- Increased risk of fraud
- Compliance and audit challenges
This enhancement introduces a structured approval mechanism to mitigate these risks within the application itself.
What’s Delivered in 25B
The solution is built using three core components:
- Feature Opt-In for Payments
- Controlled Lookup Enablement
- Spreadsheet-Based Approval Rules
This functionality applies specifically to:
- Creation of external bank accounts
- Modification of external bank accounts
Step 1: Enable Feature Opt-In
Navigate to:
Setup and Maintenance > Financials > Payments > Edit Features
Enable:
Employee Bank Account Ownership Verification Workflow
This step activates the underlying approval framework.
Step 2: Enable Controlled Lookup
Navigate to:
Setup and Maintenance > Manage Standard Lookups
Search for:
ORA_ERP_CONTROLLED_CONFIG
Enable the following lookup:
- Lookup Code: IBY_37070344
- Meaning: Enable Bank Account Approval
- Status: Enabled
This lookup acts as the trigger for approval processing.
Step 3: Configure Approval Rules
Navigate to:
Manage User-Defined Rules for Employee Bank Account Approvals
Download:
ExternalBankAccountApprovalRulesTemplate.xlsm
Important
Ensure the following privilege is assigned:
IBY_MANAGE_BANK_ACCOUNT_APPROVALS_PRIV
Without this privilege, users will not be able to configure approval rules using the task Manage User-Defined Rules for Employee Bank Account Approvals.
Step 4: Define Approval Logic
Approval rules are defined using the Excel template.
In this implementation example, a two-level approval was configured:
- Account Owner approval using username
- Approval by users with the role KP_PAYROLL_ADMIN_VIEW_ALL_DATA
If multiple users have this role, any one of them can approve the notification.
After defining the rules in Excel:
- Click Generate Rule File
- A ZIP file will be generated
- Upload the ZIP file back into Manage User-Defined Rules for Employee Bank Account Approvals
End-to-End Flow
- Employee creates or updates an external bank account
- System evaluates feature opt-in and lookup configuration
- Approval rules are applied
- Request is routed to approver or approvers
- Upon approval, the bank account is created or updated
Basic Testing of Configuration
After completing the setup, perform a simple validation to confirm the configuration is working.
Test Steps
- Login as an employee
- Navigate to Me > Pay > Payment Methods
- Add a new external bank account or update an existing one
- Submit the transaction
Expected Result
- The change should not be applied immediately
- An approval request should be triggered
- The request should appear in the approver’s worklist or notifications
Approval Validation
- Login as the approver
- Open the approval notification
- Approve the request
Result: The bank account should be successfully created or updated.
What This Confirms
- Feature opt-in is enabled correctly
- Lookup configuration is active
- Approval rules are functioning
- Workflow routing is working as expected
Key Observations
Scope of Approval
This feature applies only to:
- External bank account creation
- External bank account modification
It does not apply to other payment method configurations such as allocation or percentage splits.
Configuration Model
This feature is not configured like standard HCM approval transactions.
It does not use:
- Transaction Design Studio
- Standard BPM rule configuration
Instead, it relies on:
- Feature opt-in
- Controlled lookup
- Spreadsheet-based rule definition
Implementation Considerations
Payroll Timing
Bank account changes are applied only after approval. Approval timelines must align with payroll processing cutoffs to avoid delays.
Limitations and Considerations
While this feature addresses a critical control gap, there are important limitations to consider.
Limited Rule Authoring Model
Approval rules are defined using a spreadsheet template rather than the standard BPM rule UI.
This results in:
- Static, template-driven rules
- Limited flexibility compared to dynamic BPM configurations
- No support for advanced conditional expressions
No Support for AOR-Based Routing
Unlike other HCM approvals, this feature does not support routing based on Areas of Responsibility (AOR).
This means:
- Approval cannot dynamically route based on HR or payroll responsibility
- Routing must be predefined in the template
Limited Support for Complex Approval Scenarios
Compared to other HCM transactions, the following are not supported:
- Dynamic multi-stage approvals
- Parallel approval flows
- Rule chaining or advanced escalation logic
Approval flows are generally linear.
Dependency on Template Maintenance
Since rules are managed through a spreadsheet:
- Any change requires re-download and re-upload
- Version control must be managed externally
- There is a higher risk of manual errors
Limited Debugging Capability
Troubleshooting approval issues is less intuitive due to:
- Lack of visual rule builder
- Limited runtime diagnostics
- Errors often identified only during upload or execution
Practical Recommendations
- Start with simple approval rules, such as manager-based or payroll-admin-based routing
- Avoid overly complex logic
- Maintain proper documentation of rule logic
- Establish governance for template updates
- Validate the approval flow before enabling in production
Compliance and Audit
This feature strengthens:
- Audit traceability
- Internal controls
- Fraud prevention
User Communication
Employees should be informed that:
- Bank account changes require approval
- Changes are not immediate
- Approval must be completed before the change becomes effective
Conclusion
Oracle Cloud 25B introduces an essential control for managing employee external bank account changes.
By combining feature enablement, controlled configuration, and approval rules, organizations can significantly improve governance over payroll-critical data.
This is a practical enhancement that should be enabled and validated as part of any payroll implementation.
