What is a purchase requisition? A complete guide

A purchase requisition is the document that stands between "someone wants to buy something" and "the company actually spends money." It's the first formal checkpoint in the purchasing process, and getting it right determines whether your finance team has visibility into spending or is left chasing invoices after the fact.

What is a purchase requisition?

A purchase requisition is an internal document an employee submits to request authorization to buy goods or services. It captures what they need, how much it costs, and why the purchase is necessary. That context lets approvers say yes or no before any money leaves the account.

The requisition isn't a purchase. It's a request for permission to purchase. That distinction matters because your finance team sees planned spending before it becomes a commitment.

Every approved requisition creates a record connecting the original request to the purchase order, invoice, and payment. That's the audit trail you'll need at close and during reviews.

Key elements of a purchase requisition form

A standard purchase requisition form captures six fields that give approvers everything they need to make a decision:

• Item or service description: What's being purchased, in enough detail that the approver doesn't have to ask follow-up questions (e.g., "50 ergonomic keyboards, Model X" vs. "office supplies")
• Quantity and unit cost: How many units and the price per unit, so finance can verify the total isn't based on a guess
• Estimated total cost: The bottom-line number the approver is authorizing, calculated from quantity and unit cost
• Vendor (if known): The preferred supplier, which helps procurement check whether the vendor is already approved or whether a better contract exists
• Business justification: Why this purchase is necessary now, tied to a project, team need, or operational requirement
• Delivery date or timeline: When the items are needed, so procurement can factor in lead times and prioritize accordingly

Standardizing these fields eliminates back-and-forth between requesters and approvers. When everyone fills out the same form with the same level of detail, approvals move faster and fewer requests get sent back for clarification.

Purchase requisition vs. purchase order

A purchase requisition is internal (asking permission). A purchase order (PO) is external (committing to a vendor). They're sequential, not interchangeable, and this is the most common point of confusion in procurement.

You can't issue a purchase order without an approved purchase requisition. The requisition is the gate; the PO is what passes through it.

Why purchase requisitions matter

Purchase requisitions give your finance team three concrete advantages before any money leaves the account.

Budget control and spend visibility

You see what your team plans to spend before the money leaves the account. Every requisition forces the requester to state a cost estimate and a business reason, which means finance can catch over-budget requests, duplicate purchases, and unnecessary spending before they become commitments. Getting this upstream visibility right saves an average of 16% annually on vendor spend.

Audit trails and compliance

Every purchase has a paper trail from request to receipt. The requisition captures who asked for what, who approved it, and when, creating the documentation you need for internal audits, SOX compliance, and external regulatory reviews. Without this trail, audit prep becomes a forensic exercise in reconstructing approvals from email threads and Slack messages.

Faster, more consistent approvals

Standardized routing means approvals don't stall in someone's inbox. When your requisition process has clear rules (under $5K goes to the manager, over $5K goes to VP and finance), requests move through the pipeline predictably instead of bouncing between people who aren't sure whether they're supposed to approve. With structured approval workflows, you'll close approvals 3 times faster.

Procurement shouldn't require a whole team to figure out.

Learn how one company cut their procurement cycle from 30 days to 3. It's simpler than you think.

Watch now →

How the purchase requisition process works

Every purchase requisition moves through five steps, from the initial request to final reconciliation against the invoice.

1. Submit the request

The requester fills out the purchase requisition form with the item description, quantity, estimated cost, preferred vendor, and business justification. The form captures the "why" as much as the "what," so approvers can evaluate whether the purchase is necessary without scheduling a meeting to ask.

2. Route for approval

The requisition moves to the appropriate approver based on dollar amount, department, or spending category. In mature processes, routing rules are automated: requests under $5K go straight to the department manager, while requests over $5K require VP and finance sign-off.

3. Review and approve

The approver checks budget availability, vendor selection, and business need. They approve, reject, or send the request back with questions. For higher-value requests, multi-level approval chains are common. The department head approves first, then finance confirms the budget allocation.

4. Convert to a purchase order

Once approved, the requisition becomes (or triggers) a purchase order, the external document sent to the vendor. This is the handoff from internal request to external commitment.

In automated systems, PO creation is instant. In manual processes, someone re-enters the requisition data into a separate system, which is where errors and delays appear.

5. Receive and reconcile

When goods or services arrive, the receiving team confirms that delivery matches the PO. The purchase requisition, purchase order, and goods receipt form the 3-way match that authorizes payment.

If all three documents agree on item, quantity, and price, finance clears the invoice for payment. If they don't, finance flags the discrepancy before payment goes out.

Procurement software automates the entire flow from submission to payment, and each step creates a connected record finance can trace at any point. Manual processes run the same steps over email and spreadsheets, where each handoff is a chance for delays and lost context.

How purchase requisitions fit into procure-to-pay

The purchase requisition is the control gate in the broader procure-to-pay (P2P) lifecycle. It sits between "someone wants something" and "the company commits to buying it." Everything downstream depends on getting this step right.

The full P2P cycle has seven stages:

1. Need identification: An employee or department recognizes a need for goods or services
2. Requisition: The employee submits a purchase requisition for approval (this is where spending gets authorized or blocked)
3. Sourcing: Procurement identifies and evaluates potential vendors
4. Purchase order: An approved requisition triggers a PO to the selected vendor
5. Receiving: The company confirms delivery of goods or completion of services
6. Invoicing: The vendor sends an invoice, which is matched against the PO and receipt
7. Payment: Finance authorizes and processes payment

A weak requisition step breaks downstream accuracy. If the original request has vague item descriptions or missing cost estimates, the PO carries those same gaps forward. Invoices won't match, and your accounts payable (AP) team spends time reconciling discrepancies the process should have caught at step two.

Common challenges with purchase requisitions

Even if you already have a purchase requisition process in place, you'll likely run into the same four problems.

Manual workflows slow everything down

When your purchase requisitions live in spreadsheets, email, or paper forms, approvals take days instead of hours. Every handoff is a chance for a request to sit unread in someone's inbox. With manual procurement workflows, you'll spend an average of 46 hours per month on work that software handles in minutes.

Inconsistent approval routing

Without clear routing rules, requisitions end up with the wrong approver, skip approval entirely, or get stuck because no one knows who's responsible. A $500 software subscription goes to the CFO while a team lead approves a $50K equipment purchase. The result: wasted time for senior leaders and insufficient oversight on large purchases.

Poor visibility into spending

You can't see what's been requested, what's pending, or what's already approved until invoices arrive. You planned for $200K in Q3 vendor spend, but $280K in requisitions were already approved across departments without anyone seeing the aggregate. Real-time dashboards that show every requisition in flight solve this, but only if your process is centralized.

Disconnected systems

When the requisition process doesn't connect to your enterprise resource planning (ERP) system, accounting software, or payment tools, data gets re-entered manually at every stage. The purchase requisition tool doesn't talk to the ERP. Approved requisitions don't auto-create POs.

The payment team re-enters invoice data a third time. Each re-entry introduces errors, and the lack of a connected record makes reconciliation harder at close.

How to improve your purchase requisition process

Most purchase requisition problems trace back to four fixable gaps: inconsistent forms, manual routing, disconnected systems, and no cycle-time tracking.

Standardize your forms and approval rules

Define a single purchase requisition template with required fields and set dollar-amount thresholds for approval tiers. The manager auto-approves requests under $1K. Requests between $1K and $10K require department head sign-off. Anything over $10K goes to VP and finance.

Clear tiers eliminate one-off requests that bypass the process and reduce the time approvers spend on low-value purchases.

Automate routing and notifications

Use procurement software to automatically route requisitions to the right approver based on amount, department, or category. Set up notifications so approvers know when a request is waiting and requesters know when it's been approved.

Connect requisitions to your accounting stack

Integrate your purchase requisition process with your ERP system, general ledger, and payment tools so approved requisitions automatically create POs and flow through to payment without manual re-entry. A connected system means one data entry point, fewer errors, and a complete audit trail from request to payment.

Track cycle time and approval bottlenecks

Measure how long requisitions take from submission to approval. Identify which approvers create delays and which spending categories have the highest return rates. Track three metrics to find your bottlenecks:

• Average time to approval: How long requisitions sit before someone acts
• Approval-to-PO conversion time: How quickly approved requests become purchase orders
• Requisitions returned for revision: How often incomplete forms slow down the cycle

Do you need a purchase requisition process?

You need a formal purchase requisition process if three or more of these apply to your business:

• You have more than 10 recurring vendors across the company
• More than one person can commit to purchases on behalf of the business
• You've had surprise invoices show up that no one approved
• Your team spends more than $50K/month on non-payroll expenses
• You're preparing for an audit and can't trace who authorized what
• Departments are buying the same things from different vendors at different prices
• Approval requests come in via Slack, email, text, and hallway conversations with no central record
• You've grown past 50 employees and informal controls are breaking down

If you checked three or more, it's time to formalize.

Automate purchase requisitions end to end with Ramp

Ramp Procurement turns the purchase requisition process into a single automated workflow. Employees submit requests in plain language. Ramp pre-fills forms, flags duplicates or out-of-policy asks, and routes each request to the right approver based on amount, department, or category.

Once approved, Ramp generates the purchase order, matches it against delivery and invoice with 3-way matching, and connects directly to your accounting stack for reconciliation. No manual handoffs, no re-keying data across systems.

Ramp also deploys AI agents across the procurement lifecycle:

• Compliance reviews: Agents run vendor due diligence, security checks, and contract risk analysis before a request reaches an approver
• Renewal tracking: Ramp surfaces pricing benchmarks, flags agreements worth renegotiating, and recommends whether to extend, renegotiate, or cancel
• Price intelligence: Ramp's Price Intelligence compares your contract rates against what other businesses pay for the same vendors

Customers save an average of 16% annually on vendor spend, and Ramp eliminates 46 hours per month of manual purchasing work.

Try an interactive demo to see how Ramp handles purchase requisitions from request to payment.