Guides / NetSuite & ERP

NetSuite workflow diagrams: SuiteFlow, approvals & custom record flows

A NetSuite workflow diagram is a visual representation of a SuiteFlow workflow — the configured approval chain, state machine, or automation that NetSuite runs on records like sales orders, purchase orders, vendor bills, expense reports, and custom records. The diagram captures every state, transition, condition, and action so auditors and admins can trace exactly what NetSuite did and why.

SuiteFlow explained

SuiteFlow is NetSuite's point-and-click workflow engine. A SuiteFlow workflow runs on a specific record type, defines a set of states (Pending Approval, Approved, Rejected, etc.), and uses transitions triggered by conditions or user actions to move records between states. Inside a state, actions can send emails, set field values, lock fields, or call SuiteScript.

A workflow diagram visualizes that state machine, plus the underlying conditions — which is the artifact auditors actually want to test.

Diagramming approval chains

The most common SuiteFlow pattern is a multi-level approval (vendor bills, purchase orders, expense reports, journal entries). A clean approval-chain diagram shows:

  • Trigger event (record submitted)
  • Initial routing logic (by amount, department, location)
  • Each approver level with role and amount threshold
  • Decision diamonds for approve / reject / route-back
  • Final state (Approved → posts to GL) and audit trail

Swimlanes by role (Submitter, Manager, Controller, CFO) make the segregation of duties immediately visible.

Custom record flows

NetSuite's strength is custom records — bespoke entities for whatever your business actually does. SuiteFlow on a custom record looks identical to SuiteFlow on a native record, but auditors are less likely to know the schema, so the diagram needs to spell out:

  • Custom record name and purpose
  • Key fields used by the workflow (amount, status, owner)
  • Any SuiteScript User Event scripts that interact with the workflow
  • Saved searches or reports that surface state

Order-to-Cash in NetSuite

A typical NetSuite O2C workflow chain:

  1. Sales Order created — credit limit hold check (workflow)
  2. Customer Deposit (optional) → cash received
  3. Item Fulfillment — inventory commit, picking, packing
  4. Invoice created — revenue recognition rules applied
  5. Customer Payment applied — A/R cleared
  6. Bank Deposit / lockbox match

Mark the credit-limit hold and the revenue-recognition step as key controls for SOX-relevant implementations.

Common NetSuite workflows worth diagramming

  • Vendor Bill approval (3-way match + amount thresholds)
  • Purchase Order approval with delegation of authority
  • Expense Report approval with policy violation routing
  • Journal Entry approval (especially manual JEs at month-end)
  • Customer credit hold / release
  • Item Receipt → inventory adjustment exception handling
  • Period close lockdown sequence

Each one becomes a single-page swimlane diagram, version-controlled in your QMS or SOX documentation set.

Frequently asked questions

Where do I find the SuiteFlow definition for an existing workflow?

Customization → Workflow → Workflows. Each workflow shows its states, transitions, and actions visually inside NetSuite, but the in-product diagram doesn't export cleanly for documentation. Most teams rebuild the diagram in an external tool to control formatting, version it in their QMS, and annotate it with audit metadata.

How do I document SuiteScript that interacts with a workflow?

Add a note on the relevant transition or action box indicating the script ID, the deployment, and the event type (Before Submit, After Submit, Scheduled, etc.). Link the box to the script documentation. If the script enforces a key SOX control, mark it the same way you mark a SuiteFlow control.

Do auditors accept NetSuite's built-in workflow diagrams?

They accept them as supporting evidence, but rarely as the primary control documentation. The in-product view doesn't show segregation of duties via swimlanes, doesn't carry audit metadata (effective date, version, approver), and doesn't reconcile to your risk-and-control matrix. A purpose-built diagram outside NetSuite is the standard practice.

How granular should NetSuite workflow diagrams be?

One workflow per diagram, with every state and every transition shown explicitly. Don't combine multiple workflows into a single mega-diagram — that obscures the state-machine logic auditors need to trace. If two workflows interact (e.g., PO approval feeds Vendor Bill approval), use a top-level overview diagram with arrows between the two child workflows.

Can I generate NetSuite workflow diagrams from a spreadsheet?

Yes. Querychart accepts a structured spreadsheet that mirrors SuiteFlow's state-transition model — one row per transition with from-state, to-state, condition, action, and role — and produces a clean swimlane workflow diagram. When you change the workflow in NetSuite, you update the rows; the diagram refreshes.

Can I generate these diagrams from a spreadsheet?

Yes. Querychart turns a structured spreadsheet (one row per step, with role, action, and decision columns) into a connected swimlane flowchart automatically. When the process changes, you edit the row and the diagram updates — no manual redrawing.

Generate your NetSuite process flowchart from a spreadsheet in Querychart →