Most of the money in a restaurant arrives at the wrong time. You buy the stock, you roster and pay the staff, you turn the lights on, and only then, at the end of the night, does the income come in. There is always a gap between spending and earning, and that gap is where cash flow gets tight and working capital gets eaten. Deposits, prepayments and tickets are the tools that flip part of that timing, bringing money in before the night rather than after. That is their real value, and it is bigger than the no-show protection they also provide.
This is about using them well. For how card payments work underneath all of this, start with card payments for independent venues.
The cash-flow problem nobody names
Run a venue for a while and you feel this without naming it. You are always funding the gap between paying for something and selling it. You pay the supplier for Friday's stock before Friday. You pay the team for the shift before the takings land. For a tight independent, that gap is a constant low-level squeeze, and it is the reason a profitable venue can still feel short of cash.
Anything that pulls income earlier in that cycle eases the squeeze directly. It is not extra money, it is the same money arriving sooner, and arriving sooner is worth a lot when you are floating the gap out of your own pocket. This is the lens to see deposits, prepayments and tickets through. They are not just no-show insurance. They are cash-flow timing tools.
Deposits: a little money, early, on the right bookings
A deposit brings in part of the money up front and secures the booking. As covered in the reservations side of this, the art is applying deposits with judgement, on the bookings that can hurt you rather than on everyone. From the cash-flow angle, the deposit on a large peak booking does double duty: it protects the valuable table and it puts some of that night's income in your account before the night. A modest amount, but on your biggest bookings, arriving early.
The point is not to deposit everything in pursuit of cash flow, which would cost you bookings. It is to recognise that the deposits you are already taking for no-show protection are also doing a quiet cash-flow job, and to value them for both.
Prepayments: all of the money, early, for the right experiences
A prepayment goes further: the guest pays in full ahead of time. This suits set experiences rather than ordinary à la carte service, a tasting menu, a chef's table, a set-price special night. For those, asking for full payment up front is normal and accepted, because the guest is buying a defined experience rather than an open-ended meal.
The cash-flow effect is strong, because all of the income arrives before you cater the night. You buy the ingredients for the tasting menu knowing it is already paid for. And the no-show rate on prepaid experiences is very low, because people who have paid in full turn up. You have funded the night and removed the risk in one move.
Tickets: turning events into funded, known quantities
If you run events at all, supper clubs, themed nights, guest chefs, seasonal specials, ticketing them rather than taking bookings is usually the better model, and for the same reasons amplified. A ticketed event is paid for in advance, which funds it before you spend a penny catering it, all but eliminates no-shows, and tells you exactly how many people are coming so you can buy and roster precisely rather than guess.
There is a knock-on benefit too. A ticketed event is a clean, low-risk way to try something new. Because it is funded up front and the numbers are known, you can run a one-off night with far less exposure than adding it to normal service and hoping people come. Tickets turn an event from a gamble into a known quantity.
Keep it in one system
The practical catch with all of this is reconciliation. Deposits, prepayments and ticket sales are money taken at different times, ahead of a service, and they have to be matched back to the right booking, the right night and ideally the right guest. Done across separate systems, a ticketing tool here, payments there, the diary somewhere else, that matching becomes manual work and a source of error.
When deposits, prepayments and ticketing run through the same system as your bookings and your till, the money taken in advance is already attached to the right booking and guest, and it reconciles itself against the night when it happens. The cash-flow benefit is real, but it is only clean if you are not creating an admin headache to get it.
Where Grace fits
In Grace, deposits, prepayments and ticketed events all run through the same platform as your reservations and your till, so money taken in advance is tied to the right booking and guest from the start and reconciles automatically when the night arrives. You can take a deposit on a large booking, prepay a set menu, or ticket a supper club, and it all lands in one place against one guest record, rather than in three separate tools you then have to match up. You can see the Reservations and Ticketing modules for how it works.
It is built this way because the cash-flow squeeze is one of the most real and least discussed pressures on an independent, and pulling income earlier without creating reconciliation chaos is a genuinely useful thing for software to do.
FAQ
How do prepayments help restaurant cash flow?
They bring revenue in before you have spent on the stock and staff for that service. For a venue where cash is tight in the gap between paying for things and selling them, shifting some income earlier eases the squeeze and reduces how much working capital you need to float. - q: "What is the difference between a deposit and a prepayment?" a: >- A deposit is a partial payment that secures a booking and protects against no-shows. A prepayment is paying for the experience in full ahead of time, common for events and set menus. Both bring money in early; a prepayment simply brings in all of it. - q: "Should I ticket events at my venue?" a: >- If you run events, supper clubs, tasting nights or special menus, ticketing them is often better than taking bookings, because guests pay up front. That funds the event before you cater it, all but eliminates no-shows, and tells you exactly how many are coming. - q: "Do deposits and prepayments reduce no-shows?" a: >- Strongly, yes. When a guest has money committed, they are far more likely to turn up or to cancel properly rather than simply not appear. Prepaid and ticketed events in particular tend to have very low no-show rates for this reason.