Service Fusion billing leaks: five shapes of unbilled work in an all-in-one system
Last updated November 16, 2026 · 6 min read
Short answer
Service Fusion combines dispatch, jobs, and invoicing in one tool — but invoicing is still a manual step, and the QuickBooks sync only transports what was invoiced. The check finds all five leak shapes from your exports, labeled by cause.
The data reality
Where to export: Service Fusion exports — completed jobs/work orders crossed against invoices; agreements cross-checked per job; the check lists gaps by leak shape.
Columns that matter: WO # · Status · Completed · Invoice total · WO total
Fusion's exports bundle agreement jobs with standard jobs, and multi-visit WOs total across visits while invoices may cover one. Zero-dollar closures (warranty, agreement, error) appear as legitimate rows that mask real work. The check separates agreements, aggregates multi-visit totals, and flags zero-dollar closures for review.
Why this system leaks
The all-in-one design means the dispatcher can invoice from the same screen that dispatches — which feels like billing is woven into the workflow. In practice, invoicing remains a per-job action that busy dispatch days defer. A $549 duct replacement completes Thursday; invoicing 'waits until the office settles down'; the settle never comes; the WO shows complete in a system whose dashboard reports job counts, not billing completeness. The all-in-one feeling becomes the leak's best camouflage.
Integrated tools concentrate information but not accountability — invoicing stays a decision, and decisions deferred on integrated screens look no different from decisions made. Fusion's dashboards describe activity; none compare completed work against invoiced work backward. The check performs that comparison from exports, where every leak shape is a pattern in the data.
Integration is not enforcement
One screen for dispatch and invoicing feels like a guarantee; it is a convenience. The invoice still requires a decision per job, and decisions deferred in an integrated workflow are indistinguishable from decisions completed — until a backward comparison separates them. That comparison is the check.
The five shapes, by fix
Never-invoiced: back-invoice now. Multi-visit under-billing: invoice the accumulated visits. Missing part lines: issue the corrected invoice. Agreement drift: verify the agreement's terms. Zero-total closures: document the reason. One check, five labeled outputs — each with its action.
The sync transports; the check verifies
Fusion's QuickBooks sync moves invoiced data to the books. It cannot move what was never invoiced, and its smooth operation is read by many shops as proof of billing completeness. The check reads exports from the Fusion side and verifies billing from the completed-work side — the only direction that catches gaps.
A worked example
A shop's Fusion exports, Jan–Oct: five leak shapes present. Two WOs never invoiced ($184, $167); one two-visit WO invoiced for the first visit only ($103 short); one WO missing its $76 part line; one agreement tune-up with a $19 repair billed free; one zero-total closure on a real repair ($95).
- Recorded work
- $549.00
- Invoiced
- $0.00
- Residual
- $549.00
Residual = $549 across six distinct jobs — the inventory of shapes matters more than the total: each shape implies a different fix, and the check labels every gap with its shape so the office can fix the workflow, not just the invoice.
What the data cannot show
- Agreement terms vary per contract — the check verifies agreement jobs against the agreement's recorded terms where exports include them; ambiguous terms surface for the office to resolve.
- Warranty and goodwill zero-closures are legitimate — the check flags them for documentation, not accusation; the mark persists as the audit trail in every later check.
Questions shops ask
Does Service Fusion automatically invoice completed jobs?
No — invoicing is a per-job action, and the QuickBooks sync transports only what was invoiced. Completed-but-uninvoiced jobs are silent in both systems. The check finds them from the exports in minutes.
How do agreement jobs leak in Fusion?
Covered tune-ups bill at agreement terms, but repair work found during visits needs separate billing that 'member' framing often suppresses. The check verifies agreement jobs against their terms and flags free repair work.
What are zero-total closures?
Jobs closed at $0 — warranty, goodwill, errors, or actual gaps. Fusion treats them as normal rows; the check flags each for documentation so the legitimate ones get reasons and the accidental ones get invoices.
See a sample report for your export
See a sample report for your exportRelated
- QuickBooks contractor reconciliation: finding the invoices that should exist but don't
- Maintenance agreement mistakes: when plan coverage swallows billable repairs
- Invoice line items missing: when the job is billed but not completely
- HVAC jobs completed but not invoiced: the leak every shop has and none can see