Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
This has been a vexing problem for our customer and after an hour on the horn with support, I'm really no closer to solving the issues and instead have excuses and workarounds.
Our customer uses Desktop Pro Plus 2021. Both these issues have been occurring for about 3 months off and on, with an upgrade in early January to bring the customer up to date on 2021 with no appreciable change to the behavior.
Bank Balances Don't Agree.
One of the bank balances displayed on the home screen under "Bank Balances" does not agree with the balance in the check register. Just today, when on the phone with support, the home screen's balance was "$-63,100" (yes, negative) and yet the check register, which the user says is accurate, shows a balance of over $80,000.
After running a verify and rebuild at the direction of support (fixing two Error 61s, which we've done in the past), the tech told me this was A-OK, and if it happens again, please just run verify and rebuild again to fix it.
Our customer will use this for a few days and then this will occur again. Seriously, Intuit, this is the answer? Your product's database has a weird corruption that you can't seem to figure out how to solve, so we're just going to punt to the user to fix it all the time?
(I guarantee this is going to happen again, and when it does, the user will call us... And I will do a verify and rebuild... and around the merry-go-round we go. And the user is going to get pissed. She already wants to know what they're paying us for, and why they're paying Intuit for buggy software.)
Check numbers reset to 1 or a low number
When the user writes checks against this same account, the prior check number in the register is a large number (in this case, over 28000). The check number showing in the write checks interface is 6. Yes, 6. (not even, say, 0006 or something)
The user has reset the check number to the correct value several times previously, and at some point, it reverts back to an incorrect value.
Support's answer that this is a "known issue." Quickbooks designed that way so that users who write checks outside of Quickbooks can quickly and easily change the check numbers to accommodate manually written checks and that if the user changes the check number, it will continue on with the right numbers.
Me telling the tech "no, no, she's done this before and it resets back to a small number" apparently fell on deaf ears. This is "a known issue." I get that changing the check numbers is "by design." Perfectly reasonable. But why do the check numbers randomly reset? No solid answer there.
So, hive mind, what are your thoughts on this? Would you accept "just do a verify and rebuild" when the problem occurs? Especially if it occurs over and over?
Why should the user have to fix database corruption each time? Why can't we fix the database?
(whats that old joke about the definition of insanity? Doing the same thing over and over and expecting a different result?)
And this check number thing is annoying, and the answer ("known issue") is a non-sequitor that does not address the problem of the check numbers resetting to some odd value.
Again, why is Intuit punting this into the user's court to fix what is clearly a db issue?
I know this hasn't been an easy process for you, mirador_IT.
This isn't the kind of service we want you to experience with your support.
Not to worry. I'm here to help you resolve this issue. Let's run the File Doctor tool. This helps fix company file issues that may have caused the unbalanced amount.
To start, let's download and install QuickBooks Tool Hub.
Then, we can now run QuickBooks File Doctor.
For further guidance, please see this article: Fix Company File and Network Issues with QuickBooks File Doctor.
As for the check number, I'd suggest resetting it to a low number. If the same result, run the QuickBooks File Doctor.
Additionally, I encourage updating QuickBooks Desktop to the latest release. This keeps the software up-to-date to have the latest features and fixes.
I suggest getting back on this thread if you'll need assistance with the process, I'm always here to back you up. Have a great day!
Did it. We did that _weeks_ ago. Tells me it can't find anything wrong with the file. Every time
After I ran this first thing today,I got the screen shot above before calling support. Later, the verify & repair of the company file that support told me to run found 2 Error 61s.
Can you see why my confidence level is kind of low here?
Hi, @mirador_IT.
I appreciate you for sharing a screenshot after running a file doctor and the error message you're getting. I want to ensure the balances get corrected in no time.
Before we start with a troubleshooting step, I recommend creating a backup of your file to save your data from damages and loss. To back up your file:
After that, you can uninstall QuickBooks and do a clean install to completely fix the company file issues.
To uninstall QuickBooks:
Once done, reinstall QuickBooks Desktop.
For additional solution, you can check out the instructions under Solution 2: Uninstall QuickBooks and manually rename the installation folders.
Then, reopen QuickBooks and check the balances of your accounts.
If the issue persists, you may reconnect with our Support Team. This way, a live representative can check the previous case you had and investigate this message further,
On the other hand, here's an article you can read more to find help with bank feeds and reconciliation.
Please let me know how else I can help you with QuickBooks and your accounts. I'm always here to help. Keep safe!
@mirador_ITI am in the same spot. I've been running daily rebuilds which fixes the error but does not prevent it from happening again the very next time a check is printed. I had to laugh when I read your write up. But it wasn't a "funny" laugh. It was that panicky laugh you make when you are trying to keep yourself from crying, lol. I'll be following this thread closely to see what resolutions arise. Thanks.
I should add something else. This problem began only last week for us and we were running Enterprise 19 at the time. We use Right Networks cloud hosting and the suggested upgrading to Enterprise 21, since it was included in our pricing anyways. So we did the upgrade to 21 but it did not prevent this problem from recurring. They also ran the file doctor on the back end (hosted side) and it came out clean. The very next day the problem began again and I'm stuck in that same loop of running a rebuild and then needing to do it again after any activity occurs in the checking register.
Oh, and one more thing. This morning I thought about checking for updates. I went to Help and then Update Quickbooks Desktop. On the update now tab I do see that there is a feature update in the queue. But I cannot get it to install. The instructions say that I need to close and reopen QB and that will prompt the install to begin. I've done this several times, even with admin single user and have seen no action. Don't know if this is related or not, but I'm kinda grasping at straws at this point.
User has logged in and the bank balances agree for now. Check number is still at 6, so I am assuming she has not written a check yet.
If the bank balances stop agreeing, they will do it pretty quickly, like in the next day or so.
If it wasn't funny, you'd be sitting in a corner rocking back and forth repeating to yourself "no, its not me, its the application.."
Lets see if the user gets any resolution. this is the 2nd reinstall for the product, but hey, we'll do it.
@mirador_IT I just finished another round with QB Enterprise support. We pulled the QB file down to a local file and set up the file doctor from the tool hub. It came back clean. Then we ran the Advanced File Doctor. This was a new one on me and you may want to try it too. When you are setting up the file doctor and select the file, before pressing Continue, press Ctrl + A. The options will change and you have access to the Advanced File Doctor which will do an even deeper analysis and repair. I just finished up putting our file back in Right Networks and we will see if we can break it again. Fingers crossed!
lol
@mirador_ITafter only 10 minutes our bookkeeper was able to break it. Began seeing the same errors "QB found a problem with your bank account number."
The enterprise support person told me that if this last repair didn't fix things and the problem were to recur, then we have two options: 1. send the file to Intuit Data Services or 2. Start a new company file. He said that if Data Services (which will take 3-5 days, by the way) is unable to repair the file then our only last option is to start a new company file.
When you hit F2 inside the company file you can see version history. As it turns out we have been using the same company file since 1997. This is another indicator that we really should start a new company file. Our file size is 750mb which they said was significant but not too large to cause problems.
@mirador_ITI wanted to circle back on this. I opted to start a new QB file completely. I worked my way up to level 2 Enterprise tech support and they discovered that we have been using the same company file since 1997. It wasn't overly large in size but they said that is too long a timeline and recommended a new file.
I grabbed a copy of Transaction Pro Importer/Exporter and used that to pull 15 months of data and all of the lists out of the old file. Then saved the old file as historical reference. Imported everything into a new file. You'll have to recreate all of the customized settings and things that aren't imported, but you start fresh. Its a lot of work to get the starting balances equal the ending balances from the old file, but I suppose that will vary from company to company.
One last tip: I watched a bunch of YouTube videos from Hector Garcia on how to do all this. His info was better than TPI's own support.
Good luck.
You have clicked a link to a site outside of the QuickBooks or ProFile Communities. By clicking "Continue", you will leave the community and be taken to that site instead.
For more information visit our Security Center or to report suspicious websites you can contact us here