bethbowers I realize that I had the same problem back on 2/6 of the bank code changing somehow to one that was masked with actual asterisks for a client on 2019 PU2.  I could not figure out why that occurred.  The client was made aware of the problem because the positive pay that they submitted was accepted on 2/4, and then the next day's check run the PP they submitted on 2/5 was rejected.  I ran the system activity log for 2/4 and 2/5 and couldn't find anything that could have made this change.  There also were no changes to security logged on either of those days.   It hasn't happened again but would be good to find out why!

My client with the fix just had the bank account number become encrypted again.  The fix was installed prior to her June bank rec and Period End Processing for June.  No problem.  But after she reconciled the bank for July and Period Ended the modules, the encryption recurred.

Any update on understanding the source of this issue and why it would recur? Linda, I wrote to you directly with this information.

Barbara,

I just responded to your email with some questions.

Barbara,

I just responded to your email with some questions.

I upgraded a client from 2020.0 to 2020.1 last week,  Yesterday, she completed a bank rec, and when she processed a Positive Pay today, guess what?  Bank code encrypted.  She had a successful PP 2 days prior to the PU1 install.  She has not performed any Period End Processing, just the bank rec.

Greetings,

Thank you for the information.  Sage is still working on this issue as we try to narrow down the exact cause.  We will take another look at Bank Rec and Positive Pay with the 2020 PU1.  In all of our testing of Bank Rec and Positive Pay on various versions so far, we have not been able to duplicate the issue.

Thank you,

Kent

Greetings,

Wanted to post back that today we were finally able to duplicate the issue on 2020 PU1.  A defect has been created and we are currently working on a fix.  I do not have an ETA on the fix but I would think this will be released as a hotfix once it is available.

I will try to post back when I have more information.  Either early next week or after the Thanksgiving (U.S.) holiday.

Thank you,
Kent

This has just reared its head again.  I recently upgraded a client to v2021.2, and they just performed their first bank rec.  Bank account number is now encrypted after the bank rec.  There was a hot fix for v2020.1.  Was it not incorporated in v2021?  They do not do Positive Pay.  Users have the permission enabled to view/print/edit PII.

We are having it occur now when creating the Positive Pay file.

Greetings,

Please open a case for this issue and provide as much detail as possible on how to duplicate the issue.  This will help us investigate.

We will likely need to get some information from your customer's installation like the data dictionary files, data files for Bank Rec, etc. to help us debug.

Thank you,
Kent

Greetings,

What version of Sage 100 are you seeing this on when running Positive Pay?  Would you please also open a case with Customer Support and provide details on how to duplicate the issue.

Thank you,
Kent

This has happened to us as well after performing YE for 2021 on AP and other modules.  It was working fine all these years and the first couple weeks until I did YE for 2021 and now the first several Bank Account No. are replaced with asterisks *****12345.  I've replaced these invalid bank account numbers in notepad with the full Bank Account No. and uploaded to the bank successfully.

We are on Sage 100c Advanced 2019.2.

Any help with getting this fixed would help.

Double check to see if on the Bank Code Maintenance, that Sage did not add the asterisks to the account number.  I have had it do this several times now.

Greetings,

Please open a support case for this issue.  We will need some details on the exact steps and also some files from your system to try and figure out what happened.

Thank you,

Kent Mackall