Bill the monthyou actually had.
ceed is school administration for preschools, early learning centres and aftercare programmes. Aftercare sessions and the daily register feed billing directly, so the invoice matches what actually happened this month, not a spreadsheet rebuilt from memory at month end.
Every school gets its own isolated workspace. No school can see another's data.
Aftercare sessions
4 free sessions this month
Logging On invoice
- Mon 2Not logged Included
- Wed 4Not logged Included
- Thu 5Not logged Included
- Mon 9Not logged Included
- Wed 11Not loggedBillable
What your school stops doing
Chasing paper registers. Re-typing invoices. Rebuilding a month of aftercare from memory. ceed records each thing once, where it happens, and uses it everywhere it's needed.
Billing and aftercare
The register and aftercare sign-ins feed billing directly, so the month you invoice is the month that happened.
A daily register that locks
No more register anyone can rewrite three weeks later. Staff mark children in as they arrive; once the register is saved, the day locks, and any correction records who changed what, from what, to what, and when.
Aftercare sessions, billed automatically
Set each child’s free-session allowance. Once it’s used, the next session is flagged billable automatically, and it’s on the invoice at month end without anyone reconstructing it by hand.
Billing and invoicing
Run the month’s billing in one pass. Invoices are generated from what the register and aftercare log actually show, and you can track what’s been paid.
Bank reconciliation
Import a bank statement and match payments to invoices, instead of ticking them off against a printout.
Also included
Rounding out the day-to-day admin.
Digital sign-in and sign-out
Children are signed in and out electronically at the gate instead of on a clipboard, with a time against each.
Incident reports
An educator records what happened, when, where, who was involved, and the severity, timestamped and permanent, ready to export for an inspection.
Child records
Allergies, medical conditions, medication and emergency contacts surface on the register and the incident screen, not three clicks deep in an admin area.
Staff attendance and leave
Staff check in and out, and request leave for approval. Colleagues can see who’s away without seeing why.
Guardians and documents
Guardian details and each child’s documents live on the child’s record, not across a filing cabinet and an inbox.
Purchase requests
Staff ask for what their classroom needs. The principal works through one list instead of a dozen messages.
When someone asks what happened on a Tuesday in March, there’s an answer. The same one it was in March.
Everything that matters is recorded once, at the moment it happens, by the person who was there. After that it can’t quietly change. When a guardian queries an invoice, or you’re reconciling the books at month end, you open the record, and it says what it said on the day.
Room 2, Tuesday 10 March
Read only
- 07:41
Sign-in
Child A signed in at the gate by a guardian.
- 07:55
Staff
Two educators checked in for the day.
- 08:05
Register
Child B marked present by the class teacher.
- 11:30
Locked
Register saved. The day is locked.
- 15:45
Aftercare
Child C signed in for an ad-hoc afternoon session. The month’s free allowance is now used up.
- 31 Mar
14:06Override, added to the record
Child C’s sessionIncludedchanged toBillable
Changed by the admin doing March’s billing: the free allowance was already used that month. The 15:45 entry stays in the record exactly as it was, and the correction flows into the invoice.
Attendance locks
Once the register is saved, the day is closed. A correction needs an explicit override that records who changed what, from which value to which, and when.
Corrections are logged
A correction to the register or an aftercare session doesn’t replace what was there. It’s added next to it, with a name and a time, and the invoice it feeds forward reflects the change.
Billing follows the record
Aftercare sessions and the daily register feed invoicing directly. A session that goes over a child’s free allowance becomes a billable line automatically, not something rebuilt by hand at month end.
Your school’s data is yours alone
Every school on ceed has its own isolated workspace. No other school can see your children, your staff or your accounts.
Built for POPIA-conscious handling of children’s data
Access is scoped by role, so each person sees what their work needs: a teacher can see that a colleague is on leave without seeing why.
Running more than one centre?
ceed works the same way at every site. The register, the gate, incident reports and billing follow one process wherever your staff are, so your standards don’t depend on which centre someone happens to work at.
One way of working
Every centre records attendance, incidents and payments the same way, so every site can be held to the same standard.
One platform, not a patchwork
No separate spreadsheet, paper file and group chat at each site. Opening another centre doesn’t mean choosing another set of tools.
Staff don’t start over
Someone who knows ceed at one centre already knows it at the next, whether they’ve moved for good or are covering for a week.
Off the clipboard.On the record.
See the register lock, an aftercare session get flagged automatically, and a month's invoices go out without anyone reconstructing anything, with your own rooms and fees in mind.