Front-Desk Cash, Cards on Paper, and 'Who Changed This?'

An envelope, a notebook and a question

It is Friday afternoon at the front desk of a school-age program. A parent hands over a check. The staff member at the desk thanks them, writes the family name and the amount in a notebook, and slips the check into an envelope for the office. A few minutes later, a new family drops off their enrollment packet. On the third page, in pen, is a full card number, the expiration date and the code from the back of the card.

The next week, a parent asks why their balance went down. Someone looks it up. The balance did change. Nobody in the room knows who changed it, or why.

None of this is carelessness. Each one is a workaround that grew up around a gap in the software. Your staff are doing their best with the tools in front of them, and the tools left them holding money, card numbers and questions with nowhere to put any of it.

What you hear when you listen to a payment desk

When you listen to the people who run a payment desk, three worries come up, in different words, again and again.

• The money that is not in the system yet. Cash and checks are real payments, but until someone enters them, the family's account still shows a balance. A parent can get a bill for money they already handed over.
• The card number sitting in a drawer. A paper form with card details has to be stored, retyped and eventually destroyed. Every person who handles that form can read the number.
• The change nobody can explain. A balance moves, a credit appears, a charge disappears. If the software keeps no history, the only record is somebody's memory.

The payment side was part of the work we did with a YMCA school-age program we built alongside. You can read how we built it on our process page. Charging accounts, processing refunds and finding the cards that declined were all repetitive jobs the office did by hand. We listened to how the desk and the office really handled money before we built anything for it.

Underneath each symptom

Each of those worries is a symptom. The root causes underneath are plainer than they look.

Cash in an envelope. The symptom is a notebook at the front desk. The root cause is that the software has no place for a payment that did not come in on a card. So the desk keeps its own ledger, and the office matches the two up later, by hand, when it has time.

Cards on paper. The symptom is a card number written on a form. The root cause is that the program, not the parent, is the one entering the card. If the office has to type the number in, the number has to travel to the office somehow, and paper is how it travels.

Who changed this? The symptom is a balance nobody can explain. The root cause is that changes to an account are made without leaving a trail. The software keeps the new number and forgets how it got there.

A payment desk should never be the only place a payment exists.

A payment desk that echoes the family's account

The fixes follow the root causes, not the symptoms. Here is what we built for the program we worked alongside:

• Desk payments go on the family's account. Cash and checks taken at the front desk are recorded on the family's account, so the balance a parent sees reflects what they handed over. The notebook has nothing left to hold.
• Parents enter their own card. The parent enters the card themselves, online. It is never written on paper, and nobody at the office has to type it in.
• A history of who changed what. When a balance changes, there is a record of who changed it. The question at the top of this post becomes a question with an answer.
• Declined cards in one place. Someone in the office starts one run that bills the whole week, and declined cards are listed together in one place, so following up is one list instead of a search.
• Bills and receipts in English and Spanish, so the family reading the receipt can actually read it.

None of those are complicated ideas. They are what the front desk was already trying to do with an envelope, a notebook and a good memory. The software just does it in the same place as everything else.

Questions to bring to your own front desk

You can check your own program in an afternoon. Ask your front desk staff and your office:

• When a parent pays in cash or by check, how long until the family's account shows it? Where is it written down in the meantime?
• Is there any form in your files with a full card number on it? Who can open that drawer?
• Pick a balance that changed last month. Can you say who changed it, without asking around?
• On billing day, how does the office find out which cards declined? Is it one list, or a search?
• Does a family who reads in Spanish get a receipt they can read?

If any of those answers starts with well, usually, you have found a workaround. Write it down. It is a pain point, and it has a root cause.

Show us your front desk

We would like to hear how your day really runs at your YMCA, park district or rec center, especially at the payment desk: the envelope, the notebook, the forms in the drawer, the balance nobody can explain. Tell us, and we will show you what a payment desk sounds like when the software echoes the way your office already works.

Request a demo