Jobber completed jobs vs invoices: finding the visits that never got billed
Last updated November 16, 2026 · 6 min read
Short answer
In Jobber, completing a visit does not create an invoice — that is a separate click, and it is where work disappears. The check joins your completed-job export to your invoice export and lists every completed job that has no invoice.
The data reality
Where to export: Jobber export: Jobs (with status and completed-date) crossed against Invoices (with linked job IDs); the check lists completed jobs whose job ID appears on no invoice.
Columns that matter: Job ID · Client · Visit completed · Job status · Invoice number
Jobber's Jobs export shows visit-level completion, while invoices link at the job level — a job with several visits needs only one invoice for all of them. The check matches at job level so multi-visit jobs are not falsely flagged, and flags jobs whose visits are all complete with no invoice on any of them.
Why this system leaks
The tech completes visit #4482 on site — taps 'complete' in the app and drives off. The office's invoicing rhythm is a daily review of 'needs invoice' queues, but the queue is long, the filter defaults to today, and visit #4482's job was created eleven days earlier, so it sorts to a page nobody opens. The job is complete, the client is satisfied, and no invoice exists. Jobber will not remind anyone, because from Jobber's side the workflow is finished.
Completion and invoicing are separate states in Jobber, and nothing enforces the second after the first. The 'needs invoice' view only helps people who look at it; sort orders and date filters quietly hide older work. Leakage is structural — the check is the only step that compares the complete-set to the invoiced-set instead of trusting the queue.
The two-click problem
Jobber's design treats 'visit complete' and 'invoice sent' as separate human decisions, connected by nothing stronger than office discipline. Every busy Friday that discipline bends, and the jobs that slip are never missed by anyone — they simply stop appearing in queues while remaining permanently unbilled. The check is the cross-check the workflow lacks.
Why the built-in queue is not enough
'Needs invoice' views show what is unsorted today; they do not compare the complete-set against the invoiced-set across all time. Date-range defaults, pagination, and multi-visit jobs all erode the queue's completeness. A reconciliation over the full exports is the only view that cannot hide an old job.
Run it before the month closes
A completed job found in the same month is a five-minute invoice. Found two quarters later it is an awkward collection call against a client who assumed it was settled. The monthly rhythm is what keeps the recovery easy — the check takes minutes; the aging is what costs.
A worked example
Job #4482 — capacitor replacement, visit completed September 14. Client confirmed satisfaction by text. Job status: complete. Invoices exported from Jobber: no invoice references job #4482. Parts on the job: $68. Labor: $144.
- Recorded work
- $212.00
- Invoiced
- $0.00
- Residual
- $212.00
Residual = $212 — one ordinary repair, invisible because completion was never followed by invoicing. Shops typically find between three and eight such jobs per hundred completed on a first check.
What the data cannot show
- Jobs legitimately closed without billing — warranty, goodwill, internal work — appear in the results; the office marks them with a reason, which turns 'unknown gaps' into 'documented decisions.'
- Deposits and partial invoices are credited — a job with any linked invoice is checked for full coverage rather than flagged as fully unbilled.
Questions shops ask
How do I find completed jobs without invoices in Jobber?
Export Jobs and Invoices from Jobber's reporting, then compare: every job whose visits are all complete should appear on at least one invoice. The reconciliation automates this join — including multi-visit and deposit edge cases — and lists every gap in minutes.
Doesn't Jobber warn me about uninvoiced jobs?
Jobber offers 'needs invoice' views, but no report compares all completed jobs against all invoices across your full history. Filters, date ranges, and pagination leave gaps. The independent check works from raw exports, so nothing can hide in a default view.
How far back should I check?
At least twelve months on a first run — unbilled jobs do not expire, and clients often still pay months later when approached with a clear statement of work. After the first deep check, a monthly rhythm keeps the backlog at zero.
See a sample report for your export
See a sample report for your export