Student Fee Management System

Yes you can. You need not pick the other modules of Vawsum

Yes. Vawsum integrates directly with Razorpay, PayU, SabPaisa, Easebuzz, ICICI Bank, HDFC Bank, Axis Bank, Kotak Bank, IDFC First Bank, Bandhan Bank, Indian Bank and Punjab National Bank. The integration takes about 2 minutes – you only need to configure your merchant key and secret key. We also support Razorpay and Axis Bank POS machines for card collections at the fee counter. See the full integrations list.

We have a special module called Quick Fees for that, which lets you start collecting fees online without changing the rest of your systems.

Yes, our software support both cash and online fees collection.

Yes. The cashier panel is restricted to the school hours you configure. Once the cutoff time passes, cashiers can no longer access the panel, so no counter collection is recorded outside the working day.

Parents can pay in Cash at school. They can Online through the Web or App as well.

Yes, we can customise the solution to your requirement

Yes, our system supports multiple fees collection in a month. You can generate separate receipts for them as well.

We can configure the system in a few hours if we have all the data

Not while the earlier month is fully outstanding – the system enforces payment in sequence. Where the earlier month has been partly paid, the next month can be collected, so a family paying in instalments is not blocked while genuine arrears still surface.

Yes. Parents can be prevented from paying the current year’s fees while any fee book from the previous academic year remains outstanding, so old arrears are dealt with rather than carried forward indefinitely.

Yes. Each fee book can carry its own late fine logic, so tuition, transport, hostel and library follow the policy your institution actually applies to each rather than a single rule imposed across all of them.

Yes. Standard fees for a class-section can be edited in bulk, and concessions can be given across multiple headers and multiple months through reusable concession templates rather than student by student.

No. A receipt cannot be cancelled once a later month has been paid in full, which keeps the ledger consistent rather than leaving a gap in the middle of a paid sequence.

Automatically. The system distributes a partial payment across the fee headers itself, so the cashier does not decide which head to credit and two cashiers do not apply the same part payment differently.

No. If a header amount is edited after full payment, the fee collection reopens and further collection continues against the revised amount – so a mid-year correction to a fee structure does not leave the student stuck as fully paid.

Yes. The collected-on date can be edited after the payment has been recorded, so a receipt entered a day late reflects the date the money actually came in rather than the date somebody got to the entry.

The cashier can capture the missing transaction in a single step from the payment capture page, so the payment posts against the correct student and Vawsum stays reconciled with your payment gateway records.

Yes. Concession authority can be restricted to specifically authorised users rather than left open to every cashier. A concession cannot be applied without an approval attached to it, and the full grant – who approved it, and on what basis – is kept on an audit trail.

Cancelling a receipt requires a mandatory reason, and the cancellation is flagged separately for audit rather than simply removing the entry. The original receipt number can never be reused, so the numbering sequence itself shows exactly where a cancellation happened.

Yes. Cheques have their own dedicated workflow for recording, tracking and settling, kept separate from cash, online and POS collections rather than mixed into the same record.