In 2001, Intuit first opened up access to their product data with the introduction of their Software Development Kit (SDK), but it is not a direct connection to the database; rather it is an XML extraction which can be slow on large files.
In 2011, Intuit added an additional Custom Reporting feature for Enterprise users that allowed a more direct access to QuickBooks. It is not an Intuit sanctioned method for extracting data in a 3rd party application and does not include all of the available data.
Intuit does not give developers direct access to the QuickBooks database, but have exposed 98% of the available fields through its SDK
Users often make assumptions that because they 'see' things when they use QuickBooks, that the database operates in a similar logical manner. As you will see below, this is not always the case. Much of it has to do with the logistics of adding volume to a small business application like QuickBooks, other times, it requires complexities that are only found in higher end accounting programs.
Don't assume that because you see something in QuickBooks that it is stored in the database accordingly.
It's shocking to me that QuickBooks, being such a large company, seems to have so many gaps and holes in their system. I would not be surprised if they are the next "MySpace" that is overshadowed by competitors. After I complete this project for this client, I plan to look at alternative accounting solutions... Do you have any suggestions??
Intuit has the lion's share of this market, and will for years to come. Remember that this is off the shelf software for a very cheap price compared to high-end accounting systems that cost tens of thousands to just sniff the package.Is it perfect, no, but they are still the 600 lb gorilla when it comes to accounting systems for the small business owner.
is requesting access to a wiki that you have locked: https://clearify.com/wiki/view/152/quickbooks-desktop-data-availability