My Oracle Support Banner

Wrong Bank Account Type on Bank File Running (US NACHA Format) (Doc ID 1613166.1)

Last updated on OCTOBER 03, 2017

Applies to:

Oracle Payments - Version 12.1.3 and later
Information in this document applies to any platform.


Wrong Bank Account Type "Transaction Code" on bank file running (US NACHA Format) 

Generation of Bank Files, the system defaults the employee bank account type as CHECKING (22) not SAVINGS (32)  for some of  the employees.

The third row of the Format Payment Instruction Output show the following (for example):
6220839045631002505106       00006951784484           PRECHTEL, RYAN A        1531015610000001

The first digit is the "Record Type Code" = 6 (6220839045631002505106)
The second and third digits are the Transaction code of the Transaction = 22 (6220839045631002505106)

This code should be 22 If the External Bank Account Type is Checking and amount is greater than 0. If the amount is zero, this code should be 23.
This code should be 32 If the External Bank Account Type is Savings and amount is greater than 0. If the amount is zero, this code should be 33.

Bank File will contain the correct Transaction Code of "SAVINGS" (32), not CHECKING (22).

The issue can be reproduced at will with the following steps:
1. Submit PPR.
2. Generate Bank File

The issue has the following business impact:
Due to this issue, users cannot see correct Bank Account Type Transaction Code in Bank File.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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