Refunds, processed correctly. Approved, paid, audit-stamped.

How most Indian schools process refunds today

A Class 6 student withdraws on November 15th. The school's refund policy says: refund the unused portion of Tuition (8 months remaining out of 12), keep Admission Fee non-refundable, keep Identity Card non-refundable, refund 50% of Annual Day if not yet held. The accountant opens the parent's fee receipts, the invoices, the refund policies document, and a calculator. Twenty minutes later, a refund proposal is on paper. Twenty minutes after that, the principal questions one number. Forty-five minutes total before the cheque is even drawn.

Meanwhile, an excess-payment from a different parent (paid ₹18,000 instead of ₹15,200 by mistake) sits as 'parent credit' in the accountant's notebook waiting to be refunded — nobody has time to process it, the parent calls every week. A bounced cheque from last month means the school issued a receipt and showed the invoice PAID, but the money never came; the parent now wants the receipt cancelled and the refund issued.

Refunds are a workflow with money and trust. Get them slow, the parent loses trust. Get them wrong, the auditor flags it. Get them silent, the school gets sued. Inkwelly's Fee Refunds module makes every refund a structured, status-tracked record — with explicit approval gates, refund-mode tracking, source-payment links and a transparent timeline parents can see on their portal.

How Inkwelly Fee Refunds work

The Refunds screen at /student-fee/refunds lists every refund record with filters for status (FeeRefundStatus enum: PENDING / PROCESSING / COMPLETED / FAILED / CANCELLED), refundType (FeeRefundType enum: WITHDRAWAL / EXCESS / BOUNCED / OTHER), refundMode (FeeRefundMode enum: CASH / CHEQUE / NEFT / UPI / CARD / GATEWAY_REVERSAL / BANK_TRANSFER), and date windows. Each refund has a unique refundNumber, the source-payment / source-receipt links preserved, the refund amount and net amount (after deductions), and full audit metadata.

Refunds enter the system three ways. From a payment: from any successful Payment's detail page, click Create Refund — the dialog asks refund type, refund mode, amount, reason. From a withdrawal: when a student is marked withdrawn, the withdrawal flow auto-computes the refundable amount based on the refund policy attached to the school's fee structures and emits a draft refund. From a cancelled receipt: when a receipt is cancelled, if money has been collected, the refund workflow opens automatically with the source-receipt link.

Every refund runs through PENDING (created, awaiting approval) → PROCESSING (approved, payment in flight) → COMPLETED (money returned, audit-stamped) or FAILED (gateway/cheque rejected, with reason) or CANCELLED (admin overrode). The ProcessRefundDialog lets the finance role advance status, capture the actual refund-mode reference (cheque number / UTR / gateway refund ID), and timestamp completion. The CancelRefundDialog lets admin role cancel a pending refund with reason. Parents see refund status on their portal in real time.

Walkthrough — three views, end to end

“Pichle saal hum withdrawal refunds 2-3 hafte mein process karte the — binder se calculate, principal se sign, bank se cheque draw. Ab Inkwelly mein withdrawal mark karte hi draft refund auto-emit hota hai — line-by-line breakdown ke saath. Finance officer 24 ghante mein process kar deti hai. Razorpay payments ke liye gateway reversal one-click — parent ko 3 din mein UPI pe wapas mil jata hai. Parent reviews bhi improve hue.”

Real-world refund operations

Withdrawal refund (most common). Class 6 student withdraws Nov 15. The Student Information withdrawal flow auto-computes refund per fee head per the refund policy. Finance reviews the proposed line-by-line breakdown, processes the refund (cheque or NEFT), parent gets the money in 24-72 hours.

Excess-payment refund. Parent paid ₹18,000 instead of ₹15,200. The accounts officer creates a refund of type EXCESS from the payment's detail page, refund mode CASH or CHEQUE, parent picks up the cheque next day.

Bounced-cheque refund. Cheque was issued + receipt generated, then cheque bounced. The bounce reverses the payment and cancels the receipt automatically; if the parent had paid via card or UPI alongside, a partial refund of the over-paid portion runs through the workflow.

Gateway reversal. Parent paid via Razorpay; school refunds via gateway reversal. One click; the gateway settles to the parent's original UPI/card in 2-7 business days; the refund.processed webhook auto-marks COMPLETED.

Pre-admission deposit refund. Parent paid an admission deposit, then chose a different school. Refund type WITHDRAWAL with custom reason; refundable per the school's pre-admission refund policy.

See refund creation + processing live in 30 minutes

Bring a sample withdrawal scenario or an excess-payment case from your school. We'll model the refund inside Inkwelly during the demo — auto-compute the breakdown, advance through PENDING → PROCESSING → COMPLETED, demonstrate gateway reversal for online payments. By the call's end, you'll see the full audit trail.

Limits, safety and the small print

Status transitions are server-enforced. PENDING → PROCESSING → COMPLETED. Out-of-order writes are rejected. CANCELLED requires admin role and reason; FAILED captures the gateway / bank rejection reason verbatim.

Source links are immutable. A refund's source-payment and source-receipt links cannot be edited after creation. The full chain (Invoice → Payment → Receipt → Refund) is auditable end-to-end.

Approval gates are role-based. IAM-controlled: counter staff cannot approve; finance role advances PENDING → PROCESSING; admin role can CANCEL. Server-side enforced.

Gateway reversal depends on settlement. Refunds via Razorpay / PayU / Cashfree GATEWAY_REVERSAL mode are subject to the gateway's refund window (typically 90 days for UPI, 180 days for cards). Outside this window, manual NEFT or cheque is required.

Net amount = refund amount minus deductions. Schools that charge admin fees on withdrawal (per their refund policy) can capture the deduction line; parent sees gross + deductions + net on the refund detail.

Multi-tenant isolation. Each school's refunds are isolated. School A's refund is invisible to School B even within the same trust.

DPDP Act 2023 alignment. Refund records contain student PII, parent payment instrument data and refund destination details. Encrypted at rest with AES-256 on Mumbai-region servers; accessible only via IAM-controlled roles. Audit log records every status change, refund-mode reference, approval, cancellation and parent communication — with user, timestamp and IP. CBSE / Income Tax / GST / NCPCR inspections answer from a single audit export.