Keep QuickBooks Desktop. Add the field workflow it needs.

QuickBooks Desktop can remain the centre of the books. It already holds customers, invoices and payments. The missing piece sits between the incoming call and the reviewed invoice, where paper work orders and office calls carry the job.

We build that bridge with Intuit’s QuickBooks Desktop Web Connector, so the office PC keeps its accounting record while technicians work from their phones. The case study walks through the build for one small crew, and the pattern here holds for any HVAC shop running QuickBooks Desktop with dispatch stuck on paper.

Where the price gets typed twice

The old route began with a supplier invoice. Office staff wrote the material markup onto a physical work order. The bookkeeper later entered that work order into QuickBooks Desktop, which created a second chance for a missed line or a wrong digit.

A pricing queue now sits before the connector. The office reviews every completed job and applies the shop’s rules once. Four fields live on the customer record: labour rate, minimum call hours, materials markup and service charge. Staff can override them for a customer when the agreement requires another price.

After review, the job waits for QuickBooks Desktop Web Connector. The connector sends qbXML to the copy of QuickBooks already used by the bookkeeper. QuickBooks reports the result, and the field system compares its total to the cent. A mismatch stops the post. The same guard refuses another invoice for a work order that already reached the books.

This workflow is scoped from real QuickBooks Desktop shops and priced the same way as our other Missing Piece builds, though it hasn’t gone live in a dispatch office yet. The connector logic and cent-matching guard are built and tested end to end before that first install.

Dispatch that shows what’s happening in the field

QuickBooks Desktop records accounting events after office review. It does not act as a live dispatch board. Without one, a shop assigns technicians from memory and the office has to call for an update after the job leaves the desk.

The added board shows technicians by day with one card for each work order. Staff can drag a card to move the date or assigned person. If the move creates a conflict, the board warns the dispatcher and leaves the choice with them. An urgent no-heat call can still take precedence when the office gives it priority.

Technicians see the assigned job in a browser on their own phone. Four status choices cover accepted, on my way, delayed and rejected. The office sees a change within seconds. Clock actions live on the same page, with an office override for an unusual case that needs a recorded correction.

The field page also holds the customer and site details needed for the visit. Tapping the address opens directions. A technician can photograph completed work before passing the phone to the customer for a signature. The finished record returns to the pricing queue.

Overtime that’s calculated once and shown on the document the customer signs

Paper work orders leave weekend and overtime rules for the office to calculate later. A shop needs that multiplier visible when the customer signs, with a plain reason beside it.

The workflow checks two rules that do not stack. Saturday and Sunday use a flat weekend premium. Ontario’s Employment Standards Act threshold applies after 44 hours in a week. When one applies, the signed record can show wording such as “1.5x - Saturday” or “1.5x - over 44 hours this week.”

Signing freezes that version of the work order. If the office later corrects another timesheet from the same week, the saved customer record keeps the hours and reason shown at sign-off. The overtime rules get checked against your province’s actual thresholds before the build ships, not guessed at afterward.

Those calculations stay in the field workflow. QuickBooks Desktop receives the reviewed invoice total after the office has seen the work and confirmed the pricing. The accounting file never needs to recreate a field rule from a note.

Recurring maintenance contracts that surface themselves

Quarterly and seasonal maintenance often lives on a calendar or a reminder sheet. When that record depends on one person’s memory, a due visit can remain hidden until the customer calls.

The field system stores the repeat interval with the job and provides a due-this-week view. Dispatch can place the next visit while looking at technician availability. The completed work then follows the same pricing review and Web Connector path used by an urgent call.

Existing customer records can guide the import. We map the customer and site identifiers used in QuickBooks Desktop before recurring work enters the field system. That keeps the returned invoice attached to the accounting record the bookkeeper already trusts.

Parking, photos, and the small stuff that adds up

Parking reimbursement is easy to skip when it lives on a receipt in a truck. A technician can photograph the receipt and enter the amount from the job page instead. The office sees it in an approval queue before any customer invoice includes the charge.

For downtown visits, a nearest-lot lookup can use public municipal parking data. It helps a technician choose a destination before arrival and avoids a paid map service. The lookup stays separate from the limited location events used for job status and clock actions.

Completion photos accept iPhone formats and convert them for office viewing. The browser flow needs no app store install. A customer signature joins the frozen work order after the technician checks the recorded work.

This is one Missing Piece workflow around existing tools. The build takes 3 to 6 weeks and ends with a handoff document. The client owns the finished system. Hosting is billed at cost up to the monthly cap, and later changes use a flat feature price. There is no retainer.

Where a subscription product is honestly the better call

Jobber or Housecall Pro can fit when a shop already uses QuickBooks Online and standard field rules cover the work. Their subscription includes a broad set of features, and a small crew can get more value from that catalogue.

The custom route fits a narrower need. QuickBooks Desktop stays on the office PC. Customer pricing needs its own fields, while overtime carries a visible reason on the signed work order. The connector must also refuse a duplicate or a total that differs by one cent.

Bring the tools and rules used today. We map the path from the call to QuickBooks, then build the missing field workflow without asking the bookkeeper to move the ledger.