Same word, different count

Why Two ServiceTitan Reports Disagree, and How Both Can Still Be Right

Two ServiceTitan screens, one month, two different totals. Before anyone accuses the software, the bookkeeper or the sales manager, check what each screen is counting. ServiceTitan documents most of the differences itself, in plain sentences most owners never read.

November 13, 2026 · 10 min read

app.acmeplumbingco.com · report tie-out
Two revenue totals for one month, checked line by line
Same month, two totals, three reasons
Sample
  • PassBoth use job completion date
  • PassDashboard drops the cents$0.32
  • WarnBusiness unit: invoice item vs job
  • FailAdjustment invoices on one side only2 invoices
  • WarnItems not on an income GL account3 items
Illustrative: a sample report tie-out for a fictional plumbing company

The short answer

ServiceTitan reports disagree because they count different things under similar names. Sales date by estimate sold-on date while completed revenue dates by job completion; close rate counts sold estimates while conversion rate counts invoices; some screens follow the invoice item's business unit and others the job's; some totals include adjustment invoices and others leave them out. Match the definitions first, then compare.

On this page
  1. Twenty-four thousand dollars and thirty-two cents of disagreement
  2. Every number hangs on a date, and they do not all share one
  3. Sold, completed, invoiced: three verbs and three totals
  4. Labels that mean two things inside ServiceTitan's own help center
  5. Business units, adjustment invoices and an unmapped GL account
  6. Settings that change the count without changing the work
  7. A tie-out routine for the next time two screens disagree

Twenty-four thousand dollars and thirty-two cents of disagreement

The dashboard says Completed Revenue was $24,291. The report says $24,291.32. Someone forwards both to the owner with a question mark. ServiceTitan's article on report and dashboard mismatches, read November 11, 2026, uses exactly that example and settles it in one deadpan line: "The dashboard doesn't display cents, so this matches exactly."

Most mismatches take longer than thirty-two cents to explain, but the same article names the usual cause: "the report column and the dashboard module are displaying different types of information." Its fix is to match the dates and the business unit filters. That is the method of this page, extended to the other differences ServiceTitan documents.

One rule runs through everything below. We never call a ServiceTitan report wrong, because in the cases its help center describes, it is not. ServiceTitan says of one pair that they "will not always match" but "will still be correct." Each report is right about the thing it counts. The trouble starts when two people in one meeting assume both reports count the same thing.

Every number hangs on a date, and they do not all share one

The most common source of disagreement is the calendar. ServiceTitan's run report article says date filters "can apply to the job completion date or invoice date, depending on the KPI," and suggests hovering over a column header to see how. Here is where several familiar numbers hang, per ServiceTitan's own help articles as read in November 2026.

The date each ServiceTitan number filters on, per ServiceTitan's help center, November 2026
NumberDate it filters onWhere ServiceTitan says so
Total Sales on the dashboardEstimate sold-on dateDashboard business metrics
Completed Revenue on the dashboardJob completion dateDashboard business metrics
Non-Job Revenue and Adj RevenueInvoice dateDashboard business metrics
Call Booking RateCall dateDashboard business metrics
Campaign sold jobs, and campaign revenueCall date for sold jobs, job completion date for revenueMarketing scorecards
Technician Performance sales opportunitiesJob completion date, or the estimate's sold-on date once one is soldTechnician Performance template
Bright blue duotone of a person seen from behind holding two blank sheets of paper side by side, solid circles and triangles floating around them
Two reports, one month, two calendars underneath.

Even the date presets differ. ServiceTitan's dashboard filter article defines "Last 7 Days" as "Previous seven days, including today," while its scheduled reports' "Trailing 7 Days" is "not including the report delivery day." Compare a Monday dashboard with a Monday email and you are comparing two different weeks.

Sold, completed, invoiced: three verbs and three totals

A replacement sold on the 28th and installed on the 3rd lands in two months at once: sales in the first, revenue in the second. ServiceTitan's business metrics article says plainly, "The Total Sales will not always match Completed Revenue, but these metrics will still be correct." It lists the reasons, and every owner should know them:

  • An estimate sold in the date range whose install job "has not been completed," or was completed outside the range.
  • Revenue "that did not come from a sold estimate," such as a repair invoiced on the spot.
  • Estimate items "not connected to an income GL account," which can count in sales without ever reaching revenue.
  • Invoice items from a sold estimate that "are updated or removed" after the sale.

The same split runs through ServiceTitan's rates. Its troubleshooting article says close rate is "Exclusive to sales and estimates" and conversion rate is "Exclusive to revenue and invoices." One reads the estimate, the other the invoice. Our close rate explainer covers the versions of close rate in detail, and the average ticket explainer does the same for ServiceTitan's several averages.

Labels that mean two things inside ServiceTitan's own help center

ServiceTitan knows its vocabulary drifts. It publishes a KPI Matrix that marks, report by report, whether a KPI "matches the definition," "partially matches" or "does not match," and notes that "Only 20 legacy reports are represented in the matrix." These are a few of the drifts its own articles record.

Booking rate

The dashboard divides by call leads; the Office Performance template's Inbound Booking Rate uses "inbound calls booked into jobs." Our booking rate explainer runs one day through each.

Campaign ROI

The marketing scorecards article calls it "total revenue divided by the total campaign cost," then gives "( (Revenue - Cost) / Cost) × 100)". Two formulas, one label. See lead source ROI.

Membership opportunity

The memberships glossary counts any service location without an active membership; the dashboard counts "a completed job with a Potential Member or Potential Membership Renewal tag." See membership conversion.

Abandoned call

The glossary calls it a call a CSR answers without clicking the call bubble, and its pop-up calls it "A call where the customer hung up before reaching a CSR."

Excused call

The glossary says a manager can manually excuse a call. The call classifications article says "You cannot manually mark a call as excused."

Sold threshold

The glossary says a closed estimate's subtotal is "equal to or greater than" the threshold; the troubleshooting article says "greater than the Sold Threshold."

None of these drifts makes a report useless. Each makes a comparison between two reports unsafe until somebody checks which definition each one uses. The Reporting Dictionary is the place to check: it lists each field's description and a "Calculation" line, which reads "N/A" when there is none.

Business units, adjustment invoices and an unmapped GL account

Filters cause the quieter disagreements. ServiceTitan's Business Unit Performance template article says revenue KPIs "are based on the BU of the invoice item," while its timesheet fields follow the job's business unit. On the CSR Agent Scorecard, business unit filters apply to booking KPIs while "Call and lead KPIs are unaffected." Filter two screens to the same unit and they can still be counting different slices.

  • Technicians on two scorecards. ServiceTitan's scorecards article says items take "the job's business unit, not the technician BU" by default, so a technician "can appear on different scorecards." Our technician scorecard page deals with the fairness questions that follow.
  • Adjustment invoices in, then out. Dashboard Total Revenue includes Adj Revenue; the Business Unit Performance template's Completed Revenue says "Adjustment invoices are not included"; technician scorecards leave them out by default.
  • Only income items count. "Only invoice items connected to an Income GL Account will show on the dashboard," per the business metrics article. An item mapped elsewhere is real money the dashboard never shows.
  • Split credit. The Technician Performance template adjusts Completed Revenue "by technician Split," so per-technician totals need not add up to a company figure filtered differently.

Settings that change the count without changing the work

Some numbers move because the work changed. Others move because a setting did. ServiceTitan's dashboard depends on configuration: its dashboards overview lists mapped business units, pricebook items linked to GL accounts with sold hours, sold thresholds on job types, call reasons and campaigns among the setup steps. A company's numbers depend on those settings. That is not a fault in anyone's setup; it is how the counts are built.

  • Sold thresholds rewrite history. ServiceTitan says "Changes to the Sold Threshold in the job type settings are retroactive," and that "With a $0 sold threshold, conversion rates are always 100%."
  • Call reasons decide what a lead is. Without them, ServiceTitan says, "any call longer than 60 seconds will be classified as a lead."
  • Tags decide membership opportunities. If the Potential Member tag is renamed or deleted, "Only jobs where a membership was sold are counted as opportunities," per its membership troubleshooting article.
  • No Charge job types change the base. A No Charge job "cannot decrease" close or conversion rate but can raise either when the threshold is met.

The practical step is a change log. If the log keeps pointing at settings rather than software, our guide to when ServiceTitan needs a custom build and when it needs a better setup sorts the fixes. Whenever someone edits a threshold, a job type, a call reason or a tag, write down what changed and when. A month that looks dramatic on screen sometimes traces back to a single settings edit, and the log turns an argument into a two-minute answer.

A tie-out routine for the next time two screens disagree

Keep this routine near whoever gets the forwarded screenshot with the question mark. It follows ServiceTitan's own advice and takes minutes, most of them spent reading tooltips.

  1. 1

    Read the column tooltip

    Hover over the column header on each report. ServiceTitan says the tooltip explains "how filters are applied."

  2. 2

    Look up the calculation

    Find both fields in the Reporting Dictionary and compare the Calculation lines word for word.

  3. 3

    Check the KPI Matrix for legacy reports

    If either report is legacy, see whether the matrix marks its KPI as a match, a partial match or no match.

  4. 4

    Match the dates and the presets

    Same date field, same range, same preset. "Last 7 Days" and "Trailing 7 Days" are not the same week.

  5. 5

    Match the business unit basis

    Invoice item, job or technician: confirm which one each screen follows before filtering.

  6. 6

    Check adjustments and GL mapping

    Are adjustment invoices in both totals? Are all items on an income GL account?

  7. 7

    Write the winning definition down

    Pick the definition your company will use, in one sentence, and put it where the number appears.

That last step is what a custom ServiceTitan dashboard builds in: every tile carries its definition, so the routine runs once instead of every month. The monthly numbers review keeps the definitions honest as settings change. The rest of the explainers sit on the ServiceTitan dashboards hub, and the data plumbing behind a custom screen is on how ServiceTitan data reaches a dashboard.

If your question is really about ad platforms disagreeing with ServiceTitan, read our Google Ads conversion tracking guide; ServiceTitan's own article notes revenue is recorded on the job completion date while Google Ads records it on the ad impression date. For joining ServiceTitan with ad and call data, see ServiceTitan dashboards and reporting, and for the tracking itself, our conversion tracking setup service.

Questions owners ask about ServiceTitan dashboards and numbers

Because they count different documents on different dates. Total Sales adds up sold estimates by the estimate's sold-on date; Completed Revenue adds up income items on completed job invoices by job completion date. ServiceTitan says they "will not always match" but "will still be correct," for example when a sold install has not been completed yet, or revenue came from work that was never estimated.

Usually because the two are filtered differently or count different information. ServiceTitan's mismatch article suggests matching the date range and business unit filters first. It also notes the dashboard drops cents, so $24,291 and $24,291.32 are a match. Check, too, whether the report includes adjustment invoices and whether every item sits on an income GL account.

Pick one definition per number and write it down. A useful anchor: ServiceTitan says all basic dashboard KPIs except Call Booking Rate "correspond to columns from the Business Unit Performance report template," so that template is a natural reference for revenue and conversion. Whatever you choose, use the same one in every meeting.

Yes. ServiceTitan's help center says "Changes to the Sold Threshold in the job type settings are retroactive." Close and conversion rates for earlier months can shift after the edit, with no change in the work itself. Keep a dated log of threshold changes so a sudden move in last quarter's numbers has an explanation waiting.

Technician scorecards are organized by business unit division, and ServiceTitan says items take "the job's business unit, not the technician BU" by default. A technician who works jobs in two business units shows up on both scorecards. The scorecards also leave adjustment invoices out of revenue by default, which can make them differ from other reports.

It can settle which number your company uses, which is the useful question. A custom dashboard shows each number with its written definition and the list behind it, so nobody has to guess which report it came from. It does not overrule ServiceTitan; it reads the same data with one agreed rule.

Keep reading

Free · No obligation

Send us the two reports that disagree

Tell us which screens, which number and which month. A person at DataCram replies with the likely reason they differ, in ServiceTitan's own terms, and whether a custom screen would stop the argument for good.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote