By Louis Balla, Chief Revenue Officer, Nuage.
NetSuite handles approvals two ways. SuiteApprovals is a SuiteApp that routes record types such as journal entries, expense reports, purchase orders, requisitions, sales orders and vendor bills by approval limits and the supervisor hierarchy. SuiteFlow builds custom approval workflows from states, transitions, conditions and actions. Choose by how much custom routing your approval policy needs.
Where approvals run by email chain, spreadsheet tracker or verbal sign-off, the evidence sits in inboxes and files that someone has to piece together when an auditor asks. This guide covers NetSuite’s native approval options and how to design routing and controls an auditor can test.
What do NetSuite approval workflows do, and what do they replace?
NetSuite approval workflows are rule-based sequences that route transactions to designated approvers before the transactions post, execute or advance. They replace an informal process: someone creates a purchase order, emails a manager, the manager replies “approved,” and the AP clerk changes the status by hand. In that process, approval emails get buried and the routing goes stale when approvers leave. A $50,000 vendor bill can go through because no one formally defined the threshold. A workflow puts the approval logic into the transaction lifecycle.
How do SuiteApprovals and SuiteFlow compare?
| SuiteApprovals | Custom SuiteFlow workflow | |
|---|---|---|
| What it is | A SuiteApp that adds standard approval capabilities | A workflow you define on a record type |
| Record types | Journal entry, expense report, purchase order, requisition, sales order, vendor bill, engineering change order, email approval log and custom records, per Oracle | Any record type that supports workflows |
| Routing | Employee and general approval limits, hierarchical or custom routing, delegation of authority | Whatever conditions you define: amount, department, subsidiary, vendor attributes and more |
| Setup effort | Enable the prerequisite features and install the SuiteApp | Design, build and test each workflow |
| Use it when | A standard limit-and-supervisor model fits your policy | Your routing depends on rules the packaged model does not cover |
Oracle documents SuiteApprovals in its SuiteApprovals SuiteApp chapter, and it documents SuiteFlow in its SuiteFlow overview. Many accounts use both, with the packaged model for standard transactions and SuiteFlow for the exceptions.
What are the core building blocks in SuiteFlow?
A SuiteFlow approval workflow consists of four elements: states (such as Pending Approval, Approved or Rejected), transitions (the movement between states), conditions (the rules that govern when a transition fires) and actions (what happens during a transition, such as sending a notification or updating a field). Misconfiguring any one of them creates a control gap an auditor can find.
As an illustration, a purchase order workflow might have three states: Pending Approval, Manager Approved and Finance Approved. The transition from Pending to Manager Approved fires only when the PO amount exceeds $5,000 and the requestor’s direct supervisor approves. A second transition routes POs above $25,000 to a finance director before they reach Approved. Each transition logs the approver, the timestamp and any comments, which is the audit trail your compliance team needs. The thresholds are examples, and your policy sets the real ones.
Which transaction types need automated approvals?
Most organizations start with vendor bills, and limiting a workflow strategy to AP leaves gaps. Purchase orders, expense reports, journal entries, sales orders with non-standard discounts, inventory adjustments and intercompany transactions all carry approval risk. Each type has its own routing logic. Expense reports might route by department and amount tier, journal entries by account classification and posting period, and inventory adjustments by value. Any transaction that creates a financial obligation, adjusts the general ledger or changes inventory value should pass through a documented approval chain.
Per Oracle’s page on approving bill payments and payment runs, payment runs and vendor payments need approval when a payment exceeds the limit set in approval routing. Approval routing for payment batches can apply limits per bill payment, per vendor payment or per batch, per Oracle’s setup page.
How do you design NetSuite approval workflows that hold up in an audit?
Auditors, whether internal or SOX-focused, evaluate whether your controls operate over time and whether you can prove it. Our SOX compliance guide covers how these connect to control testing.
How do you enforce segregation of duties?
Segregation of duties (SoD) means no single person can initiate, approve and post the same transaction. In SuiteFlow you can add a condition that compares the approver to the transaction’s Created By field and blocks self-approval. Common conflicts to address are AP clerks who both enter and approve vendor bills, procurement staff who create and approve their own POs, and controllers who post journal entries they originated. Each conflict should map to a workflow condition that stops the action and routes it to an independent approver.
How do you build dynamic approval hierarchies?
Static approval lists break whenever someone changes roles or a new department forms. Dynamic hierarchies take approver assignments from employee records, department hierarchies or a custom approval matrix, so when a department head changes you update one employee record and every workflow that reads the hierarchy picks up the change. Oracle documents that SuiteApprovals routes by employee approval limits and the supervisor chain. A routing design usually considers five variables: transaction type, amount, department or cost center, subsidiary and vendor risk. For multi-subsidiary and multi-location accounts, subsidiary and location are fields a workflow condition can read, so approvals can route to the approver for that entity. As an illustration, a $2,000 office supply PO from a trusted vendor might need only a department manager’s sign-off, and a $75,000 capital purchase from a new vendor might route through procurement, finance and an executive in sequence.
What makes an audit trail hold up?
Automated workflows generate a time-stamped record of every approval decision. When an auditor asks who approved a $150,000 vendor bill and when, you want to answer it from a saved search of the workflow history. Our post on internal controls in the age of AI goes further on evidence for auditors.
How do you confirm an approval gap is real?
Confirm how approvals actually route before you call something a gap. In our health checks, findings go back to the client before anything is scheduled. At an industrial services company, a finding that purchase-order approvals were not working was set aside after the controller explained that approvals route through each employee’s supervisor and approval limits, which the first pass had not checked. At an engineering firm, a re-check found one of two duplicate approval workflows had already been switched off.
How do approval workflows handle exceptions?
Every approval workflow needs a path for the approver who is unavailable. Without one, approvals stall while the approver is out. Build these patterns in from the start:
- Time-based escalation: if an approval sits untouched for a set period, for example 48 hours, route it to the approver’s manager.
- Delegation rules: let approvers name a substitute during planned absences, with audit logging of who acted on whose behalf.
- Emergency overrides: create a controlled override path that requires a secondary approver and alerts compliance.
Which metrics show whether the workflows are healthy?
Deploying approval workflows is an ongoing job. Track four measures with saved searches and dashboards: average approval cycle time, the percentage of approvals completed within SLA, escalation frequency and rejection rate by transaction type. A spike in escalations means the routing does not match the org chart. A climbing rejection rate can mean requestors need training on policy thresholds. Many teams set up basic approval routing during implementation and do not revisit it as the business grows, so schedule a quarterly review of the routing against the org chart and the policy.
How Nuage approaches approval workflows
On client accounts, our team works in roughly this order. The order changes with each account.
- List what routes today and what is live. We inventory the approval workflows and the SuiteApprovals settings, and note which transactions have no approval step.
- Set the routing rules with the policy owner. Amount limits, supervisor chains, subsidiary and vendor rules are agreed with the controller before anything is built.
- Add dual control where money leaves. For vendor payments, we look at approval routing on payment batches, using the limits Oracle documents.
- Test with realistic cases in sandbox. We use representative roles and edge cases, such as edits after submission and vendor changes.
- Re-check before restating a finding. Where an approval looks missing, we confirm with the process owner and a live check how the approval actually routes.
Nuage’s NetSuite experts do this work as part of NetSuite optimization and managed services. On the purchasing side, our advanced procurement guide covers the three-way match approval, and our AP automation guide covers vendor bills. To see where your approvals stand, request the free NetSuite Performance Scorecard or schedule a call with a NetSuite expert.
Frequently asked questions about NetSuite approval workflows
What are NetSuite’s native approval options, and how do I choose?
SuiteApprovals is a packaged approval layer for supported record types, with approval limits, supervisor routing and delegation. SuiteFlow builds custom workflows with conditional routing. Use SuiteApprovals when a limit-and-supervisor model fits your policy, and use SuiteFlow where routing depends on rules the packaged model does not cover. Many accounts combine them.
How do I test approval workflows before deploying them to production?
Validate workflows in a NetSuite sandbox using realistic transactions, representative roles and edge cases such as edits after submission or vendor changes. Include a short user acceptance cycle with finance, procurement and auditors so the workflow behavior matches policy and evidence expectations. Keep the test cases as part of the control documentation.
How can I prevent users from editing transactions after approval?
Lock critical fields after approval and require a controlled resubmission when a change affects risk, such as amount, vendor, GL account or subsidiary. For minor edits, allow the change but append a change log note and route only the modified items for re-approval. System notes show who changed what, so auditors can confirm the control worked.
How do approvals work across multiple locations or subsidiaries?
Route by the subsidiary and location fields on the transaction, and assign approvers from the employee hierarchy so each entity’s approver is picked up automatically. Test each entity with a sample transaction, because a rule written for one subsidiary can behave differently in another. Document the routing by entity so auditors can trace any approval to its rule.
Who should own approval workflows long term: IT, finance or operations?
Finance should own the control design and the approval policy, while a NetSuite administrator or center of excellence owns configuration standards and release management. A quarterly review with finance, procurement and compliance keeps the workflows aligned as the organization and audit requirements change.
About the author
Louis Balla is Chief Revenue Officer at Nuage, a NetSuite optimization partner that has served 250+ clients since 2011 and holds a 4.9 out of 5 rating on Clutch. The client work in this article is our team’s.
