Why Clover Deposits Do Not Match Daily Sales

How to Reconcile Credit Card Settlements Without Misstating Revenue

A shop closes the day with $8,420 in card sales, but only $7,986 reaches the bank. The owner sees the difference and assumes something is missing. In many cases, the deposit is correct. The processor may have deducted fees, included sales from a different batch, withheld a chargeback, separated tips, or combined payments from more than one day. The accounting problem begins when the bank deposit is treated as the sales record.

Clover, Stripe, Square, QuickBooks Payments, and other processors move money in batches. The amount that reaches the bank is a settlement, not a complete description of what the shop sold. A reliable bookkeeping system must preserve the gross customer payments and then account separately for fees, refunds, tips, chargebacks, and timing differences. Otherwise, the shop may understate revenue, lose track of fees, duplicate income, or leave unexplained balances in QuickBooks.

Sales and Settlements Are Different Records

The point of sale or shop management system records what customers purchased. The payment processor records how those customers paid. The bank records the net cash that arrived. These are three related records, but they are not interchangeable.

Consider an illustrative daily batch with $8,000 of service revenue, $640 of sales tax, and $300 of employee tips. Gross card activity is $8,940. If the processor deducts $268 in fees and the entire batch settles together, the bank may receive $8,672. None of those numbers is automatically wrong. They describe different parts of the transaction. Revenue is $8,000, sales tax and tips are liabilities, processing fees are expenses, and the bank receives the net settlement.

The timing can create another difference. A transaction completed after the processor’s cutoff may appear in today’s sales report but tomorrow’s settlement. Weekend and holiday activity may be grouped together. Comparing one calendar day of sales with one bank deposit can therefore produce a difference even when every transaction is correct.

Why Posting the Net Deposit to Sales Fails

If the bookkeeper records the $8,672 bank deposit as sales, revenue is understated because processor fees were netted against it. Sales tax and tips may also be incorrectly included in income. The P&L no longer shows the full amount sold or the actual cost of accepting cards. That makes pricing and service profitability harder to evaluate.

The opposite problem occurs when sales are already recorded through invoices or sales receipts and the bank feed deposit is added as new income. The books then contain both the original sale and a second income transaction for the settlement. Revenue is overstated even though the bank account may still reconcile.

A bank reconciliation proves that the recorded bank balance matches the statement. It does not prove that every deposit was classified correctly. A duplicated sale and an offsetting error can still produce a reconciled bank account.

How a Clearing Account Works

A payment processor clearing account acts as a temporary bridge between customer payments and bank settlements. When a customer pays, the gross payment moves into the clearing account. The related invoice or sales receipt records revenue, sales tax, and any tip liability. When the processor sends a settlement, the net cash moves from the clearing account to the bank. Fees, refunds, chargebacks, and other adjustments are also recorded against the clearing account.

After all activity for a batch has been recorded, the clearing account balance for that batch should return to zero. A timing balance may remain at month end when a payment was processed before the cutoff but settled afterward. The important point is that the balance must be explainable by specific unsettled batches or documented adjustments.

This structure makes the processor settlement report the controlling record for deposits. The bank feed is used to match the net deposit, not to invent the underlying sales. That distinction protects the income statement and preserves a clear audit trail.

What Causes the Difference

Processing fees are the most familiar difference, but they are not the only one. Common causes include:

Each item should have its own account so the owner can see the economics of accepting the payment. Burying everything in one net deposit may make data entry faster, but it removes information the shop needs for management.

A Daily Reconciliation Process

The closing report should identify gross sales, sales tax, tips, refunds, discounts, and each payment method. The processor report should identify the card transactions included in each batch. The settlement report should show the net amount and every deduction. Someone should confirm that the expected batch reached the clearing account and that unusual items were documented.

The process should also confirm that cash, checks, financing proceeds, and card payments were not mixed together. A customer may pay a deposit by card and the final balance by cash. The job record should show both payments while the settlement report includes only the card portion.

Daily review catches errors while the transactions are still familiar. Waiting until month end can turn one missing batch into hours of research across work orders, processor portals, bank feeds, and customer records.

The Month End Reconciliation

At month end, reconcile the processor clearing account separately from the operating bank account. List deposits in transit, unresolved chargebacks, pending refunds, and processor adjustments. Compare processing fee expense with processor reports. Confirm that tip and sales tax liabilities make sense. Large or old clearing balances should be investigated instead of rolled into the next month.

This review is especially important when multiple systems are connected. An invoice may originate in Urable, TintWiz, Jobber, or another platform, while Clover processes the payment and QuickBooks receives both an integration and a bank feed transaction. Automation saves time only when each system has a defined role. Without that map, the same activity can enter the books twice.

Document how transactions should flow. Identify where the sale begins, where the payment is recorded, how the settlement reaches QuickBooks, and who reviews exceptions. When software changes, test the full path before assuming the integration is correct.

Warning Signs

Several patterns indicate that settlements are being handled incorrectly. Revenue may equal the exact amount of net bank deposits, processing fee expense may be unusually low, or the same processor deposit may appear in both Undeposited Funds and income. The clearing account may carry a large balance for months, or deposits may be split across revenue accounts without customer level support.

Another warning sign is forcing a deposit to match by changing sales. A difference should be traced to the processor report, not buried in an uncategorized account. Small unexplained amounts can accumulate into a meaningful reporting problem in a high-volume shop.

A processor deposit should match the processor settlement, while sales should match the underlying customer transactions. When those records are kept separate and connected through a clearing account, the owner can see gross revenue, fees, taxes, tips, refunds, and actual cash received.

If yesterday’s sales do not match today’s deposit, do not force the numbers together. Reconcile the path the money traveled. The Tounsley Group helps shops build bookkeeping systems that reflect the transaction from estimate through final settlement.