HCM ENCRYPTION FRAMEWORK, Specific Tables (Including PAY_DISTRIBUTION) And NACHA Regulations (Doc ID
Question On - HCM ENCRYPTION FRAMEWORK, Specific Tables (Including PAY_DISTRIBUTION) And NACHA Regulations (Doc ID 2790442.1)
I do agree with this following statement
"This specific table is a process record and with regards to what entails encryption, the fields will be masked and this satisfies the NACHA regulations."
But with just storing masked account number , we loose the actual account number that snapped into pay_distributn at the time of pay confirmation. That is the reason why it would make sense to snap the encrypted value also at the time of pay confirmation. This will enable to send the correct account on ddp file , also will assist for any future reference while reversing the check, or reporting and so on.