Concern
Reconciliation by hand
Reconciliation at the end of the day is work the software should never have created. On one system, the booking, the order, and the payout always match.
The cost
The day ends with a spreadsheet and a discrepancy.
When payments live in one tool and bookings in another, someone matches them by hand each day, hunting the difference that separate systems leave behind — time after service, on figures that should already agree.
How the system addresses it
Figures that match because they never split.
One system
Bookings, orders, and payments on the same system.
Tied transactions
Each payment linked to its order and booking.
Deposits accounted
Holds and deposits reconciled with the bill.
One payout
All transactions settle into a single, reconciled payout.
No exports
Nothing to download and match by hand.
A read, not a rebuild
The end of the day is a check, not a recount.
The fastest reconciliation is the one that was never needed. Everything lined up before the service ended.
Questions
Reconciliation by hand, answered.
Why do restaurants reconcile bookings and payments by hand?
Restaurants reconcile by hand when bookings, orders, and payments live in separate tools that have to be matched at the end of the day. Inservo holds them in one place, so each payment is already tied to its order and booking, and the close is a read of the record rather than a daily match.
Does one ledger remove the nightly close?
It removes the matching. Because the figures were never separated, the close is a check of the record rather than a recount of it.
Are deposits and refunds included automatically?
Yes. Deposits, refunds, and adjustments sit on the same record as the bill, so the payout reflects the service without a separate calculation.
Let the system reconcile itself.
A short walkthrough of one system from the booking to the payout.