ION Factory OS
  • Welcome to ION
  • Features
    • Procedures
      • Steps
        • Content
        • Datagrid
        • Fields
        • Attributes
      • Dependencies
      • Part-Procedure Relationship
      • Attributes
      • Standard Steps
      • Installation Requirements (Beta)
      • Nested Steps and Nested Standard Steps
      • Procedure Best Practices
    • Runs
      • Run Execution Overview
      • Runs And Step States
      • Batching Runs
        • Batching 2.0 Changes
      • Workcenter execution
      • Split Inventory on a Run
      • Redlines
      • Export run data
      • Scheduling runs
      • Time Tracking
      • Attributes
      • Outside Processing
      • Runs Best Practices
    • Parts Library
      • As-built Bill of Materials (aBOM)
        • Editing aBOM build requirements
        • aBOM Beta Changes
          • aBOM actions for developers
      • Inventory
        • Inventory status
        • Inventory splitting
        • Inventory merging
        • Inventory scrapping
        • Kitting
        • Inventory Movement Automations
      • Manufacturing bill of materials (mBOM)
        • mBOM versions
        • Made on Assembly (MOA)
        • Part Substitutes
        • Reference designators
      • Part Attributes
      • Part revision interchangeability
      • Supplier Part Numbers & Purchase Unit Conversions
    • Kitting and Inventory Fulfilment
      • Kit Statuses and Workflows
      • Inventory requests
      • Kitting and runs
      • Fulfilling Multiple Kits
      • Kanban Kitting
    • Purchasing
      • Purchase Orders
        • Types of Purchases
        • Purchase Order Approvals
        • Purchase Order FAQs
        • Supplier Part Numbers & Unit Conversions
        • PO Requirements, Terms, and Quality Clauses
      • Receiving/Inspection
      • Outside Processing
      • Consigned Parts
    • Barcode Labels
      • Templating
        • ION barcode minimum sizes
        • Sample templates
      • Printing
        • Configuring Zebra Browser Print
        • Server Based Barcode Printing (PrintNode)
      • Scanning
        • Scan barcodes from other systems
    • Quality
      • Issues
      • Further Actions - CAPA
      • Issues States, Dispositions, and Resolutions
      • Quality Best Practices
    • Tools
    • Locations
    • Attributes
    • Labels
      • Deleting labels
    • Notifications
    • Search
    • Settings
      • Role based access control
        • Full Glossary of ION Permissions
    • ION Actions
      • ION Actions examples for Quality
      • ION Actions examples for Runs and Procedures
      • ION ACTIONS examples for Supply Chain
  • Analytics
    • Inventory valuation
    • Part impact analysis
    • Users, Roles, Teams
    • Analytics FAQ
    • Data Connector
    • Data Products
  • Plans and Autoplan
    • Autoplan
    • Autoplan glossary
    • Preparing to use Autoplan
    • Clear to build reporting
    • Running Autoplan on a schedule
    • Firm and blocked plan items
    • Location constraints
    • Autoplan suggested suppliers and procedures
    • Reorder point
    • Plan input serial numbers
    • Applying a calendar
    • Plan Reservations
    • Independent schedules
    • Drive demand from kits
    • Drive demand below buy parts configuration
    • Group plan items with the same date
    • Manualy Changing Autoplan Status
  • API
    • How to create an App with ION
    • Access Tokens
    • About GraphQL
    • Interactive API explorer
    • API Keys
    • Examples
      • Notifications
      • Runs
      • Automatically updating fields in runs
      • Parts and Part Revisioning
      • mBOMs
      • Part Inventory and Kitting
      • aBOM (As-built Bill of Materials)
      • Edit time-tracking session data
    • Changelog
    • Webhooks
    • Pagination
  • Automations
    • Auto-checkout of Run Steps
    • Auto-Consumption of Lineside Inventory
    • Automatically Send Purchases to Suppliers
    • Set Close by Run Step on Issue Creation
    • Intent Management / Grade / Tier / Pedigree
      • Data Imprinting
      • ION Actions for Intent
    • Auto-Update mBOM Revision on Part Revision Update
    • Auto-approve part-procedure relationships
    • Purchase Order PDF and Versions
    • Auto Populate PO Line Attributes
    • Imprint Attributes from One Object to Another on a Desired Event
  • Integrations
    • Deploying Integrations and Automations
    • Arena
    • Cofactr
    • Datum
    • Duro
    • NetSuite
      • Purchasing in NetSuite, Receiving in ION
      • Work Order/Assembly Builds
    • Procurable
    • PDF Generator
    • Quickbooks
    • Ramp
    • Silkline Integration
    • Slack
    • Smartsheet
    • SOLIDWORKS
    • Teamcenter
  • Training
    • Standard Operating Procedures
      • Cycle Counting
      • Tool Utilization
    • Guided Flows
    • ION Sandbox
    • Chat Support for ION
  • Troubleshooting
    • Resetting your password
    • Resetting your Multi-Factor Authentication
    • You have no roles... error
  • Changelog
  • Adminstration
    • Security
      • Backups and Security FAQ
      • Single Sign-On (SSO)
        • Okta SAML connection setup
      • Export Control
      • Report Generator Disclaimer
    • Browser and Device Compatibility
    • Authentication
      • My company is new to ION, logging in for the first time.
      • I'm told I'm not authorized to access the application
      • My account has been deactivated
    • Login Page
  • Tickets Portal
Powered by GitBook
On this page

Was this helpful?

  1. Integrations

NetSuite

PreviousDuroNextPurchasing in NetSuite, Receiving in ION

Last updated 6 months ago

Was this helpful?

Please note that the Netsuite integration is available as a paid add-on. Contact your customer success manager to learn more about pricing and how to enable the Netsuite integration for your account.

NetSuite is a comprehensive cloud-based ERP solution that offers businesses a robust platform for managing their finance, operations, and customer relations. For companies utilizing ION to manage manufacturing processes and workflows, integrating with NetSuite can significantly enhance data visibility, streamline operations, and consolidate financial reporting. This integration bridges the operational efficiency of ION with the financial intelligence and scalability of NetSuite, empowering businesses to achieve a holistic view of their operations and strategic financial outcomes. However, the integration between ION and NetSuite is not a one-size-fits-all solution; it requires careful configuration to align with specific business needs and the existing setup of NetSuite. Tailored integration ensures that organizations can maximize the benefits of both systems, making critical business data actionable and enhancing operational decisions.

Recommended System Configuration

High-level goals of the integration:

  1. Billing integration with proper 3-way matching functionality

  2. AP/AR/GL tracking

  3. Accurate cost of goods sold (COGS) for make parts (labor and materials)

  4. Controlled sales order process

When thinking about how your systems interact it is important to define a business process "swimlane." The swimlane should contain key business processes and in which system you desire them to be performed. Here is a common NetSuite<>ION business process swimlane:

In the above example, Business A wishes to do all their factory operations like purchasing, receiving, warehouse management, work order execution, etc... in ION and use NetSuite for sales, employee configuration, vendor onboarding, billing, etc... The two systems need to talk to one another to ensure the right data is available to perform said processes.

Once you have a high-level idea of your business processes and where they will be performed it is helpful to understand how and where the systems will interact & the level of detail required to be pushed between systems. Here is an example NetSuite configuration diagram based on tried and true business practices & with the simplicity/reliability of the integration in mind:

In the above diagram, ION handles everything from plans to work order execution. Telling NetSuite when it makes purchase orders, consumes material on runs, and scraps material due to quality defects. An (optional) addition to the software stack is a PLM to manage engineering development and part release. The PLM sends parts to both systems, and BOMs to ION, so that activities can happen on the ION side and GL configuration can happen on the NetSuite side. A few additional notes:

  1. Sales orders, created in NetSuite, transfer over to create Autoplan inputs

  2. Purchase orders are generated from plans in ION. These purchase orders are duplicated on the NetSuite side to add inventory to the system and to enable billing

  3. Receiving activities in ION to generate item receipts in NetSuite to enable a 3-way match

  4. Billing activities can take place in NetSuite

  5. Runs are generated from ION plan items using procedures. Runs can generate workOrder objects in NetSuite (optional) or upon run completion an assemblyBuild record can be generated to put assemblies into NetSuite at cost (labor and materials)

  6. When material is scrapped in ION, the material is scrapped in NetSuite

  7. Both systems have inventory but ION maintains the granular location-based tracking & NetSuite has a bucketed view. Doing so gives finance teams a simplified, yet accurate, view of inventory. Bucketizing the inventory in NetSuite also greatly simplifies the integration between the two systems.

Remember, this is our recommended flow and can be altered based on the preferences of your business. We recommend this flow for its simplicity and efficiency although we have seen other customers be successful with other configurations.

In the following pages, we outline the details of various flows.