Why does my CRM show more revenue than QuickBooks for the same month?

The most common reason is timing: your CRM counts a job as revenue when it is completed, while QuickBooks counts revenue when payment is received. At any point in the month, open invoices that have been completed but not yet paid create a gap. If the gap persists after adjusting for open invoices, look at how your CRM handles cancelled jobs and post-invoice discounts, both of which can inflate the CRM total without a matching QuickBooks entry.

How do I reconcile ServiceTitan revenue with QuickBooks?

Start by pulling both reports for the same closed month, then match totals by category: completed jobs in ServiceTitan against paid invoices in QuickBooks. Differences will fall into one of a few buckets: open invoices, cancelled jobs not voided in ServiceTitan, discounts applied after invoicing, or partial payments. Establishing a crosswalk document that maps ServiceTitan job types and lead sources to QuickBooks classes or cost centers is the foundation of a repeatable reconciliation. Teams using a unified dashboard configured to connect both sources can surface this reconciliation check automatically rather than building it manually each month.

Which number should I use for KPIs, CRM revenue or QuickBooks?

Use CRM revenue for operational KPIs: average ticket, booking rate conversion, technician revenue per job, and anything tied to daily or weekly performance management. Use QuickBooks revenue for financial KPIs: gross margin, labor percentage, net operating income, and any number that will appear on a financial statement or be shared with a lender. The key is to document which definition each KPI uses and apply it consistently so managers are not comparing percentages calculated on different bases.

Does a dashboard tool fix the mismatch between QuickBooks and my CRM?

A unified dashboard surfaces the mismatch and makes it visible in real time, which is a major improvement over finding the problem at month-end. It does not fix bad data upstream. If cancelled jobs are not voided in your CRM, or discounts are not captured at the field level, the dashboard will accurately display the gap between two imperfect sources. The field-level fixes in your CRM settings and the class mapping in QuickBooks have to happen first. The dashboard then tells you whether those fixes are holding.

How big of a variance between QuickBooks and my CRM is normal?

For most home-service companies, a variance of 1–3% at month-end is common and usually explained by open invoices that cleared in the following period. A persistent variance of 5% or more after adjusting for timing typically points to a structural issue: cancelled jobs not being voided, discounts not captured in the CRM, or multi-department coding that splits differently in each system. If your variance is consistent every month at roughly the same percentage, it is almost always a definition problem rather than a sync problem.

Why is my labor percentage different depending on which revenue number I use?

Labor cost is fixed at the amount paid to your team. If your CRM booked revenue is 6% higher than QuickBooks collected revenue, the same labor cost looks lower as a percentage of CRM revenue and higher as a percentage of QuickBooks revenue. For financial decisions, including whether to hire, what to price at, and how to report to investors, labor percentage should always be calculated against QuickBooks collected revenue. Using CRM revenue inflates the apparent efficiency of your business.

What is the easiest first step to stop QuickBooks and CRM from showing different numbers?

The highest-impact first step is usually not a technical fix. It is defining, in writing, which revenue number owns which business decision. Post it in your weekly reporting template and make it explicit at your next management meeting. This stops the argument immediately and gives your team a rule to follow while you work through the upstream data fixes. The second step is auditing how your CRM handles cancelled jobs and post-invoice discounts, because those two categories almost always explain the majority of the structural gap.

Can Housecall Pro and QuickBooks show the same revenue if set up correctly?

They can get much closer with careful setup. The main levers are: setting Housecall Pro to record revenue on the same basis as QuickBooks (cash or accrual), voiding cancelled jobs in Housecall Pro on the same day they are cancelled, configuring discounts to capture the net amount, and mapping Housecall Pro job types to QuickBooks classes. Even with good setup, a small timing variance is normal. A real-time dashboard that shows both figures and the gap gives you a standing check rather than a surprise at month-end.

When QuickBooks and your CRM reports don't match: what it means and how to fix it

Your CRM says October revenue was $412,000. QuickBooks says $389,000. Both systems are technically correct, and that gap is costing you real money in bad decisions, stalled closes, and a finance team that has stopped trusting its own numbers.

By Datacube content engineAutogeneratedJune 24, 2026

The problem

Two systems, two different answers, one expensive problem

Every home-service company with both a CRM and an accounting system eventually faces this moment: the numbers disagree, everyone defends their system, and no one can make a confident decision until someone exports three spreadsheets and spends an afternoon reconciling them. It is not a one-time data glitch. It is a structural gap between how a CRM records jobs and how QuickBooks records money that, if left unresolved, quietly corrupts every KPI report in the business.

Monthly revenue in your CRM is consistently 5–15% higher or lower than QuickBooks shows for the same period

Finance closes the books on the 10th but the sales team is still claiming October numbers the CRM never corrected

Refunded jobs, partial payments, and warranty calls reduce QuickBooks revenue but stay as booked revenue in the CRM

Lead source attribution in the CRM doesn't reconcile to the deposit lines in QuickBooks, so ROAS is calculated on the wrong base

You can't confidently tell an investor or lender which revenue number is correct, because the answer depends on which system they're looking at

Your controller and your operations manager disagree on gross margin because they're each pulling from a different tool

Why QuickBooks and your CRM measure revenue differently

A CRM like ServiceTitan, Workiz, or Housecall Pro is built to track jobs: what was booked, dispatched, and completed. It records revenue at the point a job is finished or invoiced. QuickBooks, on the other hand, records revenue when money moves: a deposit collected, a check cleared, or an invoice marked paid. Those two definitions of "when revenue happened" almost never align perfectly, and every edge case in your business, cancelled jobs, partial payments, warranties, discounts applied after the fact, splits between trade departments, widens the gap.

Neither system is wrong. They are measuring different things. The problem is that most contractors run their business as if both systems should agree, and when they don't, managers default to whichever number makes their department look better. That is when a reporting gap becomes a management problem.

Seven root causes of QuickBooks and CRM mismatches (and where each shows up)

Root cause	How the CRM records it	How QuickBooks records it	Typical gap size
Accrual vs. cash timing	Revenue posted when job is completed or invoiced	Revenue posted when payment is received or deposited	Varies; worst at month-end with open invoices
Cancelled or voided jobs	May stay as completed if not updated; offset by a separate credit	Voided in QuickBooks immediately; credit memo reduces AR	1–4% of monthly booked revenue, varies by business
Warranty and callback calls	Shows as a job with $0 revenue, but counts toward job count and tech metrics	Often posted as a negative adjustment against COGS; no revenue line	Inflates CRM average ticket; mutes QuickBooks margin
Discounts applied post-invoice	Original invoice amount stays; discount may be tracked separately or not at all	Collected amount is the QuickBooks revenue line; discount is explicit	Typically 2–6% of total revenue, higher in competitive markets
Partial payments and payment plans	Full invoice amount shows as revenue once job is complete	Only collected amounts post; remainder stays in AR	Material on install and replacement jobs with financing
Lead source attribution	CRM tags each job with a lead source; revenue credited to that source	QuickBooks has no lead source concept; revenue is by customer/invoice	ROAS and cost-per-lead become unreliable; marketing budget is at risk
Multi-department jobs (HVAC + plumbing on one visit)	Split by department in CRM; each department gets its revenue share	One invoice in QuickBooks, often coded to a single class or department	Department P&L in QuickBooks understates or overstates one side

Warning

Data visibility gap: the decision you're making on the wrong number

When a contractor uses CRM revenue to set the marketing budget and QuickBooks revenue to calculate labor percentage, those two percentages describe different businesses. A labor cost of 28% against CRM revenue might look fine. Against QuickBooks net collected revenue it could be 31% or higher. The gap is not academic: it determines whether you hire another tech, raise prices, or cut ad spend. Running the two numbers separately, without knowing which decisions belong to which definition, is one of the most common and hardest to spot causes of margin erosion in home-service companies.

Reconciliation health check: where does your business stand?

Run these checks against your last closed month. Each one surfaces a different layer of the QuickBooks-CRM gap.

Revenue variance (CRM vs. QuickBooks, same period)Over 5% usually means a structural definition problem, not a sync issue
Watch
Current
Check yours
Target
Under 2%
Cancelled job handling: are voids reflected in both systems within 24 hours?Delayed cancellations inflate CRM revenue at month-end
Watch
Current
Check yours
Target
Yes, same day
Discount tracking: does your CRM capture the net-of-discount amount?Most CRMs default to pre-discount; you need to configure this or adjust downstream
Poor
Current
Check yours
Target
Net amount tracked
Lead source revenue: is there a mapping between CRM source tags and QuickBooks classes?Without this, ROAS is calculated on CRM revenue that QuickBooks never confirms
Poor
Current
Check yours
Target
Mapped and current
Multi-department job coding: do QuickBooks classes match CRM department splits?Common failure point for HVAC+plumbing or service+install shops
Watch
Current
Check yours
Target
Aligned
Frequency of manual reconciliation: how often does finance manually adjust numbers?Frequent manual fixes signal that the integration or field definitions need a permanent fix
Good
Current
Check yours
Target
Rare, documented

Metric	Current	Target	Status
Revenue variance (CRM vs. QuickBooks, same period)Over 5% usually means a structural definition problem, not a sync issue	Check yours	Under 2%	Watch
Cancelled job handling: are voids reflected in both systems within 24 hours?Delayed cancellations inflate CRM revenue at month-end	Check yours	Yes, same day	Watch
Discount tracking: does your CRM capture the net-of-discount amount?Most CRMs default to pre-discount; you need to configure this or adjust downstream	Check yours	Net amount tracked	Poor
Lead source revenue: is there a mapping between CRM source tags and QuickBooks classes?Without this, ROAS is calculated on CRM revenue that QuickBooks never confirms	Check yours	Mapped and current	Poor
Multi-department job coding: do QuickBooks classes match CRM department splits?Common failure point for HVAC+plumbing or service+install shops	Check yours	Aligned	Watch
Frequency of manual reconciliation: how often does finance manually adjust numbers?Frequent manual fixes signal that the integration or field definitions need a permanent fix	Check yours	Rare, documented	Good

A practical action plan for contractors with mismatched reports

01
1. Define which number owns each decision
Before fixing the systems, fix the policy. Decide: CRM revenue owns sales performance, booking rate, and average ticket. QuickBooks revenue owns financial statements, labor percentage, gross margin, and anything you would show a lender or investor. Document this and put it in the weekly reporting template. This alone eliminates most of the argument.
02
2. Audit the seven causes in the table above for your specific setup
Pull one closed month and walk through each mismatch category. Which ones apply? Timing and cancellations almost always do. Partial payments and multi-department splits depend on your business model. Identify the top two or three contributors before trying to fix everything at once.
03
3. Standardize field definitions in your CRM
If your CRM allows it, configure discount fields to capture net amounts, set a standard for how cancelled and warranty jobs are coded, and establish a rule for when a job counts as complete for revenue purposes. These configurations typically live in your CRM admin settings and do not require developer help.
04
4. Map CRM job types and lead sources to QuickBooks classes
Create a simple crosswalk: CRM lead source X maps to QuickBooks class Y. If your CRM has department splits for HVAC and plumbing, make sure each department maps to the correct QuickBooks cost center or class. This mapping lives outside both systems, often in a shared doc, until you have a unified dashboard that enforces it.
05
5. Build one unified view that shows both numbers and flags the variance
The goal is not to make the two numbers identical; they measure different things. The goal is to see both numbers in one place, labeled correctly, with the variance calculated automatically. When a unified dashboard shows CRM booked revenue, QuickBooks collected revenue, and the gap between them as a single row, the reconciliation happens every day instead of on the 10th of the month.

Info

Owner takeaway: what a 6% revenue discrepancy actually costs in bad decisions

Consider a hypothetical plumbing and HVAC shop with $4 million in annual CRM booked revenue and a persistent 6% gap versus QuickBooks collected revenue. That is roughly $240,000 in revenue the owner believes they earned but cannot find in the bank. If the labor percentage is being calculated against the higher CRM number, it looks like 26%. Against the QuickBooks figure it is 27.5%. That 1.5-point difference over a $4M business is $60,000 a year in misattributed labor cost. The actual dollars lost depend on your trade, your market, and your business model, but the direction of the error is consistent: CRM-only operators overpay in their mental model of how the business is performing. These figures are illustrative; your gap may be larger or smaller.

What a unified financial view looks like across both systems

When QuickBooks and your CRM feed a single dashboard, the reconciliation check becomes automatic. Here is the kind of cross-system financial view a GM or controller sees in a datacube Financial board, designed to consolidate sources including QuickBooks and your CRM.

Dashboard preview

Figures are illustrative. Your live datacube board reflects your own connected QuickBooks and CRM data with your definitions applied.

What a unified dashboard can and cannot fix

A cross-system dashboard can surface the variance, label it correctly, and alert you when it grows beyond your tolerance. It can show QuickBooks and CRM revenue side by side so the gap is never hidden. For teams using ServiceTitan or Housecall Pro alongside QuickBooks, a datacube Financial board can be configured to pull from both and display the reconciliation check as a standing KPI rather than a monthly fire drill.

What a dashboard cannot do is fix bad data upstream. If cancelled jobs are not voided in the CRM, if discounts are not captured at the field level, or if two departments are coded to the same QuickBooks class, the dashboard will show the clean summary of messy inputs. The action plan above, specifically steps 3 and 4, addresses the upstream fixes. The dashboard is the visibility layer that tells you whether those fixes are working.

For contractors where the mismatch runs deeper, often because different managers have been using different definitions for years, see inconsistent KPI definitions. That page covers how to align on shared definitions across locations and departments before a reporting build starts.

What to take away from this page

QuickBooks and CRM revenue measure different things: collected cash versus completed-job invoices. A variance under 2% is typical. Over 5% signals a structural definition problem.
The seven most common causes are timing, cancellation handling, warranty jobs, post-invoice discounts, partial payments, missing lead-source mapping, and multi-department coding mismatches.
The fix starts with a policy decision: which number owns which business decision. Then standardize field definitions, map departments, and verify with a shared view.
A cross-system dashboard shows both numbers and the variance in one place, making reconciliation a standing KPI rather than a monthly manual exercise.
Calculating labor percentage or margin against CRM revenue instead of QuickBooks collected revenue is one of the most common sources of silent margin erosion in home-service businesses.

QuickBooks and CRM mismatch FAQs

See both numbers in one place, every day

Book a live demo and we will show you how a datacube Financial board can be configured to pull from your CRM and QuickBooks simultaneously, flag the variance automatically, and give your controller and your GM the same number for the same decision. No more two-spreadsheet reconciliation on the 10th.

Schedule a live demo Self-guided demo

Keep exploring

How to fix review requests not convertingDiagnose and fix review requests not converting with the right dashboard view.

How to fix sales close rate problemsDiagnose and fix sales close rate problems with the right dashboard view.

How to fix service department profitabilityDiagnose and fix service department profitability with the right dashboard view.

How to fix ServiceTitan reporting limitationsServiceTitan is a powerful field-service CRM, but its built-in reporting has blind spots that operators only discover mid-month, when the revenue is already gone. This page maps the specific gaps, the KPIs they obscure, and the cross-tool view that closes them.

Go deeper