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
Purchase orders, vendor bills, sales orders, expense reports: at go-live these frequently post with no routing, because approvals were "phase two." 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 and none of your branding. 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), and 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 being managed and locked: closed periods should be locked so nobody back-dates a transaction into a month you've already reported. If there's no period-close checklist, that's the first process to write down.
A few more worth a look
Duplicate detection on customers and vendors, reminders and notifications, bank feeds and reconciliation, and auto-generated document numbering all tend to need a second pass. 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 exactly the post-implementation cleanup we do: making a NetSuite that's technically live actually work day to day.
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 closed accounting periods be locked?
Yes. Lock closed periods so nothing gets back-dated into a month you've already reported, and write down a period-close checklist if one doesn't exist yet.