School Management: Students, Classes & Tuition

Overview

• The student is in the class; somebody else pays for it. The invoice goes to the payer chosen on the enrolment - a guardian, a sponsoring company, or an adult student paying for themselves - and each line carries the child's name, so a family with three children can read one invoice and tell which lessons belong to whom.

• Classes are generated from a weekly pattern. Tuesday and Thursday at 18:00 across a term becomes twenty-four real lessons. Regenerating in week six never touches a lesson that has already happened, nor one somebody moved by hand.

• A mid-term joiner pays for the lessons that are left, counted off the real timetable rather than a fraction somebody guessed. The same number refunds a withdrawal, as a credit note against the posted invoice.

• The register closes itself. One row per student per lesson, and a lesson that is over is closed the next morning - so the absence list is true without depending on a teacher remembering a button. A register cannot be signed in advance.

• An excused absence earns the lesson back, a plain one does not, and the balance follows the correction a parent phones in the next morning. Spending a make-up lesson is an action somebody takes, never a number that quietly drifts.

• Marks that add up. Assessment weights are held to a hundred percent, and the final mark is computed on what has actually been marked - a student with 80% in the only test that has happened has 80%, not 8%.

Requirements

Odoo 18.0, Community or Enterprise. Standard apps: Invoicing (account) and Products (product). No Enterprise module is needed. Full source, OPL-1.

Getting started

1. Programmes and terms. A programme is what you teach; a term is when. Both live under School → Configuration.

2. Classrooms carry a real capacity. A class cannot outgrow its room, and no room or teacher is ever double-booked - including when a cover teacher is put on a single lesson.

3. Create a class, give it a weekly slot pattern, and generate the term. The timetable fills with real lessons you can move, cancel or cover one at a time.

4. Enrol students. Choose the payer on the enrolment. Invoice from the enrolment and the tuition is raised for the lessons that remain.

Usage

Data, privacy and limits

• A teacher never sees a fee, and nobody outside the office sees a child's details. That is an access rule on the models and on every one of the fields - date of birth, admission number, guardian list, care note - not a hidden notebook page. A notebook page hides a tab; it does not stop Contacts, select all, Export.

• This is a tuition and timetable system, not a full student information system: there is no transport, no boarding, no state reporting export.

• Marks are recorded and weighted; the module does not print certificates or transcripts.

• Everything runs inside your Odoo. No external service is called and no data leaves the database.

Troubleshooting

Regenerating a term did not create the lessons I expected. Generation never touches a lesson that has already happened or one that was moved by hand. Those are left exactly as they are, on purpose.

A student's invoice looks short. Pro rata counts the lessons that remain on the real timetable at the moment of invoicing, not a fraction of the term.

A teacher cannot see the fee fields. That is the access rule working. Fees are visible to the office roles only.

Support

Every request answered within 24 hours, setup help included, by the people who wrote the code: support@bambooforge.dev

Uninstallation

Changelog