What is the difference between a booking, a job and an invoice in ServiceTitan?
A booking is a request to be scheduled and may never become anything. A job is scheduled work with appointments, a business unit and a technician. An invoice is the money record attached to that work. One booking can produce one job, one job can carry more than one invoice, and revenue exists only on invoices. Counting bookings as demand is fine. Counting bookings as revenue is not.
The chain, and where each link can break
The normal path is booking to job to appointment to invoice. Every arrow in that chain is a place where the count can drop. A booking can be created and never converted. A job can be created and cancelled before it is dispatched. An appointment can be scheduled and rescheduled three times. A job can be completed and sit uninvoiced while paperwork catches up.
This is why the same week looks different depending on which object you count. Bookings, jobs and invoices are not three views of one number; they are three different numbers measured at three different moments.
Bookings are not the same thing as calls
A booking record is created when someone requests service — through the call center, a web scheduler, or a technician selling follow-up work. It is not the same as a phone call, and it is not the same as a lead in your marketing reporting. A call that produces no booking leaves no trace in the job data at all, which is exactly why call analysis and operational data have to be joined rather than compared.
One job, many invoices
The relationships are not all one-to-one, and reporting breaks when people assume they are.
- Job to appointment is one-to-many. A multi-day install or a return trip for parts adds appointments without adding jobs. Counting appointments as jobs inflates volume.
- Job to invoice is one-to-many. Deposits, progress billing and change orders can each generate their own invoice. Summing invoices per job is right for revenue; counting invoices is wrong for job volume.
- Customer to location is one-to-many. Property managers and commercial accounts hold many service addresses under one customer.
- Invoice to payment is one-to-many. Billed is not collected, and an aging report answers a different question than a revenue report.
Pick the object that matches the question
Use bookings to measure demand and intake performance. Use jobs to measure operations, capacity and technician output. Use invoices to measure money. Mixing them produces reports that cannot be defended when someone questions them in a meeting.
When a dashboard shows revenue by campaign, the honest version walks all the way down the chain: campaign to booking to job to invoice, with a stated count of records that could not be traced. That traceability is the whole point of revenue intelligence rather than a prettier version of the ad platform report.
Topics: bookings · jobs · invoices · data model
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.