EAP: ACH PPD file -- Trace Number (Record 6, Position 80-87) is now NACHA compliant (Doc ID 2181767.1)

Last updated on SEPTEMBER 12, 2016

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

In the process of testing an ACH file for a new Bank. The External Account is setup for Payment Method = ACH, Layout = PPD. When reviewing the ACH file, for Record Type 6, position 80-87, which is the Trace Number, the output is not matching the Bank's specifications. Assume that both the Bank's specifications and the PPD file should be NACHA compliant.

Per the Bank specifications, for Record Type 6, position 80-87 should be the Bank's transit/ABA number. Currently, the system is populating this position with the Supplier's Bank Account Number.

Based upon the NACHA requirements at https://www.nacha.org/rules, NACHA states that the Trace Number (Record Type 6, position 80-87) should be constructed as follows:

Positions
01-08 Routing number of ODFI (the Originating DFI Identification)
09-15 Entry Detail Sequence Number - The number assigned in ascending order to each Entry within each batch. Provisions should be made by the ODFI to avoid duplication of Trace Numbers if multiple dat Files are prepared on the same day. Trace Numbers are not required to be contiguous.
 
STEPS
1. External Bank Account setup with Payment Method = ACH, Layout = PPD
2. Supplier has Supplier Bank Account setup
3. Create a Voucher for the Supplier in Step 2 for Payment Method = ACH, Layout = PPD
4. Pay the Voucher through the Pay Cycle
5. Check the PPD file created
6. Record Type 6, position 80-87 is reflecting the Supplier's Bank Account

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms