Follow the complete school fee journey

Begin with the demand

Identify the academic year, applicable fee heads, due dates and concessions. Review how transport or optional charges are assigned, and how changes affect an already-issued demand. Opening balances deserve their own reconciliation before rollout.

Distinguish a payment attempt from a receipt

An online payment can be pending even after a browser returns to the school app. Ask which provider confirmation is required before a receipt is issued. A retry, webhook or browser refresh should not duplicate a collection.

• Can the office identify a pending transaction?
• Is the amount checked against the demand and provider evidence?
• What happens when the provider is temporarily unavailable?
• Can the family see a clear next step without an unsupported claim about their bank balance?

Check adjustments and reconciliation

Ask to see the receipt, allocation and outstanding balance together. Test partial payments, concessions, duplicate attempts and refunds with synthetic data. Overpayments need an explicit accounting policy; do not assume that cash collected and income earned always mean the same thing.

Treat reminders as a separate service

Preparing a reminder is different from delivering it. In-app messages, email, SMS, WhatsApp and push each have their own requirements. Confirm sender configuration, consent, provider cost, delivery status and failure handling before promising a family an alert.

Reconcile before and after migration

Agree totals for students, fee demands, paid amounts and balances before import. Compare those totals afterwards, inspect exceptions and obtain a review from the person responsible for the accounts. Keep a recoverable copy of the original records.