Design fee collection so every receipt can be explained later.

A fee module is useful only when the school agrees on the fee structure, who may collect money, how discounts are approved and what happens when a receipt needs correction.

Define fee heads before collecting

Start by documenting the fee heads and expected amounts the school actually uses. Avoid creating slightly different names for the same charge because that fragments reports and makes reconciliation harder.

Use the student record as the collection anchor

Search and select the verified Student Master record before collecting a fee. The collection should inherit the student's school context rather than asking staff to type the student's identity from memory on every receipt.

Separate normal collection from exceptional changes

Discounts, late fees and receipt adjustments deserve more control than ordinary collection. Decide which role can apply them and whether the school requires a reason. The system should record the final amount and preserve the operational trail.

Do not run parallel receipt systems

If one office records receipts in the ERP while another maintains a separate spreadsheet as the “real” ledger, discrepancies are almost guaranteed. During rollout, decide which system is authoritative and use temporary reconciliation sheets only as migration aids.

Reconcile by totals and exceptions

At the end of a day or reporting period, compare receipt count and collection totals with the school's cash/bank process. Investigate exceptions such as unusual discounts, cancelled operations or duplicate references instead of editing totals to force a match.

Permissions matter

• view fees only;
• collect fees;
• apply adjustments where permitted;
• view reports;
• perform sensitive correction or administrative action.

Not every teacher or staff user needs every level. Grant the least access that still lets the person complete their assigned job.

Before importing historical collections

Verify the student identifiers and receipt references first. Historical imports should be staged and reviewed because old spreadsheets often contain inconsistent class labels or formatting that was acceptable in a manual process but becomes ambiguous inside a database.