Project margin on materials rarely disappears in one event. It leaks through many small, untracked requests over the life of a project, and the loss usually appears only at project close. In D365 F&O, the fix is to make the material request the control point, before stock leaves the warehouse.
How project margin on materials leaks, step by step
Most project businesses that lose margin on materials don’t lose it all at once. They lose it in small amounts, across dozens of transactions, over months. By the time anyone notices, the decisions that could have changed the outcome were made long ago.
The cause is usually the same: material requests that happened outside the system. Not dishonestly, and often not even carelessly. Just informally, through whatever channel was fastest on the day.
Step 1: The request happens, the record doesn’t
A site engineer needs materials. He sends a message, makes a call or walks to the stores. The storekeeper issues the stock. In D365 F&O, however, nothing has happened: no request, no approval and no cost on the project.
Step 2: The cost is lost, parked or misplaced
One of three things then happens. The cost isn’t posted at all until the next stocktake finds the gap. It’s posted to a general materials account, where the project manager can’t see it. Or it’s posted to the wrong project, so one project looks better than it is and another looks worse.
Step 3: The budget looks fine when it isn’t
Project managers track the costs they can see. If issued materials aren’t on their project, the budget looks healthy. So they approve extra scope, don’t raise concerns and don’t push back on a change order. The reported position is better than the real one.
Step 4: The truth arrives at project close
When the project closes and every cost is finally reconciled, the real margin becomes visible. By then, the work is finished, billing is complete and the change order window has closed.
Why the gap stays invisible
During a project, everyone watches schedule, scope and subcontractors. Nobody watches the gap between materials issued on site and costs recorded in D365, because there’s usually no tool that shows it.
Here’s an example. Suppose 10% of your material issues end up unrecorded or on the wrong project, and your annual materials spend is AED 15 million. That’s up to AED 1.5 million a year in costs that aren’t where your project reports say they are.
This matters even before you invoice. With progress or milestone billing, the billing team relies on the project figures. If those figures overstate margin, decisions about the project are made on a picture that’s better than reality.
Over-ordering: the hidden tax
Without a shared view of requests, over-ordering looks like prudent planning. It shows up in three patterns.
Duplicate requests
Two sites need the same item and both ask for it informally. The warehouse fills both, so one site ends up with surplus that sits, gets damaged or ends in a write-off. If both requests were in one system, someone could cover both from one stock.
Safety padding
When deliveries are unpredictable, engineers ask for a little extra. For example, a 10% buffer on 200 requests a year adds up to 20 extra requests’ worth of materials. A request with a visible required date gives the warehouse time to plan, which makes padding less necessary.
Surplus nobody can see
Surplus at one site isn’t returned or transferred, because nobody knows it exists. Another site then orders fresh stock. D365 supports transfers between sites, but only if the stock and the requests are visible.
The costs appear as cash tied up in stock, storage and handling on crowded sites, write-offs at project close and higher prices from unplanned buying.
Budget control that comes too late
Most D365 F&O setups apply budget control to external spend: purchase orders, purchase requisitions and vendor invoices. Stock issued from your own warehouse often falls outside it. The issue happens, the cost posts, and nobody checked whether the project had budget for it.
The result is a familiar conversation. “Why is Project X over budget on materials?” “We’re still matching movements to job sheets. Give us two weeks.”
There are two points where control can work before the cost is incurred:
- When the request is submitted. The system checks the request value against the project budget, then warns about or blocks an overrun.
- When the request is approved. The approver sees the budget position next to the request and makes an informed decision.
Both need a formal request. D365 budget control can check a request, but it can’t check a WhatsApp message.
How to keep the margin on the project
The fix is upstream: make the material request the control point. When every issue starts with a formal request:
- The cost posts to the right project the moment stock is issued
- The budget is checked before materials move, not after
- Project managers see their real cost position during the project
- Duplicate requests and surplus stock become visible across sites
- Month-end needs far less correction
We explain the full process in our guide to site material requests in D365, and the month-end side in why project costs don’t reconcile.
How SysMaterialRequest protects the margin
SysMaterialRequest makes the site request the only way materials leave your warehouse. Each request goes through a project budget check on submission, then D365 workflow approval, then a one-click issue, which creates the journal with the project already filled in. In addition, one list shows every open request across sites, so duplicates stand out.
Frequently asked questions
Why is material cost the hardest part of project margin to control?
Because it’s spread across many small issues, often handled informally. Each one is minor, so none of them triggers an alarm. The total only becomes clear when the project closes.
How does over-ordering affect project margin?
Surplus materials tie up cash, take up space on site and often end as write-offs at project close. Those write-offs reduce margin but are rarely traced back to their cause.
Can D365 stop a project from overspending on materials?
Yes, if there is a request step. D365 budget control can check a material request against the project budget before approval and warn or block an overrun. Without a request, the check comes too late.
Where should we start?
Start with the request step, the budget check and the warehouse queue. Those three changes close most of the gap between what is issued and what is recorded.
Keep the margin where it belongs
Bring one of your projects and a typical material list. In 30 minutes, we’ll show you a request going from site to project cost in Dynamics 365. Book a SysMaterialRequest demo.