Use a NetSuite purchase requisition to capture an internal need and route it toward purchasing. Use a purchase order to document the approved order placed with a supplier. The design decision is where your business separates the employee's request, sourcing activity and authority to commit company funds.
NetSuite also has a Purchase Requests capability, which should not be treated as another name for requisitions. Oracle explains that requisitions can be raised before the vendor or exact price is known, split across suppliers, or consolidated into purchasing. Purchase requests follow a different, single-vendor relationship.
Begin with the employee's information
Ask what the requestor actually knows. They may know the required equipment and delivery date but not the supplier, catalogue item or final price. Requiring them to invent those details makes a form look complete while pushing unreliable data into purchasing.
Define a minimum request: business purpose, specification, quantity, required date, destination, budget owner and estimated amount where known. Include an attachment only when it helps a buyer understand the requirement. Avoid collecting sensitive employee information in an unrestricted purchasing memo.
Clarify whether an employee is requesting a stock item, service or expense. The eventual purchase order and receipt evidence may differ. A service request needs a named person who can confirm completion; a stock request needs a receiving location and unit.
Separate need approval from supplier commitment
Approval of a requisition can mean that the business accepts the need and budget expectation. It does not necessarily authorize any supplier, price or contractual term a buyer later selects. Define which changes require renewed approval.
For example, require review when the final order exceeds a specified policy threshold, changes the receiving entity or introduces a materially different service. Those thresholds are company policy and need configuration and testing; they are not automatically implied by enabling requisitions.
Make the buyer's authority explicit. Who can select a new vendor, approve payment terms or release the order externally? Keep these responsibilities visible even if the same person performs more than one role in a small company.
Decide whether consolidation helps
Requisitions can support centralized buying across requests. A buyer might combine compatible demand for a supplier while preserving which employee or department requested each line. This can simplify ordering, but the destination and required date still need to survive consolidation.
Do not combine lines simply because they share a description. Different specifications, legal entities, delivery dates or budget approvals can make consolidation inappropriate. Establish the conditions under which requests can be grouped and how allocated quantities will be communicated back to requestors.
If almost every request is already a fully specified, single-vendor order, a simpler purchase-request or direct purchase-order process may fit. Evaluate the actual approval and sourcing requirements rather than assuming an additional record always improves control.
Preserve the downstream evidence
A purchase order is followed by physical receipt or service acceptance, supplier billing and payment. Define who owns discrepancies at each stage. A requisition marked ordered does not prove that the employee received the requested goods.
Track partial orders, partial receipts, cancelled requests and residual quantities. When the business no longer needs the remainder, close it through an approved process and preserve the reason. Otherwise, outdated demand can remain in a buyer's queue and be ordered again.
Where a supplier requires an advance payment, introduce a separate prepayment control. NetSuite's vendor prepayment application is a distinct accounting step with eligibility rules; a purchase order alone does not establish that an advance has been correctly applied to a bill.
Hypothetical request-to-order example
Three departments request a total of eight identical monitors for the same office. The approved requests specify the model and need-by date, but the buyer has not selected a supplier. Purchasing confirms a suitable vendor and creates a consolidated order while retaining the relationship to each department's demand.
The supplier can deliver six immediately and two next month. The buyer checks whether the delayed date remains acceptable for the affected employees. Receiving records six monitors, and the outstanding two stay visible until delivered or cancelled.
Now suppose the supplier offers a different model at a higher price. The buyer follows the agreed change-approval rule instead of treating the original requisition approval as permission for any substitute. This hypothetical example illustrates the responsibility split; the exact record flow depends on enabled features and account configuration.
A decision checklist for the purchasing team
Choose the process by answering these questions:
- Does the requestor know the vendor and final price?
- Can one request contain needs from several suppliers?
- Should buyers consolidate demand from several employees?
- Which approval accepts the need, and which permits supplier commitment?
- Which changes trigger renewed review?
- How are requestors informed about partial or delayed delivery?
- Who closes abandoned demand and resolves invoice differences?
Capture the answers in a short policy with transaction examples. Train requestors on what they need to provide and buyers on what they are authorized to decide.
Test roles and exceptions
Use ordinary employee, buyer, approver and receiving roles in acceptance testing. Confirm that employees see the appropriate requests and cannot bypass required approvals. Test an absent approver, a rejected request, a split order, a price increase and a cancelled remainder.
Also test the reporting language. “Approved,” “ordered,” “received” and “paid” should mean different things to users. Clear status definitions prevent employees from assuming that approval guarantees an imminent delivery.
The right requisition design gives employees a simple way to express demand and gives purchasing enough control to source it responsibly. Select the records and approval boundaries that make those responsibilities clear, then prove the complete path through receipt and billing.
Related resources