For US controllers and purchasing leads who want one clear NetSuite flow from purchase request to vendor payment.
Last reviewed: 23 October 2026. Product details reflect this review date. Availability and behavior can vary by account, role and release.
The NetSuite procure to pay process runs every step of buying in one system: purchase request, purchase order, approval, item receipt, vendor bill, three way match and payment. Each step creates a linked record, so finance can trace any payment back to the person who asked for the goods. Spend, stock and payables update as the work happens.
Procure to pay is where purchasing, the warehouse and accounts payable meet. When the steps live in email, paper and a separate payments tool, bills get paid twice, discounts are missed and nobody can say what the company owes. NetSuite keeps the whole chain on one record trail.
Procure to pay, often shortened to P2P, is the full cycle from a staff member asking to buy something to the vendor being paid. It covers requests, purchase orders, approvals, receiving, vendor bills, matching and payment.
In NetSuite, each stage is a transaction type. A purchase requisition becomes a purchase order. The purchase order is received with an item receipt. A vendor bill is created from the purchase order, and a bill payment closes it. Every record links back to the one before it, which is what auditors want to see.
Here is a typical flow for a US company.
Steps 5 and 6 are where most of the time goes in a paper process. NetSuite bill capture features can read a PDF invoice and suggest the bill, and matching rules let clean bills move straight to approval. Our guide to NetSuite three way match exceptions for vendor bills covers the bills that don't match.
A clear owner for each step stops bills from waiting in someone's inbox. It also gives you segregation of duties, which means no single person can create a vendor, approve a purchase and release the payment.
| Step | Owner | Key control |
|---|---|---|
| Request | Requester | Item, quantity and reason recorded |
| Purchase order | Purchasing | Approved vendor and agreed price |
| Approval | Budget owner | Approval limits by amount and department |
| Receipt | Warehouse | Receive only what arrived |
| Vendor bill | Accounts payable | Bill created from the purchase order |
| Three way match | Accounts payable | Price and quantity tolerances |
| Payment run | Finance or treasury | Second approver on the payment batch |
Use NetSuite roles to enforce the split. Accounts payable can enter bills but not change vendor bank details. Purchasing can raise orders but not approve its own. Our post on designing NetSuite accounts payable approval controls explains how to set the limits.
A hypothetical Georgia manufacturer orders 400 units of a component at $25 each. The vendor ships 380 units but bills for all 400. Terms are 2% off if paid within 10 days.
| Stage | Amount |
|---|---|
| Purchase order (400 units at $25) | $10,000 |
| Item receipt (380 units) | $9,500 |
| Vendor bill from the vendor (400 units) | $10,000 |
| Difference flagged by the three way match | $500 |
| Bill approved after the vendor credit | $9,500 |
| Early payment discount at 2% | $190 |
| Payment sent | $9,310 |
NetSuite flags the bill because the billed quantity is higher than the received quantity. Accounts payable holds it and asks the vendor, who confirms the short shipment and sends a $500 credit note. Accounts payable records it as a vendor credit. The approved bill of $9,500 is paid on day 8, so the 2% discount applies and the payment is $9,310. Without the match, the company would have paid $10,000 for goods it never received.
These figures are illustrative. Your terms and tolerances will differ.
Most delays come from a handful of issues. NetSuite gives you a fix for each.
Set a rule that any spend above a set amount needs a purchase order, and make vendors quote the PO number on every invoice. Bills without one go to a review queue instead of straight to payment.
Route approvals in NetSuite by amount and department, with a backup approver for holidays. Approvers see pending items in their NetSuite reminders and the mobile app, and every decision is saved on the record.
The same invoice can arrive by email, post and a vendor portal. Turn on duplicate number checks and train the team to search before entering. Our guide to NetSuite duplicate vendor invoice controls shows the setup.
Run the payment selection by discount date as well as due date. A weekly payment run with clear cutoffs keeps both under control.
Track a few measures on a NetSuite dashboard and review them each month.
These measures show where the cycle slows. A rise in bills held by the match, for example, often points to one vendor with pricing problems or a receiving step being skipped. Procure to pay is the mirror of the sales side, which our guide to the NetSuite order to cash process covers from quote to payment.
At CuriousRubik, we map your current purchasing flow, find the step that slows payables most and fix it in NetSuite first. Read about our NetSuite implementation approach and our NetSuite services in the United States.
The main steps are purchase requisition, purchase order, approval, item receipt, vendor bill, three way match and bill payment. Each step is a linked transaction in NetSuite, so you can trace a payment back to the original request. Many companies automate approvals and matching so clean bills move without manual work.
Yes. NetSuite compares the vendor bill with the purchase order and the item receipt. You set price and quantity tolerances, and bills that fall outside them are held for review. Accounts payable then resolves the difference with the vendor, often through a vendor credit, before the bill is approved for payment.
Yes. With the Electronic Bank Payments SuiteApp, NetSuite creates payment files for US banks, including ACH, from the bills selected in a payment run. Vendor bank details sit on the vendor record with restricted access. Finance reviews the batch, a second approver releases it and the payments post to the ledger automatically.
Vendors who need a Form 1099 are flagged on the vendor record. Because every payment runs through NetSuite, the year end 1099 figures come from the same payment records, with no separate list to keep. Payments made by card are usually handled differently, so confirm which vendors and payments need a form with your tax adviser.
The sales side of the cycle, from quote to cash in the bank.
How the three purchasing records differ and what each one proves.
How to handle vendor bills that don't match the order or the receipt.