Two correct numbers that disagree
Every restaurant manager runs into this eventually: the POS close-out report says one number, the bank deposit says a smaller one, and the gap between them looks like something went wrong. In the overwhelming majority of cases, nothing did — the two numbers were never measuring the same thing.
The ten reasons below cover almost every gap you'll actually run into. None of them is a math error. All of them are the ordinary mechanics of how a card payment moves from a customer's card to your bank account, several days and several deductions later.
1 · Processing fees deducted before the deposit
Every processor takes a cut before the deposit lands — typically a percentage of the batch plus a small per-transaction fee. On a $4,000 batch with a couple hundred transactions, that fee alone can easily account for $100 to $150 of the gap.
Look for: a deposit consistently 2 to 4 percent below the batch total, scaling roughly with transaction volume.
This is the single largest and most consistent contributor to the gap, and the first thing worth checking before looking anywhere else.
2 · The batch settles a day or more later
A batch closed Tuesday night rarely deposits Tuesday night. Most processors settle on a one- to three-business-day lag, which means comparing Tuesday's batch to Tuesday's bank activity will always look like a mismatch — because the relevant deposit hasn't landed yet.
Look for: a batch with no corresponding deposit on the same day, but a clear match two or three business days later.
This isn't a discrepancy — it's a timing difference that resolves itself once the settlement window has passed.
3 · Card tips ride the batch but pay out separately
A credit-card tip is captured at the point of sale and included in the batch total, but the actual cash that reaches a server's pocket typically comes from the till or a separate payout, not directly from the card deposit.
Look for: a tip total that appears in the batch report but doesn't correspond to any single line in the bank deposit.
That's expected — the tip amount is a component of the batch total, not a separate deposit of its own.
4 · A refund lands in a different batch than the original sale
A refund processed today for a purchase made last week reduces today's deposit, not last week's. Comparing this week's batch to this week's deposit without accounting for that refund makes the deposit look short by exactly the refunded amount.
Look for: a deposit that's short of the batch total by an amount matching a specific, identifiable refund from a prior period.
5 · A chargeback arrives weeks later
A customer disputing a charge with their card issuer can trigger a chargeback weeks after the original sale — long after the original batch has closed, been forgotten, and moved on to the next reconciliation cycle.
Look for: a deposit reduced by an amount tied to a transaction from a batch closed weeks or even a month earlier.
Chargebacks are the reason a reconciliation that only looks at the current week can miss something real — the cause sits in the past, not the present.
6 · Multiple batches combine into one deposit
Some processors bundle more than one day's batch into a single deposit, particularly around a weekend or a lighter processing day. A deposit that looks too large for a single day's batch is often exactly that — two or three days combined.
Look for: one deposit whose amount roughly equals the sum of two or three consecutive days' batches, not any single one.
7 · One batch splits across two deposits
The reverse pattern also happens: a single large batch settles across two separate deposits, sometimes a day apart, occasionally tied to a processor's own risk or volume thresholds on unusually large days.
Look for: two deposits that together, but not individually, add up close to a single day's batch total.
8 · Cash tips never touch the bank account
Cash left at the table goes straight into a server's pocket or the house till — it never appears in the POS batch, the processor statement, or the bank deposit. Any attempt to reconcile “total tips” using only those three sources will always come up short by the cash portion.
Look for: a tip figure that consistently undercounts what staff report actually receiving, by roughly the same amount each shift.
9 · A voided sale still shows in the POS total
A transaction rung up and then voided before it ever settles shouldn't contribute to either the batch or the deposit — but some POS reports include voided lines in a printed summary total even though they never actually processed.
Look for: a batch report total that's higher than what actually appears to have settled, by an amount matching one or more voided transactions.
10 · A holiday batch settles late
A batch closed the day before a bank holiday, or over a long weekend, often waits until the next business day to settle — sometimes combined with the following day's batch in the same deposit, compounding reasons six and two at once.
Look for: a batch closed right before a known bank holiday, with its deposit landing several days later than the usual pattern.
Why almost none of this is a mistake
It's worth saying plainly: the overwhelming majority of gaps described here don't come from anyone doing anything wrong. They come from a payment system with several moving, independent parts — a POS terminal, a card network, a processor, a bank — each operating on its own schedule and its own accounting logic.
A batch report reflects what a POS system saw. A deposit reflects what a processor actually paid out, after its own fees and adjustments. Those were never designed to be the same number — they're two different measurements of the same underlying activity, taken at different points in the process.
The pattern behind all ten
Looked at together, all ten reasons share a structure: something that happened at one point in time gets recorded, netted or deducted at a later point in time, by a different system than the one that originally recorded the sale.
None of the ten is a rounding error or an arithmetic mistake. They're timing differences and structural deductions that show up clearly the moment both sides are read and matched — and look like an unexplained mystery only when one side is compared to the other from memory instead.
What chasing the wrong number actually costs
None of these ten reasons sound expensive individually. A processing fee is a known, expected cost. A one-day settlement lag costs nothing but a little confusion. The real cost shows up downstream, when a tip pool, a cash-flow forecast, or a manager's report gets built from the wrong number and that error compounds every time the same unreconciled figure gets reused.
A tip pool built from the gross batch total instead of the confirmed card-tip figure distributes money that doesn't match what actually settled. A cash-flow forecast built from batch totals instead of expected deposits overstates what's actually coming in, by exactly the amount fees and timing lags account for.
The fix costs almost nothing once the habit exists: read both documents, match them, and use the reconciled figure — not the first number that happened to be on the screen.
There's a slower, less visible cost too. A staff member who notices, once or twice, that the tip pool doesn't quite match what they expected starts trusting the numbers a little less each time — not because anyone did anything wrong, but because nobody explained where the gap came from. That erosion of trust is harder to fix than the number itself.
Who inside the restaurant should be catching this
In most restaurants, nobody has this as an explicit job. A general manager closes out the shift and moves to the next fire. A bookkeeper sees the deposit weeks later, disconnected from the shift it came from. The gap between the two sits in nobody's specific lane — which is exactly why it goes unexplained more often than it should.
The ten-minute check described below doesn't need a dedicated controller to work. It needs to sit with whoever already has the batch report in hand at close-out, with these ten reasons as a concrete checklist rather than a vague instinct that something looks off.
What tends to make the difference isn't adding headcount, it's making the check specific enough that it doesn't depend on the reviewer remembering all ten reasons from memory. A short, named list, checked against a document that's already in front of someone, survives a busy Friday night in a way that a vague intention to “double-check the numbers” never does.
One gap, from flagged to explained
It's worth following one case through, because a concrete example makes more sense than a list of rules on their own.
A Friday batch closes at $3,840.20. The expected deposit doesn't appear on Monday as usual. A quick check confirms the batch did close and submit successfully — so the gap isn't reason two, a normal settlement lag, since that window has already passed.
The processor statement shows the answer: Friday's batch settled together with Saturday's in a single Tuesday deposit, because the bank was closed Monday for a holiday — reason ten and reason six at once. The full deposit, once matched against both days' batches combined, accounts for the total exactly.
What made this fast wasn't luck — it was checking the processor statement for a batch reference before assuming the deposit was simply missing.
A ten-minute check before you build the tip pool
Does the batch's deposit amount roughly equal the batch total minus a plausible processing fee?
Has enough time passed for the deposit to have actually settled?
Does the processor statement show any refund or chargeback tied to this period?
Could this deposit be combined with, or split from, an adjacent day's batch?
Is the card-tip figure being used for the tip pool the confirmed batch total, not a printed summary?
Five questions, ten minutes, applied before a tip pool gets distributed or a discrepancy gets escalated. It's far cheaper than unwinding a distribution built on the wrong number after the fact.
If the pool was already built from the wrong number
The first step is locating the actual reconciled figure — the confirmed card-tip total once fees, refunds and timing are accounted for — rather than guessing at a correction.
The second step is comparing that figure to what was actually distributed, and adjusting the next payout to correct the difference rather than trying to claw back an exact cent amount from a prior distribution, which rarely goes smoothly.
The third step, once resolved, is asking whether the same source — a printed batch summary instead of a reconciled figure — will cause the same problem next time, and fixing the process rather than just this one instance.
An eleventh reason, less common but worth knowing
Beyond the ten regular patterns, an eleventh shows up occasionally at restaurants that see international cards: a currency conversion applied by the processor when a foreign-issued card is charged in the restaurant's local currency, with a conversion spread deducted alongside the usual processing fee.
It's uncommon enough that most weekly reconciliations never encounter it, which is exactly why it's worth naming separately — a gap that doesn't match any of the ten regular patterns, at a location with meaningful tourist or international traffic, is worth checking against this eleventh one before assuming something is genuinely wrong.
How to actually ask your processor about a gap
A question like “my deposits seem low” gets a generic answer, usually a link to a fee schedule nobody has time to parse. A question like “batch reference 48291 on July 14th shows $2,940.15, the matching deposit on July 17th shows $2,847.20 — can you confirm the $92.95 breakdown” gets a specific, useful answer, often within one reply.
The difference is entirely in the specificity of the question, and the specificity is only possible once the batch and deposit have already been matched — which is the whole point of doing the reconciliation before, not after, reaching out to support.
It also matters who's asking. A question that comes with the batch reference, the expected amount and the actual amount already laid out reads as someone who's already done the work — which tends to get routed to a more knowledgeable support tier faster than a vague complaint does, simply because the support rep doesn't have to spend the first five minutes gathering information that was already provided.
When the same gap shows up week after week
A gap explained once by a processing fee is unremarkable. The same unexplained gap, at roughly the same size, showing up week after week, is a different situation — it usually means one of the ten reasons is present but not being accounted for consistently, rather than a new problem each time.
A recurring gap is worth tracing back to its source once, carefully, rather than re-investigating it fresh every single week. Once identified — a consistent fee rate that was never being subtracted, say — the explanation applies going forward without needing to be rediscovered each time.
A gap that recurs but changes size week to week is a different signal again — usually a variable cost, like a rate that scales with transaction mix, rather than the fixed cost a flat recurring gap usually points to.
Does this apply outside restaurants?
Every business that takes card payments through a POS system runs into some version of these ten reasons — a retail shop, a salon, a repair service. What's specific to restaurants is reason three: the tip pooling layer that sits on top of an already imperfect batch-to-deposit match, adding a second reconciliation on top of the first.
A business without tips only has to solve the batch-to-deposit half of this problem. A restaurant has to solve that half and then build a fair tip distribution on top of a figure that's only trustworthy once the first half is actually reconciled.
That second layer is why restaurants tend to feel this gap more acutely than other card-accepting businesses — the mismatch isn't just an accounting curiosity, it directly affects how much money lands in a specific server's pocket that week, which is exactly the kind of consequence that turns an abstract reconciliation exercise into something staff notice and ask about, often before anyone in the back office has even looked at the numbers themselves, which is exactly why a quiet timing gap can turn into a loud staff conversation faster than it really should, if nobody's checked the reason first.
What a new manager usually gets wrong first
A manager new to running close-outs almost always makes the same first mistake: treating the printed batch total as the final number for the night, because it's the number sitting right in front of them at 11pm, and nobody explained that a smaller number is coming three days later for entirely ordinary reasons.
The fix isn't a long training document — it's walking through one real batch and its eventual deposit together, once, so the gap between the two stops looking like a mystery and starts looking like the ordinary mechanics described in this article.
A second common mistake follows close behind the first: once a new manager learns the deposit is usually smaller, they start assuming every gap is the processing fee and stop checking for the other nine reasons entirely — which is how a genuine chargeback or a real discrepancy slips past unnoticed for weeks.
What actually makes this easier
None of these ten reasons require specialized software to understand — a batch report and a processor statement, read side by side, are enough to explain almost any gap. What's genuinely tedious is doing that side-by-side read consistently, week after week, across every batch a restaurant closes.
A document reader that pulls the relevant figures from both sides automatically — batch totals, fees, refunds, deposit amounts — removes exactly that tedium, leaving the actual judgment call, when there is one, to a person instead of a spreadsheet full of manually retyped numbers.
The full step-by-step routine, including how often to check and what to do with an unexplained gap once one turns up, is in how to reconcile tips and POS settlements — this article covers the why, that guide covers the how.
Either way, the goal is the same: a gap that's explained the first time it's noticed, not re-investigated from scratch every time it resurfaces, week after week, by whoever happens to be closing that night.
What this article isn't
This isn't accounting or tax advice, and it isn't a guarantee that every gap you encounter falls into one of these ten categories. It describes patterns that come up often, not an exhaustive list covering every processor's specific quirks.
A gap that doesn't match any of these ten explanations after a genuine check is worth raising with your processor directly — that's a real discrepancy, not a timing difference waiting to resolve itself.
The step-by-step routine to check this on a regular cadence, rather than only when something looks off, is in how to reconcile tips and POS settlements.