Site Material Requests in D365: The Complete Guide for Project Businesses

Site material requests in D365: request, approve, issue and post to the project
Why site material requests in D365 F&O break down at project sites, what a good process looks like, and the three internal workflows every project business needs.
Site material requests in D365: request, approve, issue and post to the project

Table of contents

Authors

Picture of Hichem Chekebkeb

Hichem Chekebkeb

Subscribe to our newsletter

Site material requests in D365 are how a project team asks the warehouse for stock the company already owns. Most Dynamics 365 Finance & Operations setups have no dedicated process for them. This guide explains where the gap comes from, what a good process looks like and which workflows close it.

Why site material requests in D365 break down

You went live on Dynamics 365 Finance & Operations. The system is configured, the training is done and go-live was declared a success. Then you visit a project site six months later.

The site engineer has a WhatsApp group with the storekeeper. The foreman emails the warehouse a list of items he needs by Thursday. Meanwhile, D365 is where finance posts the invoices after the fact.

This is not a technology failure. It’s a process design gap, and it’s common in project businesses.

The last mile gets overlooked at go-live

Most implementation teams design around financial control: the chart of accounts, legal entities, vendors and the purchase order process. All of it gets careful attention, and rightly so.

What gets less attention is the last mile: how materials are requested, approved and issued at the project site. Site teams don’t think in purchase orders. They think about what they need to keep the work moving, and by when.

The standard tools, such as purchase requisitions, inventory journals and project item journals, are powerful. However, Microsoft built them for other jobs, so site teams look for an easier path. That path usually leads away from the ERP.

The four failure points

In project businesses on D365 F&O, site procurement usually breaks down in one of four places:

  1. The request is never formalized. Site teams pass on needs by message or phone, with no structured document and no project reference.
  2. Approval happens outside the system. Someone agrees by email or in person, so nobody can trace who approved what, or why.
  3. The cost lands in the wrong place. Without a request tied to the project and its financial dimensions, the cost of issued stock goes to a default account or the wrong project.
  4. There is no view across sites. One site’s over-order is another site’s shortage, but nobody sees all the requests together.

Each of these costs money. Project margins become unreliable, budget overruns appear only after the fact, and there is no evidence when a client disputes a claim. We cover each cost in detail in how untracked material requests erode project margin.

What good site procurement looks like

A working process doesn’t have to be complex. It has to be structured. In practice, it has seven characteristics.

1. The request starts everything

Nothing leaves the warehouse without a formal request. The request is the control point: it names the project, checks the budget and starts the approval. Everything downstream flows from it.

2. It’s quick for the site team

A process the site team won’t use is only a policy. A good request form holds only what a site request needs: site, warehouse, required date, items, quantities, priority and project. Engineers pick from a short list of items, not the whole item master. As a result, the formal route is easier than the informal one.

3. Approval happens in D365, not in email

The approver gets a D365 workflow notification, sees the items and the project, and approves, rejects or returns the request with comments. D365 logs every decision with a name and a timestamp.

4. The budget is checked before stock moves

The request is the only moment when you can prevent an overrun rather than just report it. If the project has reached its materials budget, the system warns or blocks before anything is issued. Read more about this in the Microsoft Learn overview of budget control.

5. The stores team sees what’s coming

Approved requests appear in a warehouse queue as soon as they’re approved. The storekeeper can plan picking for the day, so materials are ready when the site team arrives. If stock is short, the requester knows before it becomes a delay.

6. Issuing the stock creates the journal

When the storekeeper issues the request, D365 creates the inventory movement or project item journal with the items, quantities and financial dimensions from the request. The cost reaches the project straight away, with no manual allocation by finance.

7. Every request is traceable

Any authorized user can open a request and see who asked for what, who approved it, what was issued and which journal posted the cost. This is the foundation of audit readiness, and it also gives you clean data on material use per project.

Three internal workflows every project business needs

Most D365 F&O projects configure the external procurement cycle well: requisitions, purchase orders, receipts and vendor invoices. The internal cycle, which governs how your own stock moves between warehouses and project sites, often depends on improvisation. These are the three workflows it needs.

Workflow 1: Site-to-warehouse material request

This is the core workflow. It should let a site engineer create a structured request, route it for approval, check it against the project budget, alert the warehouse and create the journal when the stock is issued.

Without it, businesses fall back on purchase requisitions (the wrong process), journals keyed by the warehouse (no approval trail) or nothing in D365 at all.

Workflow 2: Inter-site transfers

In a multi-site operation, materials also move between project sites. Surplus stock at one site could cover another site’s need, but only if someone can see it.

D365 already supports transfer orders between sites and warehouses. What’s often missing is the visibility that makes a transfer the obvious choice. When all requests are in the system, surplus at one site becomes visible to the people planning another site’s needs.

Workflow 3: Returns and surplus stock

When a project closes or a site has more than it needs, unused materials should return to the warehouse in a controlled way. The return should credit the project, restore stock and make the materials available for the next project.

Too often this becomes a stocktake at project close, followed by manual adjustments and write-offs. A return needs a document and a journal of its own, just like the original request.

Together, these three workflows form a full lifecycle: request, approve, issue, transfer and return. D365 F&O already has the building blocks, including the item master, inventory journals, financial dimensions and the workflow engine. What’s usually missing is the request layer in front of them.

Why purchase requisitions don't fill the gap

Many teams assume purchase requisitions cover site requests. They don’t, because a requisition exists to buy from a vendor and lead to a purchase order. A site request issues stock you already own and should lead to an inventory journal.

We compare the two side by side in purchase requisition vs material request in D365.

How to start

Begin with a simple test. Ask your warehouse team how they receive requests from sites. If the answer involves anything other than D365, the gap is there.

Next, pick one recent project and try to trace a material issue back to its request and approval. If that takes more than a few minutes, the request layer is missing.

From there, you can design the process with configuration and development, or use a ready-made add-on. SysMaterialRequest adds the site-to-warehouse request to D365 F&O, with a budget check, workflow approval and one-click issue that creates the journal.

Frequently asked questions

It’s a request from a project team to the warehouse to issue stock the company already owns, charged to a specific project. Standard D365 F&O has purchase requisitions for buying from vendors, but no dedicated document for this internal request.

Yes, if there is a request step to check. D365 budget control validates transactions against the available budget. A material request gives it a document to check before stock moves, instead of after the cost has posted.

Not necessarily. A request process can run inside standard D365 F&O, which adapts its layout to the device. SysMaterialRequest, for example, has no separate mobile app and uses the screens and access your users already have.

Start with the request form and the warehouse queue. Once the formal route is quicker than a message, site teams switch on their own. We explain why in why site teams still use WhatsApp for material requests.

See it on your own project

Bring one of your projects and a typical material list. In 30 minutes, we’ll show you a site request going from the request to the budget check, approval, issue and project cost in Dynamics 365. Book a SysMaterialRequest demo.