It depends almost entirely on entity count and complexity. Two or three outlets, one bank, mostly card and cash: honestly, it may be too much at this stage, and we'll say so. Hong Kong has no small-company audit exemption, but a three-entity audit season is survivable on Xero.

Past eight or ten entities, with a central kitchen recharging outlets, six tender types settling on different schedules, and a group consolidation owed under s.379, the calculation flips. The cost of the current setup, in controller time and in what the spreadsheets hide, is usually already higher than it looks.

Yes, and it's a common path. OneWorld lets you add subsidiaries to an existing instance, so outlet companies join the same tenant as the holdco with consolidation across the whole group. The work is in the hospitality layer: POS journals, tender clearing accounts, and intercompany recharge flows that a corporate implementation never needed.

The caveat is the quality of the existing build. Clean chart of accounts and sensible segments make this straightforward; a generic rollout may need remediation first. We assess the existing instance as part of discovery.

The platforms pay you gross order value minus commission, refunds, and adjustments, on their own schedule. If you book the deposit as revenue, sales are understated and commission, one of your largest and fastest-moving costs, disappears into a netting entry nobody reviews. KeeTa's standard takeaway commission has run as high as 28 percent; that deserves its own line in the P&L.

In NetSuite, each platform gets a clearing account per outlet. The POS day posts at gross, the settlement clears against it, commission posts as a visible cost, and anything unmatched sits where someone can see it and chase it.

Yes, and you keep your POS. NetSuite doesn't replace Simphony, Infrasys, or Eats365 at the counter; it receives what they produce. The standard pattern is a daily sales journal per outlet: gross sales by category, tender-level takings into clearing accounts, voids and discounts as their own lines. How it arrives, via API or scheduled file, depends on the POS.

What matters is that the journal posts at gross with tenders split out. That's what makes settlement matching work downstream, and it's the part generic integrations most often get wrong.

Not exactly. The entity structure you have is the entity structure NetSuite is built for: each outlet 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: whether to cut over at year-end, which is cleanest, or mid-year, which is faster. That's one of the things the discovery phase maps before you commit to anything.

A properly configured NetSuite implementation for a multi-outlet 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.

Evaluate it against what the current setup costs: the finance team's week lost to settlement reconciliation, the audit premium for records assembled by hand across twenty companies, and the outlets that stayed open too long because nobody could see their real P&L.

Honest answer: no, and you shouldn't want it to. Hong Kong hospitality payroll runs on the Employment Ordinance's 713 average daily wage calculation, which drags tips and service charges into a rolling 12-month figure per employee, and the new 468 rule brings more casual staff into statutory coverage from January 2026. That belongs in a payroll system built for it.

NetSuite's job is what happens next: payroll posts as per-outlet, per-entity labour cost, so the number that decides whether a site is viable includes what it actually costs to staff it.

Service 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. Nobody runs a Saturday service while migrating that Saturday's books.

Phasing usually follows the structure: pilot on a small set of outlets, prove the POS journal and settlement matching, then roll the remaining entities in waves. The discovery phase maps that sequence before the build begins.

Since 1 January 2025, hotels and guesthouses collect 3 percent on accommodation charges and file a return with the IRD within 14 days of each quarter end. It lands on the operator, and the numbers have to reconcile to your accommodation revenue, net of the exempt categories, every quarter. That's a new recurring filing on a tight clock, four times a year.

NetSuite doesn't file the return; your team or your tax advisor does. What it provides is the figure: accommodation revenue isolated from F&B and other charges, by property, from a ledger where locked periods can't be quietly edited after the return has gone in.

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.