Fee collection is where admission season traditionally hurts most: cash counters, demand drafts, bank challans and a reconciliation backlog that outlives the admissions themselves. Managed online, the entire pipeline runs itself. Here is how modern fee collection works on ePravesh.
The old process vs the online pipeline
❌ Counter-and-challan
- Bank queues and demand drafts
- Weeks matching challans to applications
- Cash handling risk at the office
- Receipts issued at a window
✅ Online fee collection
- UPI, cards, net banking in the form
- Auto-verified, auto-reconciled
- Reconciliation worker catches stragglers
- Instant branded receipt PDFs
Online fee collection, end to end
Every payment mode students actually use
The application form ends at a payment step offering UPI, debit and credit cards, and net banking. UPI matters most: it is how the majority of Indian students and parents now pay, with no card details to type on a phone.
Automatic verification — including the failure paths
Each payment is verified with the gateway and the application is marked paid instantly. The paths that break manual processes are handled too:
- A background reconciliation worker re-checks pending payments, so a payment that succeeded at the bank but missed its confirmation callback still lands as paid — no student is stuck holding a debited-but-unconfirmed payment.
- Admin overrides let your team record a cash or offline payment against an application, so one process covers every payer.
Structured fees without spreadsheet math
Fee rules that used to live in a clerk's head are configuration:
- Category-wise fees — each category in your institute's list can carry its own fee per course; the form charges applicants correctly based on their selected category.
- Early-bird and late slabs — date-range fee schedules apply the right amount automatically as deadlines pass.
- Coupons — discount codes, up to full waivers, apply at payment time for scholarship or staff cases.
Instant, branded receipts
Every payer immediately downloads a payment receipt PDF carrying your institute's logo, alongside their application form PDF. The "receipt window" ceases to exist.
Reconciliation your accounts team will accept
The payments dashboard lists every transaction with its gateway reference and exports to Excel, matching the gateway's settlement report line for line. For institutes with an ERP, payment-confirmed events can be pushed to it in near-real time via webhooks, so finance systems stay current without manual exports.
Beyond the application fee
The same pipeline collects admission fees from selected candidates and works with fee management for post-admission collections — one gateway relationship, one reconciliation process, every fee type.
See how ePravesh works, or book a free demo to walk through your fee structures — categories, slabs and all — on the platform.
Frequently Asked Questions
How do institutes collect admission fees online?
Through a payment gateway integrated into the application flow — students pay by UPI, debit/credit card or net banking at the end of the form, the payment is verified automatically, and a receipt is generated instantly.
Can different student categories pay different fees?
Yes. ePravesh supports per-category fee overrides — each caste/category in your institute's list can carry its own fee per course, and the system charges the right amount based on the category the applicant selects in the form.
What are early-bird and late fee slabs?
Date-range fee schedules — a lower fee for applications before a chosen date and a higher fee after the deadline extension, applied automatically by date without staff intervention.
What happens if a payment succeeds but the confirmation fails?
A background reconciliation worker re-checks payments against the gateway, so a payment that succeeded at the bank but missed its confirmation callback is still marked paid automatically. Admins can also record offline or cash payments against an application manually.
How does the accounts team reconcile online admission payments?
Every payment sits against an application with its gateway reference, and the payments list exports to Excel. The export matches gateway settlement reports, which removes manual challan-matching entirely.