Education · Reference build
A full school group ERP, built to show that fees and accounts can share one ledger
Reference build, not a client deployment
We built this in our own environment to test the design, so the figures below come from seeded data rather than a real school's records.
By Asif Mulani, who built Frappe Sheets · Published
In numbers
Figures from the build.
- Students seeded
- ~3,500
- Students seeded
- Attendance rows
- 68,740
- Attendance rows
- Timetable periods
- 8,580
- Timetable periods
- Database for fees and the ledger
- 1
- Database for fees and the ledger
Outcome
Campus profit and loss, receivables ageing and procurement all sit in the same database as each child's timetable.
The situation
School ERPs in this market collect fees and then push them to a separate accounting package, so the school's finance team works in one system while the books live in another.
What we did
- 01Billed a complete fee cycle that posted into the same ledger as procurement and payroll
- 02Seeded nine campuses with roughly 3,500 students and a full year of timetables and attendance
- 03Built a parent and teacher app, where a teacher marks attendance and the parent sees the attendance percentage update
One more thing we did
- Listed what it doesn't do: no app store listing, no push notifications, no GPS and no biometrics
Stack
ERPNext- Frappe Education
Frappe HR
Frappe CRM- Custom PWA
Related services and work.
- ERPNext implementationAccounts, stock, buying and selling, with your setup kept in code.
- ERP discovery and blueprintA paid, signed requirements document you can take to any implementer.
- School ERP and admissions CRMWhat we build for school groups, from enquiry capture to fees on the ledger.
- Admissions CRM for a Nine-Campus School GroupK-12 school group, nine campuses
- SEO Audit of a Multi-Campus Education GroupMulti-campus education group
Let's start with a call.
Thirty minutes, free of charge, and you won't sit through a sales deck.