QuickBooks Desktop

QuickBooks Desktop is an accounting software for managing and controlling finance-related processes for inventory-based businesses that need to scale as they grow. Skyvia supports QuickBooks Desktop 2006 and higher.

QuickBooks Desktop connections can work only via Agents. QuickBooks Desktop must be installed on the same computer, on which the Agent application is installed.

Data integration: Skyvia supports importing data to and from QuickBooks Desktop, exporting QuickBooks Desktop data to CSV files, replicating QuickBooks Desktop data to relational databases, and synchronizing QuickBooks Desktop data with other cloud apps and relational databases.

Backup: Skyvia Backup does not support QuickBooks Desktop backup.

Query: Skyvia Query supports QuickBooks Desktop.

For QuickBooks Online connector, see QuickBooks Online.

Establishing Connection

When creating a QuickBooks Desktop connection, you need to select an Agent, installed on the same computer with QuickBooks Desktop instance, and specify the Application Name and Company File.

Requirements

Skyvia Agent bitness must correspond the bitness of the QuickBooks Desktop instance. Note that Skyvia Agent installs both 64 bit and 32 bit versions on 64 bit systems, so you can run the corresponding Agent app version.

Creating Connection

To connect to QuickBooks, perform the following steps:

1. Select an Agent, installed on the same computer with QuickBooks Desktop instance.

   

2. Specify the Application Name, for example, Skyvia. This name will be displayed in the QuickBooks Desktop prompt to grant or refuse access to the data.
3. Specify the path to Company File — a QuickBooks company file that saves all of your financial info, for example C:\Companies\sample\sample_product-based business.qbw. By default, QuickBooks Desktop stores company files in the C:\Users\Public\Public Documents\Intuit\QuickBooks\Company Files folder. This is not required if you plan to connect to a file, currently opened in QuickBooks Desktop (QuickBooks Desktop must be running, the file must be opened in it, and you must select the Yes, whenever this QuickBooks company file is open mode in QuickBooks Desktop on step 5.).

4. Click Test Connection. Skyvia connects to QuickBooks Desktop, and the corresponding prompt displays in it:

   

5. Select how Skyvia is allowed to access QuickBooks Data. We recommend selecting Yes, whenever this QuickBooks company file is open or Yes, always; allow access even if QuickBooks is not running.

   The Yes, whenever this QuickBooks company file is open mode does not require the company file specified, but it requires QuickBooks running.

   In the Yes, always; allow access even if QuickBooks is not running mode, QuickBooks will run automatically as a background process when you access the QuickBooks data.

   In the latter mode, you may not be able to open the file in QuickBooks Desktop after Skyvia works loads data from or to it. In such case, after Skyvia finishes loading data, restart the Agent application to correctly close session.

6. Optionally select the Allow this application to access personal data such as Social Security Numbers and customer credit card information checkbox. This allows Skyvia to work with certain fields like the CreditCardInfo* fields in the Customer object.
7. Click Continue, then click Yes, and then click Done.

After this, the connection is ready. You can switch back to Skyvia, save it and use it.

Additional Connection Parameters

Sometimes, when performing INSERT or UPDATE operation against QuickBooks Desktop, it may not assign values to some of the mapped fields. In such cases, QuickBooks Desktop sends a warning. By default, Skyvia ignores QuickBooks warnings, and doesn’t display them in logs.

You can clear the Ignore Warnings checkbox in the Advanced Settings in the connection editor to change this behavior. If this checkbox is not selected, QuickBooks warnings are treated as errors. This means that Skyvia treats records, for which QuickBooks Desktop returned a warning, as failed and adds them to error logs, even though the records were added/partially updated in QuickBooks Desktop.

Revoking Access

If you want to revoke granted access and disconnect Skyvia from QuickBooks, you can revoke access in QuickBooks Desktop Preferences. From the Edit menu, select Preferences. In the opened Preferences dialog box, switch to Integrated Applications.

There, on the Company Preferences tab, you can see and manage the list of application, for which access is allowed to this company file. You can revoke access by removing the application from the list or see its properties and manage access rights.

Connector Specifics

Object Peculiarities

Charge

The INSERT operation requires mapping either the CustomerName or the CustomerId field and either the ItemName or the ItemId field.

Checks

The INSERT operation requires mapping either the AccountName or the AccountId field and either the LineItems or the ExpenseLines fields. Consider the account type when importing records to this object. If the account doesn’t support checks, you receive an error.

CreditCardCharge

The INSERT operation requires mapping either the AccountName or the AccountId field, either PayeeEntityId or PayeeEntityName and either the LineItems or the ExpenseLines, fields. This object supports the inserting of records for the credit card account type only.

CreditCardCredit

The INSERT operation requires mapping either the AccountName or the AccountId field, either PayeeEntityId or PayeeEntityName and either the LineItems or the ExpenseLines, fields.

Complex Structured Data

Some of the QuickBooks tables store complex structured data. These are the following tables: Charge, Check, CreditCardCharge, CreditCardCredit, Invoice, Estimate, Bill, CreditMemo, JournalEntry, Payment, PurchaseOrder, SalesOrder, SalesReceipt.

For example, an invoice or bill can have several lines. Skyvia represents this information in such tables as a JSON field LineItems. Here is an example of the LineItems field value from the Invoice table:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
[
  {
    "Id": "3B1F-1071532020",
    "IsItemGroup": false,
    "ItemId": "30000-933272655",
    "ItemName": "Removal",
    "Desc": "Removal labor - strip damaged roof on garage",
    "Quantity": 46.0,
    "Rate": 35.00,
    "ClassId": "40000-933272658",
    "ClassName": "Remodel",
    "Amount": 1610.00,
    "SalesTaxCodeId": "20000-999022286",
    "SalesTaxCodeName": "Non"
  },
  {
    "Id": "3B20-1071532020",
    "IsItemGroup": false,
    "ItemId": "10000-933272655",
    "ItemName": "Framing",
    "Desc": "Framing labor - reconstruct low pitch roof",
    "Quantity": 20.0,
    "Rate": 35.00,
    "ClassId": "40000-933272658",
    "ClassName": "Remodel",
    "Amount": 700.00,
    "SalesTaxCodeId": "20000-999022286",
    "SalesTaxCodeName": "Non"
  },
  {
    "Id": "3B25-1071532020",
    "IsItemGroup": false,
    "ItemId": "D0000-933272656",
    "ItemName": "Subs:Roofing",
    "Desc": "Roofing - weather proofing and shingle materials applied",
    "Rate": 855.00,
    "ClassId": "40000-933272658",
    "ClassName": "Remodel",
    "Amount": 855.00,
    "ServiceDate": "2007-03-28T00:00:00Z",
    "SalesTaxCodeId": "20000-999022286",
    "SalesTaxCodeName": "Non"
  }
]

For user convenience, lines of these objects are also available as separate records via read-only tables with names containing LineItem suffixes, like InvoiceLineItem, BillLineItem, etc. They allow you to view these lines in a tabular form with Query, export them to CSV with Export, import them from QuickBooks to a cloud application or database, where these lines should be stored in a separate table, etc.

Since these tables (that have the LineItem suffix in their name) are read-only, they are not available in Import packages as a target or in Synchronization packages. To modify lines of a bill, journal entry, etc., you need to provide values in JSON format for the Lines field of the corresponding main table - Bill, JournalEntry, etc. For example, to import bills from a CSV file to QuickBooks, you need to specify bill lines in the JSON format in one of the CSV file columns and import this file to the Bill table. You need to map the Lines field of the Bill table to this column of the CSV file.

You can use our Nested Objects mapping feature in Import packages. For this, you need to select the Nested Objects checkbox in the package. Then, in the mapping settings, you can map the fields of the corresponding line items. See see QuickBooks Online tutorials to know how to use this feature. Additionally, you can use Nested types feature of Data Flow.

Incremental Replication and Synchronization

Synchronization and Replication with Incremental Updates enabled are not supported for objects without TimeCreated or TimeModified fields.

Supported Actions

Skyvia supports all the common actions for QuickBooks Desktop.

Troubleshooting

Retrieving the COM class factory for component with CLSID {45F5708E-3B43-4FA8-BE7E-A5F1849214CB} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).

This error means that QuickBooks Desktop is either not installed on the computer with Skyvia Agent running or is incorrectly installed on this computer.

1. Make sure that you have selected the correct agent in the connection.
2. Make sure that the agent app is installed and running on the computer with QuickBooks Desktop, and that it uses the correct key — the key of the agent, selected in the connection.
3. Make sure you are using the agent app of the same bitness (32bit or 64bit) as your QuickBooks Desktop instance.
4. If everything is correct, this probably means that QuickBooks Desktop is installed incorrectly. Please reinstall QuickBooks Desktop and try again.

Could not start QuickBooks

This error can be caused by the similar reasons as the previous one, so please check the above solution. Additionally, it can be caused by QuickBooks running on a different user level than the agent app. They both need to be running as a normal user or both running as administrator, but not mixed. You can also see the QuickBooks documentation on this issue.