Restaurant sales can differ from money deposited in the same period because an order, its payment settlement, and the bank deposit can happen on different dates. Refunds and processing fees can also reduce a payout without changing the original gross sales figure. A useful report should let you trace those differences instead of treating every gap as missing money.
Start by matching the same transactions, not just the same calendar dates. Then check which amounts are still pending, which were deducted, and whether the deposits actually reached the bank.
Map the order, settlement, and deposit dates
An order date tells you when a sale was recorded. A settlement date is when a payment is processed into a settlement batch. A deposit date is when money reaches the bank. Those dates answer different questions, so a Monday-through-Sunday sales report will not necessarily match deposits received during that week.
Before comparing totals, ask each provider which date controls its report. A report labeled “sales this week” might group by order date, while a payout report groups by settlement or deposit date. Also check the cutoff time and time zone. An order near closing could fall into a different reporting day from the one your staff expects.
Hypothetical worksheet: A restaurant records $1,000 in gross card sales from Monday through Sunday. All the related refunds and fees are included in the batches below. Cash sales, tips, taxes, delivery charges, and any other adjustments are excluded. The example assumes two settlement batches and no prior-period transactions in either batch.
| Batch | Gross card sales | Refunds and fees | Net deposit and date |
|---|---|---|---|
| A | $620 | $10 refunds + $10 fees | $600, Sunday |
| B | $380 | $30 refunds + $20 fees | $330, Tuesday |
| Total | $1,000 | $40 refunds + $30 fees | $930 |
The table tracks the same $1,000 of sales through two batches. If you compare that week’s sales with deposits received by Sunday, the bank shows only $600. The $400 gap consists of $330 deposited Tuesday, $40 in refunds, and $30 in fees. It is not a $400 loss or proof that $400 is missing.
The expected result is that the two deposits add up to $930 and the deductions explain the remaining $70. If Tuesday passes without the $330 deposit, the timing explanation is no longer enough: check the payout status and bank activity before closing the difference.
In a real review, record the order period, each batch’s settlement date, expected deposit date, and actual bank posting date. If a batch contains sales from more than one period, split it by transaction detail rather than assigning the entire payout to the week when it arrived.
Reconcile gross sales, refunds, and fees
Gross sales are not the same measure as the amount deposited. In the worksheet, the gross figure is $1,000 before refunds and fees. Subtract $40 in refunds to get $960 after refunds; subtract $30 in processing fees to get the $930 expected net deposit. The $40 is money returned to customers, while the $30 is a payment cost. Neither is itself a deposit.
Use the same approach with your own reports, but first establish whether each figure is gross or net. If the sales report already subtracts refunds, subtracting them again will create a false gap. Likewise, a fee shown on a separate invoice should not also be deducted from a payout unless the payout detail shows that it was withheld there.
Look for the actual fee presentation as well as the economic cost. One provider may deduct fees from each payout; another may deposit a larger amount and collect fees separately. The bank deposit alone does not show which arrangement costs less. Compare the documented charges for the same period and payment activity.
Other components may need their own rows. Tips, taxes, cash, gift cards, delivery charges, discounts, chargebacks, and third-party payments can be treated differently across reports. Ask what each total includes before adding or subtracting anything. A cash sale, for example, should not be expected in a card payout; if cash is later banked, trace it as a separate deposit.
For each reconciliation, keep these definitions next to the numbers:
- Sales scope: channels, payment methods, dates, and whether the total is before or after discounts and refunds.
- Payout scope: the transactions and adjustments included in each batch.
- Bank scope: the account and posting dates being reviewed.
- Excluded items: amounts tracked separately, such as cash or tips, and where they will be checked.
A restaurant POS system can be part of this workflow, but the buying question is whether its reports give your team enough detail to match the records you actually receive. Ask a qualified adviser about the appropriate accounting or tax treatment for your circumstances.
Separate pending settlement from a real exception
A pending payment is not the same as a missing deposit. It may have a documented payout date that falls outside your sales period. An exception is an amount that remains unexplained after you check the transaction, settlement status, deductions, and bank record.
Use a short exception log instead of repeatedly adjusting a spreadsheet total. Give each item an identifier, an amount, a status, an expected date, and an owner. Note what evidence would close it: a bank posting, a refund record, a fee line, or an explanation from the payment provider.
For the hypothetical $330 batch, mark it pending through its expected Tuesday deposit date. On Tuesday, compare the batch identifier and net amount with the bank entry. A $330 posting closes that timing item. A $300 posting leaves a $30 exception unless a documented adjustment explains it. Do not assume the difference is another processing fee merely because the amounts happen to match.
Set observable pass or fail criteria before reviewing a reporting workflow:
- Pass: The report identifies the period and date basis, and its transaction detail can be matched to the payout batches.
- Pass: Refunds and fees are visible as separate amounts, and the expected net payout can be calculated without counting either twice.
- Pass: Pending amounts have a status and expected date, and an actual deposit can be checked against the bank.
- Fail: A total changes without an identifiable transaction or adjustment explaining the change.
- Fail: The team cannot tell whether an unmatched amount is pending, deducted, deposited elsewhere, or genuinely unresolved.
These criteria apply to the combined records you use, not necessarily to a single screen. A bank statement may provide the posting confirmation while a payment report provides batch detail. If the records cannot be matched, assign the question to the right provider and keep it open until the explanation is documented.
Review exceptions at a consistent cadence that fits your deposit schedule. Avoid declaring an amount missing just because it has not arrived within the sales-report period. Equally, do not leave an item marked pending indefinitely after its expected date has passed.
Ask vendors for definitions and usable detail
During a buying discussion, ask the vendor to walk through a sample report using fictional or simulated records. A practice review should not create a real payment, guest message, or courier dispatch. If you later run a live service pilot, agree on its scope separately and use your normal controls for real transactions.
Give the vendor a scenario like the worksheet above and ask staff to trace it from sales total to expected deposit. The vendor does not have to use the same screen for every step, but each handoff should be clear. Ask to see how an unresolved difference is recorded and how someone can return to it later.
Bring these questions to the demonstration:
- Which date does each report use: order, settlement, or deposit? Can we see the cutoff time and time zone?
- Are refunds, fees, tips, taxes, and other adjustments shown separately? Is each sales figure gross or net?
- Can we see transaction and batch identifiers, payment method, status, and expected payout date?
- What detail can we export, in which format, and for what date range? Can we match it to the payment provider’s records?
- How are partial refunds, mixed-period batches, and later adjustments displayed?
- Which records come from the restaurant software, the payment provider, or a separate accounting tool? Who helps investigate a mismatch?
Ask to see the exact configuration you would buy. A summary dashboard may be useful for a quick sales check, while reconciliation may require transaction detail from another system. Fleksa’s partner portal shows sales and order summaries for a selected period, along with order-status views; available views and configurations vary. Confirm whether the detail and exports your process needs are available for your setup.
If information must move between systems, review the available integrations and ask what data each connection actually transfers. Do not assume a connection carries payout identifiers or accounting detail just because it carries orders. The guide to one platform or separate tools can help you decide where separate records may still be needed.
For a cost comparison, get a written quote for the configuration and services you need. Check Fleksa’s current plans and pricing; the published pricing details were checked in November 2026. Compare any software charges alongside separately quoted payment and other service costs, rather than judging the workflow by a deposit amount alone.
Next step: Take one recent sales period and its corresponding payout and bank records, then apply the worksheet and pass/fail checks. Compare your requirements with Fleksa’s restaurant management software and confirm current availability before choosing a workflow.
Frequently asked questions
Should weekly sales equal weekly bank deposits?
Not necessarily. The reports may use different dates, and deposits can reflect refunds, fees, and batches containing transactions from other periods. Match the underlying transactions before comparing totals.
Does a smaller deposit mean money is missing?
No. First check pending settlement, documented deductions, and the expected deposit date. Treat the remaining unexplained amount as an exception and follow it until the records agree.
What should I ask for in a reconciliation report?
Ask for clear date and gross-versus-net definitions, transaction and batch identifiers, separate adjustments, payout status, and exportable detail. Confirm which information must come from the payment provider or bank.
