Most software comparisons written for Rajasthan schools are the same article with a city name swapped in. This one is not a comparison at all — it is a checklist for the person who will have to live with the decision.
The legal framework is identical in Jaipur, Jodhpur, Kota, Udaipur, Ajmer and Bikaner: the Rajasthan Schools (Regulation of Fee) Act, 2016 applies to private schools across the state, and schools affiliated to the Board of Secondary Education, Rajasthan work to the same board calendar. What differs between cities is scale, campus geography, medium mix and how many branches one trust is running. Buy against that, not against a brochure.
Start by writing down what actually breaks
Before looking at any product, write down the three things that go wrong every year. In most Rajasthan schools the list looks something like this:
- Fee follow-up is manual and reactive. Nobody knows on the 12th of the month who has not paid, who paid partially, and who was promised a waiver by someone who has since left.
- The same student exists in four places. Admission register, fee book, marks register and transport list disagree about the section, the phone number, or whether the student is still enrolled.
- Nothing survives a staff change. The accountant who knew which fee heads applied to which class leaves, and the knowledge leaves with them.
If a demo does not visibly fix at least two of those, it does not matter how many modules the vendor lists.
Questions that separate a real system from a reseller
Ask these in the first meeting. The answers are diagnostic.
- “Show me one student’s complete fee history, including a partly-paid installment and a reversed payment.” If the vendor can only show a summary screen, there is no ledger underneath.
- “Where does the late fee live?” It should be a separate, visible component on the row, waivable with a record of who waived it — not silently folded into the amount due.
- “If I give a sibling concession in September, what happens to the installments already raised?” The right answer is that existing unpaid installments are reduced in place with an audit record, and the change can be reversed. The wrong answer is “we edit the amount.”
- “How do payments reach my bank account?” Ask whether online payments settle into the school’s own merchant account or into the vendor’s, and who holds the gateway credentials.
- “What happens on 1 April when the academic year rolls over?” Ask to see last year’s data after the roll — it should still be readable and still attached to the correct academic year.
- “Who can see what?” Ask whether a class teacher can open another class’s attendance or marks. If the answer is “we tell them not to”, the check is not in the software.
Migration is where projects actually fail
Do not accept a migration promise in the abstract. Run this test instead: pick one class, hand over the real files, and ask the vendor to migrate it end to end — students, guardians, the fee plan and installment schedule, everything already paid this year, and the last term’s marks. Then reconcile the opening balances against your own books line by line.
Two details are worth insisting on:
- Historic paid amounts must import as paid, not as adjustments. If the migration writes off dues instead of recording receipts, your collection reports for the year are meaningless.
- Phone numbers must arrive in a canonical format. Guardian numbers stored inconsistently are the single most common reason parent messaging silently fails after go-live.
Costs that do not appear on the quote
Rajasthan schools are usually quoted a per-student or per-module price. The real total tends to include things nobody mentions:
- Per-message charges. SMS is priced per message and requires registered DLT templates; WhatsApp business-initiated messages are priced by Meta per conversation. Ask which channel each notification type uses, and who pays.
- Hardware. Biometric devices, RFID cards and cameras are often quoted separately, and sometimes only after the software contract is signed.
- Training and the second year. Ask what training is included, and what the renewal looks like once the introductory year ends.
- Exit. Ask, in writing, how you export your own data if you leave, and in what format.
Claims to reject on sight
Some numbers circulate through Indian school-software marketing without any source behind them. If a proposal contains any of the following, ask for the study — and treat the absence of one as an answer:
- A specific number of hours saved per week.
- A percentage improvement in fee collection, attendance or “parent satisfaction”.
- An encryption bit-length quoted as a feature. Encryption strength is not a differentiator between school systems, and a number in a brochure tells you nothing about how keys are managed.
- A customer count the vendor will not back with two reference calls to schools of your size in your state.
What EdunodeX is, in plain terms
EdunodeX is a cloud school system built around a single per-student fee ledger, with academics, attendance, transport, HR and communication attached to the same student record.
- Fees. Fee items, class-level plans, installment schedules, subscriptions for transport and hostel, grace-day and late-fee rules, concessions with a per-installment audit trail, waivers, write-offs, settlements and payment reversals. Amounts are stored as integers in paise, and receipt numbers come from a database sequence rather than an application counter.
- Collection. A collection screen that handles cash, UPI, bank transfer and cheque, with partial payments (if the school enables them) allocated oldest-due-first, and advance collection that spills into upcoming installments up to the student’s total pending.
- Online payments. Each school configures its own Razorpay or Cashfree account, so parent payments settle into the school’s own merchant account. Stored gateway secrets are encrypted, and each school’s webhook is verified with that school’s own secret. If a school has not configured a gateway, online payment is simply unavailable rather than falling back to someone else’s account.
- Communication. Official WhatsApp through Meta Cloud API or MSG91, template-only for business-initiated messages, with per-guardian opt-in recorded and STOP/START keywords honoured automatically.
- Academics. Exam terms, marks entry, CBSE/ICSE/State grading systems, report cards with scholastic and co-scholastic sections, question bank, curriculum and syllabus tracking, and a structured teaching diary.
- Roles. Admin, Accountant, Principal and Teacher as built-in roles, with custom roles and a permission matrix on top. Attendance access for teachers is scoped server-side to the classes assigned to them in the current academic year.
- Compliance. A rules-driven compliance engine with state-specific overrides, weekly re-evaluation, and a UDISE export.
What it does not do: it is not an accounting package replacement — it exports to Tally rather than pretending to be it — and it does not integrate with Shala Darpan, which is a government and government-aided school portal that private schools do not use.
Before you sign
Run a two-week pilot on one class with real data and one real fee cycle. Collect at least one payment through the system, send at least one parent message, and generate one report card. Then ask your accountant, one class teacher and one parent what they thought. That conversation is worth more than any feature matrix.
One last point on tax: fees for education up to higher secondary at a recognised institution are exempt from GST under Entry 66 of Notification 12/2017-Central Tax (Rate). And zero merchant discount rate on BHIM-UPI person-to-merchant payments is a universal rule that has applied since January 2020 — not a benefit any vendor is providing you.