If you spend more than ninety seconds setting up a fee cycle, you are doing it wrong. Feezy's fee-cycle builder is opinionated — it asks you four questions, infers the rest from your existing batch structure, and generates the entire month of links in one shot.
The four questions
Which batch is this for? Which fee head (tuition, hostel, transport, exam)? How often does it recur — monthly, quarterly, or one-time? And what is the due day each cycle? That's it. No fiddly per-student configuration, no separate template for every variant.
Behind the scenes, Feezy materialises one invoice per active student in the batch on the due day, applies your discount and fine rules, and queues the reminder cadence. You see a dashboard. The parent sees a payment link.
Walkthrough: tuition + hostel for Class 11
Open Fees → New Cycle → pick the Class 11 batch. Add the Tuition head at INR 8,500 monthly, due on the 5th. Add Hostel at INR 12,000 quarterly, due on the 10th of cycle month one. Save. Done.
Feezy now generates 76 invoices on the 5th and 76 invoices on the 10th, sends the soft reminder three days before, the firm reminder on the due day, and the recovery reminder three days after. You will only get a notification if a parent has not paid by the 14th.
What this replaces
It replaces the Wednesday-evening spreadsheet ritual. It replaces the WhatsApp template you copy-paste 76 times. It replaces the moment where you ask your assistant 'did Aarav's parent pay?' and the answer is 'I think so?'. Predictable cycles are not a feature — they are the product.
