How to find the late purchase orders that matter in Dynamics 365

What Dynamics 365 already gives you

In Dynamics 365 Supply Chain Management, everything you need to judge a late purchase order already exists. It is spread across pages built for different jobs:

• All purchase orders (Procurement and sourcing > Purchase orders): the order list. Orders with quantities still to receive keep the purchase order status *Open order*, including partly received ones.
• The Purchase order receipt and follow-up workspace: lists of receipts that are overdue or due soon from the supplier.
• The Delivery tab of each order line: the *Requested receipt date* (when you asked for the goods) and the *Confirmed receipt date* (the date the vendor confirmed).
• On-hand list (Inventory management > Inquiries and reports): on-hand inventory by item, with the dimensions you choose, such as site and warehouse.
• Net requirements (open a released product, then Plan > Net requirements): the receipts, issues and projected available inventory that master planning calculated for the item, by period.
• Inventory transactions of the item: the issues that give you a usage history.

Each one answers part of the question. None of them ranks your late orders by the stock risk behind them. An overdue list sorted by date tells you who is late, not who to call first.

The method, step by step

1. List the open order lines past their receipt date

Start from the overdue receipts in the follow-up workspace, or filter purchase order lines on the *Open order* status, and export them. Keep the lines whose receipt date is before today. Use the confirmed receipt date when the vendor gave one, the requested receipt date otherwise, and flag the lines with no confirmation: their date is still your request, not the supplier's word. A past-due purchase order is any line in that list.

2. Get stock and usage for each item

Take on-hand inventory per item and warehouse from the On-hand list. Compute average daily usage from the item's issue transactions over a fixed window, for example the last 12 weeks, counting only the issues that mean consumption in your plant, such as picking for production or shipping to customers. Use the same window for every item.

3. Compare days of cover with the real arrival date

Days of cover = on-hand inventory / average daily usage. For each late line, take the date you now expect it to arrive. Check Net requirements for another open receipt on the same item that arrives earlier; it only reflects new orders after master planning has run for the item, so refresh it first. If cover runs out before any order arrives, the line is a shortage risk.

4. Sort by days of cover, shortest first

Among the shortage risks, the item with the fewest days of cover goes to the top. That is your chase list for today. For each line, write down stock, usage, cover, the receipt date and days late: when you call the supplier, you are discussing facts.

Illustrative example, not a customer result

Two lines from the same overdue receipts list:

• Line A, hydraulic fitting: 10 days late. The On-hand list shows 1,800 pieces and usage is about 30 a day: 60 days of cover. Another order arrives next week.
• Line B, control board: 3 days late, no confirmed receipt date from the vendor. 80 pieces on hand, usage of about 20 a day: 4 days of cover. No other open receipt.

Sorted by days late, line A comes first. Sorted by days of cover, line B does, and line B is the one that can stop production this week.

Where the manual method breaks

• It does not scale. Opening Net requirements item by item works for ten late lines, not for two hundred every Monday.
• Usage needs care. New, seasonal or lumpy items make a 12-week average misleading. Flag them rather than trusting the number.
• Dates are only as good as their maintenance. If vendor confirmations are not entered, the line still carries your requested date.
• Days of cover tells you when an item runs out, not which production order or customer order it affects. Linking the two still needs your planners and your bill of materials.

How WERISCO does it

WERISCO automates the data work behind these steps: it reads every open order line, computes days of cover for each part and flags late or undated orders by severity, with the evidence on each line. For a first supply chain audit, it starts from two exports you can pull from Dynamics 365 today: on-hand inventory by item and open purchase order lines. A direct Dynamics 365 connection, which reads on-hand inventory, purchase order lines and inventory transactions through OData, is in preview: built, not yet validated on a customer environment. It reads only; nothing is written back to Dynamics 365, and your team decides what to chase.