A purchase requisition is an internal request to buy goods or services before a formal purchase order is created. In SAP, it starts the procurement cycle, captures demand, and routes the request for review or approval. It is an upstream control point for spend governance and sourcing discipline.
What a purchase requisition does in procurement
A purchase requisition is not the purchase itself. It is the internal intake step that turns a need into a reviewable demand signal, so procurement can check purpose, budget, category fit, and whether the request should proceed at all. In enterprise systems, that upstream control point is often where spend discipline begins.
Because it sits before the purchase order, the requisition is where organisations can distinguish approved demand from ad hoc buying. That makes it a governance object as much as an operational form, especially when the buyer, approver, and requester are different people or teams.
How purchase requisitions support spend control
Requisitions help enforce buying rules before money is committed. They create a record of who asked for what, why it is needed, and which approval path applied, so finance and procurement can compare demand against policy, delegation limits, and sourcing strategy.
They also support consistency. Without a requisition step, organisations often lose visibility into shadow purchasing, fragmented supplier choices, and duplicated demand. A disciplined requisition flow makes it easier to aggregate needs, standardise vendors, and route common purchases through preferred contracts.
Where purchase requisitions sit in the procurement lifecycle
The requisition usually precedes supplier selection and purchase order creation. In practical terms, it is the bridge between business need and formal commitment, and it is often the point where the organisation decides whether the request should be fulfilled through catalog buying, competitive sourcing, or exception handling.
In ERP platforms such as SAP, the requisition can also trigger workflow, budget checks, and approval routing. That makes it part of the control plane for procurement, not just a data entry step, because the resulting approval outcome shapes downstream ordering and receiving activity.
Why the term matters in governance and auditability
A purchase requisition provides traceability for spend decisions. If an auditor, controller, or procurement lead needs to understand why a purchase happened, the requisition trail can show the business justification, approver, timestamps, and any policy exceptions that were accepted.
It also creates accountability. Clear requisition records reduce ambiguity around who initiated demand and who approved it, which matters when organisations review procurement leakage, budget overruns, or failure to follow sourcing policy.
Risk and Threat Considerations
Purchase requisitions are a control point, but they can fail when approval chains are weak, exceptions are informal, or demand is entered after the fact. In that case, the organisation loses pre-commitment oversight and may approve spend that should have been challenged, aggregated, or competitively sourced.
Failure mechanism: Bypassed or low-friction requisition workflows can enable maverick spending, policy circumvention, duplicate purchases, and poor budget visibility. In a system like SAP, weak routing or excessive approver discretion can turn the requisition into a rubber-stamp step instead of an effective control.
Impact: The result is often higher cost, weaker supplier governance, reduced auditability, and a larger gap between recorded policy and actual buying behaviour.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-6 — Least Privilege | Requisition approvals enforce least-authority spending decisions and delegated approval limits. |
| AU-2 — Audit Events | Requisitions create auditable records of demand, approval, and exceptions. | |
| Recommendation — Restrict requisition approval authority to the minimum delegated approvers needed for the spend category. Log requisition creation, approvals, changes, and overrides as auditable events. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | Requisition workflows rely on controlled approval access and separation of duties. |
| Recommendation — Limit who can submit, approve, or override requisitions based on role and delegation. | ||
| ISO/IEC 27001:2022 | A.5.3 — Segregation of duties | Requisitioning and approving purchase demand should be separated to reduce misuse risk. |
| A.5.15 — Access control | System access determines who can create, approve, or alter requisitions in procurement tooling. | |
| Recommendation — Separate request, approval, and purchase execution responsibilities for procurement. Apply role-based access to requisition creation, approval, and override functions. | ||
Practitioner Guidance
Why practitioners should care: The requisition is only valuable if it is treated as a decision gate, not a clerical precursor to ordering. Owners should ensure the request captures enough context to support budget review, sourcing review, and approval accountability.
Governance implication: Define who may raise requisitions, who may approve them, and what thresholds or exceptions require additional review. Where procurement operates in an ERP workflow, keep the requisition-to-order handoff tightly controlled so exceptions remain visible.
Practitioner takeaway: A strong requisition process is less about paperwork and more about stopping unreviewed demand before it becomes committed spend.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org