WhatsApp
Tecifo Solutions logo: orange hexagon cube with blue hexagon dotsTecifo.Book a call
← All work
ERPprivate client

School ERP on Frappe

Custom school management system built on Frappe, ERPNext and HRMS covering the full student and staff lifecycle.

Sector
Education
Engagement
Build — ERP implementation
Timeline
May 2024 → Feb 2025
Team
1 Frappe engineer, 1 integration engineer
01 — The problem

A 2,400-student school group ran admissions, fees, attendance and payroll in four systems that never agreed.

Admissions lived in spreadsheets, fees in accounting software, attendance in a biometric device's own database, and payroll with an external bookkeeper. A single student existed as four records with four spellings, and reconciling fee arrears against enrolment took the finance team most of a week each term.

Off-the-shelf school platforms had been evaluated twice and rejected both times: none matched the group's fee structures — sibling discounts, staggered instalments, scholarship categories — and the workarounds required were worse than the spreadsheets.

02 — How we solved it

What we built, and why in that order

01
Frappe as the foundation
ERPNext and HRMS gave us accounting, payroll and permissions as solved problems, leaving the school-specific logic as the only thing to build. No vendor lock on the data model.
02
Custom DocTypes for the real rules
Admissions, enrolment, fee plans, instalments, discounts and scholarships were modelled as the school actually operates them, with one student record all four former systems now point at.
03
Biometric attendance integration
The existing devices push directly into attendance records for students and staff, feeding both parent notifications and payroll instead of sitting in a separate database.
04
Reports the leadership asked for
Arrears by class, collection against target, attendance trends and staff cost per campus — built as ERPNext reports the administration runs itself.
StackFrappeERPNextHRMSPythonMariaDB
Outcome
4 → 1
Systems of record
1 wk → 20 min
Termly fee reconciliation
2,400
Student records migrated and deduplicated
0
Payroll runs outsourced since go-live
The first term-end where nothing had to be reconciled by hand felt like a mistake. It wasn't.
Group finance manager, education client
03 — Where they are now

The group has been running on the system for over a year and has added a campus on it.

Our role: ERP customization

Fee collection is tracked against target continuously rather than reconstructed at term end, and arrears follow-up starts from a report instead of a search. Payroll runs in-house on HRMS with attendance flowing straight in.

A third campus was onboarded in 2026 as configuration rather than a project, which was the point of building on Frappe. The school's own administrator now handles fee-plan changes and new report requests; we are retained for upgrades and the occasional custom DocType.

Next case studyEnergy Monitoring SystemIoTSimilar problem?Start a projectinfo@tecifo.com

Have something that needs to ship?

Scope agreed in writing, architecture first, weekly increments you can review. Start with a 30-minute call or send the brief.