Skip to main content

What is the actual relationship between jobs, appointments and invoices in ServiceTitan?

ServiceTitan Published November 19, 2026
Short Answer

They are three separate levels, and the relationships are one-to-many in both directions in practice. One job can have several appointments when a crew has to return, and one job can carry more than one invoice when work is split or re-billed. Counting jobs, counting appointments and counting invoices will therefore give you three different numbers for the same week of work.

The level you count determines the answer

Most reporting confusion in a field service system comes from picking a grain without noticing. A job is a unit of work sold to a customer at a location. An appointment is a scheduled visit against that job. An invoice is a billing document produced from it. These are not interchangeable, and each answers a different business question.

Count jobs when you want to know how much work you sold. Count appointments when you want to know how much capacity you consumed. Count invoices when you want to know what you billed. A replacement that took three visits is one job, three appointments and possibly one invoice.

Where the fan-out bites

  • Multi-visit work inflates appointment counts. Any "jobs completed" metric built on appointments will overstate volume for trades that routinely return, and understate the true cost per job.
  • Split billing creates multiple invoices per job. Deposits, progress billing and change orders can all produce separate documents against one job.
  • Recalls and warranty visits may attach to the original job or open a new one. Which convention your office uses changes both your job count and your callback rate.
  • Membership and recurring billing produce invoices with no field visit at all, so invoice counts and appointment counts diverge structurally, not accidentally.

How to choose a grain and stick to it

Pick the grain from the question, then aggregate up rather than down. Marketing questions almost always want the job grain, because that is what a lead becomes. Capacity and scheduling questions want the appointment grain. Financial questions want the invoice grain. Build the dataset at the finest grain you need and roll it up; never try to reconstruct detail from a pre-aggregated report.

A practical trap: average ticket computed at the invoice grain differs from average ticket computed at the job grain whenever multi-invoice jobs exist. The invoice-grain number will look lower and nobody will know why.

Why this matters for attribution

Marketing attribution has to land on the job, because that is the object the lead created. If your pipeline joins campaign data to invoices instead, every multi-invoice job gets credited more than once and your cost per acquisition looks better than it is. Getting this right is the difference between a reporting layer that is trusted and one that gets quietly abandoned.

We model these levels explicitly when connecting field service data to ad platforms and call records, which is described further in ServiceTitan AI integration and in how we approach marketing intelligence.

Topics: data model · jobs · invoices · appointments

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.

Related Answers

People who read this also asked

Browse the Answer Hub →

AI is easy to access. Making it useful is hard.

Bluefrog makes AI useful by integrating it with the way your business actually works — your software, your calls, your customers, your marketing and your revenue.

Technology development since 1997 · AI integration platforms since 2001