Every fee, structured
Fee heads, class-wise variants, and transport or hostel matrices, set once per campus.
06 · Money that stays explainable.
Fees & Finance
Dues, receipts, concessions, and refunds stay clear in every transaction.
Hear it from Syfty
EdSyft module 06
Why it matters
The operating detail behind the promise.
Fee software earns or loses trust in a very specific moment: when a parent disputes a number, and someone has to explain exactly how it was arrived at. Most systems let a balance change with an edit: a number goes in, a different number comes out, and nobody downstream can tell what happened. Edsyft doesn't allow that. A fee balance only moves through a recorded transaction: payment, concession, refund, or reversal. Each entry is dated and linked to the person who posted it.
Every fee head a school charges, such as tuition, transport, hostel, or activity fees, is configured once, with its own billing behaviour. A fee head can be flat for everyone, scaled by class size, split by zone, or tied to a room type for hostel charges. Demand plans can bill annually, term-wise, or on a custom installment schedule. None of this is hardcoded per school; it's set up once in configuration and reused every term.
Discounts and waivers are never a quiet edit to a student's balance. A concession is filed as a request: percentage-based or a fixed amount, capped either way, and it does not take effect until the organization approves it. There is no button that lets a school approve its own concession; the approval step exists at the network level by design, so a discount always has a second set of eyes on it before it touches a family's dues.
Cash handling gets the same discipline. A cashier opens a shift with a declared amount, collects through the day, and closes against what the system expects based on actual recorded payments, not a manual tally. If the drawer doesn't match, that variance doesn't get shrugged off locally; it routes to the organization for approval before the shift is considered closed.
What it handles
The work that should not disappear between screens.
Every capability below maps to a real operating decision, handoff, or record inside the module.
Receipt and ledger, together
Every payment posts in one step, on a gapless, sequenced receipt number.
Reprints, never invisible
A reprinted receipt is logged with who, when, and why, and stamped "Duplicate copy."
Nothing erased, only reversed
Concessions and refunds route through approval, and every ledger change leaves a reason behind.
Cash that reconciles itself
Cashier shifts close against actual collections; any variance goes to the organization for approval.
Dues that don't drift
Late-fee rules apply automatically, and outstanding dues are visible by student, class, or campus.
A concession, start to finish
A discount on a family's fees is never a direct edit. It's a request that has to clear approval before it changes anything.
01
Requested
School files a concession request against a fee head, percentage or fixed amount.
02
Capped
The request is checked against the configured maximum for that fee head.
03
Sent to org
There is no school-level approval step. It goes to the organization.
04
Approved or denied
The organization decides, with the reason on record either way.
05
Applied
Only once approved does the concession touch the student's balance.
How it is controlled
Rules that make the workflow trustworthy.
Permissions, approvals, and state changes are part of the workflow itself, not instructions left for a staff meeting.
Concessions, capped either way
A concession is set as a percentage of the fee head or a fixed rupee amount, and either way, a configured maximum stops a discount from going further than policy allows.
No self-approval, anywhere
A school can file a concession or a refund. Only the organization can approve one. That separation is structural, not a setting someone could turn off.
Grace days, then a rule, not a guess
Late fees follow a configured grace period, a fine type, and a frequency, with an optional cap, applied the same way for every family, every term.
A reprint is still on the record
Reprinting a receipt doesn't create a quiet duplicate. The copy is watermarked, and the reprint itself is logged against the person who asked for it.
Value propositions
A better day for the people doing the work.
What changes for the team once this module is running in daily work.
An append-only ledger
A mistake isn't erased. It's reversed in the open, with a name and a reason attached to the reversal.
Approval before balances move
Concessions, refunds, and cashier variances all route to the organization before anything changes.
Fee heads that fit how you actually charge
Whether flat, class-based, zone-based, or room-based, a fee head's billing logic matches the real policy, instead of forcing every charge into one shape.