NACHA File Missing Bank Required Information (Doc ID 2039296.1)

Last updated on APRIL 18, 2024

Applies to:

Symptoms

On : 12.2.4 version, US Payroll - General

NACHA file issue

NACHA (For US legislation) is not in sync with bank requirements

EXPECTED BEHAVIOR

File header record (“1” record)
• In field 3, (positions 4-13- the “immediate destination” field) we are looking for the XXX ABA number (“b999000999 where b= blank space). This is blank on their file.
• In field 4, position 14-23 (‘immediate origin’ field) we are looking for the customer’s File ID. This is blank on their file.
• In field 11, position 41-63 (immediate destination name), we are looking for “<Company Name>” followed by 12 spaces. This is blank on their file.
• In field 12, position 64-86 (immediate origin name), we are looking for THEIR name. This is blank on their file.

Batch header record (“5” record)
• In field 9, position 70-75, (effective entry date) they need to put the date they want these transactions to settle. They have a date of 2/28/15. But the file was created on 6/5/15, making this a stale dated file.
• In field 12, position 80-87 (originating DFI ID) they should be putting the first 8 digits of our ABA number (“09100001”) Instead, it appears as though they are missing that completely, which leaves their batch header record 86 characters long rather than the required 94 characters.

Entry Detail record (‘6’ record)
• They have the same issue on the detail record that they do on the batch header record- they should be including the first 8 digits of the XXX ABA number “99900009” in positions 80-87, and then the transaction number in the next 7 positions. They have omitted the XXX ABA number, and this line is only 86 characters long rather than 94 characters.

Batch Control record (‘8’ record)
• In field 10, position 80-87 (originating DFI ID) they should be putting the first 8 digits of our ABA number (“99900009”) Instead, it appears as though they are missing that completely, which leaves their batch control record 86 characters long rather than the required 94 characters.



STEPS
The issue can be reproduced at will with the following steps:

• Submit NACHA file

Cause

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