From Fee Registers to a Daily Dues List: Tuition Class Fee Collection

This is an illustrative case study. It describes a typical tuition centre we model during onboarding and shows how tuition class fee collection can move from paper registers to a simple daily routine. The numbers are representative examples, not results from a specific customer.

The institute

Picture a Class 8–12 tuition centre in a tier-2 city in Madhya Pradesh. It has around 180 students across CBSE and state board batches, three classrooms, five teachers and one front-desk person who also handles fees. The owner teaches maths for Class 11–12 and runs the business in the gaps between classes.

Fees are charged per academic year, per subject group. For example, a Class 10 maths + science student pays a net fee of ₹24,000 for the year, and a Class 12 PCM student pays ₹48,000.

The challenge

Fees were tracked in two registers and on the owner's phone. Parents paid in cash at the counter or by UPI to the owner's number. The problems were familiar:

• No due dates. Parents were told "pay in parts", so nobody knew exactly what was late.
• UPI payments were missed. Screenshots arrived on WhatsApp but were not always written into the register.
• Discounts were verbal. A sibling or "known family" discount was agreed at admission and forgotten by the time the next payment came.
• Month-end panic. Once a month the owner spent an evening adding up the registers, and the total never matched the bank and cash in hand.

The real cost was not only unpaid fees. It was awkward calls with parents who said they had already paid, and the owner's time spent checking instead of teaching.

What they set up in Klass360

The centre kept the setup deliberately small. In this example, it took about three working days, with the front-desk person doing most of the entry.

1. Courses with standard fees. Each subject group for each class became a course with its standard annual fee and subjects. The front desk stopped quoting different numbers to different parents.
2. Batches. Each course got its batches with days, timings, a batch-leader teacher and the number of seats, so the owner could see which batches still had room.
3. Students and admissions. All 180 current students were added with parent details and linked to their course and batch. The course fee flowed into each student's fee record.
4. Discounts recorded properly. Every existing discount was entered on the total fee with its reason — sibling, early payment or owner's discretion — so the net fee was visible for each student.
5. Dated installments. Year-long courses were split into installments with due dates — for example, ₹8,000 at admission, then ₹8,000 on 10 August and ₹8,000 on 10 November for a ₹24,000 net fee. For existing students, only the remaining balance was split.
6. Payments with receipts. Every payment, cash or UPI, was recorded against an installment with the mode, a UPI reference where relevant, and a numbered receipt.

The rule they followed throughout: for every student, Paid + Pending must equal the Net Fee. If those did not match for a student, the record was checked that day.

How the day changed

The biggest change was a short routine at 3:30 pm, before the evening batches began. The front-desk person opened the fee views and went through three lists:

• Due today — installments falling due that day.
• Overdue — anything past its due date, oldest first.
• Due this week — parents to remind politely in advance.

Reminders were still sent by hand on WhatsApp, but now they were specific: the student's name, the installment, the exact amount and the due date. The centre used a few fixed message formats so that every parent got the same polite tone. When a parent paid by UPI, the payment was entered straight away and the receipt was shared back on the same chat.

The owner stopped asking the front desk "how much is pending?" and looked at the dashboard instead: collections this month, pending and overdue, in one place.

Results in this example

Because this is a modelled scenario, these are the kinds of outcomes the setup is designed to produce rather than measured figures:

• Every payment has a receipt. Disputes about "I already paid" become a quick lookup instead of an argument.
• Overdue fees are visible early. A parent who is ten days late is called in week two, not discovered at month-end.
• Discounts stop leaking. Each discount has a reason, so the owner can see the total given in a month.
• Month-end takes minutes. Collections in the system can be matched against cash and bank statements quickly, because every payment carries its mode and reference.

In this example the centre does not collect more by pressuring parents. It collects more reliably because every rupee has a due date and every payment is recorded on the day it arrives.

Lessons any institute can use

You can apply most of this with or without software:

1. Fix the net fee at admission, with any discount and its reason written down.
2. Give every installment a date, not just an amount. "Pay in parts" cannot be tracked.
3. Record UPI payments the moment they arrive and share a receipt back.
4. Check dues daily at a fixed time, not monthly.
5. Remind early and specifically. Our free fee reminder generator and fee reminder message templates give you ready wording.

For a deeper walkthrough of the same principles, read our guide to fee tracking, installments, discounts and refunds. If you run a similar centre and want to see installments, receipts and the daily dues list working with your own batches, you can explore Klass360 fees and refunds or start a free 7-day trial.