Databus Logo
Blog Login →
ML Propensity-to-Pay scoring · RFM-ST features · Probabilistic forecasts with confidence intervals

School Fee Prediction Software for Indian Operations VPs & Finance Committees

Your CA tells you about defaulters in April. You need to know in October.

ML-based Propensity-to-Pay (PTP) scoring per parent using established RFM-ST behavioral features. Random Forest + XGBoost + Bayesian Neural Networks. Probabilistic cash flow forecasts with explicit confidence intervals — not false-precision accuracy claims.

Identifies at-risk fee defaulters 60-90 days before due date. Hands off flagged parents to the Auto Fee Reminders execution layer. Built for Indian Operations VPs and Finance Committees who plan budgets months ahead — and currently work with software that only reports what already happened.

PTP
0-100 score per parent
RFM-ST
5 behavioral features
60-90 d
Early defaulter warning
12 mo
Minimum training data

Four hidden costs of backward-looking accounting

Why traditional school ERP can't tell you what's coming next month.

📉

Backward-looking accounting

Standard ERPs report transactions after they happen. By the time the dashboard shows ₹12 lakh short of expected collection, the cash flow gap has already opened. Operations VPs need 60-90 day forward visibility, not a perfectly formatted post-mortem in April.

📨

One-size-fits-all dunning

Without prediction, every parent gets the same reminder cycle — including the family that has paid on the 1st of every month for 9 years. They feel hounded. They start complaining about the school being aggressive. Meanwhile the actual chronic defaulters get the same nudge that annoys good parents.

📊

Budgets on guess revenue

Principal approves a ₹20 lakh science lab upgrade in September assuming Q2 collections will cover it. December arrives. Collections fell short. The lab order is half-paid, the vendor wants the balance, and there's no plan B. The whole "plan" was a gut estimate dressed up as a budget.

🚪

Reactive inter-branch transfers

For Trusts running multiple schools, Branch B's payroll-day cash shortage is discovered 5 days before salary day. Emergency inter-branch transfer. Bank fees + frantic phone calls + Trustee panic. All preventable with a forecast that showed the gap coming 60 days earlier.

Propensity-to-Pay · RFM-ST framework · Bashar et al. 2023

Established academic ML framework. Not magic.

The platform applies the Propensity-to-Pay (PTP) classification framework from machine learning literature (Bashar et al. 2023, Intelligent Systems with Applications, Elsevier) to school fee payment prediction. Predictions are probabilistic with explicit confidence intervals — not false-precision accuracy claims.

Features · RFM-ST

5 behavioral features per parent

Recency (days since last payment), Frequency (payments per academic year), Monetary (cumulative paid amount), S Customer Relationship Duration (years enrolled), T Average Transaction Interval (gap between invoice and payment). Plus school-specific: payment modality, sibling status, attendance correlation.

Models · ML algorithms

Multiple classifier variants

Logistic Regression (baseline), Random Forest (production default), XGBoost (higher accuracy variant), Bayesian Neural Networks (explicit uncertainty quantification). The Bayesian variant flags when it doesn't have enough data — instead of overconfidently predicting.

Output · Probabilistic

PTP score + confidence band

Per parent: PTP score 0-100 with confidence interval (e.g., "78 ± 5 — Medium PTP") + expected payment date range. Per institution: monthly cash flow forecast with confidence band (e.g., "July: ₹45-52 lakhs with 80% confidence"). Honest probabilistic framing, not false certainty.

PTP segments — who gets what reminder treatment

  • High80-100: Pays on time consistently. Single polite reminder. Preserves relationship.
  • Medium40-79: Often 10-15 days late. Enters structured 3-stage reminder cycle.
  • Low0-39: Chronic defaulter. Flagged for immediate Accounts Head call to renegotiate.

Reference: Bashar M.A. et al. "Machine learning for predicting propensity-to-pay energy bills." Intelligent Systems with Applications 17 (2023), 200176. Elsevier. RFM framework: classic customer relationship management model extended to RFM-ST per recent ML research on customer behavior prediction.

Cash Flow Forecasting

Probabilistic forecasts, not single-point estimates that pretend to be certain.

The platform produces revenue projections with explicit confidence bands — because every cash flow forecast is inherently uncertain, and pretending otherwise leads to broken budgets. A typical July forecast: "Expected collection ₹45-52 lakhs with 80% confidence; central estimate ₹48 lakhs."

  • 30 / 60 / 90 day rolling projections: Three concurrent forecast horizons updated weekly as new payment data arrives.
  • Deficit early warning: Compares projected inflows against committed fixed expenses (payroll + rent + AMC commitments) pulled from Finance Management. Flags gaps 30-90 days ahead.
  • Seasonal velocity heatmap: Year-over-year comparison of weekly collection velocity. Identifies if this November is running 12% slower than last November.
  • Multi-branch macro forecast: For educational trusts, per-branch predictions aggregated into Trust-level cash flow view with surplus/deficit highlighting per campus.
SchoolDeck cash flow forecast dashboard with confidence intervals and PTP segments
"I am the Operations Vice Principal at a 1,400-student CBSE school in Bengaluru. My job sits between the academic team and the Finance Committee — I am the one who has to explain to the Trust why we approved a ₹35 lakh smart classroom project in August and then ran short of payroll cash in December. For three years I had no good answer. Our existing ERP showed me what happened, never what was coming. When SchoolDeck's prediction module went live, the first thing I noticed was the honesty. It does not tell me 'we will collect ₹48 lakhs in November' — it tells me '₹44-51 lakhs with 80% confidence, central estimate ₹47.2 lakhs.' The confidence interval was the trust-building feature, not a weakness. The PTP segmentation also stopped the parent complaints. Our 412 High PTP parents were getting the same three reminders as our 47 chronic defaulters — and the good parents were getting annoyed. Now High PTP families get one polite nudge; Medium PTP enter the structured cycle; Low PTP are flagged for me to personally call. Complaints down. Recovery up. And last December I went to the Finance Committee with a 90-day forecast showing the gap I needed to close — not an apology after the fact."
K
Mrs. Kavitha Subramanian
Vice Principal Operations · CBSE School, Bengaluru · 1,400 students · 412 High PTP / 941 Medium / 47 Low · Migrated November 2024

The structural cash flow gap in Indian schools

Running a school requires a delicate balancing act of capital. Unlike retail businesses that collect revenue at the moment of service delivery, schools operate on a deferred, cyclical revenue model. You provide educational services daily, but you only collect fees quarterly or semi-annually. Meanwhile, your largest operational expenditures — teacher salaries, rent, transport fuel, vendor AMC contracts — are rigidly fixed and due every 30 days.

This structural mismatch creates a chronic cash flow gap. A school projecting ₹1 crore in term fees that collects only ₹60 lakhs by the due date because 40% of parents delayed payment faces severe liquidity stress — exactly when payroll is due. Traditional accounting methods cannot solve this because they only report on the past. By the time the dashboard shows a shortfall, the shortfall has already happened.

What school fee prediction software actually does

School fee prediction software represents the evolution of educational ERP from record-keeping databases into predictive financial tools. It is the analytical layer that sits on top of the core Fee Management module and applies machine learning to forecast future revenue streams.

Instead of an accountant guessing how much money will arrive next month based on gut feel, the Predictive AI analyzes thousands of historical payment events to generate a probability distribution. It transitions the school's financial posture from reactive ("Who hasn't paid yet?") to proactive ("Who is likely to be late next month, and how do we plan for it?").

Predict vs Act vs Collect — three modules, three jobs

The SchoolDeck fee cluster contains three closely-related but functionally distinct modules. Getting the boundary right matters:

  • Fee Management — CORE COLLECTION: Invoice generation, UPI/card/net banking payment processing, receipt generation, fee structure configuration. Answers: "How do we generate and accept fee payments?"
  • Fee Prediction (this page) — PREDICTIVE ANALYTICS: Identifies which parents are likely to be late before due date. Generates institution-wide cash flow forecasts with confidence intervals. Segments parents by PTP score. Takes no direct action on flagged parents. Answers: "Who is going to be late and how much will we collect?"
  • Auto Fee Reminders — EXECUTION: Receives PTP scores from this prediction module via API. Runs the actual 3-stage reminder workflow (Pre-Due Nudge + Due Date Alert + Overdue Escalation) per the parent's PTP segment. Answers: "What do we actually do about flagged defaulters?"

Clean separation matters because using the same logic for predicting AND executing tends to make the reminder workflow too generic. Without prediction-driven segmentation, every parent gets the same nudge — including the family that has paid on the 1st of every month for 9 years. They feel hounded. With prediction-driven segmentation, High PTP parents get a single polite reminder; Low PTP parents get immediate human escalation.

The Propensity-to-Pay (PTP) framework explained

Propensity-to-Pay is an established academic machine learning framework formalised in Bashar M.A. et al. "Machine learning for predicting propensity-to-pay energy bills" (Intelligent Systems with Applications 17, 2023, Elsevier). The framework was developed for energy utility bill prediction but generalises directly to any subscription/cyclical billing context including school fees.

The core insight: payment behavior is more predictable than it appears, but only when you analyze it as a multi-feature classification problem rather than guessing from total outstanding amounts. The same Manager who has the same job has been paying his daughter's school fees on the 28th of every month for 4 years. Last quarter he paid on the 11th. Next quarter, statistically, he is highly likely to pay around the 28th again. Each parent has a behavioral signature that, when captured as features and fed into a classification model, produces a meaningful probability prediction.

The framework explicitly emphasises prediction uncertainty — the model produces probability distributions with confidence intervals, not point estimates dressed up as certainty. This is why the platform's outputs include phrases like "78 ± 5" rather than "78%". The ± is the honesty.

Feature engineering — what the model actually reads

Two categories of features feed the classifier:

RFM-ST framework features (extended from classic RFM in customer relationship management research):

  • R — Recency: Days since the parent's last fee payment.
  • F — Frequency: Payments per academic year, normalised by enrolment duration.
  • M — Monetary: Cumulative paid amount across all years.
  • S — Customer Relationship Duration: Years as parent of enrolled child.
  • T — Average Transaction Interval: Typical gap between invoice issue and payment received.

School-specific features extending the framework:

  • Payment modality: UPI / auto-debit users typically show different payment velocity patterns than cheque / cash users. The pattern is captured as a feature in the classifier — not asserted as certainty.
  • Sibling enrolment status: Families with multiple children often show different payment patterns than single-child families.
  • Prior penalty / late fine history: Past late fines are a feature, weighted by recency.
  • Attendance correlation: Declining student attendance sometimes precedes financial hardship for the family.
  • Seasonal demographic indicators: For schools in agricultural belts, post-harvest liquidity cycles are captured as seasonal features.
  • Historical concession / scholarship status: Captured as a feature, not as a deterministic factor.

Predictions explicitly exclude sensitive attributes: religion, caste, political affiliation are never used as features. The model focuses on observable payment behavior, not demographic profiling.

PTP segmentation — three groups, three treatments

The model assigns each family a PTP score from 0-100 with confidence interval, then maps to three risk segments:

  • High PTP (80-100): These parents have paid consistently on time. Treatment: single polite reminder 5 days before due date. No follow-up unless the actual payment misses by 7+ days. Preserves the school-parent relationship for the families that don't need pressuring.
  • Medium PTP (40-79): These parents often pay 10-15 days late but eventually pay. Treatment: structured 3-stage reminder cycle (Pre-Due Nudge 5 days out + Due Date Alert + Overdue Escalation 7 days late). Most of the school's reminder volume goes to this segment.
  • Low PTP (0-39): Chronic defaulters. Treatment: immediate human escalation. The Accounts Head calls the family directly to discuss payment plan options before the debt becomes unrecoverable. Automated reminders are paused because they don't work and are perceived as harassment.

The platform supports "compassionate hold" — Operations VP can manually pause aggressive reminders for a family in known temporary hardship (job loss, medical emergency, family crisis). The model respects the hold for 60 days while preserving the analytical record.

Handoff to Auto Fee Reminders — predictions become actions

This module produces predictions only — it does not send any reminders, make any calls, or take any direct action on parents. Predictions flow via API into the Auto Fee Reminders execution layer, which:

  • Routes each parent into their PTP-segment workflow (High → single polite nudge; Medium → 3-stage cycle; Low → human escalation queue).
  • Consolidates Family ID — siblings in the same family receive one consolidated reminder, not three duplicates.
  • Handles cheque bounce workflows automatically.
  • Runs the WhatsApp / SMS / app push reminder economics (utility templates at ~₹0.125/message in India under Meta's per-message pricing model).

The clean separation is operationally important. Operations VP sees what the model predicts; Accountant sees what the reminder workflow is doing. Neither sees the other's complexity. Both see the unified outcome — which families are flagged and how the school is responding.

Forecasting and institutional budget planning

Budgeting without accurate forecasting is wishful thinking. A school Principal might draft a budget allocating ₹20 lakhs for a new computer lab in September, assuming Q2 fees will cover it. However, if the Prediction Engine forecasts that Q2 collections will likely fall short by 15% due to historical pattern + identified PTP-segment risks, the dashboard surfaces this BEFORE the Principal signs the lab vendor's PO.

The integration with Finance Management creates a feedback loop:

  • Finance Management owns the budget allocation per department.
  • Fee Prediction (this module) projects when the cash to fund those allocations will actually arrive.
  • When committed outflows from Finance Management exceed projected inflows from prediction, the deficit early warning fires.
  • Operations VP can defer a CapEx commitment, accelerate specific PTP-flagged families via /auto-due-reminders/, or activate a credit line — well before the salary day arrives.

Multi-branch macro forecasting for educational trusts

For educational trusts operating multiple campuses via the Multi-Branch Module, predicting cash flow becomes a multi-entity problem. One branch might be highly profitable; a newer branch might be burning cash. A 2-school trust can plan around this if predictions are visible 60-90 days ahead; a 4-school trust can't reliably plan around it without macro forecasting.

The Trustee Dashboard aggregates per-branch predictions into a consolidated Trust-level macro forecast. Example output: "Pune branch projected ₹2.4-2.7 crore surplus in Q2; Aurangabad branch projected ₹40-55 lakh deficit; net Trust position +₹1.85-2.30 crore. Confidence highest for Pune (4-year data), medium for Aurangabad (recently opened — wider band)."

The macro forecast also identifies which branch's prediction has highest uncertainty (less historical data, recently opened, demographic instability) so trustees know which projections to treat as soft estimates vs hard plans. Inter-branch fund transfers can be planned proactively rather than discovered as emergencies.

Legacy ERP vs SchoolDeck Fee Prediction

Capability Legacy school ERP SchoolDeck Fee Prediction
Revenue outlook Backward-looking (reports past) Forward-looking (30-90 day projections)
Defaulter identification timing After the due date passes 60-90 days before due date
Parent segmentation One reminder cycle for all PTP segments (High/Medium/Low)
Prediction framework None / accountant gut feel RFM-ST + ML classifiers (Bashar 2023)
Uncertainty handling Single-point estimates only Confidence intervals + Bayesian variants
Deficit early warning None — discovered post-shortfall 30-90 day advance alert with magnitude
Multi-branch macro forecast Manual consolidation per branch Auto Trust-level cash flow view
Handoff to reminder workflow Same logic for all parents PTP-segment API to /auto-due-reminders/

Frequently asked questions

What Operations VPs ask before switching.

How is Fee Prediction different from Auto Fee Reminders and Fee Management?

+

Three modules, three jobs. Fee Management owns CORE COLLECTION — invoices, UPI/card/net banking, receipts. Fee Prediction (this page) owns PREDICTIVE ANALYTICS — identifies who will be late before due date, generates cash flow forecasts with confidence intervals, segments parents by PTP. Takes no direct action. Auto Fee Reminders owns EXECUTION — receives PTP scores via API and runs the 3-stage reminder workflow per segment. Clean separation: predict here, act there. The separation matters because it lets the reminder workflow be PTP-segment aware — High PTP parents get one polite nudge; Low PTP parents get human escalation.

What is Propensity-to-Pay (PTP) scoring and how is it calculated?

+

Propensity-to-Pay is an established academic ML framework (Bashar et al. 2023, Intelligent Systems with Applications, Elsevier) for predicting the probability that a customer will pay an outstanding bill on time. Each parent gets a dynamic PTP score 0-100 calculated from RFM-ST behavioral features: Recency (days since last payment), Frequency (payments per year), Monetary (cumulative paid), S (years enrolled), T (average gap between invoice and payment). Plus school-specific features: payment modality, sibling status, attendance correlation, prior fines. Classifier algorithms: Random Forest (production baseline), XGBoost (higher accuracy variant), Bayesian Neural Networks (for explicit uncertainty quantification). Output: PTP score + confidence interval ("78 ± 5 — Medium PTP").

How accurate are the predictions?

+

Honest answer: the model produces probability distributions with explicit confidence intervals — not false-precision percentage accuracy claims. After 12 months historical training, a typical cash flow forecast generates a confidence band like "July collection expected ₹45-52 lakhs with 80% confidence" rather than a single point estimate. PTP scores per parent come with their own confidence interval ("78 ± 5"). Accuracy improves with more historical data — 24-36 months produces tighter bands. Multiple algorithm variants available: Random Forest (production default), XGBoost (higher accuracy), Bayesian Neural Networks (explicit uncertainty quantification — model flags when it doesn't have enough data rather than overconfidently predicting).

What features does the prediction model use?

+

Two categories. RFM-ST framework (extended from classic CRM RFM): Recency (days since last payment), Frequency (payments/year), Monetary (cumulative paid), Customer Relationship Duration (years enrolled), Average Transaction Interval (invoice-to-payment gap). School-specific features: payment modality (UPI/auto-debit users typically show different velocity than cheque users — captured as feature, not asserted as certainty), sibling enrolment status, prior fine history, attendance correlation, seasonal demographic indicators (agricultural belt schools have post-harvest cycles), concession/scholarship status. Explicitly excluded: religion, caste, political affiliation — never used as features. Model focuses on observable payment behavior, not demographic profiling.

What if a parent's situation changes — does the model adapt?

+

Yes — and this matters. A parent going through temporary job loss might have always been High PTP but suddenly becomes Medium PTP. The model recalculates monthly as new payment data arrives. A score is a snapshot of current signals, not a permanent label. The platform also exposes per-feature contribution to each prediction — Operations VP can see exactly which features moved a parent from High to Medium ("two months later than usual payment + recent younger sibling enrolment"). Operations VP can also manually flag "compassionate hold" (known hardship — pause aggressive reminders for 60 days) which the model respects until manually lifted. Designed to support humans making nuanced decisions, not automate parents into rigid debt collection categories.

Can it predict multi-branch consolidated cash flow for Trusts?

+

Yes. Per-branch predictions aggregate into consolidated Trust-level macro forecast. Example: "Pune branch projected ₹2.4-2.7 cr surplus Q2; Aurangabad ₹40-55 L deficit; net Trust position +₹1.85-2.30 cr. Confidence highest for Pune (4-year data), medium for Aurangabad (recently opened — wider band)." Trust Treasurer can plan inter-branch fund transfers proactively rather than discovering Branch B is short on payroll 5 days before salary day. The macro forecast identifies which branch's prediction has highest uncertainty so trustees know which projections to treat as soft estimates vs hard plans.

How does the deficit early warning system work?

+

Compares projected fee inflows against committed fixed monthly expenses pulled from Finance Management (payroll, rent, AMC commitments). When projected inflows for a future month fall below committed outflows, the system raises early warning 30-90 days in advance with the magnitude of the gap and contributing factors. Example: "December projected inflow ₹38-42 lakhs vs committed outflow ₹47 lakhs — gap ₹5-9 lakhs driven by typical Q3 collection slowdown + 8 Low PTP families representing ₹3.2 lakhs outstanding." Operations VP can then accelerate specific PTP-flagged families via /auto-due-reminders/, defer non-critical CapEx, arrange inter-branch transfer, or activate credit line — before salary day arrives.

Can we import historical fee data from existing software?

+

Yes. Bulk CSV/Excel Import Utility handles 2-3 years historical fee transaction data from Tally / Excel / MS Office Accounting / competing ERPs. Typical import for 1,500-student school: 3-4 working days including data quality checks (deduplication, missing-field flagging, payment-mode normalisation). After import: model trains ~30 minutes; initial PTP scores per parent + first cash flow forecast within 24 hours. Predictions improve over 90 days as model observes which families pay on time vs late under your school's specific demographic — initial scores conservative (wider intervals), tightening as current-cohort data accumulates.

Does it export to Tally or our existing accounting tools?

+

Yes. Predictions typically consumed in SchoolDeck dashboard (real-time, drill-down per parent and per cohort). Platform exports forecast summaries to Excel/CSV for Finance Committee meetings, PDF for Trustee Board packs, and XML to push monthly projected revenue into Tally budget lines for budget vs actual variance analysis. PTP scores per parent exportable as anonymised CSV for sharing aggregate insights with CA or auditor.

What does deployment look like and what's the pricing?

+

Deployment: 7-10 working days end-to-end. Onboarding handles legacy data import (2-3 years historical fee transactions), model training (~30 minutes), initial PTP scoring per family, first cash flow forecast within 24 hours, dashboard configuration with RBAC (Operations VP, Finance Committee, Principal, Accountant, CA), API handoff configuration to /auto-due-reminders/ execution layer. First useful predictions immediate; tighter predictions after 90 days of current-cohort data. Pricing: bundled within standard SchoolDeck plan at ₹30 per student per month. No separate per-prediction or per-PTP-score charge. Multi-branch macro forecasting included. No additional infrastructure — model trains and runs on SchoolDeck cloud.

Fee cluster

Three modules. Three jobs. No overlap.

For Operations VPs who plan budgets months ahead

Know cash flow 60-90 days early. Plan accordingly.

ML Propensity-to-Pay scoring. RFM-ST behavioral features. Confidence intervals, not false precision. Hands off to Auto Fee Reminders for execution. Honest probabilistic forecasting.

From ₹30/student/month · 500+ Indian schools · Live in 7-10 days