Purchase Requisition vs Material Request in D365 F&O: What’s the Difference?

Purchase requisition vs material request in D365 F&O compared
A purchase requisition buys from a vendor. A material request issues stock you already own. Here is how the two differ in D365 F&O, area by area.
Purchase requisition vs material request in D365 F&O compared

Table of contents

Authors

Picture of Hichem Chekebkeb

Hichem Chekebkeb

Subscribe to our newsletter

Purchase requisition vs material request: in D365 F&O, a purchase requisition asks to buy from an external vendor and leads to a purchase order. A material request asks the warehouse to issue stock you already own and should lead to an inventory journal. Treating them as the same process is a common cause of poor site adoption.

Purchase requisition vs material request: two different jobs

One assumption comes up in almost every D365 F&O project for a project business: “We have purchase requisitions, so material requests are covered.” They aren’t.

The two processes serve different purposes, suit different people and lead to different transactions. When one has to do the other’s job, operations stops using the system.

What a purchase requisition is for

A purchase requisition in D365 is an internal request to buy something from a vendor. Once approved, it becomes a purchase order.

It’s built for procurement. It works with vendor catalogs, procurement categories, spending limits and approval hierarchies based on who can commit the company to external spend. For that job, it works well.

What a material request is for

A site material request asks the warehouse to issue materials the business already owns. Nobody needs to buy anything. The site engineer needs the stock moved to the project, charged to the right project, by a certain date.

This is an internal stock movement, not a purchase. Still, it needs the same control as any external purchase: approval, cost allocation and an audit trail.

Side-by-side comparison

Purchase requisitionMaterial request
PurposeBuy from an external vendorIssue stock from your own warehouse
Typical userProcurement and admin staffSite engineers and field teams
ResultPurchase order to a vendorInventory movement or project item journal
StockNot yet in inventoryAlready in the warehouse
Approval logicSpending limits and procurement policyProject, site and priority
Speed expectedDays are acceptableOften same day

Where the two processes differ in practice

The form

The requisition form includes procurement categories, vendor suggestions and purchasing policy fields. A site engineer requesting cable ties and conduit doesn’t need any of them. A material request form needs only the site, warehouse, required date, items, quantities, priority and project.

The item list

Requisitions open the full item master and vendor catalogs. Site teams work better with a short list of items flagged for site requests, so they’re not scrolling through thousands of products.

The approval workflow

Requisition workflows follow procurement policy, such as spending limits and department hierarchy. Site requests need routing by project and priority instead. A request for materials needed tomorrow can’t wait three days in an approver’s queue.

Budget control

Both can use D365 budget control. D365 checks a requisition as a purchase commitment. A material request, instead, should go through a check against the project budget on submission, which is the moment stock issued from your own warehouse is usually not checked at all.

What happens after approval

This is the biggest difference. An approved requisition leads to a purchase order and a goods receipt. There is no standard path from an approved requisition to an internal inventory journal.

So, when teams use requisitions for site requests, the warehouse has to create the inventory journal by hand, as a separate step, with no link to the request. That manual step is where most errors start: late journals, wrong quantities and wrong project codes.

Financial dimensions and the audit trail

On a requisition, dimensions flow to the purchase order and the invoice. With a material request process, they should flow from the request straight into the journal, so nobody re-enters them. In addition, the journal should keep a reference to the request, so the chain from request to ledger entry can be traced both ways.

Visibility across sites

Requisition views serve procurement: by vendor, category and policy. Operations managers need a different view: all open requests by site, project and status. That view is what reveals duplicate requests and surplus stock.

When to use each one

Use a purchase requisition when:

  • The items must be bought from a vendor
  • The result should be a purchase order
  • The user works in procurement or administration
  • Approval follows spending limits and procurement policy

Use a material request when:

  • The items are already in your warehouse
  • The result should be an internal inventory movement
  • The user is a site engineer, foreman or project team member
  • Approval follows the project and the priority

The two are not competing. They’re complementary processes for different jobs, and project businesses need both.

Why the workarounds don't hold

Some teams use requisitions anyway, sometimes with dummy vendors or manual journals. Others skip the request and let the warehouse post journals directly. Both approaches fail in predictable ways.

With requisitions, the process is too slow for site teams, so they go back to WhatsApp and email. With direct journals, stock moves without a request, an approval or a budget check, so you get the transaction but lose the control.

The fix is a dedicated request step between the site and the warehouse. We describe the full process in our guide to site material requests in D365.

How SysMaterialRequest handles the second flow

SysMaterialRequest adds the material request to D365 F&O and leaves your purchase requisitions as they are. It provides:

  • A short request form with a curated item list
  • A budget check on submission, with warn, block or override options
  • D365 workflow approval by project and priority
  • One-click issue that creates the inventory movement or project item journal, with the dimensions filled in
  • One list of all requests across sites and statuses

Frequently asked questions

Technically yes, but it creates problems. The requisition leads to a purchase order, not an inventory journal, so the warehouse has to bridge the gap manually. Site teams also find the form too slow and go back to informal channels.

No. Requisitions remain the right tool for buying from vendors. A material request covers the internal issue of stock you already own. Most project businesses need both.

Yes. With D365 budget control, the system checks the request value against the project budget on submission, before any stock moves. You decide whether an overrun warns, blocks or needs an override.

In a good process, the storekeeper issues what’s available and the rest stays open on the same request. In SysMaterialRequest, the storekeeper issues the remaining quantity when stock arrives.

See the difference in your own system

Bring a typical site request and we’ll show you both routes in Dynamics 365 in 30 minutes. Book a SysMaterialRequest demo.