Implementation Checklist

Share this checklist with the bank’s implementation manager to track and confirm that each implementation step is completed by the responsible party.

Refer to this guide for detailed explanations. Your implementation might include additional use cases that aren't covered by this checklist.

Connectivity

Owner Client Action in Oracle Fusion Cloud ERP Bank Action/Confirmation Completion Evidence Status
Client Confirm that the implementer has the Financial Application Administrator role or an equivalent custom role. No action. Manage Embedded Banking Configurations opens. Not Started
Client Enter the promotion code received from Oracle Support. No action. Manage Embedded Banking Configuration becomes available. Not Started
Client Add the Oracle-provided lookup code under ORA_ERP_CONTROLLED_CONFIG. No action. Bank of America appears in the list of available banks. Not Started
Joint Select Bank of America and enable only the services that match the agreed scope of work. Confirm the services requested for implementation. Enabled services are documented and approved by both teams. Not Started
Joint Download the generated SSH and PGP keys. Provide secure key exchange instructions to the client. Keys are downloaded and securely shared with the bank. Not Started
Bank No Oracle Fusion action. Receive and load the Oracle Fusion-generated SSH and PGP keys and configure the transmission. Bank confirms that the keys are loaded Not Started
Bank No Oracle Fusion action. Send B2Bi UAT and Production Portal credentials to the client, including the user ID and temporary password. Client receives the credentials through the approved channel. Not Started
Client Sign in to the bank’s B2Bi Portal using user ID and reset the password. Confirm that the B2Bi credential reset is complete. Portal access is verified and the password reset is complete. Not Started
Joint Return to Manage Embedded Banking Configurations, select Bank of America, select Next, and enter the user ID in the User Account Name field. Confirm that the user ID is active and available for the Oracle B2B Service connection. Connectivity is established and the selected services change from In Progress to Completed. Not Started

Banks and Bank Accounts

Owner Client Action in Oracle Fusion Cloud ERP Bank Action/Confirmation Completion Evidence Status
Joint

Create or verify the bank and bank accounts in Oracle Fusion Cloud ERP.

*Account numbers in Oracle Fusion Cloud ERP must exactly match the bank’s account numbers, including any leading zeros.
Confirm that the bank account details match the bank’s records. Bank and account records are created or validated. Not Started

Funds Disbursement

Owner Client Action in Oracle Fusion Cloud ERP Bank Action/Confirmation Completion Evidence Status
Joint

Configure payment use cases. Update the CBPR+ payment template, if necessary.

See the implementation workbook for configuration options.
Provide additional requirements to support country-specific payment type configuration use cases. Payment XML file is approved for each use case. Not Started
Joint Enter the bank-provided ACH Company ID where required. Provide the ACH Company IDs. Payment file includes the ACH Company ID, where relevant. Not Started
Joint Enter the bank-provided Sender ID as the Bank Identifier. Provide the Sender ID. Payment file includes the Sender ID. Not Started
Client Update the relevant Payment Process Request to use BOFA ISO20022 CGI CBPR or BOFA ISO20022 SEPA CBPR as the Payment Process Profile. No action. Bank receives payment file. Not Started
Bank Provide the Oracle Fusion POD family name to the bank. Embedded Banking Services recognizes only correctly named encrypted acknowledgment files.

Send encrypted payment acknowledgment files using this naming convention:

<POD NAME>.BOFA.PAY-ACK.L*.<YYYYMMDDHHmmss> .xml.pgp

Production acknowledgment file is received and recognized by Oracle Fusion Cloud ERP. Not Started

Funds Capture

Owner Client Action in Oracle Fusion Cloud ERP Bank Action/Confirmation Completion Evidence Status
Client Update Manage Receivables System Options for each participating business unit. No action. Business unit receivables options are updated. Not Started
Joint Provide the ORA_BAI2_EXTENDED_GENERIC template. Provide lockbox receipt details in the provided BAI2 format. Sample BAI2 lockbox file produced. Not Started
Joint Configure the lockbox with the origination number exactly as it appears in the bank’s file name, including leading zeros. Provide the correct lockbox number and bank origination number. The lockbox configuration contains the bank-provided lockbox and origination number. Not Started
Bank Embedded Banking Services recognizes only correctly named encrypted lockbox files.

Send lockbox files using this naming convention:

ORALB.<Lockbox Number>.<ABA Number/origination Number>.BofA.<YYYYMMDDHHmmss>.txt.pgp

Lockbox file is received and processed by Oracle Fusion Cloud ERP. Not Started

Bank Statement Processing

Owner Client Action in Oracle Fusion Cloud ERP Bank Action/Confirmation Completion Evidence Status
Client Configure user-defined reconciliation rules, if relevant. Confirm that the same accounts are enabled for statement delivery. Reconciliation-ready accounts are documented. Not Started
Bank Use the ISO20022 CAMT.053.001.02 format for prior-day bank statements. Confirm the bank’s CAMT.053 template is configured. Sample statement imports successfully. Not Started
Bank Provide the Oracle Fusion POD family name to the bank. Embedded Banking Services recognizes only correctly named encrypted CAMT.053 files.

Send statement files using this naming convention:

<POD NAME> .BOFA.CAMT53*.<YYYYMMDDHHmmss> .xml.pgp

CAMT.053 file is received and processed by Oracle Fusion Cloud ERP. Not Started