Disclosure: NetSuiteForge may earn a commission through affiliate links in this article. We only recommend solutions we've personally implemented for ecommerce clients. Our editorial process is independent, and our recommendations are based on hands-on experience.

NetSuite Approval Workflows for POs and Expenses

Approval workflows are the guardrails that keep your ecommerce business from accidentally (or intentionally) spending money it shouldn't. Without them, any employee with NetSuite access can create a $50,000 purchase order or submit a $10,000 expense report with no oversight. That might work when you're a 5-person startup, but once you're past 15 employees and $5M in revenue, uncontrolled spending becomes a real risk.

I've seen an ecommerce brand where a junior buyer accidentally created a duplicate purchase order for $28,000 worth of inventory that was already on order. Without an approval workflow, the PO went straight to the vendor and they shipped it. The brand was stuck with double the inventory they needed, tying up cash for months. A simple approval threshold would have caught it.

NetSuite's SuiteFlow workflow engine lets you build sophisticated approval chains that match your organizational structure. This guide covers practical approval workflow configurations for purchase orders and expense reports, with specific examples relevant to ecommerce operations.

Key Takeaways

• SuiteFlow is NetSuite's workflow automation engine that powers multi-step approval routing for any transaction type
• Approval workflows should balance control with speed—too many approval steps slow down operations; too few create risk
• Dollar-based thresholds are the most common routing logic, but you can also route by department, vendor, item category, or any custom field
• Escalation and delegation rules prevent approval bottlenecks when approvers are unavailable
• Mobile approval via the NetSuite mobile app keeps the process moving when approvers are away from their desks

What Is SuiteFlow and How Does It Work?

SuiteFlow is NetSuite's visual workflow builder. It lets you define business rules that automate actions on records—including approval routing, email notifications, field updates, and status changes.

SuiteFlow Concepts

States: The stages a transaction moves through (e.g., Draft → Pending Approval → Approved → Rejected)

Transitions: The rules that move a transaction from one state to another (e.g., "If total > $5,000, transition to Pending VP Approval")

Actions: Things that happen during a transition or within a state (e.g., send email notification, set a field value, create a task)

Conditions: The criteria that must be met for a transition to occur (e.g., amount > threshold, department = marketing, vendor = specific vendor)

Why SuiteFlow Over SuiteScript for Approvals

You could build approval logic with SuiteScript (NetSuite's JavaScript framework), but SuiteFlow is better for approvals because:

• Visual design: Non-developers can understand and modify workflows
• Audit trail: Every state change is logged automatically
• Built-in approval actions: Approve/reject buttons, email notifications, delegate functionality
• Maintenance: No code to debug when business rules change

Use SuiteScript for complex conditional logic that SuiteFlow can't handle (rare for standard approval workflows).

How Do You Design a Purchase Order Approval Workflow?

The PO approval workflow needs to balance two competing needs: spending control (prevent unauthorized or wasteful purchases) and operational speed (don't slow down procurement so much that you miss vendor deadlines and stock out).

Designing the Approval Matrix

Start by answering these questions:

1. What spending levels require oversight? (Dollar thresholds)
2. Who can approve at each level? (Organizational hierarchy)
3. Are there exceptions? (Emergency orders, recurring vendors, blanket POs)
4. How fast do approvals need to happen? (SLA targets)

Example approval matrix for a $15M ecommerce brand:

PO Amount	Approval Required	Expected Turnaround
Under $500	Auto-approved	Immediate
$500 - $2,500	Purchasing Manager	4 hours
$2,500 - $10,000	Director of Operations	24 hours
$10,000 - $50,000	VP of Operations + CFO	48 hours
Over $50,000	CEO	As needed

Building the Workflow in SuiteFlow

1. Navigate to Customization → Workflow → New
2. Record Type: Purchase Order
3. Release Status: Testing (build and test before going live)

State 1: Draft

• Entry action: None
• This is where POs are created and edited before submission

Transition: Submit for Approval

• Trigger: User clicks "Submit" button
• Condition: PO status is Draft
• Action: Evaluate the total amount and route to the appropriate approval state

State 2: Pending Manager Approval (for POs $500 - $2,500)

• Entry actions:
  • Send email to Purchasing Manager with PO details
  • Create a task assigned to the Purchasing Manager
  • Set PO status field to "Pending Approval"
• Available transitions: Approve → Approved, Reject → Rejected

State 3: Pending Director Approval (for POs $2,500 - $10,000)

• Entry actions:
  • Send email to Director of Operations
  • Create a task with a 24-hour due date
• Available transitions: Approve → Approved, Reject → Rejected

State 4: Pending VP + CFO Approval (for POs $10,000 - $50,000)

• This requires sequential approval: VP approves first, then CFO
• Sub-state 4a: Pending VP Approval
  • VP approves → Transition to sub-state 4b
  • VP rejects → Transition to Rejected
• Sub-state 4b: Pending CFO Approval
  • CFO approves → Transition to Approved
  • CFO rejects → Transition to Rejected

State 5: Approved

• Entry actions:
  • Set PO status to "Pending Receipt"
  • Send confirmation email to the requester
  • Optionally, auto-email the PO to the vendor

State 6: Rejected

• Entry actions:
  • Send rejection email to the requester with rejection reason
  • Set PO status to "Rejected"
• Transition: Requester can edit and resubmit (moves back to Draft)

Auto-Approval Rules

Configure auto-approval for low-risk scenarios to reduce approval fatigue:

• POs under $500: Auto-approve (no human intervention needed for small purchases)
• Recurring POs to approved vendors: If the vendor has been approved for the category and the PO matches a blanket PO, auto-approve regardless of amount
• Replenishment POs generated by reorder points: If the system generated the PO based on safety stock rules, auto-approve up to $5,000

Implementation: Add a transition from Draft directly to Approved with conditions that check for these auto-approval criteria.

Email Notification Templates

Configure meaningful approval email notifications:

Subject: [ACTION REQUIRED] PO #{PO_NUMBER} - ${VENDOR_NAME} - ${TOTAL} - Needs Your Approval

Body should include:

• PO number and creation date
• Vendor name
• Line items with quantities and prices
• Total amount
• Requested by (employee name)
• Required delivery date
• Link to approve/reject directly in NetSuite
• Note: Include a "View PO" deep link to the NetSuite record

How Do You Build an Expense Report Approval Workflow?

Expense report approval is equally important for ecommerce brands—especially for marketing spend, travel, and software subscriptions that can add up quickly.

Expense Categories for Ecommerce

Common ecommerce expense categories that need approval routing:

Category	Examples	Risk Level
Marketing/Advertising	Google Ads, Facebook, influencers	High (can overspend quickly)
Software Subscriptions	Shopify, Klaviyo, ShipStation	Medium (recurring, predictable)
Warehouse Supplies	Boxes, tape, labels, dunnage	Low (operational necessity)
Travel	Trade shows, vendor meetings	Medium (discretionary)
Professional Services	Consultants, photographers, designers	High (scope creep)
Samples/Prototyping	New product samples from vendors	Medium

Expense Approval Matrix

Expense Amount	Category	Approver
Under $100	Any	Auto-approved
$100 - $500	Non-marketing	Department manager
$100 - $500	Marketing	Marketing Director
$500 - $2,000	Any	Department Director
$2,000 - $10,000	Any	VP + CFO
Over $10,000	Any	CEO

Building the Expense Workflow

The structure mirrors the PO workflow but with expense-specific considerations:

1. Record Type: Expense Report
2. Routing logic: Based on total amount AND expense category
3. Receipt requirement: Any line item over $25 requires an attached receipt image
4. Policy compliance check: Flag expenses that exceed per-diem limits, duplicate submissions, or violate policy

Pre-Approval for Large Expenses

For marketing spend and professional services, require pre-approval before the expense is incurred:

1. Employee submits a "Spend Request" (custom record) with estimated amount, vendor, and business justification
2. Spend Request goes through approval workflow
3. Once approved, the employee can incur the expense and submit the actual expense report
4. Expense report approval references the pre-approved Spend Request

This prevents the situation where someone spends $5,000 on Facebook ads and only asks for approval afterward.

Software Subscription Management

Recurring software expenses deserve special treatment:

• Create a custom record for "Software Subscriptions" that tracks:

  • Application name
  • Monthly/annual cost
  • Renewal date
  • Owner (who requested it)
  • Business justification
  • Number of licenses/seats

• Set up a workflow that triggers 30 days before renewal with a review request to the owner and their manager

• Auto-flag any new subscription expense that doesn't have a matching approved subscription record

Ecommerce insight: The average ecommerce brand uses 15-25 SaaS tools. Annual reviews of software subscriptions typically find 10-20% can be eliminated or downgraded, saving $5,000-20,000/year.

How Do Escalation and Delegation Work?

Approval workflows fail when approvers are unavailable—on vacation, in meetings, or simply too busy to check their approval queue. Escalation and delegation prevent bottlenecks.

Escalation Rules

Configure automatic escalation when approvals aren't processed within the expected timeframe:

Escalation ladder:

1. 4 hours after submission: Send reminder email to the approver
2. 24 hours after submission: Send escalation email to the approver's manager
3. 48 hours after submission: Auto-assign to the next level in the approval hierarchy
4. 72 hours after submission: Alert the CFO/CEO that an approval is stuck

Implementation in SuiteFlow:

• Use a scheduled workflow that checks for POs/expenses in "Pending Approval" state for longer than the threshold
• Add transition conditions based on the time elapsed since entering the approval state
• Each escalation step sends a notification and optionally changes the assigned approver

Delegation Configuration

Allow approvers to delegate their approval authority when they're unavailable:

1. Create a custom record: "Approval Delegation"

   • Delegator (the approver who's away)
   • Delegate (the person who will approve in their place)
   • Start date
   • End date
   • Transaction types (POs only, expenses only, or both)
   • Amount limit (delegate can only approve up to $X)

2. Modify the workflow to check for active delegations before routing to the original approver

3. If a delegation exists and the amount is within the delegate's limit, route to the delegate instead

Best practice: Require delegation setup before PTO. Add it to your PTO request process—when someone requests time off, the system prompts them to set up their approval delegation.

Emergency Override

Sometimes a PO needs immediate approval and the normal approver chain is unavailable:

• Create an "Emergency Override" role assigned to 2-3 senior leaders
• The emergency approver can approve any transaction regardless of normal routing
• All emergency overrides are logged and reviewed monthly by the CFO
• Limit emergency override to purchases that are operationally critical (preventing stockouts, vendor deadlines)

How Do You Track and Report on Approval Metrics?

Approval workflows generate valuable data about your organization's spending patterns and operational efficiency.

Key Approval Metrics

Average approval time: How long does it take from submission to approval? Target varies by amount—same day for under $2,500, 2 days for larger amounts.

Approval rate: What percentage of POs/expenses are approved vs. rejected? A rejection rate above 15% suggests either unclear policies or inadequate pre-screening.

Rejection reasons: Why are POs/expenses being rejected? Common reasons include exceeding budget, duplicate request, insufficient justification, and policy violation.

Escalation rate: How often do approvals require escalation? High escalation rates indicate approvers aren't responsive or thresholds need adjustment.

Auto-approval rate: What percentage of POs are auto-approved? This should be 30-50% for a well-configured system. Too low means your thresholds are too conservative; too high means you're not catching enough.

Building Approval Reports in NetSuite

Create saved searches that report:

1. Pending Approvals Dashboard: All POs and expenses currently awaiting approval, sorted by age (oldest first)
2. Approval Aging Report: Average time-to-approval by approver, department, and amount tier
3. Monthly Spend by Department: Approved spend broken down by department and category
4. Budget vs. Actual: Compare approved spend to departmental budgets
5. Rejection Analysis: Rejected POs/expenses with reasons and resubmission history

Dashboards for Approvers

Create role-specific dashboards:

For Approvers:

• My pending approvals (action required)
• My recently approved/rejected items
• My team's spending this month vs. budget

For Finance:

• All pending approvals across the organization
• Spend trending by category
• Budget utilization by department
• Approval SLA compliance

For Executives:

• High-value pending approvals
• Monthly spending summary
• Year-over-year spending trends
• Vendor concentration analysis

Frequently Asked Questions

How many approval levels should my workflow have?

Most ecommerce brands need 3-4 levels at most: auto-approve for small amounts, manager approval for medium amounts, director/VP approval for large amounts, and executive approval for very large amounts. More than 5 levels creates bureaucracy that slows operations without proportional risk reduction.

Can approvers approve from their mobile phones?

Yes. The NetSuite mobile app supports approval actions. Approvers can view the PO/expense details and tap Approve or Reject directly from their phone. This dramatically improves approval speed—from hours (waiting to get to a computer) to minutes (approve from anywhere).

What happens if a PO is rejected?

The PO returns to Draft status and the requester is notified with the rejection reason. The requester can edit the PO (reduce quantity, change vendor, add justification) and resubmit it for approval. The full rejection and resubmission history is maintained in the workflow history log.

Should I require approval for vendor bills in addition to POs?

If you have three-way matching enabled (PO → receipt → bill), additional approval on vendor bills is usually unnecessary—the PO was already approved, and the three-way match catches discrepancies. Add bill approval only for vendor bills that don't have a corresponding PO (e.g., utility bills, one-time services, subscription renewals).

How do I handle budget-based approvals?

SuiteFlow can check the transaction against a budget. Create a budget record for each department/period, then add a workflow condition that compares the PO amount plus year-to-date approved spend against the budget. If the PO would exceed the budget, route to a higher approval level or reject with a "budget exceeded" notification.

Can I retroactively add approval workflows to existing POs?

Yes, but be thoughtful. When you activate a new workflow, you can choose whether it applies to existing records or only new ones. For a smooth transition, set all existing POs to "Approved" status and apply the workflow only to POs created after the activation date.

Ready to Implement Approval Controls?

Approval workflows protect your ecommerce business from unauthorized spending while maintaining the operational speed you need. The key is calibrating thresholds to your business size—too tight and you slow everything down, too loose and you lose control.

Start with a simple 3-level approval for POs and expenses, then refine based on the data. Your approval metrics will tell you exactly where to adjust thresholds, add auto-approval rules, or tighten controls.

Take our free NetSuite readiness assessment → to evaluate your current spending controls and get a customized approval workflow design for your ecommerce operation.