Payment Reconciliation: Why the Deposit Never Matches the Sales

Payment Reconciliation: Why the Deposit Never Matches the Sales | HL Hunt
Payments & AI

Payment Reconciliation: Why the Deposit Never Matches the Sales

You processed $12,400 yesterday. This morning $11,847.32 landed. Nobody sent an explanation, and the difference isn't just the fees. Between a card being tapped and money reaching your account sit batch timing, fee structures, refunds netted from unrelated days, chargebacks, reserve holds, and adjustments — and the only party checking whether the arithmetic is correct is you. Processors make errors. Rates get applied incorrectly. Deposits go missing. None of it surfaces unless someone reconciles. This guide covers how settlement actually works, how to match payouts to transactions, and how to build a process that catches the money you're owed.

By the HL Hunt Research Desk · 15 min read · Updated August 2026

What sits between sale and deposit

The chain from authorization to funds is longer than most merchants realize, and each step can introduce a difference.

  1. Authorization — the card is approved but no money moves.
  2. Capture — the transaction is submitted for settlement, which may be immediate or delayed until fulfillment.
  3. Batching — captured transactions are grouped, typically once daily at a cutoff time you may not control.
  4. Settlement through the networks and acquirer.
  5. Funding to your account, on a schedule that varies by provider and risk profile — per our funding guide.

The differences that arise along the way:

  • The batch cutoff isn't midnight. Sales after cutoff settle with the next batch, so a calendar day of sales and a batch are different sets of transactions. This alone explains most of the confusion.
  • Authorized and captured amounts can differ — tips added after authorization, partial shipments, or adjusted amounts.
  • Refunds are netted against incoming funds, and a refund for a sale from three weeks ago reduces today's deposit.
  • Chargebacks and their fees are deducted when they occur.
  • Reserves may be withheld from each payout.
  • Fees are deducted per transaction or billed monthly depending on your settlement model.

Which produces the foundational instruction: stop comparing deposits to daily sales. That comparison will never balance, and merchants who attempt it conclude either that their processor is stealing from them or that reconciliation is impossible. Match payouts to the batches they represent.

Gross versus net settlement

This determines your entire accounting approach and many merchants don't know which one they have.

Net settlementGross settlement
What arrivesSales minus fees, in one amountFull sales amount
FeesAlready deductedDebited separately, usually monthly
Reconciliation difficultyHarder — two flows combined into one numberEasier — flows visible independently
Fee visibilityMust be reconstructed from statementsDirectly observable
Cash flowSmootherLarger deposits, one larger monthly debit
PrevalenceMore commonFrequently available on request

Gross settlement is meaningfully better for anyone who wants to understand their costs. It separates revenue from expense at the source, which makes the effective rate immediately visible, makes fee errors obvious, and produces cleaner books. The trade-off is a single larger monthly debit that has to be planned for in cash flow — a real consideration for a thin-margin business, and usually worth it.

If you're on net settlement, ask whether gross is available. Many providers offer it and never mention it.

Nobody else is checking
Your processor won't tell you they applied the wrong rate, missed a deposit, or double-charged a fee. There is no audit function watching this on your behalf — reconciliation is the only thing that finds it.

Matching at the right level

Effective reconciliation happens at three levels, and each catches different problems.

Payout level — does the deposit equal what the payout report says it should? This catches missing deposits, short deposits, and duplicate deposits. Fast, and it should be done as deposits arrive.

Transaction level — does every transaction you recorded appear in a payout, and does every transaction in a payout correspond to something you recorded? This catches transactions that never funded, transactions funded at the wrong amount, and — importantly — transactions in your payout that you have no record of, which can indicate a genuine problem.

Statement level — do the fees charged match your agreed pricing? This is monthly and it's where pricing errors surface.

The practical sequence:

  1. Export the payout report from your processor with the transaction detail behind each payout.
  2. Match the payout total to the bank deposit. Differences here are usually timing or a missing payout.
  3. Match transactions in the payout to your own records — order system, invoicing system, or point of sale.
  4. Identify unmatched items on both sides and categorize them: timing, refund, chargeback, fee, or genuinely unexplained.
  5. Investigate the unexplained ones rather than writing them off.

The rule that matters: a small persistent difference is almost never rounding. It's usually a systematic error — a fee applied incorrectly, a transaction type mishandled, a rounding convention that runs one direction. Writing off $30 a day because it's small is writing off roughly $11,000 a year and never finding out why.

The deduction categories

Each of these belongs in its own bucket rather than netted into a single difference:

  • Processing fees — per-transaction, percentage, and monthly. The structure is in our fees guide, and the components should be separable.
  • Refunds, which reverse a prior sale and may or may not return the original processing fee depending on your agreement — worth knowing, since it affects your true refund cost, per our refund guide.
  • Chargebacks, which have multiple components and deserve their own treatment below.
  • Reserve withholdings — money held rather than lost, which means it's an asset on your books and not an expense. Merchants routinely record reserves as costs, understating both assets and margin.
  • Reserve releases, arriving later and easily mistaken for an unexplained credit.
  • Adjustments — corrections, interchange adjustments, and network fees.
  • Third-party deductions where a platform or gateway takes its own cut.

On chargebacks specifically: a single dispute typically produces the reversal of the sale amount, a separate chargeback fee, and — if you win — a later credit returning the sale but usually not the fee. Recording these as one net adjustment destroys the two numbers you actually need: what disputes cost you and what your win rate is. Both are essential to the economics in our chargeback guide, and neither is recoverable from netted entries.

Recording it properly

The accounting treatment that makes the books usable:

  • Record revenue at the sale, gross, at the full transaction amount — not at the net deposit. Recording revenue net of fees understates both revenue and expenses and makes your cost of acceptance invisible.
  • Use a clearing account for funds in transit. Sales debit the clearing account; deposits credit it. The balance represents money processed but not yet received, which should be explainable at any moment and is a genuine receivable.
  • Record processing fees as an operating expense in their own account, so the annual number is visible.
  • Record reserves as an asset, not an expense.
  • Record chargeback losses separately from processing fees, since they're a different problem with different remedies.
  • Reconcile the clearing account monthly. A growing unexplained balance is the clearest signal that something is wrong, and it's the single most useful control in the whole process.

The reason this matters beyond tidiness: a business that records revenue net of fees cannot tell you what it pays to accept payments. Which means it can't evaluate a competing quote, can't calculate whether the surcharging in our surcharge guide is worth the compliance burden, and can't tell whether routing large transactions to bank rails would save anything.

The monthly statement review

Payout reconciliation catches missing money. Statement review catches wrong pricing, and it's the one merchants skip.

Calculate your effective rate — total fees divided by total volume — and track it monthly. It should be stable. When it moves, something changed, and the causes are worth knowing:

  • Card mix shifted toward higher-cost card types, which is normal and outside your control.
  • Transactions downgraded to more expensive interchange categories because data wasn't submitted correctly — which is in your control and is a common, quiet cost, particularly on business card transactions per our B2B guide.
  • New fees appeared, including pass-through network fees and compliance charges.
  • Your rate changed, which does happen, sometimes with notice buried in a statement message.

What to verify each month: that the rate matches your agreement; that monthly fees match what you agreed to; that no new line items appeared unexplained; that chargeback and refund counts match your own records; and that any fee you don't recognize gets questioned. Ask about anything unfamiliar — the answer is sometimes that it shouldn't be there, and it will not be reversed if nobody asks.

Errors worth finding

The recurring findings when merchants reconcile properly for the first time:

  • Missing payouts — a batch that never funded, occasionally sitting unnoticed for weeks.
  • Duplicate refunds, where a customer was refunded twice through different channels.
  • Refunds processed without the original sale being located, which can indicate a process problem or something worse.
  • Rate errors, where the applied pricing doesn't match the agreement.
  • Fees for services not used, including equipment no longer in service and add-ons never activated.
  • Chargebacks not deducted and then deducted twice.
  • Reserve releases never received, which is money owed to you that arrives only when requested.
  • Transactions captured but never settled, which is revenue you recorded and were never paid.

That last one deserves emphasis: an authorized transaction that was never captured, or captured and never settled, is a completed sale you weren't paid for. It doesn't announce itself — the customer received the goods and your system shows an approval. Only transaction-level matching finds it.

Building the process

What a workable process looks like at different scales:

Small volume: daily payout-to-deposit check, weekly transaction-level match, monthly statement review with effective rate calculation. Spreadsheets are adequate.

Growing volume: automated transaction matching with rules, exception queues for unmatched items, a clearing account reconciled monthly, and effective rate tracked as a metric someone owns.

Higher volume or multiple providers: automated matching across sources, exception handling with defined thresholds and ownership, and reconciliation as a closing task rather than an ad hoc one.

Design principles that hold at every scale:

  • Automate the matching, not the judgment. Rules should clear the routine 95% so people look at exceptions.
  • Set an exception threshold with an owner, so items don't accumulate unexamined.
  • Never write off unexplained differences as policy — investigate a sample even when the amounts are small, because the pattern is the finding.
  • Keep the data. Payout reports and statements should be retained, since investigating a six-month-old discrepancy requires them and providers don't keep them accessible forever.
  • Reconcile the clearing account monthly without exception. It's the control that catches what the others miss.

Multiple rails and providers

Reconciliation complexity grows faster than volume when you add providers, and this is where most merchants lose track.

The complications:

  • Different settlement timing per rail — cards, ACH per our bank payments guide, and wallets all fund on different schedules.
  • Different report formats requiring separate mappings.
  • Different fee structures, making blended cost analysis harder.
  • Returns behaving differently. An ACH return can arrive long after settlement — the finality gap that catches merchants coming from cards.
  • Orchestration layers adding a reconciliation step, per our orchestration guide.
  • Platform deductions where a marketplace takes its cut before you see anything.

The approach that works: reconcile each rail separately against its own source, then consolidate. Attempting a single combined reconciliation across providers with different timing and formats produces a difference nobody can decompose — and a reconciliation you can't explain is one you'll eventually stop doing.

Reporting that reconciles

HL Hunt Pay provides payout reports with full transaction detail behind every deposit, fees itemized rather than netted, and chargebacks, refunds, and reserves reported as separate line items — so matching is mechanical and the effective rate is visible without reconstructing it from a statement.

Get Started with HL Hunt Pay

Frequently asked questions

Why doesn't my payment deposit match my sales total?

Batch cutoffs, netted refunds and chargebacks, fees, and reserves all sit between them — and a deposit covers a batch rather than a calendar day. Match at the payout level and account for each deduction separately.

What is the difference between gross and net settlement?

Net deducts fees before depositing; gross deposits the full amount and bills fees separately. Gross is substantially easier to reconcile and makes your cost of acceptance visible — ask whether it's available.

How do I record chargebacks in my accounting?

As separate components — the sale reversal, the chargeback fee, and any later credit if you win. Netting them destroys both your true dispute cost and your win rate.

How often should a merchant reconcile payments?

Payout level as deposits arrive; statement level monthly with an effective rate calculation. The two catch different problems — missing money and wrong pricing.

Key takeaways

  • Deposits never equal daily sales — batch cutoffs, netted refunds and chargebacks, fees, and reserves all sit in between.
  • Gross settlement makes reconciliation and fee analysis far easier than net; ask whether your provider offers it.
  • Reconcile at three levels: payout to deposit, transaction to record, and statement to agreement.
  • Record revenue gross, use a clearing account, and treat reserves as an asset rather than an expense.
  • Track the effective rate monthly — it's how downgrades, new fees, and rate changes become visible.
  • Never write off small persistent differences; they're usually systematic, and the pattern is the finding.

Know what you're actually paying

Sign up for HL Hunt Pay for cards, ACH, and wallets through one integration — with itemized statements, per-rail reporting, and cost analytics that make the effective rate a number you watch rather than one you reconstruct.

Sign Up for HL Hunt Pay


This guide is educational and does not constitute accounting or tax advice. Settlement models, fee structures, and reporting formats vary by provider; consult a qualified accountant regarding treatment for your business.