All posts

QuickBooks Desktop

The API I built for QuickBooks Desktop

How a Windows connector, a local mirror and a small API made accounting data useful outside the company file.

I run a directory publishing business. A question like “Which unpaid invoices need my attention today?” used to mean opening QuickBooks Desktop, running a report, and checking the inbox to see what had happened since the last follow-up. I wanted the accounting part of that question available from the same place I review the rest of my work.

Start with the company file

QuickBooks Desktop stays in charge of the books. I wrote a connector that runs on Windows and talks to the Desktop SDK through its qbXML request processor. It asks QuickBooks for records such as invoices and payments and copies the fields I need into a database. The API reads from that database, so looking up an invoice does not require opening a QuickBooks session for every request.

That distinction changed what I could build. A dashboard can load a list of open invoices while another job looks up a specific invoice. Both can use the same accounting data without waiting on separate Desktop sessions.

A copy has an age

A mirror tells you what QuickBooks reported at the last successful sync. If a payment came in this morning and the sync stopped last night, a perfectly good query can still give you the wrong answer for today. When that answer could trigger a follow-up, the sync status belongs beside the balance. If the data is stale, the useful result is a flag to check it.

I also had to get specific about what a balance means. A payment on a customer account and a payment applied to a particular invoice answer different questions. I want the software to carry that distinction through to the screen where I decide what to do next.

The first useful outcome

The first thing worth building was a view I could use every day. Once I could get at invoice status reliably, I could put it beside recent correspondence and decide which conversations deserved my attention. That is where the API started saving steps.

The Intuit Desktop SDK documentation is the starting point for the QuickBooks side of the integration.