Duplicate Fee Challans: Causes and How to Remove

Why does a student end up with two challans for the same month?

In EDUBase, fee challans are created in bulk for a campus, a class or the whole school, either by someone in the office or by Fee Automation on a fixed date. A second challan for the same month almost always traces back to one of a few situations, and some of them are not errors at all.

Before removing anything, work out which situation you are looking at. Removing a genuine installment voucher or a challan that has already been paid causes more trouble than the duplicate did.

• Scheduled challan generation is switched on and someone also generated the same month manually.
• A school-wide run was started twice because the first one was still processing in the background.
• A large fee was split into installment challans, so the student correctly has more than one voucher.
• A fine or extra charge was raised as a new challan instead of being added to the existing one.
• The parent is reading arrears carried forward from an unpaid earlier month as a second bill.

How do I tell a real duplicate from a legitimate second voucher?

Open the student's challans and compare the two side by side: month, fee heads, amounts and payment status. A true duplicate repeats the same fee heads for the same month. An installment challan carries part of a larger charge such as annual or admission fees. An arrears line shows old dues rolling into the current voucher, which can print as a month-wise breakdown.

Then find out where each challan came from. If the school uses Fee Automation, its run history logs every run with what it did, so a double month can be traced quickly. For manual runs, User Logging shows who created the records and when, and the student change log shows who changed the child's fee, class or status.

• Same month, same fee heads, both unpaid: likely a duplicate.
• Same month, different portions of one large charge: installment challans, keep both.
• One challan with an old-dues breakdown: arrears carried forward, not a duplicate.
• Check Payment History and Day Wise Paid Challans to see whether either one has been paid.

How do I remove the extra challan safely?

Only remove the copy that is both extra and unpaid. If the parent has paid one of the two, keep the paid one and cancel the other. A user needs the right privilege to cancel challans; per-user, per-screen and per-action rights decide who can do it.

If the duplicate affected a whole class or campus, deal with it as a batch rather than child by child, and confirm the counts afterwards in Student Wise Fee Status and the fee defaulter reports so families are not chased for money they do not owe.

• Identify the unpaid duplicate for each affected student.
• Cancel that challan from the student's challan list using an account with the right privilege.
• Leave any paid challan untouched; the cancelled record and who did it remain traceable in the voided transactions list.
• Re-run Student Wise Fee Status and the defaulter reports to confirm balances are correct.
• If a reminder already went out, send a short correction to the affected families.

What if the parent has already paid both challans?

If both copies were paid, the family has been overcharged for that month. Keep the payment record, and either refund the difference or let it count towards a later month according to your school's policy. Refunds post to the finance ledger automatically, so the books stay in line with the fee records.

For bank payments, each challan carries its own consumer number. Once a challan is paid, any later bank inquiry for that voucher answers as paid, so the same voucher cannot be charged twice. The risk only arises when two separate vouchers exist, which is why cancelling the unpaid duplicate promptly matters.

How do I stop duplicate challans from happening again?

Most duplicates come from two people, or a person and the automation, doing the same job. Decide on one method for each month's challans and restrict who can run bulk generation.

• If Scheduled challan generation is on, stop manual generation for the same campus and classes.
• Use the preview in Fee Automation to see exactly which children would be affected before it acts.
• After starting a school-wide run, wait for the in-app notification that it has finished instead of clicking again.
• Use Add amount to generated challans for fines and extra charges instead of creating a new challan.
• Limit challan generation rights to named finance staff and review User Logging for fee changes.

Common reasons for two challans in one month and what to do

Related modules

• Fee Management & Challans — Fee plans, monthly challans, discounts, family payments and receipts, without spreadsheets.
• Fee Automation — Let the system generate challans, apply late fees and chase defaulters on schedule.
• Fee Reports & Defaulters — Know what was billed, what was collected and who still owes, per class, family or month.
• Bank Fee Collection — Parents pay at the bank, in their banking app or at a kiosk; EDUBase posts it automatically.
• Users, Privileges & Activity Log — Give each staff member exactly the screens and actions they need, and see who changed what.
• Finance & Accounting — Chart of accounts, journals, ledgers, trial balance, P&L and balance sheet, fed by fees and payroll.