NetSuite Approval Workflows: What SuiteFlow Can and Can't Do
SuiteFlow is the right starting point for approval workflows in NetSuite. It handles the most common patterns well, it has a graphical designer that admins can work with, and it does not require scripting for straightforward routing. Most of what people need from approvals, SuiteFlow can do.
This post is about the edges. Where SuiteFlow works, where it starts to strain, and what your options are when it is not enough. If you are building approval workflows or inheriting someone else's, knowing these boundaries before you hit them saves you from designing yourself into a corner.
What SuiteFlow does well
SuiteFlow handles a lot of approval scenarios cleanly.
Amount-threshold routing is the most common pattern and SuiteFlow's sweet spot. Under $5K goes to a manager, over $5K goes to a director, over $50K goes to the CFO. This works exactly the way you would expect.
Role-based and department/subsidiary conditional routing lets you branch the approval chain based on who submitted the transaction or where it belongs in the org chart. Formula-based conditions handle moderately complex logic without scripting.
Sequential multi-level chains work well up to about three levels. Manager to director to VP is clean. Each level gets email notifications, fields lock based on approval status, and the system notes give you a basic audit trail.
The Create Line action eliminated the need for SuiteScript on sublist operations. If your workflow needs to add or modify lines during the approval process, this was a real gap that no longer exists.
For a single-subsidiary company with straightforward approval policies, SuiteFlow covers most of what you need. The rest of this post is about what happens when your business outgrows those defaults.
Where it starts to strain
SuiteFlow still works in these scenarios, but you are fighting it more than using it.
Multi-level routing beyond simple chains. Three levels is practical. Beyond that, performance degrades and state management gets complicated. Parallel approvals, where two people need to approve simultaneously, require careful state design that most admins cannot build without help. Before long you have custom fields tracking who has approved, custom actions checking whether all required approvals are in, and a workflow that nobody wants to touch six months later.
Delegation of authority. Native delegation exists, but your approval limits still apply to your delegate. If I delegate to you and my limit is $10K, you can approve up to $10K on my behalf, but you cannot escalate beyond that. Building proper delegation with proxy approvers, expiration dates, and automatic return requires SuiteScript custom actions or a custom record-based matrix. It is doable, but it is no longer a drag-and-drop workflow.
Cross-subsidiary routing. Behavior is inconsistent by record type, and this trips people up. Expense report approvers only see their own subsidiary. PO and requisition approvers can see across subsidiaries. If your approval policy needs consistent cross-subsidiary behavior, you are building workarounds for the record types that do not cooperate.
Record types without native approvals. Vendors, customers, inventory adjustments, and several other record types have no native approval workflow support. You either build a full SuiteFlow workflow from scratch with custom status fields, or you skip formal approval on those records entirely.
Multi-currency threshold logic. Approval limits align with the base currency. If you operate in multiple currencies, the threshold logic does not convert. A $50K limit does not automatically become a 45K EUR limit. I have seen this surface mid-deployment when someone tests with a non-base currency for the first time and the routing makes no sense.
The Approval Routing to SuiteFlow migration gap. If you are moving from legacy Approval Routing to SuiteFlow, you lose auto-generated email notifications, Employee Center approve/reject buttons, and supervisor hierarchy routing. You rebuild all of it manually in the new framework. It is a real project, not a migration wizard.
Where it breaks down
These are not edge cases you can design around. They are gaps in what SuiteFlow was built to do.
Performance at volume. Real-time workflows on high-volume transaction processing slow the instance. Your AP team feels it. Batch approval is capped at 25 records, so if your team processes hundreds of bills a week, someone is clicking through approval screens all day.
Mobile and email approvals. There is no native mobile approval app. Email approval is limited: no one-click approve from email natively. SuiteApprovals adds it for some record types but not all. Executives who approve from their phone are either logging into the full NetSuite UI on a mobile browser or not approving until they are back at a desk. If your CFO reviews things between flights, that is a real workflow gap.
The context problem is subtler but just as damaging. The approval screen shows the transaction. It does not show the Slack thread, the email chain, the vendor quote, or the budget comparison that explains why the amount is what it is. Approvers rubber-stamp because they do not have context, not because they do not care. You can attach files to transactions, but that requires someone to remember to attach them before submission.
Then there is complex conditional logic. If your approval matrix is a spreadsheet with 40 rows of conditions covering department, subsidiary, amount band, item category, and custom segments, SuiteFlow's condition builder runs out of room. You land on SuiteScript custom actions inside the workflow, which means you need a developer to maintain what was supposed to be an admin tool. I have seen this in SOWs where "configure standard approval workflows" turns into a month of custom development. If you are reviewing a SOW right now, make sure you know what that line actually means.
Your options when SuiteFlow is not enough
When you hit SuiteFlow's limits, you have a few paths forward.
SuiteScript custom actions inside SuiteFlow. This extends the workflow with code while keeping the overall structure in the graphical designer. Good for one or two complex conditions. Bad when the entire approval matrix lives in script and the workflow is just a shell around it.
Full SuiteScript-based approvals. You get exactly what you want, and you need a developer on staff or on retainer to keep it running. Every NetSuite update is a regression test. Every new approval rule is a code change. Some organizations genuinely need this level of control, but the ongoing cost is real and it does not go away.
SuiteApprovals (Oracle's free SuiteApp). A pre-built approval framework that covers journal entries, POs, requisitions, expense reports, sales orders, and vendor bills. It has real capabilities: email approval, batch processing, configurable routing. It also has real limitations. One rule set per subsidiary means duplication in multi-subsidiary environments. Memorized transactions created before enabling the app will not process through it. There is an 18K approver record cap. Journals cannot be edited while in approval status. Test it thoroughly before committing.
Third-party approval apps. Tools built specifically for NetSuite approvals that handle delegation, cross-subsidiary routing, mobile approval, complex conditional logic, and context-rich approval screens without SuiteScript.
Building or outgrowing approval workflows?
If you're hitting the walls described above, take a look at Greenlight Approvals. It handles delegation, cross-subsidiary routing, and mobile approvals natively inside NetSuite.
Picking the right approach
SuiteFlow is not the problem. It is a capable tool that covers the majority of approval scenarios. The problem is assuming it covers all of them, or finding out it does not three months into a build when switching costs are high.
If your approval needs are straightforward, start with SuiteFlow and you will be fine. If you are running into the limits described above, you are not the first. The main thing is to pick your path deliberately instead of bolting on workarounds until the workflow is unmaintainable.
Need help with NetSuite?
If you are building approval workflows and want help evaluating what SuiteFlow can handle vs. what needs something else, that is a conversation I have regularly.