School Fee Payment Software

Card data is never stored on your servers or in the fee module database. When a family pays by card through the online portal, the transaction is processed entirely within the payment gateway's PCI-compliant environment. The fee module receives only a tokenized confirmation and records the payment against the invoice. Your institution's PCI DSS scope is limited to the gateway integration layer, not the fee management system itself. For institutions on self-hosted deployments, this architecture is documented in the implementation guide.

Installment plans are defined at the fee structure level: you configure how many installments, the due date for each, and whether a late fee applies if an installment is missed. When a family makes a partial payment, the system records it against the earliest outstanding installment first, carries any remainder forward, and updates the running balance immediately. AR aging reflects partial payment status accurately, a student with a partially paid invoice appears in the correct aging bucket, not grouped with fully unpaid accounts.

When a payment fails (whether due to insufficient funds, a declined card, or a gateway timeout) the system records the failed attempt with a reason code and sends a notification to the family with a direct link to retry. The finance team sees the failed attempt in a dedicated failed payments queue in the dashboard. The invoice remains open and the student's balance is unchanged. For installment plans, a failed payment triggers a configurable grace period before a late fee applies, giving the family time to resolve the issue without an immediate penalty.

Fee invoices and payments post directly to the accounting module's general ledger with no duplicate entry. Each fee type maps to a revenue account you configure during setup, so a tuition invoice posts to the tuition revenue account and a hostel charge posts to the hostel revenue account automatically. When a payment is recorded, the corresponding accounts receivable entry clears. Finance teams using the accounting module for GL management, bank reconciliation, and financial reporting work from a single source of data. No export, no import, no re-entry.

Yes. A parent portal account can be linked to multiple students. When the parent logs in, they see a combined dashboard showing each child's current balance, pending invoices, and payment history. They can pay each child's invoice separately or, where the institution allows combined transactions, pay for multiple accounts in a single checkout. All receipts download per-student and per-transaction from the portal history, without the parent needing to contact the bursar's office.