AI is moving beyond experimentation and beginning to connect directly to enterprise systems. For companies running NetSuite, the bigger question may no longer be what AI can do, but what it should be allowed to do.
For the last several years, companies have been experimenting with AI largely outside their core business systems. Spreadsheets were uploaded, data was copied into prompts, queries were generated and employees found increasingly creative ways to use these tools. That experimentation demonstrated enormous potential. It also happened faster than most companies could establish meaningful governance around it. As AI begins connecting directly to systems like NetSuite, that period is coming to an end.
NetSuite contains far more than accounting data. It contains customers, pricing, margins, inventory, purchasing, sales activity, transactions and years of operational history. Giving AI access to that information can be extraordinarily useful.
But connecting an AI platform to NetSuite is fundamentally different from asking it a question about an exported spreadsheet. Permissions matter. Roles matter. The underlying architecture matters. An AI system should not automatically have access to something simply because the technology makes that access possible. The same controls companies have spent years establishing around ERP users and integrations now need to be considered when AI enters the environment.
This is where the conversation becomes much less about AI itself. Should sales have AI access to customer history? Probably. Should it see margins, payroll or unrestricted financial information? That requires a different discussion.
The same questions apply to what AI should be allowed to change. Creating an Opportunity is very different from changing an Item Receipt, Vendor Bill or Journal Entry. Those decisions require more than understanding an AI platform. They require understanding how the company operates, how NetSuite has been configured and what happens downstream when something changes. The technology will continue getting easier. Knowing where to put it, and where not to put it, may become considerably more valuable.
The valuable skill may not be knowing AI. It may be knowing the business well enough to know where AI belongs. For companies running NetSuite, AI does not eliminate the need for ERP governance. It makes good ERP governance considerably more important.
Most NetSuite problems are not accounting problems. They are systems problems.
Left Ledger Inc. helps companies already running Oracle NetSuite regain operational clarity, financial trust, and process control across the ERP environment.
Independent. No license reselling. No partner quotas. No layers of project management.
You work directly with a NetSuite ERP soloist focused on how the system actually behaves inside day-to-day operations.
Jack Ring
Left Ledger Inc.
724-816-1000
...
NetSuite CRM is one of the most overlooked and underutilized components of most accounts. If your organization pays for NetSuite but still relies on external CRM systems, there's a strong chance you're spending more time, money, and energy than you need to while your teams operate in silos.
NetSuite offers a few different ways to add landed costs into the value of an item. Each method has certain benefits & drawbacks. The method discussed in this article is basic and flexible but also somewhat prone to user error. It involves manually entering landed costs directly on an Item Receipt transaction.
Most companies believe their ERP is under control because they can close the books and produce financials. That is a low bar. The real test is whether the system reflects reality without explanation, adjustment, or second guessing.
Control does not break all at once. It starts in small places, usually in purchasing, where commitments, receipts, and billing begin to drift out of sync. The Purchase Order History Report exposes that drift immediately, and it does it without interpretation.
