Independent NetSuite consultancy · London, UK
NetSuite for independent schools and nurseries.
For an independent school or nursery group, NetSuite works best as the group ledger behind the systems your settings already use. iSAMS and Famly keep raising fees and managing families; NetSuite OneWorld consolidates every setting, recognises fee income in the right term, reconciles funded hours and shows the board one set of numbers.
I build the integration natively in SuiteScript 2.1, so the data that drives your fee income stays traceable from the board pack back to the bill in iSAMS or Famly.
When you need this
Your group runs several schools or nurseries, finance rekeys fee data from iSAMS or Famly each month, and nobody can say quickly what is owed, what was billed or what funded hours are still unclaimed.
What I cover
- iSAMS and Famly as billing sub-ledgers
- One NetSuite OneWorld subsidiary per setting
- Termly fee billing and revenue recognition
- Funded hours reconciliation by setting
- Bursaries, scholarships and sibling discounts
- Occupancy, revenue leakage and board reporting
iSAMS and Famly as billing sub-ledgers to NetSuite OneWorld
iSAMS (schools) and Famly (nurseries) are good at what happens inside a setting: pupils and children, fees, registers and parents. They are not built for group finance: consolidation, intercompany, one debtor ledger and statutory accounts. NetSuite OneWorld is. The design I use keeps each system doing its own job:
- Settings to subsidiaries. Each iSAMS school and Famly site maps to its NetSuite subsidiary, with year groups or rooms as classes or departments.
- Payers to customers. Only the financially responsible contact becomes an AR customer. Each pupil or child sits under that customer, so split billing across separated parents still works.
- Fee codes to items. Tuition, lunches, trips, wraparound care and deposits each map to a NetSuite item, GL account and tax code. An unmapped code stops in a queue rather than posting to the wrong place.
- Bills, payments and credits. Invoices, receipts and credit notes flow in with the source ID stamped on them, so re-running a sync never creates duplicates.
That is the pattern behind my iSAMS and Famly case study, a representative engagement across 40 subsidiaries, with customers, invoices and payments syncing hourly. I explain the wider reasoning in NetSuite for independent-school and nursery groups.
Fee billing, VAT and revenue recognition
Schools usually bill a term in advance. If those invoices post straight to income, the monthly accounts are wrong for most of the year. In NetSuite, term fees can feed Advanced Revenue Management, so income is recognised across the term and the manual deferral journals go away.
VAT needs the same care. HMRC guidance says that from 1 January 2025 education and boarding services provided by a private school for a charge are taxable at the standard rate of 20% (HMRC policy paper). Nursery classes made up wholly, or almost wholly, of children below compulsory school age remain exempt (VAT Notice 701/30). A group with both schools and nurseries therefore needs tax codes set per fee type and per setting. Your VAT adviser decides the treatment; I make sure every fee code in iSAMS or Famly carries the right SuiteTax code into NetSuite.
Funded hours reconciliation
In England, local authorities fund early education places. For eligible children of working parents aged 9 months and above, they must secure 1,140 hours of free provision a year, which works out at 30 hours a week over 38 weeks (DfE statutory guidance). The setting delivers the hours; the local authority pays the provider. That gap between delivered, claimed and paid is where nurseries lose money without noticing.
In NetSuite I model the funded element as its own line type, for example a 15-hour or 30-hour funded line, mapped to a funded-hours item with the local authority as the funding customer. Each setting can then reconcile four numbers: expected, claimed, paid by the local authority and posted. On the case study engagement, Famly's Public API did not expose funded hours as a separate object, so the design allowed for reading that data through an isolated adapter. Check what your own Famly account exposes before relying on it.
Bursaries, discounts and revenue leakage
Bursaries, scholarships, sibling and staff discounts are real costs, and boards want to see them. I post them as discount items or negative lines by award type, reported separately rather than netted into fees, so gross fees, the cost of each award type and net fee income are all visible.
Leakage is quieter. The causes I look for first in education groups are:
- pupils or children enrolled but never invoiced
- discounts applied inconsistently between settings
- extras such as clubs, trips or late pick-ups delivered but not billed
- credit notes for leavers that were never matched to a refund or a new invoice
Putting enrolment or occupancy next to billing makes these visible. A Revenue Leakage Audit reconciles what should have been billed with what was invoiced and ranks every gap by value, using a read-only role.
Occupancy and board reporting
Once every setting posts to one ledger, the board questions get quick answers: how much is owed across the group, by setting and by age; fee income against budget per term; occupancy against capacity, and what unfilled places cost; funded hours still unclaimed.
In the case study, daily occupancy snapshots from iSAMS and Famly fed projected revenue, one AR view replaced 40 separate logins, and the group close moved from around ten working days to roughly three. Those figures belong to that engagement; your own will depend on your settings and processes. You can explore the reporting in the schools and nurseries finance dashboard demo, which uses sample data.
How I can help
- NetSuite for the group. OneWorld design, chart of accounts, fee items, revenue recognition and consolidation through my NetSuite implementation service.
- iSAMS and Famly integration. A native SuiteScript 2.1 build with staging, mappings, retries and reconciliation, through my NetSuite integration services.
- Revenue assurance. A fixed-scope Revenue Leakage Audit to put a figure on unbilled fees and inconsistent discounts.
FAQ
NetSuite for schools and nurseries: common questions.
Do we have to replace iSAMS or Famly to use NetSuite?
No. iSAMS and Famly stay where fees are raised and parents are managed. NetSuite OneWorld becomes the group general ledger, with invoices, payments, credit notes and bill payers flowing in from each setting.
How do you set up NetSuite for a group of schools and nurseries?
Usually one subsidiary per school or nursery company, a shared chart of accounts, fee codes mapped to NetSuite items and GL accounts, and consolidation in OneWorld. Bill payers become customers, and each pupil or child sits under the payer so you can report per child as well as per family.
How do you reconcile funded hours?
I model the funded element as its own line type mapped to a funded-hours item, with the local authority as the funding customer. Each setting can then reconcile expected hours to claimed, paid by the local authority and posted, and see any unreconciled balance.
How should bursaries and sibling discounts be shown?
As discount items or negative lines by award type, reported separately rather than netted into fee income. That way the board sees gross fees, the cost of each award type and net fee income.
Does VAT now apply to our fees?
Since 1 January 2025, education and boarding services provided by private schools for a charge are standard-rated at 20%, according to HMRC. Nursery classes made up wholly, or almost wholly, of children below compulsory school age remain exempt. Confirm the treatment for each fee type with your VAT adviser; I then set the tax codes in NetSuite to match.
How long does an iSAMS or Famly integration take?
It depends on the number of settings, fee codes and payment routes. I usually start with one or two settings, prove the billing-to-ledger flow and the reconciliation reports, then roll out across the group.
Keep reading
Related case study, insight and demo.
NetSuite × iSAMS & Famly
Schools and nurseries connected to NetSuite OneWorld across 40 subsidiaries.
Read the case study →NetSuite for school and nursery groups
Why multi-setting groups outgrow setting-level billing, and how the sub-ledger model works.
Read the insight →Live demo: schools and nurseries finance
Consolidated debtors, occupancy, leakage and funded hours, with sample data.
Try the demo →Running schools or nurseries on iSAMS, Famly and NetSuite?
Book a free 30-minute call. Tell me how your settings bill today and I'll tell you honestly what connecting them to NetSuite would take.