R12: IBY: Wrong Bank Account Type on Bank File Running (US NACHA Format)
(Doc ID 1613166.1)
Last updated on AUGUST 11, 2022
Applies to:
Oracle Payments - Version 12.1.3 and laterInformation in this document applies to any platform.
NOTE: In the images below and/or the attached document, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Symptoms
ACTUAL BEHAVIOR
-------------------------
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):
622################### XXXXXXXXXXXXXX LASTNAME, NAME YYYYYYYYYYYYYYYY
The first digit is the "Record Type Code" = 6 (622###################)
The second and third digits are the Transaction code of the Transaction = 22 (622###################)
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.
It is expected that Bank File will contain the correct Transaction Code of "SAVINGS" (32), not CHECKING (22).
Due to this issue, users cannot see correct Bank Account Type Transaction Code in Bank File
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Submit PPR.
2. Generate Bank File
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |