To explain the gap between card sales and a bank deposit, start with the processor’s settlement report, not just the POS sales total. Match the batch or deposit ID, transaction dates, gross card payments, refunds, processing fees and other adjustments to the bank deposit. Then check whether any sales settled in a different batch.
A shift close checks what the restaurant recorded and how guests paid. Deposit reconciliation follows those card transactions through the processor to the bank. Both checks matter, but a balanced shift does not by itself prove that a deposit is complete.
Start with dates and identifiers
Gather three records for the period you are checking: the POS card payment report, the processor’s batch or settlement report, and the bank statement or deposit activity. If refunds and disputes appear in separate processor reports, gather those too.
Use the deposit as your starting point. Find its date and amount in the bank account, then locate the processor payout with the same amount or a matching payout reference. From that payout, identify the batches and transactions it includes. A single deposit may cover more than one batch, and a batch may not arrive in the bank on the same day the restaurant made the sales.
Ask your POS and payment provider which fields connect these records. Useful fields include:
- Transaction date and time: When the payment was recorded, along with the report’s time zone.
- Transaction or payment ID: A reference for matching an individual payment across reports.
- Batch ID: The group of transactions submitted or settled together.
- Settlement or payout ID: The processor reference connecting a settlement to a deposit.
- Bank deposit date and amount: The money actually credited to the account.
Also ask when the processor closes a batch and whether its reporting day matches the POS business day. A restaurant that closes after midnight can record a sale in one business day while the processor places it in another calendar day. Weekend and holiday processing schedules can also affect when money arrives.
If the POS report shows a different time zone from the processor report, note the conversion before calling a payment missing. Do not rely on a guest name or ticket amount alone to identify a transaction: two parties can pay the same amount on the same night. For sensitive card data, use the limited identifiers shown in your reports rather than copying full card numbers into a worksheet.
When evaluating a restaurant POS, ask to see sample reports for a sale, a refund and a payout. Can you follow each item by ID, and can you export the fields needed for your bookkeeper? Ask which processor provides the settlement report; the POS and processor reports may be separate.
Separate sales, deductions and timing differences
Gross card payments are the starting amount before the deductions shown on a settlement. They are not necessarily the amount deposited. Read the processor report’s definitions carefully: a POS sales figure may include items that are presented separately in a payment report. Check how each report treats tips, voids, refunds and payment adjustments before comparing totals.
Common explanations for a difference include:
- Refunds: Money returned to guests may reduce a settlement. A refund can relate to a sale from an earlier day, so match it by transaction reference rather than assuming it belongs to the same day’s sales.
- Processing fees: Some reports show fees deducted before payout; others may show them separately. Use the actual fee lines rather than applying an assumed percentage.
- Disputes or other adjustments: A processor may show a separate debit or credit. Identify the reason and reference before accepting it as part of the difference.
- Timing: A payment recorded by the POS may belong to a later batch. It is not a fee or a lost sale merely because it is absent from today’s deposit.
A deposit is cash received from the processor. Sales are what the restaurant recorded; fees are charges for processing. Do not treat those three figures as interchangeable. A quoted processing fee also is not the restaurant’s all-in operating cost: software, hardware and other costs may be billed separately. The guide to POS costs and reports can help frame those separate questions.
Before doing the math, confirm whether each line is already included in another total. For example, subtracting a refund from gross payments makes sense only if that gross figure has not already been reduced by the refund. The same check prevents counting a fee twice.
Work through a sample deposit
The following figures are hypothetical. Assume the POS recorded $1,120.00 in card payments for a business day. The processor report places $1,000.00 in the payout being checked and $120.00 in a later batch. The $120.00 is a timing difference, not a deduction from this payout.
The table reconciles only the $1,000.00 included in the first payout. It includes a refund, processing fees and a separate adjustment shown on that payout. The processing fees shown are variable charges; no fixed charge is included in the payout. The adjustment is an exception cost. Other operating costs billed outside the payout are excluded.
| Settlement line | Amount | Effect on payout |
|---|---|---|
| Gross card payments in this payout | $1,000.00 | Starting amount |
| Refund | -$42.35 | Deducted |
| Processing fees | -$26.15 | Deducted |
| Separate adjustment | -$5.00 | Deducted |
| Expected bank deposit | $926.50 | Net payout |
The calculation is $1,000.00 − $42.35 − $26.15 − $5.00 = $926.50. If the bank shows a $926.50 deposit with the matching payout reference, that payout balances to the cent. The $120.00 still needs to be matched to its later settlement and deposit; it has not been proven received by balancing the first payout.
This example also shows why comparing the full $1,120.00 POS total directly with the $926.50 deposit would be misleading. The $193.50 difference consists of $120.00 assigned to a later batch and $73.50 in deductions from the first payout. Verify the reason for the $5.00 adjustment in the processor detail rather than leaving it as an unexplained plug.
If the bank instead showed $921.50, the payout would be short by $5.00 against the report’s expected amount. Check for a separate bank entry, an omitted processor line or a reference mismatch. Do not change the worksheet to force a match.
Assign and investigate unmatched items
Give one person responsibility for maintaining the reconciliation, even if a manager, bookkeeper and payment provider each handle different parts. A practical routine is to review new deposits regularly, log exceptions and return to open items until they are resolved.
For each exception, record the amount, business date, transaction or payout ID, the report where it appears, the expected deposit, and the next action. Keep the supporting reports with the worksheet using your restaurant’s normal access controls. A short status such as “awaiting next payout” or “processor investigating” is more useful than an unexplained difference carried forward.
For a delayed settlement, the assigned person should check the next processor payout and bank deposit first. If the transaction still cannot be found, send the processor the relevant IDs, dates and amounts and ask for the settlement status. Record the response and a follow-up date. A provider can explain its payout schedule and the specific transaction; a restaurant should not assume every delay follows the same schedule.
For duplicate-looking records, compare transaction IDs, batch IDs, timestamps and statuses. A payment, a later adjustment and a refund may appear on separate lines without being duplicate charges. Conversely, two lines with similar amounts deserve review if their identifiers suggest two distinct transactions. Ask the provider to explain any status you cannot interpret before removing a line from the worksheet.
For an unfamiliar fee or adjustment, request the itemized processor explanation and compare it with the written payment quote. If a contract term or its legal or tax treatment is unclear, ask the appropriate qualified adviser. The operational goal is to know what was deducted, where it appears and who is following up.
Keep reconciliation separate from the restaurant’s cash and tender close, but connect the records where useful. A manager can confirm the POS business-day total, while the person handling deposits follows the payout through to the bank. Restaurant management software may be part of the reporting workflow; ask which exports and settlement details are available for your setup.
Next step: Choose one recent payout and list the fields your team needs to trace it from POS payment to bank deposit. Request a Fleksa demo and bring those requirements and a sale, refund and delayed-settlement scenario. Ask to walk through the reports using simulated records, without charging a real card or contacting a guest.
Frequently asked questions
Why is my deposit lower than my card sales?
Refunds, processing fees or other adjustments may reduce a payout, and some payments may settle later. Match the processor’s payout detail to the bank deposit before deciding which explanation applies.
Should every day’s card sales equal that day’s deposit?
Not necessarily. POS business-day boundaries, batch cutoffs and bank deposit timing can differ. Follow each batch or payout to the deposit that includes it.
What should I do if a payout does not balance?
Recheck dates, IDs and whether deductions were counted once. Log the remaining difference, assign an owner and ask the processor to trace the relevant payout or transactions.
