A NetSuite go-live is a finish line and a starting line at once. The data's in, the invoices are going out, and the implementation project is "done," but implementations run on deadlines, and the settings that don't block go-live are the ones that get deferred and then forgotten. Here are the five that most often need attention in the first weeks, once real people are using it every day.
1. Tighten roles and permissions
To get everyone working, implementations tend to hand out broad roles: sometimes Administrator, often a standard role with far more access than a job needs. That's fine for launch and a real risk afterward: too many people can edit records, change setup, or see financials they shouldn't. Review who has what, build role-based access around what each function actually does, and keep segregation of duties in mind (the person entering bills shouldn't also approve and pay them). This is the highest-value cleanup and the one most often skipped.
2. Turn on the approval workflows
Four transaction types frequently go through at go-live with no approval routing, because approvals were "phase two":
- Purchase orders
- Vendor bills
- Sales orders
- Expense reports
Set up the SuiteFlow approvals that match how you actually sign off on spending and commitments. Even simple threshold-based routing (over $X needs a manager) closes the gap between "the system allows it" and "we approved it."
3. Build saved searches and role-based dashboards
Out of the box, people land on generic dashboards and hunt through default lists. The thing that makes NetSuite feel usable (and reportable) is a set of well-built saved searches and dashboards tuned to each role: the KPIs a controller watches, the open orders a fulfillment lead needs, the aging a collector works. If your team is exporting to spreadsheets to answer basic questions, this is why.
4. Fix the transaction forms and templates
Default invoice, PO, and sales-order forms show every field in a generic layout. Two jobs here:
- Customize the on-screen forms so users see the fields they need and not the ones they don't, and set the right fields as mandatory to keep data clean.
- Build proper Advanced PDF/HTML and email templates so what reaches customers and vendors looks like your business, with the correct terms and remittance details.
5. Lock down accounting defaults and period close
Confirm the accounting preferences, default posting accounts on items, and numbering are set the way your books need them. Small defaults here create big cleanup later. Then make sure accounting periods are actually being closed once they're reported. A closed period stops anyone back-dating a transaction into a month you've already reported; a locked one still lets roles with override permission post. NetSuite's built-in Period Close Checklist is the place to start.
A few more worth a look
These all tend to need a second pass:
- Duplicate detection on customers and vendors
- Reminders and notifications
- Bank feeds and reconciliation
- Auto-generated document numbering
None are dramatic; together they're the difference between a system that fights you and one that just works.
When to get help
If your go-live is behind you and any of the above sounds familiar (reports that need spreadsheets, access that's too broad, approvals that aren't really approvals), that's the post-implementation cleanup I do: making a NetSuite that's technically live actually work day to day.
Ten Rivers Systems handles technical setup, configuration, and data migration only and does not provide accounting or tax advice. I am not an accountant or tax adviser. How you keep your books and what you owe stays between you and your own professionals.
Common questions
What should I fix first after a NetSuite go-live?
Roles and permissions. Implementations hand out broad access to hit the launch date; tightening role-based access and separating duties is the highest-value cleanup and the one most often skipped.
Why does NetSuite still feel clumsy after go-live?
Usually because saved searches and role-based dashboards were never built. Out of the box, everyone gets generic dashboards and default lists. Tuning them per role is what makes NetSuite feel usable and reportable.
Should past accounting periods be closed?
Yes. Close each period once it's reported, so nothing gets back-dated into it. Locking alone still lets roles with override permission post, and NetSuite's Period Close Checklist walks through both steps.