Why Your Field-Service App Never Matches QuickBooks (and How to Fix It)

The core mismatch: invoiced revenue vs. deposited cash

When you pull a revenue report from Jobber, ServiceTitan, or Housecall Pro, you see the total your customers were invoiced. When you open QuickBooks and look at what hit your bank account, you see deposits. Those two numbers are almost never the same, and the gap is not a software glitch. It is a structural difference in what each system is measuring.

The field-service app records an invoice the moment you send it or mark a job complete. QuickBooks records a deposit when money actually arrives in your bank, minus whatever the payment processor took out along the way. Without a deliberate reconciliation step, those two ledgers drift further apart every month.

The five culprits behind the gap

Most of the mismatch comes from a handful of predictable sources.

• Merchant processing fees: Card processors deduct their fee before sending the deposit, so a payment collected through Jobber Payments or Stripe lands in your bank net of the fee. The invoice was for the full amount. The deposit is lower. That difference needs to be recorded as a merchant fee expense, not treated as missing revenue.
• Batched deposits: Processors typically sweep all card payments settled in a day or week into a single deposit. One bank deposit can cover dozens of invoices. Unless you match the batch back to the individual invoices, you cannot see which jobs have actually been paid.
• Tips and surcharges: If customers pay tips or if your processor adds a convenience fee, those amounts appear in the processor settlement but may not map cleanly to any invoice line in your FSM tool. They need their own accounts in QuickBooks.
• Refunds and chargebacks: A refund issued through your FSM app reduces the original invoice. A chargeback comes through the processor and reduces a deposit. Both events need to be recorded in QuickBooks or your revenue total is overstated.
• Timing between invoice date and deposit date: Net-30 terms, check payments, or financing arrangements all create a gap between when a job is invoiced and when the money arrives. A month-end close that does not account for outstanding receivables will show the wrong revenue for the period.

Why it matters for job costing and margins

The revenue mismatch is not just a bookkeeping nuisance. It flows directly into the job-cost numbers you use to bid work and manage crews.

If your QuickBooks deposits are understated because merchant fees are coming out silently, your gross margin looks thinner than it is. If batched deposits are not matched to individual jobs, you cannot see which jobs were profitable and which were not. If refunds are not recorded, you are carrying phantom revenue. Any one of these gaps makes your job costing unreliable, and unreliable job costing is how contractors end up pricing the next job wrong.

How reconciliation actually works

A proper FSM-to-QuickBooks reconciliation has four steps, run each month after your processor closes its billing period.

First, pull the processor settlement report, not just your bank statement. The processor statement shows every transaction, every fee, every refund, and the net deposit for each batch. The bank statement only shows the net deposit. You need the processor statement to reconcile correctly.

Second, match each batch deposit in QuickBooks to the individual invoices it covers. This is usually done through a clearing account: each invoice payment flows into the clearing account at full invoice value, and the processor deposit flows out of the clearing account net of fees. The difference between those two amounts is the merchant fee, which gets posted to a merchant fees expense account.

Third, account for anything that does not map to an invoice: tips, convenience surcharges, refunds, and chargebacks each get posted to the correct account. Refunds reduce revenue. Chargebacks reduce deposits and may also trigger a dispute fee that needs to be expensed.

Fourth, run a three-way check: the total of all invoices marked paid in your FSM tool should equal the total of all payments recorded in QuickBooks, which should equal the total of all deposits from that processor plus the total of all fees expensed. If all three agree, the reconciliation is clean.

How a clean sync changes your close

The goal of a recurring FSM-to-QuickBooks sync is to make this reconciliation fast and reliable every month, rather than a detective exercise each time. A clean sync maps your FSM invoices, processor settlements, and QuickBooks entries so that deposits, fees, refunds, and tips all land in the right accounts automatically.

We include FSM-to-QuickBooks reconciliation on the Crew plan and up. We work inside your own QuickBooks Online file, so you keep full access to your books. Each month you get a reconciled close with merchant fees broken out, receivables tracked, and job-level revenue you can trust. If your FSM and QuickBooks have been drifting for months, we can also clean up the backlog so you start from a reliable baseline.

FAQ

Keep reading