Why Your ServiceTitan and QuickBooks Numbers Don’t Match
Your ServiceTitan and QuickBooks numbers disagree because the two systems record different events at different moments. ServiceTitan counts the job. QuickBooks counts the money. Most of the gap is timing and definition, not a broken sync. The fix is a line by line tie out that tells you which differences are normal and which are real.
Why Don’t My ServiceTitan and QuickBooks Numbers Match?
Because they are answering two different questions. ServiceTitan records what happened in the field: the job, the invoice, the payment taken at the door. QuickBooks records what happened to the money under accounting rules: when revenue is recognized, how a credit is applied, which period a transaction lands in.
Two systems, two clocks, two definitions of the word revenue. A gap between them is expected. A gap you cannot explain is the problem.
This is the same disease as the one behind your marketing report and your sales report never agreeing, applied to a different pair of systems. One event, several systems, no shared definition.
Which Numbers Should Tie Out, and Which Are Supposed to Differ?
Some figures should match to the dollar in a closed period. Others are supposed to diverge, and chasing them wastes a week.
Should tie out (same closed period)
- Total invoiced revenue
- Payments collected
- Sales tax billed
- Invoice count and customer count
Supposed to differ
- Invoiced vs recognized revenue. Work invoiced in one period may be recognized in another.
- Job revenue vs cash collected. The difference is your accounts receivable, not an error.
- Deposits and progress payments. Money taken before the work is finished is a liability, not revenue yet.
- Credits, refunds, write offs. Often applied in the books after the original invoice posted.
- Manual journal entries. Anything typed straight into accounting never existed as a job.
Write that distinction down once. Most of the panic in a month end close comes from treating a normal difference as a broken integration.
Is This a Sync Problem or a Process Problem?
Usually process, occasionally sync, and you can tell them apart in about ten minutes.
Sync problem
Mechanical and lumpy. The usual suspects are a posting batch that errored and was never re run, an item with no account mapping, or an entity pointed at the wrong file. Check those three first. The signature is a clean, traceable block of missing or misfiled transactions.
Process problem
Human and steady. Two people define a completed job differently, one closing it at dispatch and one at final invoice. Adjustments get made in one system and not the other. The cutoff moves depending on who closes the month. The signature is a gap that is always there, always roughly the same shape, and never quite the same number.
Sync problems get fixed once. Process problems come back every month until someone writes down the rule.
How Do I Find Where the Gap Starts?
Work top down, in one closed period, and stop at the first number that breaks. Here is the method you or your office manager can start Monday.
- Freeze one period. Take the last full closed month. Do not reconcile a live month, the numbers will move while you work.
- Pull the same figure from both systems. Start with total invoiced revenue for that period. One number from ServiceTitan, one from QuickBooks.
- Write down the gap in dollars. Not a percentage. The dollar figure is what you will explain.
- Sort the gap into four buckets: timing, adjustments, missing transactions, mapping. Most gaps are mostly one bucket.
- Drill into the largest bucket only. Go to the transaction level there and nowhere else yet.
- Write the rule for every difference you find. “Deposits sit in liability until the job closes” is a rule. Rules turn a mystery into a checklist.
- Re run it next month. A tie out that took three days the first time should take under an hour once the rules exist.
The output you want is not a matched number. It is a short document that explains every difference, so next month nobody has to rediscover it.
Why Do We Run a Tie Out Before Calling Any Build Finished?
Because we learned this one the hard way, on our own project.
CDA built a set of marketing dashboards for a DTC dental implant healthcare lead generation provider. The build shipped and the methodology was genuinely better than the spreadsheet and reporting stack it replaced. But this was an owner who knew his numbers like the back of his hand, which is exactly why a dashboard he could not reconcile to them was never going to survive.
Validation had been left as a spot check. Pull a report, compare a handful of records, gut check anything that looks off. That plan put the burden on the owner to notice what was wrong. He was not obligated to do that work, and eventually he stopped opening the dashboard at all. The build delivered. The validation did not.
The rule that came out of it
Numbers must reconcile line by line against the reports a client already trusts, for a full reporting period, before an engagement is called complete. The validation gate cannot be the client’s vigilance. It has to be the process.
What Does It Cost to Run on Numbers That Don’t Tie Out?
It costs you the ability to act on your own reporting, which is more expensive than the bookkeeping hours.
Month end stretches because someone is hunting a difference by hand instead of closing. Marketing decisions get made on revenue figures that have not been trued up, so a channel looks profitable in one system and ordinary in the other. And the quiet one: people stop trusting the screen. Once an owner has been burned by a number, every future number gets a second guess, which is the same as having no dashboard at all.
If your reports do not tie out, a free Profit Leak Audit traces your booked revenue back through your own systems and shows you where the numbers stop agreeing. Reconciliation is step one of the audit, because nothing downstream is trustworthy until it is done.
Do I Need to Replace ServiceTitan or QuickBooks to Fix This?
No, and switching usually makes it worse before it makes it better.
ServiceTitan is doing its job. It runs dispatch, jobs, and invoicing, and contractors who use it heavily are generally well served by it. QuickBooks is doing its job too. The gap is not inside either system. It lives in the space between them, in the definitions and the timing, which is exactly the part no software vendor owns.
A migration resets that space to zero and hands you a fresh set of undefined edges, plus a data conversion. If the reconciliation rules were never written down, you will be writing them anyway, only now on top of a new platform.
When this does not apply
If you run a single location with a light invoice volume, a formal monthly tie out is overkill. A quarterly spot check is probably enough. The program earns its keep when volume, locations, or the number of people touching the data grows past what one person can hold in their head.
Once the numbers tie out, the reporting on top of them becomes worth building. That is when a profit per job view starts telling you something you can act on, and it is one of the three hidden profit leaks most shops are already paying for.
The output you want is not a matched number. It is a written explanation for every difference.
If you would rather not run the tie out yourself, that is what we do first on every engagement. The Profit Leak Audit is free, read only, and the findings are yours to keep whether or not you ever work with us.
Frequently Asked Questions
Why does my ServiceTitan revenue look higher than my QuickBooks revenue?
Usually timing and deposits. ServiceTitan shows invoiced job value as the work happens, while QuickBooks may not recognize that revenue until the period it belongs to. Deposits collected before a job closes sit in liability rather than revenue. Credits issued after invoicing widen the gap further. Check timing first, then adjustments.
Should ServiceTitan revenue equal QuickBooks revenue?
Invoiced revenue for a closed period should tie out to the dollar. Recognized revenue often will not, and that is correct. Deposits, progress billing, credits issued after invoicing, and manual journal entries all create legitimate differences. The goal is not one identical number, it is a written explanation for every difference.
How often should I reconcile ServiceTitan and QuickBooks?
Monthly, on a closed period, once the rules are documented. The first reconciliation is slow because you are discovering the rules. After that it should take under an hour. Shops with low invoice volume and a single location can reasonably move to a quarterly check.
Is a mismatch between ServiceTitan and QuickBooks a sync error?
Sometimes, but process differences are more common. Sync failures look lumpy and traceable, such as a batch that never posted or an item with no account mapping. Process differences look steady and repeat every month, such as two people defining a completed job differently. Check the shape of the gap before blaming the integration.
Do I need to switch software to fix reporting that does not tie out?
Usually no. The gap lives between the systems, in definitions and timing, not inside either product. Migrating resets those edges to zero and adds a data conversion on top. If the reconciliation rules were never written down, you will have to write them regardless of which platform you land on.
Find where your numbers stop agreeing
A free Profit Leak Audit traces your booked revenue back through your own systems, read only, and shows you exactly where ServiceTitan and QuickBooks part ways. Reconciliation is step one, because nothing downstream is trustworthy until it is done. The findings are yours to keep whether or not you ever work with us.
Book a Profit Leak Audit