Delete and Regenerate Fee Challans Made by Mistake

Should you remove the challans or correct them in place?

Not every mistake needs a full delete and regenerate. If the month, due date and students are right but an amount is wrong, it is usually quicker and cleaner to correct the existing fee challans than to remove the whole batch.

Remove and regenerate when the batch itself is wrong: the wrong month, the wrong campus or class, a duplicate run for a month already billed, or the wrong due date across the board.

• A fine or extra charge was missed: use Add amount to generated challans on the challans that already exist.
• One child's fee is wrong: use the per-student fee change for that single challan, with any concession recorded against the plan.
• A large charge should have been split: generate installment challans instead of one voucher.
• The whole run is for the wrong month, scope or due date: remove the unpaid challans from that run and generate again.

What should finance check before removing a wrong batch?

Before anything is removed, confirm exactly which challans came from the mistaken run and whether any family has already paid against them. A few minutes of checking avoids cancelling a genuine payment or leaving a duplicate behind.

• If the challans were created by scheduled challan generation, open the automation's Run history to see what that run created and when.
• Check Day Wise Paid Challans and Payment History for any payment, including bank payments, recorded against the wrong challans.
• If bank fee collection is active, remember a parent may have paid the consumer number at a branch, ATM, mobile app or 1Bill/1LINK channel; those payments post in real time.
• Note whether parent alerts went out on generation, so you can send a correction afterwards.

How do you remove the wrong challans and generate them again?

Work in a fixed order so balances stay correct. Payments come first, then the unpaid challans, then the new run.

Doing this promptly matters: in EDUBase unpaid balances roll into the next challan as arrears, so a mistaken challan left in place can carry forward onto the following month's voucher.

• Cancel any payment taken against a wrong challan; cancelled fee transactions appear in Voided transactions with who and when.
• Remove the unpaid challans from the mistaken run, using a login that has been given that action.
• Correct the cause: the month, due date, expiry, campus or class scope, or the schedule settings if fee automation created them.
• Generate challans in bulk again for the correct month and scope; school-wide runs are queued in the background and you are notified in-app when they finish.
• Re-take any cancelled payment against the new challan and print a receipt, using a consolidated or family receipt where that suits the parent.

What happens to payments made against a mistaken challan?

A paid challan should never simply disappear. Cancel the payment first so the record of the cancellation is kept, then re-apply the money to the correct challan once it has been generated.

Fee payments post to the finance ledger automatically, so after cancelling and re-taking payments it is sensible to check the cash report and general ledger for the day. For bank payments, paid-voucher protection means a challan already paid answers as paid to any later inquiry, so the family is not charged twice on that voucher.

How can you stop wrong challans being generated again?

Most wrong runs come from a mistyped month or scope, or from an automation set up before the fee policy was final. EDUBase gives you several checks before money is billed.

• Every automation ships switched off and has a preview that shows which children would be affected and by how much, charging nothing.
• Scheduled challan generation uses a fixed generation day, due date, expiry and scope; review these whenever the session or fee plan changes.
• Late fee automation can also be previewed, so fines are not applied to challans you intend to remove.
• Give the right to generate and remove challans only to the staff who need it, using per-user, per-screen and per-action privileges.
• The AI assistant's form-fill copilot proposes the fields for a task such as this month's challans with a due date; you review and save.

Who can remove challans and how is it tracked?

Access is controlled per user, per screen and per action, and can be limited to particular campuses. A school can therefore let one person generate challans while reserving removal and payment cancellation for a senior finance officer.

User Logging records who created, changed or deleted any record, with the changed fields highlighted and a severity badge, and a daily summary of important changes reaches the navbar bell and the Owner App.

Fixing fee challans generated by mistake: which approach fits

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.
• Finance & Accounting — Chart of accounts, journals, ledgers, trial balance, P&L and balance sheet, fed by fees and payroll.
• Users, Privileges & Activity Log — Give each staff member exactly the screens and actions they need, and see who changed what.
• AI Assistant & Automation — Ask the built-in assistant in English or Roman Urdu, speak instead of type, and let it fill forms.