Netsuite For Education

Yes, and you keep it. NetSuite doesn't replace iSAMS, PowerSchool, or OpenApply in the school office; it receives what they produce. The standard pattern is enrolment and billing data flowing into NetSuite as invoices and revenue schedules, per student intake, per campus, so the fee ledger and the general ledger stop being two different truths.

How it arrives, via API or scheduled file, depends on the system. What matters is that the school-side record drives the accounting record instead of someone re-keying between them.

Honest answer: payroll calculation belongs in a payroll system built for Hong Kong, like Workstem, and we'd rather integrate one than pretend. What NetSuite owns is the liability side, which in schools is unusually heavy: contract-end gratuities that accrue over two-year contracts, ORSO and MPF populations running side by side, and long service payment provisions that changed when offsetting was abolished in May 2025.

Those obligations belong on the books as they build, per teacher cohort, per entity, not as a surprise in the leaving month. NetSuite accrues them continuously, so staff cost by campus is real, current, and complete.

A properly configured NetSuite implementation for a multi-entity education group is a real investment, in licensing and in implementation work, and we won't pretend otherwise. The discovery phase scopes the work and the number before you commit, so there's no open-ended bill.

Weigh it against what the current setup costs: the finance team's weeks lost to per-entity consolidation, the audit premium for records assembled by hand across a dozen companies, and decisions made late because nobody could see which campuses actually make money.

School doesn't stop, so the implementation can't ask it to. The build runs alongside your current setup: new activity starts clean in NetSuite at cutover while legacy periods run to their natural close in the old system. The school year gives you a natural cutover point that most businesses don't get, and we plan around it.

Phasing usually follows the structure: pilot on one campus or entity, prove the fee billing and the bank matching, then roll the remaining entities in waves. The discovery phase maps that sequence before the build begins.

On the balance sheet, mostly, and under more scrutiny than they used to get. Refundable debentures are liabilities until redeemed. Non-refundable levies and nomination rights need a recognition policy you can defend. And since the EDB's 2023 approval mechanism, schools report to parents on the use of proceeds at least annually, which means tracking what those funds actually paid for.

NetSuite carries each instrument as what it is, keeps proceeds traceable to spending, and produces the reporting without a year-end reconstruction. Your fee structure is between you, your advisors, and the EDB; the books just have to hold it properly.

Not exactly. The entity structure you have is the structure NetSuite is built for: each operating company becomes a subsidiary in OneWorld with its own books, and the group view exists on top of them instead of in a spreadsheet. Current-year data migrates cleanly; prior years usually stay archived in Xero for audit reference rather than being rebuilt.

The real question is sequencing. A school year has a natural cutover point that a calendar year doesn't, and fee billing cycles make mid-year moves messier than they look. That's one of the things the discovery phase maps before you commit to anything.

Honestly, sometimes yes. A single centre or one small campus on one company, with one bank account and a part-time bookkeeper, should stay on Xero or QuickBooks, and we'll tell you so. Hong Kong has no small-company audit exemption, but a two-entity audit season is survivable.

The calculation flips with structure, not headcount. Multiple campuses in separate companies, a group consolidation owed under the Companies Ordinance, fees deferred across terms, and gratuity liabilities accruing across teacher contracts: at that point the cost of the current setup, in controller time and in what the spreadsheets hide, is usually already higher than it looks.

Carefully, because it's the heart of school accounting. Money collected before teaching happens is deferred revenue, not income, and Hong Kong's fee rules keep most tuition arriving monthly through the year with limited advance collection. NetSuite builds the recognition schedule per term and per intake, releases revenue as teaching is delivered, and handles the awkward cases: mid-term withdrawals, pro-rata refunds, and enrolment deposits.

The by-product is the record. When your auditor asks why revenue was recognized when it was, the schedule and the evidence sit behind every figure, entity by entity.

It raises the bar rather than changing the rules. Tax exemption under s.88 comes with conditions: profits applied solely to charitable purposes, and the IRD can call for accounts and records at any time to check that activities still match the school's objects. The register is actively reviewed, and exemptions do get withdrawn. Commercial sidelines, from venue hire to camps for non-students, need their own clean treatment.

NetSuite keeps the record producible on demand: income and spending traceable to purpose, entities separated, periods locked once closed. Whether an activity is charitable is a question for your tax advisors. Whether your records can answer the IRD's letter is a question for your system.

OnePacific is now part of PS Global Consulting.

hk.psglobalconsulting.com is the dedicated Hong Kong NetSuite practice site for the same award-winning team clients knew as OnePacific, while psglobalconsulting.com covers the broader PS Global Consulting business across the region.

We continue to deliver NetSuite implementation, customization, integration, and support services for clients across Hong Kong and APAC.