Frequently asked questions
The questions the registry, the bursar's office and IT ask about student records, fees and campus payments, before a proposal.
Records and fees
What does one student record change?
Admissions, billing, the parent portal and the bursar's ledger read the same record rather than each keeping their own. A returning or transferring student is found rather than created again, so fees stop sitting against a record nobody is looking at. A family sees one figure for what it owes.
How are instalments and late fees handled?
Tuition, deposits and recurring charges are billed against the student record, and instalment plans, due dates and late-fee rules are applied by the system rather than tracked by hand. Reminders go out on a schedule, so officers work the exceptions instead of chasing every balance.
Payments and the close
Can parents pay fees from home?
Yes. The parent portal shows statements, outstanding balances and instalment schedules, and a parent can settle a fee at eleven at night without calling the office in the morning. Every payment posts to the same ledger the bursar reads.
How do payments at the canteen and bookstore work?
The canteen, the bookstore and the service counters accept DuitNow QR, cards and the major Malaysian e-wallets, with stored-value accounts where the campus runs them. Parents top up from home, and the takings reconcile into the same finance records as fees.
What changes at semester close?
Fees, campus takings and settlement are reconciled daily against what was billed, so closing the term is reading a report rather than a fortnight of matching. Departments, campuses and cost centres are visible separately without separate books, and management sees enrolment, fee collection and arrears during the term rather than after it closes.
Rollout and the agreement
How is it rolled out without disrupting intake?
It goes live on one programme, one campus or one intake first, before the whole administration commits to it. Migration happens between intakes, not during one, with cutover dates chosen against the institution's own calendar. Admissions and fee collection continue throughout, and the previous path stays available until the new one is trusted.
Where does it run, and can our other systems talk to it?
In the institution's own cloud account or data centre. idataraya installs it, hardens it and keeps it current, and the institution's team holds the keys, the backups and the data. Learning management and academic systems stay where they are, and idataraya integrates asasii campus with what the institution already runs. A documented API lets other systems or a third party read student records, fees and payments and post what they need to.
What does the yearly agreement cover?
Software updates, the customisations made for you, monitoring, severity-based response and restoration targets, and the changes needed as programmes and fee structures change. Hosting stays with you. It is a fee, not a subscription.
Still have a question?
Send it with the institution and the number of students, and an engineer replies within one working day.