The overdue balance report
Every week someone runs a report of direct bookings with balances due. They email each guest a reminder with bank details or a payment link, note who has paid, and chase again a few days later. Some guests pay by bank transfer with a reference nobody can match. One pays twice. Another has not paid and arrives next week.
Security deposits are handled separately, and refunds after checkout are remembered by whoever notices.
Why payment chasing stays manual
Many property management systems can take payments, but agencies often end up with a mix: some bookings on card, some by bank transfer, some with deposits held and some without. The payment terms vary with how far ahead the booking was made. So the team falls back to a report and a set of email templates.
Bank transfers are the hardest part, because they need matching to bookings, and guests do not always use the reference provided.
What manual chasing costs
Staff time is the most obvious cost. Late balances mean uncertainty for owners and for your cash flow. Guests who arrive with a balance still due create awkward conversations. Unmatched transfers sit unallocated. And security deposit refunds that are slow or forgotten generate complaints and poor reviews.
The payment schedule we build
We build a payment layer for direct bookings that follows your booking terms. The terms themselves are yours.
- Schedule per booking: when a direct booking is made, a schedule is created from your terms, for example a deposit now, the balance a set number of weeks before arrival, and a security deposit or card hold before check-in.
- Reminders with card links: guests receive reminders with a secure Stripe payment link before each due date, and a follow-up if payment does not arrive.
- Bank transfer matching: incoming transfers are matched to bookings by reference, amount and guest name, with uncertain matches left for a person to confirm.
- Booking updates: payments are recorded against the booking in your property management system, and arrival instructions are only released once the balance is paid.
- Exceptions list: your team sees overdue balances and unmatched payments in one list, with the booking and history attached, and decides what action your terms allow.
- Deposit release: after checkout, security deposits or holds are released automatically unless a damage report has been raised against the booking.
| Payment | When | How it is handled |
|---|---|---|
| Booking deposit | At booking | Card payment on the booking page |
| Balance | Before arrival, per your terms | Reminder with card link, bank transfer matched |
| Security deposit or hold | Before arrival | Card hold or payment, per your terms |
| Deposit release | After checkout | Automatic unless a damage report exists |
After the change
Most balances are paid on time without anyone chasing. Your team deals with a short list of real exceptions. Arrival instructions are only sent when payment is complete. Security deposits are released promptly, and held back only when there is an actual damage report.
Owners benefit as well. Because payments are recorded against bookings as they arrive, owner statements and forecasts reflect money actually received, and the question of whether a guest has paid for next week can be answered from the booking rather than from a colleague's inbox.
Repeat guests notice the difference too. A clear schedule, a working card link and a prompt deposit refund are small things, but they are part of why people book direct with you again rather than going back to a channel.
Signs you need this
- Balance reminders are sent by hand from a weekly report.
- Bank transfers from guests are hard to match to bookings.
- Guests have arrived with balances outstanding.
- Security deposit refunds are late or forgotten.
- Payment terms vary and are applied from memory.