In EDUBase, set your late fee policy, then turn on late fee automation and choose when it applies: on the due date, the day after, or after a grace period. Per-day fines accrue up to the policy limit, never land on a weekly off or holiday, and can be previewed first.
How does automatic late fee work in EDUBase?
Late fee automation is part of the Fee Automation module. It takes the late fee policy your school already uses and applies it on schedule, so the finance office no longer has to work out each fine by hand once the due date passes.
You decide when the fine starts: on the due date itself, the day after it, or after a grace period. If your policy charges per day, the fine keeps accruing each day until it reaches the policy limit, so a family who pays a week late is not charged the same as one who pays two months late, and nobody is charged beyond the cap.
Every automation in EDUBase ships switched off. Nothing is charged until someone with the right access turns it on.
What should be set up before switching it on?
Automatic fines depend on correct challan dates and a correct calendar. Check these first so the first run does exactly what your policy intends.
- Confirm your late fee policy: the amount, whether it is a one-time or per-day fine, and the maximum limit.
- Check that challans carry the right due date. If you use scheduled challan generation, the generation day, due date, expiry and campus and class scope are set once and reused every month.
- Enter the school's closed days in the Holiday Calendar and confirm your weekly off, because fines are moved off these days.
- Decide whether a grace period suits your families, for example a few working days after the due date.
- Agree internally who may switch automations on, using per-user and per-action privileges.
How do weekends and holidays affect the fine?
Fines never land on a weekly off or a Holiday Calendar date. If the day a fine would apply falls on one of those days, it moves to the next working day.
This matters for finance teams because parents commonly cannot reach a bank branch or the school counter on closed days. Keeping the Holiday Calendar up to date, including unplanned closures, keeps the fines fair and reduces disputes at the counter.
Can I check who will be fined before anything is charged?
Yes. Every automation has a preview that shows exactly which children would be affected and by how much, and the preview charges nothing. Use it before the first live run, and again whenever you change the policy, the grace period or the Holiday Calendar.
After each run, the run history logs what the automation did. If a month looks missed or charged twice, the log lets you trace it in seconds rather than going through challans one by one.
How does the fine fit with collection and reminders?
Unpaid balances roll into the next challan as arrears, and a month-wise breakdown of old dues can print on the voucher, so the family sees what they owe and why. Where bank fee collection is enabled, the voucher carries a consumer number that parents can pay at a branch, ATM, mobile app or through 1Bill/1LINK channels, and the payment posts in real time.
For one-off charges outside the policy, staff can still add a fine or extra charge to challans that already exist. Many schools pair late fees with automatic fee defaulter reminders, choosing the day, hour, channels (SMS, WhatsApp, branded SMS, app) and recipients, so families are reminded before fines grow.
Which reports show the effect of late fees?
Finance officers can follow the impact through the standard fee reports, all of which export to Excel or CSV.
- Fee defaulters by total amount, by family or by month, with print and SMS/WhatsApp actions.
- Detail Fee Report for charges and payments by student, particular and month.
- Day Wise Paid Challans for the daily cash-up by day and by user.
- Payment History for every payment a student or family has made.
Ways to charge late fee fines
| Approach | What it involves | Best suited to |
|---|---|---|
| Manual fine on existing challans | Staff add a fine or extra charge to challans already generated | One-off cases or exceptions outside the policy |
| Automatic on the due date | Policy fine applies as soon as the due date arrives | Schools with a strict, well-communicated deadline |
| Automatic the day after the due date | Families have the full due date to pay before any fine | Schools where parents commonly pay on the last day |
| Automatic after a grace period | Fine starts only after the agreed grace days | Schools wanting fewer disputes and softer enforcement |
| Per-day accruing fine | Fine grows daily until it reaches the policy limit | Schools that want the fine to reflect how late payment is |
Related modules
- Fee Automation — Let the system generate challans, apply late fees and chase defaulters on schedule.
- Fee Management & Challans — Fee plans, monthly challans, discounts, family payments and receipts, without spreadsheets.
- Fee Reports & Defaulters — Know what was billed, what was collected and who still owes, per class, family or month.
- School Setup & Multi-Campus — Campuses, classes, sections, sessions, academic year and reference lists, set once and reused everywhere.
- Bank Fee Collection — Parents pay at the bank, in their banking app or at a kiosk; EDUBase posts it automatically.
- SMS, WhatsApp & Notifications — Reach parents by SMS, WhatsApp, branded SMS or app notification, from every screen that matters.