A late-to-the-party post but we are just completing a project for a Laserfiche VAR, integrating between LF Cloud and multiple Quickbooks Desktop files. Here's how we did it without the ODBC Connector due to pricing and yearly cost for the ODBC connector: We registered a dev account with Intuit to get a trial Quickbooks Desktop. We created a couple Global Script Rules in LF Cloud - one for pushing Bills to QB Desktop and one for getting Bill Payment updates. On a workstation we installed the remote agent and created a script rules DLL that takes requests from Cloud and generates QBXML requests. Quickbooks Web Connect is the middle layer that allows interaction with Quickbooks Desktop files without needing user interaction. The only part of the installed Quickbooks SDK we use is the XMLValidator tool. We also had to create a custom SOAP web service to communicate between the Script Rules DLL and Quickbooks Web Connect. There are a lot of moving parts which we centralized through a Configuration application and we log events to a location on the workstation, and created email alerts when there is a serious issue. The Quickbooks desktop and QBXML required to interact with it are old tech - requiring SOAP and XML 1.0. One of the issues we ran into is that Quickbooks accounts can contain special characters like "middle period" within Quickbooks, but you can't pass them through an XML 1.0 file. So instead of matching up on description passed from Laserfiche we had to add a layer that gets the ListID and matches the Account Name passed from a Laserfiche Template field to the Quickbooks ListID for that account. Intuit Tech support was no help but in the end it is painful but doable.