What is a purchase requisition? How to control spend before it happens

Most organizations have a gap between the moment someone needs something and the moment someone approves the spend. A purchase requisition can help close that gap.

Yet many growing organizations still rely on informal approvals: a Slack message, a verbal okay from a manager, or an employee who just orders what they need and submits an expense report after the fact.

This guide covers what a purchase requisition is, how the process works, how it differs from a purchase order, and how to make the workflow faster without sacrificing control.

What is a purchase requisition?

A purchase requisition (PR) is an internal document submitted by an employee or department requesting approval to make a purchase. It comes before a purchase order is issued.

A purchase requisition is the internal approval step that comes before a purchase order (PO). It's how your organization decides whether a purchase should happen at all. The purchase order comes later, after the purchase requisition is approved, and is the document that actually goes to the vendor.

The core function of a purchase requisition is documentation. It creates a formal record of what was requested, who requested it, why it's needed, and at what estimated cost, all before anyone spends a dollar.

Purchase requisition vs. purchase order

The difference comes down to who the document is for and what it commits. No PO can be issued until the purchase requisition is approved. Think of the purchase requisition as the internal gate and the PO as the door it opens.

How does the purchase requisition process work?

The purchase requisition process typically runs through four to six defined steps, from the initial request all the way to an approved purchase order. The entire process is internal, and no vendor contact happens until a PO is issued.

Step 1: Submit the purchase requisition form

An employee fills out a purchase requisition form with the details: item description, quantity, estimated cost, business justification, required-by date, and cost center. Depending on the organization, this happens through a procurement system, an ERP, or a standardized paper or digital form.

Step 2: Validation and budget check

The system or an approver checks the request against the budget, approved vendor lists, and any existing contracts. Items that exceed spending thresholds or fall outside normal purchase categories get flagged for additional review before moving forward.

Step 3: Approval routing

The purchase requisition routes to the right approvers based on spend amount, department, purchase category, or vendor type. You can streamline the approval process with Amazon Business, which allows you to embed approval workflows directly into the buying experience. This helps reduce manual handoffs that create delays and errors.

Automation helps get the right eyes on the right requests without creating unnecessary bottlenecks, making it a critical technology for supporting execution.

Step 4: Approval or rejection

Approvers review the business justification, verify the budget is available, and either approve or reject. If the request is rejected, the requestor gets notified with a reason so they can revise and resubmit.

Step 5: Convert to purchase order

When a purchase requisition is approved, it converts to a purchase order sent to the vendor. The purchase requisition ensures that the commitment to spend is authorized before it's made, not discovered after the fact on an expense report.

How this works in Amazon Business

Amazon Business handles spend approval in one of two ways, depending on your setup. Natively, it uses order-level approvals: when a buyer places an order, that order is held until the designated approver signs off, so the control happens at the point of purchase rather than through a separate requisition document.

For organizations that run purchasing through an e-procurement or ERP system, the full requisition-to-PO flow described above happens in that system, and the approved order connects to Amazon Business for fulfillment.

The takeaway: Amazon Business doesn't require a standalone requisition form to authorize spend before it happens. The order-level approval gives you that same checkpoint, built into the buying experience.

What fields belong on a purchase requisition form?

A well-designed purchase requisition form captures everything an approver needs to make a confident decision. The core fields are:

• Item name and description: What is being requested and for what purpose

• Quantity: How many units are needed

• Unit price estimate: Best available estimate for cost per unit

• Total estimated cost: Quantity multiplied by unit price

• Preferred vendor: If the requestor has a vendor in mind

• Business justification: Why this purchase is necessary

• Department and cost center: Where the cost gets allocated

• Requestor name and contact: Who submitted the request

• Required delivery date: When the item is needed

• Budget code: Which budget line this purchase draws from

Complete, structured purchase requisition forms are the foundation of the data your organization can use later to analyze patterns, identify savings, and plan future spend.

Why use a purchase requisition process?

Formalizing how purchase requests move through your organization pays off across four areas.

Control

A purchase requisition process helps stop unauthorized spend before it happens by requiring every purchase to start as a formal request, before any money is committed. That request is what an approval workflow then evaluates and routes for sign-off.

The two work together: the requisition creates a required front door and a clear record of what's being bought and why, and the approval step checks it against budget, approved vendors, and compliance rules. Without a requisition process, there's no consistent point at which that check happens, so employees may buy on their own judgment and seek approval after the fact, if at all.

Visibility

Every approved spend gets documented. When your finance team needs to audit spending or build a budget forecast, they're working from clean records rather than piecing together receipts and emails.

Budget alignment

The purchase requisition process catches overspend before a commitment is made to a vendor. An approver can see in real time whether the department has budget available, rather than discovering a problem after the invoice arrives.

Vendor compliance

Purchase requisitions can help ensure purchases go through approved vendors. That matters for organizations that have negotiated contracts, need to meet supplier diversity goals, or operate under regulated purchasing requirements.

Formalizing the purchase requisition process is a first step toward making procurement a measurable business function rather than an administrative cost center.

How to modernize your purchase requisition process

Some organizations may manage purchase requisitions through email chains, spreadsheets, or paper forms. The bottlenecks are predictable: requests sit in inboxes, approvals may require multiple follow-up messages, and there's no visibility into where a request stands at any given moment.

Modernizing the purchase requisition workflow comes down to three things.

1. Structured digital forms

Replace paper or unstructured email requests with a standardized form that collects the same fields every time. This eliminates the back-and-forth that happens when approvers don't have enough information to make a decision.

2. Automated approval routing

Instead of manually forwarding requests to the right person, configure your system to route based on spend amount, category, or department. Requests reach the right approver faster, and approvers see exactly what they need to take action.

3. A native approval layer, or a connected system

How you execute depends on how you buy. If you run purchasing through an e-procurement or ERP platform, the approved purchase order from that system can connect to your buying tools for fulfillment and tracking. If you don't, order-level approvals offer another route, holding an order until an approver signs off without a separate requisition form. Amazon Business supports both models, with approval controls built into the buying experience and integrations that link to your existing procurement systems.

Build the controls before the spend happens

A purchase requisition process gets your organization ahead of spend rather than behind it. When the approval step is built into the workflow, you capture better data, reduce unauthorized purchases, and give finance teams the visibility they need to manage budgets with confidence.

If you're looking to strengthen your accounts payable process or move beyond manual approval workflows, Amazon Business spend management gives you the tools to build approval workflows, enforce buying policies, and connect your approved purchasing directly to fulfillment.