Oracle NetSuite

In OneWorld, every subsidiary is a node in a hierarchy inside the same account rather than a separate instance. Transactions carry the subsidiary they belong to, and consolidation happens by rolling up that hierarchy, with intercompany eliminations posted automatically to designated accounts.

The practical consequence is that adding a legal entity is a configuration task, not a new implementation, and that group reporting is a saved search or report filtered by hierarchy level rather than an export-and-merge exercise. It also means chart-of-accounts discipline matters enormously: a segment structure defined loosely in month one shows up as unreportable data in year two.

Everything in NetSuite is a record: customers, items, sales orders, invoices, purchase orders, work orders. Records reference each other, so a sales order can generate a fulfilment, an invoice, and the revenue schedule behind it while remaining linked back to the original document.

That linkage is why the order-to-cash flow is coherent: inventory decrements when fulfilment posts, cost of goods hits the ledger at the same moment, and receivables and revenue recognition follow from the same transaction rather than from a monthly import. Companies coming from separate accounting and inventory systems usually find this is the single largest process improvement.

NetSuite is customised through SuiteFlow for workflows and SuiteScript for code, plus custom records and fields. This flexibility is genuine — most process gaps can be closed — but each customisation becomes something to maintain and regression-test across the two annual releases.

The teams that stay happy on NetSuite tend to keep a written inventory of every script and workflow, review it annually, and delete what is no longer used. The teams that struggle inherited a decade of undocumented customisation from a departed partner.

Reporting is built on saved searches and report builder, both powerful and both with a learning curve that surprises people expecting a drag-and-drop experience. Most finance teams designate one person as the reporting owner within a few months of go-live.

For the close itself, period locking, approval routing, and the close checklist are native, and the consolidated close runs off the same hierarchy used all month. Teams commonly report a multi-day reduction in close time after moving off separate systems, driven mostly by eliminating manual consolidation and reconciliation steps.