Buying / Practical answers
What actually syncs between field-service software and QuickBooks Online?
Understand one-way syncing, changed invoices and paid-status mismatches, with specific Jobber and Housecall Pro documentation and a test checklist.
Check the integration version, the direction of each record and the event that triggers an update. Jobber’s new integration does not send paid status back from QuickBooks to Jobber. Housecall Pro requires a manual push for specified invoice edits after the first sync. “Integrated” does not mean every record updates both ways.
Is a QuickBooks integration automatically two-way?
No. Ask separately about customers, items, invoices, payments and edits. An initial import from accounting is also a different process from ongoing synchronization. Record the source system for each type of change and the person responsible for resolving a mismatch.
This guide examines Jobber’s new QuickBooks Online integration and Housecall Pro’s documented QuickBooks Online workflow. It does not establish the behavior of QuickBooks Desktop, an older integration or every other field-service product. Confirm the configuration in your own account before applying a documented procedure.
Why can a QuickBooks invoice be paid while Jobber still shows it unpaid?
Jobber’s new QuickBooks Online integration sends clients, products/services, invoices and payments from Jobber to QuickBooks. The ongoing sync is one-way; an invoice’s paid status does not sync back from QuickBooks to Jobber. Payment syncing depends on the sync settings.
For that integration, check where the payment was recorded and follow the documented workflow for reconciling the two records. Do not request another customer payment simply because the application still shows a balance. Have the accounting owner identify the actual transaction before changing records.
When evaluating the system, include a payment recorded outside the usual workflow. The useful question is how staff recognize the mismatch and correct it without duplicating a transaction. Keep the invoice and payment identifiers in the test record.
Why did my changed Housecall Pro invoice not update in QuickBooks?
Housecall Pro’s QuickBooks Online guide says invoice line-item, quantity, price and description changes do not automatically update QuickBooks after the initial sync. A manual push is needed to refresh those changes.
Use the official guide for the applicable manual push, then inspect the linked invoice. Check the changed line and total rather than only looking for a successful connection indicator. The integration being connected and the revised invoice being present are different observations.
In a demo, make the edit after the original invoice has already appeared in QuickBooks. A demonstration that only sends a brand-new invoice will not expose this exception.
What should an integration test include?
Use a vendor demonstration or an appropriate test environment with fictional records. The proposed procedure below is our evaluation checklist, not a statement that both products support identical controls.
| Step | Inspect in both systems | Record |
|---|---|---|
| Create invoice | Customer, line items, tax and amount | Linked invoice IDs |
| Record partial payment | Payment allocation and remaining balance | Payment reference |
| Edit approved work | Changed item and revised total | Trigger or manual action needed |
| Handle an exception | Warning or mismatch visibility | Owner and resolution step |
| Review at close | No unexplained duplicate or difference | Reconciliation completed |
Example: a fictional invoice begins at $300 before tax, receives a $100 payment and is later increased by $50 of approved work. The intended remaining balance is $250 before tax. Use that arithmetic to compare the records; it is not a promise about how any particular integration updates itself.
If the result differs, identify whether the invoice edit, payment or tax treatment is missing before making another change. Repeatedly entering the same record to force the totals to agree can conceal the original problem.
How do you avoid duplicate records during setup?
Agree where new customers, items and invoices should originate after connection. Before a large transfer, reconcile a small sample that includes similar customer names and a customer with multiple properties. Record how the integration identifies an existing record rather than assuming names alone are sufficient.
Choose the historical date range deliberately and review the official onboarding instructions for the exact integration. Your bookkeeper should understand which older invoices and payments are intended to appear. This guide does not establish a universal import procedure, rollback or duplicate-removal method.
What should you ask before buying a QuickBooks-connected plan?
- Which QuickBooks product, region and integration version is supported?
- Which field-service plan and additional charges apply?
- Which records sync, in which direction, and after what trigger?
- How are partial payments, refunds and post-sync edits handled?
- Where do failures appear, and who owns their resolution?
- How do historical records and existing customer matches work?
End with a written operating rule for staff and a verified sample, not just a connected logo. If the office knows where to enter changes and how to find exceptions, the integration has a clearer role in the daily workflow. For invoice creation itself, use the estimate-to-invoice guide; for price comparison, use the shared costs page.