QuickBooks that stops corrupting

QuickBooks has been at the center of small business accounting for decades, and it has particular requirements that it does not announce clearly. Most of the QuickBooks problems we are called about are not accounting problems at all. They are network, permission or file-hosting problems presenting as accounting problems.

Multi-user mode, which is where it usually goes wrong

QuickBooks in multi-user mode is genuinely sensitive to how the company file is hosted and how the network behaves. The Database Server Manager has to be installed and running on the machine holding the file. Folder permissions have to be correct. Specific ports need to be open. And the file should be on a wired connection, because Wi-Fi packet loss that no other application notices will corrupt a QuickBooks file over time.

When a business tells us QuickBooks is slow, drops users out, or reports the file is in use when it is not, the cause is almost always one of these four things. They are entirely fixable, and they are also entirely invisible unless someone knows to look for them.

File corruption

Company files can be repaired, and the outcome depends heavily on how quickly the problem is caught and whether clean backups exist. We run the verification and rebuild process, work through the log to identify what is damaged, and where necessary restore from backup and re-enter the intervening transactions. What we will not do is promise a perfect recovery before examining the file, because that is not a promise anyone can honestly make.

Hosting decisions

There are three reasonable places for a QuickBooks company file: on a local server, on Intuit's hosted platform, or with a third-party hosting provider. Each suits a different situation. A single-office business with a healthy server often does best locally. A firm with people in four states usually does better hosted. We lay out the actual cost and performance implications rather than pushing whichever we would prefer to manage.

Year-end and tax season

For accounting firms, February and March are when everything must simply work. We plan around that: no non-essential changes during the busy period, backup frequency increased, and response prioritized for clients whose season it is. Scheduling a server migration for an accounting firm in early March would be a self-inflicted wound.