quickbooks data – Cooper Mann Consulting

August 25, 2025

Maximize QuickBooks Performance with Proper Data Maintenance

Millions of businesses around the globe use QuickBooks software for their accounting. With an estimated 84% of the small business accounting market making the buying decision to go with it, QuickBooks has enough product momentum and functionality to support small businesses through midmarket customers.

This is a broad base of customers for any accounting product, and the continued popularity of QuickBooks Enterprise is a testament not just to the application’s usefulness, but to the large gap that exists in the space where QuickBooks Enterprise desktop leaves off and the well-known enterprise ERP systems start.

Initially, a business will implement their accounting system to keep track of customers, vendors, items, and cash. More detailed processes are then introduced as the business requirements grow, such as tracking more specific information on the costs of certain products, or drilling into customer purchases or item sales activity to see more details. This additional data provides a much more informed basis for business decision-making but also has impacts on systems and software as the volume of data to be managed grows.

Data growth can happen in many ways. Growth can occur in the number of products or services offered, growth in the number of transactions processed regularly, growth in the dollar value of transactions, or growth in the number of employees who need access to the system. Each impacts the ability of the system to continue to support the business requirements, but not necessarily in a way that isn’t manageable.

Given enough time, a certain “density of data” will eventually be reached, causing the system to lose efficiency in manipulating the file. The business process requirements may not have changed, just the size or condition of the file and data. The file opens slower, operations slow down and processes take longer, the system crashes frequently or has errors, and the usefulness of the product is severely diminished.

Keeping the QuickBooks data maintained and in good condition will improve performance and increase longevity of the application.

Too often, businesses assume they have outgrown their QuickBooks software because it is slower or has problems when they begin using additional features. Frustration sometimes even turns to looking at changing the accounting software entirely. Yet experience has shown that many of these situations are solved with some data file maintenance and repair, and sometimes a little re-training or setup work.

Regular file maintenance and a little housekeeping can keep a QuickBooks file in good working condition for a long time. Regular backups with a complete verification and other routines will clean up the file and help the software manage the file more efficiently. But there are limits to how much data a single QB company file can hold, so it is wise to consider starting a new file every few years, just to keep the file manageable. This in no way means abandoning any data, as previous files can be retained and available to open and view at any time. How many years of data you can store in a QB Enterprise company file depends on a number of variables, and can range from a few to many.

While QuickBooks is very easy to use compared to most accounting products that service this small/medium enterprise market, this is both a benefit and a bit of a problem. Many users aren’t really trained in accounting, they are trained in how to operate QuickBooks. Moreover, the knowledge of how to make something work in QuickBooks doesn’t always translate to either proper use or to proper accounting. Even if it is simple to accomplish something in QuickBooks, it is always wise to get a little confirmation of the setup and training on proper use.

For a QuickBooks Enterprise desktop customer, the next step up in software is a big one no matter what, and it would come with drastic change, require data conversion (or abandonment), and incur high costs in licensing, implementation and training services. If there is a good business purpose to make such a change, then it makes sense. But bearing the significant costs of change may not make sense if the problems are centered on poor housekeeping or improper usage.

Mendelson Consulting’s team of QuickBooks Enterprise experts and ERP consultants can help your company get your data file and QuickBooks operations in the condition they need to be. With data file analysis tools and numerous methods for dealing with QuickBooks data and operations issues, Mendelson provides the services businesses need to continue success with QuickBooks. And, if we find that you have outgrown what a QuickBooks-based solution can do for your business, we’ll have that conversation, too.

jm bunny feet Make sense?

March 8, 2022

Good Housekeeping for Healthy QuickBooks

QuickBooks desktop software is very easy to install and use, and that is precisely why it is the standard for small business bookkeeping and accounting. QuickBooks is simple to use.

Getting QuickBooks on your computer is also simple. You can just buy the software from wherever – your QuickBooks solution provider, a retail outlet or an online store. Then you download it to your PC and run a setup application, and voila! It’s there on your PC ready to help you do your books.

When just a single user needs to use QuickBooks, things are very straightforward because there is no networking to worry about and no multi-user access required. On the other hand, there are many businesses using QuickBooks that experience a lot of frustration with trying to install QuickBooks on a network and managing the software that must be installed on multiple computers.

Other than networking QuickBooks desktop software, it seems that the majority of issues users experience can be attributed more to poor software habits and a lack of PC housekeeping

QuickBooks desktop software has been engineered over many years to be as simple to use as possible, but at the same time has grown to be a product with lots of features, add-ons and extensions. People have found ways to make QuickBooks do things it wasn’t really designed to do, which is sometimes a good thing and sometimes a bad thing. When it works, it works great. When it doesn’t work, it’s beyond frustrating.

Yet there are a few things that QuickBooks desktop users should be doing regularly to keep their QuickBooks software and data in good working condition. While these items are very important to keeping your QuickBooks system working for you, they will never overcome problems with your network, the server or any of the workstations connected to it.

To solve these networking, software management and other IT platform issues, I recommend moving to a virtual cloud server on the Microsoft Azure cloud platform. NOOBEH’s QuickBooks on Azure service is just that… your QuickBooks software and data running securely on your own private cloud server in your own account on the Microsoft cloud, fully managed and supported by experts. With NOOBEH’s service, you don’t have to worry about server failures, network problems or hardware problems any longer, and we eliminate the issues surrounding multi-user, multi-location, and remote access for QuickBooks.

When it comes to PC housekeeping and other chores, I cannot stress enough the importance of keeping the QuickBooks company file in good condition

What’s the accounting and financial data worth, after all? A little time spent taking care of the file can save on a lot of time and headaches trying to recreate or reenter the data. A QuickBooks company file is a database and is a complicated framework for keeping track of all sorts of related information. Anyone who has used QuickBooks desktop products for a while understands that the data file can get messed up for a variety of reasons, and it can mean lost time, work and revenue when it isn’t working correctly.

What many users don’t realize that QuickBooks has built-in utilities to check and fix data problems in the company file, so it makes sense to periodically use them to check for problems. Like a check-up with the doctor, these utilities can help diagnose issues with the data file before they become big issues. They are easy to find in the software… simply go to the File menu and select Utilities.

Run the file Verify any time the file starts to act slow or if QuickBooks crashes when the file was open, and if the Verify tells you there are errors, you should run a Rebuild to fix them. Note that a rebuild may have to run multiple times to fix all the issues in the file, and even then, may not correct everything. Some manual work may even be required to resolve all errors.

You should also back up the company file to a “portable” type file periodically, and to then restore it for use. This doesn’t need to be done very often, maybe once a year or so. This process can not only validate the integrity of the file, but it also helps condense and condition the file. Conditioning the data file periodically can help prevent data corruption and/or loss of data.

A very important housekeeping item for QuickBooks desktop is the file backup. Backups don’t just make copies of your company file for safekeeping, which is important to have, but when you run a backup with complete/full verification, the process also reduces the file size of the TLG file. For QuickBooks, the TLG file is a transaction log, and when it gets too big the file can perform poorly and even get corrupted. Run backups more frequently if you have a lot of transactional activity, or less often if there is not so much going into the company file.

When you do the file backup, it is a good idea to consider where the backup will go. Keeping the backup files on your PC is convenient, but it also does nothing to protect your data if your PC gets hit with malware or has a hardware problem. Put the backup file in a protected location that isn’t stored on your PC, like Microsoft OneDrive, Google Drive, Dropbox or even a removeable USB device. You can’t put your live QuickBooks company file in this type of location, but you can store the backup files there. This way, if your PC does have a problem, you’ll have backups of your company file that you can use to get yourself back in business.

Close the company file and exit QuickBooks occasionally, please

Users who leave their computers on all the time are not allowing the computer to run periodic power-on self-tests, which means the machine or operating system could have an issue that isn’t recognized until computer restarts. For this same reason, programs and their data files should be closed when not being used – so they can run through their own startup and validation routines before you use them. Also, leaving the program open means it is active on the computer, and leaving the data file open means that it’s available (available=vulnerable). A random by passer accessing the computer, a program crash, a machine crash… loss of power or a furry kitty running over the keyboard could each result in catastrophic damage to the application and/or data. It’s just better and safer if the files and programs are closed when not being used. Maybe use a screensaver with a password, too, or at least lock the keyboard when the machine is on but not in use.

QuickBooks and VPN / WAN are not awesome together

Just because a user can connect their remote PC to the office network doesn’t mean the PC will work like it’s in the office. In the office, it’s a Local Area Network where the machines are all cabled together and communicate with nearby machines (e.g, Local). The speed of LAN communications is fast enough to allow multiple computers to share a QuickBooks company file in multi-user mode. When there is a remote PC to connect, businesses often elect to utilize a VPN to provide local area network access to the remote computer. This turns the Local Area Network connection into a Wide Area Network connection, where the network has been extended to include the remote computer.

Unfortunately for QuickBooks users, the WAN connection is NOT fast enough to allow the remote user to open QuickBooks and use it like others in the network. QuickBooks multi-user access is designed to work on a local network where local means the machines are in the same locale and on the same LAN. This is why many companies elect to use remote-access/remote-control software to access to QuickBooks desktop remotely.

Use NOOBEH QuickBooks on Azure to get remote access, managed service, update support, and the ability to run any other applications or add-ons your business needs. When QuickBooks desktop and the other software a business uses are hosted on the company’s Microsoft cloud server with NOOBEH, the QuickBooks application and the company files are all on the same environment so it works exactly as it is supposed to for all users no matter where they are located.

Use Automatic Update

New features and enhancements are provided, new technologies and operating platforms must be supported, and security and privacy must constantly be addressed in the software. What this all means is that software products necessarily change over time and users will be expected to update their products or lose out. While some IT departments may desire to prevent software from updating itself, QuickBooks users should recognize that the software’s proper function often depends on timely updates. Especially when payroll or banking is involved, it is important to keep the software current.

QuickBooks has a feature that allows the software to automatically download and install updates as they are released by Intuit. Leaving this feature turned on allows the software to check with Intuit periodically to see if there are updates available. If so, they are downloaded and readied for installation on the computer.

Updates are changes made to an edition and year version of the software. Upgrades, on the other hand, are changes from one year version to another (2021 to 2022, for example) or a change in QuickBooks edition (like Premier to Enterprise). Automatic updates manage the changes to the currently installed edition/year version, but do not upgrade the software.

Customers using NOOBEH’s QuickBooks on Azure service have their QuickBooks updates and their QuickBooks upgrade installations managed for them, as well as the other applications installed on the customer’s private cloud server.

Doing maintenance on your QuickBooks software and the company file can help keep them free from poor performance and potential corruption

It’s worth spending a little time on chores occasionally so that you avoid what could be a costly problem down the road. Some good housekeeping to keep your QuickBooks healthy is just good business.

jm bunny feet Make Sense?

January 26, 2016February 3, 2016

No REST for QuickBooks Desktop Integration Developers

Intuit, the maker of QuickBooks small business accounting software (among other things), is discontinuing service for the REST API and the Sync Manager on March 1, 2016 [1]. Developers with applications which integrate with the desktop editions of QuickBooks using this method must change their approach right away or risk having their integrations simply stop functioning. It’s not that Intuit will DO something on March 1^st. Rather, they’ll stop doing something – like handling Sync Manager integrations.

There are a lot of different types of businesses in the world, and each of them produces and consumes a lot of information. From sales to human resources; from operations to finance – every business generates and manages information to support the various processes which make up the business activities. Computer systems and software represent the tools businesses use to develop and manage information, and often become foundations for structuring the information which flows through the organization. Just as there may be different people in the business, each with their own responsibilities and job functions, there are likely software applications which are similarly oriented to support different processes within the business. Integrating or connecting different applications and processes within the business helps the organization be more efficient with information usage, generally increasing the quality of access and reporting throughout the business while at the same time reducing or eliminating redundant data entry and the potential for errors. Software integrations are a big thing to many businesses, which is why the discontinuation of Intuit’s Sync Manager for QuickBooks Desktop editions is a big deal.

Intuit’s Sync Manager was the big thing just a few short years ago. Providing developers with a seamless method for accessing QuickBooks company data and passing it to/from web-based and other applications was a boon to the online application model and paved the way for many disk-based integrated solutions to migrate to SaaS offerings instead. Developers who saw success operating in Intuit’s QuickBooks marketplace as recognized add-ons were encouraged to use Sync Manager so that they would be able to seamlessly market to, subscribe and onboard new users who purchased QuickBooks products. Whether or not the developer participated in Intuit’s application marketplace, the Sync Manager and the REST API provided them with some very important capabilities and supported new methods now recognized as “standards” for development of web-based solutions and services.

The World Wide Web has succeeded in large part because its software architecture has been designed to meet the needs of an Internet-scale distributed hypermedia system. The modern Web architecture emphasizes scalability of component interactions, generality of interfaces, independent deployment of components, and intermediary components to reduce interaction latency, enforce security, and encapsulate legacy systems. http://dl.acm.org/citation.cfm?doid=337180.337228

In order to integrate a solution with QuickBooks desktop products, there are two essential problems to solve. First, there must be access to the QuickBooks data. Few products are able to directly access the data in a QuickBooks data file; generally, the QuickBooks program itself is used to ‘broker’ access to the company file. So, developers need a way to work inside of QuickBooks to use it to access the data their applications need. Second, the data must be transported (via the Internet) to allow for data to come from QuickBooks into another app, or to allow data from the other app to come to QuickBooks. The REST API and the Sync Manager addressed both of those problems and provided developers with the mechanisms required to facilitate the data integration as well as transport the data.

REST (representational state transfer) is “the software architectural style of the World Wide Web [2]” and represents a standard for creating scalable, distributed system interactions. Using this method, developers were able to make their online solutions access, read and write data in QuickBooks desktop products because Intuit had first sync’d the data to its servers, so developers needed only to reach the Intuit servers to reach the data. The Sync Manager provided the transport, carrying the data to/from the desktop installation where the Sync Manager service was running. And, because the Sync Manager was basically built-in to QuickBooks, there was no additional software to install and maintain on the computer because it was all part of the QuickBooks installation.

Intuit did a fantastic job of getting developers to move to the API integration method, positioning all those lovely 3^rd party solutions for linkage via an Intuit.com account and, now, to QuickBooks Online. Intuit is clearly favoring the QuickBooks Online edition and the API integration method available with that platform, and is telling developers that they must convert their customers to QBO in order to retain the easy connective ability they had with the desktop editions via Sync Manager.

Now that Intuit has announced the discontinuation of the REST API and the Sync Manager, what options do QuickBooks integration developers have, and how can customers using 3^rd party integrations keep using them? Options do remain, and they aren’t all that bad. In fact, the options which remain continue to be the methods of choice for certain developers. These developers recognized early on that Intuit’s somewhat “lightweight” methods couldn’t handle the complexity or full functionality of their integrations facilitated their solutions using the SDK and never looked back (and still don’t). For this community of developers – many of whom likely never considered trying to market their solutions in the Intuit app marketplace – the elimination of the REST API and Sync Manager don’t really matter. They didn’t bother with them in the first place, just as they aren’t bothering with QBO. Those solutions don’t fit their customers, anyway.

The QuickBooks desktop SDK (Software Development Kit) has been around for years, and using the SDK developers have been able to craft tight integrations between their solutions and the QuickBooks desktop products. From payment plug-ins to fully integrated sales, customer relationship, inventory and manufacturing solutions – a broad range of integrated applications built with the SDK have been successfully deployed to QuickBooks customers all over the world. Many applications which integrate with QuickBooks desktop solutions are desktop products themselves and are designed to work within the same desktop and network environment as QuickBooks, so there is no need to worry about “transport” of the data over the Internet.

For other solutions, such as online applications and services, there may be a need to exchange data via the Web. The QuickBooks Web Connector has also been a very popular solution for developers of applications that integrate data with QuickBooks. The Web Connector is just what its name implies: it is a way to connect QuickBooks to the web and vice versa. With the Web Connector application and a web connector configuration file, developers could provide a method of exchanging data between QuickBooks desktop and another solution fairly simply. While the Web Connector is quite useful in providing a means to transport integrated data to/from the QuickBooks desktop to an external system (like an online application), it only allows access to whatever data Intuit decides. For this reason, many developers use both an SDK application and the Web Connector so their applications can access all data required and also have a web service available to transport it.

There are numerous implications relating to the sunset of QuickBooks REST API and Sync Manager, and another among them is the impact in hosted environments. For customers who are (or might) benefit from hosted QuickBooks delivery models, what does the end-of-life of the Sync Manager mean? Since the Sync Manager was basically built into QuickBooks desktop editions, it meant that there wasn’t any extra software to install or manage when a company wanted to adopt a Sync Manager-based 3^rd party integrated solution. In a hosting environment, this means that the customer could easily add integrated applications to work with their hosted QuickBooks and the service provider might never even know it was being done. There would be no additional software to install on the host servers; so many providers would simply be unaware that their customers were using these other solutions.

As developers return to SDK and Web Connector implementations in order to integrate with QuickBooks desktop, customers will ask their hosting providers to install the QWC (QuickBooks Web Connector) and/or integration software in their service. In shared service delivery models, this may be virtually impossible to do without potential compromise to existing customers using those servers or other applications resident on the systems. Hosting customers will not always understand that a “simple plug-in” actually represents installable software that must be secured, maintained, managed, and kept from improperly interacting with other software in the environment. Some providers may not even be willing to work with the new integration software, while others may allow it but will not take adequate precautions to ensure proper and secure function.

Intuit has said to many constituent groups that its focus on desktop editions of QuickBooks will continue, and new certifications and benefits for desktop ProAdvisors (and continued development of interoperability with other solutions, like the Revel POS integration for QuickBooks desktop) give support to those statements. Yet developers who support integrations with QuickBooks desktop are once again adjusting to the not infrequent changes Intuit makes to developer programs and philosophies. The push to QBO and connected apps may be the focus for QuickBooks marketing dollars, but there are still quite a number of (very busy!) developers supplying solutions to businesses who don’t shop inside their QuickBooks software.

Joanie Mann Bunny Feet Make Sense?

[1] https://developer.intuit.com/blog/2014/09/08/timeline-to-discontinue-the-quickbooks-desktop-rest-api

[2] https://en.wikipedia.org/wiki/Representational_state_transfer

January 11, 2013

Trends Impacting Every Business | Forbes.com

You think good accounting isn’t a big factor in getting business credit? Consider this tidbit from Intuit’s CEO Brad Smith, from a recent article on Forbes.com:

Two-thirds of Intuit’s QuickBooks customers were declined a loan due to poor FICO scores and other credit measurements. In the Loan Finder trial, a business could opt-in to allow banks to use QuickBooks data to evaluate if a prospect was a credit risk. As a result of this additional data, the banks provided several hundred new loans with an average of $10 million dollars.

Accounting professionals… isn’t this something you could be helping your clients with?

Read more about helping make small businesses bankable

Make Sense?

Read more about how accountants need business intelligence, too
Read more about how there’s no fear and loathing in accounting
Read more about the pressure on accountants to deliver more value and intelligence to their clients
Read more about Data Warriors: accounting in the cloud

November 19, 2012

Simultaneous Syncing Sinks Solution: Extend Access but Control Integrations

Accounts and ProAdvisors: Make sure you “enable” only those who need it

In this wonderfully interconnected world of hosted and online applications and the integrations which complement them, it is important to not let the excitement of connectivity and collaboration replace reasonable control. While there is much conversation on this topic when it involves file sharing and similar services, the discussion of data synchronization and data integration doesn’t often come up. However, it has been my experience that there is usually a misunderstanding in how, exactly, a particular sync or integration should be applied and who should have access to the functionality when it is deployed as an extension of the QuickBooks desktop financial software.

An example of the problem might be seen when QuickBooks desktop editions are set to integrate or sync data with a web-based solution such as Method Integration or Santrio Open for Business Order Bridge. Solutions like these, which extend the functionality of QuickBooks through extending access and integrating data, rely upon QuickBooks integration functionality move data between their solutions and the QuickBooks database. These solutions are quite beneficial for businesses because they can affordably deliver support for various business functions via a true web application and incorporate QuickBooks data in those application views. Additionally, this type of solution is able to push information from the web application to QuickBooks, allowing for complete integration of financial and other relevant data.

While having this type of integrated service is beneficial, there are a lot of businesses who don’t fully understand how to appropriately implement the solution and end up creating a great deal of difficulty for themselves. One of the most frequent failures I have seen when implementing this type of solution is where the customer doesn’t really understand who should or should not have the integration.

When a web-based solution exchanges data or syncs with QuickBooks, a path is created to communicate between the two systems – the web solution and the QuickBooks application and data file. This path must be open, and both sides of the communication identified, in order for data to sync. The most important thing to remember is that there should be only one controlling entity on each side handling the integration. What this means for QuickBooks users is that only one installation – one PC accessing QuickBooks – should be configured to facilitate the primary integration with the QuickBooks company file.

To illustrate, consider an implementation of Method Integration and QuickBooks that was done for a business some time ago. This business used Method-based applications for a variety of business functions, and those applications used data sync’d from QuickBooks desktop. Just after implementation, it was discovered that system sync’s were not happening as they should, and sometimes when they went to sync data, it would take a huge amount of time (which was not supposed to be normal behavior). In short, the system proved to be problematic and, at times, unusable. But the problem didn’t have anything to do with the Method Integration system, nor the technology.

The problem was that all workstations in the office were set up to sync data between QuickBooks and Method. QuickBooks was installed on all the PC’s, even though most of the users did not use QuickBooks (they used the Method Integration system to do their jobs), and each PC had the Method Integration sync engine installed and set up to run. This caused the system to be frequently overloaded with sync requests and caused QuickBooks to behave erratically or crash. In addition, users who did not need (and should not have had) access to QuickBooks financial information were starting up QuickBooks and opening the company file every day because they thought it was required to allow them to access or use QuickBooks data in the Method Integration system.

The benefits of using web applications which can connect to and integrate data with QuickBooks is that a business can give users functionality and data access required to get the job done, but not expose those users to more software or data than they need. In most cases, if not all, QuickBooks is not necessary for users of the web application (saving you the cost of purchasing and installing QuickBooks for these users). Further, to ensure proper functionality and to remove any possible conflict or confusion in the sync process, only one workstation with QuickBooks should be set up to sync data to/from the web solution. While it makes sense to have a “backup” PC setup with the ability, syncing should remain inactive on this machine unless the primary “sync machine” is out of service. The key element to remember here is that the data coming from the web application is being added to the QuickBooks company file. Once the data is in QuickBooks, QuickBooks users may access the data from QuickBooks and do not need the connection to the web application.

When deploying this combination of solutions with a hosting service provider, the same rules will apply. Only users who need the sync capability require service with both QuickBooks and the integration installed. In some cases, this may make selection of host services more affordable, as only those who need the “additional application” (being the sync solution or integration tool) require customized service, and the rest of the QuickBooks-only users need standard QuickBooks service. *It might also be worth noting that many hosting providers do not support “persistent” connections – sync connections which continue to run even when you are not logged in), so syncing of data would only be able to occur if the primary user was logged in to QuickBooks and had the sync integration active on the host solution.

Accounting professionals, QuickBooks ProAdvisors, and small business consultants can help their clients understand the value and potential of extending QuickBooks desktop editions with connected web-based solutions. The additional value these professionals bring to the conversation is the understanding of the need for structure and control of the data flowing into and out of the financial systems, offering their expertise to ensure that the accountability and appropriate treatment of the information exists throughout the business.

Make Sense?