A broken approval chain costs more than time. When a $40,000 purchase order sits in limbo because the designated approver left the company, or an expense report bypasses the finance controller because two conflicting workflows fired simultaneously, the downstream impact reaches month-end close, vendor relationships, and audit trails. Configuring a NetSuite purchase order approval workflow correctly inside NetSuite ERP means building routing logic that accounts for org structure, subsidiary boundaries, role changes, and escalation windows from day one. This guide covers the full configuration sequence for purchase order, expense report, and custom transaction approvals using SuiteFlow, the native workflow engine inside NetSuite. You will find step-by-step setup instructions, routing patterns for multi-subsidiary organisations, and a reference table of the most common misconfiguration errors and their fixes.

High-angle view of a person filling out forms on a clipboard, emphasizing paperwork and documentation.

How NetSuite Approval Workflows Work: SuiteFlow vs Standard Approval Routing

NetSuite offers two approval mechanisms that operate independently and must not be run in parallel on the same record type.

Standard Approval Routing is a simplified rule set configured at Setup, Accounting, Accounting Preferences. It supports basic supervisor chains and spend thresholds but has no branching logic, no conditional state transitions, and no way to route by subsidiary, department, or custom field value. For organisations with more than one approval tier or any subsidiary complexity, standard routing hits its limits quickly.

SuiteFlow (Workflow Manager) is NetSuite’s full workflow engine, accessible at Customization, Workflow, Workflows. It models approval processes as state machines: each state represents a point in the process (Draft, Pending Approval, Approved, Rejected), and transitions move a record between states based on conditions, user actions, or scheduled triggers. Each state can carry actions such as sending email notifications, updating field values, creating tasks, or locking the record for editing.

CapabilityStandard Approval RoutingSuiteFlow
Multi-tier approval chainsLimited to supervisor hierarchyUnlimited states and transitions
Conditional routing by department or subsidiaryNot supportedSupported via condition groups
Spend threshold branchingSingle global thresholdPer-state conditions on any field
Email notifications on state changeBasic notification onlyCustomisable template per action
Escalation after inactivityNot supportedScheduled actions with time-based triggers
Audit trail in recordStatus field onlyFull execution log on System Information subtab

For most mid-market NetSuite deployments, SuiteFlow is the correct tool. Standard approval routing may be appropriate only for single-entity, single-tier setups where no conditional logic is needed.

Disabling Standard Approval Routing Before Using SuiteFlow

This step is non-negotiable. Running both mechanisms on the same record type produces duplicate approval requests, conflicting status updates, and audit logs that do not reflect the actual decision path.

To disable standard approval routing, navigate to Setup, Accounting, Accounting Preferences. Look for the Approval Routing section. You will see checkboxes for each transaction type: Purchase Orders, Expense Reports, Vendor Bills, and others. Uncheck each type you intend to manage with SuiteFlow, then save.

Disabling standard routing does not affect records already in an approval state. For records mid-process at the time of the change, complete or cancel them manually before switching. For new records created after the change, SuiteFlow takes full control of the approval cycle.

If you are migrating from standard routing to SuiteFlow on a live account, schedule the switchover during a low-volume period, communicate the change to approvers in advance, and verify the SuiteFlow workflow is published and set to trigger on record creation before disabling the standard setting.

Building a Purchase Order Approval Workflow Step by Step

The following sequence produces a working NetSuite purchase order approval workflow with two approval tiers and a rejection path. Adjust state names and conditions to match your organisation.

1. Create the Workflow

Go to Customization, Workflow, Workflows, New. Set Record Type to Purchase Order. Set the trigger to Before Record Submit for the initial state transition, and use After Record Submit for notification actions so the record ID is available. Name the workflow clearly, for example PO Approval Routing v1. Set Status to Testing until the workflow is verified in sandbox.

2. Define States

Create four states: Draft, Pending Level 1 Approval, Pending Level 2 Approval, and Approved. Add a Rejected state as a terminal state. The initial state should be Draft, entered when a new PO is created.

3. Configure the Draft to Pending Level 1 Transition

Add a transition from Draft to Pending Level 1 Approval. Set the trigger to Record is Saved and add a condition: Status equals Pending Approval (this is the value NetSuite sets when a submitter clicks Submit for Approval). In the transition actions, add a Send Email action using the standard Approval Request template and set the recipient to the field Supervisor on the Employee record of the person who created the PO.

4. Configure Level 1 Approval Actions

In the Pending Level 1 Approval state, add two user event actions triggered by a button: Approve and Reject. For the Approve button on records below your spend threshold (for example, under $10,000), add a transition directly to Approved. For records above the threshold, transition to Pending Level 2 Approval. For the Reject button, transition to Rejected and send a notification email to the PO creator.

5. Configure Level 2 Approval

Mirror the Level 1 configuration, routing to the appropriate senior approver field. On approval, transition to Approved and set the Approval Status field to Approved. On rejection, transition to Rejected.

6. Lock the Record in Approved State

In the Approved state, add a Set Field Value action that sets the record to a locked or read-only status where appropriate. This prevents post-approval edits without a formal amendment process.

Consult the NetSuite implementation guide for a full reference on workflow permissions and record locking options during initial configuration.

Overhead view of hands highlighting financial documents on a desk.

Configuring Expense Report Approval Chains

Expense report approval in NetSuite follows the same SuiteFlow framework, but the record type, field references, and common routing patterns differ from purchase orders.

Record Type and Trigger

Set the workflow record type to Expense Report. The standard submission trigger is when the employee clicks Submit, which sets Status to Pending Approval. Your workflow condition on the Draft-to-Pending transition should match this status value.

Routing by Amount

A common configuration routes low-value expense reports (under $500) directly to the employee’s immediate supervisor and routes higher amounts to the department head or finance controller. In SuiteFlow, create a branch on the outgoing transition from Draft. Add a condition group: if Amount is less than 500, route to Supervisor field. If Amount is greater than or equal to 500, route to a custom Department Controller field on the Department record.

Policy Violation Flags

If your organisation uses expense categories with maximum amounts or restricted vendor types, you can add a condition check before the approval state transition. If a violation flag custom field is set to True, route the report to a compliance review state before standard approval. This creates a documented review trail without manual intervention.

Reimbursement Trigger

After the Approved state is reached, add a Create Record action that generates a vendor payment or journal entry, depending on your payroll and reimbursement process. Alternatively, add a notification to the Accounts Payable team with the approved expense report link.

Advanced Routing: Subsidiary-Based and Role-Based Approvals

Multi-subsidiary NetSuite accounts require routing logic that does not depend on named employees. Personnel changes break named-employee routing immediately; field-referenced and role-based routing adapts without workflow edits.

Subsidiary-Based Routing

At the first branching point after the initial submission state, add a condition group that checks the Subsidiary field on the transaction. Create a separate transition for each subsidiary, each routing to a custom Regional Controller or Subsidiary Approver field stored on the Subsidiary record. When the controller changes, the Subsidiary record is updated once and all in-flight and future approvals route correctly.

Role-Based Routing

Rather than routing to an employee field, route to a role. In the Send Email action or Create Task action, set the recipient to a role such as AP Manager or Regional Controller. NetSuite delivers the notification to all active users holding that role. This is more resilient than field references for organisations with frequent staff changes, though it means multiple people receive the notification and must coordinate on who acts.

Hybrid Approach

A practical pattern for most mid-market accounts: use field references (Supervisor, Department Head field) for the primary routing, and fall back to a role for the escalation action. If the primary approver does not act within the escalation window, the task routes to the role, ensuring it is never left unattended.

Approval Actions: Email Notifications, Field Updates, and Escalations

Each state in a SuiteFlow approval workflow can carry multiple action types. Understanding which action type to use and when to fire it prevents duplicate notifications and missed field updates.

Email Notifications

Use the Send Email action type. Set the sender to a generic system email address rather than the record creator to avoid confusion on replies. Use a custom email template that includes the record number, amount, and a direct link to the record using the {record.url} token. Place this action in the Entry Actions of each pending-approval state so the notification fires once when the record enters the state, not on every save.

Field Updates

Use Set Field Value actions to update status fields, clear temporary flags, or populate an Approval Date field. Place these in the Entry Actions of terminal states (Approved, Rejected) so the field values are set as soon as the state is reached. Avoid placing field update actions on transitions, as they execute before the record fully enters the new state in some trigger contexts.

Escalations

Add a Scheduled Action to each pending-approval state. Set the trigger to a fixed interval after the record enters the state, for example 48 hours. The action sends a reminder email to the approver and, if you add a second scheduled action at 72 hours, routes to a backup approver field or role. Escalation actions require the workflow scheduler to be enabled in your NetSuite account settings.

Close-up of a tablet displaying analytics charts on a wooden office desk, alongside a smartphone and coffee cup.

Testing Approval Workflows in NetSuite Sandbox

All approval workflows should be validated in a sandbox account before deployment to production. NetSuite’s sandbox environment mirrors your production configuration and allows full end-to-end testing without affecting live records.

Sandbox Testing Sequence

  1. Set the workflow status to Testing in sandbox. This limits execution to the user who created the workflow.
  2. Create a test purchase order or expense report as the workflow creator. Verify it enters the Draft state.
  3. Submit the record. Confirm it transitions to the first pending-approval state and that the notification email is sent to the correct recipient field.
  4. Log in as the designated approver user in sandbox and verify the approval task appears. Approve the record. Confirm it transitions to the next state or to Approved.
  5. Repeat the test with a record that triggers the rejection path.
  6. Test the escalation by manually advancing the system date in sandbox or by temporarily reducing the escalation interval to 1 minute for the test run.
  7. Review the Workflow Execution Log on the System Information subtab of each test record to confirm each state transition is recorded with the correct timestamps and user.

After all paths are verified, set the workflow status to Released in production. Released workflows execute for all users, not just the workflow creator.

Common Configuration Errors and Fixes

ErrorRoot CauseFix
PO triggers both standard routing and SuiteFlow simultaneouslyStandard approval routing not disabled for Purchase OrdersDisable at Setup, Accounting, Accounting Preferences, Approval Routing
Approval email not sent after submissionSend Email action placed on transition instead of Entry Actions of the destination stateMove the action to Entry Actions of the pending-approval state
Record stuck in pending state after approver account deactivatedRouting to named employee rather than field reference or roleReplace named employee with Supervisor field reference; add escalation to backup role
Workflow fires on every save, not only on submissionTransition condition missing Status equals Pending Approval checkAdd the status condition to the Draft-to-Pending transition
Field update not visible after approvalSet Field Value action placed on transition rather than Entry Actions of Approved stateMove to Entry Actions of the Approved state
Escalation never firesWorkflow scheduler not enabled, or scheduled action interval set in days but unit set to hoursEnable scheduler at Setup, Company, Enable Features; verify interval unit
Duplicate approval tasks created for same recordWorkflow published twice, or workflow has no deduplication condition on re-entryAudit workflow list for duplicates; add condition to check current state before re-entry

Frequently Asked Questions

Can I configure a NetSuite purchase order approval workflow without disabling standard approval routing?

You can, but it creates conflicts. If both standard approval routing and a SuiteFlow workflow are active for Purchase Orders, a PO may trigger both simultaneously, resulting in duplicate approval requests or unexpected status changes. The recommended practice is to disable standard approval routing for the record types you are managing with SuiteFlow, using Setup, Accounting, Accounting Preferences, Approval Routing.

How do I route approvals to different people based on the subsidiary?

Add a condition group at the first branching point in your workflow that checks the Subsidiary field on the record. For each subsidiary, create a separate transition that routes to the appropriate approver field, such as a custom Regional Controller field on the Subsidiary record. Use field references rather than named employees so the routing updates automatically when personnel changes occur.

What happens to a purchase order in the approval queue if the assigned approver account is deactivated?

If the approver is a named employee and their account is deactivated, the approval task remains in limbo. The best safeguard is to route to a role rather than a named employee, or to a field-referenced supervisor that can be updated quickly. You can also configure an escalation action that fires after a set period and routes to a backup approver or the role’s full membership group.

How do I view which workflow state a record is currently in?

Open the record, go to the System Information subtab, and look at the Workflow Execution Log. It shows the current state, all previous states, and the timestamps for each transition. For a live queue view, create a saved search on the record type filtered by Status equal to Pending Approval and include the Workflow State column if you have added a custom field to track it.

Is it possible to allow an approver to delegate their approval rights in SuiteFlow?

SuiteFlow does not have a native delegation feature, but you can replicate it. Create a custom Delegate Approver field on the employee record. In your workflow, use a formula condition to check whether the Delegate Approver field is populated, and if it is, route the approval request to that field reference instead of the standard Supervisor field. The employee updates their own delegate record when they are out of office.

Configuring NetSuite approval workflows correctly from the start prevents months of rework, audit exceptions, and approval bottlenecks as your organisation grows. Our NetSuite implementation services cover SuiteFlow design, multi-subsidiary routing, and full approval lifecycle setup tailored to your finance operations.

Book a free consultation

A well-configured NetSuite approval workflow removes manual follow-up from finance operations and gives auditors a complete decision trail on every transaction. Start with purchase orders, validate the routing logic in sandbox against your actual subsidiary and role structure, then extend the same pattern to expense reports and vendor bills. Once the core states and field references are correct, adding new routing tiers or subsidiaries is a matter of adding condition groups rather than rebuilding from scratch.