P2P, or Procure to Pay, is a commercial process in which companies request, obtain, and pay for goods and services. Because completing a single order frequently requires numerous manual processes, companies automate the process by utilizing an ERP platform like Oracle or NetSuite.
Key Takeaways
- Manual P2P processes create compounding costs: 46% of organizations were still processing more than half of their invoices manually as of the 2023 PPN Survey. Manual supplier onboarding alone costs up to $35,000 per vendor versus $2,400 with automation. Every manual step is a cost and a control gap.
- P2P is not just an AP function: It spans purchasing, receiving, finance, and accounting. When these teams work in disconnected systems, duplicate payments, unapproved purchases, and invoice discrepancies are routine outcomes. NetSuite connects all of them in a single transaction flow.
- Three-way matching is the core financial control: NetSuite automatically matches purchase orders, item receipts, and vendor bills before payment is authorized. This single control prevents the most common sources of overpayment and fraud in the P2P cycle.
- Advanced Receiving separates receipt from billing for better control: Enabling this feature lets receiving staff log item receipt before the AP team enters the vendor bill. Without it, these two steps collapse into one, reducing visibility and control.
- The vendor portal reduces email-based communication: Giving vendors access to their own portal to view POs, submit invoices, and check payment status removes a significant source of back-and-forth and keeps transaction records centralized.
- Approval workflows must be configured before go-live: SuiteFlow and SuiteApprovals both support multi-tier procurement approval routing. Without this configured correctly, purchases get committed without authorization, which is the first place spend control breaks down.
What is NetSuite Procure to Pay?
Procure to Pay (P2P) is the end-to-end process that integrates purchasing and accounts payable into one continuous workflow. It starts when someone in the organization identifies a need for goods or services and ends when the supplier receives payment. Between those two points are internal approvals, vendor communication, receipt of goods, invoice verification, and payment processing.
As NetSuite’s own P2P documentation explains, the process integrates the purchasing department with accounts payable to boost efficiency and brings together multiple stakeholders: the requesting employee or department, budget owners, procurement professionals, AP staff, and suppliers. When these groups work from different systems or communicate by email, every handoff between them is a potential failure point.
In NetSuite, the P2P process works through a connected chain of transactions that build on each other. A purchase requisition converts to a purchase order. A purchase order generates an item receipt. An item receipt enables the vendor bill. The vendor bill feeds the payment run. The payment posts to the general ledger. Each step references the records from the step before it, creating a complete audit trail from the original request to the final GL entry.
Core Features of the NetSuite P2P Process
Purchase Requisition with Approval Routing
The purchase requisition is the internal gate that prevents unauthorized purchases. It captures what is needed, who needs it, and for which department, before any commitment is made to a supplier. Approval routing through SuiteFlow or SuiteApprovals ensures that every requisition is reviewed by someone with budget authority before it advances to a purchase order. For businesses that need multi-tier approval chains based on amount, department, or budget availability, this guide to NetSuite SuiteApprovals explains how to configure these routing rules correctly.
Purchase Order with Budget Commitment Tracking
The purchase order is the external commitment to the vendor and the internal signal that procurement has been authorized. In NetSuite, approved POs immediately reduce the available budget in the committed cost calculation, which means finance sees the real budget position, not just what has been invoiced. This prevents the common problem where a department appears within budget in accounting but has already committed to more spending than remains in their allocation.
For recurring or high-volume purchasing with the same supplier, blanket purchase orders reduce the administrative load by establishing a pre-approved framework for multiple releases without a new PO approval each time.
Item Receipt and Goods Inspection
The item receipt records what physically arrived and creates the reference document that three-way matching uses to verify the vendor’s invoice. It is also the record that updates inventory. When goods are received, NetSuite automatically determines where received items should go: directly to a work order build, to a specific bin or warehouse location, or to fill an outstanding customer order. For businesses using lot or serial number tracking, the item receipt is where those identifiers are entered and attached to the inventory record.
Three-Way Matching
The three-way match compares the PO (what was ordered at what price), the item receipt (what arrived), and the vendor bill (what the supplier is charging). All three must align within configured tolerance limits before payment is authorized. Invoices that do not match are flagged and routed to AP for resolution before payment is released. This is the control that catches billing errors, quantity discrepancies, and fraudulent invoices before money leaves the bank.
Vendor Return Authorization and Vendor Credit
When goods must be returned to a supplier, NetSuite’s Vendor Return Authorization records which items are being returned, in what quantity, and the reason for the return. The return authorization goes through an approval step before goods are shipped back. Once the return is processed, a vendor credit is created that can be applied against future payables from that vendor, ensuring the credit is used rather than lost in a manual reconciliation.
Setting up Procure to Pay in NetSuite
Using NetSuite Procure to Pay requires more than one step. Following these procedures and, if feasible, automating them will increase your company’s procurement efficiency.
Create A Vendor
To use Procure to Pay, you must first create a vendor in the NetSuite system.
Go to Lists > Relationship > Vendor > NewCertain necessary vendor information, including the company name, must be filled out. You can also include your contact information, the vendor’s address and website, and any valuable remarks about them. You can also provide the contact information of employees of this firm, such as sales representatives or another critical point of contact.
Create An Item
You will need to record the item you wish to buy.
Choose Lists > Accounting > Items > New > Non-Inventory > Purchase to start creating your item.This stage will display a form that requires the following fields to be filled out: name of item, number of item, tax schedule, and vendor. If you offer an item to a particular merchant, it will always be available when you choose it in the future.
Create Vendor & Item Requisition
Next, you must draft a requisition. A requisition is a formal request for products or services delivered to your company’s purchasing department, individual, or division. Requesting quotes is simple.
Click Purchases > Transactions > Enter Requisition > NewThe following information is required to be provided: Name of the requester, Date, Required Item, and Department. Once you hit “Submit,” the status of your requisition order will change to “Pending.” You must order a specific item requisition to proceed to the next phase.
A purchase order will be generated upon the submission of the order requisition. Once “OK” is selected, the status will become “Started.”
Enter Purchase Order
- The purchase order is automatically prepared after the request is received.
- To locate the purchase order, go to
Transactions >. Purchase > Enter Purchase Order > List - To add data to the order, you must choose “Edit.” You can enter information such as Kind, Price, and Quantity here. This will create a pending receipt.
Generate An Item Receipt
Following receipt of the item from the vendor, you must:
- Examine the products in light of the information on the purchase order.
- Examine them for any damage or other problems with quality.
- After that, you have to enter the data into NetSuite and produce a receipt.
Create An Invoice
Next, the vendor will give you an invoice or include it with the items you ordered. Invoices should include the following:
- A detailed description of goods.
- Pricing information
- Payment due date
This information must be reconciled to the purchase order and entered into the NetSuite system.
Settle Payment with Vendor
The accounts payable procedure requires tracking your transactions and paying your vendor bills. If everything is in order, send your payment to the merchant.
Check the General Ledger
- Once the payment is sent, you can compare it to the general ledger (GL).
- Go to Bill Payment > Action > GL Impact.
This phase will demonstrate how your purchase has impacted the general ledger and account balances.
Configuration Decisions That Determine P2P Effectiveness
The setup steps described above are the mechanics. The configuration decisions below determine whether the process actually delivers control.
Approval Thresholds and Routing Rules
Configure approval thresholds before you go live, not after the first unapproved purchase has already been made. Define the amount at which each tier of approval is required, which roles are authorized to approve at each tier, what happens when an approver is unavailable (delegation), and how long a pending approval can sit before it escalates. Every one of these parameters should be documented and signed off by both procurement leadership and finance before implementation.
Preferred Vendor and Item Master Alignment
The item master and vendor master must be complete and accurate before the P2P process has value. An item record without a preferred vendor assigned means the purchasing team has to look up the vendor manually each time, which introduces inconsistency and allows ad hoc supplier selection outside of approved vendor lists. Audit item records for preferred vendor assignment before go-live.
Three-Way Match Tolerance Settings
NetSuite allows you to configure tolerance limits for three-way matching: a vendor bill that is within a defined percentage or dollar amount of the PO will pass matching automatically rather than requiring manual review. Setting these tolerances too wide reduces the effectiveness of the control. Setting them too tight creates excessive manual review for small legitimate variances. Configure them based on your actual supplier billing patterns, not on a theoretical ideal.
Critical features of Procure to Pay in NetSuite
Several NetSuite features need to be enabled before the full P2P workflow is available. Navigate to Setup > Company > Enable Features and confirm the following are active:
- Accounts Payable (A/P): Required for vendor bill processing and payment runs.
- Purchase Orders: Enables the PO transaction type and the requisition-to-PO conversion flow.
- Purchase Requests: Enables the internal requisition form that precedes the PO.
- Advanced Receiving: This is the most important non-obvious setting. It separates item receipt from billing, allowing receiving staff to log what arrived from a vendor before the AP team enters the invoice. Without Advanced Receiving, receipt and billing collapse into one step, reducing your ability to enforce three-way matching and control.
Advanced Receiving is worth specific attention because its absence is the most common configuration gap in NetSuite P2P setups. When receiving and billing are the same action, you lose the ability to confirm that what arrived actually matches what was ordered before you commit to paying for it. Enable it before you process your first purchase order.
Final Thoughts
The NetSuite Procure to Pay process works well when it is configured correctly and used consistently. Every skip in the process, a purchase made without a requisition, a vendor bill entered without matching it to a receipt, a payment processed without going through the approval chain, creates a gap that audit and reconciliation have to close manually after the fact. Configuring the process correctly from the start is significantly less expensive than trying to reconcile three months of unstructured procurement data.
If you are implementing NetSuite P2P for the first time, start with the features that deliver the most control: Advanced Receiving, three-way matching, and SuiteFlow-based approval routing. Get those right before adding complexity like blanket POs, vendor portals, or Advanced Procurement capabilities.
Folio3’s NetSuite procurement implementation specialists have configured the full P2P cycle for businesses across manufacturing, distribution, professional services, and retail. If your current procurement process is generating reconciliation problems, unauthorized spending, or vendor relationship friction, the configuration assessment is a practical first step toward understanding exactly where the gaps are and what it takes to close them.
