SchoolLedger
The whole school. One connected system.
Business systems
The problem
A school is several connected organisations at once: an educational setting, a finance operation and a network of families. A person may be a parent, staff member and donor; a household may have several children but one billing contact. Tuition agreements, payments and access permissions have to follow those relationships consistently.
The difficulty is keeping operational changes aligned with financial records across legal entities, while giving the office, families and transport staff different views of the same underlying information.
The solution
SchoolLedger models people, households, enrolments and billing relationships together, connecting the school day to tuition, donations, payment allocation and double-entry accounting. Separate office, family and driver experiences expose the information each role needs.
Important rules sit in the database as well as the interface, including access boundaries and protections against duplicate billing or bookings. Hebrew and Gregorian dates run through the same workflows. AI-assisted changes are recorded and undoable, so convenience does not remove the trail of what changed.
The decisions behind it
- Relationships before screens
- A household, a student and a payer are related records with different responsibilities. The data model keeps those roles connected without treating them as interchangeable.
- Operations meet accounting
- A usable office screen must still preserve allocations, accounting entries and legal-entity boundaries. Financial rules cannot depend only on what a form allows.
- Different people, different access
- Families, office staff and drivers work from the same platform through distinct views and permissions.
- Student records, enrolment and attendance
- Tuition, donations and multi-entity accounting
- Family portal, transport and staff workflows