NetSuite procure-to-pay process flow
Editable NetSuite procure-to-pay process flow: purchase requisition, supervisor approval, purchase order and purchase limits, item receipt, vendor bill with variance hold, and bill payment in swimlanes.
What the NetSuite procure-to-pay process flow process is
NetSuite makes procure-to-pay look simple: a purchase order has Receive and Bill buttons, and the vendor bill can be paid from the Pay Bills page. The simplicity is real, but it hides the decisions that make the process controlled: who can approve a requisition, which purchase limit a PO exceeds, and what happens when a bill does not match what was ordered and received.
Those decisions are usually configured as SuiteFlow workflows and employee purchase limits, and they are the first thing an auditor or a new controller asks about. A swimlane flow puts them on one page, in the lanes of the people who make them.
Use the template when implementing NetSuite, tightening purchasing controls as the company grows, or training new staff. Rename lanes, write your limits on the decisions, and delete the requisition stage if buyers raise POs directly.
What this flowchart covers
In this template
- Purchase requisition entry and supervisor approval routing
- Purchase order creation from the requisition and approval against the employee's purchase limit
- Item receipt against the purchase order
- Vendor bill entry from the PO, with variance holds when the bill does not match the PO and receipt
- Bill payment in a payment batch by ACH or EFT
When to use this template
- You are implementing NetSuite and designing purchasing approvals
- The company has grown and you need documented controls for an audit or due diligence
- Bills are paid without receipts or approvals and you need to show where the gap is
- New buyers and AP staff need training on how purchasing works in NetSuite
How it works
Rename the lanes
Match lanes to your employees, approvers, purchasing, receiving and AP; small teams can merge purchasing and AP into one lane.
Write your approval limits
Put the real purchase limits and approval routing rules on the decisions, so the flow states who can approve what.
Decide on matching
Note whether bills are matched to receipts (three-way) or only to POs, and which variances hold a bill.
Add your exceptions
Add paths for bills without a PO, prepayments and partial receipts if they are common.
Approve and share
Send the flow to the controller for approval; the approved version stays with the chart for auditors.
Frequently asked questions
What is the procure-to-pay process in NetSuite?
An employee enters a purchase requisition, a supervisor approves it, a buyer creates a purchase order, the PO is approved if it exceeds the buyer's limit and sent to the vendor, the goods are received against the PO, the vendor bill is created from the PO and checked against the order and receipt, and the bill is paid in a payment batch.
How do purchase approvals work in NetSuite?
Purchase limits on the employee record set how much someone can approve, and approval routing for requisitions and purchase orders can use NetSuite's standard approval features or a custom SuiteFlow workflow. The flow should state the actual limits on each decision.
Does NetSuite support three-way matching?
Yes. Vendor bills can be matched against the purchase order and the item receipt, and bill variances outside tolerance can hold the bill for review before payment. Whether you match two-way or three-way is a design decision worth recording on the map.