Fee plans per student
Term plans, optional components, sibling and staff concessions and transport slabs resolve into one due amount per student, with the rule that produced it visible.
School management system · Fee management software for schools
Fee management that closes the month without a spreadsheet.
Fee collection in an Indian school is not one number. It is term plans, concessions, transport slabs, late fees, partial payments and a reconciliation that someone does by hand every month. SquareCampus keeps all of it on one ledger with an owner against every exception.
Finance officersBursarsTrust accountantsPrincipals
Direct answer
What is fee management software?
Fee management software is the part of a school system that defines fee structures, raises dues per student, records payments across channels, applies concessions and late fees, issues receipts and reconciles collections against the bank. Done well, it is a ledger the whole school shares rather than a collection module that finance reconciles against everything else.
SquareCampus is school management software built as a connected School OS. It covers the record-keeping and workflows schools expect from school management and ERP software, and connects them with owners, approvals and audit history on one institutional record. Read the canonical definition.
How it runs in SquareCampus
Each step has an owner and leaves a record
A module list hides the real question: does the work connect? These are the workflows as SquareCampus is designed to run them.
Collection across channels
Online payments, counter cash, cheques and bank transfers post to the same ledger and issue receipts from one sequence.
Reminders with an acknowledgement
Dues reminders go to parents in context, and the record shows what was sent, when, and whether it was seen.
Concessions and refunds as approvals
Every concession, waiver and refund runs through a role-scoped approval with a reason, so the finance trail is complete before an audit.
Reconciliation and audit exports
Collections reconcile against settlements and bank statements, with exports in the formats auditors and trust boards ask for.
This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when.
A worked example
A sibling concession above the desk's limit
How the workflow is designed to run, step by step, and where configuration, scoping or separate quotes apply.
- 1The accounts desk applies a sibling concession larger than its approval limit.
- 2The request routes to the approver the institution named for that limit, with the reason attached.
- 3Once approved, the fee plan, the next invoice and the receipt reflect it; if refused, nothing changes.
- 4The approval, the approver and the reason stay on the student's fee record for audit.
Configured, scoped or quoted separately
- Fee heads, instalments, concessions and late-fee rules are configured from your current structure during implementation.
- Payments run through your institution's own gateway account; SquareCampus never handles the money, and gateway fees are between you and the gateway.
- Connections to accounting software are scoped integration work, assessed per package; there is no pre-built connector.
- Historical dues and receipts are migrated from Pro and validated in a parallel run; anything the old records cannot support is flagged before go-live.
Built for India
The realities Indian schools run on
Boards, fee structures, trusts and parent channels are configuration here, not customisation projects.
India-first specifics
- GST-aware receipts for taxable components such as transport and hostel.
- Partial payments and instalment plans without losing the original due.
- Late-fee rules that respect board holidays and school-specific grace periods.
- Trust-level visibility across campuses with campus-level execution.
- Follow-up on overdue fees as a workflow with an owner, not a printed list.
What to check in any vendor
Ask these of every vendor you evaluate, including us. The answers separate a connected system from a set of modules.
- 1Can one student carry a term plan, a concession and a transport slab without a manual override?
- 2Do online, counter and bank payments land on the same ledger and the same receipt sequence?
- 3Is every concession and refund approved by a named role with a recorded reason?
- 4How long does month-end reconciliation take, and who does it?
- 5Can the trust board see collections across campuses without a prepared report?
Questions
Fee management software for schools: common questions
Short answers, the way a buyer asks them. The FAQ page covers evaluation, security and rollout in more depth.
Yes. Term plans, concessions, transport slabs, late fees, partial payments and GST-aware receipts are part of the fee model rather than customisations.
Online payments through a payment gateway, counter cash, cheques and bank transfers post to one ledger. Gateway options are confirmed during scoping.
Outstanding dues become a follow-up workflow with reminders in context, an owner, and a record of every contact, so leadership sees the state without chasing the office.
Yes. Collections and receipts export in accounting-friendly formats, and a bounded deployment can run alongside the existing finance stack.
More on evaluation, security and rollout in the FAQ.
Related
Keep reading
The pages a buyer on this question usually reads next.
School fee reconciliationWhy the month-end takes so long, and what fixes itSchool management systemFees inside the wider operating loopSquareCampus vs Entab CampusCareAn honest comparison for finance-led evaluationsRolloutParallel run on the fee ledger before go-livePricingStudent-volume bands, modules included
Next step
Bring one real bottleneck. We will show how it runs.
A guided demo on your own scenario, followed by a written scope, from a founder-led team. The licensing model is published; figures follow a written proposal.