Fee structures
Define yuran templates, transport, meals, and one-off activities — then apply per student before you hit Issue.
This is the finance and admin layer — school invoicing, aging, and audit-friendly totals in the owner cockpit. Parents pay on SchoolDesk’s FPX Telegram rail; your team owns the invoice lifecycle.
Before anyone calls a parent, your admin sees outstanding RM, overdue families, and which invoices cleared overnight — filtered by campus or year.
Malaysian schools invoice by term, class, and sibling rules — then chase the same families every month. SchoolDesk mirrors that rhythm instead of forcing a one-size subscription model.
Define yuran templates, transport, meals, and one-off activities — then apply per student before you hit Issue.
Paid, pending, and overdue roll up by class so follow-up lists don’t live in three WhatsApp chats.
Every FPX or manual payment links back to the invoice row parents saw in Telegram — ready for board or audit questions.
Four steps from fee run to reconciled totals — separate from how parents tap Pay via FPX.
Pick class or campus, apply fee structures, and generate itemised school invoices in one batch.
Linked Telegram threads show amount due and line items — no separate portal password.
Aging KPIs and invoice pills update as FPX payments land or staff record manual receipts.
Match payouts and receipts to invoices, then export totals for finance sign-off.
Honest answers before you reach out.
No. This page is admin invoicing and aging. Parents use the FPX Telegram Mini App to pay — both sides share the same invoice records.
Yes. Adjustments apply per student before you issue a run, so published invoices already reflect your policy.
Most schools stop maintaining parallel aging sheets. Export when auditors ask; daily follow-up stays in the cockpit.
Invoicing connects to parent chat, FPX checkout, and the owner cockpit.
Share a few details about fee runs, aging KPIs, or FPX handoff — our team will follow up to discuss.
Learn more