INSIGHT · EDUCATION
NetSuite for independent-school and nursery groups
Why multi-setting education groups outgrow setting-level billing, how iSAMS and Famly become a billing sub-ledger to NetSuite, and how to surface revenue leakage and funded-hours reconciliation.
Independent schools and nursery groups reach a point where the billing system that got them started — iSAMS, Famly, or a patchwork of spreadsheets — can no longer answer the questions the board is asking. How much are we actually owed across all settings? Where is revenue leaking? Are funded hours being billed completely? That's usually the moment NetSuite enters the conversation.
Why education groups outgrow their billing system
iSAMS and Famly are excellent at what they do: managing pupils and children, fees, registers and parent communication at the setting level. What they're not built for is consolidated, multi-entity finance — a group P&L, intercompany positions, debtor-day analysis across every school and nursery, and audit-ready statutory reporting. As a group acquires settings, the gap widens.
What NetSuite brings
NetSuite OneWorld gives a multi-academy or nursery group one general ledger across every entity, with consolidation, intercompany handling and a single view of receivables. Crucially, the framing stays commercial — profit and loss, fee debtors, debtor days — rather than being forced into charity-specific vocabulary that doesn't fit a commercially run group.
The integration question
The right architecture keeps iSAMS and Famly as the billing sub-ledger — that's where fees are raised and parents are managed — and treats NetSuite as the group general ledger. A native, bidirectional integration moves invoices, credit notes, payments and bill-payer records into NetSuite, and writes external identifiers back so every transaction is reconcilable end-to-end. There's no need to re-platform what the settings already do well; you connect it.
Funded hours and revenue leakage
Two numbers tend to surprise education groups when they finally get a consolidated view. The first is revenue leakage — sessions delivered but never billed, discounts applied inconsistently, or credits that quietly erode fee income. The second is funded-hours reconciliation: government-funded entitlement hours that have to be tracked against what's actually claimed and delivered. A finance dashboard that pulls occupancy and billing together makes both visible — often for the first time.
Getting started
You don't need a big-bang migration. A sensible first phase connects one or two settings, proves the billing-to-GL flow and the reconciliation reporting, then rolls out across the group. The goal is a finance function that can answer the board's questions on demand — with the settings still running the tools they know.
Key takeaways
- Keep iSAMS/Famly as the billing sub-ledger; make NetSuite the group general ledger.
- A native bidirectional integration writes identifiers back for end-to-end reconciliation.
- Consolidated view exposes revenue leakage and funded-hours gaps — often for the first time.
- Frame everything commercially (P&L, fee debtors, debtor days), not in charity vocabulary.
- Roll out setting-by-setting; no big-bang migration required.
Working on something similar? Book a free call and we'll talk it through — no obligation.
Need this done on your NetSuite?
Book a free 30-minute consultation. I'll review your setup and tell you honestly whether I'm the right fit.