Sage 100

We upgraded a client to version 2022.2 about two or three weeks ago thinking that was going to resolve this issue – they emailed me today saying that it disappeared again.{sigh}

We upgraded a client to version 2022.2 about two or three weeks ago thinking that was going to resolve this issue – they emailed me today saying that it disappeared again.{sigh}

We upgraded a client to version 2022.2 about two or three weeks ago thinking that was going to resolve this issue – they emailed me today saying that it disappeared again.{sigh}

We upgraded a client to version 2022.2 about two or three weeks ago thinking that was going to resolve this issue – they emailed me today saying that it disappeared again.{sigh}

Me too.  Keep me posted if anyone finds a fix.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

Any chance the issue is related to role permissions?  Curious if the user has GL security event - Allow Viewing, Printing, and Editing of Highly Sensitive Personally Identifiable Information.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

Nope, it's not that.  And it's not ALL the time, either.

Any chance the issue is related to role permissions?  Curious if the user has GL security event - Allow Viewing, Printing, and Editing of Highly Sensitive Personally Identifiable Information.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

I wonder if it's another user causing it to disappear with another process, and just being noticed by the positive pay user 

Nope, it's not that.  And it's not ALL the time, either.

Any chance the issue is related to role permissions?  Curious if the user has GL security event - Allow Viewing, Printing, and Editing of Highly Sensitive Personally Identifiable Information.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

Maybe we should create a SAW alert to monitor!!!!

I wonder if it's another user causing it to disappear with another process, and just being noticed by the positive pay user 

Nope, it's not that.  And it's not ALL the time, either.

Any chance the issue is related to role permissions?  Curious if the user has GL security event - Allow Viewing, Printing, and Editing of Highly Sensitive Personally Identifiable Information.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

Did anyone else have a situation where the bank account table had a blank record?

Maybe we should create a SAW alert to monitor!!!!

I wonder if it's another user causing it to disappear with another process, and just being noticed by the positive pay user 

Nope, it's not that.  And it's not ALL the time, either.

Any chance the issue is related to role permissions?  Curious if the user has GL security event - Allow Viewing, Printing, and Editing of Highly Sensitive Personally Identifiable Information.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

Bank Account Number and the Bank Code Description are missing

Adding this link as cross-reference to a similar report ( if not a report about this issue ). Sage claims it's fixed  in the KB but it doesn't seem like the reports here are supporting that.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

So is the problem that the user needs bank account permissions and PII, and somewhere in the permissions check it can blank out the fields?

Bank Account Number and the Bank Code Description are missing

Adding this link as cross-reference to a similar report ( if not a report about this issue ). Sage claims it's fixed  in the KB but it doesn't seem like the reports here are supporting that.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

@Phil McIntosh - we'd love to know... The irritating part is that it is not consistent, i.e. doesn't happen EVERY period end or EVERY Positive Pay or EVERY whatever it is.  Or maybe it IS consistent, but the trigger is that you're standing on your head barking like a dog while right clicking the up arrow and people don't do that every month.  :-)

So is the problem that the user needs bank account permissions and PII, and somewhere in the permissions check it can blank out the fields?

Bank Account Number and the Bank Code Description are missing

Adding this link as cross-reference to a similar report ( if not a report about this issue ). Sage claims it's fixed  in the KB but it doesn't seem like the reports here are supporting that.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

This isn't fixed in 2023 PU 2 which is what my client is running.

@Phil McIntosh - we'd love to know... The irritating part is that it is not consistent, i.e. doesn't happen EVERY period end or EVERY Positive Pay or EVERY whatever it is.  Or maybe it IS consistent, but the trigger is that you're standing on your head barking like a dog while right clicking the up arrow and people don't do that every month.  :-)

So is the problem that the user needs bank account permissions and PII, and somewhere in the permissions check it can blank out the fields?

Bank Account Number and the Bank Code Description are missing

Adding this link as cross-reference to a similar report ( if not a report about this issue ). Sage claims it's fixed  in the KB but it doesn't seem like the reports here are supporting that.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

Didn't Sage say at MOTM 2025 that they finally figured this out & they will be releasing a fix? I have this memory of a grand applause moment... but I can't find it fixed in any PU or hotfix. Was a fix ever published? Did I imagine this all?

This isn't fixed in 2023 PU 2 which is what my client is running.

@Phil McIntosh - we'd love to know... The irritating part is that it is not consistent, i.e. doesn't happen EVERY period end or EVERY Positive Pay or EVERY whatever it is.  Or maybe it IS consistent, but the trigger is that you're standing on your head barking like a dog while right clicking the up arrow and people don't do that every month.  :-)

So is the problem that the user needs bank account permissions and PII, and somewhere in the permissions check it can blank out the fields?

Bank Account Number and the Bank Code Description are missing

Adding this link as cross-reference to a similar report ( if not a report about this issue ). Sage claims it's fixed  in the KB but it doesn't seem like the reports here are supporting that.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

v2024 PU 2

Didn't Sage say at MOTM 2025 that they finally figured this out & they will be releasing a fix? I have this memory of a grand applause moment... but I can't find it fixed in any PU or hotfix. Was a fix ever published? Did I imagine this all?

This isn't fixed in 2023 PU 2 which is what my client is running.

@Phil McIntosh - we'd love to know... The irritating part is that it is not consistent, i.e. doesn't happen EVERY period end or EVERY Positive Pay or EVERY whatever it is.  Or maybe it IS consistent, but the trigger is that you're standing on your head barking like a dog while right clicking the up arrow and people don't do that every month.  :-)

So is the problem that the user needs bank account permissions and PII, and somewhere in the permissions check it can blank out the fields?

Bank Account Number and the Bank Code Description are missing

Adding this link as cross-reference to a similar report ( if not a report about this issue ). Sage claims it's fixed  in the KB but it doesn't seem like the reports here are supporting that.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

Thank you! @Jeff Schwenk

It would be so silly for Sage to actually update the KB article that the fix was published in particular product updates. :)

v2024 PU 2

Didn't Sage say at MOTM 2025 that they finally figured this out & they will be releasing a fix? I have this memory of a grand applause moment... but I can't find it fixed in any PU or hotfix. Was a fix ever published? Did I imagine this all?

This isn't fixed in 2023 PU 2 which is what my client is running.

@Phil McIntosh - we'd love to know... The irritating part is that it is not consistent, i.e. doesn't happen EVERY period end or EVERY Positive Pay or EVERY whatever it is.  Or maybe it IS consistent, but the trigger is that you're standing on your head barking like a dog while right clicking the up arrow and people don't do that every month.  :-)

So is the problem that the user needs bank account permissions and PII, and somewhere in the permissions check it can blank out the fields?

Bank Account Number and the Bank Code Description are missing

Adding this link as cross-reference to a similar report ( if not a report about this issue ). Sage claims it's fixed  in the KB but it doesn't seem like the reports here are supporting that.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

Didn't Sage say at MOTM 2025 that they finally figured this out & they will be releasing a fix? I have this memory of a grand applause moment... but I can't find it fixed in any PU or hotfix. Was a fix ever published? Did I imagine this all?

This isn't fixed in 2023 PU 2 which is what my client is running.

@Phil McIntosh - we'd love to know... The irritating part is that it is not consistent, i.e. doesn't happen EVERY period end or EVERY Positive Pay or EVERY whatever it is.  Or maybe it IS consistent, but the trigger is that you're standing on your head barking like a dog while right clicking the up arrow and people don't do that every month.  :-)

So is the problem that the user needs bank account permissions and PII, and somewhere in the permissions check it can blank out the fields?

Bank Account Number and the Bank Code Description are missing

Adding this link as cross-reference to a similar report ( if not a report about this issue ). Sage claims it's fixed  in the KB but it doesn't seem like the reports here are supporting that.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

What I find crazy is that it seems many of these bugs are solved by now hidden fixes that you have to encounter on your own then call Sage and get a disclaimer/waiver (not sure why the VAR has to sign these but that's a different issue ).

Then when you are staging an upgrade like Sage 100 2025 you can grab PU1 but I'm always left with this uneasy feeling that I'm probably missing a patch or two.

There's now no way to find these one-off patches since unless they are big enough to embarrass Sage it doesn't seem like the patches are publicly available.

Which makes no sense to me as part of getting a client system all staged for an upgrade.

Didn't Sage say at MOTM 2025 that they finally figured this out & they will be releasing a fix? I have this memory of a grand applause moment... but I can't find it fixed in any PU or hotfix. Was a fix ever published? Did I imagine this all?

This isn't fixed in 2023 PU 2 which is what my client is running.

@Phil McIntosh - we'd love to know... The irritating part is that it is not consistent, i.e. doesn't happen EVERY period end or EVERY Positive Pay or EVERY whatever it is.  Or maybe it IS consistent, but the trigger is that you're standing on your head barking like a dog while right clicking the up arrow and people don't do that every month.  :-)

So is the problem that the user needs bank account permissions and PII, and somewhere in the permissions check it can blank out the fields?

Bank Account Number and the Bank Code Description are missing

Adding this link as cross-reference to a similar report ( if not a report about this issue ). Sage claims it's fixed  in the KB but it doesn't seem like the reports here are supporting that.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

Testing hotfixes for general release have real costs (for Sage, and all developers with enhancements affected by the fix). 

I don't like it, but I do understand why issues not getting lots of complaints will be put on the list for general PU QA testing.

What I find crazy is that it seems many of these bugs are solved by now hidden fixes that you have to encounter on your own then call Sage and get a disclaimer/waiver (not sure why the VAR has to sign these but that's a different issue ).

Then when you are staging an upgrade like Sage 100 2025 you can grab PU1 but I'm always left with this uneasy feeling that I'm probably missing a patch or two.

There's now no way to find these one-off patches since unless they are big enough to embarrass Sage it doesn't seem like the patches are publicly available.

Which makes no sense to me as part of getting a client system all staged for an upgrade.

Didn't Sage say at MOTM 2025 that they finally figured this out & they will be releasing a fix? I have this memory of a grand applause moment... but I can't find it fixed in any PU or hotfix. Was a fix ever published? Did I imagine this all?

This isn't fixed in 2023 PU 2 which is what my client is running.

@Phil McIntosh - we'd love to know... The irritating part is that it is not consistent, i.e. doesn't happen EVERY period end or EVERY Positive Pay or EVERY whatever it is.  Or maybe it IS consistent, but the trigger is that you're standing on your head barking like a dog while right clicking the up arrow and people don't do that every month.  :-)

So is the problem that the user needs bank account permissions and PII, and somewhere in the permissions check it can blank out the fields?

Bank Account Number and the Bank Code Description are missing

Adding this link as cross-reference to a similar report ( if not a report about this issue ). Sage claims it's fixed  in the KB but it doesn't seem like the reports here are supporting that.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.

But what about the "costs" to the end user and reseller by NOT communicating via the KB that the problems has been resolved with this PU or hotfix that you have to jump through Sage legal hoops to get.  At LEAST communicate this end user can make an informed decision on how to proceed.  And so the reseller can do productive things instead of searching for an elusive KB fix or asking on the 90M forum or on the Sage Community.

Communication is a LOT less expensive than burying your head in the sand!

Testing hotfixes for general release have real costs (for Sage, and all developers with enhancements affected by the fix). 

I don't like it, but I do understand why issues not getting lots of complaints will be put on the list for general PU QA testing.

What I find crazy is that it seems many of these bugs are solved by now hidden fixes that you have to encounter on your own then call Sage and get a disclaimer/waiver (not sure why the VAR has to sign these but that's a different issue ).

Then when you are staging an upgrade like Sage 100 2025 you can grab PU1 but I'm always left with this uneasy feeling that I'm probably missing a patch or two.

There's now no way to find these one-off patches since unless they are big enough to embarrass Sage it doesn't seem like the patches are publicly available.

Which makes no sense to me as part of getting a client system all staged for an upgrade.

Didn't Sage say at MOTM 2025 that they finally figured this out & they will be releasing a fix? I have this memory of a grand applause moment... but I can't find it fixed in any PU or hotfix. Was a fix ever published? Did I imagine this all?

This isn't fixed in 2023 PU 2 which is what my client is running.

@Phil McIntosh - we'd love to know... The irritating part is that it is not consistent, i.e. doesn't happen EVERY period end or EVERY Positive Pay or EVERY whatever it is.  Or maybe it IS consistent, but the trigger is that you're standing on your head barking like a dog while right clicking the up arrow and people don't do that every month.  :-)

So is the problem that the user needs bank account permissions and PII, and somewhere in the permissions check it can blank out the fields?

Bank Account Number and the Bank Code Description are missing

Adding this link as cross-reference to a similar report ( if not a report about this issue ). Sage claims it's fixed  in the KB but it doesn't seem like the reports here are supporting that.

I have a client who recently upgraded from 2020 to 2023.2.  She is now experiencing the blank account issue.  She uses Positive Pay.  I have another open case with Sage (8010015279) that Ronnie Aspe and Kent Mackall are involved in.  Kent is going to create a version of the Positive Pay program that keeps a log of any postings to the Bank Code file, but we've done this before on a prior version and got nowhere.

I also have another client on 2021 who just recently started having it happen and they do NOT use Positive Pay, but the BR clerk noticed it happened after updating the Bank Reconciliation Report (purge) at period end.

And I have a third client on 2023.1 who just recently started having it happen and they also use Positive Pay.

We kept thinking it had something to do with Positive Pay, but now I'm thinking it's just that the clients who use Positive Pay NOTICE it because it screws up their file.

This seems to go in spurts.  I have X number of clients who have the issue, then all of a sudden I get several more added to the list.  Very perplexing and irritating.

It's alive!!!!!!

Bank account maintenance Account number field is suddenly blank.  It took several rejected positive pay submissions before the client reached out.  Rekeyed bank account number and resolved positive pay file issue.  Now for the root cause.  Client running 2023.2 SQL with DSD enhancements.  Worked without issue for the past two months.  Then out of the blue - Wham.

Me too.  Keep me posted if anyone finds a fix.