All modules & pricing
EssentialsStaff portalStudent portalParent portal

Finance

Invoice the school's fees, collect them online, chase what is late automatically, and let every family see exactly what they owe and what they have paid.

Get startedTalk to usPay-as-you-go · deducted daily from your prepaid credit

What this module bills

  • Fee invoices issued₦5.00 per invoice · first 100 free each month
  • Fee payments recorded₦20.00 per payment · first 100 free each month
  • Fee refunds issued₦25.00 per refund · first 20 free each month

What this module is

Fee collection is the process a school cannot afford to get wrong and almost always runs on the weakest tooling it owns. The fee structure lives in a document, invoices are generated in a spreadsheet and mail-merged, payments arrive as bank transfers a bursar reconciles by eye, and the answer to "has this family paid" depends on which teller's book you look in. The cost is not only the unpaid fees — it is the hours, and the arguments with parents that neither side can settle with evidence.

School Fees & Finance puts the whole cycle on the pupil record. Fee categories are defined once per session; scholarships and discounts reduce them by rule rather than by exception; invoices are raised in bulk against the classes they apply to; families pay online and are receipted automatically. Overdue invoices are chased by the system on a daily schedule, not by whoever remembers. And every one of those events posts to a school-wide finance ledger that also carries hostel charges, store sales and equipment spend — so "what did we bill, what did we collect, what do we still owe" is one query, not four.

A reported month can also be closed: accounting periods bound where a posting may land, and the guard sits in the one funnel every module posts through — so the library, the hostel and the shop are all held to the bursary's calendar rather than to their own. The module has a workspace for the bursar and a view for everyone who is billed. Parents get invoices, online payment and a payment history; students get read-only visibility of their own account; staff — who are billed too, for staff-ward tuition and levies — get the same in their own portal. What follows walks the bursar through the whole cycle, then shows it from each of those three sides.

What you get

One fee structure, applied by rule

Categories carry a default amount, a frequency and the year groups they apply to. Setting fees is a session task, not a per-child spreadsheet formula.

Scholarships that apply themselves

A staff-ward or sibling discount can be set to apply automatically at the percentage or amount defined, drawn against a budget the school can watch. Merit and hardship awards stay manual and approved.

Invoices raised in bulk, delivered automatically

Generate a term's invoices in one run and deliver them by email and in-app to the guardians the platform already knows. Every issued invoice notifies the family without anyone addressing an envelope.

Families pay online and are receipted instantly

A parent pays from the invoice by card or transfer through the school's own Paystack account. The payment is verified, allocated and receipted without a bursar touching it.

Overdue fees chase themselves

A daily job finds invoices past their due date and dispatches reminders under the school's own rules — how many days before due, how long after, how often, and how many times before it stops.

Debt you can actually work

Outstanding balances are aged into buckets and broken down by class and by pupil, with the oldest debt and days past due on each row. Collection becomes a worked list ordered by size and age.

Corrections leave a trail

Refunds, waivers, adjustments and statement credits are requests that get approved and processed against the original payment — so a correction is evidence rather than an erased line.

One ledger across every module

Fee invoices and payments, hostel charges, store sales, staff billing, library acquisitions and equipment purchases all post to the same Transactions journal, with the module, event and counterparty on every entry — and one filter bar over the lot.

A reported month stays reported

Accounting periods bound where any module may post. Close June once it has been signed off and no library invoice, hostel charge or store sale can land in it afterwards — the check lives in the one funnel every posting goes through, so a module added next year inherits it.

Nobody leaves owing money by accident

Finance holds its own line in exit clearance, and its register lists who owes the school right now rather than only those who happen to be leaving. A payment taken at the desk clears the line, and nothing overnight quietly undoes that.

Every flow, every role

How Finance actually works

The screens below are the real application, running live on this page with sample school data — not screenshots. Each one is the same screen your team would use.

On this page

Bursar / school admin

The bursar runs the module and answers for the number at the bottom. Each screen is one job rather than a tab on someone else's: issue the bills, structure the fees behind them, chase what is unpaid, correct what was wrong, close the month when it is reported, clear the leavers, and read the whole school's money in one journal.

1

Issue the term's invoices

Invoicing is its own screen, not a tab. It answers one question — what has been billed, to whom, and what is still due on it.

Issued, paid and outstanding totals as live figures across the school, with invoice counts beside them.
Invoices per pupil with subtotal, discount, total, amount paid and amount due — and a status that distinguishes issued, partially paid and paid.
Bulk invoice generation for a term, so a session's billing is one run rather than 1,800 documents.
Bulk delivery to the guardians already on the pupil record.
A payment recorded straight from an invoice row, without leaving the screen.
2

Define the fees behind the billing

Everything on the invoicing screen is generated from this one. Fee categories are the structure that stops billing from becoming per-child data entry.

Fee categories with a code, a default amount, a frequency — one-off, termly, sessional, monthly, annual — and the year groups they apply to.
Recurring and one-off charges modelled separately, so an admission fee behaves differently from tuition.
Scholarships and aid on their own screen alongside: merit, need-based, staff ward, sibling, institutional and external awards, each as a percentage or a fixed amount.
Automatic or manual application per scholarship: a sibling discount can apply by rule, a hardship bursary stays a decision.
A budget per scholarship with the amount awarded against it and the remaining balance, so aid is affordable by design.
Awards held against the individual pupil with an approval and a validity window.
Reminder and receipting behaviour configured here too — days before due, first overdue reminder, interval, maximum reminders, and whether invoices and receipts go by email or SMS.
3

Work the debt

Chasing unpaid fees is a different job from raising them, done by different people on a different rhythm — so it is a different screen.

Outstanding balances aged into 0–30, 31–60, 61–90 and 90+ day buckets, with the aging distribution charted.
Aggregation by class and by year group, so a persistent problem in one cohort is not hidden inside a school-wide average.
A drill-through per pupil showing every open invoice and the oldest unpaid one.
Follow-up tasks assigned to a named staff member with a priority and a due date.
Promises to pay recorded against a pupil with the amount and the date promised, then tracked against what actually arrived.
4

Correct what needs correcting

Every school issues wrong invoices, takes duplicate payments and agrees waivers. The question is whether the correction is auditable. Here it is a request with a reason, an approver and an outcome.

Four distinct types: a refund of money, a waiver of a charge, an adjustment to an invoice, and a statement credit carried forward.
Each request tied to the pupil and the invoice or payment it corrects.
A status trail through pending, approved or rejected, and then processed.
A payout method recorded — statement credit, cash, bank transfer, or a refund back through the payment gateway.
Whether reversals need approval, or refund automatically, set as a school-wide policy rather than decided case by case.
5

Close the month when it is reported

Accounting periods are the windows a posting is allowed to land in. Nothing in the product bounded a backdated posting before they existed — and several modules derive a posting date from something a user typed, so a library title catalogued today with a 2019 invoice date landed in 2019 and quietly reopened a year the school had already reported.

A register a bursar reads down rather than a settings form: each row is a window, with what has already posted into it beside its dates.
Open or closed, with a reason on the close and both directions audited — closing a month too early has to be undoable, or nobody will close one at all.
The guard sits in the single funnel every module posts through, so a module added next year inherits it without knowing it exists.
A date no period covers still posts. This is a bound the school opts into, not a gate it must satisfy — otherwise a school that never built a calendar could not take a payment. The hole is reported rather than enforced.
Other modules ask before they commit: a librarian dating an acquisition into a closed month is told while the date field still has focus, and they hold no finance permissions to be told it.
Periods may not overlap, because a date covered twice gives two answers to "is this closed?".
6

Clear the leavers, and everyone else

Finance holds a line in the school-wide exit clearance, and the register behind it answers a question the product could not answer at all before: not "who is leaving and owes us" but "who owes us", today.

The live debt list — every pupil, family or employee carrying an unpaid balance right now, whether or not anybody is leaving.
A second register across the tab strip: the leavers whose exit is being held open by finance, waiting on the bursary's sign-off.
A line the system cleared can be reopened by the system when the debt returns; a line a person cleared is never silently reverted — a desk-side cash payment stands.
Reading and signing it needs finance permissions rather than an office appointment, which is what used to leave a fully-permissioned bursar looking at an empty page.
7

Read the whole school's money in one journal

Every module that moves money writes to the same append-only journal. Transactions is the only place a bursar has to look — and the filters are what used to be six separate embedded ledgers.

Fee invoices and payments, hostel charges, store sales, library acquisitions, equipment purchases and staff billing, all as entries on one journal.
Filter by module, event, direction, counterparty type and date range — and search by student, staff, vendor, description or reference.
The filter state lives in the URL, so "all outstanding debt" or "this term's refunds" is a link a bursar can bookmark or send.
Per-currency debits, credits and net for the window, with the opening balance carried in and the closing balance carried out.
CSV export of exactly what is on screen, for the accountant who works in a spreadsheet.
Manual adjustments for money no module recorded — an opening balance, a write-off, a keying error — posted with a reason and never edited, only reversed.
8

See it beside everything else

The same figures also appear in the school-wide Reports roll-up, next to attendance, results, HR and operations. That placement is the argument: a collection problem in one class is rarely only a finance problem.

Literally the same cards as the Finance module's own analytics page — one definition of "collected", not a second one that drifts.
Each card carries its own period, so a debtor list over the term can sit beside a collection rate for the week.
A layout the school can rearrange, so the board sees what that board cares about.

Ready to run your school on this?

Every screen in “Bursar / school admin” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Parents & guardians

The parent side is where the module earns its money back. Almost every collection problem is really an information problem — the family did not know, could not check, or could not pay easily. These two screens remove all three.

1

See every invoice, and pay it

A guardian lands on what is owed across all their children, with each invoice broken into the lines that make it up. And they can pay from this screen — which is the whole difference between a bill being seen and a bill being settled.

A summary across every ward, and per-ward totals underneath — one login for a family with three children.
Each invoice with its number, term, total, amount paid, amount due and due date.
Line-item detail, so "what is this ₦35,000 for" is answered on the page.
Pay online by card or transfer through the school's own gateway, with the payment verified and allocated automatically.
Download the invoice as a PDF for a sponsor or an employer.
Raise a dispute against an invoice, which the bursary sees and resolves on the record rather than by phone.
2

Keep the receipts

Payment history is the screen that ends the argument. Every payment the school has recorded against the family, with its method, its receipt number and its status.

All payments across every ward, with amount, method and date.
Receipt numbers and downloadable receipts per payment.
Status shown honestly — a transfer awaiting approval reads as pending rather than as paid.
Totals paid and pending, so a family reconciling against their bank statement can do it themselves.

See this on your own school’s data.

Every screen in “Parents & guardians” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Students

Older pupils — sixth form, and anyone whose fees they help manage — need to see their own account without going through a parent or the bursary. Their view is deliberately read-only: they can see and evidence, but they cannot pay or dispute.

1

Their own invoices

Every invoice raised against the pupil, with what each line is for and what is still due. Read-only, and complete.

Invoices with total, amount paid, amount due and due date.
Line-item detail on each invoice.
Downloadable as a PDF — the document a scholarship sponsor or a guardian abroad actually asks for.
2

Their own payment record

Every payment recorded against them, with receipts. It means the sentence "we paid that last term" is checkable by the person saying it.

Payments with amount, method, date and status.
Receipts downloadable per payment.
Read-only: paying is done by the guardian, from the parent portal.

Set this up for your team.

Every screen in “Students” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Staff

Employees are billed too — staff-ward tuition at the employee discount, levies, and anything else the school charges its own people. They get the same self-service the families get, in their own portal, so they are not queueing at the bursary as both employee and parent.

1

Their own fee invoices

Staff fee invoices are a first-class record, not a note in the ledger. An employee sees what has been raised against them, what the discount took off, and what is still due.

Invoices with subtotal, discount, total, amount paid and amount due.
Line-item detail and a downloadable PDF.
Pay online from the invoice, the same way a parent does.
2

Their own payment history

What they have paid, when, by what method, and whether it has been approved — with the receipt attached.

Ready to run your school on this?

Every screen in “Staff” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

How it connects to the rest of the platform

  • Pupils, guardians and classes come from the base platform

    Invoices are raised against the school's existing pupil records and delivered to the guardians already linked to them. There is no billing contact list to maintain, and a transfer or a leaver flows straight through.

  • Notifications ride the platform's own delivery

    Invoice issued, payment receipted and overdue reminder are dispatched through the platform's notification pipeline to the contacts on the pupil record, in-app and by email.

  • Boarding charges land on the same accountrequires Hostel Management

    Hostel fees post to the shared finance ledger as the same kind of debt as tuition, so a boarder's family sees one balance rather than two bills from one school.

  • Store sales post to the same ledgerrequires School Store

    Uniform and stationery sales are recorded against the ledger with the family as counterparty, which is what makes the "all debts" view complete rather than tuition-only.

  • Dispensed medicine can be chargedrequires Health & Clinic Management

    Where the clinic is enabled, medication dispensed to a pupil can be written onto the family's draft invoice instead of being absorbed or chased separately.

  • Equipment spend appears beside fee incomerequires Inventory Management

    Delivered purchase orders post to the same ledger as an expense against the vendor, so what the school spent sits in the same place as what it collected.

  • Staff billing uses the staff recordrequires Human Resource Management

    A staff fee invoice is raised against the employee record HR maintains, which is also how the staff-ward discount knows who qualifies.

Common questions

Can parents actually pay online, or only see the invoice?+

They can pay. A guardian pays from the invoice by card or bank transfer through the school's own Paystack account, and the payment is verified, allocated to the invoice and receipted automatically. The school configures its own gateway keys, so the money goes directly to the school.

Does it chase overdue fees on its own?+

Yes. A daily job finds invoices past their due date and dispatches reminders to the family, under rules the school sets: how many days before the due date to warn, how long after it to send the first chase, how often to repeat, and how many reminders to send before stopping. Auto-reminders can also be switched off entirely.

How do scholarships and sibling discounts work?+

A scholarship is defined once — its type, its discount as a percentage or a fixed amount, the fee categories it applies to, and a budget. Rule-based ones like a sibling or staff-ward discount can apply automatically; merit and hardship awards are granted to named pupils and approved. Every award is tracked against the scholarship's budget, so the school can see what its aid is costing before the term starts.

Can a family dispute a charge?+

Yes. A guardian raises a dispute against an invoice from the parent portal, and it is resolved on the record by the bursary. Where the outcome is a correction, it becomes a refund, waiver, adjustment or credit request with its own approval trail.

Can students pay their own fees?+

No. The student portal is read-only for finance: a pupil can see their invoices and payments and download PDFs and receipts, but paying is done from the parent portal (or, for an employee, from the staff portal). If your sixth-formers pay their own fees, that is worth flagging to us.

Does it replace our accounting system?+

No. It handles billing, collection and the receivables side — invoices, payments, refunds, aging and reporting — and posts every event to a school-wide finance ledger that also carries hostel, store, staff and equipment entries. What it is not is a general ledger with a chart of accounts, so schools running one keep it and reconcile against these figures.

What about staff who are also parents?+

Staff fee invoices are a separate record from pupil invoices, raised against the employee and visible in their own staff portal — which is where the staff-ward discount is applied. They can pay from there directly.

Run your whole school on one connected platform

Start with the base package, switch on the modules you need, and give every parent, student and staff member a single place to log in.