Guide
School fee vouchers and receipts, done properly
What belongs on a fee voucher, numbering an auditor can trust, receipts against bank transfers, and printing a class's challans in one run.
A fee voucher is a small document doing serious work: it is the school's formal demand, the parent's proof of what was asked, and the auditor's trail when something looks wrong. Done properly, vouchers and receipts make fee disputes short and fraud hard. Done loosely, with hand-numbered books and totals kept in someone's head, they make both easy. Here is what properly looks like.
What belongs on the voucher?
| Block | Contents | Why |
|---|---|---|
| Identity | Voucher number, student, class and section, roll number, period | One voucher, one student, one period: the audit unit. |
| Charges | Each fee head on its own line; concessions as visible lines | A discount shown as a line keeps the outstanding figure honest; a silently reduced total hides who approved what. |
| Terms | Total, due date, the late rule as published | The fine that surprises nobody is the fine that gets paid. |
| Payment routes | Desk hours, bank account details for transfers | Families pay faster when the voucher says how. |
How does a clean voucher-to-receipt cycle run?
- Generate the month as a batch, with a preview. In EDUTIG a whole class's invoices generate from the fee plans with a preview first, so the wrong-amount voucher is caught before printing, not at the desk.
- Number continuously, by the system. No hand-kept sequence, no duplicate books, no gaps that need explaining.
- Receipt every payment against its invoice, whether it arrived at the desk or as a bank transfer with uploaded proof. The receipt names the voucher it settles.
- Reverse, never delete. A wrong entry is reversed with a reason, keeping both the mistake and the correction on the record. A system that lets anyone delete a payment is a system an auditor cannot trust.
- Reconcile weekly: vouchers issued, payments received, outstanding remaining. Three numbers that must agree, and in software they agree automatically because they come from one ledger.
What does this look like at audit time?
An auditor, a board inspection, or a parent dispute all ask the same three questions: what was demanded, what was received, and where is the difference? A school on this cycle answers from one screen: the voucher sequence with no gaps, each receipt against its invoice, concessions as approved lines, reversals with reasons. A school on voucher books answers with a week of totalling. The ledger thinking behind this is in our fee management guide, the collection channels in online fee collection, and the module itself, with screenshots, on the fees and collection feature page. One forward note: Pakistan's proposed e-invoicing rules would make disciplined, numbered invoicing a legal baseline rather than good practice; our FBR e-invoicing guide explains the actual status of that proposal.