EPY: Requirement to Encrypt/Decrypt for Pay Distribution Issues When Self Service User Changes Account Before Running Direct Deposit Create File
(Doc ID 2802539.1)
Last updated on SEPTEMBER 30, 2022
Applies to:PeopleSoft Enterprise HCM Payroll for North America - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
When the NACHA encryption is used, if the account information or the priority gets changed either by employee or by an agent between payroll confirmation and post confirm jobs, the outbound extract will not reflect the same account number populated in PAY_DISTRIBUTN.
The file needs to be manipulated to provide the correct File ID, unless the employees are locked out of the system.
For some Companies, locking the employees out does not work for their business process. Is there anything that can be done to change how this process works with HCM Encryption Framework?
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