Purchase Requisition Form Template Explained

A purchase requisition form template gives your business a repeatable way to request, justify, and approve spending before any money leaves the account. It is the quiet first step in procurement: an employee fills it out, a manager signs off, and only then does an order go to a supplier. Get this one document right and you turn ad-hoc, "can I just buy this?" requests into a controlled, auditable process.

This guide explains exactly what a purchase requisition form is, the fields it must contain, how each section works, and how it slots into your wider buying workflow. Whether you run a five-person agency or manage purchasing for a growing startup, you will leave with a clear picture of how to build and use one.

What a Purchase Requisition Form Actually Is

A purchase requisition is an internal request to buy something. It is not an order, and it never goes to a supplier. Its only audience is inside your own business: the person requesting the purchase and the people who approve it.

Think of it as a permission slip with a paper trail. An employee identifies a need, fills out the form, and submits it for approval. Once approved, the procurement team or finance turns it into a purchase order (PO), which is the external, binding document the supplier actually sees.

The distinction matters. A requisition asks "may we buy this?" A purchase order says "we are buying this." Keeping the two separate creates a clean checkpoint between wanting something and committing company money to it.

Why the form exists at all

Without a requisition step, spending decisions happen invisibly. People order things, receipts pile up, and finance discovers the cost after it is already incurred. The requisition form moves the decision earlier, where it can still be questioned, adjusted, or declined.

It also creates accountability. Every approved purchase traces back to a named requester, a named approver, and a documented reason. When budgets get reviewed or an auditor asks questions, the requisition is your evidence.

When Your Business Needs a Purchase Requisition Form

Not every purchase needs a formal requisition. Buying a $3 cable does not. But several situations make the form genuinely useful rather than bureaucratic.

• Spending above a threshold. Many businesses require requisitions for any purchase over a set amount, such as $250 or $500.
• Recurring or contracted spend. Software subscriptions, equipment leases, and supplier contracts benefit from a documented request.
• Shared budgets. When multiple people draw from one department budget, requisitions prevent overspend and surprise.
• Multiple approvers. If a purchase needs both a manager and finance to agree, the form routes it cleanly.
• Inventory and stock. Businesses that hold inventory use requisitions (sometimes called material requisitions) to control reordering.

Small businesses sometimes assume requisitions are only for large corporations. In practice, a lightweight requisition form is one of the cheapest ways to install spend discipline before bad habits form. The earlier you introduce it, the easier it is to scale.

The Exact Sections a Purchase Requisition Form Template Must Contain

A good purchase requisition form template is short enough to fill in two minutes and complete enough to approve without a follow-up email. These are the fields it should contain:

• Requisition number - a unique identifier for tracking.
• Date of request - when the form was submitted.
• Requester name and department - who is asking and from which team.
• Vendor or supplier (preferred) - the proposed source, if known.
• Item description - clear detail of each good or service.
• Quantity - how many units of each item.
• Unit price (estimated) - the expected cost per unit.
• Total estimated cost - quantity multiplied by unit price, summed.
• Required-by date - when the items are needed.
• Delivery location - where goods should be sent.
• Budget or account code - which budget line the spend hits.
• Business justification - why the purchase is necessary.
• Approver name and signature - who must sign off.
• Approval date and status - approved, declined, or pending.

That is the full anatomy. The next section explains how each part actually works in practice.

A Section-by-Section Breakdown

Knowing the fields is one thing. Knowing what to write in each is what separates a form that gets approved quickly from one that bounces back with questions.

Requisition number

Give every requisition a unique number, ideally sequential (PR-0001, PR-0002) or coded by department (MKT-2026-014). This is how finance references the request later and how it links to the eventual purchase order. Never reuse numbers - uniqueness is the whole point.

Requester and department

State who is asking and which team they belong to. This tells the approver whose budget is affected and who to contact with questions. In larger teams, add a cost center code so finance can attribute the spend without guessing.

Item description and quantity

Be specific. "Laptop" is not enough; "Dell Latitude 5550, 16GB RAM, 512GB SSD" is. Vague descriptions force the approver to chase details, slowing everything down. List each line item separately with its own quantity so nothing is bundled ambiguously.

Unit price and total estimated cost

These are estimates, not commitments - the requisition precedes the actual order. Still, get them close. A realistic total lets the approver judge the request against the budget. If you genuinely do not know the price, write "to be quoted" rather than inventing a figure.

Required-by date and delivery location

The required-by date drives urgency and tells procurement how fast they must act. The delivery location matters when a business has multiple sites or remote staff. Leaving this blank is a common cause of misdirected shipments.

Budget or account code

This connects the purchase to your books. The account code tells finance which ledger line absorbs the cost, which is essential for accurate reporting later. If your business uses a chart of accounts, this field is where it shows up on a requisition.

Business justification

This is the field people skip and approvers wish they had. One or two sentences explaining why the purchase is needed - "current monitors are failing and slowing the design team" - gives the approver context to say yes quickly. A blank justification invites a "why?" reply and a delay.

Approval and signature

The form ends with who must approve it and space for their decision. For higher-value requests, you may need a two-tier approval: a line manager first, then finance. Capture the approval date and final status so the requisition becomes a permanent record, not a loose conversation.

Purchase Requisition vs Purchase Order vs Invoice

These three documents are constantly confused, yet each plays a distinct role at a different stage of the buying journey. The requisition asks, the purchase order commits, and the invoice bills.

The clean sequence is: requisition approved, purchase order issued, goods delivered, invoice received, invoice matched against the PO, payment made. This "three-way match" is a cornerstone of sound procurement and a major defense against paying for things you never ordered.

If you want to go deeper on the documents that follow the requisition, our guides on purchase order best practices and when to use a purchase order pick up exactly where this article ends.

A Realistic Purchase Requisition Example

Meet Priya, an operations manager at a 12-person digital marketing agency. The content team's two laptops are three years old and crashing during video edits, costing billable hours. Priya needs new machines but cannot simply order them - the agency requires a requisition for anything over $500.

She opens the template and fills it in:

• Requisition number: PR-2026-031
• Date: 18 June 2026
• Requester: Priya Sharma, Operations
• Preferred vendor: TechSupply Ltd
• Item: MacBook Pro 14", M-series, 18GB RAM - quantity 2
• Estimated unit price: $1,899
• Total estimated cost: $3,798
• Required by: 5 July 2026
• Delivery location: Head office, London
• Account code: 6200 - Equipment
• Justification: "Existing content-team laptops are failing during video editing, delaying client deliverables. Replacement restores billable capacity."

Because the total exceeds $2,000, the workflow routes the form to the agency director after Priya's department head approves it. The director reads the justification, sees a clear link to billable work, and signs off the same afternoon. Procurement converts PR-2026-031 into a purchase order, sends it to TechSupply, and the laptops arrive before the deadline.

Notice what made this fast: a specific item description, a credible cost, and a justification that connected the spend to revenue. A vague form - "2 laptops, around $4k, we need them" - would have triggered a string of clarifying emails and missed the deadline.

Pros and Cons of Using a Purchase Requisition Form

The form is not free of friction, so it is worth being honest about the trade-offs before you roll one out.

Pros

• Spend control before commitment. Costs are reviewed while they can still be stopped, not after.
• Clear accountability. Every purchase ties to a named requester and approver.
• Budget protection. Account codes and totals keep departments inside their limits.
• Audit readiness. Approved requisitions form a documented trail for finance and auditors.
• Fewer rogue purchases. Employees cannot quietly commit company money.

Cons

• Added friction. Every controlled purchase needs a form and a sign-off, which takes time.
• Risk of bottlenecks. If approvers are slow, urgent buys stall.
• Over-bureaucracy. Applied to tiny purchases, it frustrates staff and gets bypassed.
• Maintenance. Someone must own the template, numbering, and process.

The cons are real but largely solvable with sensible thresholds and a fast approval path. The control and visibility you gain almost always outweigh a few minutes of form-filling on meaningful spend.

Common Mistakes to Avoid

Even a simple form goes wrong in predictable ways. Watch for these.

Skipping the justification

A requisition without a reason is just a shopping list. Approvers cannot judge necessity, so they either rubber-stamp everything (defeating the point) or chase every request (creating delays). Always require a justification, even one line.

Vague item descriptions

"Software" or "supplies" tells the approver nothing about cost or appropriateness. Specify the exact product, edition, or service so the request can be evaluated and the eventual purchase order is accurate.

Inventing prices

Some requesters guess wildly to push a form through, then the real cost lands far higher. If the price is unknown, mark it "to be quoted" and let procurement obtain real numbers before the PO is issued.

No unique numbering

Reusing or omitting requisition numbers makes tracking impossible. You lose the link between the request, the purchase order, and the invoice - the very chain that prevents duplicate payments and fraud.

Treating the requisition as an order

Sending a requisition straight to a supplier collapses the control step. Suppliers should only ever receive a purchase order, issued after internal approval. Mixing the two undermines the whole system.

One approver for everything

Routing every request, large or small, to a single overloaded approver creates a bottleneck. Build tiered approval so small spends clear fast and only large ones reach senior sign-off.

Best Practices for Purchase Requisition Forms

Follow these to keep the process tight without making it painful.

1. Set clear approval thresholds. Define amounts that require no form, single approval, and dual approval. Publish them so no one guesses.
2. Number every requisition uniquely. Use a consistent format and never reuse a number, so each request is traceable end to end.
3. Make justification mandatory. A required reason field forces requesters to think and gives approvers what they need to decide quickly.
4. Link to budget codes. Tie each requisition to an account or cost center so spend reports stay accurate from day one.
5. Keep the form short. If it takes more than a couple of minutes, people avoid it. Capture only what an approver genuinely needs.
6. Go digital where possible. A digital form routes itself, stores automatically, and is searchable - far better than a paper tray or a shared spreadsheet.
7. Define a fast approval SLA. Commit to approving or declining within, say, one business day so requisitions never become a bottleneck.
8. Archive every approved form. Store the full record so the audit trail survives staff turnover and finance can reconcile later.

How the Form Fits Your Procurement Workflow

A purchase requisition form is the opening move in a longer sequence, and its value comes from how cleanly it hands off to the next stage. Here is the typical flow.

First, an employee identifies a need and submits the requisition. Second, the relevant manager reviews it against budget and necessity, then approves, declines, or asks for changes. Third, once approved, procurement or finance converts it into a purchase order and sends that to the supplier. Fourth, the goods or services arrive. Fifth, the supplier issues an invoice, which finance matches against the original purchase order and delivery before paying.

That sequence - requisition, approval, purchase order, receipt, invoice, payment - is the backbone of organized buying. The requisition is where the chain starts, and a weak or missing first link compromises everything downstream. If you want to see how the whole journey connects, the complete purchase order handbook maps it out, and our guide to invoice approval workflows covers the payment end.

Connecting requisitions to the rest of your documents

The requisition does not live in isolation. It feeds the purchase order, which is later matched against the supplier's invoice. Many growing businesses manage all of these documents - quotes, purchase orders, invoices, credit notes, and receipts - in one place so the data flows between them rather than being re-keyed at each step.

This is where modern tools earn their keep. Instead of a static template re-typed every time, an AI-powered platform can generate the downstream documents from a plain-language instruction once a requisition is approved, keeping numbers, vendors, and totals consistent across the chain. That consistency is exactly what makes a three-way match painless and an audit boring - which is the goal.

Scaling the process as you grow

A two-person business can run requisitions on a shared form and an email approval. By the time you have several departments and a real budget, you want defined thresholds, tiered approvals, and digital storage. The form stays conceptually the same; the routing and controls around it mature. Designing the template well early means you are not rebuilding the process when the volume arrives.

The aim throughout is balance. Enough control that no money leaves without a documented, approved reason - and little enough friction that the form genuinely gets used rather than quietly abandoned.

Summary

A purchase requisition form template turns informal spending requests into a controlled, traceable process. It is an internal document - never sent to a supplier - that captures what is needed, how much it will cost, which budget it hits, and why, then routes to an approver before any purchase order is issued.

The essential fields are a unique number, requester and department, item descriptions with quantities and estimated prices, a required-by date, a budget code, a business justification, and approval sign-off. Keep the form short, set sensible thresholds, make justification mandatory, and link every requisition to a budget code. Avoid vague descriptions, invented prices, and treating the requisition as an order.

Done well, the form is the clean first link in the requisition-to-payment chain that protects your cash, satisfies auditors, and keeps your buying organized as you scale.

Frequently asked questions

What is a purchase requisition form?

A purchase requisition form is an internal document an employee uses to request approval to buy goods or services before any order is placed. It lists the items needed, quantities, estimated costs, the relevant budget, and a justification, then routes to a manager for sign-off. It is never sent to a supplier - once approved, it becomes the basis for a purchase order.

What is the difference between a purchase requisition and a purchase order?

A purchase requisition is an internal request asking permission to buy; it stays inside your business and is not legally binding. A purchase order is the external, binding document sent to a supplier once the requisition is approved. Put simply, the requisition asks "may we buy this?" and the purchase order says "we are buying this."

What information should a purchase requisition form include?

It should include a unique requisition number, the request date, requester name and department, the preferred vendor, item descriptions, quantities, estimated unit and total prices, a required-by date, delivery location, a budget or account code, a business justification, and space for approver sign-off. These fields let an approver evaluate the request without follow-up questions.

Who approves a purchase requisition?

Approval depends on your structure and the spend amount. Small purchases may need only a line manager, while larger ones often require both a department head and finance. Many businesses set monetary thresholds that determine how many approvers a requisition must pass through before a purchase order can be issued.

Do small businesses really need purchase requisition forms?

Yes, even small businesses benefit. A lightweight requisition form installs spend discipline early, prevents rogue purchases, and creates an audit trail before bad habits form. The key is keeping it proportionate - apply it only to spending above a sensible threshold so it controls meaningful costs without slowing down trivial ones.

How do you fill out a purchase requisition form?

Enter a unique requisition number and date, your name and department, then describe each item precisely with quantities and estimated prices. Add the required-by date, delivery location, and budget code, then write a short justification linking the purchase to a business need. Submit it to the right approver and record their decision and date.

When does a requisition become a purchase order?

A requisition becomes a purchase order once it is approved internally. Procurement or finance reviews the approved requisition, confirms the vendor and pricing, and issues a formal purchase order to the supplier. The PO carries forward the approved details and is the binding document the supplier acts on.

What is a justification field and why does it matter?

The justification field is where the requester explains why the purchase is needed, ideally in one or two sentences tied to business impact. It matters because it gives the approver context to decide quickly. A blank justification almost always triggers a clarifying email and a delay, while a clear one - like "restores billable capacity" - speeds approval.

Can a purchase requisition be declined?

Absolutely. The entire point of the requisition step is to review spending while it can still be stopped. An approver may decline a request that is outside budget, poorly justified, duplicated elsewhere, or simply not a priority. The form should capture a declined status so the decision is documented alongside approved ones.

How do purchase requisitions help with audits?

Each approved requisition ties a purchase to a named requester, approver, budget code, and reason, forming a documented trail. When matched against the resulting purchase order and supplier invoice, this creates a three-way match that auditors look for. It demonstrates that spending was authorized, justified, and properly recorded from the start.

Conclusion

A well-designed purchase requisition form template is one of the most cost-effective controls a business can put in place. It moves spending decisions to the point where they can still be questioned, ties every purchase to a named requester and a documented reason, and creates the clean first link in the requisition-to-payment chain. Whether you are a freelancer formalizing your buying or a startup adding structure as you scale, the same principles apply: keep the form short, make justification mandatory, number every request uniquely, and route it through sensible approval thresholds.

Get the requisition right and everything downstream - purchase orders, invoices, and the all-important three-way match - becomes simpler, faster, and far easier to audit. The form is small, but the discipline it installs pays off across your entire procurement process.

Related guides

• The Complete Purchase Order Handbook: Everything You Need to Know
• When Should You Use a Purchase Order? A Practical Guide
• Purchase Order Best Practices: How to Issue POs That Prevent Disputes and Errors
• Invoice Approval Workflows Explained: How to Build One That Works
• Digital Approval Workflows Explained: How to Build One That Works
• Accounts Payable Explained: How It Works and How to Manage It

Sources and further reading

• Procurement (Wikipedia)
• Purchase order (Wikipedia)
• What Is a Purchase Requisition? (Investopedia)
• U.S. Small Business Administration
• Internal control (Wikipedia)