It is 10.55pm. The kitchen shows four deliveries, but the card terminal shows only two payments. That can be right. Check the room charges before calling it a shortfall. Start with the order list, then match each completed order to the record for how it was settled.

On this page

Start with the orders that reached a guest

Put the order list, card receipts and the relevant room-account postings side by side. Use the same shift window in all three. Find the hotel’s business date in the property system if the shift runs past midnight. A posting can sit under Friday’s business date even when a wall clock says Saturday.

Match by ticket or reference where available. If all you have is an amount, two burgers at the same price can look like a match. Check the time and the order detail in the hotel system before ticking either one off. Put an order still in the kitchen queue on the handover list, outside the delivered total.

Work one shift on paper first

The figures below are a worked example in pounds. A partial refund has a separate reference. Keep it with the original settlement so the next person can explain the net amount.

Worked example for a single shift
TicketOrder or adjustmentExpected netMatched net
104Delivered, paid by card£24.50£24.50
105Delivered, charged to room£18.00£18.00
106Delivered, room posting missing£16.00£0.00
107Cancelled before preparation£0.00£0.00
108£30.00 card payment, £8.00 refund£22.00£22.00
TotalExcludes open kitchen tickets£80.50£64.50

Ticket 106 accounts for the £16.00 difference. Ask the person authorised to check the room account whether it was posted late. Reposting before that check can double-charge the guest.

Write the handover someone can act on

Record the ticket reference, expected amount, evidence already checked and who will take the next action. Use the approved hotel system for any guest or room identifiers. “106, £16 room charge, delivered at 22.41, no matching posting visible, night manager to check” gives the next shift a place to start.

If your team only has time to fix one thing before tomorrow’s service, make sure reception can find the kitchen ticket number. It saves a round of guessing when two payments are for the same amount.

Take a snapshot at a named time

Pick the time the team will use and note the hotel business date beside it. Export or record the same shift from the kitchen and from the payment or property system. Compare like with like. A report covering the whole restaurant day is too broad if your list is room service from the evening shift. If you have to filter one report, write down how you filtered it.

Keep the authorised operator involved when a receipt looks wrong. Use references from the systems rather than copying card or guest details into a shared sheet. If a charge appears after the snapshot, mark when it posted and update the exception list. Someone looking at the same report later should be able to tell why their total differs from yours.

Start with one row per order

An order may have several dishes, a service charge or a later adjustment. Keep one order row for the comparison and attach the related entries underneath or by reference. Match the total the guest was expected to settle. Before treating a difference as missing money, ask whether a discount, complimentary item or charge reversal was recorded on one side only.

If a booking changed rooms, search the order reference before deciding where the charge belongs. A named guest or room number can have changed between order and posting. Where a payment covers more than one order, attach the authorised payment reference to both and write which amounts it covers. Do not force a one-to-one match against the payment report.

Keep open tickets and refunds visible

Open kitchen tickets need an owner even though they sit outside the delivered total. Record their latest status and ask the outgoing kitchen station what will happen next. A pending order can still be prepared on the next shift, cancelled after the guest calls, or moved to the following business date. Each outcome needs a later check rather than a forced entry at close.

For refunds, check that the approved adjustment and original payment are both present. A cancellation before cooking may never have entered the payment flow. A refund after delivery should match the operator’s entry and the guest communication. Oracle’s transaction documentation separates voids, returns and check operations. Use the corresponding actions and references in your own payment system.

Source Oracle Simphony transaction functions for voids, returns and payments

Give the morning shift a short list of exceptions

When the totals differ, give the next team a reference and a check to run. “Review all receipts” sends someone back through the entire shift. “Compare ticket 106 with the room posting list after the nightly close” is specific enough for another person to complete. Separate cases to research from cases that already have an authorised correction pending.

For the first few closes with a new system, ask the morning shift to record what solved each discrepancy. Look for the same mismatch coming back more than once. It might be a payment terminal reporting a different business date, a desk posting that arrives late, or a missing reference. Fixing the reporting expectation once is faster than asking each new receptionist to learn it by trial and error.

Check the interval between posting and close

If the kitchen stops at 22:30 but the desk runs its reports at 22:20, write down who will check the last ten minutes. The same goes for a terminal close that runs before room charges are posted. Give those entries a later check of their own. Moving the cutoff to make an individual discrepancy disappear means the next person loses the reference point.

Ask the morning worker to confirm which exceptions were checked after the business date rolled over. Record the answer against the original ticket even when the correction appears on another report. This keeps the evening total understandable.

Source Oracle Hospitality on the business date and end-of-day reconciliation