This chapter covers the following topics:
Bank account transfers represent fund transfers between internal bank accounts. You can create bank account transfers manually or automatically through Cash Leveling process (see Cash Positioning section for more details) and/or Sweep Transactions Generation concurrent program. The access to bank account transfer creation for a particular legal entity is subject to bank account use security. The bank account transfers are reflected in Cash Position automatically. Payment processing for bank account transfers is managed using Oracle Payments. Journal entries are created through a centralized subledger accounting engine.
The following bank account transfers are supported from the point of view of bank account ownership:
Intra-Company Transfers
Intra-company transfers represent cash transfers between two internal bank accounts that belong to the same legal entity.
Inter-Company Transfers
Inter-company transfers represent cash transfers between two internal bank accounts that belong to two different legal entities. In case of such transfers, the system can produce balanced journal entries for both legal entities.
The following bank account transfers are supported from the point of view of transfer currency:
Domestic
The currency of both bank accounts and the transfer amount is the same. For example, you are transferring USD between two bank accounts that are denominated in USD.
International
The currency of one bank account is the same as the currency of the transfer amount but the currency of the other bank account is different. For example, you are transferring USD from a bank account denominated in USD to the bank account denominated in EUR.
The following scenarios are not supported in Cash Management for Bank Account Transfers:
| Scenario | Functional Currency | Bank Account Currency | Transaction Currency |
|---|---|---|---|
| 1 | USD | CAD | EUR |
| 2 | USD | CAD | USD |
You can define Cash-In-Transit account by defining Intracompany Rule for same Debit And Credit BSV with same Debit and Credit account, for clearing of Bank Account Transfers within the same BSV.
A Sample Cash-In-Transit account for BSV 001 would be as below:
| Debit BSV | Credit BSV | Debit Account | Credit Account |
|---|---|---|---|
| 001 | 001 | 001.100.200.000 | 001.100.200.000 |
Similarly you can define cash-in-transit account for all the BSV's.
Note: You can create a cash-in-transit account only under the 'Cash Management' source and 'Bank Transfers(1)' category.
Payment templates allow defining reusable sets of bank account transfer attributes and payment processing options. During bank account transfer creation you have an option to select a payment template. If you do so, all the attributes of the payment template will default into the bank account transfer.
If you are using repetitive payment codes or repetitive wire codes, you can define those as payment templates.
Navigate to the Payment Templates page.
Click Create.
Enter payment template attributes on General Details and Payment Details tabs. Select attributes are explained below.
Repetitive Code: This parameter defines whether this is repetitive payment template or not. If the parameter is set to Yes, then the source and destination bank accounts will be required for the template creation. Furthermore, when you are creating a bank account transfer with this template, the source and destination bank accounts will default in and will not be updateable. If the parameter is set to No, then all the template attributes will be updateable after they default in during bank account transfer creation.
Authorize Transfer: This parameter defines whether the bank account transfer created using this template requires authorization before it can be processed for payment in Oracle Payments or not. If you select Yes, the bank account transfer has to be manually authorized before it can be paid. If you select No, the bank account transfer will be automatically authorized for payment as soon as it is created and validated.
Settle Transaction: This parameter defines whether the bank account transfer created using this template requires payment processing in Oracle Payments or not. If you select Yes, the bank account transfer will be routed for payment processing in Oracle Payments as soon as it is manually or automatically authorized. If you select No, the bank account transfer will not be routed for payment processing in Oracle Payments. Excluding bank account transfer from the payment processing may be useful when the payment instructions have been communicated to the bank outside of the system or if you are not using Oracle Payments but still want to account for such a transaction.
Source Bank Account: The bank account from which the transfer will be made.
Destination Bank Account: The bank account that will receive the transfer.
Payment Method: The method of payment.
Payment Reason: The reason for the payment.
Anticipated Value Date: This field indicates the number of clearing days between the transaction date and settlement date. If a value for anticipated value days exist in the payment method, this value will automatically default here. However, the default can be overwritten by the user.
Click Apply.
Navigate to the Payment Templates page.
Enter search parameters and click Go.
Select the payment template and click Update.
Update payment template attributes as necessary. If you want to disable the payment template and prevent the users from using it in the future, set the Status to Inactive.
Click Apply.
Navigate to the Bank Account Transfers page.
Click Create.
Enter bank account transfer properties. Please note that if you select a payment template, the bank account transfer attributes defined at the template level will default in automatically. Select attributes are explained below.
Settlement Transactions through Oracle Payments: This parameter defines whether the bank account transfer requires payment processing in Oracle Payments or not. If you select Yes, the bank account transfer will be routed for payment processing in Oracle Payments as soon as it is manually or automatically authorized. If you select No, the bank account transfer will not be routed for payment processing in Oracle Payments. Excluding bank account transfer from the payment processing may be useful when the payment instructions have been communicated to the bank outside of the system or if you are not using Oracle Payments but still want to account for such a transaction. .
Source Bank Account: The bank account from which the transfer will be made.
Destination Bank Account: The bank account that will receive the transfer.
Payment Method: The method of payment.
Payment Reason: The reason of payment.
Anticipated Value Date: This field indicates the anticipated date when the funds will reach the destination bank account. If you select a payment template, this field is populated as the Transfer Date plus the number of anticipated value days on the payment template. If you select a payment method, this field is populated as the Transfer Date plus the number of anticipated value days on the payment method. However, the default can be overwritten by the user.
Click Apply. The bank account transfer is saved with status New. If you would like to validate the bank account transfer at the same time as saving it, click Apply and Validate instead of Apply. Please note that the bank account transfer will be available for further processing (manual authorization, payment and journal creation) only after it has been validated.
| Manual Authorization Required? | Settlement through Oracle Payments Required? | Bank Account Transfer Status after Successful Validation | Bank Account Transfer Status after Manual Authorization Settlement in Process Settled |
| Yes | Yes | Validated | Settlement in process |
| Yes | No | Validated | Settled |
| No | Yes | Settlement in process | |
| No | No | Settled |
Navigate to the Bank Account Transfers page.
Enter search criteria and click Go.
Select a bank account transfer and click Validate. Please note that the Validate icon is enabled only for bank account transfers in status New or Invalid.
Navigate to the Bank Account Transfers page.
Enter search criteria and click Go.
The bank account transfer status can be one of the following:
New: The transfer has been created but not validated yet.
Validated: The transfer has been created and validated. It is ready to be manually authorized for settlement.
Invalid: The transfer has failed validation.
Rejected: The transfer is rejected by the user who is performing manual authorization.
Settlement in Process: The transfer has been authorized for settlement and sent to Oracle Payments.
Settled: The transfer was successfully processed by Oracle Payments or it did not require settlement through Oracle Payments.
Failed: The transfer failed processing in Oracle Payments.
Canceled: The transfer has been manually canceled by the user.
Navigate to the Bank Account Transfers page.
Enter search criteria and click Go.
Select bank account transfer and click Update.
Note: The Update icon is enabled only for bank account transfers in status New, Validated, Invalid, or Rejected.
Modify bank account transfer attributes.
Click Apply. The changes saved. If you would like to validate the bank account transfer at the same time as saving the changes, click Apply and Validate instead of Apply. If the validation is successful, the bank account transfer is saved with Validated status.
Navigate to the Bank Account Transfers page.
Enter search criteria and click Go.
Select bank account transfer and click Cancel. The Cancel icon is disabled for bank account transfers in status Settled if at least one underlying cash flow is cleared or reconciled
If a bank account transfer requires settlement through Oracle Payments and the status of the transfer is Settlement in Process or Settled, canceling the bank account transfer will not stop or reverse payment processing in Oracle Payments. The user will have to switch to Oracle Payments and manually stop the payment process or cancel the payment.
If you would like another user to approve the bank account transfer before it is processed for payment and/or journalized, you can set up the system parameter to required manual bank account transfer authorization. Bank account transfer authorization is a completely separate function from bank account transfer update.
Navigate to the Bank Account Transfer Authorization page.
The list of bank account transfers awaiting your authorization is displayed. This list is subject to bank account use security.
Select transfers and click Authorize Transfers. If it requires payment processing, it will now be automatically sent to Oracle Payments. If it does not require payment processing, it will now be available for journal creation.
If you would like to reject the transfer, click on Reject Transfers instead.
Bank account transfer payment instructions can be communicated to the bank electronically through Oracle Payments. When a bank account transfer that requires settlement is authorized in Oracle Cash Management, a payment process request is automatically created in Oracle Payments. For more details on payment instruction creation and bank communication, see: Understanding Funds Capture Bank Account Transfers, Oracle Payments User Guide.
If the payment is successfully processed in Oracle Payments, the status of the bank account transfer will be automatically set to Settled. If the payment is not successfully processed, the status of the bank account transfer will be automatically set to Failed and may require the user's intervention to recreate the transfer.
Bank account transfers can be posted to Oracle General Ledger through the centralized subledger accounting engine by running Create Accounting concurrent program. See the program description and Subledger Accounting section for more details.
Bank account transfers that require settlement in Oracle Payments are available for journal creation when their status is set to Settlement in Process. Bank account transfers that do not require settlement in Oracle Payments are available for journal creation when their status is set to Settled. This corresponds to Bank Account Transfer Created accounting event type in the Bank Account Transfers event class. Additional event types are created in the system when the bank account transfer is canceled or when the related cash flows are cleared or un-cleared.
You can use Cashflows window to view the detail of existing cashflows or to cancel the cashflows. Cashflows are available for clearing and reconciliation. Clearing cashflows will generate accounting entries through Subledger Accounting. See Subledger Accounting chapter in this document for more information. Cashflows also can be included in Cash Positioning as a positioning source.
Cashflows can be created from the following programs:
Manual Entry of Bank Account Transfers
Generate Sweep Transactions
Cash Leveling
Bank Statement Cashflows
Each cashflow is designed to produce a balanced journal, with a debit and credit journal entry. Cashflows are also used in clearing and reconciliation. Cashflows can be included in Cash Positioning as inflow and outflow sources.
Navigate to Cashflows window. From the navigator, choose Cash Transactions > Cashflows.
Enter the criteria for the cashflows you want to query and click Go
Cashflow Number: Unique cashflow identifier.
Transaction Type: The source transaction type of cashflow. There are two possible values:
Bank Account Transfer - if the cashflow is created from Manual Entry of Bank Account Transfers, Generate Sweep Transactions, or Cash Leveling program.
Statement Line - if the cashflow is created from Bank Statement Cashflows program.
Transaction Number: Bank Account Transfer number. If the cashflow is generated by Bank Statement Cashflow program, then this field is null.
Transaction Subtype: Transaction subtype that is assigned to the cashflow.
Bank Account: Cashflow bank account number.
Counterparty Bank Account: Counterparty bank account number. This field is null for cashflows generated from the Bank Statement Cashflows program.
Direction: Inflow or Outflow.
For the cashflows with Bank Account Transfer transaction type, inflow means that the counterparty bank account is funding bank account whereas the cashflow bank account is beneficiary bank account. On the other hand, outflow means that the cashflow bank account is funding bank account whereas the counterparty bank account is beneficiary bank account. For the cashflows with Statement Line transaction type, inflow means that the cashflow bank account is beneficiary bank account that receives fund from the GL account specified in Bank Statement Cashflow Mapping. On the other hand, outflow means that the cashflow bank account is funding bank account that sends fund to the GL account specified in Bank Statement Cashflow Mapping.
Amount: Cashflow amount.
Currency: Cashflow currency code.
Cashflow Date: Date that the cashflow is created.
Status: Cashflow status. There are four possible values:
Created - when Cashflow is newly created.
Canceled - when Cashflow is canceled.
Cleared - when Cashflow is cleared.
Reconciled - when Cashflow is reconciled.
Cancel Cashflow: Choose Cancel Cashflow icon to cancel the cashflow. Cashflow with Statement Line transaction type cannot be canceled once the cashflow is reconciled. You must first unreconcile the cashflow before you cancel it. Cashflow with Bank Account Transfer transaction type can only be canceled by canceling the bank account transfer in Bank Account Transfer window. Cancel actions cannot be undone.
Header Section:
Cashflow: Cashflow identification number.
General Information Section:
Cashflow Amount: Cashflow amount.
Direction: Inflow or Outflow.
Cashflow Date: Date that the cashflow is created
Cashflow Status: Created, Canceled, Cleared, or Reconciled.
Transaction Type: Bank Account Transfer or Statement Line.
Transaction Subtype: Transaction subtype that is assigned to the cashflow.
Source Transaction Number: Source transaction number.
Bank Reference Number: Transaction identifier used in Autoreconciliation as a matching key.
Bank Statement Number: Bank statement number that the cashflow is generated from.
Value Date: Value date of the cashflow.
Bank Account Section:
Bank Account Number: Source bank account number.
Bank Account Name: Source bank account name.
Bank Account Currency: Source bank account currency.
Branch Name: Branch name of source bank account.
Bank Name: Bank name of source bank account.
Counterparty Bank Account Section:
Bank Account Number: Destination bank account number.
Bank Account Name: Destination bank account name.
Branch Name: Branch name of destination bank account.
Bank Name: Bank name of destination bank account.
Counterparty: Counterparty name.
Clearing Information Section:
Cleared Amount: Amount cleared in bank account currency.
Cleared Base Amount: Amount cleared in accounting currency.
Changes Amount: Amount charged in bank account currency
Charges Base Amount: Amount charged in accounting currency.
Error Amount: Error amount in bank account currency.
Error Base Amount: Error amount in accounting currency.
Cleared Date: Date that cashflow is cleared.
Exchange Rate: Exchange rate used in clearing.
Exchange Date: Exchange date used in clearing.
Exchange Rate Type: Exchange rate type used in clearing.
Accounting Information Section:
Accounting Status
Accounted: If all accounting events associated with cashflow have 'ACCOUNTED' status.
Not Accounted: If all accounting events associated with cashflow have 'UNACCOUNTED' status.
Partially Accounted: Only some of but not all accounting events associated with cashflow have 'ACCOUNTED' status.
Accounted with Error: At least one of accounting events associated with cashflow has 'ACCOUNTING_ERROR' status.
Not Applicable: Cashflow canceled.
View Accounting Details:
This opens up accounting detail page.
You can define mapping rules for the creation of cashflows from your bank account files in the Bank Statement Cashflow Mappings window, and these cashflows can be accounted for and reconciled in Oracle Cash Management.
To Create Bank Statement Cashflow Mappings:
Navigate to the Bank Statement Cashflow Mappings window and select the bank account for which you wish to define cashflow mapping rules.
Enter the bank transaction code or select from the list of values. Note: You will only be able to set up rules for codes which have been previously defined in the Bank Statement Transaction Codes window. For more information, see: Bank Statement Transaction Codes.
(Optional) Enter a search string. The search strings are used for pattern matches with the information in the description field of the bank statement line.
Enter the GL Account Number which will be used to record the receipt or expense. The cash GL Account Number will be derived from the bank accounts cash GL Account defined in the General Controls.
(Optional) Enter the Reference information. This can be used for reporting purposes and will be included in the journal entry associated with the created cashflow.
(Optional) Select a Transaction Subtype. For more information, see: Transaction Subtypes.
Proceed to Creating Cashflows from a bank statement file.
To Create Cashflows from Bank Statement Files:
Load and import the bank statement. For more information, see: Importing Bank Statements.
Run the AutoReconciliation program for the bank statement. For more information, see: Reconciling Bank Statements Automatically.
Note: To avoid creating cashflows for transactions already recorded in your systems, it is recommended that you run the AutoReconciliation program or manually reconcile for the bank statement prior to running the Bank Statement Cashflow Creation program.
Run the Bank Statement Cashflow Creation program for the bank statement to create cash management cashflows.
Note: The program does not apply the mapping rules to reconciled bank statement lines or bank statement lines for which cashflows have been created in the past unless the cashflow has been cancelled.
A cashflow will be created and an accounting event raised if a match as specified in the Bank Statement Cashflow Mappings window for the bank account is found.
The program automatically generates the Bank Statement Cashflow Creation Execution Report, which lists all of the details of the created cashflows. For more information, see: Bank Statement Cashflow Creation Execution Report.
You can account for these cashflows in your subledger by running the create accounting program. For more information, see: Subledger Accounting (SLA) IntroductionSubledger Accounting section.
Note: Cashflows created from bank statements are created in a cleared status because by nature they have already cleared the bank. These cashflows can not be uncleared, but if they have not been reconciled they can be canceled.
Run the AutoReconciliation program for the bank statement to reconcile the cashflows that were created.
Number: The bank account number.
Name: The name of the bank account.
Bank Name: The name of the bank.
Bank Branch: The name of the bank branch.
Bank Transaction Code: The code assigned to a bank transaction.
(Optional) Search String: Free text field for pattern matches.
GL Account Number: The non cash general ledger account that will be used to account for the cashflow.
(Optional) Reference: Free text field.
(Optional) Transaction Subtype: The transaction subtype assigned to the created cashflow and used for classifying and reporting on cashflows.