For manufacturers and distributors on Dynamics 365 Finance & Supply Chain Management, the month goes into the gaps the ERP records but does not work: purchase order lines past their date with no receipt posted, the GRNI balance aged by hand at close, supplier follow-ups, invoices that cannot three-way match, planning parameters someone typed in once. We build the agents and optimization apps that work those gaps inside F&O, with a person approving every posting, on your own Microsoft stack. One of them, the PO Receipt Chase Agent, is built and demonstrated on request today.
Three kinds of gap in a manufacturer’s F&O
Recorded, not worked
Overdue PO lines, unposted receipts, GRNI ageing, pending vendor invoices, supplier confirmations. The ERP holds every one of them and chases none.
Stored, not derived
Safety stock, reorder points, prices, slotting. Fields a person typed in, never recomputed from the demand the ERP has been recording since.
Audited, not governed
F&O logs everything a user did. Which forms an agent may open, what it may post, and who approves it are decisions nobody has made yet.
A manufacturer's Dynamics 365 is full of correct records and empty of decisions. It knows which purchase order lines are past their confirmed delivery date; it does not chase them. It knows a product receipt was never posted; it lets the vendor invoice wait in the pending queue. It holds a safety stock on every item; it does not ask whether the number was ever derived. It keeps a complete audit trail of what people did; it has no view of what an agent should be allowed to do.
Every one of those gaps is worked by hand today: a buyer's spreadsheet of late lines, a controller's GRNI ageing at close, a planner's parameter review once a year, a security administrator's reading of a new agent's role. The hand-offs between them are where the month goes.
The agentic layer Microsoft now ships, the Dynamics 365 ERP MCP server and its first-party agents, makes the gaps reachable. It does not fill them. The receipt still has to be chased, the number still has to be computed, the approval still has to be designed. That is where we work.
The freshest objects on this track, each with a status word and a date.
Finds overdue purchase order lines, reports them by buyer, takes the plant's confirmation of what arrived and posts the product receipt behind an explicit approval. Runs on test data in a demonstration environment today; a recorded run exists.
See how it works →Every first-party ERP agent Microsoft ships, the partner agents Microsoft has named, the MCP servers underneath, each with Microsoft's own status label and source, and the line where a custom build on your F&O begins.
Read the catalog →Microsoft's roadmap item 571677 adds agent-specific roles, duties and privileges by legal entity: preview in October 2026, general availability in December 2026. The governance design it formalises is the first thing we do on any estate.
Close the governance gap first →Each links to the page that argues it. Nothing is restated here.
The PO Receipt Chase Agent works the overdue lines and the GRNI backlog from the receipt side; Microsoft's Procurement Agent chases the vendor from the other. Together they close the gap between the dock and the ledger.
PO Receipt Chase Agent →Planning and inventoryF&O runs replenishment to the parameters you typed in. The Demand & Inventory Optimizer derives them from your own demand history and lead-time variability, and writes them back through the supported surface.
Demand & Inventory Optimizer →WarehouseTravel is roughly half of picking time and the ERP records the placement without choosing it. Slotting and pick-path are operations-research problems, solved beside the ERP.
Pick-Path & Slotting Optimizer →Pricing and quotingThe ERP applies the lowest price you entered. The Pricing Optimizer works out what the price should be from your own transactions, and the quoting agents read it before they act.
Pricing Optimizer →Data foundationLink to Fabric, OneLake, the semantic model and lineage over the F&O estate, so every agent and every optimizer computes on one governed layer.
The Fabric data foundation →Governance and auditAgent-only roles, approval before posting, segregation of duties and an audit trail your auditors accept. Designed before the first agent is switched on, not after.
Making Dynamics 365 agents auditable →Readiness first, then a costed activation in your own sandbox. Nothing is switched on in production until it has run on your data behind your approvals.
Your F&O version and environment tier against Microsoft's prerequisites, your customizations against what the dynamic MCP server can reach, and the roles an agent would run under.
The agent or optimizer runs on a copy of your environment, on your open orders, your items, your history, with the approval boundary in place from the first run.
Production under the roles and approvals agreed in the sandbox, with the audit trail and the status word for every component stated in writing.
Readiness, piloting, governance and audit, and what Microsoft's own agents cover versus a build on your customized F&O.
Microsoft's Account Reconciliation Agent clears reconciliation exceptions in bulk across Dynamics 365 Finance. Here's what it handles well, the exceptions it hands back, and how to close that last gap.
Read more3 min read
Microsoft's Finance Agent brings AI to collections in Dynamics 365 — prioritising accounts, drafting outreach, surfacing risk. Here's what it drives well, where the customer relationship stays human, and how to make it run on your policy.
Read more3 min readAI on top of the ERP has become four different things sold to four different buyers. Here's how to tell them apart — and which layer actually moves your margin — on Microsoft Dynamics 365 and Business Central.
Read more4 min read
Business Central now ships AI agents — a Payables Agent that reconciles POs and an Expense Agent that checks reports for policy violations. Here's what they do, where they stop, and when a mid-market team needs a custom build.
Read more3 min readMicrosoft's 'business skills' let you define your procedures as reusable, governed context for Dynamics 365 agents. Here's how to turn the way your business actually runs into skills an agent can use — and why that's the real work.
Read more3 min read
Microsoft's ERP Copilot plugin is GA — and an agent acting for a user can currently do anything that user can do. The role-based controls have no release date. Here's how to close the governance gap before you activate agents on Dynamics 365.
Read more3 min readMicrosoft's ERP agents work beautifully on standard Finance & Operations — and stall on the X++ and ISV customizations that make your estate yours. Here's the last-mile fix: exposing your logic as governed MCP Action tools.
Read more3 min read
Most teams that can't activate Microsoft's Dynamics 365 agents aren't blocked by the AI — they're blocked by data quality, role design, customizations and governance. Here's the honest readiness checklist.
Read more3 min readEvery page on this track ends with a person, because the next step is a working session, not a form.
Mudassir Marwat
Founder & CEO, Cognilium AI
Leads the Dynamics 365 practice and sits in the first working session on every F&O engagement.