Fee week, before the ledger was one place
Walk into most school offices during fee collection and you will see the same choreography. The accounts desk has a register open to today's counter receipts. A staff member is scrolling through a bank statement on a phone, trying to match UPI references to student names someone shouted across the room. Parents at the gate are asking whether yesterday's payment counted, because the WhatsApp screenshot they sent never got a reply.
None of this happens because schools are careless. It happens because fee work was never designed as one system. Fee heads live in one file, concessions in someone's notebook, online transfers in email, and reminders in a chat group that half the office muted months ago. By the time the principal asks for a dues summary, someone spends an afternoon rebuilding numbers that should already exist.
KIDUART was built around a simple idea: the fee book is not a report you generate at the end of the month. It is the operational centre of school finance structures, allocations, collections, dues, and receipts all reading from the same record.
What "UPI-ready" actually means for a school
Parents in India already pay with UPI more often than they carry cash to the counter. "UPI-ready" is not a sticker on a brochure. It means three things work together without manual reconciliation:
- Parents see exact dues tied to the fee book, not a PDF someone edited last week
- Online payment through Razorpay or Stripe posts back to the student's fee record automatically
- The office issues a receipt from the same ledger, whether payment came at the counter or on a phone
KIDUART connects to your Razorpay merchant account. Settlement goes to your bank under your agreement. We do not pool parent payments through our account. That matters for audits, for trust with families, and for the accountant who already knows your gateway dashboard.
When a parent pays online, Razorpay confirms through a signed webhook. KIDUART writes the payment against that student's fee record and assigns a receipt number. The accountant is not matching bank entries to screenshots the next morning.
Building the fee book first
Schools that get clean fee weeks usually set structure before they chase collections. KIDUART follows the same order as the rest of the product:
Fee heads and categories
Tuition, transport, activity, hostel, exam every charge your school recognises should exist as a defined head before you allocate it to a class or student. Ad-hoc line items in spreadsheets are where "why is this student's total different?" arguments start.
Structures and templates
Most schools repeat the same fee pattern each year with small changes. Reusable templates let you define a structure once and apply it to a session or class group, then adjust concessions at student level where policy allows.
Allocation at class and student level
A fee book that only works at school level forces manual splitting when sections have different transport routes or optional subjects. Allocation at class and student level keeps dues honest when two students in the same grade pay different amounts for legitimate reasons.
Concessions on the record
Scholarships and staff discounts belong in the system, not in a parallel list only the principal remembers. When concessions sit on the student record, reports and parent portals show the same number the accounts team sees.
Counter collection and online collection, one ledger
Many Indian schools will always take cash and cheque at the window. That is fine. KIDUART treats counter collection and online collection as two doors into the same room.
When fees are collected at the counter, staff record payment in the finance panel, print or share a receipt, and the student's balance updates immediately. When fees are collected online, the gateway posts the payment and the receipt follows the same numbering logic.
The dues list who owes what, as of today is one list. Reminders, parent portal views, and principal dashboards read from it. You are not maintaining "the online list" and "the offline list" and hoping they match before the board meeting.
How parents pay from the parent panel
The parent panel is deliberately narrow: guardians see their own children, not the whole school. For fees, that means:
- Open dues with due dates that match the school calendar
- Pay through Razorpay checkout (UPI, cards, net banking, wallets as your gateway supports)
- Download or view receipts after payment
- See history without calling the office for "what is my balance?"
We are honest about limits. PayPal is on the roadmap, not shipped today. Schools that need a specific regional gateway should ask during evaluation we list live connectors on the integrations page rather than implying everything is connected.
Reminders that respect real due dates
Generic calendar reminders annoy parents ("fee due soon") when the school's actual due date is two weeks away. KIDUART ties reminders to dues in the fee book. Finance teams configure channels the school already uses SMS, email, WhatsApp where connected and the message reflects real balances.
Reminders reduce phone tag; they do not replace conversations about hardship or disputes. Those still belong with a person. The win is fewer calls asking for a number that should already be visible.
Receipts, refunds, and audit questions
Receipts are not cosmetic. They are how schools answer "did we receive this payment?" months later.
Every collection counter or online generates a receipt tied to the fee entry. Refunds are recorded in the same module so the ledger stays coherent. When a parent disputes an amount, finance staff are not reconstructing history from three sources.
Sensitive financial actions sit behind role permissions. An accountant sees the fee book; a class teacher does not. Audit logging covers authentication and financial events so "who changed this entry?" has an answer when it matters.
Expenses and reporting without a second project
Fee collection is half of school finance visibility. The other half is knowing what was collected against what was expected, campus by campus if you run more than one.
KIDUART includes expense tracking and finance reporting that read the same fee book not a export-and-pivot-table exercise every time leadership asks for collections last week. Organisations running multiple campuses can roll up reports without merging databases by hand.
A realistic first term with online fees
Schools that move to UPI-ready collection in one dramatic week often stumble. A calmer path looks like this:
- Week 1–2: Define fee heads, structures, and allocations for the current session
- Week 3–4: Run counter collection in KIDUART while keeping your old register beside it
- Week 5–6: Connect Razorpay, test with a small parent group, verify webhooks and receipts
- Week 7 onward: Open online pay to all families; keep counter open for those who prefer it
Parallel running for a few weeks beats a launch day where every balance is questioned at once.
What changes for office staff
Teams that complete this journey describe the same shifts:
- Fee week feels quieter because balances are not debated across WhatsApp
- Online payments appear on the student record the same day, not after someone checks the bank
- Principals open a dashboard instead of waiting for a compiled sheet
- Parents stop treating the office as a balance enquiry desk
None of that removes the need for sound fee policy or compassionate handling of genuine difficulty. Software applies rules consistently; people still set the rules.
Honest boundaries
KIDUART is strong at fee book operations, Razorpay and Stripe online collection, receipts, dues, reminders, and parent portal pay. We do not claim every accounting package integrates live finance data exports for your accountant in standard formats. We do not claim certifications we have not completed; security controls like role permissions, tenant isolation, and audit logs are described on our security page for IT reviewers.
Questions to ask on a fee demo
Before you sign, sit the accounts team in front of a live fee workflow not a slide of payment logos:
- Show fee head creation and class allocation on screen
- Collect a test Razorpay payment and watch it post to the student record
- Print or download the receipt from the same ledger
- Show the parent portal dues view for that student
- Show what the principal sees without opening the finance panel
If any step requires export to Excel, note where manual work remains.
After go-live: first fee cycle review
Hold a thirty-minute retrospective after the first full fee instalment on KIDUART: count manual corrections, parent disputes, and unmatched online payments. Those three numbers tell you whether the ledger is trusted yet better to extend parallel running than declare victory early.
Closing: one ledger parents and auditors can trust
If fee week still feels like a storm in your school, the fix is usually structural: one ledger, one dues list, one path for UPI to land on the right student. That is the problem KIDUART set out to solve.
