NetSuite approvals

Purchase order approval in NetSuite: limits, levels and routing

How to set PO approval limits and levels in NetSuite so spend is controlled before it is committed.

7 min read · Updated 1 November 2026

On this page

Approve spend before it is committed

A purchase order commits the company to spend. Approving it is the cheapest point of control — much cheaper than querying a bill after the goods have arrived.

Requisition or purchase order?

  • Requisitions let employees ask for something; purchasing turns approved requisitions into POs. Approve the requisition for need and budget.
  • Purchase orders commit to a vendor and price. Approve the PO for commercial terms when they differ from the requisition, or above a value.

Many companies approve one or the other, not both — decide which, and write it down.

Setting limits

Approval limits usually depend on amount, and sometimes on category (capex, IT, marketing) or subsidiary. In NetSuite, a single approver per amount band can run on native routing with limits on the employee record. As soon as you need department owners, category owners or parallel sign-off, use SuiteFlow or SuiteApprovals.

Multi-level and parallel approvals

  • Sequential levels — budget owner, then finance, then CFO above a threshold.
  • Parallel approvers — for example IT and Security both approve a software purchase. Both must say yes before the PO moves.

Approvers should always see which level they are at ("level 2 of 3") and who has already approved.

Keep buyers moving

  • Send each approver the request in Teams or Slack the moment it is their turn.
  • Remind after a set number of hours; escalate after that.
  • Let approvers ask the requester a question without leaving the approval.
  • Close the request automatically if the PO is changed or cancelled — and send a fresh one for the new version.

See Axiera Approvals on your own NetSuite records