Why is this order on hold? Answered with the evidence. Released only by the right role.
The Credit Hold Agent is an AI agent for Dynamics 365 Finance that answers the question every sales desk puts to the credit team: why is this order on hold, and who can release it? It reads the sales order, the blocking reasons Dynamics 365 recorded, the customer's credit record and their open invoices, explains the hold in plain language with the evidence, and, once the order is released, shows who released it, the reason they gave and the review date they set. The release itself stays behind a role-gated review: only a person holding the credit manager's role can clear a hold, and the agent never does it for them. It is built and demonstrated as a training build on Microsoft's demo data. It has not yet run on a customer's environment, and we say so on every page.
One held order, explained
Illustration · Microsoft demo dataInvoice overdue
47 days past due on one invoice
Credit limit used
This order takes the share used above the threshold
What would clear it
Nothing on the order. A payment on the overdue invoice, or a release by the credit manager with a reason and a review date.
Release button: visible to the credit manager role only.
The hold everyone phones about
Dynamics 365 Finance puts a sales order on credit hold for a recorded reason: an invoice overdue by more than the allowed days, an account status, a payment term, an expired credit limit, an overdue amount, the order's own value, the share of the credit limit it would use, a change to the terms or the settlement discount, or a credit manager who forced the hold by hand. The order goes to the credit management hold list and waits for a person with the right role to release it with a reason and a review date. That is the product working as designed, and since version 10.0.47 it is a permanent part of Finance rather than a feature to switch on.
The hold is not the problem. The explanation is. The sales rep sees a blocked order and phones credit. The credit manager opens the hold list, the blocking-reasons box that may only say Multiple, the customer's ageing, the open invoices and the credit limit, and reconstructs the story. Then explains it, by phone, to someone who cannot see any of those screens. When the order is finally released, the trace of who released it and why lives in a field that nobody outside credit ever opens.
Every fact needed to answer the rep is already in Dynamics 365. The answering is still done by a person, several times a day.
Why is my order on hold, and what would clear it? Asked of someone who has the screens, by someone who does not.
Hold list, blocking reasons, ageing, open invoices, credit limit, for each held order, before a single release decision is made.
Who released the order, with what reason, on what review date. Recorded in Dynamics 365, invisible to everyone who asked.
How it works, in four steps
The agent reads Dynamics 365 Finance live, through Microsoft's own surface, under the roles it is given. People ask it in plain language: “Why is this order on hold?”
- 01
Ask
A sales rep, a customer-service agent or the credit manager asks about one order, or asks for every held order for one customer. The question is in words, not in a filter on the hold list.
- 02
Read
It reads the order header, the blocking reasons Dynamics 365 recorded against it, the customer's credit record, open invoices and credit limit, and whether the hold was forced by hand. All of it through Microsoft's supported surface, under its assigned role.
- 03
Explain
It states the hold in one paragraph with the evidence: which reasons apply, since when, what on the order changes nothing, and what outside the order would clear it, such as a payment on a named invoice. The person can disagree with any line of it.
- 04
Hand over
The review button is role-gated. Only a person holding the credit manager's role sees it and can release the hold, with a release reason and a review date, as the product requires. Afterwards the agent shows who released it, when and why, to the person who asked.
The agent never releases a hold, never changes a credit limit and never edits a blocking rule. What changes is who gets the explanation, how fast, and whether the release can be traced by the people the hold affected.
What Dynamics 365 covers, and what this agent adds
Microsoft's credit management is complete on its own terms. The agent sits on top of it; it replaces none of it.
| Dynamics 365 Finance covers | The Credit Hold Agent adds |
|---|---|
| Blocking rules by customer, group or all, with exclusions | Nothing. Your rules stay yours. |
| The credit management hold list across legal entities | A plain-language answer about one order, for someone without access to the list. |
| Blocking reasons per order, shown as Multiple when there are several | The reasons unpacked, dated, with the evidence behind each, and what would clear them. |
| Release with a release reason and a review date, with or without posting | The release kept behind the credit manager's role, and the trace shown to the people who asked. |
| An approval workflow for release, and Evaluate for release when reasons clear | Nothing. Where a workflow exists the agent reads its state; it does not bypass it. |
| Forced credit hold by a credit manager | The forced hold reported as such, with the person and the reason, never released by the agent. |
Source: Microsoft Learn, “Credit holds for sales orders”, ms.date 2026-04-01, and “What's new or changed in Dynamics 365 Finance 10.0.47”, ms.date 2026-09-11. Both read 2026-10-21. [1] [2]
Where it stands today, exactly
A status against everything we show.
Answer “why is this order on hold?” with the recorded reasons and the evidence
Working, training buildBuilt and demonstrated as a training build on Microsoft's demo data. Not yet run on a customer's environment.
Role-gated review: release stays with the credit manager's role
Working, training buildSame build. The review button is visible only to the role that may release.
Show who released a hold, the release reason and the review date
Working, training buildSame build, reading the release the product recorded.
Run on your Finance environment, with your blocking rules, exclusions and workflows
Built to orderEngineering on a sandbox copy of your environment after the readiness review. No packaged app.
A Teams notice to the sales rep when a hold is placed or released
BlueprintDesigned on Microsoft-documented capabilities; not built.
What it will not do
An agent that sits next to a credit decision is judged on what it refuses.
| It will not | Because |
|---|---|
| Release a hold | Release is a role-gated human action with a reason and a review date. The agent routes the request and reports the result; it never clears the hold. |
| Change a credit limit or a blocking rule | Credit policy is set in Dynamics 365 by the people who own it. The agent reads policy; it does not write it. |
| Bypass an approval workflow | Where release is gated by a credit management workflow, the agent reports where the order is in that workflow and stops. |
| Answer about a customer it cannot read | It runs under a security role you assign. If that role cannot see the customer, the agent says so rather than guessing. |
| Guess a reason | When the recorded reasons and the evidence do not settle why an order is held, it says what it found and hands the order to credit. |
| Quote credit terms to a customer | It explains holds to your people. What is said to the customer is decided by them. |
The same approval boundary runs through the PO Receipt Chase Agent and the Aged GRNI Investigation Agent, and is argued in full on the agentic ERP hub.
Credit holds and the agent, answered plainly
- What is a credit hold in Dynamics 365 Finance?
- A credit hold is Dynamics 365 Finance's credit management stopping a sales order from moving forward because a blocking rule matched. Microsoft's documentation lists nine reasons an order can enter the hold list: days overdue, account status, terms of payment, an expired credit limit, an overdue amount, the sales order amount, the share of credit limit used, a change of payment terms and a change of settlement discount. A credit manager can also force a hold by hand. Held orders sit in the credit management hold list until a person releases or rejects them.
- Why is my sales order on credit hold?
- Because at least one blocking rule matched when the order was processed, or a credit manager forced the hold. Dynamics 365 records the reasons against the order; when there are several the list shows Multiple and the detail sits in the blocking-reasons view. The agent reads those recorded reasons, the customer's open invoices and credit limit, and explains them in plain language to the person asking, together with what would clear the hold.
- Can the agent release the hold?
- No. Release in Dynamics 365 Finance needs a release reason and a review date and, where a credit management workflow is configured, an approval. The agent keeps that behind a review button visible only to the credit manager's role. It routes the request with its explanation attached and, once a person has released the order, shows who did it, when and why.
- Who can release a credit hold?
- Whoever holds the security role your organisation has assigned for it, normally the credit manager, acting in the hold list with a release reason and a review date, or through the credit management approval workflow if one is set up. The agent does not change who that is. It makes sure the person asking can see the answer, and the person releasing can see the whole story.
- What is a forced credit hold, and how does the agent treat it?
- Microsoft's documentation describes Force credit hold as a credit manager placing an order on hold by hand for a reason the blocking rules do not cover, with a forced hold reason. Such orders cannot be released automatically and are not processed by workflow. The agent reports a forced hold as exactly that, with the person and the reason, and never proposes to release it.
- Does this change our blocking rules, exclusions or workflows?
- No. The agent reads what credit management recorded and explains it. Blocking rules, exclusion rules, ranked payment terms, the auto-release parameter and the credit management workflow stay as you set them. If any of them should change, that is a conversation with your credit team, not something an agent does.
- What does “training build on Microsoft's demo data” mean?
- It means the agent was built and is demonstrated on Microsoft's standard demonstration data for Dynamics 365 Finance, with its demo customers, invoices and credit limits, and has not yet run on a customer's environment. Everything shown works there. Running it on your Finance, with your blocking rules and your roles, is engineering we do on a sandbox copy after the readiness review, and we would not describe it as more than that.
- Is our data leaving Dynamics 365?
- Microsoft's ERP MCP server stores no customer data; the agent reads through it under its assigned role. Where the conversation itself is processed depends on the agent platform and the model your tenant has approved, and we review that with your IT before anything runs on your data. The readiness review covers it.
- Can it go rogue?
- It cannot release a hold, change a limit or touch a rule, because it has no path to do any of those: release is a human, role-gated action with a reason and a date, and the agent's role is scoped to reading. If it cannot read something it says so. If the evidence does not settle the reason it says that too and hands the order to credit.
Turning agents on in Dynamics 365, in detail
Readiness, piloting, governance and audit, and what Microsoft's own agents cover versus a build on your customized F&O.
AI account reconciliation in Dynamics 365: what the agent clears, and the part it hands back
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
AI collections in Dynamics 365: what the agent drives, and where the relationship stays human
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 your ERP: the four layers, and which one actually moves your margin
AI 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 AI agents: what the Payables and Expense agents do, and where a custom build takes over
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 readCodifying your procedures as governed business skills for Dynamics 365 agents
Microsoft'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
A Dynamics 365 agent can do anything the user can. Close that gap before you turn it on.
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 readWhy Microsoft's Dynamics 365 agents stumble on your customized F&O — and the last-mile fix
Microsoft'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
AI Agent Readiness for Dynamics 365: are you actually ready to turn agents on?
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 read