How to surpress a 627(Credit) Record from a 220 (Debit) record for Nacha? (Doc ID 303121.1)

Last updated on DECEMBER 13, 2016

Applies to:

Oracle HRMS (US) - Version 11.5.10.2 and later
Information in this document applies to any platform.
Checked for relevance on 12-DEC-2012


Goal

The 3rd Party Nacha File is creating a 627 (Credit) Record, how can this not be created?

The problem is that the file is creating a final entry detail record with a Transaction Code of 27,the financial institution states that a 627 record should not be used with a 220 because it represents a credit only file.

How canthe 627 record be blocked from creation?



Solution

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