Why don't ServiceTitan batch deposits match the bank in QuickBooks?

They don’t match because ServiceTitan posts each customer payment at the amount collected, while the bank shows one processor deposit, often net of fees, refunds, and holds. Until those payments are grouped into one QuickBooks deposit that equals the bank line, Match has nothing the same size.

A batch is the group of payments meant to equal one bank deposit. The processor payout is that deposit hitting checking. The native ServiceTitan sync posts the invoices and payments so you are not retyping them. It does not group those payments the way the processor grouped them, and it does not net the fee. QuickBooks Match only fires when one deposit record equals that bank line to the cent. The click path that builds that deposit is how to reconcile ServiceTitan deposits in QuickBooks Online. This page is why the four lists disagree before you get there.

Four lists, four numbers

The bank shows one number. ServiceTitan and QuickBooks show many.

List	What it shows	Why it disagrees with the bank
ServiceTitan deposit or payment batch	Gross payments the office grouped	Fees, refunds, and holds often still sit inside the gross
Processor settlement	Net deposit, fees, refunds, holds, deposit date	This is the number that should equal the bank, often days later
Undeposited Funds	Each exported payment as its own line	Many lines against one lump
Bank feed	One lump the processor sent	No invoice list, and the text is usually generic

ServiceTitan’s payments overview, read 2026-10-07, is apply, batch, post, export. After export, a positive payment credits Accounts Receivable and debits Undeposited Funds. After you record the QuickBooks deposit, Undeposited Funds credits and the bank debits. Until that last step, the bank line and the books are different jobs.

If the shop uses ServiceTitan Payments with Adyen, autobatched deposits appear each morning to match that day’s bank settlement. You still export the batch and build the matching QuickBooks deposit. Autobatch names the group. It does not post the QuickBooks deposit for you.

Gross payments, net bank line

The usual miss is gross in QuickBooks and net at the bank. ServiceTitan’s Adyen autobatching help, read 2026-10-07, states the deposit Total is net, gross minus fees. Their example is a $5,000 gross deposit with $125 in fees, Total $4,875. Review Gross Fees on Bank Deposits, then Amount of Fees on the Adyen Settlement report.

That $125 never shows as its own bank line. The processor already took it. Intuit’s record bank deposits help, updated 2026-08-03, puts processing fees on the same Bank Deposit as a negative line. ServiceTitan’s own QBO steps say the same, with fees of $100 entered as -100. A fee expense posted as a separate deposit will sit unmatched forever.

Refunds in the same settlement reduce the net the same way. ServiceTitan’s refund article, read 2026-10-07, is written for Desktop, and the miss happens in Online too. The TSYS Settlement report shows the refund. QuickBooks only offers it on the Bank Deposit screen if that refund type maps to Undeposited Funds. Map it there, or the deposit you build will be high by the refund.

Holds work the other direction. The TSYS Settlement report has a Hold Amount column for money the processor has not paid yet. That cash is in ServiceTitan. It is not in this week’s bank line. Leave it unmatched until a later settlement releases it.

Shops that run TSYS cards and Adyen Pay-By-Bank get two cadences. ServiceTitan’s Adyen fee article says you will see a daily net for Pay-By-Bank and a monthly net for TSYS. Two processors, two lumps, two QuickBooks deposits.

One bank line, many payment lines

Intuit’s deposit help, updated 2026-08-03, says it outright. When the bank groups several payments into one total, and you record each payment separately, the records will not match the bank. Use Bank Deposit to combine them.

Intuit’s Undeposited Funds help, read 2026-10-07, says every payment in that account appears on the Bank Deposit screen. Find the account by detail type Undeposited Funds, even if someone renamed it Payments to deposit. Check only the payments in this settlement. Save. That one deposit is what Match can see.

Intuit’s categorize help, updated 2026-08-24, treats Categorize or Post as a new ledger entry. Take Match when QuickBooks offers the deposit you just saved. Categorize on a ServiceTitan payout records the cash twice. A bank rule that auto-adds processor deposits to income does the same thing overnight.

ServiceTitan’s Touchless Integration FAQ, read 2026-10-07, says shops on that path now get a Bank Deposit journal entry from ServiceTitan, and QuickBooks can suggest a match by amount and date. QuickBooks does not confirm the suggestion is the right settlement. Check it. Shops still on the Undeposited Funds path have to build the deposit themselves.

Settlement lag and two batch numbers

The batch date in ServiceTitan is the day the office grouped the payments. The bank date is the day the processor funded checking. ServiceTitan’s reconcile guide, read 2026-10-07, puts card settlements at 1 to 2 business days and ACH at 3 to 5. Weekend and holiday batches pile up. Tuesday deposits run fat. ACH payments show “Payment Submitted - Pending Settlement,” which is expected.

On a TSYS shop, the TSYS batch number is not the ServiceTitan export batch number. Match TSYS batches to QuickBooks Online deposits, read 2026-10-07, uses the TSYS Settlement report. Match Net Deposit to the bank. Double-click the TSYS batch for each payment, refund, hold, and ServiceTitan payment-batch number, then build the QuickBooks deposit from that list. Matching on the ServiceTitan export batch ID against a TSYS-sized bank line is why the totals look random.

ServiceTitan’s payments overview says to batch after the payment is in the bank, the check has cleared, or the merchant has funded the card. You can batch cash and checks earlier. Post and export those only after they have been deposited and cleared. A batch of Friday card swipes will not equal Friday’s bank line.

The export never landed where Match looks

ServiceTitan’s deposit-into-QuickBooks article, read 2026-10-07, names two export paths. The default debits Undeposited Funds and credits Accounts Receivable. A journal-entry export debits the account you mapped instead. Those lines never appear on the Bank Deposit screen. Find them in that account’s register and match the bank feed to that journal.

QBO onboarding, read 2026-10-07, tells you to leave Accounts Receivable and Undeposited Funds active. Deactivating either one dumps the next export somewhere Match cannot see.

“Exported” on the batch is not the same as synced. ServiceTitan’s reconcile guide says a batch can show Exported while one record still sits on Error. Read the per-record status on the Pending Export Report. Zero-dollar payments do not transfer. If a payment is missing in QuickBooks, look there before you re-export.

One bookkeeper on r/Bookkeeping in June 2026 described the QuickBooks connection dropping, a backlog of unexported payments, and the register falling behind until the link came back. Another, in July 2026, described about $20,000 of ServiceTitan deposit-report lines that never hit the bank, and about $50,000 of bank deposits missing from the ServiceTitan report. Treat the four lists as separate. Match by date, amount, batch, invoice, and customer. A bad match in QuickBooks makes AR look cleaner than it is.

ServiceTitan’s Deposit Workflow is a different job. An unapplied customer payment exports as a debit to Undeposited Funds and a credit to a liability. That is a down payment on unfinished work, not the processor payout. Apply it to the invoice in ServiceTitan when the job is done, then export.

Symptom	Likely cause
QuickBooks total is higher than the bank by about the fee	Gross payments, net deposit
Bank line has no matching deposit	Batch never exported, still on Error, or exported as a journal
ServiceTitan report has deposits the bank never got	Timing, holds, or a report that is not the settlement
Bank has deposits missing from ServiceTitan	Another processor, a manual deposit, or a batch never created
Undeposited Funds keeps growing	Payments exported, never grouped
Deposit exported as a journal	Journal-entry export, Match the feed to that journal
Refund in the settlement, missing on the deposit screen	Refund type mapped off Undeposited Funds

What still works

The native ServiceTitan sync wins the posting job. It is included with the FSM and creates the invoices and payments so you are not retyping them. Undeposited Funds, reconciled by a careful bookkeeper, does tie out. Someone still has to group the payments the processor grouped, and catch the fee.

If a payment was recorded twice, once in ServiceTitan and once by hand, confirm against the settlement report before you void either one. Keep the memo. Prefer exclude or void with a memo over a bulk delete.

Pull last week’s ServiceTitan deposit or Adyen or TSYS settlement report, the bank statement, and the Undeposited Funds detail in QuickBooks. Start with those three files. They already exist.