How to Reconcile Split Payments on a Standalone Card Terminal: Match Each Share, Payment Status and Balance

For split payments on a standalone card terminal, match each share to a clear amount, the actual transaction status and a system record, then check what remains due. First, clarify the full bill and how it will be shared. Complete one share before moving on to the next; even if everyone has used their card, you still need to reconcile each transaction at the end.

Confirm what is due without going over every bill-splitting step again

Check the table, items ordered, additions, amounts already paid and current discounts, and agree with the guests on how shared dishes will be split. The split methods available in MenuSnap—equally, by item or by amount—must be selected from the options supported by the current bill. Resolve any disagreements first, then check that the shares add up to the amount due. Do not promise that every possible combination can be handled automatically.

Keep a matching record for every payment

• Original bill and current share identifier: ____; amount due and payment method: ____; staff member handling this payment: ____.
• Amount entered on the terminal: ____; transaction time and any necessary reference: ____; confirmed by the terminal / still being checked: ____.
• Corresponding payment record in the system: ____; original bill and amount checked: ____.
• Cash received and change given, if applicable: ____; payment for this share verified: ____.
• Balance currently due for the full bill: ____; explanation of any discrepancy: ____; next step and person responsible: ____.

This manual checklist is only for matching bill shares and transactions. Do not use it to store full card numbers, security codes, passwords or customer information unrelated to the payment. Card transactions are confirmed by the terminal and payment provider. Verify that a payment succeeded before recording it against the correct share. MenuSnap does not automatically verify this external transaction, and you should not assume the terminal will automatically receive the amount.

Choose the next step based on the discrepancy

• The terminal shows a successful payment, but there is no system record: First check the original bill, transaction time and latest payment status. If you confirm the payment was not recorded, add it to the corresponding share; do not charge the card again.
• The terminal status is unclear: Check the original transaction using the provider’s process and leave it marked as pending investigation. Neither a bill still showing an amount due in the system nor a notification on the customer’s phone is, by itself, a reason to charge the card again.
• The system shows an amount, but it does not match the terminal evidence: Pause further payments and check whether the wrong share was selected, the amount was entered incorrectly or the payment method was recorded incorrectly. Do not simply erase the discrepancy.
• Items are added or a discount is changed after payment: Check what the current bill allows, and clarify with the guests who will pay for the additions. Do not continue collecting payment based on the original paper bill or assume that the paid shares will be recalculated automatically.

Keep cash, rounding differences and tips separate

Record cash received and change given; do not rely on someone saying “it’s paid.” If an equal split leaves a small rounding difference, check the actual amount assigned to each share and the total, then explain it to the guests. Do not have everyone estimate their own card payment and casually write off the difference at the end.

If a guest pays extra, first confirm whether it is a tip or payment toward the remaining balance. Record it using a method the restaurant actually supports; do not automatically treat it as a tip or quietly let the next guest pay less to offset it. If another staff member helps, clarify whether they are responsible for explaining the payment or organizing the records. Do not let two people collect payment for the same share at the same time.

Close out network issues, refunds and shift handovers separately

If the server connection is interrupted, keep the necessary manual evidence. Once the connection is restored, check the latest payment records before recording any confirmed payments. Payments, refunds, settlements and shift processing in MenuSnap require server confirmation. A standalone terminal follows its own connectivity requirements, so do not promise that the entire process will work offline.

A staff member with the appropriate authority must check the original payment and process any refund through the relevant payment method. Changing the split, printing a bill or recording an external refund in the system will not automatically refund a standalone terminal transaction. The result must also be confirmed by the terminal or payment provider, and someone must follow up on any unresolved issue.

Before closing out the table, check the balance and any unresolved issues. At shift handover, review discrepancies transaction by transaction before checking the total. Payments received through the payment provider may involve subsequent settlement or fees; the net amount deposited in the bank is not a substitute for reconciling that shift’s transactions. Record whether a discrepancy came from shared dishes that were not clearly split, an amount change, an input error or a successful payment that was not recorded. Next time, correct the relevant step rather than trying to speed up the rotation of card payments.