Purchase requisition
Concept
An internal request to buy goods or services that states what is needed, how much and where, before any commitment is made to a vendor.
함께 다룬 주제
Purchase requisition 관련 에피소드에서는 Dynamics 365 Procurement and Sourcing, Request for quotation (RFQ), Three-way matching, 미지급금, Dynamics 365 Supply Chain Management 및 Purchase order도 다룹니다.
Description
A purchase requisition is an internal request to buy goods or services. It records what an organization needs, in what quantity and, where relevant, where the purchase should be delivered. Its defining feature is timing: a requisition comes before any commitment to a vendor. It is a request inside the organization, not an order placed with a supplier.
Because no commitment exists yet, the requisition gives the organization room to act before money is spent. The episode "Dynamics 365 Procurement and Sourcing - Simply Explained" describes this as an opportunity to review the requirement, check budgets, apply purchasing policies and obtain the appropriate approvals before the purchase proceeds. In practice, the requisition separates the person who has a need from the process that decides whether and how that need is met.
The same episode explains that requisitions apply to many kinds of purchases. It lists examples such as laptops, office furniture, training, repairs, cleaning, software and legal services, and notes that Dynamics 365 can support both goods and services while maintaining controlled purchasing processes. An employee typically specifies the item or service, the quantity and the delivery location, and the request then moves through the organization's review steps.
In Microsoft's business applications, the purchase requisition is an early step in procurement. Dynamics 365 Procurement and Sourcing treats it as the internal request stage, ahead of the commitments made with vendors. Typical decisions around it include who may raise a requisition, which budgets it is checked against, which purchasing policies apply and who must approve it. Those rules are what turn a simple request into a controlled purchasing process.
The term also appears in discussions of automation. The episode "Orchestration-First Architecture for Business Logic" lists the automation of purchase requisition or expense report approvals as an example of an approval workflow, stating that this reduces approval times and ensures accountability. Here the requisition is the item moving through a workflow, with approvals handled by automated steps rather than manual hand-offs.
Autonomous agents are a further context. In "Autonomous AI Agents: Use Cases, Risks, and Governance", a procurement scenario has an employee request new equipment, after which the agent reads the request and creates a purchase requisition. This shows the requisition as the structured record that turns an informal request into a trackable procurement item, which is also why governance matters when software creates such records on behalf of people.
The supply chain perspective adds another use. In "Supply Chain Visibility with Fabric and Dynamics 365 SCM", closed-loop actions include automatically creating a purchase requisition, advancing an alternate supplier or splitting a shipment, with each action logged and auditable. In that scenario, a requisition can be triggered by monitoring conditions such as predictive exceptions, and the audit trail keeps the resulting actions traceable.
Across these episodes, the purchase requisition acts as a control point. It captures need, quantity and delivery details early, keeps the organization free of vendor commitments while checks happen, and provides a record that approvals, workflows and automation can attach to. Whether a person or an automated process creates it, the requisition marks the step where a need is formally stated and reviewed before any purchase order or vendor agreement follows.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
| Type | Concept |
|---|
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.
Maintained by Mirko Peters (Microsoft MVP) · Last updated: