A requisition is a formal, documented request for goods, services, actions or approval within an organization. It initiates procurement or internal transfers, records the need for later reporting and controls, and — when properly managed — enforces approval workflows, budgeting and inventory updates. Requisitions can be paper or digital; modern organizations increasingly use electronic, catalog-driven systems that feed directly into procurement and accounting systems.
Key takeaways
– A requisition is an internal request (not a vendor contract). It documents needs, approvals and budget intent.
– A purchase requisition becomes a purchase order (PO) only after approved and converted to an external commitment with a supplier.
– Digital purchase-to-pay (P2P) systems automate requisition, purchasing and payment flows, improving control and lowering costs.
– Variants include job requisitions (hiring), requisitioned property (government seizure) and requisition reconciliation (accounting control).
How a requisition works — typical flow
1. Request initiation
• An employee chooses items or describes a service and completes a requisition form (often via a catalog or shopping cart).
2. Manager and budget approval
• The requisition routes to the appropriate manager(s) for approval and budget verification.
3. Purchasing review
• Procurement checks vendor selection, contract terms, compliance and may consolidate with other requisitions.
4. Conversion to purchase order (if external)
• Procurement issues a PO to the vendor; the PO is the legally binding purchase contract.
5. Fulfillment and receiving
• Goods or services are delivered; receiving validates quantity/quality and records receipt.
6. Invoice/payment
• Accounts payable matches the vendor invoice to PO and receiving record; payment is processed per terms.
7. Recordkeeping and reporting
• Requisition and PO data support inventory updates, spend reporting and audit trails.
Standardized requisition forms — what to include
A well-designed requisition form (paper or electronic) should collect:
– Requestor name, department, contact info
– Date of request and required delivery date
– Itemized line items: item description, SKU/catalog number, unit of measure, quantity, unit price (if known), extended amount
– Reason/justification for purchase
– Account codes or GL charge distribution (project, cost center)
– Budget/approval authority and approval signatures (or electronic approval routing)
– Delivery location and address
– Vendor preference (if any) and suggested supplier
– Attachments: quotes, specifications, recurring contract reference
– Special terms: expedited shipping, installation, training
– Tracking/reference number and status field
Purchase requisition vs. purchase order
– Purchase requisition (internal): a non-binding request to buy goods/services. Used to get approvals and start procurement.
– Purchase order (external): the binding document sent to the vendor that specifies items, prices, delivery and terms. Upon vendor acceptance, it becomes a contract.
Example walk-through (practical scenario)
Scenario: Training team needs supplies for a multi-site workshop.
1. Requestor searches the company e-catalog and adds 100 training manuals and 5 projectors to the shopping cart.
2. The requisition auto-fills GL codes and estimated costs, then routes to the training manager for approval.
3. The manager approves; the requisition routes to procurement. Procurement checks preferred vendor agreements and confirms pricing.
4. Procurement authorizes a PO, sends it to the vendor. Vendor accepts and ships.
5. Receiving logs delivery, updates inventory, and notifies accounts payable.
6. Accounts payable matches the vendor invoice to the PO and receiving note, then pays on agreed terms.
Practical steps to set up and operate a robust requisition process
1. Define policy and thresholds
• Establish dollar thresholds for approval levels and for PO creation vs. P-card or petty cash usage.
2. Standardize forms and fields
• Use the checklist above. Make GL coding mandatory to avoid post-hoc reclassification.
3. Map approval workflows
• Implement multi-tier approvals for higher-value requests; include budget-holder signoff.
4. Use a catalog and templates
• Maintain a preferred vendor catalog for frequently purchased items to speed requisitioning and ensure preferred pricing.
5. Integrate systems
• Connect requisitioning to procurement, inventory and accounting systems to automate PO creation, receiving and AP matching.
6. Require documentation for exceptions
• For sole source, emergency purchases or contract deviations, capture justification and higher-level approvals.
7. Train users
• Provide short guides, recorded demos and quick-reference checklists for requestors and approvers.
8. Monitor and measure
• Track cycle time (request to PO), requisition-to-PO conversion rate, compliance to preferred vendor lists and spend by department.
9. Periodically audit
• Reconcile requisitions, POs and invoices. Spot-check GL coding and approval compliance.
10. Continually improve
• Use feedback and KPIs to shrink approval times, reduce maverick spend and simplify the user experience.
Special considerations and common pitfalls
– Overly complex workflows: long approval chains slow procurement and frustrate users.
– Missing budget controls: requisitions should validate funds available before approval.
– Poorly maintained catalogs: outdated SKUs or prices lead to rework and incorrect orders.
– Insufficient data capture: missing GL or project codes create month-end cleanup and audit risk.
– Manual handoffs: paper or email-based processes increase errors and lost requests.
– Emergency requisitions: define expedited processes that include post-facto controls.
Automation and purchase-to-pay (P2P) systems
– P2P systems automate requisition → procurement → PO → receiving → invoice matching → payment.
– Benefits: fewer manual steps, automated approvals, better spend visibility and faster processing. Vendors claim large cost reductions (studies suggest meaningful savings; see Medius on P2P benefits).
– Practical rollout tips: start with a pilot department, migrate catalogs gradually, enforce data standards, and integrate with ERP/GL.
Requisition reconciliation in accounting — practical steps
Requisition reconciliation ensures requisitions, POs and invoices are consistent and accounted for:
1. Extract reports of open requisitions, open POs, and unmatched invoices.
2. Match requisitions to POs and POs to receiving records (three-way match: PO, receipt, invoice).
3. Investigate discrepancies:
• Quantity or price variances
• Missing receiving documents
• GL coding mismatches
4. Clear or escalate exceptions:
• Return requisition to requestor for corrections, request a credit memo from vendor, or adjust entries with proper approvals.
5. Post accruals:
• For goods received but not invoiced, record accruals to reflect liabilities until vendor invoice arrives.
6. Document reconciliation steps and retain audit trail per company policy and GAAP controls.
What is requisitioned property?
– Requisitioned property refers to private property taken by a government for public use (distinct from voluntary purchase). In the U.S., the Fifth Amendment requires just compensation for government seizure (see U.S. Department of Justice for historical context). This is a legal context separate from internal corporate requisitions.
What is a job requisition?
– A job requisition is an internal request to open and fill a position. Typical fields:
• Job title, department, location
• Justification for hire (new headcount, replacement)
• FLSA status and proposed salary or salary range
• Required qualifications and job description
• Approvals from HR and hiring manager
– Job requisitions ensure budget and headcount governance and centralize hiring approvals.
Fast fact
– A requisition itself is not a legal purchase contract — only the PO (once accepted by a vendor) or a signed contract creates binding obligations.
Practical template (recommended fields) — quick checklist
– Requestor, date, department
– Itemized needs (description, SKU, qty, est. unit price)
– GL account/project code
– Delivery location and required date
– Justification/benefit
– Vendor preference/contract reference
– Approvals required (names, dates)
– Attachments (quotes/specs)
Metrics to monitor (examples)
– Requisition cycle time (request → approval)
– Requisition-to-PO conversion rate
– Percentage of spend on contracted vendors
– Number of exceptions/PO-match failures
– Time to invoice payment (DPO trends)
The bottom line
A requisition is the foundation of disciplined procurement and internal controls. Well-designed requisition policies, standardized forms and automated P2P systems reduce errors, increase transparency and provide better financial control. Whether used for supply purchases, hiring or government action, the requisition concept creates an auditable trail to support decisions and financial reporting.
Sources and further reading
– Investopedia — Requisition:
– Medius — Purchase to Pay Process Explained: /
– U.S. Department of Justice — History of the Federal Use of Eminent Domain
Editor’s note: The following topics are reserved for upcoming updates and will be expanded with detailed examples and datasets.