Purchase Requisition Fields and Checklist Guide

Purchase Requisition Fields and Checklist Guide

Use this guide to plan purchase requisition fields, supporting evidence, budget checks, and approval routing before buying starts.

A purchase requisition is more than a request title and an amount. It should give procurement and finance enough detail to approve, source, reject, or return the request without chasing the requester for basic information. This guide helps teams define a practical requisition checklist before opening a template.

General Purchase Requisition FormStart from: General Purchase Requisition Form
01

Separate requisition detail from approval status

A useful requisition record keeps the requested purchase details separate from the approval decision. That makes it easier to return incomplete requests without losing the original business need.

  • Requester, department, project, category, and business justification.
  • Line items, quantity, estimated unit cost, total amount, and required delivery date.
  • Preferred supplier, supplier status, quote file, and sourcing notes.
  • Approval status, approver, returned reason, and decision date.
02

Define what evidence is required by spend type

Evidence requirements should not be the same for every requisition. Higher-risk purchases may require quotes, contract checks, supplier review, or finance notes before approval.

  • Quote or pricing evidence for competitive buying decisions.
  • Budget or cost center evidence for finance-controlled spend.
  • Policy exception notes when the request falls outside standard rules.
  • Supplier evaluation or comparison records when vendor choice is not obvious.
03

Use thresholds to keep approvals practical

Approval workflows become noisy when every requisition follows the same path. Thresholds help routine requests move quickly while high-value, risky, or exceptional requests receive the right review.

  • Amount threshold, spend category, department, project, and urgency.
  • Manager approval for business fit and finance approval for budget risk.
  • Procurement review for sourcing, supplier, or contract questions.
  • Escalation status for overdue or high-impact requisitions.
04

Plan the handoff after approval

A requisition does not end at approval. The record should show whether a buyer must request quotes, compare vendors, create a PO, or track an order after the decision.

  • Buyer owner and target PO date.
  • Supplier comparison required or not required.
  • PO request or PO approval status.
  • Requester update and procurement change tracking if the scope changes.

A practical purchase requisition checklist

Use this checklist to decide what must be complete before a requisition moves to review.

Checklist itemRequired detailCommon blockerOwner
Business needReason, requester, department, project, needed-by date.Approver cannot tell why the purchase is needed.Requester
Line itemsItem, service, quantity, estimated cost, files, specifications.Buyer cannot source or validate scope.Requester or buyer
Budget contextCost center, budget code, funding status, exception reason.Finance cannot confirm spend fit.Requester or finance
Supplier contextPreferred supplier, quotes, comparison notes, supplier status.Vendor choice is unclear or unsupported.Procurement
Approval pathApprover, threshold, returned reason, decision, approval date.The requisition stalls without a clear owner.Manager, finance, or procurement

Questions about purchase requisition checklists

Is a purchase requisition the same as a purchase request?

They are closely related. Many teams use purchase request for lighter intake and purchase requisition for a more formal approval record with budget, line-item, and supplier evidence.

What fields should be required on a purchase requisition?

Require the fields that approvers need to decide: business reason, item or service detail, amount, budget context, needed-by date, supplier context, and supporting files.

When should supplier comparison be included?

Include supplier comparison when the vendor choice affects cost, risk, quality, delivery, or compliance, especially for new or high-value suppliers.

Can a requisition checklist reduce approval delays?

Yes. A clear checklist reduces back-and-forth because requesters know what evidence is required before the record reaches approvers.

Open the purchase requisition template

Preview the Jodoo template, then adapt requisition fields, approval thresholds, supporting evidence, and buyer handoff around your process.

Preview this template