Last updated on MARCH 17, 2016
Applies to:PeopleSoft Enterprise FIN Cash Management - Version 9.2 and later
Information in this document applies to any platform.
When creating the NACHA file using Financial Gateway, there are many fields in the NACHA file and batch header that do not allow the user to configure or populate with information that the bank indicates needs to be changed, but cannot be changed due to its use for other purposes, such as BU (legal entity) name.
Below are the items requested:
1. File Header
This is the Immediate Destination Name aka Bank Name (in the red box). We use the Legal Name for the bank which is what they want printed on the checks. They just want Deutsche Bank in this field, not the full name.
This is the Immediate Origin Name aka company name (in the blue box). The bank wants us to use XXXXXXX, not XXXXXXX Corporation. This needs to be the same for all files going to this bank. It can not be one name for one file and a different name for a different file (see below). The system is populating that field from the business unit name from the first business unit in the first batch header. In the file below, the file header should still be XXXXXXX.
2. Batch Header 1
This field is where the remitter company name resides. These fields are not allowed to contain punctuation marks and, according to NACHA rules, must be a name that the recipient can easily identify. In Batch Header 2, this needs to be COSCI and should not have a comma. This information is coming from the BU description
This is the Company Entry Description. NACHA rules indicate that the information in this field must also be something descriptive enough as to the purpose of the transfer. ACH is being populated by the payment method. ACH is not descriptive enough. We need to populate something like VNDR PYMNT.
Enhancement Request is needed to be able to have these fields as configurable fields similar to the Immediate Origin ID and Immediate Destination ID for the fields in the header record and the Company ID for the fields in the batch header.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms