EAR 9.2: Customer Bank Account Number Is Missing on Direct Debit Payment File Generated by Financial Gateway if Bank Account Encryption Has Been Enabled (Doc ID 2938071.1)

Last updated on OCTOBER 01, 2024

Applies to:

Symptoms

A problem has been detected after enabling NACHA Bank Account Number encryption functionality, where Direct Debit electronic files (ACH 820) being generated by Financial Gateway at the time of dispatching payments for FIN Receivables Invoices (Transaction Type COLL), are missing the Customer's Bank Account Number on the BPR line.

Sample BPR line generated by the system before, and after, the run of Bank Account Number Encryption process (FSCM_CRYPTAE AE Program), shows how the Customer's Bank Account dummy value (123456789) is missing:

    - BEFORE:    BPR*D*1000.00*D*ACH*CCP*01*121042882*DA*0741-256458*1234567890**01*121000248*DA*123456789*20230105~
    - AFTER:    BPR*D*1500.00*D*ACH*CCP*01*121042882*DA*0741-256458*1234567890**01*121000248*DA**20230105~

The second row, (AFTER), shows DA** at the almost very end, when it should be DA*123456789* instead.

REPLICATION STEPS:

    1.- Ensure that the Company's External Bank Account has been configured with Collection Method of Direct debit using File Layout 820 ACH, and settled by Financial Gateway (Navigation Path: Banking > Bank Accounts > External Accounts > Collection Methods tab)
    2.- Define a new Direct Debit Profile ID targeting the External Bank Account configured, and File Layout 820 ACH (Navigation Path: Set Up Financials/Supply Chain > Product Related > Receivables > Payments > Direct Debit Profile)
    3.- Configure a new MICR ID to a given Customer, with Bank Account Number 123456789 (Navigation Path: Customers > Customer Information > MICR Information)
    4.- Link the new MICR ID configuration with the existing Customer, and define the Payment Method as Direct Debit, as well as the newly created Direct Debit Profile ID (Navigation Path: Customers > Customer Information > Create Customer Information > Bill To Options tab)
    5.- Define the Key Value for the Algorithm ID aes_ks256_cbc_encrypt, under Keyset ID Bank_Account_Number (Navigation Path: PeopleTools > Security > Encryption > Encryption Algorithm Keysets)
    6.- Set up Parameter Value is Bank_Account_Number under Encryption Profile ID FSCM_ACCT_NUM_ENCRYPT (Navigation Path: PeopleTools > Security > Encryption > Define Encryption Profiles)
    7.- Define the Key Value for the Algorithm ID aes_ks256_cbc_decrypt, under Keyset ID Bank_Account_Number (Navigation Path: PeopleTools > Security > Encryption > Encryption Algorithm Keysets)
    8.- Set up Parameter Value is Bank_Account_Number under Encryption Profile ID FSCM_ACCT_NUM_DECRYPT (Navigation Path: PeopleTools > Security > Encryption > Define Encryption Profiles)
    9.- Validate the Encryption and Decryption Profile IDs, and launch the Bank Account Number Encryption process (Navigation Path: Set Up Financials/Supply Chain > Common Definition > Encryption Configuration > Bank Account Number Encryption)
    10.- Create a new Pending Item Group in FIN Receivables module for the configured Customer, and set it to Post Action Batch Standard (Navigation Path: Accounts Receivable > Pending Items > Online Items > Online Item Group Entry)
    11.- Launch AR Update with the option of 'Pending Items' selected (Navigation Path: Accounts Receivable > Receivables Update > Request Receivables Update)
    12.- Run the Create Direct Debits process for the Business Unit and Direct Debit Profile ID in question (Navigation Path: Accounts Receivable > Direct Debits > Administer Direct Debits > Create Direct Debits)
    13.- Proceed to remit the newly created Direct Debit Worksheet ID for the transaction at hand (Navigation Path: Accounts Receivable > Direct Debits > Administer Direct Debits > Update Direct Debits > Remit button/icon)
    14.- Launch AR Update with the option of 'Direct Debits' selected (Navigation Path: Accounts Receivable > Receivables Update > Request Receivables Update)
    15.- Continue the processing by remitting to the Bank the EFT file, by running the AR_FG_PROC to Financial gateway (Navigation Path: Accounts Receivable > Direct Debits > Remit to Bank > Create Remit to Bank EFT File)
    16.- Now proceed to dispatch the Direct Debit Payment via Financial Gateway (Navigation Path: Financial Gateway > Process Payments > Payment Dispatch)
    17.- PROBLEM: Review the generated flat file containing the Direct Debit Payment information, and confirm that in row BPR the Customer's Bank Account Number is missing after the DA string

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.

The Bank or Financial Institution receiving the submitted EFT electronic file rejects it as it is missing crucial information of the Customer's Bank Account Number in the BPR line, and as such, the Direct Debit payment cannot be processed. This is affecting the company's stream of revenue, as Direct Debits cannot be charged to customers.

After having run the Bank Account Number Encryption process (FSCM_CRYPTAE AE Program), the Direct Debit Payment EFT file should still contain the needed Customer's Bank Account Number value in the BPR line.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.