How Requisition Status Works
A requisition begins with information such as the requested item or service, quantity, expected price, department, subsidiary, required date, and accounting classification. Once submitted, its status changes according to the actions taken by requesters and approvers.
The status therefore acts as an operational signal within procurement. Purchasing teams can distinguish requests that are ready for ordering from requests still awaiting authorization, while managers can identify pending spending decisions that may affect budgets or upcoming commitments.
If supplier information flows between ERP and connected finance applications, API Integration Vendor Data provides a framework for keeping vendor records consistent as approved requests progress into supplier-facing transactions.
Common Requisition Status Stages
- Draft: The requester is preparing the requisition and has not yet submitted it for approval.
- Pending approval: The requisition has been submitted and is waiting for one or more authorized reviewers.
- Approved: Required authorization has been completed and the request can progress toward purchasing activity.
- Rejected: An approver has declined the request, typically with a reason that allows the requester to understand the decision.
- Converted: The approved request has progressed into a formal purchasing transaction.
- Cancelled or closed: The request is no longer expected to progress further.
The exact statuses available can depend on the organization's configuration and approval design, so users should interpret them according to the workflow implemented in their NetSuite environment.
Using Status for Approval Control
Status reporting helps managers identify requisitions that have remained pending beyond the expected approval period. A request awaiting authorization for several days may require reviewer attention, while a large number of approved but unconverted requests may indicate future purchasing commitments that have not yet become supplier orders.
An Accounts Payable Approval Workflow applies later when supplier invoices require financial authorization, but requisition status provides the earlier purchasing-side control. Together, these stages preserve a clear authorization trail from spending request through recognized liability.
Accurate status information also allows departments to distinguish committed plans from requests that remain under review, improving budget and cash requirement forecasting.
From Approved Status to Invoice Validation
Once an approved requisition progresses into an order and goods or services are received, downstream invoice processing can use the purchasing evidence established earlier. Supplier invoices may then move through capture, validation, GL coding, matching, approval, and posting.
An AP Invoice Matching Workflow can compare invoice details with approved order and receipt information before posting. Vendor Invoice Processing 2025: AI Supplier Workflow Guide is relevant when teams evaluate how invoice capture, extraction, matching, coding, approval, and posting follow the purchasing stages reflected by requisition status.
AP Automation Software can automate invoice processing and payment planning around approved purchasing records, helping finance teams maintain controlled downstream activity after the requisition has completed its earlier lifecycle.
Status Visibility and Supplier Administration
Approved requisitions that progress toward supplier commitments depend on accurate vendor management data, including supplier identity, terms, tax information, and payment details. Consistent records help ensure that the purchasing transaction created from an approved request is associated with the correct supplier.
Status visibility is also useful for operational reporting. Teams can monitor how many requisitions are pending, approved, rejected, or converted and identify departments or approval levels where requests remain open longer than expected.
Connection to Payments and Finance
Requisition status occurs early in the purchasing lifecycle, but the approved request eventually influences future financial obligations. Once invoices reach accounts payable, finance teams can evaluate approvals, payment methods, discounts, fraud controls, settlement dates, and cash outflows.
Approved payments can then be scheduled according to supplier terms and liquidity priorities. Maintaining status continuity from requisition through ordering and invoicing gives finance teams better visibility into how anticipated purchasing activity develops into actual liabilities and cash requirements.
Status Metrics and Best Practices
A useful metric is Pending Requisition Rate = Pending Requisitions / Total Open Requisitions × 100. If 180 of 600 open requisitions are awaiting approval, the pending requisition rate is 180 / 600 × 100 = 30%.
A higher rate can indicate a larger volume of requests awaiting management action, while a lower rate generally means a greater share of open requests has progressed beyond approval. The appropriate level depends on purchasing volume, approval timing, and organizational policy.
Teams should review aging requisitions, maintain current approval hierarchies, close requests that are no longer needed, and monitor approved requests that have not progressed into supplier orders. Clear ownership and status reporting improve spend visibility and support stronger purchasing decisions.
Summary
NetSuite Purchase Requisition Status shows where an internal purchase request sits in its lifecycle, from draft and pending approval through approval, rejection, conversion, or closure. Reliable status tracking strengthens authorization controls, helps teams manage pending spending decisions, and provides upstream visibility for supplier ordering, invoice validation, payment planning, cash flow forecasting, and financial reporting.