Feature
Budget and Finance
Collection is one side; expenses, payouts and profitability are the other.
Last updated: August 17, 2026
Packages and collection cover the revenue side of the institution; this module shows the whole statement. Income and expense entries are recorded with a category and a document. Pending student payments can be listed and collected in bulk, and a payment collected by mistake can be reverted. The same flow works on the teacher side: pending payouts are listed, the selected ones are paid, and can be reverted if needed. A staff payment is created with a suggested amount and lands as pending. A collection or payment made through quick actions does not just close the record, it lands in the statement on its own: a collected instalment is written as operating revenue and a paid teacher payout as operating expense, carrying the plan's category and the relevant branch. For a chosen date range you can pull a hierarchical financial statement, a collection status report and an income-expense report.
How it works
Record the entry with its document
An income or expense entry is filed with a category, and a document (invoice, receipt) can be attached. The record can be edited or deleted later.
Run student collection
Pending student payments are listed and the selected ones are collected in bulk. A payment marked by mistake can be reverted to pending.
Pay teacher payouts
Pending teacher payments are listed, the selected ones are paid, and can be reverted if needed. A staff payment is created with a suggested amount and joins the pending queue.
Let the entry reach the statement by itself
A collected instalment is written to the budget as operating revenue and a paid payout as operating expense; the category comes from the plan's own definition and the entry is attached to the relevant branch. No second entry is created for the same instalment or the same staff payment, so there is no double-entry risk.
Read the category breakdown
Income and expense categories are reported separately; the monthly finance table and the executive summary are produced from the same data.
Pull the statement
For a chosen date range the system produces a hierarchical financial statement, a collection status report and an income-expense report. Budget simulation takes its baseline from the institution's real data.
What it offers each role
Institution Admin
Manages income and expense entries, runs the collection and payout flows, and reads the statement and executive summary.
Teacher
Sees their own payout records; coaching payouts are listed month by month.
Parent
Receives the payment confirmation notification and follows paid and pending instalments from their own screen.
- Income and expense entries are recorded with categories, and a document (invoice, receipt) can be attached to each one.
- Pending student payments are collected in bulk, and a mistaken record can be reverted to pending.
- Teacher payouts follow the same flow: pending items are listed, selected ones are paid, and can be reverted.
- A staff payment is created with a suggested amount and joins the pending queue.
- Income and expense category breakdowns are reported separately.
- Hierarchical financial statement, collection status and income-expense report by date range.
- Collected instalments and paid payouts reach the statement on their own, with no separate manual budget entry.
- The automatic entry carries the plan's category and the relevant branch, and no second entry is produced for the same instalment.
- Budget simulation takes its baseline values from the institution's real data.
Frequently asked questions
Packages and Collection manages the student's package, instalments and card payments, that is the revenue side. This module covers the whole statement: expense entries, teacher payouts, staff payments, category breakdowns and financial statements by date range.
Yes, a document can be uploaded to a budget entry; the invoice or receipt stays attached to the record.
Yes. Both student collection and teacher payment can be reverted to pending; the operation is not one-way.
When a staff payment is created the system offers a suggested amount and the record lands as pending. On the coaching side, payouts are additionally listed month by month.
No. The moment a collection is marked, an operating revenue entry is created, and when a payout is paid an operating expense entry is created; the category comes from the plan's definition and the entry is written to the relevant branch. The system does not open a second entry for the same instalment.
For a chosen date range: a hierarchical financial statement, a collection status report, an income-expense report and a category breakdown report. There is also a monthly finance table and an executive summary dashboard.
Related features