Find the cause
Understand why work gets stuck, numbers disagree, or an integration needs constant attention.
NetSuite Systems Review · Introductory offerKnow your NetSuite.
Know your NetSuite.
Know what to do next.
We start by learning how your team uses NetSuite, where work gets stuck, and what needs attention.
You’ll receive a written review of your NetSuite setup, the problems we found, and recommendations in priority order.
See a sample reviewInside an Ebenstead reviewUnderstand what’s slowing you down.
Understand what’s slowing you down.
Know what to fix first.
When reports don’t agree, routine work needs a spreadsheet, or nobody can explain a customization, it’s hard to know where to start. We investigate the cause and recommend what to fix first.
Choose the right next step
See the business impact, recommended fix, relative effort, and dependencies before deciding what to tackle.
Keep the knowledge
Leave with documentation your team can use to operate, maintain, and improve the system.
Explore a sample deliverable
Read the sample Start with the summary. Open any finding for the evidence, recommendation, and test that would confirm the fix.
Illustrative review. This sample review is for a fictional distributor. The company, records, measurements, and findings are all made up to show the report’s format and level of detail.
EBENSTEADExample Distribution Co.
NetSuite Systems Review
How the system works. Where it needs attention. What to do next.
Sample deliverable
Review edition 01
Review edition 01
Start with reliable orders, payments, and reporting.
The sample company uses NetSuite for purchasing, inventory, sales, and finance. Its routine transaction paths are established, but overlapping approval logic, repeat warehouse messages, and overbroad access create avoidable risk. Start with those three controls, then address billing exceptions, reporting accuracy, supplier data, and slow order entry.
8Prioritized findings
3Controls to address first
2Improvement opportunities
1Practical action plan
What the business needs from NetSuite
In this example, Finance wants a receivables balance it can trust. Operations wants orders to move without repeated checks. Leadership wants to add another warehouse without carrying today’s workarounds into the new location.
What is working
- All 12 sampled routine order-to-invoice scenarios completed as expected.
- Purchasing and receiving have identified business owners and documented daily steps.
- Finance maintains a close checklist and a reference receivables report.
What needs attention first
- Reapproval when an order changes after approval.
- Protection against a warehouse event being processed twice.
- Separation of vendor maintenance and payment responsibilities.
Recommended first decision
Assign the Controller, operations lead, and integration owner to resolve findings 01–03. Keep the existing core processes while testing those corrections in sandbox.
The review separates confirmed findings, improvement ideas, and questions that still need investigation. The coverage register below makes that distinction visible. This example uses selected transactions and 30 days of operational history.
Look across the business and the system.
The table shows what was reviewed, what was found, and what still needs checking. Areas that haven’t been tested are marked as open.
| Business question | What we examine | Status in this example |
|---|---|---|
| Does NetSuite fit how we work? | Business goals, process-owner interviews, manual workarounds, sales, purchasing, fulfillment, billing, and growth plans. | Selected processes mapped. Warehouse expansion requirements remain to be confirmed. |
| Can Finance trust the numbers? | Account and subsidiary setup, accounting periods, close tasks, reconciliations, AR/AP, and reporting definitions. | Receivables tested in 05. Full close, AP, and intercompany testing remain open. |
| Is our underlying data reliable? | Customer, vendor, and item records; duplicates; required fields; transaction quality; and ownership of corrections. | Vendor sample tested in 07. Customer and item data need separate validation. |
| What is running behind the scenes? | Scripts, workflows, forms, fields, custom records, saved searches, dependencies, and whether each customization is still needed. | Inventory completed; selected logic traced in 01, 02, 05, and 08. Ownership gaps in 06. |
| Why does routine work feel slow? | Record saves, searches, dashboards, background jobs, processing queues, and representative busy-period usage. | Order-save timing tested in 08. Busy-period account-wide performance remains open. |
| Do our connected systems agree? | Data ownership, mappings, schedules, accepted and rejected records, retries, duplicate handling, alerts, and reconciliation. | Four connections mapped; warehouse and billing behavior tested in 02 and 04. |
| Does each person have the right access? | User lifecycle, roles, sensitive permissions, separation of duties, authentication, and integration access. | Operations role tested in 03. Authentication and remaining role combinations need review. |
| Could we use what we already have? | Enabled features, purchased modules, SuiteApps, user adoption, training, and native alternatives to custom work. | Two opportunities identified below. License entitlements and fit need confirmation. |
| Are we prepared for platform changes? | SuiteScript and API dependencies, authentication methods, release notices, vendor support, and regression tests. | A dependency list is recommended. Release deadlines and compatibility have not been checked in this sample. |
| Can someone else support the system? | Owners, documentation, source history, sandbox use, change review, recovery steps, and support handoffs. | Ownership and recovery gaps documented in 06; backup-administrator exercise recommended. |
Depending on what your business uses, the review may also cover revenue recognition, subscriptions, projects, manufacturing, advanced inventory, tax integrations, and multi-subsidiary consolidation. This sample shows the report format; it does not cover every NetSuite feature.
Follow an order through the business.
42Active users
28Custom scripts
14Active workflows
4External connections
The sample account has two subsidiaries, three inventory locations, and four external connections: a web store, a warehouse, a billing platform, and a reporting export.
Web store → order connector → NetSuite sales order.
Approval dependencies ↓Review workflow + defaulting script → warehouse release search.
Finding 01 · Conflicting logicWarehouse event → fulfillment import → item fulfillment.
Finding 02 · Duplicate eventInvoice → nightly export → billing acknowledgment.
Finding 04 · Missing alert| Component | Record or identifier | Dependency and purpose | Accountable team |
|---|---|---|---|
| Sales order reviewWorkflow | customworkflow_ex_so_review | Reads order amount; writes the custom review status used for release. | Finance |
| Order defaultsUser Event script | customscript_ex_so_defaults | Runs on order edits; also writes the review status. | NetSuite administration |
| Warehouse fulfillmentMap/Reduce script | customscript_ex_wms_fulfill | Reads warehouse events and creates item fulfillments. | Integrations |
| Billing exportScheduled script | customscript_ex_invoice_export | Exports invoices and records destination acknowledgments. | Owner to confirm |
| Receivables dashboardSaved search | customsearch_ex_ar_dashboard | Summarizes open invoices and joins customer contacts. | Finance |
Full sample inventory: 28 scripts across 37 deployments, 14 active workflows, 18 custom record types, 86 saved searches (23 scheduled), and 4 external connections. The table above shows the components tied to this review’s findings.
See the problem, the impact, and the next step.
Eight findings, each connected to a business process, supporting evidence, an owner, and a way to verify the correction. Open a finding to read the details.
3 High Transaction or access controls to address first. 4 Medium Reliability, reporting, data, and performance. 1 Low Documentation and continuity.
High01 · Order edits can bypass the approval policyChanged orders can reach the warehouse without the approval they now require.
- What we found
- In the sample’s 40 edited sales orders, 8 moved from below the $10,000 approval threshold to above it while the custom review status still showed Approved. A sandbox replay reproduced the behavior.
- Why it happens
- The workflow
customworkflow_ex_so_reviewchecks the amount when the order is created. A User Event script,customscript_ex_so_defaults, restores the previous value ofcustbody_ex_review_statuson edit. The two automations write the same field without a shared rule for reapproval. - What it means for you
- The warehouse release search treats that custom status as authorization to ship. An order can therefore be released using an approval that covered a smaller amount.
- Recommended action
- Give one automation ownership of the review status. Reset it to Pending Review when the order total, customer, or payment terms changes in a way that requires reapproval. Update the release search to use the corrected approval control.
- How to verify the fix
- Test orders below, at, and above $10,000; then change amounts, customers, and terms through the UI and the connected order flow. No order requiring reapproval should appear in the warehouse release queue until a new approval is recorded.
- Who should own it
- Controller + NetSuite administrator
- Evidence reference
- E-01 · View the sample evidence register
Example evidence
Illustrative trace · SO-10482
09:14 — Order approved at $8,400.
10:02 — Order edited to $12,600.
10:02 — The script retains Approved; the release search includes the order.
Expected: Pending Review, with shipment release withheld.
High02 · A retried warehouse message can create a second fulfillmentOne warehouse shipment can be recorded more than once.
- What we found
- The sample of 120 warehouse messages includes 6 repeat deliveries. In controlled sandbox replay, 2 of those repeated messages created a second item fulfillment for the same shipment event.
- Why it happens
- The Map/Reduce script
customscript_ex_wms_fulfillcreates the fulfillment before acknowledging the warehouse message. It does not reliably recover a previously created fulfillment if the run stops between those steps. - What it means for you
- Duplicate fulfillment records can distort shipped quantities and inventory and require manual correction. This example demonstrates the defect in sandbox; it does not assume a production financial loss.
- Recommended action
- Use a stable shipment-event identifier, retain its processing state, and link it to the resulting fulfillment. Handle overlapping executions and recovery after a record is saved. Resolve an existing result before attempting another fulfillment.
- How to verify the fix
- Replay the same event sequentially and concurrently, then interrupt processing immediately after the fulfillment is saved. Each scenario must leave one valid fulfillment and one traceable completed event.
- Who should own it
- Integration owner + warehouse operations
- Evidence reference
- E-02 · View the sample evidence register
Example evidence
Illustrative event · WH-48291
First attempt: fulfillment saved; acknowledgment interrupted.
Second attempt: message retried; another fulfillment created.
Expected: The retry finds the existing result and completes the acknowledgment.
High03 · An operations role combines vendor changes with payment entryAn operations role can change vendor payment information and enter payments.
- What we found
- Seven of the 42 active users have the sample Operations Supervisor role. Role testing shows that it can both change vendor payment details and enter vendor payments. Only two of the seven users have documented finance duties.
- Why it happens
- Finance access was added to the shared operations role during temporary coverage and retained after that coverage ended. The role no longer matches the intended responsibilities.
- What it means for you
- One role can change where a payment goes and record a payment without the intended separation of duties. Access is broader than the business requirement; the review does not allege misuse.
- Recommended action
- Separate operations and finance access, define who can maintain vendor payment information, and require an independent review of sensitive changes. Test the narrower roles before removing access required for daily work.
- How to verify the fix
- The operations role can still complete receiving and fulfillment tasks but cannot perform the identified finance actions. An authorized finance role and its reviewer can complete the approved payment process.
- Who should own it
- Controller + access administrator
- Evidence reference
- E-03 · View the sample evidence register
Medium04 · Invoice export failures have no accountable ownerInvoices can be missing from the receiving system without anyone being alerted.
- What we found
- Nine of the sample’s 30 nightly billing export runs contain partial or failed results. Destination acknowledgments are missing for 14 invoices. The run summary does not notify an actively monitored mailbox.
- Why it happens
- The scheduled export records individual errors but does not reconcile the sent and accepted invoice counts. Its operating instructions list a former employee as the escalation contact.
- What it means for you
- Finance can see invoices in NetSuite that the receiving billing platform has not accepted. Staff discover the exceptions during customer follow-up.
- Recommended action
- Add a run summary with sent, accepted, and failed counts; a queue of invoice-level exceptions; a named primary and backup owner; and a documented retry process that checks destination acknowledgments.
- How to verify the fix
- Force one successful export, one partial failure, and one unavailable destination. Confirm alerts reach the assigned owner, failed invoices remain visible, and retries do not create duplicate destination records.
- Who should own it
- Finance operations + integration owner
- Evidence reference
- E-04 · View the sample evidence register
Medium05 · The receivables dashboard counts some invoices twiceThe sample dashboard overstates open receivables by $18,420.
- What we found
- In the 50-invoice sample, 12 invoices appear twice in the dashboard’s source search. The dashboard shows $242,600 against a reference receivables total of $224,180: a difference of $18,420.
- Why it happens
- The custom search
customsearch_ex_ar_dashboardjoins invoice rows to multiple customer contacts, then sums the remaining amount. The comparison uses the same subsidiary, USD currency, date, and invoice population. - What it means for you
- The dashboard overstates open receivables for the sample population and sends collections staff back to the underlying reports to determine the correct balance.
- Recommended action
- Keep financial aggregation at one row per invoice. Separate contact information from the balance calculation, and document the date, subsidiary, currency, and status filters used for reconciliation.
- How to verify the fix
- Each sample invoice appears once; the total equals $224,180 with a $0 unexplained difference. Repeat the comparison for an additional period and customer set before release.
- Who should own it
- Controller + reporting owner
- Evidence reference
- E-05 · View the sample evidence register
Low06 · Key customizations depend on undocumented knowledgeA staff change can leave critical automation without a clear owner or recovery steps.
- What we found
- Eleven of the 28 scripts have no confirmed business owner in the sample inventory. Six lack a usable operating or recovery procedure. File names alone do not explain their dependencies.
- Why it happens
- Customizations were added by different teams over time without a maintained inventory linking the business purpose, deployment, owner, and recovery steps.
- What it means for you
- Routine changes and staff absences take longer to manage because someone must rediscover what the script does and which processes rely on it.
- Recommended action
- Complete a customization register with purpose, script and deployment IDs, triggers, records read and written, dependencies, owner, and recovery instructions. Start with order release, fulfillment import, and billing export.
- How to verify the fix
- A backup administrator can explain each of the three critical flows, locate its logs and configuration, and follow a sandbox recovery exercise without relying on the original author.
- Who should own it
- NetSuite administrator + process owners
- Evidence reference
- E-06 · View the sample evidence register
Medium07 · Duplicate supplier records make purchasing harder to controlStaff must work out which record contains the current terms and transaction history.
- What we found
- In the fictional 200-vendor sample, seven candidate pairs were flagged. Finance confirmed four as duplicate representations of the same supplier; three still need investigation.
- Why it happens
- Different teams create vendor records without a consistent identity check or named data steward. A matching name alone is not enough to establish that two suppliers are the same.
- What it means for you
- Purchasing staff can select an outdated record, split supplier history, and use inconsistent terms. This finding does not establish that a duplicate payment occurred.
- Recommended action
- Assign a vendor-data owner; validate identity, subsidiary use, open transactions, terms, and connected-system mappings; then decide how to consolidate or retire confirmed duplicates. Test the chosen approach with Finance before changing live records.
- How to verify the fix
- The four confirmed pairs have an approved disposition, relevant transaction history remains traceable, and the purchasing team can identify the correct active record. Review new records for repeated duplication.
- Who should own it
- Accounts payable lead + data steward
- Evidence reference
- E-07 · Vendor comparison and validation log
Medium08 · Repeated searches slow down order entryThe sample isolates avoidable work in a customization that runs when an order is saved.
- What we found
- In 20 paired sandbox tests using the same role, form, and representative orders, median save time was 8.4 seconds. A diagnostic version that removed duplicate lookups and narrowed the search filters reduced the median to 5.1 seconds.
- Why it happens
customscript_ex_so_defaultsretrieves the same customer-order data twice during a save and reads more records than the decision requires. Timing traces connect that work to the delay.- What it means for you
- Order-entry staff wait on avoidable processing during routine work. These controlled sample measurements are not a prediction of savings or a production performance guarantee.
- Recommended action
- Reuse the lookup result, restrict the data retrieved, and retain every required validation. Coordinate with the approval correction in finding 01 because both changes touch the same script.
- How to verify the fix
- Repeat the same paired test set, confirm unchanged order and approval results, and measure a representative busy period. Release only after the process owner accepts both behavior and timing.
- Who should own it
- NetSuite developer + sales operations
- Evidence reference
- E-08 · Order-save timing and behavior tests
Get more from the system you already use.
Some improvements need a simpler process, an existing feature, or training rather than new development. We would check these two ideas with the sample company before recommending either as a project.
Make billing exceptions part of the daily routine
Sample observation: Finance exports invoice lists into a spreadsheet to find missing billing acknowledgments.
Opportunity: Evaluate a shared exception view using the account’s existing searches and dashboard tools, with a named daily owner and a short operating guide.
Success measure: Compare the time spent checking invoices and the number of unresolved exceptions before and after a pilot. Correct export handling in finding 04 first.
Check native functionality before adding another customization
Sample observation: Purchasing maintains a separate reorder spreadsheet and has requested another custom automation.
Opportunity: Check the company’s item data, enabled inventory capabilities, license entitlements, and purchasing needs. Demonstrate a native option where it fits and identify the remaining gaps.
Success measure: A buyer completes a representative replenishment scenario and understands any exceptions. Include training and data cleanup in the decision.
What to tackle first.
These are proposed planning windows for the sample company. Owners confirm timing after the changes and their dependencies are understood.
| Sequence | Work and owner | Completion evidence |
|---|---|---|
| First 30 daysControl the exposure | Controller: correct reapproval and access separation (01, 03). Integration owner: correct duplicate-event handling (02). | Boundary and edit tests pass; replay and restart tests create one fulfillment; approved roles pass the access matrix. |
| Days 31–60Make exceptions visible | Finance operations: reconcile export acknowledgments and assign alert ownership (04). Reporting owner: correct the AR search (05). AP lead: validate duplicate suppliers (07). Developer: improve order-save performance after the approval correction (08). | Forced failures produce actionable alerts; retries reconcile; AR totals agree; vendor decisions are recorded; order timing improves without changing approvals. |
| Days 61–90Make the system maintainable | NetSuite administrator: complete ownership, dependency records, and recovery instructions for the critical flows (06). | A backup administrator completes the documented sandbox recovery exercises. |
| Work item | Effort | Dependency and client decision |
|---|---|---|
| Approval control · 01 | Medium | Controller confirms the approval policy and accepts the changed-order tests. |
| Warehouse retries · 02 | Higher | Warehouse vendor supplies event identifiers and supports interruption and replay tests. |
| Role separation · 03 | Medium | Finance and Operations confirm duties and test the replacement roles. |
| Billing alerts · 04 | Medium | Destination acknowledgments are available and primary/backup owners are assigned. |
| Receivables search · 05 | Lower | Finance signs off the reference report and matching filters. |
| Documentation · 06 | Medium | Process owners validate the register; a backup administrator tests the instructions. |
| Vendor data · 07 | Medium | AP validates identities and downstream mappings before any record changes. |
| Order performance · 08 | Medium | Coordinate with 01; repeat behavior tests and agree the measurement approach. |
Lower effort means a small change with few dependencies. Medium effort includes configuration or code changes and testing with the process owner. Higher effort involves several systems and recovery testing. We include savings estimates and project prices when there is enough information to support them.
Release and recovery
Record the existing configuration, test the revised behavior with the process owner, and define a rollback before each change. After release, reconcile affected transactions and retain the test results with the system documentation.
The detail behind the conclusions.
Each finding links to the records and tests behind it. The entries below show how those references appear in a report; they are fictional, not client records.
E-01 · Approval behavior
Workflow definition; User Event source and deployment; System Notes for 40 edited orders; sandbox replay of the threshold-crossing case. Links to finding 01.
E-02 · Warehouse processing
120 message records; fulfillment mapping; script execution logs; controlled replay and interruption results for 6 repeat messages. Links to finding 02.
E-03 · Access matrix
42 active user assignments; the shared operations role; confirmed job responsibilities; sandbox tests of vendor changes and payment entry. Links to finding 03.
E-04 · Billing reconciliation
30 nightly run summaries; invoice export results; destination acknowledgments; exception handling and alert routing configuration. Links to finding 04.
E-05 · Receivables comparison
Saved search definition and join structure; 50-invoice comparison; reference receivables report using matching filters; sandbox results after removing the duplicate-producing join. Links to finding 05.
E-06 · Ownership register
28 scripts and 37 deployments; owner interviews; operating instructions; dependency records for order release, fulfillment import, and billing export. Links to finding 06.
E-07 · Vendor identity review
200 vendor records; seven flagged pairs; Finance’s disposition of four confirmed duplicates and three unresolved candidates; subsidiary, terms, and integration-mapping checks. Links to finding 07.
E-08 · Performance comparison
20 paired sandbox runs; consistent role, form, and representative orders; save-time observations; script timing traces; diagnostic change; matching business-result checks. Links to finding 08.
Open questions to carry forward
Still to check: how long billing acknowledgments are kept, who owns the export, remaining role and authentication tests, and purchased NetSuite features. The finance processes and platform dependencies listed as open also need review. These items remain open until checked.
Documentation included in this example
- Executive summary and prioritized findings
- Process and integration dependency map
- Customization and ownership register
Working records for the team
- Evidence index and transaction sample list
- List of fixes and who is responsible
- Acceptance tests and recovery instructions
NetSuite reference material
System Notes and workflow activity help trace changes; Map/Reduce restart behavior informs duplicate-processing tests. These Oracle references explain the methods, not the fictional findings.
Transaction System NotesWorkflow activityMap/Reduce error handling
System Notes and workflow activity help trace changes; Map/Reduce restart behavior informs duplicate-processing tests. These Oracle references explain the methods, not the fictional findings.
Transaction System NotesWorkflow activityMap/Reduce error handling
What would you like to understand about your NetSuite?
Tell us what takes too long, which numbers you question, or what you’ve inherited. We’ll trace those problems through your NetSuite setup.
You’ll receive a written review and a walkthrough of the findings, so your team can ask questions and decide what to do next. Ebenstead can help carry out the recommendations when you’re ready.
Request a Systems ReviewNetSuite Systems Review
Our introductory offer brings the standard review to $1,000.
Standard review
$1,000
Introductory priceFor a typical environment with a focused set of processes.
- Business processes and responsibilities
- Configuration, customizations, and integrations
- Operating instructions, risks, and recommendations
- Editable documentation and PDF
Advanced review
$10,000–$15,000
For more departments, automation, and integrations.
- Cross-department process maps
- Technical dependencies and exception handling
- Finance and close procedures
- Prioritized recommendations
Large environments
Custom quote
For extensive OneWorld setups, hundreds of scripts, or unusually complex operations.
- System inventory and scope review
- Phased work where needed
- Process-owner review
- Agreed delivery milestones
We document the agreed scope in depth and identify anything we couldn’t verify. Full code reviews and third-party system reviews are included only when specified.
What your team takes away
How the business runs
Process maps, responsibilities, approvals, transaction flows, close procedures, and instructions for recurring tasks.
How the system fits together
Account structure, roles and permissions, scripts, workflows, custom records, integrations, and dependencies.
What to improve
A record of risks and system problems, with recommendations in priority order. We’ll review the findings with your team.
Documentation you can keep
Editable documentation and a PDF, plus a walkthrough of the findings with your team. Use the recommendations to plan work internally or discuss the next steps with Ebenstead.
From your questions to a practical plan
01
Start with your priorities
Talk through what slows your team down, which numbers you question, and what you need the business to do next.
02
Follow the evidence
Walk through the work with your team, inspect the relevant setup, and trace transactions, customizations, and connected systems.
03
Leave with clear next steps
Review the findings with your team, answer questions, and agree on priorities, owners, and how each fix should be tested.
Before you request a review
Is this useful if our NetSuite mostly works?
Yes. A review can document a system your team has inherited, explain recurring workarounds, or help you prepare for growth. Findings should also identify what is working and worth keeping.
What will you need from our team?
We’ll need your main questions, a walkthrough with the people who use NetSuite, existing documentation, and access to the relevant account information.
Does the review include making changes?
The review documents the current system and recommends improvements. Any implementation work is discussed separately; the action plan helps you decide which changes are worthwhile.
How do we get started?
Send us a request with what you want to understand or improve. We’ll reply to discuss your setup and how the review would work.
Ready to get your system documented?
Tell us about your NetSuite and where you need a clearer picture.
Request a Systems Review