ServiceTitan completed jobs not invoiced: the gaps inside batch invoicing
Last updated November 16, 2026 · 6 min read
Short answer
ServiceTitan invoices through a batch flow: select, review, post. Any job that never enters a batch — status quirks, pending parts, long lists — sits complete and unbilled. The check joins completed jobs to invoices across your exports.
The data reality
Where to export: ServiceTitan exports — Jobs (status, completed date, totals) crossed against Invoices (job links, amounts); the check lists completed jobs with no invoice linkage.
Columns that matter: Job Number · Status · Completed On · Job Total · Invoice #
ServiceTitan exports are rich but split: job totals exclude sales tax until invoicing, project-type jobs aggregate sub-jobs, and 'Completed' status can coexist with 'Pending' inventory items that block invoicing. The check normalizes totals and treats pending-item jobs as a distinct, reviewable category.
Why this system leaks
Batch invoicing is efficient precisely because it processes many jobs at once — and efficient at hiding the jobs it misses. A job left in 'Pending' because a part receipt hadn't posted drops out of the batch silently. The batch posts, the day's invoice count looks normal, and the pending job's resolution — the part posts days later — triggers no return to invoicing. The job stays complete, unbilled, and outside every dashboard that counts the day's posted invoices.
Batch flows move sets, not items: the batch's completeness is only as good as the selection behind it, and nothing verifies selection against the complete-set afterward. ServiceTitan's own reports count posted invoices forward; they never compare backward against all completed work. The check is that backward comparison, run on exports so it sees past status filters.
Batch invoicing hides its own misses
The batch's efficiency is the leak's cover: a normal-looking batch post says nothing about the jobs that never entered it. Status filters, pending parts, and long lists each subtract jobs from selection without signaling the subtraction. The check restores the signal by comparing all completed jobs to all invoices, regardless of what any batch contained.
Pending parts are the classic trap
A job held for a part receipt is correct — until the receipt posts and nothing routes the job back to invoicing. The 'pending' category in the check's output exists for exactly this: a short, reviewable list of held jobs, each needing either an invoice or a documented reason it still holds.
Enterprise tooling, same fundamental gap
ServiceTitan's sophistication raises the floor but not the ceiling: completion and billing remain separate states joined by human batching. The reconciliation reads raw exports precisely so it is independent of workflow states — the only perspective from which the gaps are visible.
A worked example
A three-truck shop's ServiceTitan exports, Jan–Oct: 2,141 completed jobs, 2,133 invoices. Eight jobs uninvoiced — several stuck behind resolved 'Pending' part receipts, one a project sub-job masked by its parent's invoice, two scrolled past in a Friday batch. Total: $964.
- Recorded work
- $964.00
- Invoiced
- $0.00
- Residual
- $964.00
Residual = $964 across eight jobs — under half a percent of volume, typical for a disciplined ServiceTitan shop, and still four figures a quarter. The pending-item jobs alone account for half; they are the shape batch invoicing hides best.
What the data cannot show
- Jobs awaiting genuine part receipt are correct to hold — the check flags them as a distinct 'pending' category so the office can verify each resolves into an invoice rather than into silence.
- Project and membership structures aggregate billing — sub-job coverage is evaluated against the parent's invoice where the export shows the relationship, avoiding false positives.
Questions shops ask
How do I find uninvoiced jobs in ServiceTitan?
Export Jobs and Invoices, then compare: every completed job needs invoice coverage at its full value. The check automates the join, normalizes pending items and project structures, and returns the exception list in minutes.
Does ServiceTitan warn about uninvoiced jobs?
It surfaces 'needs invoicing' queues, which depend on someone working the queue and on the job appearing in it — pending items and status filters can exclude jobs. The check is independent of queues and statuses: it compares the full completed-set against the full invoiced-set.
We run tight batch discipline — can gaps still exist?
Yes, at lower volume: pending-item jobs, project sub-jobs, and selection slips all survive disciplined batching. Even half a percent of a ServiceTitan shop's volume is real money. The check quantifies your exact residual.
See a sample report for your export
See a sample report for your export