The Approval Suite brings multi-level approvals for purchase orders, vendor bills and invoices into any NetSuite account — productive in hours instead of weeks. 100 % native SuiteScript, no extra module, no external platform.
Most approval solutions push you into someone else's model: a rollout project measured in weeks, a platform of its own next to NetSuite, and a consultant for every change to an approval limit. The Approval Suite turns that around — it runs entirely inside your account, is set up through a guided wizard and stays in your hands afterwards.
No extra modules, no complex setup — the standard features it needs are active in practically every account.
Install the bundle, walk the wizard, switch on a document type. No rollout project, no interface, no data sync.
Approvals by department, project, amount or your own logic — instead of one rule that has to fit everyone.
Lean SuiteScripts instead of a middleware layer: stable performance and nothing sitting between you and your data.
On the record, by email link without login, in bulk, or from the dashboard — whichever way your approvers actually work.
Automatically captured vendor bills run through the same process, including the match against purchase order and item receipt.
SuiteBundle 705359 installs like any other bundle — workflows, custom records, scripts and interfaces included. No external system, no data replication.
The guided wizard creates configuration, email sender, security settings and your first route with its levels — step by step, validated at every station.
One workflow per document type: purchase orders, vendor bills and invoices are activated individually, so you roll out gradually instead of all at once.
Speed only helps if the solution holds afterwards. The suite covers the whole approval cycle: from route resolution through delegates and rejections to an audit-proof log.
Any number of levels per route, ordered by ascending amount threshold. Each level can be narrowed to specific departments.
The right route is determined per document: own logic, project, department or generic — with a clean fallback order instead of a rigid assignment.
Approvers decide straight from the notification. The link is secured with a SHA-256 token, expires, works once and is logged.
Review open cases together and approve or reject them in one pass — with a batch limit, so nothing slips through unchecked.
Holidays and sick leave no longer block approvals: employees set their own delegate through a self-service page.
Vendor bills are checked against purchase order and item receipt. Differences in quantity or amount steer the route instead of passing quietly.
“Waiting for my approval” plus your own delegations right on the NetSuite dashboard — the entry point for day-to-day work.
See before submitting which levels and approvers will apply. The question “who actually has to approve this?” answers itself.
Two separate actions with a mandatory comment. The requester is informed automatically — including the approver's reasoning.
Every action lands in the audit log: time, person, comment, plus IP, browser and operating system for email approvals.
The approval email carries the rendered document as a PDF — optionally including files attached to the case, such as the scanned invoice.
Thresholds work across currencies: amounts are converted at the document date's rate, subsidiaries are respected throughout.
For every document the suite determines the applicable route through a fixed order of precedence. If the most specific level doesn't apply, resolution falls cleanly through to the next one. A handful of routes therefore cover many constellations without leaving special cases unhandled. Inside the route, the amount decides.
Plenty of solutions cover approvals in NetSuite. The difference is in the rollout effort, the technical base, and how much you can change yourself after go-live.
| Topic | Approval Suite | Usual shape |
|---|---|---|
| Rollout | Hours — bundle, wizard, document type | Days to weeks as a project |
| Routes | By department, project, amount and own logic | Mostly hard-wired |
| Technical base | 100 % SuiteScript inside the account | Often a platform of its own alongside |
| Changes after go-live | Key users maintain routes and thresholds themselves | Frequently through the vendor |
| Ways to approve | UI, email link without login, bulk, dashboard | Usually only in the interface |
| Invoice capture | Captured bills matched against purchase order and item receipt | Additional configuration required |
SuiteBundle 705359 — installation and updates through NetSuite's bundle mechanism.
SuiteScript 2.x and SuiteFlow, entirely inside the account. No external platform, no data replication.
Purchase order, vendor bill, invoice — one workflow each, activated individually.
Server-side scripting, custom records, workflow, subsidiaries, departments, multi-currency. Projects is supported but not required.
German and English — interfaces and notifications, per user.
Signed one-time links with expiry: SHA-256 token, constant-time comparison, complete audit log.
Hook module for your own route resolution and for checks before or after approval.
Health check console: configuration, routes and email delivery verifiable at a glance.
Interfaces and emails in your corporate look — without touching the bundle's ability to update.
Usually within a day. Installation takes minutes and the wizard walks you through configuration and the first route. What costs time afterwards is the business question of who approves above which amount — not the technology.
No. What's needed are standard features active in practically every account: server-side scripting, custom records, workflow, subsidiaries, departments and multi-currency. The Projects feature is supported but not a prerequisite.
Yes — that is the core of the product. Routes, levels, thresholds, approvers and delegates are records in NetSuite and are maintained there. A new approval limit needs no script and no consultant.
Not necessarily. Approval can happen straight from the email, through a signed one-time link with an expiry. Alternatively there is approval on the record, bulk approval and the dashboard portlet.
Yes. Automatically captured vendor bills are matched against the corresponding purchase order. If a line cannot be matched unambiguously, the case is not waved through quietly but routed into exception handling.
Every action is logged in its own audit record: time, person, action and comment. For approvals via email link, IP address, browser and operating system are added.
Through the delegation feature employees set their own stand-in. Approvals keep running without administration having to step in.
Yes. Besides the configurable route logic there is a hook module for customer-specific rules and a workflow template for variants beyond the standard — without giving up the bundle's ability to update.
In a 30-minute demo we set up a route for one of your real approval cases — and you watch the document run through the levels instead of having to imagine it.