WHAT THIS IS
An Islamic institution system is a web application that runs the administration of a sekolah agama, tahfiz centre, maahad, madrasah, or mosque office: monthly yuran billing, FPX payments, donation records, attendance, receipts, and reporting.
How DuaLab Builds Islamic Institution Systems
Most Islamic institutions need a web system before they need an app. Fees arrive late because collecting them means WhatsApp messages and manual bank transfers; donations go unrecorded; attendance lives in exercise books. A web system fixes the money and the records first: parents pay by FPX from any Malaysian bank, receipts generate themselves, and the office sees who has paid at a glance. No agency in the Islamic app space offers this category; DuaLab builds it because it runs one.
Deeper reading: App or Web System First: A Guide for Institutions.
What Decisions Come Before Any Code?
Three product decisions decide whether an institution system earns trust or becomes another spreadsheet with a login page.
The first is what money the system is allowed to collect. Monthly yuran, class fees, and pledges are the school’s own. Sadaqah, infaq, and wakaf are the mosque’s own to collect and record. Zakat administration in Malaysia sits with each state’s Majlis Agama Islam and its collection body, so a build calculates and routes zakat, or operates under a wakalah appointment; it does not invent a private zakat till. Scoping that line before quoting is how a Malaysian build differs from an offshore deck that copies a charity-app template.
The second is how payment is confirmed. Malaysian parents settle by FPX (and often DuitNow QR) through a licensed gateway. DuaLab’s own JomAlQuran system uses CHIP for FPX. The rule that keeps the books honest is simple: the system never trusts a callback’s claim that money arrived; it asks the gateway’s API to confirm before marking a bill paid. Amounts live as integer sen end to end so rounding cannot invent or erase a fee, and settlement is idempotent so the same confirmation twice cannot create two payments.
The third is who owns the repository. SaaS products such as ASIS (Awfatech) and specialised tahfiz platforms sell subscriptions with their modules and their login. That fits a school that wants modules on day one and will accept the vendor’s roadmap. A custom build fits when the school needs Malaysian payment rails wired its way, a hafazan or murajaah record the templates refuse, or a system it can hand to any local Laravel developer later. The app or web system first guide settles the app-vs-web order; the SaaS-vs-custom call is the next sentence in the same conversation.
What Does the Money Path Look Like?
On the 1st of each month the system raises that month’s bills. Each bill carries a payment link a parent can open from WhatsApp without installing anything. FPX takes them into their own bank’s app; when the gateway confirms, the bill flips to paid and a receipt is ready. The office dashboard is a paid/unpaid list, not a bank-statement archaeology session. The same path can take recurring infaq or wakaf pledges when the institution asks for them, with reporting that shows what came in and when.
What Else Belongs Beside Billing?
Student and parent accounts, attendance, and progress records (including hafazan and murajaah where the school teaches Quran) sit next to billing so a parent sees what is owed and what was taught in one place. Staff roles and a security audit trail keep office access accountable. Export exists because the school will need a CSV the day a board member asks for last term’s collection. Government reporting systems such as SIMPENI are a separate lane; a DuaLab build does not replace them, and it does not pretend to.
What a Build Includes
A islamic institution systems build from DuaLab covers the features listed below:
- Monthly yuran billing raised automatically, paid by FPX
- Gateway-verified payments (callback never trusted alone; amounts in integer sen)
- Payment links parents open from WhatsApp, no app install
- Receipts and payment history for every parent
- Attendance and student progress records (including hafazan / murajaah when taught)
- Donation, infaq, and wakaf records with reporting
- Staff roles, security audit trail, and CSV export
- Repository in the institution’s name from day one (Laravel / Blade)
Why Trust DuaLab With This Category?
DuaLab built and uses this exact system: the JomAlQuran fee system bills monthly yuran through CHIP FPX with 161 automated tests on the payment paths. Read the case study.
What Does It Cost?
An institution web system is DuaLab’s RM 20,000 tier (6–8 weeks); agencies quote USD 8,000–15,000 where the category exists at all. Every quote is fixed and in writing, and the repository is yours from day one. Full tiers are on the pricing page.