NetSuite Purchase Order Process 2026: From Requisition to Receipt

Key Takeaways

• The NetSuite purchase order process spans six core stages: purchase requisition, requisition approval, PO creation, PO approval and vendor communication, item receipt, and three-way matching with vendor bill processing.
• Purchase requests and purchase requisitions are different. A purchase request is typically used when the employee already knows the vendor and price. A purchase requisition is more flexible and can be routed to a buyer for sourcing.
• Approval routing is threshold-based. NetSuite can route POs and requisitions to supervisors or other approvers based on purchase approval limits and workflow rules.
• Three-way matching is automated when the workflow is installed and configured. NetSuite’s 3 Way Match Vendor Bill Approval Workflow validates vendor bills against purchase orders and item receipts using configured exception criteria.
• Blanket purchase orders help manage recurring purchasing. They let teams define vendor pricing, terms, and release activity under a broader purchasing agreement.
• Most procurement problems are not platform limitations. They usually come from missing purchase limits, delayed item receipt entry, incomplete item/vendor data, or approval workflows that add more friction than control.

What Is the NetSuite Purchase Order Process?

The NetSuite purchase order process is the sequence of steps a company follows to request, approve, order, receive, and pay for goods or services inside NetSuite. The full cycle begins before the vendor-facing purchase order is created and ends when the vendor bill is matched, approved, and ready for payment.

The six major stages are:

1. Purchase Requisition: An employee submits an internal request for goods or services.
2. Requisition Approval: The request is reviewed according to approval rules and purchase limits.
3. Purchase Order Creation: A buyer converts the approved request into one or more purchase orders.
4. PO Approval: The purchase order is approved before being sent to the vendor.
5. Item Receipt: The receiving team records what was physically received.
6. Three-Way Matching: The vendor bill is checked against the PO and item receipt before payment approval.

This broader cycle is often called procure-to-pay. Finance teams that treat procurement as a full lifecycle, rather than just a PO entry task, usually get cleaner audit trails, more reliable accruals, and better control over committed spend.

NetSuite supports two common starting points for procurement. A purchase request is used when a non-buyer employee already knows the vendor and expected price. Once approved, it can become a purchase order. A purchase requisition is more flexible. It can include partial information, multiple vendors, or notes for a buyer who will confirm sourcing and pricing before creating the PO.

For companies running NetSuite across multiple subsidiaries, departments, or locations, the purchase order process can be configured to reflect different approval paths while still supporting consolidated reporting.

NetSuite Purchase Order Process: Stage-by-Stage Overview

Step 1: Creating a Purchase Requisition in NetSuite

A purchase requisition is the internal document an employee uses to request that the purchasing team buy goods or services. It is not a vendor-facing commitment. It is an intake form that captures what the employee needs and routes that request for review.

In NetSuite, a requisition can include partial information. For example, the requester may know the item but not the final vendor, or may estimate the cost while the buyer confirms pricing. This is useful when purchasing requires sourcing, quote comparison, or vendor selection.

Key fields in a NetSuite requisition often include:

• Item or expense category
• Quantity and estimated unit cost
• Required-by date
• Delivery location
• Department, class, subsidiary, or project
• Notes for the buyer
• Preferred vendor, if known

One requisition can include lines that ultimately go to different vendors. When the buyer converts the requisition, NetSuite can split lines into separate purchase orders based on vendor assignments and buying decisions. This makes requisitions especially useful for companies where employees know what they need but the procurement team controls vendor selection.

A purchase request is different. It is usually the faster path when the employee already knows the vendor, item, and price. Once approved, the purchase request can be converted into a purchase order without the same sourcing step.

Use a purchase request when the vendor and price are already known. Use a purchase requisition when procurement needs to source, confirm, or split the request.

Purchase Request vs. Purchase Requisition

Step 2: The Requisition Approval Workflow

After a requisition is submitted, NetSuite can route it through an approval workflow. The approval path depends on how the account is configured. Many companies route the request to the employee’s supervisor first, then escalate if the amount exceeds the supervisor’s approval limit.

The workflow typically checks:

• The requester’s purchase limit
• The supervisor’s approval authority
• The total requisition amount
• Department, subsidiary, class, project, or location
• Whether the request is routine or exceptional
• Whether finance review is required

If the first approver does not have enough authority, the workflow can continue up the hierarchy until it reaches someone with the proper limit. This threshold-based routing helps avoid routing every request to the same executive approver.

Companies can customize requisition approval in SuiteFlow. Common rules include:

• Auto-approval for low-risk purchases under a defined amount
• Department head approval for department-specific purchases
• Finance review for capital expenditures
• Project manager approval for project-related purchases
• Dual approval for high-value or high-risk categories

Approvers may see requests in NetSuite task lists, dashboards, or email notifications depending on configuration. Approved requisitions move forward to purchasing. Rejected requisitions return to the requester with notes.

A well-designed requisition workflow is one of the strongest controls for stopping spend before a vendor commitment is made. The goal is not to add approvals everywhere. The goal is to make sure meaningful purchases are reviewed by the right person at the right time.

Step 3: Converting Requisitions to Purchase Orders

Once a requisition is approved, the buyer converts it into one or more purchase orders. This step turns an internal request into a vendor-facing document.

NetSuite supports different conversion approaches depending on how procurement is configured.

Manual Conversion

Manual conversion gives the buyer control. The buyer reviews approved requisitions, selects which lines to convert, confirms the vendor, checks pricing, and creates the purchase order.

This method is best when:

• Pricing changes often
• Vendor selection requires judgment
• The buyer needs to compare quotes
• Delivery timing must be coordinated
• Minimum order quantities or freight terms affect the decision

Manual conversion is common in companies where procurement is more strategic than transactional.

Automatic Purchasing

Automatic purchasing relies on item-level vendor and pricing configuration. When preferred vendors and purchasing data are maintained correctly, NetSuite can generate purchase orders from approved requisitions with less buyer intervention.

This works best when:

• Vendor relationships are stable
• Items have preferred vendors
• Pricing is predictable
• Purchasing volume is high
• Procurement wants to reduce manual PO entry

Manufacturers and wholesale distributors often benefit from this approach because they buy the same materials repeatedly from established suppliers.

Consolidating Lines

Buyers can consolidate lines from multiple requisitions into a single PO for the same vendor. This is useful when the vendor has minimum order quantities, volume discounts, or preferred shipping terms. NetSuite maintains traceability so teams can still see which requisition led to each PO line.

The finished purchase order usually includes the vendor, item details, quantities, unit costs, expected receipt date, shipping address, terms, and any special instructions. Once saved, it may route through a separate PO approval process before being sent to the vendor.

If your team is setting up procurement from scratch or redesigning it after an ERP migration, NetSuite Consulting can help create an approval structure that controls spending without slowing down routine purchasing.

Step 4: PO Approval and Vendor Communication

The PO approval workflow is separate from the requisition approval workflow. This matters because a requisition is an internal request, while a purchase order is the vendor-facing commitment. Many companies approve of both.

The Purchase Order Approval Workflow SuiteApp can route purchase orders based on amount, employee approval limit, supervisor hierarchy, or custom conditions. If the PO exceeds the creator’s authority, it routes to the appropriate approver. If that approver does not have enough authority, the workflow can escalate.

Once approved, the buyer sends the PO to the vendor. Common communication methods include:

1. Email from the PO record using a configured PDF template
2. Vendor Center access for suppliers that interact with NetSuite directly
3. EDI for high-volume vendors that exchange structured purchasing data

After the PO is sent, NetSuite helps teams track receipt and billing activity. The purchase order record can show quantities ordered, quantities received, quantities billed, and remaining open quantities. This gives purchasing and finance a shared view of what has been committed, received, and invoiced.

This real-time status visibility is one of the core reasons companies use NetSuite procurement instead of managing POs in spreadsheets. With the right saved searches and dashboards, teams can review open commitments by vendor, buyer, department, location, subsidiary, or expected receipt date.

What Are the PO Statuses in NetSuite?

NetSuite purchase order statuses show where a PO stands in the approval, receiving, billing, and closing cycle. The exact statuses shown can vary depending on enabled features, including Advanced Receiving and billing configuration.

Common PO statuses include:

These statuses are especially important during period close. A PO in Pending Receipt may represent committed spend for goods not yet received. A partially received PO may require follow-up with the vendor or receiving team. A received but unbilled PO may point to an accrual need.

For high-volume procurement teams, NetSuite saved searches and dashboard portlets can surface open POs by buyer, vendor, subsidiary, department, or expected receipt date. This eliminates manual tracking and helps finance catch issues before close.

Step 5: Receiving Goods and Recording Item Receipts

An item receipt is the NetSuite transaction that records goods received from a vendor. It confirms that the company physically received items against a purchase order. For inventory items, the receipt can also update inventory records depending on configuration.

Item receipt entry is a key operational control. Without it, AP cannot complete three-way matching cleanly because the system has no confirmation that the invoiced goods arrived.

How to Create an Item Receipt

To create an item receipt, the receiving team opens the approved PO and selects the receive action. The receipt form shows open lines from the purchase order. The receiver can then:

• Confirm the quantity received
• Record location, bin, lot, or serial details when applicable
• Note shortages, damage, or discrepancies
• Set the receipt date
• Save the receipt against the PO

The receipt should reflect what actually arrived, not what was ordered. If a vendor ships 60 units against a 100-unit PO, the receiving team should receive 60 units. The remaining 40 stay open.

Partial Receipts and Multi-Location Receiving

NetSuite supports partial receipts. This is important for manufacturers, distributors, and retailers where split shipments, backorders, and staged deliveries are common.

For multi-location companies, receiving can often be recorded by location while purchasing is managed centrally. This supports centralized buying with decentralized warehouse operations.

Why Same-Day Receipt Entry Matters

Delayed receipt entry is one of the most common causes of AP bottlenecks. If goods arrive Monday but the receipt is not entered until Friday, AP may receive the vendor bill before NetSuite shows the goods as received. That creates a matching exception, slows payment approval, and forces manual follow-up.

A same-day receipt entry policy keeps procurement, inventory, and AP aligned. It also improves inventory accuracy and helps finance make better accrual decisions.

For companies with complex warehouse, inventory, or receiving workflows, NetSuite Managed Services can help keep procedures aligned after go-live.

Step 6: Three-Way Matching and Vendor Bill Processing

Three-way matching verifies a vendor bill against the original purchase order and the item receipt before payment is approved. In NetSuite, this can be automated through the 3 Way Match Vendor Bill Approval Workflow, which is part of the NetSuite Approvals Workflow SuiteApp.

The workflow checks whether the vendor bill agrees with the PO and receipt within configured tolerance rules. If it does, the bill can continue through approval. If it does not, NetSuite can flag an exception for AP review.

What Three-Way Matching Checks

A typical match reviews:

1. Purchase order: Were the item, quantity, and unit cost ordered?
2. Item receipt: Were the invoiced goods actually received?
3. Vendor bill: Does the bill fall within configured tolerance and exception criteria?

Common exceptions include:

• Vendor billed more than the PO quantity
• Vendor billed more than the received quantity
• Unit price differs from the PO
• PO was amended but the vendor billed against old terms
• Receipt was entered late or incorrectly

Three-way matching is a strong control against duplicate invoices, overbilling, and payments for goods that were never received. It also helps AP focus on exceptions instead of manually checking every bill.

For service purchases or expense lines where physical receiving is not applicable, teams may use PO-based bill approval, two-way matching practices, or a custom workflow that validates the bill against the purchase order without requiring an item receipt. The right approach depends on item type, approval policy, and finance control requirements.

When vendor bills are entered into NetSuite accounting software, matching rules help determine whether the bill should continue to approval or be routed for review.

Blanket Purchase Orders for Recurring Procurement

Blanket purchase orders are used for recurring purchases from a vendor over a defined period. Instead of creating a brand-new PO every time the company reorders, the blanket PO defines the broader purchasing agreement. Releases are then created against that agreement.

Blanket POs are useful when a company has:

• Recurring raw material purchases
• Monthly MRO purchases
• Office supply agreements
• Vendor agreements with fixed pricing
• Repeated purchases under a known contract period
• Regular replenishment from a strategic supplier

In NetSuite, a blanket PO can define the vendor, item list, pricing, total commitment, and effective period. Each release references the blanket PO and draws against the agreement. This can reduce repetitive approvals and help buyers maintain control over recurring spend.

The Blanket Purchase Order Approval Workflow can validate blanket POs against purchase limits before they become active. Companies may also configure release-level rules so routine releases move quickly while larger or unusual releases still require review.

For manufacturing and wholesale distribution companies with high-frequency suppliers, blanket POs can reduce administrative overhead and help procurement focus on vendor performance, pricing, lead times, and supply continuity.

NetSuite Advanced Procurement Features

NetSuite Modules include Advanced Procurement capabilities for companies with more complex purchasing requirements. Standard purchasing may be enough for smaller teams, but Advanced Procurement becomes more useful when procurement involves multiple departments, recurring agreements, competitive quotes, or complex approval needs.

Standard vs. Advanced Procurement Feature Comparison

Key Advanced Procurement capabilities include:

Purchase Requisitions provide a structured intake process when employees know what they need but not the final vendor, price, or sourcing path.

Blanket Purchase Orders support recurring purchasing agreements and help reduce repeated PO creation for predictable vendor relationships.

Purchase Contracts help manage formal vendor agreements, pricing, quantities, and performance over time.

Vendor RFQ Workflows support quote requests and vendor comparison before a purchase order is created.

Other related NetSuite capabilities may be configured alongside procurement. Landed cost tracking can help allocate freight, duties, and handling fees across received inventory. Vendor return processes can help manage goods returned to suppliers. Project purchasing controls can help associate purchases with project-level costs. These capabilities may depend on licensing, enabled features, and configuration.

Activating the right procurement features during NetSuite Implementation or a later NetSuite Optimization project can reduce manual work and improve cost visibility.

Configuration Best Practices for NetSuite Procurement

Strong procurement performance depends on setup quality. The following practices consistently help NetSuite teams reduce approval delays and AP exceptions.

Configure Purchase Approval Limits by Role

Purchase limits should reflect responsibility and authority. A warehouse supervisor, department manager, controller, and VP of Operations should not all share the same approval limit.

If limits are too low, routine purchases escalate unnecessarily. If limits are too high, significant spend may go unreviewed. Review employee records, roles, and approval workflows together so authority limits match the company’s control policy.

Use Preferred Vendors and Item-Level Pricing

Preferred vendor and pricing setup drives purchasing automation. When item records include accurate vendor assignments, pricing, lead times, and purchasing units, buyers spend less time manually building POs.

This is especially important for manufacturers and distributors that repeatedly buy the same items from the same suppliers.

Keep Approval Workflows Practical

Approval workflows should create real control, not approval theater. Four or five approvers may look strong on paper, but they often slow routine purchases without reducing meaningful risk.

Use conditional routing so low-risk purchases move quickly and high-value or unusual purchases get the review they need.

Maintain Clean Vendor and Item Data

Bad vendor and item data creates downstream problems. Duplicate vendors, missing tax settings, incorrect purchasing units, and outdated vendor pricing can all cause PO, receipt, and bill matching issues.

Procurement cleanup should include vendor records, item records, approval limits, purchasing units, subsidiary access, and preferred vendor assignments.

Operational Best Practices for NetSuite Procurement

Even a well-configured NetSuite account can struggle if the team does not follow consistent procedures.

Enforce Requisition-First Discipline

Requisition-first purchasing creates a documented request before vendor commitment. It also gives finance and department leaders a chance to review spend earlier in the process.

This is especially important for companies with multiple departments, locations, or projects.

Enter Receipts the Same Day

Receiving delays create AP delays. Item receipts should be entered when goods are physically confirmed. Same-day receipt entry keeps inventory, procurement, and AP aligned.

Review Open POs at Period Close

Open POs represent committed spend that may not yet be received or billed. A monthly open PO review helps identify stale orders, goods in transit, missing receipts, and accrual needs.

Treat PO Amendments as Vendor Communication

If a PO changes after it is sent to the vendor, the updated PO should be communicated clearly. Otherwise, the vendor may ship or invoice against old terms, creating matching exceptions later.

Configuration Mistakes That Cause PO Approval Delays

Not Assigning Purchase Limits

If employees do not have accurate purchase approval limits, the workflow may route too many POs to the same person. This creates bottlenecks and frustrates both buyers and approvers.

Over-Engineering Approval Chains

A long approval chain slows procurement. Use more review only where risk justifies it. Routine, low-value purchases should not require the same path as major capital expenditures.

Ignoring Landed Costs for Imported Goods

Companies that import goods need a process for freight, duties, brokerage, and handling. If these costs are not captured correctly, inventory value and gross margin reporting can be distorted.

Failing to Train Requesters

Requesters need to know when to use purchase requests, when to use requisitions, and what information to include. Poor intake creates buyer rework and slows the whole process.

Operational Mistakes That Break Three-Way Matching

Skipping the Requisition Step

When employees bypass requisitions and create POs directly, the company loses an important pre-commitment review step. This can lead to budget surprises and inconsistent approval records.

Failing to Enter Receipts Promptly

Late item receipts are one of the most common causes of vendor bill exceptions. AP cannot match a bill to goods that have not been recorded as received.

Amending POs Without Updating the Vendor

If buyers change quantities, pricing, or delivery terms in NetSuite but do not send the updated PO to the vendor, the vendor may invoice based on the old version. That creates avoidable variances.

Using Blanket POs Without Release Discipline

Blanket POs only work if releases are tracked properly. If teams treat the blanket PO as an open-ended purchasing shortcut, spend visibility weakens.

Final Verdict: Which NetSuite Setup Is Right for Your Team?

There is no single best procurement setup for every company. The right NetSuite purchase order process depends on purchase volume, approval complexity, vendor structure, and finance control requirements.

For smaller teams with centralized buying, Standard NetSuite Procurement is often enough. It supports purchase requests, purchase orders, item receipts, and approval routing without requiring a more complex sourcing process.

For mid-market and enterprise teams, the Advanced Procurement SuiteApp is a better fit when the company needs purchase requisitions, blanket purchase orders, purchase contracts, or RFQ workflows.

For teams already using NetSuite but experiencing bottlenecks, the issue is often configuration. Common fixes include assigning purchase limits, simplifying approval chains, cleaning up item/vendor data, and improving receiving procedures.

Anchor Group is a certified Oracle NetSuite Alliance Partner with experience configuring procurement workflows for manufacturing, wholesale distribution, retail, and professional services clients. If your NetSuite purchasing process is creating friction, a focused review can usually identify the root cause quickly.

Book a 30-Minute Fix Session

How We Developed This Guide

This guide is based on common patterns across manufacturing, wholesale distribution, retail, and professional services environments.

Methodology included:

Workflow mapping: Reviewing the procurement lifecycle from request intake through vendor bill approval.

Configuration analysis: Identifying common setup gaps, including missing purchase limits, delayed receiving, and overbuilt approval workflows.

Feature assessment: Comparing when Standard Procurement is sufficient and when Advanced Procurement adds meaningful value.

Failure pattern review: Identifying the process issues that most often cause approval delays, AP exceptions, and poor spend visibility.

Assessment: NetSuite’s purchase order process is strong when configured correctly. The platform supports approval routing, receiving, three-way matching, blanket POs, and spend visibility. Most issues trace back to setup and operating discipline, not the core platform.

Next Steps for Your NetSuite Procurement Process

The NetSuite purchase order process gives mid-market businesses a configurable framework for procurement control: approval routing, PO tracking, receiving, vendor bill matching, and recurring purchasing support. The difference between smooth procurement and constant bottlenecks usually comes down to setup quality and daily process discipline.

If your NetSuite procurement workflow is slowing down buyers, approvers, receiving teams, or AP, Anchor Group’s certified NetSuite consultants can review your current process, identify the friction points, and recommend a practical remediation plan.

Frequently Asked Questions

What is the difference between a purchase request and a purchase requisition in NetSuite?

A purchase request is typically used when the employee already knows the vendor, item, and price. A purchase requisition is more flexible and can be used when a buyer needs to source the vendor, confirm pricing, or split the request across multiple purchase orders.

How does the NetSuite purchase order approval workflow work?

NetSuite can compare the PO amount against the creator’s purchase approval limit. If the amount exceeds that limit, the workflow routes the PO to a supervisor or another approver. Approval logic can be customized using SuiteFlow and workflow conditions.

Can NetSuite automatically create purchase orders from requisitions?

Yes, when item records, preferred vendors, and purchasing data are configured correctly. This is most useful for recurring purchases from stable vendor relationships.

What is three-way matching in NetSuite?

Three-way matching compares the vendor bill against the purchase order and item receipt. It helps confirm that the company is paying for what was ordered and received.

What is a blanket purchase order in NetSuite?

A blanket purchase order is a purchasing agreement used for recurring purchases over a defined period. Releases against the blanket PO draw down against the broader agreement.

How do partial receipts work in NetSuite?

If a vendor ships part of an order, the receiving team records only the quantity received. The remaining quantity stays open on the PO until it is received or closed.

What are common PO statuses in NetSuite?

Common statuses include Pending Supervisor Approval, Rejected by Supervisor, Pending Receipt, Partially Received, Pending Bill, Pending Billing / Partially Received, Fully Billed or Billed, and Closed. Exact statuses may vary by configuration.

How can I speed up NetSuite procurement approvals?

Start by reviewing purchase approval limits, removing redundant approval steps, using preferred vendors, improving item data, and creating auto-approval rules for low-risk purchases. A NetSuite Support Services review can identify where the workflow is slowing down.

Related Articles: 

• SuitePeople: NetSuite's HR & Payroll Module Explained
• NetSuite Carrier Integration: How to Automate Shipping With UPS, FedEx & More
• NetSuite Email Marketing: Campaigns, Templates & Automation
• NetSuite CRM vs Salesforce: Which CRM Is Better for Your Business?

Disclaimer: This content is for general informational purposes only and may not reflect current updates or your specific configuration—please confirm details with your Anchor Group consultant.