Cash close in an aesthetic center: the method to balance every day
Balancing the till isn't counting notes at closing time: it's a method that separates what you've collected from what you've delivered, payment method by payment method, until the gap with the system is zero. If your center closes "by eye" and carries discrepancies no one can explain, you don't have an honesty problem: you have a process problem. Here's the daily method, step by step, so the till balances every day and you know why when it doesn't.
The problem: the till that "almost" balances
At closing, the till is short. It's not a crisis: someone tops up the difference, notes "discrepancy" and heads home. The next day there's a surplus. And so, month after month, the center lives with small differences no one investigates because they're small. The problem isn't one day's difference: it's that no one knows where it comes from, and what can't be explained can't be fixed.
An aesthetic center takes payment in many ways at once —cash, card, transfer, packages, deposits— and delivers services paid for today but consumed three months from now. With that mix, balancing "by eye" is impossible: either you have a method that separates each item, or the discrepancy becomes background noise that hides what actually matters. The cash close isn't counting money; it's reconciling two versions of reality —the drawer's and the system's— until they match.
The small thing that hides the big one
A discrepancy of a few euros that repeats every day stops being an anecdote: it becomes the curtain that hides a process error, a package deducted wrong, or a payment that never came in. If you always balance by "topping up the difference", you'll never know what causes it.
Step 1: the blind count, before you look at the system
The first mistake in a close is looking first at what the system says should be in the till. The moment you see that figure, your mind counts toward it. So the method starts backwards: count the physical money first, without knowing how much "should" be there, and only then compare it with the system. It's called a blind count, and it's the only way to make the recount independent.
The count is always done the same way, in the same order, so it can be repeated and compared across days and across people. It isn't bureaucracy: it's what turns the close into reliable data instead of an impression.
- Set aside the fixed float —the change you open with each day— before counting anything else: that money isn't the day's sales.
- Count the cash by denomination, notes and coins, and record the total without looking yet at the system's figure.
- Gather the card terminal receipts and add up their total separately from cash.
- Collect the proof of transfers and deposits that came in that day.
- Only then open the system and compare: counted cash against expected cash, and each payment method against its total.
Step 2: balance each payment method separately
A discrepancy is almost never "in the till" in general: it's in a specific payment method. So you don't balance one single total, you balance several. Cash is compared with the count; card, with the terminal total; transfers, with the confirmed entries at the bank. When each channel balances on its own, a discrepancy stops being a mystery and gets a surname: "short on card", "over on cash".
The most common confusion is mixing channels: taking cash for something recorded as card, or the reverse. Added together, the till "balances" even though each method is wrong, and the error only surfaces when the bank doesn't match what was recorded. Separating the methods from minute one avoids that mirage. All this reconciliation is far faster when the payment, the ticket and the payment method live in the same system as your package billing, with nothing exported to a separate spreadsheet.
Packages consumed vs packages collected: the discrepancy no one sees
Here's the part a generic cash close ignores and that, in aesthetics, changes everything. When a client buys a multi-session package, money comes in today, but the service is delivered over weeks or months. That day you've collected the whole package, but you haven't consumed it. If your close treats that payment as the day's sales, your till looks richer than it is and your real activity is inflated.
So you have to separate two things that are constantly confused: the collected —the money that comes in when the package is sold— and the consumed —the value of the service delivered each time the client comes to spend a session—. The day you sell a package you collect a lot and consume little; the day that client comes to use it, you collect nothing but consume service. A well-run close records both sides, because the difference between them is money you already hold but still owe in the form of sessions.
Collected isn't the same as earned
Package money comes in today, but it's a promise of service settled over time. If your close doesn't tell collected from consumed, you confuse cash with result: you spend as profit money you actually owe in sessions.
The typical discrepancies and their real cause
Almost every discrepancy in a center repeats and has a specific cause. Identifying it is half the work, because a named discrepancy is fixed by changing a process step, not by watching people. These are the most frequent:
- Over on cash, short on card: a card payment was logged as cash, or the reverse. Cause: recording the payment method from memory at the end, not at the moment of payment.
- A constant small shortfall: wrong change or rounding. Cause: front-desk rush and no fixed, counted float.
- A package that throws off activity: the client used a package session but it wasn't deducted from the balance. Cause: the consumption wasn't recorded on the profile, so the service looks given away.
- Deposits that appear and vanish: an advance payment taken one day and applied another with no clear trail. Cause: not separating the collected deposit from the consumed service.
- The discrepancy you only see at the bank: cash and terminal balance, but the bank entry doesn't match. Cause: transfers recorded as collected before being confirmed.
Who signs the close and what happens to the data
A close with no owner is a close no one reviews. The method comes full circle when a specific person validates the count, notes the incidents and signs off the day's result. Not to point fingers, but so there's a clear chain: who counted, who balanced and who signed the day off. With per-person permissions, each person does only what's theirs to do, and the close stays tied to whoever signed it.
And the close doesn't end in the drawer: it ends in data. When each day is recorded —collected, consumed, discrepancies and their cause—, you stop having impressions and start having a series you can read in your analytics. That's where a recurring discrepancy stops being bad luck and shows up for what it is: a process step to fix. If you want the full operational method, the Total Operational Control resource works it through step by step.
Illustrative center (example figures, not measured)
Picture a center that leaves a small unexplained discrepancy every day and, on top of that, sells four packages a week it treats as pure sales. Within a few months, its till looks healthy while it piles up a pool of sessions already collected but not delivered, and no one knows how much of what came in is service still owed. The concrete figures depend on each center; what doesn't change is the mechanism. (Illustrative scenario to explain the effect, not a measured average.)
What if your center stopped having invisible leaks?
We show you Qleven working on your center's real operations. No commitment, in 15 minutes.
See Qleven in your center · 15-min demoFrequently asked questions
How often should I do the cash close?
Why count the till before looking at what the system says?
How do packages affect the cash close?
A small but constant discrepancy — is it serious?
Keep digging deeper
The Qleven features that solve what you just read about.
