All modules Leadership & Analytics

Fee Reports software for Indian schools

Collection and dues

Feature identity
Fee Reports
An illustration, not a screenshot. The interactive example below shows what this capability actually does.

Fee Reports in a school workflow

Filter-aware example

School scopeSelected periodAuthorised columns

Evidence fieldSourceReview state

Collection, outstanding, aging and defaulter reportsScoped school recordReviewable

IST day-bucketing on every money dateScoped school recordReviewable

CSV and Excel export with numeric rupee columnsScoped school recordReviewable

Figures reconcile with the GL statementsScoped school recordReviewable

Code-native illustrative example · not live product UI · no customer dataExample labels and outcomes come from this capability's reviewed catalogue record.

Product scope

What it does

The finance picture in named reports: fee collection per class (billed, collected, pending), outstanding, aging buckets (0-30 / 31-60 / 61-90 / 90+ days) and a student-level defaulter list — all in exact paise, IST-bucketed so a late-evening payment lands on the right school day.

The school problem

School teams need a dependable way to handle Fee Reports: Collection and dues. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

Collection and dues.

Collection, outstanding, aging and defaulter reports
IST day-bucketing on every money date
CSV and Excel export with numeric rupee columns
Figures reconcile with the GL statements

Operational result

What your school gets

Exact-paise collection, outstanding, ageing and defaulter reports that reconcile to supported finance sources.

Access and ownership

Who typically uses it

Accountant
Bursar
Principal
School owner

What each person can actually see depends on the role you give them and which classes or records you assign.

Availability and setup

What to confirm before rollout

Included from Starter

A fixed library of school reports with tables, charts and CSV or XLSX export.

A plan that includes Reports, plus issued invoice/payment records
Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Connected operating context

Available workflows

These are the documented neighbouring capabilities that school teams may review with this module. A related page does not imply that every hand-off is automatic or enabled in every plan.

Explore all modules

Buyer questions

Frequently asked questions

The questions school owners ask before they subscribe: what it does, who can see it, and what to set up first.

Does Fee Reports work on its own?

Pending Fee Tracking, Financial Summary, Accounting Reports, Export Excel are the documented neighbouring capabilities. They help a school evaluate the surrounding hand-offs, but a related page does not mean every integration is automatic or included in every plan.

What should our school prepare before enabling Fee Reports?

A plan that includes Reports, plus issued invoice/payment records. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Is AI used in Fee Reports?

No AI capability is asserted for Fee Reports. Its documented work remains controlled by school records, roles and permissions.

How do we confirm the plan and implementation scope?

Fee Reports is included from Starter in the current public plan matrix. Final rollout scope, services and external dependencies are confirmed in your written proposal.

See the Leadership & Analytics workspace Compare plans and commercial costs

See it in your school context

Run fee reports the connected way.

See how this workflow fits your school's current records, roles, plan and rollout requirements.