For the Finance Office

The Finance
Dashboard.
Every rupee, accounted.

Six surfaces written for the desk that carries the school's money — a live collection ledger, a dues engine that chases itself, nightly reconciliation, payroll and expense control, an append-only audit record, and a cashflow forecast that warns months ahead. The number stops being assembled and starts being available.

Scroll the keynote — one act per surface, one decision per act.

01Collections

Today’s collection, closed by 6 PM — not by month-end.

In most schools the real collection number is three days old. Cash sits in a drawer register, UPI lands in a bank statement nobody has downloaded, cheques are in a folder waiting to clear, and the accountant reconciles all three into a spreadsheet at month-end. Until then, every answer the owner asks for is an estimate dressed as a fact.

Edullent closes the ledger as the day runs. Every receipt — cash, UPI, card, cheque, bank transfer — posts against the student, the term and the head the moment it is taken. The finance officer ends the day with a number that is already reconciled, already broken down by class and branch, and already defensible.

How it works

A live fee ledger that posts every receipt against student, term and fee head at the moment of collection, across every payment mode.

Signals it reads

  • Receipts across cash, UPI, card, cheque and bank transfer
  • The fee structure assigned to each student
  • Concessions, scholarships and sibling waivers
  • Term schedule and due dates

What the engine computes

  • Each payment split across fee heads by the structure, not by hand
  • Partial payments carried as a running balance rather than a note
  • Class, branch and head totals recomputed on every entry
  • One ledger per student, whatever mode the money arrived in

Decisions it drives

  • Whether today’s collection is on pace for the term
  • Which class or branch is lagging, while there is still time
  • What to bank tonight, and what is still uncleared

One number, always current

Collected · pending · overdue, recomputed on every receipt. The owner asks at 4 PM and gets today’s figure, not last week’s spreadsheet.

Receipt at the counter

Numbered receipt generated, printed and pushed to the parent’s app in the same action. No duplicate books, no missing serials, no re-entry.

Every mode, one ledger

Cash, UPI, card, cheque and transfer land in the same student ledger — with clearance state carried, so uncleared cheques never inflate the day.

6 PM

Day closed with a reconciled collection figure · vs month-end in the register era

0 serials lost

Receipt numbering issued by the system, never by a counter book

02Dues · Reminders

The defaulter list that chases itself.

Fee follow-up is the job every school does badly, because it is the job nobody wants. Someone prints a defaulter list, someone else calls thirty parents, half the numbers are stale, the calls are awkward, and by the time the list is worked the next term has begun. Collection slips not because parents refuse, but because nobody was reminded on time.

Edullent turns the defaulter list into a schedule that runs itself. Reminders go out before the due date, again on it, and again after — each carrying the exact amount and a payment link. The finance desk stops dialling and starts handling only the cases that genuinely need a human conversation.

How it works

An ageing-based dues engine that schedules reminders automatically and escalates only the cases a person needs to handle.

Signals it reads

  • Outstanding balance per student and term
  • Days past due, bucketed by ageing
  • Reminder history and parent response
  • Payment plans and agreed extensions

What the engine computes

  • Dues aged into buckets rather than one flat overdue list
  • Reminders scheduled before, on and after the due date
  • Each reminder carrying the exact amount and a direct payment link
  • Students on an agreed plan held out of the chase automatically

Decisions it drives

  • Which families to call today, and which need no call at all
  • Where to offer a plan instead of a reminder
  • When to escalate to the principal, with the history attached

Reminders on a schedule

App, SMS and email sequences fire on the ageing bucket — not when someone remembers. Every send is logged against the student.

Ageing, not one list

0–30, 31–60, 61–90, 90+ — the desk works the oldest money first instead of re-reading the same names every week.

Plans respected

A family on an instalment plan stops receiving chase messages the moment the plan is recorded. Goodwill survives the follow-up.

~70% fewer calls

Manual follow-up calls needed per term · the rest close on a reminder

9 days earlier

Median day a term’s dues clear · vs the print-and-call cycle

03Payments · Reconciliation

The bank statement and the ledger agree. Every night.

Online fee payment created a second problem the moment it solved the first. Money now arrives through a gateway, in settlement batches, minus charges, sometimes days later, sometimes failed-but-debited. The accountant matches a bank line to a student by hand, and the mismatches pile into a column nobody can explain by March.

Edullent reconciles the two sides itself. Gateway settlements are matched to receipts, charges are booked to their own head, failed-but-debited cases are surfaced the same day, and refunds carry an approval trail. The unexplained column stops existing.

How it works

Automatic matching of gateway settlements and bank credits to student receipts, with exceptions raised the day they occur.

Signals it reads

  • Gateway settlement files and their batch references
  • Bank credits and cheque clearance
  • Receipts issued against each transaction
  • Refund and chargeback events

What the engine computes

  • Settlement batches matched to receipts by reference, not by eye
  • Gateway charges booked separately so net and gross stay distinct
  • Failed-but-debited payments flagged the same day rather than at audit
  • Refunds routed through approval and written back to the ledger

Decisions it drives

  • Which transactions need a human look today
  • Whether a parent’s failed payment needs a refund or a retry
  • What the true net collection is, after charges

Gateway-aware

Settlement batches, charges and T+2 timing modelled properly — so gross collection and net credit are never confused for each other.

Exceptions, same day

Failed-but-debited, duplicate payment, short credit — each raised as a case with the parent, the amount and the reference attached.

Cheque lifecycle

Deposited → cleared → bounced, each with its own state. A bounced cheque reopens the due and notifies the parent automatically.

Nightly

Reconciliation run · vs a month-end matching exercise

<0.5%

Transactions needing manual matching after the automatic pass

04Payroll · Expenses

Money out, held to the same standard as money in.

Schools measure fee collection closely and expenses barely at all. Salaries are computed in a spreadsheet that one person owns, vendor bills are approved over WhatsApp, petty cash is a drawer, and the expense side of the year is assembled from memory when the auditor asks. The surplus a school thinks it has is usually a number missing half its costs.

Edullent runs the outflow with the same discipline as the inflow. Payroll is computed from attendance and the salary structure, statutory deductions are applied, vendor bills carry an approval chain, and every expense sits under a budget head with the bill attached. The surplus becomes a fact.

How it works

Payroll computed from attendance and structure, and expenses recorded against budget heads with approvals and documents attached.

Signals it reads

  • Staff attendance, leave and salary structure
  • Statutory rules for PF, ESI and TDS
  • Vendor invoices and purchase approvals
  • Budget heads and their allocations

What the engine computes

  • Salary computed from recorded attendance, not re-keyed each month
  • Deductions applied by rule and carried into the payslip
  • Every expense tied to a budget head with the document attached
  • Approval chain enforced before payment, not reconstructed after

Decisions it drives

  • Whether payroll is ready to release this month
  • Which heads are running ahead of their allocation
  • Which vendor bills to clear this week, and which to hold

Payroll from attendance

Salary structure × recorded attendance × statutory rules — computed, not typed. Payslips publish to staff without a second file.

Bills with a trail

Raised → approved → paid, each stamped with who and when, each carrying the scanned bill. WhatsApp approvals leave the process.

Budget vs actual

Every head shows allocated, spent and remaining as the year runs — so an overrun is caught in month four, not in the audit.

1 source

Payroll, expenses and fee collection in one book · vs three spreadsheets and a drawer

Month 4

Typical point a budget overrun surfaces · vs year-end in the manual cycle

05Audit · Compliance

Every rupee has a receipt, an author and a timestamp.

The audit season tells a school the truth about its records. Entries have been edited with no history, a concession was given by someone who cannot be identified, a receipt book has a gap, and the explanation is always the same sentence: that is how we have always done it. The finance officer spends three weeks reconstructing a year.

Edullent makes the record immutable by default. Nothing is edited silently — a correction is a reversing entry with a reason and an author. Concessions need approval at the level the policy sets. The audit stops being an excavation and becomes an export.

How it works

An append-only financial record where corrections are reversing entries, and every concession or waiver carries its approver.

Signals it reads

  • Every ledger entry, with author and timestamp
  • Concessions, waivers and write-offs
  • Approval levels set by school policy
  • Statutory report requirements

What the engine computes

  • Entries never overwritten — corrections posted as reversals with a reason
  • Concessions blocked until approved at the level the policy requires
  • Receipt series continuous, with cancellations recorded rather than removed
  • Statutory and management reports generated from the same record

Decisions it drives

  • Whether a concession is within policy before it is granted
  • Who to ask about an entry, without guessing
  • What to hand the auditor, without reconstructing a year

Append-only ledger

No silent edits. A correction is a reversing entry with a reason and an author — the history survives the fix.

Approval by policy

Concession, waiver, write-off and refund each need the approval level the school sets. The limit is enforced, not remembered.

Audit export

Day book, ledger, receipt register and head-wise summary export for any date range — in the form an auditor asks for.

3 weeks → 1 day

Typical audit-preparation effort once the record is the system

100% attributable

Financial entries carrying an author and a timestamp

06Forecast · Cashflow

The salary month you can see coming in August.

A school’s money arrives in three or four bursts a year and leaves in twelve equal instalments. Every finance officer knows the squeeze months by feel, and every year one of them arrives worse than expected — a term collected slower, an admission cycle softer, a vendor payment landing in the same week as salaries. The response is a scramble, because the warning came in the same week as the problem.

Edullent projects the year forward from what is actually happening. Expected collection from the fee roll, observed collection velocity, admission and withdrawal movement, and the committed outflow calendar combine into a month-by-month cashflow view. The squeeze month shows up while there is still room to act on it.

How it works

A forward cashflow projection built from the fee roll, observed collection velocity and the committed outflow calendar.

Signals it reads

  • Expected fee income per term from the fee roll
  • Observed collection velocity against that expectation
  • Admission, withdrawal and transfer movement
  • Committed outflows — payroll, vendors, loans

What the engine computes

  • Projection built from this year’s behaviour, not last year’s total
  • Collection curve applied per term rather than assumed as a single date
  • Inflow and outflow placed on the same monthly timeline
  • Branch-wise view for groups, consolidated view for the owner

Decisions it drives

  • Which month will be tight, with months of notice
  • Whether a capital plan is safe to start this quarter
  • Where to pull collection forward instead of borrowing

Month-by-month view

Projected inflow against committed outflow for the full year — the gap month is visible in August, not discovered in December.

Velocity-based

Built from how this term is actually collecting, not from last year’s closing total. The forecast moves as the term moves.

Branch and group

Each branch’s cashflow stands alone and rolls up. A group owner sees which branch funds the others, and by how much.

4 months

Median notice before a projected shortfall month

Per branch

Cashflow modelled individually, then consolidated for the group

Tomorrow's finance office
won't assemble the number. It'll act on it.

Edullent ships the live collection ledger, the ageing-based dues engine, nightly reconciliation, payroll and budget control, the append-only audit record and the forward cashflow view — so the finance desk spends its month deciding rather than reconciling.