By Louis Balla, Chief Revenue Officer, Nuage. Updated October 2026.
NetSuite Advanced Procurement is an add-on module that extends standard NetSuite purchasing. Employees raise requisitions without needing to know the vendor or price, and buyers combine approved requisitions into purchase orders. Purchase contracts and blanket purchase orders apply negotiated pricing to new orders, and the Procurement Dashboard tracks open transactions and spend by vendor and department.
This guide explains the module’s records and how to set them up. The last sections cover bill approvals and three-way match, with examples from our team’s recent client tickets.
What is NetSuite procurement?
NetSuite procurement covers the purchasing side of the system: vendor records, purchase orders, item receipts, vendor bills and bill payments. Standard NetSuite also includes purchase requests, which an employee enters when they already know the vendor and the price.
The Advanced Procurement module adds the records a central buying team uses. A requisition captures what someone needs, who approved it and when it is needed, and a buyer then decides where to source it. Oracle’s Requisitions Overview puts it this way: a requestor can start a purchase “even if they do not know the exact price or vendor name.”
Key terms
- Purchase request: an employee’s request to buy from a known vendor at a known price. Each request is for one vendor.
- Requisition: an internal request for items, services or expenses. The vendor and price can be added later, and one requisition can produce purchase orders to several vendors.
- Purchase contract: a record of terms negotiated with a vendor, including quantity-based pricing. NetSuite applies the contracted pricing when buyers create purchase orders against it.
- Blanket purchase order: an agreement to buy a set quantity of items from a vendor at a fixed price over a period, with deliveries released against it on a schedule.
- Request for quote (RFQ): a request sent to vendors for bids, created from a buyer’s sourcing need.
- Procurement Dashboard: a dashboard of procurement reports and reminders for outstanding transactions and vendor performance, with spend by department, class, location and vendor.
- Three-way match: comparing the vendor bill with the purchase order and the item receipt before the bill is approved for payment.
- Tolerance and difference limits: the percentage and absolute quantity thresholds a three-way match workflow uses to decide whether a bill’s variance needs an approver.
NetSuite Advanced Procurement vs standard purchasing
| Capability | Standard NetSuite purchasing | With Advanced Procurement |
|---|---|---|
| Internal request | Purchase request, with the vendor and price entered up front | Requisition, with the vendor and price optional at entry |
| Vendors per request | One vendor per purchase request | Several vendors on one requisition, which can produce several purchase orders |
| Combining demand | Each request is ordered on its own | Approved requisition lines from many requesters can be ordered together on one purchase order |
| Negotiated pricing | Entered by the buyer on each purchase order | Purchase contracts and blanket purchase orders apply contracted pricing to new orders |
| Sourcing | Buyer contacts vendors directly | Requests for quote can be issued from the buyer’s sourcing need |
| Spend view | Purchasing reports, saved searches and workbooks | Procurement Dashboard, alongside the same reports and searches |
Oracle’s help pages document each of these features but do not say which subscriptions include which ones, so confirm with your NetSuite account team what your account has before you plan a rollout.
Core features of the NetSuite Advanced Procurement module
Requisitions and consolidated purchase orders
Requisitions move the sourcing decision from the requester to the buyer. An employee asks for a laptop, a desk chair and a phone on one requisition, and after approval the buyer orders each item from whichever vendor fits. Oracle’s documentation uses this example, with the one requisition producing three purchase orders.
Buyers work approved lines from the Order Requisitions page (Transactions > Purchases/Vendors > Order Requisitions). They can filter by requisition, subsidiary or vendor, select lines from several requisitions and create the purchase orders in one pass. A line needs a vendor and a rate (or an amount, for expenses) before it can be ordered, and the requisition number carries onto the purchase order line so the two can be traced.
Purchase contracts and blanket purchase orders
A purchase contract stores the pricing and terms you negotiated with a vendor, including tiered pricing tied to volume. When a buyer creates a purchase order for that vendor and item, NetSuite applies the contracted price, so buyers do not need to look the terms up.
A blanket purchase order suits recurring purchases at an agreed price. You commit to a quantity over a set period and release deliveries against it as you need them. Oracle’s guide to setting up blanket purchase orders notes that once the feature is on, it can be turned off only after every blanket purchase order is closed.
The Procurement Dashboard
The Procurement Dashboard puts procurement reports and reminders on one page. Buyers and controllers use it to follow outstanding transactions and vendor performance, and to analyze spend by department, class, location and vendor. Oracle documents a few behaviors to plan for:
- It is set up by default only in the Classic, Accounting and Shipping centers. Other centers need it configured by hand.
- Portlets that use currency follow the currency of each transaction, which matters if you consolidate across subsidiaries with different currencies.
- Spend reports use the class, department, location and vendor on the transaction’s main line. If your team codes those values on individual lines, build a saved search or workbook for line-level spend.
How to set up NetSuite Advanced Procurement
These steps follow Oracle’s documentation. Check field and menu names against your own account, since roles and forms are often customized.
- Confirm what is provisioned. Ask your account team which procurement features are on your subscription, then decide which ones you will roll out first. You can start with requisitions and approvals and add contracts later.
- Map the current process. Write down who requests, who approves at which amounts, who buys, who receives and who approves bills. The setup decisions below come from this map.
- Enable the features. In Setup > Company > Setup Tasks > Enable Features, on the Transactions subtab, check Purchase Orders and Requisitions. Check Purchase Contracts and Blanket Purchase Orders if you will use them. Request for Quote has its own box and needs Purchase Contracts turned on as well.
- Give requesters a role that can enter requisitions. Oracle’s documentation names the Employee Center or Consultant role for this. Review the requisition and purchase order forms at the same time and remove fields nobody fills in.
- Set up requisition approvals. Oracle’s documentation says requiring approval on requisitions takes a SuiteFlow workflow: either a workflow that sends requisitions to a supervisor or approver, or the Requisition Approval Workflow when you need more customization. Pick one and test it with real amounts.
- Load contracts for your main vendors. Create purchase contracts or blanket purchase orders for the vendors and items where you have negotiated pricing, and check a test purchase order picks up the contracted price.
- Set up the Procurement Dashboard for the roles that need it outside the Classic, Accounting and Shipping centers.
- Set up bill approval. If you use the 3 Way Match Vendor Bill Approval workflow, set tolerance and difference limits on the item, vendor and subsidiary records before go-live. The next section explains why.
Migrate open purchase orders and vendor records cleanly before go-live, and train each group on the step it owns.
How a requisition becomes a paid bill
Each step in procure-to-pay belongs to a different person, and the setup above assigns them:
- Requester: enters the requisition from the Employee Center with the item, quantity and need-by date.
- Approver: the supervisor or approver named by the approval rules signs off on the requisition.
- Buyer: orders approved lines from the Order Requisitions page, choosing vendors and combining lines, with contract pricing applied.
- Receiving: records the item receipt against the purchase order.
- Accounts payable: enters the vendor bill, which the bill approval workflow compares with the purchase order and receipt before payment.
Our guide to NetSuite accounts payable automation covers the bill entry and payment side in more detail.
Approval workflows and three-way match in NetSuite procurement
NetSuite’s 3 Way Match Vendor Bill Approval workflow, part of the NetSuite Approvals Workflow SuiteApp, compares quantities and amounts on the vendor bill with the purchase order and the item receipt. It uses tolerance limits (a percentage) and difference limits (an absolute quantity) set on the item, vendor and subsidiary records. Oracle’s tolerance and difference limit documentation notes that when those fields are left blank on the subsidiary and vendor records, the workflow does not run the checks that use them.
Blank tolerance fields were the cause in two recent bill approval tickets our team handled. A nutrition products company told us small bills were going to a second approver, “Even when the dollar value is as small as $800!” Their three-way match workflow had no tolerance limits defined, so it flagged every bill without a linked purchase order as a discrepancy. At an automation and controls company, missing tolerance values on subsidiary records made the same workflow skip its matching steps. Both tickets closed within 28 days of being opened.
Routing can also follow the size of the exception. A food and beverage company wanted bill approvals to route on how far a bill differed from its purchase order and item receipt, where the workflow had been routing on the bill total. We added fields to store the three-way match exception amount against the purchase order and the receipt, and changed the approval workflow to route on that amount, with a separate path for exceptions under $100.
Some accounts have the workflows and do not use them. In 2026 environment assessments, two client accounts had vendor bill or invoice approval workflows configured but not running, and at one distributor AP approvals went through a weekly email. Purchase order forms can also fill up with unused custom fields. At an industrial equipment manufacturer, a manager described their purchase order form this way: “50% of that purchase order is just blank… a lot of those are custom fields which were made previously for some kind of project.”
Our article on NetSuite approval workflows covers approval design beyond procurement, and the NetSuite SOX compliance guide covers the audit trail approvals leave behind.
How Nuage approaches procurement and bill approval work
Procure-to-pay work, covering purchase orders, vendor records, bills, payments and approval routing, made up 192 of the 3,241 client support tickets Nuage handled between February 2023 and July 2026. By the time we measured, 105 of the 192 had closed, with a median of 15.2 calendar days.
In recent procurement and bill approval projects, including the ones above, our team has worked through these steps:
- Find out how approvals actually happen today. In the assessments above, approval workflows existed in the account while AP approvals ran by email, so we check the live process as well as the configuration.
- Read the workflow conditions and the tolerance fields before changing anything. In both tolerance tickets above, the cause was missing tolerance values.
- Agree the routing rule with the client. The food and beverage company asked for its rule: route on the exception amount, with a separate path for exceptions under $100.
Our team does this work as part of ongoing NetSuite optimization and managed services.
NetSuite Advanced Procurement FAQ
Is Advanced Procurement included with a standard NetSuite license?
Advanced Procurement is a separate module. Oracle’s Procurement Dashboard documentation states that the dashboard is available in the Advanced Procurement SuiteApp included in the module, and directs customers to their NetSuite sales representative to purchase it. Ask your account team which procurement features your current subscription includes and what adding the module would involve.
What is the difference between a purchase request and a requisition in NetSuite?
A purchase request is entered by an employee who already knows the vendor and price, and it covers one vendor. A requisition states the need without requiring a vendor or price, can include items from several vendors, and goes through approval before a buyer orders it. Requisitions suit companies where a central buyer sources purchases and wants to combine demand across departments.
Can I consolidate multiple requisitions into a single purchase order?
Yes. On the Order Requisitions page, buyers see approved requisition lines from across the company, select the lines to order and create purchase orders in one pass. Lines for the same vendor are ordered together, which reduces the number of purchase orders and gives the buyer a larger order to negotiate with. Each line needs a vendor and rate first.
What is the NetSuite purchasing module?
NetSuite’s purchasing features handle vendor records, purchase requests, purchase orders, item receipts, vendor bills and payments. Companies with a central buying team add the Advanced Procurement module for requisitions, purchase contracts, blanket purchase orders, requests for quote and the Procurement Dashboard. Companies building production plans also connect purchasing to demand planning, which suggests purchase orders from forecast demand.
How does three-way match work in NetSuite?
The 3 Way Match Vendor Bill Approval workflow compares the vendor bill with its purchase order and item receipt. If quantities or amounts differ by more than the tolerance or difference limits set on the item, vendor and subsidiary records, the bill routes for approval. Leaving those limits blank changes which checks the workflow runs, so set them before go-live and test with bills above and below each limit.
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 procurement and bill approval projects in this article are our team’s work.
