Two children sit in the same class. One owes a registration fee this year and one does not. Which is which depends on the year each of them joined the school, not on the class they are sitting in.
That is a real rule, from a real school of roughly 1,400 students in Punjab. It is also the rule that several school management systems could not bill.
Why it defeats a fee module
Most school software models fees as a list of heads with a frequency against each one. Tuition, monthly. Transport, monthly. Registration, one-time. The frequency options are almost always the same six: monthly, quarterly, half-yearly, yearly, term and one-time.
A fee that repeats every second year is not on that list. Worse, it is not even a property of the fee. It is a property of the student, because the two-year count starts from the date that particular child was admitted. Two children in Class VI can be on opposite halves of the cycle.
So the vendor has two answers, and both are bad. The first is to add an “every second year” option, which still bills the whole school in the same year and gets half the students wrong. The second is to tell the office to mark the affected children by hand, every year, forever.
What actually solves it
The school did not need a product that had already thought of their situation. They needed one that could be told about it.
EduBold has no “every two years” setting either. What it has is a rule that can read the student’s own record, including the date they were admitted, and decide from that what to charge. The condition is written once. It then applies itself to every child, in every class, for every year, without anybody marking anything by hand.
That distinction matters more than any feature list. A feature list tells you what somebody has already imagined. A rule engine tells you what you can still describe after you have bought it.
The part worth copying
If you are evaluating school software and your fee structure has awkward corners, do not ask whether the product supports your rule. Ask the vendor to show you your own students billed correctly, on a sample of your own data, before you decide anything.
That school’s principal sent a sample of his data. About ten rules covered 95% of what he needed, and he saw it working on his own students before he paid anything. He bought EduBold afterwards, once he had seen it, and his office has used it every working day since early 2026.
The rule that had defeated several other systems turned out to be one line in a list of ten.