School Fee Payment Reminder Web App for Parents with Receipt Download

This project builds a School Fee Payment Reminder Web App for Parents with Receipt Download, a web app that tracks fee dues child by child, reminds parents before each due date, and issues a downloadable receipt for every payment. Parents currently juggle fee circulars, diary notes and bank messages, and a missed due date surfaces as a late fee or a call from the school office. This app replaces that scattered tracking with one parent dashboard: each child gets their own fee heads (tuition, transport, activity and exam fees), each with an amount and due date, and the reminder engine follows a fixed schedule so nothing depends on a parent remembering to check. When a payment is recorded, the ledger updates and a sequentially numbered receipt is generated for download. The build is web-only and database-backed, so the whole flow — dues, reminders, payments and receipts — can be demonstrated end to end on a laptop with school data.

The School Fee Payment Reminder Web App for Parents works as a simple closed loop: fee dues go in, reminders go out on schedule, payments come back into the ledger, and receipts come out for the parent to keep. A school-side entry creates fee heads for each child — tuition, transport, activity or exam fees — with an amount and a due date, and the parent dashboard immediately reflects what is due, what is due soon and what is overdue. Around each due date the reminder engine walks its fixed schedule, updating each fee head's status badge as reminders are sent, scheduled or become overdue. When a payment is recorded against a fee head, the ledger gains a row, the dashboard totals update, and a sequentially numbered receipt is generated for download. Nothing in the loop depends on a parent remembering a date: the schedule drives every nudge, and the receipt trail proves any payment later.

1. Fee heads are entered per child — tuition, transport, activity or exam fees — each with an amount in rupees and a due date.
2. The parent dashboard aggregates dues per child and overall, splitting them into due now, due in the next 7 days, overdue and already paid.
3. The reminder engine evaluates each unpaid fee head daily against its fixed schedule: 7 days before, 3 days before, on the due date, and 1 day after if still unpaid.
4. Each reminder updates the fee head's status badge (Scheduled, Sent or Overdue) with the date it was sent or is due to be sent.
5. The parent records a payment against a fee head, choosing the child, fee head, amount and payment mode (UPI, net banking or cash at the school office).
6. The payment lands in the record table immediately, the fee head flips to paid, and the dashboard totals recalculate.
7. A sequentially numbered receipt is generated for the payment and offered as a download the parent can keep for school records.

Tech stack:

• HTML5 · CSS3 · JavaScript (single-file demo)
• Node.js · Express (backend API, built-to-order build)
• SQLite (fee heads, reminders, payments, receipts)
• REST endpoints for dues, reminders and receipts
• Nodemailer (email reminder delivery, built-to-order build)
• LocalStorage demo state (browser demo only)
• Git

The School Fee Payment Reminder Web App for Parents gives a parent one dashboard for every child, with four capabilities doing the heavy lifting: a per-child fee-head ledger that shows what is due, what is overdue and what is already paid; a reminder schedule that messages the parent at fixed points around each due date rather than once and never again; a payment record table that keeps a complete, filterable history of every payment; and numbered receipt generation so each payment produces a downloadable receipt the parent can file. Around those four, the app adds child switching for multi-child families, reminder-status badges showing whether a reminder was sent, scheduled or overdue, and a demo data set modelled on a real school term. Every capability below is implemented in the demo build; items marked as future scope are not claimed as working features.

• [Per-child fee-head ledger] Each child has separate fee heads — tuition, transport, activity and exam fees — each with its own amount, due date and paid-or-due status, so one child's dues never blur into a sibling's.
• [Scheduled reminder engine] Reminders fire at 4 fixed points per fee head: 7 days before, 3 days before, on the due date, and 1 day after if still unpaid — then stop until the next fee head falls due, so parents are nudged without being spammed.
• [Reminder status badges] Every fee head shows Sent, Scheduled or Overdue status with the date, so a parent (and a viva examiner) can see exactly where each reminder stands.
• [Payment record table] A complete ledger of payments with date, child, fee head, mode and amount, filterable by child, with new payments added to the table immediately on recording.
• [Downloadable numbered receipts] Every recorded payment generates a sequentially numbered receipt (never reused) that the parent can download and keep for school records.
• [Multi-child parent view] One parent account covers all their children in the school, with a child switcher that filters dues and payments to the selected child.
• [Working parent-dashboard demo] A real single-file web demo with a dashboard, receipt view and payment ledger, using realistic term data for 2 children and 4 fee heads.
• [Future scope: live payment gateway] Online payment collection through a gateway is documented as future scope only; the shipped build records payments and issues receipts rather than moving money.

• Working parent-dashboard web demo (dashboard, receipt view, payment record table)
• Built-to-order backend build: fee-head management, reminder schedule, payment ledger and receipt generation
• Demo data set for 2 children and 4 fee heads across one school term
• Project report PDF (problem, design, reminder-schedule rationale, data model, testing)
• PPT presentation for final review
• Viva Q&A preparation document (reminder scheduling, receipt numbering, data model, web architecture)