The full school-fee cycle, end to end.
Not a spreadsheet replacement — a revenue operations platform, from setting the fee schedule to knowing the money actually landed.
Set fees once, apply them everywhere.
Define tuition and levies per class and per term. Every student in that class inherits the right structure automatically — no re-entering the same numbers for 40 students one at a time.
- ✓Per-term, per-class fee items (tuition, levies, PTA dues, etc.)
- ✓Changes to a class's structure apply to every student in it
- ✓Historical terms stay untouched once invoiced
A card terminal for the front desk.
Some parents want to pay in person — at the desk, on open day, at an event. A card terminal plugs that gap: take the payment by card, and it lands against the right student and invoice automatically, settling to the school's own account like every other naira.
- ✓Take card payments at the school, not just by transfer
- ✓Every charge matched to the right student and invoice
- ✓Settles to the school's own account — we never hold the money
The hard-to-see decisions that make this work.
Software for money and school records has to be boring in the right way. Here's some of the thinking behind it.
Batched by design, not by accident
Bulk imports and account provisioning run in small chunks with progress feedback, specifically so onboarding a 300+ student school doesn't hit a server timeout. We load-tested this with a real 400-student import.
Safe to walk away from
If an admin navigates away mid-import, the background work stops cleanly instead of silently continuing or corrupting data — a real bug we found and fixed during our own testing.
Credentials encrypted at rest
Every school's own payment provider keys are stored encrypted (AES-256-GCM), never in plaintext, and never exposed to the browser.
Provider-agnostic by architecture
Payment and messaging providers sit behind stable internal interfaces, so swapping or adding a provider later doesn't mean rewriting business logic.
Tested before it costs money
Our messaging pipeline has a full mock mode — every part of the compose-send-log flow is verified end to end before we spend a naira or need compliance sign-off to go live.
Designed around Nigerian data law
Data handling is built around the NDPA — schools stay the data controller for their students' information, and we act strictly as a processor on their instruction.
Built to connect with what you already use.
Trusted payment and messaging providers, behind interfaces we control.
Every feature above works together, automatically.
No piecing it together yourself — fees, invoicing, payments and reminders are already connected. See it on your own students, not a demo.
Request accessOr email us directly at support@fees101.com