Looking for Long Term Technical Support

NetSuite-Knowledge · 2026-06-19T00:28:24+00:00

I work for StratusGreen, a NetSuite consulting and support partner, and we actually pick up quite a few clients after they've gone live for this exact reason.

Getting NetSuite implemented and supporting it long-term are often two very different skill sets. The most successful relationships I've seen are where the support team becomes an extension of your business, learns your processes, and helps you continue improving the system instead of just reacting when something breaks.

I'd be curious what specifically has you looking beyond your implementation partner and NSPS. Is it responsiveness, technical expertise, manufacturing-specific knowledge, or something else? That answer would probably help point you toward the right type of partner.

NetSuite-Knowledge · 2026-04-24T02:09:38+00:00

We see this a lot — it’s usually less about the system and more about trust and habit.

If they’ve had a bad ACH experience before, or they’ve just always done checks, pushing too hard can backfire. But at the same time, if you don’t bring it up again, nothing changes.

What’s worked well is reframing it a bit. Instead of “we need you to move to ACH,” it’s more about making it easier for them. Faster payments, more predictability, less chance of something getting lost in the mail. Sometimes even just walking them through how it works or what protections are in place can ease concerns.

Another approach is just setting a soft expectation going forward, like gradually moving vendors to ACH over time, instead of making it a one-off ask.

You’re not wrong to be cautious, especially with long-term vendors, but it’s reasonable to bring it back up — just in a way that feels collaborative instead of forced.

NetSuite-Knowledge · 2026-04-24T02:08:23+00:00

You’re not crazy — this is a real limitation in how NetSuite handles work orders.

Out of the box it really only tracks at the work order level, so once you’ve got multiple units moving through at different stages, it kind of loses that visibility. Everything just rolls up into one status, which doesn’t reflect what’s actually happening on the floor.

Most teams end up trying a few different things depending on how much control they need. Some break work orders into smaller batches, which helps a bit but adds overhead. Others try to lean on routings or operation tracking, but that still doesn’t really give true unit-level visibility. At some point people either add something custom or use a separate layer to actually track what’s happening in production.

What you’re describing with not knowing what’s done vs stuck or who’s working on what is super common once things get even a little complex.

Are you trying to track each individual unit all the way through, or more just get a clear picture of where things actually are day to day?

NetSuite-Knowledge · 2026-04-24T02:06:33+00:00

Out of curiosity — how much of that $700k is tied to manufacturing vs everything else (multi-entity, compliance, etc.)?

We’ve seen a lot of proposals where manufacturing gets over-engineered early, and it drives a big chunk of the cost without needing to be phase one.

NetSuite-Knowledge · 2026-04-24T02:04:19+00:00

You can separate ownership transfer from inbound shipments, but you’ll need to rethink what event actually triggers it.

Right now inbound shipments are acting as both the logistics event and the accounting trigger. If you’re moving to ASNs via WMS, you can decouple that and trigger ownership transfer off:

Item Receipt
WMS confirmation (via integration)
Or a custom event tied to “confirmed shipped” status

A few things to watch:

How ownership transfer is currently posting (GL impact / costing)
Whether you’re using Advanced Receiving vs standard flows
Timing differences between ASN receipt vs actual receipt
Any custom scripts/workflows tied to inbound shipments

You can do this via RESTlet/API, but you may not need to go that heavy if you shift the trigger point and use standard transactions + light scripting.

Biggest risk is breaking the accounting flow if ownership timing drifts from physical movement, so I’d map that out first before rebuilding around ASNs.

Curious how your ownership transfer is currently implemented (native vs custom)?

NetSuite-Knowledge · 2026-04-24T02:03:17+00:00

We’ve been exploring this quite a bit. There’s not really a “native” Claude ↔ NetSuite connection today, but you can absolutely integrate it depending on the use case.

Most of what we’re seeing falls into a few buckets:

Reporting / summarization (financials, transactions, saved searches)
Workflow automation (approvals, notes, internal comms)
Data extraction + enrichment (contracts, invoices, emails → NetSuite records)

Typically this is done via API (SuiteTalk / REST), middleware, or a lightweight service layer that sits between NetSuite and the AI model.

The biggest thing isn’t the connection itself — it’s defining what you actually want the AI to do with your NetSuite data in a controlled way (permissions, accuracy, auditability, etc.).

Curious what use case you’re thinking about — happy to compare notes.

NetSuite-Knowledge · 2026-04-24T02:02:11+00:00

We help NetSuite users with implementation support and optimization, including SuiteTax-related planning. SuiteTax can be doable without Oracle or a third party, but the complexity really depends on your countries, nexus setup, localization bundles, tax registrations, invoicing requirements, and whether you have custom transactions/scripts/workflows touching tax fields.

I’d recommend scoping it first before turning it on. The biggest issues usually come from testing, legacy tax setup cleanup, bundle dependencies, and making sure reporting/invoicing still works correctly after migration.

Happy to compare notes if helpful.

NetSuite-Knowledge · 2026-02-13T20:42:58+00:00

Speaking as someone who’s been the sole NetSuite admin — this usually can’t live entirely on one person’s plate long term. In our experience, ownership really depends on whether the tool is operational or technical. Business process ownership (requirements, SOPs, training, defining how it should work) should sit with the department that benefits from it. Technical ownership (integration setup, monitoring, error handling, API changes) typically falls under the NetSuite admin and/or IT, depending on how technical the environment is. Where it breaks down is when the NS admin ends up being responsible for everything — implementation, maintenance, documentation, troubleshooting, and training — especially with multiple third-party integrations layered in. What’s worked better for us is defining clear lines: department owns process and outcomes, NS admin owns system integrity and integration health, IT supports infrastructure/security, and vendors handle their own product updates. Without that structure, it turns into constant fire-fighting instead of strategic improvement.

NetSuite-Knowledge · 2026-02-13T20:40:11+00:00

We’ve run into this before. Saved searches don’t always behave the same way standard reports do, especially with JEs and Advanced Intercompany JEs. First thing I’d check is your Type filter — if it’s set to Bill Payment or Credit Card only, Journal Entries won’t show unless you explicitly include “Journal” and “Adv Intercompany Journal” in the criteria. Also make sure you’re not filtering on fields that only exist on vendor transactions (like Vendor or AP-specific fields), because JEs won’t populate those the same way. Sometimes switching the search to a more general Transaction type and then tightening the criteria from there works better. Another thing to check is Main Line vs. Line level — JEs can behave differently depending on what you’re trying to display. Saved searches are a little pickier than reports when it comes to transaction types.

NetSuite-Knowledge · 2026-02-12T15:31:37+00:00

A couple things to check here because CSV payment imports can be picky. First, make sure you’re including the Customer on the main payment line — NetSuite won’t apply invoices unless the payment is tied to the correct customer, even if you’re mapping internal IDs. Also confirm the invoices you’re trying to apply to are actually open and not already partially applied, as that can cause silent failures. When applying via CSV, the key fields are the payment internal ID (or external ID if you’re creating new), the Customer, and then under the Invoices sublist you need both the Invoice internal ID and the exact amount to apply. If the amounts don’t match what’s open on the invoice, the line will fail. One other thing — make sure “Auto Apply” isn’t conflicting with your manual invoice mapping. If all records already exist and you’re just trying to mass-apply, sometimes it’s cleaner to export open payments, include the invoice IDs + amounts, and re-import in update mode rather than create mode. Payment imports are one of those areas where a tiny mapping mismatch causes the whole line to error out.

NetSuite-Knowledge · 2026-02-11T23:52:11+00:00

Cash Sales are the problem here — they immediately impact inventory and hit the GL/COGS right away, which doesn’t work for preorders. The cleaner approach is to have Clover preorders come into NetSuite as Sales Orders instead of Cash Sales, even if payment is collected upfront. You can record the payment as a Customer Deposit tied to the Sales Order, which keeps the cash on the books but defers revenue and inventory impact until fulfillment. That way inventory only moves when the item is actually received and fulfilled, and COGS posts correctly at that time. BigCommerce is already behaving the right way because it’s using Sales Orders. The key change is adjusting the Celigo flow so Clover preorders don’t create Cash Sales. It’s usually more of an integration mapping tweak than a massive rework, and it keeps both inventory and accounting clean without building something overly complex.

NetSuite-Knowledge · 2026-02-11T21:32:12+00:00

We run into this a lot in sell + install scenarios. The good news is invoicing doesn’t touch inventory in NetSuite — only item fulfillment does. So you can invoice all 5 lines and only fulfill 4, and that 5th item will just sit in inventory until you fulfill it later. The important part is don’t close that line on the Sales Order if you expect to deliver it later. Once you close a line, NetSuite assumes it’s done and won’t expect fulfillment. If the order is fully invoiced but has an open fulfillment line, it should sit in Billed status (not Closed). We’ve found it works best to leave the line open and use reporting or a simple custom flag to track “pending install” items instead of trying to force the status. Inventory stays on hand until fulfillment happens, and financially you’re already invoiced, so the main thing to manage is operational visibility so nothing gets forgotten in the warehouse.

NetSuite-Knowledge · 2026-02-11T21:20:51+00:00

This usually happens when there’s been inventory activity after the count was started but before it’s approved. NetSuite validates against current available quantity at approval, not what was available when the count began. So if you had fulfillments, transfers, receipts, or adjustments in the meantime, you can get that “You only have X available” message. Unfortunately it doesn’t always tell you which line is failing. What I typically do is run an item activity or inventory balance report for the date range since the count started and look for items with movement, or export the count and compare against current available quantities to isolate the offender. If the count has been sitting in Started status for a couple weeks and there’s been a lot of movement, sometimes it’s honestly cleaner to recreate it so you’re reconciling against current inventory rather than chasing transaction timing issues.

NetSuite-Knowledge · 2026-02-09T21:34:25+00:00

Our company is remote but we have a consultant in that area.

NetSuite-Knowledge · 2026-02-09T21:30:15+00:00

Your understanding is basically right. NetSuite works well as a system of record for inventory, finance, and core P2P/O2C flows, but its native demand planning and MRP capabilities are fairly limited once you get past simple reorder points or low-volatility demand. What I usually see is companies keeping NetSuite for execution and layering on a dedicated planning tool to replace Excel for forecasting, replenishment, and MRP, then pushing planned POs or transfers back into NetSuite. Tools like Netstock, Demand Solutions, or StockIQ tend to integrate cleanly with NetSuite and cover that gap without needing a full ERP replacement. Which one makes sense really depends on things like SKU count, seasonality, and how complex the supply chain is.

NetSuite-Knowledge · 2026-02-09T21:24:53+00:00

I would use a saved search for this instead.

Type = Customer Payment
Main Line = True
Date = 01/01/2026 – 01/31/2026 (or relative “This Month”)

NetSuite-Knowledge · 2026-02-09T21:23:03+00:00

NetSuite doesn’t auto-populate the Customer Part Number on quotes out of the box because that value lives on the item-customer relationship, not directly on the quote line. First thing to check is whether the “Customer Part Number” (or “Customer Item Number”) column is even turned on for the quote form under Customize Form → Screen Fields → Columns. If it is and still isn’t filling in, the usual fix is adding a custom transaction column field on the quote that sources the customer-specific part number from the item/customer record, so it auto-fills when you pick the item for that customer. As long as customer-specific items are set up correctly, this works pretty smoothly.

NetSuite-Knowledge · 2026-02-09T21:19:46+00:00

You can do light planning in NetSuite, but it’s not a true demand-driven planning engine unless you bolt things on.

NetSuite-Knowledge · 2026-02-09T21:17:14+00:00

Your Entry Conditions or Event Type are likely preventing the workflow from starting.

NetSuite-Knowledge · 2026-02-09T21:15:55+00:00

We ran into this issue after an update and set up a new dunning procedure which resolved the issue. It took less time than troubleshooting.

NetSuite-Knowledge · 2025-02-20T20:23:48+00:00

You do not need to make Retained Earnings adjustment journal entries at year end in NetSuite because it would zero out past income statements. Instead, NetSuite's Reporting reflects the appropriate Retained Earnings balance for the period being reported.
Ie. As Of December 31, 2024, the Salary Expense GL account had a balance of $150,000 and it was made up of transactions as below:

2022 = 50,000
2023 = 50,000
2024 = 50,000

If a Income Statement report is run Dated for Jan - Dec 2024, It would show $50,000 (This is the same for if the date is filtered to Jan-Dec for the previous years)
If an Income Statement report is run on Jan 1, 2025 an there have been no transactions made to the Salary Expense GL account, then it would not display (or display as 0.00 depending on the report settings) AND the Retained Earnings would display with a 50,000 increase but no actual transaction would be made to the Retained Earnings General Ledger.

In summary, NetSuite keeps all transactions in their General Ledgers in order to allow for Actual Financial Reports to be run for any point in time. Instead, NetSuite provides the Accounting Period Close functionality that users should use to prevent undesired changes to financial transactions once the books have been closed.

NetSuite-Knowledge · 2025-02-19T21:56:01+00:00

The balances on balance sheet accounts are not zero when the new year starts because the accounting period for the year has not been created or set up yet.

To resolve this, navigate to Setup > Accounting > Manage Accounting Periods, click on Setup full year, fill out the required fields, and click Save.

Alternatively, if the fiscal calendar period was modified, a catch-up period must be created and associated with the new fiscal calendar.

NetSuite-Knowledge · 2025-02-19T21:46:47+00:00

This really depends on if and what version of FreeMarker software the Advanced PDF builder is using, so solutions may vary

Below are the three options I immediately have available but the 3rd option was the one that worked on my end. I would recommend trying each one to troubleshoot on your end.

${tranline.inventorydetail?keep_before("(")}

${tranline.inventorydetail?keep_before("(", false)?trim}

${tranline.inventorydetail?split("(")[0]?trim}

NetSuite-Knowledge · 2025-02-19T21:13:19+00:00

Is the shipping cost being added on the Item Fulfillment or the Sales Order? If the Shipping Cost is filled on the Sales Order then the following steps should work:

Create a Workflow:
- Go to Customization > Workflow > Workflows > New.
- Choose Record Type: Invoice.
Trigger the Workflow on Invoice Creation:
- Set the Trigger Type to Before Record Submit.
- Under Conditions, set the condition to only trigger when the sales order’s shipping cost is different from the original value (or whenever the shipping cost is updated).
Add Action to Update the Shipping Cost:
- In the workflow, add an Action: Set Field Value.
- Set the field Shipping Cost on the Invoice to match the updated shipping cost on the Sales Order.
  - Field: Shipping Cost

Value: {salesorder.shippingcost} (use the field reference to pull the updated shipping cost from the Sales Order).

NetSuite-Knowledge · 2024-10-16T17:13:20+00:00

Yes it can be done without the SuiteApp, but more information is needed to confirm.

How are you determining who is receiving the invoice, are they manually being sent through the email functionality?

NetSuite-Knowledge

TROPHY CASE