Configure Funds Capture

Use this integration to process customer receipts through your bank accounts.

Configure lockbox receipts in Oracle Fusion by using standard Fusion implementation methodology.

  • The bank provides the lockbox number and bank origination number.
  • The Oracle Fusion lockbox configuration must include the bank origination number.
  • The Oracle Fusion lockbox number and origination number must exactly match the values used in the file name, including any leading zeros.
Note: You are responsible for requesting that your bank's implementation manager follow the embedded lockbox process. The file format and name must conform exactly to these standards. Embedded Banking Services won't recognize the file if there are any variations.
  • Lockbox template format: Request that your lockbox receipt details be provided in BAI2 format. Follow the link to get the template and integration rules: ORA_BAI2_EXTENDED_GENERIC.xlsx
  • File name: ORALB.<Lockbox Number>.<ABA number/origination number>.BofA. <YYYYMMDDHHmmss>.txt.pgp
    • Don't replace periods (.) with underscores (_).
    • 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.
  • Coordinate with the bank if you need additional receipt details using attributes within Record Type 6. You’ll need to map those additional attributes.
  • Oracle Fusion doesn’t support multiple DDA’s within a single lockbox.

Once the above conditions are met, the embedded banking process automatically processes the lockbox file when the bank receives it. Coordinate with the bank on the frequency for receiving lockbox files. You may view the results of lockbox file processing in the Manage Receipts page.