Electronic Payments
With this integration, you can process electronic payments using your bank accounts with the BOFA EFT Payment method for ACH, Global ACH (GACH), SEPA, and wire payments.
You are responsible for working with your bank's implementation manager to properly configure the provided BOFA ISO20022 CGI CBPR or BOFA ISO20022 SEPA CBPR payment formats to meet your specific electronic payment requirements.
Configure payments in Oracle Fusion following standard Fusion implementation methodology and the associated Bank of America predefined codes. Test and confirm that custom configurations are accepted by the bank.
If you use your existing electronic payment methods, you must add the alias TRF to your current payment method header.
Configure Payment IDs
To configure the payment IDs, you must enter the ACH Client ID and the Sender ID.
- Go to Navigator > My Enterprise > Setup and Maintenance.
- Select the Financials offering.
- Open Cash Management and Banking and search for the task Manage Bank Accounts.
- Select Create (+) to create a new account, or search for an existing account and open it for editing.
- On the Create Bank Account page, go to the General tab.
- In the Bank Company Identifier field, enter the bank-provided ACH Client
ID.
The bank provides the ACH Client ID for each relevant bank account.
- Select Save and Close, then Done.
- Go to Navigator > My Enterprise > Setup and Maintenance.
- Select the Financials offering.
- Open Payments and search for the task Manage Payment Systems.
- Search for and select the payment system you want.
- Open its payment system options.
- Select Edit Payment System Accounts and select the relevant BOFA Payment System account.
- In the account settings setup and details area, locate the row for Bank
Identifier and enter the bank-provided Sender ID in the Value column.
If multiple Sender IDs are required, create multiple payment system accounts by copying the BOFA Payment System payment system account and update the Sender ID.
- Select Save and Close, then Done.
Check Printing Service
You may use Bank of America for outsourced check printing services as part of the integration using the BOFA Check Payment Method.
You are responsible for working with your Bank of America implementation manager to configure the provided BOFA ISO20022 CGI CBPR payment format to meet your check printing payment needs.
Be sure to complete the required paperwork, test, and confirm that the configurations are acceptable to Bank of America.
You may use Delivery Channels via Payment Code to represent the check print stock template and mailing instructions. Work with your Bank of America implementation manager to determine the required codes.
Processing Payments
To ensure that your payment configurations use Bank of America embedded connectivity, update your Payment Process Request (PPR) to use the Payment Process Profile (PPP) named BOFA ISO20022 CGI CBPR or BOFA ISO20022 SEPA CBPR.
<POD NAME>.BOFA.PAY.0103.<variable information>.xml.pgpAcknowledgments
Payment processing acknowledgments occur in four stages to validate payment files, confirm processing status, provide core processing, foreign exchange, and clearing details, and deliver final processing status.
The bank sends file-level and transaction-level acknowledgments at your request.
- File name: <POD NAME>.BOFA.PAY-ACK.L*.<YYYYMMDDHHmmss>.xml.pgp
- Provide the bank with your Oracle Fusion POD name.
- Don't replace periods (.) with underscores (_).
- The POD NAME should only include the POD family name. Don't include qualifiers like "-test" or "- dev1".
- Use the provided encryption keys. The .pgp extension is added automatically after encryption. Don't manually rename the file to add the .pgp extension. Oracle Fusion Embedded Banking Services recognizes only properly encrypted PGP files.
- Include the complete date and time stamp to ensure a unique file name. Embedded Banking Services doesn't process duplicate file names.
- The bank doesn't send payment acknowledgment files during UAT testing. These files are available only in production.
If the payment file status doesn't change to Acknowledged within a few hours, a validation error has likely occurred. Correct the error and resubmit the payment.
There are four levels of payment acknowledgment files during the clearing process, identified by file names containing L1, L2, L3, and L4.
- First Level (L1) Technical File Acknowledgment: Generated by the bank usually within seconds of receiving the payment file. Confirms that the file-level syntax within CashPro is correct.
- Second Level (L2) Payment System File Receipt Acknowledgment: Generated by the bank usually within seconds of receiving the payment file. Confirms additional payment validations.
- Third Level (L3) Payment System Core Processing Acknowledgment: Generated at the end of a two-hour processing window. Provides foreign exchange rate information and clearing details, when available. Applies only to foreign exchange and wire payments.
- Fourth Level (L4): Generated within two hours or after all items are processed, whichever occurs first. Currently available only for APAC customers. Applies only to foreign exchange and wire payments.
L3/L4 files are sent at the end of a 2-hour clearing window. Currently, these files apply only to FX and wire transfers.
Recommended Settings for Funds Disbursement
These settings are recommended for funds disbursement based on the predefined configuration.
| Parameter | Description |
|---|---|
| Service Level Code |
For ACH transactions, select NURG. For wire and cross-border transactions, select URGP. For check payments, select CCHQ. |
| Delivery Channel |
For US ACH, use CCD, PPD, CCD+, PPD+, CTX, or IAT. For check printing, delivery channel includes custom Payment Codes, such as US. To create payment codes: Go to Setup and Maintenance > Payments > Manage Payment Codes > Create a Payment Code (type = Delivery Channel). |
| Payment Method Alias |
For ACH payments, the payment method is preconfigured with the alias TRF. If you create your own payment method, use TRF as the alias. For check payments, the payment method is preconfigured with the alias CHK. If you create your own payment method, use CHK as the alias. |
| Alias Values |
Service level alias values: NURG, URGP, or SEPA. Payment reason alias values: SUPP (Supplier Payment), TRAD (Trade), and CORT (Trade Settlement Payment). |
| Validations |
Various validations run at the format and payment method levels:
|