What Is a Purchase Requisition? Definition, Process, and Automation
A purchase requisition is an internal document an employee uses to request approval for a purchase before an order goes to a supplier. It records what's needed, why, and at what cost, so the company approves spend before committing money.
That timing is the whole point. A requisition moves the spend decision to the one moment when oversight costs nothing, because no supplier has shipped anything and no invoice exists yet. Skip that step and finance meets most purchases for the first time as an invoice, when the only options left are pay it or fight about it.
If you're standing up spend controls, the requisition is where they anchor. Approval thresholds, budget checks, and the audit trail all attach to this document, and everything downstream, from the purchase order to the payment, inherits its data.
Key Takeaways
A purchase requisition asks for internal permission to buy; a purchase order places the order and becomes binding once the supplier accepts it.
Requisitions exist to control spend before it happens. Approval thresholds, budget validation, and the audit trail all start at the request, not the invoice.
The workflow runs from request through budget-owner, finance, and procurement approval, and its output is the purchase order the supplier eventually invoices against.
Incomplete forms and manual, email-based routing cause most approval delays, and slow approvals push employees to buy off-process.
Requisition automation routes requests by amount and category, enforces required fields at entry, and keeps the request linked to the PO, invoice, and payment that follow.
What does a purchase requisition mean?
A purchase requisition means an employee is formally asking the company for permission to spend. It's a request, not an order. The document names the item or service, the quantity, the estimated cost, the department paying for it, and the business reason, then routes to whoever owns that budget for a decision.
Companies bother with the paperwork because of unauthorized spend. The Hackett Group's 2023 Procurement Key Issues Study found that maverick, off-contract buying still makes up a material share of indirect spend at many firms, and every one of those purchases skipped the moment when someone could have said no, negotiated, or pointed to an existing contract.
The cleanest test I know for whether a requisition process is working comes from pulling the last five invoices that surprised AP and counting how many had an approved requisition behind them. In my experience the answer is usually zero. Each of those invoices was a purchase decision somebody made alone, and the requisition exists to make that impossible.
Who raises and who approves a purchase requisition?
Any employee can raise a purchase requisition, and approval belongs to the people accountable for the money, typically the requester's manager or the budget owner first, then procurement. Larger purchases climb higher. A common ladder lets managers clear small requests on their own, sends mid-range amounts to a director or department head, and reserves anything above a set limit for the CFO or a spend committee.
Procurement's review is different from the budget owner's. The budget owner confirms the spend is necessary and funded; procurement checks whether a preferred supplier or negotiated contract already covers it. Getting both sign-offs in the right order matters more than teams expect, and it shows up constantly in software reviews. As one G2 reviewer of AP software put it, "customizable workflows ensure the right people are involved in the approval process."
Is a purchase requisition legally binding?
No. A purchase requisition is an internal document, and it creates no obligation to any supplier. Nobody outside the company ever needs to see it.
The binding step comes later, when an approved requisition becomes a purchase order and a supplier accepts it. That's why the requisition stage is the cheap place to catch mistakes. Editing or rejecting a requisition costs nothing, while canceling an accepted PO can mean restocking fees, dispute emails, and a supplier relationship that needs repair.
How is a purchase requisition different from a purchase order?
A purchase requisition asks for permission to buy inside the company; a purchase order places the order with the supplier once that permission exists. The PO carries the final pricing, quantities, and delivery details, and it becomes binding when the supplier accepts. They're consecutive checkpoints in the full procure-to-pay cycle, and confusing them is how spend oversight quietly falls apart.
Attribute | Purchase requisition | Purchase order |
What it is | Internal request for approval to buy | External order sent to a supplier |
Audience | Budget owner, finance, procurement | The supplier |
Created by | The employee who needs the item | Procurement or purchasing, after approval |
Legal status | Not binding; internal only | Binding contract once the supplier accepts |
What it fixes | Need, estimated cost, business justification | Final price, quantities, delivery, and payment terms |
Timing | Before sourcing or supplier contact | After approval and supplier selection |
Reference number | PR number, used for tracking and audit | PO number, quoted on the invoice for matching |
The PO also locks in commercial details a requisition only estimates, including the negotiated payment terms your cash flow planning depends on. None of that paperwork is free, either. APQC's 2023 Open Standards Benchmarking data on procurement puts the cost of manually processing a single purchase order in the tens of dollars, which is a strong argument for requisitions clean enough that the PO doesn't bounce back for rework.
Protect cash flow with modern AP
Modernize AP to cut costs, speed approvals, and mitigate payment risk — gaining the real-time visibility to protect cash flow and scale with confidence.
Download the whitepaper
When does a requisition become a purchase order?
A requisition becomes a purchase order once the final approver signs off and procurement converts it. If a preferred supplier already exists, conversion can be nearly instant; if not, procurement runs its sourcing step first, then issues the PO. From that point the documents chain together. The supplier invoices against the PO number, and AP compares the purchase order against the invoice before anything gets paid. Teams that keep purchase orders disciplined usually trace that discipline back to requisitions that were complete on day one.
How does the purchase requisition workflow work?
The purchase requisition workflow moves a request from submission through approvals to PO conversion, usually in six steps. Here's the standard sequence.
The requester identifies the need and completes the requisition form, including the item, quantity, estimated cost, and justification.
The request enters the queue, by email and spreadsheet in manual shops, or through a procurement or AP system with a requisition module.
The budget owner reviews it against the department budget and either approves, rejects, or returns it for edits.
Finance or a second approver clears requests that cross a dollar threshold, following the approval ladder.
Procurement checks supplier options, existing contracts, and pricing, then gives the final sign-off.
The approved requisition converts to a purchase order, and the requisition, with its approval history, is retained for audit.
Where does this stall? Almost always in routing. When approvals travel by email, requests sit in inboxes, nobody can see whose turn it is, and a two-day approval turns into two weeks. Incomplete forms are the other repeat offender, because every missing cost code or justification triggers another round trip to the requester.
Slow approvals do more damage than delay. Once employees learn the official path is slow, they buy first and apologize later, and the fallout lands on AP as invoices with no PO behind them. G2 reviewers of AP platforms complain specifically about gaps in invoice OCR when PO numbers are missing, which is exactly the artifact off-process buying leaves behind. Deloitte's 2023 Global Chief Procurement Officer Survey puts spend visibility and digital procurement at the top of CPO priority lists, and this is a big part of why. Teams that manage accounts payable well usually got there by fixing what happens before the invoice, not after.
What information belongs on a requisition form?
A complete requisition form gives approvers everything they need to decide without a follow-up email. At minimum, that means the following.
Requester name, department, and date of request
Description of the item or service, with quantity and unit of measure
Estimated cost and currency, plus the budget line or GL code it charges to
Date needed, so approvers can see urgency
Suggested supplier, if one exists, and any quote or contract reference
Business justification in a sentence or two
Cost center and project codes that drive approval routing
The form doubles as the front end of your audit trail. Every approval that follows gets time-stamped against it, and when auditors ask who authorized a payment, the answer traces back here. AP feels the difference daily, since matching and coding during the accounts payable process run on the codes and references this form captures. The fraud angle is just as practical. AFP's 2024 Payments Fraud and Control Survey found 80% of organizations faced payments fraud attempts, and documentation created before money moves gives AP an independent record to verify against.
Approvals stuck in inboxes? See how Corpay routes every request, purchase order, and payment through one controlled workflow.
How does automation improve the requisition process?
Automation improves the requisition process by replacing manual routing with rules. Software reads the amount, category, and department on each request, sends it to the right approvers in the right order, and blocks submissions with missing fields, so the two biggest sources of delay never start.
A purchase requisition system worth the license handles a few specific jobs.
Routes requests by dollar threshold and category, with reminders and escalation when an approver sits on one
Validates required fields and budget availability at entry, before anyone spends review time
Points requesters to catalogs and preferred suppliers, so contract pricing gets used
Converts approved requisitions into purchase orders in one step
Keeps the full approval history attached and searchable for audit
The speed difference is well documented. Ardent Partners' 2023 procurement research shows organizations that automate requisitioning cut requisition-to-order cycle times sharply compared with manual processes. The firm's 2023 State of ePayables adds a cost dimension, finding that top-performing procurement teams process purchase orders at markedly lower cost than average performers. Adoption is moving the same direction. The 2024 Billentis/Comarch global e-invoicing report tracks e-procurement climbing steadily across North American mid-market firms.
What automation really buys, though, is continuity. An approved requisition should flow into a PO, the PO into invoice matching, and the match into payment, without anyone rekeying data between systems. That's the same logic that drives accounts payable automation generally. Most teams hit a gap at the last mile. The approval workflow gets automated, PO conversion gets automated, and then the payment itself still goes out as a hand-keyed check run nobody matched against the original request.
Turn approved requisitions into controlled payments with Corpay
That last mile is where we focus. Corpay's AP automation picks up where the approved requisition leaves off, capturing invoices against their POs, running approvals under the same rules you set upstream, and executing payment by virtual card, ACH, or check with the audit trail intact. Virtual cards extend approved-spend controls onto the payment itself and generate rebates on spend you already cleared.
The whole chain stays inside your system of record. Corpay connects to 180+ ERP and accounting systems, including NetSuite, SAP, Oracle, Microsoft Dynamics, Sage Intacct, QuickBooks, and Xero, so requisition data, PO references, and payment status sync instead of living in a side spreadsheet. And because our team handles supplier enrollment and payment follow-up, the workflow you tightened upstream doesn't unravel at execution. PwC's 2024 Global Working Capital Study puts digitizing source-to-pay among CFOs' top working-capital priorities, and requisition-to-pay is that priority made concrete.
If your requisition workflow is solid but payments still run on manual effort, that's the seam worth closing first.
Frequently Asked Questions
What is a requisition?
A requisition is a formal internal request for something an employee needs the company to provide. Purchase requisitions request goods or services from outside suppliers, materials requisitions pull stock from internal inventory, and job requisitions request approval to hire. All three route through an approval before anything is committed.
What is a requisition in procurement?
In procurement, a requisition is the document that opens the buying cycle. It records what's needed, the estimated cost, and the business justification, then collects approvals before procurement sources a supplier and issues a purchase order. Nothing is ordered until the requisition clears.
What is a PO requisition?
PO requisition is an informal name for a purchase requisition, the internal request that precedes a purchase order. The two documents stay linked. Once the requisition is approved it converts into a PO, and the PO number traces back to the original request for matching and audit.
What is a purchase requisition system?
A purchase requisition system is software that digitizes the request-and-approval workflow. It validates required fields at entry, routes each request to the right approvers automatically, enforces budget and policy rules, and converts approved requests into purchase orders. Some run as ERP modules, others as dedicated procurement or AP tools.
Can a purchase requisition be rejected or changed after submission?
Yes. Approvers can reject a requisition outright or return it for edits, and requesters can revise and resubmit. Because nothing has been communicated to a supplier yet, changes at this stage carry no cost or contractual consequence, which is exactly why the review happens here.
Do small businesses need purchase requisitions?
Requisitions pay off once more than a handful of people can commit spend. A small business doesn't need heavy workflow, but a simple rule, such as any purchase over $500 requiring a requisition and a manager's approval, prevents surprise invoices and duplicate buying without slowing anyone down.
Switch to Corpay
Discover how making the move to Corpay streamlines payments and strengthens your business.
Talk to an ExpertSmarter payments. Stronger growth. Keep business moving.
Corpay powers payments for 800,000+ businesses worldwide. Let’s build what’s next for yours.