Payment Operations
Reconciling a Debit Terminal Batch at Opening
A debit terminal batch can settle at a different total than the POS reported the night before. The gap may come from a tip adjustment, a void that did not sync, a chargeback, or a terminal that dropped offline mid-shift. Reconciling at opening gives the store a clean starting point before the first sale. Waiting until month-end turns a small, explainable difference into a stack of unresolved tickets.
Pull the batch before the first sale
Print or export the terminal batch report before opening the register. Capture the batch number, the settlement date, the gross amount, the refund amount, and the net deposit. Do the same for the POS payment summary for the same business day. Keep both reports together so the comparison uses the same time window.
Check that the terminal and the POS are set to the same business-day cutoff. A terminal that closes at midnight and a POS that closes at 2 a.m. will disagree for reasons that have nothing to do with missing money. Record the cutoff times in the opening checklist. If the cutoffs differ, reconcile to the terminal batch first and then map the POS totals to it.
Match settlement to the POS summary
Start with the net deposit rather than the gross sales. Tips, refunds, and chargebacks change the amount that actually reaches the bank. Match the batch total to the POS debit total, then match the individual transactions that make up the difference. Do not assume the larger number is the correct one.
Use the transaction identifiers to pair terminal records with POS tickets. A ticket that appears in the POS but not the terminal may have been voided after authorization. A terminal record with no POS ticket may be a duplicate swipe or a manual entry. List both exceptions separately so the cause is visible.
Limit terminal access to the opening lead and one backup. A shared login makes it impossible to tell who ran a batch or voided a ticket, and the reconciliation note loses its owner. If the processor supports individual accounts, use them even when the store is small. Review the access list when a shift lead changes roles, and remove old accounts the same week. A named owner makes the next question easier to answer.
Classify the variance before adjusting anything
Group differences into timing, authorization, and settlement categories. A timing difference clears on its own once the batch posts. An authorization difference may need a void or a reversal. A settlement difference may involve a chargeback or a terminal fee that the store did not expect. The category tells the reviewer who should act.
Record the amount, the transaction reference, and the category on one reconciliation sheet. Do not net a refund against a sale in the same line, because the two have different evidence. If the terminal report does not show enough detail, request the merchant portal export before guessing. The cash pickup routine uses the same one-line-per-event discipline for a different payment type.
Handle chargebacks and fees separately
A chargeback is not a terminal error. It is a customer dispute that follows its own timeline and needs its own file. Record the date the chargeback appeared, the amount, the reason code, and the response deadline. Do not mark the batch reconciled while an open chargeback is unresolved.
Terminal fees and monthly adjustments should be recorded against the merchant statement, not against the daily sales total. If a fee appears in the batch, note the line and compare it with the contract or the prior month. A fee that changes without explanation deserves a call to the processor. Keep the explanation in the reconciliation file so the next reviewer does not repeat the inquiry.
Write a closing note that survives a shift change
End the reconciliation with a short note: matched amount, open items, owner, and next check date. Attach the terminal batch, the POS summary, and any merchant portal export to the same case. If the difference is unresolved, mark the batch as open rather than complete. A second person should be able to read the note and know exactly what to do next.
Do not correct the POS total to match the bank before the cause is known. A forced match hides the evidence and may create a second error. If a correction is required, record the before and after values and the approver. The PCI Security Standards Council publishes payment-security guidance that is useful when the store reviews terminal access and retention. Keep card data out of the reconciliation file.
Review the pattern every week
Count variances by terminal, shift, and category. A terminal that repeatedly produces timing differences may need a software update or a network check. A shift that repeatedly produces authorization differences may need a refresher on void procedures. Share the pattern with the manager who owns the payment process, not only with the opening staff.
Choose one fix and compare the next two weeks. Do not change the terminal, the POS cutoff, and the reconciliation sheet at the same time. Keep the weekly review short and focused on one category. The settlement batch review method describes how to measure the pattern across a longer period. A clean opening reconciliation is a record of what happened, not a promise that no difference will ever appear.