Booking operations
Two calendars every booking business needs
An appointment and its payment can belong to different days. A guest might reserve a visit weeks ahead, pay a deposit now, move the appointment later, and settle the balance on arrival. Treating those events as one date makes both the front desk and the accounts harder to understand.
Start the working day with scheduled arrivals
The operational calendar should answer a practical question: who is expected at this location today? Build that view around the appointment’s current scheduled start, using the location’s local calendar day. A reservation made last month belongs on today’s arrival list if the appointment is today. A payment taken this morning for next month does not.
Give staff the details that change what they do next: local start time, service, duration, room or resource, party size, and current status. Keep sensitive contact information in the authorized booking view rather than copying it into a public display or a home-screen summary.
- Check the location and timezone before comparing dates.
- Use the current scheduled time after a reschedule.
- Make canceled and other terminal statuses explicit instead of leaving them among expected arrivals.
- Keep required-form status visible without assuming a booking means every participant has completed a form.
Reconcile money on the day it moves
The payment view answers a different question: what money moved during this reporting period? It should distinguish successful collections, pending attempts, deposits, later installments, and refunds. The appointment date is useful context, but it should not replace the payment event’s own timestamp.
A deposit is a part-payment against a booking, not a second booking sale. To follow the money, retain the booking reference, individual payment reference, amount, currency, status, and the quote or invoice it relates to. Searching by an exact amount can help locate a record, but an amount alone does not establish identity when several transactions match.
Use a simple example to catch the mix-up
Consider a fictional reservation made on Monday for a Saturday visit. A deposit is collected on Monday and the remaining balance on Saturday. Monday’s payment report contains the deposit; Saturday’s arrival list contains the appointment. Saturday’s payment report contains only the money collected that day.
If the visit moves to Sunday, the operational calendar should move with it. The original Monday payment remains a Monday event. A reschedule should not rewrite the date on which a historical payment happened. This separation keeps staffing decisions and reconciliation grounded in the right records.
Check boundaries before trusting a daily total
Daily reports need a defined timezone and a clear interval. Think in terms of the start of the local day up to, but not including, the next local day. Around daylight-saving changes, a calendar day is not always a fixed number of elapsed hours. For a multi-location operation, decide whether you are viewing each store’s local day or a deliberately chosen reporting timezone.
Test the view with an appointment purchased earlier but occurring today, a purchase today for a future appointment, and an appointment moved across midnight. Then compare a small sample with the underlying reservation and payment references. A clean dashboard is useful only when its labels explain which events it counts.
A short opening-shift check
Before the first arrival, confirm today’s location, scheduled appointments, capacity and required forms. Separately, review payments and unresolved attempts using their own event dates. When the two views disagree, trace the references before creating a replacement booking, collecting another payment, or resending a message.
The goal is a shared operating picture: staff know who is coming, and the payment history still tells the truth about when money moved.