Considerations When You Create Accounts

Banks, branches and accounts fit together on the premise of the Bank Account model. The Bank Account model enables you to define and keep track of all bank accounts in one place.

The Bank Account Model can explicitly grant account access to multiple business units, functions, and users. Consider the following when you set up bank accounts:

• Assign a unique general ledger cash account to each account, and use it to record all cash transactions for the account. This facilitates book to bank reconciliation.

• Grant bank account security. Bank account security consists of bank account use security, bank account access security, and user and role security.

Legal Entity-Based Data Access for Bank Account Setup

By default, users with the necessary function security privileges have access to create and manage all internal bank accounts.

Optionally, restrict access to bank account information based on the user's legal entity data access. This allows cash managers to add, review, or modify only the bank accounts associated with the legal entities that the user has access to. For example, only users who have been assigned a cash manager role for Vision Operations legal entity, will be able to create, review, or modify internal bank accounts associated to this legal entity.

Decentralized organizations will benefit with improved security by ensuring that users only manage the bank account setup for the organizations they are authorized for.

Business benefits include:

• Improve security and increase control of bank account setup by limiting user access to bank account information.
• Helps decentralized organizations that require users only to manage the bank account information for the organizations they are authorized for.

To enable the feature Legal Entity-Based Data Access for Bank Account Setup, you must:

1. Use the Opt in UI to enable the feature.
2. Assign users to the appropriate legal entity security context:
   1. In the Setup and Maintenance work area, Select the Offering as Financials, Functional Area as Users and Security, and Task as Manage Data Access for Users.
   2. On the Manage Data Access for Users page, create data access for users by entering the user name, Cash Manager as role, legal entity as security context, and legal entity name as security context value, to create the data access for the user.
   3. Save the changes.

Once the feature is enabled, legal entity-based data access security is applied when an internal bank account is created or managed using either the UI or REST API.

Account Use

Account Use refers to accounts created for:

• Oracle Fusion Payables

• Oracle Fusion Receivables

• Oracle Fusion Payroll

Select the appropriate use or uses when creating an account in one or more of these applications.

Account Access

Payables and Receivables account access is secured by business unit. Before the bank account is ready for use by Payables or Receivables, you must:

1. Select the appropriate use for the application.

2. Grant access to one or more business units.

Note: You can only assign access to the business units that use the same ledger as the bank accounts owning the legal entity,

User and Role Security

You can further secure the bank account so that it can only be used by certain users and roles. The default value for secure bank account by users and roles is No. For Payables and Receivables, you must have the proper business unit assigned to access a bank account even if the secure bank account by users and roles is No. If the secure bank account by users and roles is set to Yes, you must be named or carry a role assigned to the bank account to use it.

• You must assign the security duty role Cash Management Administration to the Cash Manager job role to provide access for setting up banks, branches, and accounts. You must have the assigned Manage Bank Account Security privilege (CE_MANAGE_BANK_ACCOUNT_SECURITY_PRIV) to modify the User and Role Security.

• If you want to restrict the access to the Security tab, you must create a customized role and remove the privilege Manage Bank Account Security (CE_MANAGE_BANK_ACCOUNT_SECURITY_PRIV). For example, you would copy the Cash Management Administration duty role, rename it, and remove the privilege.

GL Cash Account Segments

Consider selecting the option to enable multiple cash account combinations for reconciliation if you want to reconcile journal lines of multiple cash account combinations matching the same natural account and other specified segment values.

For example, if you set up 01-000-1110-0000-000 as your cash account, and select Account and Sub-Account as GL Cash Account Segments, you're able to manually or automatically reconcile journal lines entered on different account code combinations matching the same natural account '1110' and sub-account '0000'.