Reconciling Merchant Processing Deposits to Bank Deposits

How to match card-processing batch settlements to the deposits that land in a business bank account, and why the two totals rarely match exactly.

9 min read · Updated October 6, 2026

Why processor volume and bank deposits diverge

Businesses that accept card payments typically receive a separate merchant processing statement showing gross card volume, refunds, chargebacks, and fees, alongside their bank statement showing the net amounts the processor actually deposits. These two documents describe related but not identical numbers, and reconciling them is useful both to validate reported card revenue and to confirm that bank deposits labeled as processor settlements are legitimate and complete.

The processing statement shows gross sales volume before fees are deducted. The bank deposit, by contrast, is usually the net amount after the processor's fees, and sometimes after holding back a reserve. Settlement timing also differs: a batch of card sales run on a Monday might not settle into the bank account until Wednesday or later, and weekend batches are often combined into a single Monday deposit.

The reconciliation steps

A workable reconciliation process follows these steps:

  • Identify processor-deposit candidates in the bank data — ACH credits from a recognized processor or acquiring bank name, usually recurring on a near-daily or business-day basis.
  • Pull gross volume, refunds, chargebacks, and fees for the same date range from the processing statement.
  • Estimate net settlement per batch: gross sales minus refunds, chargebacks, and fees for that batch, adjusted for any held reserve.
  • Match estimated net settlements to bank deposits by date proximity and amount, allowing for the typical settlement lag (commonly one to three business days).
  • Flag unmatched items on either side — a bank deposit with no corresponding processing batch, or a processing batch with no matching bank deposit — for follow-up.

A worked example

Consider a fictional retailer, Lakeside Outfitters. Its merchant processing statement for a given week shows daily gross card sales of $4,200, $3,950, $4,600, $5,100, and $8,700 (Monday through Friday, with Friday capturing weekend volume carried into that batch), refunds of $150 for the week, and processing fees of 2.6% of gross volume. Total gross for the week is $26,550; after $150 in refunds and approximately $690 in fees (2.6% of $26,550), estimated net settlement for the week is about $25,710.

On Lakeside's bank statement for the same week, four ACH credits appear from 'ABC Processing Inc.': $4,050 (Tuesday, for Monday's batch), $3,810 (Wednesday), $4,460 (Thursday), $13,540 (Monday of the following week, combining Friday's batch and the weekend). Summing these: $4,050 + $3,810 + $4,460 + $13,540 = $25,860. That's within about $150 of the estimated net settlement of $25,710 — a small difference consistent with rounding in the fee estimate and the exact timing of fee deduction, and well within a reasonable reconciliation tolerance. If the gap were several thousand dollars rather than $150, that would warrant flagging for review.

What reconciliation reveals

A clean reconciliation (deposits matching processing volume net of fees and refunds, within a small tolerance) corroborates that reported card revenue is real and is actually reaching the bank account — useful when card sales make up a meaningful share of a business's revenue. A reconciliation gap can indicate several things worth investigating: a reserve being held back by the processor, deposits being swept to a different account than the one reviewed, a second processor not included in the submitted statement, or, in less common cases, inconsistencies in what was reported.

Reviewer guidance

A reviewer should check that the date ranges on both documents actually overlap (processing statements and bank statements are not always aligned to the same billing cycle), that the fee rate used in the estimate is reasonable for the stated processor and card mix, and that any reconciliation gap is explained with a specific cause rather than dismissed. Multiple processor accounts for the same business are common (for example, a primary processor and a backup) and each should be reconciled separately before being summed.

See how LendLucid handles this in practice.

All resources