An illustrative case: a $34,000 vendor invoice in a manufacturer's Business Central tenant. The Payables Agent drafted it from an emailed PDF, an AP clerk confirmed the review, and Business Central's approval workflow routed it to the purchase approver on file. Six weeks later the external auditor asks a narrower question than who approved it. What did the reviewer check on the agent's draft, which vendor and purchase order did the agent match, and where is the evidence that anyone looked at accuracy? Microsoft's own Payables Agent documentation says "This review confirmation isn't a Business Central approval workflow, and the agent doesn't post the invoice."
The invoice itself was fine. The audit question is whether the control around AI-drafted invoices was. In a survey of 100 US CFOs at companies with $50M to $500M in revenue, commissioned by the finance-automation vendor Maximor and fielded by Wakefield Research, the audit trails finance leaders want cover "who made a decision, what data supported it, and what rules applied" (CFOtech, 28 January 2026). In the same survey, 86% said their team has hit inaccurate or hallucinated data (Journal of Accountancy, 9 February 2026), so the reviewer's job is accuracy as well as sign-off. Manufacturers look least ready for the audit itself: Grant Thornton's Manufacturing Insights 2026 AI Impact Survey summary reports 12% confident they could pass an independent AI governance audit, against 22% across industries. The summary page shows no sample size or date.
Business Central agent governance, separate from what any single tool's settings screen shows you, is the shared answer to three questions across every AI surface writing to your ERP: which system made the write, who's the named person accountable for it, and where the record lives. For purchase documents, Business Central already answers all three natively through its approval workflow. Five surfaces sit around that workflow today: Payables Agent, Copilot in Business Central, Agent Designer, Power Automate, and IntelliConnectQ's own OpsGrid. Each answers the questions differently for everything it touches outside it.
Copilot agents in Business Central, plus Power Automate and OpsGrid
Five surfaces write to, or route decisions around, a Business Central tenant in this comparison. Four are Microsoft surfaces: a built-in agent, an in-product assistant, an agent builder and an automation platform. The fifth is IntelliConnectQ's own beta product, listed apart from them. Microsoft ships more than these: the Sales Order Agent (generally available November 10, 2025) and a Business Central MCP server for outside agents (public preview from October 31, 2025, also exposed through the Power Automate connector's MCP Server Configuration parameter). The columns below leave both out; the headless ERP article covers outside agents. Update 29.0 also adds a Microsoft Copilot chat experience, which Microsoft's what's-new page lists as public preview. 365vanguard, a Business Central partner, reported on October 2, 2026 that the new chat is read-only and "can't call Business Central agents," so the Sales Order Agent and Payables Agent are still used from their own experiences inside Business Central. The columns below leave the chat out too. Microsoft's own page refers to the chat's "read-only capabilities," and the version that can write, Edit with Copilot, exists only as an early access preview for partner sandboxes, where Microsoft says "Data changes are committed immediately to Business Central while Copilot works" and "Granular administrative settings or permissions for Edit with Copilot aren't yet available." Until it ships, the Copilot column describes the chat as it runs in production. Here's what each of the five is, and how mature it actually is, not how mature the announcement made it sound.
Business Central's own approval workflow is the baseline
A purchase invoice sent for approval moves to Pending Approval and, in Microsoft's words, "remains locked for processing until all approvers approve the record" (Microsoft Learn). Approval users are set up with amount limits on the Approval User Setup page, and the workflows cover purchase documents and incoming documents (Microsoft Learn). If the invoice above went through that workflow, its approval entries name who approved it, and the Payables Agent hands its unposted draft to exactly that workflow. Whether the company switched the workflow on for vendor invoices is the controller's first question, and it has nothing to do with AI.
The gap this guide covers starts where that workflow stops. It records the approval of the document. By Microsoft's own wording, the Payables Agent's review confirmation is not an approval workflow, so it does not record who reviewed what the agent drafted. It does not show which logic a Power Automate flow used to route an approval, or anything outside the document types the workflows cover. IntelliConnectQ makes the argument for approvals alone in the 3-way version of this guide.
Business Central Agent Designer, Payables Agent and Copilot: where each AI agent's authority stops
Five tools, five different answers to who's allowed to do what, and who has to answer for it afterward. The table below lines them up across the dimensions that matter once something goes wrong: not what a tool does when it works, but what it produces when someone has to check.
| Dimension | Payables Agent | Copilot | Agent Designer | Power Automate | OpsGrid |
|---|---|---|---|---|---|
| Purpose | Extracts invoice data, matches to POs, drafts for review | Conversational Q&A and drafting across BC data | In-product builder for custom BC agents (sandbox environments only) | DIY flows scripting routing around BC events | Governed decision routing on Business Central data |
| Interaction model | Automatic trigger on incoming invoice email | User-initiated, reactive chat | Manual invocation only, no auto triggers yet | Depends on the flow's own trigger logic | Proactive monitoring, routes ranked signals to a named owner |
| Human-in-the-loop | Agent doesn't post; the unposted draft goes to BC's approval workflow, and the agent's own review confirmation is not an approval (Microsoft) | User reviews before acting; no autonomous write path | Runtime requires explicit user review and consent for sensitive operations; each agent's configuration decides what counts as sensitive (Microsoft) | Whatever the builder configures, not platform-enforced | Architectural requirement: no BC write without named-owner approval, for decisions routed through OpsGrid |
| Governance / audit trail | BC change log plus agent timeline (execution log, not a named-approver record). The named approver comes from BC's approval workflow when the draft goes through it | No dedicated audit record beyond the standard BC transaction log | Diagnostic and troubleshooting logs, built for developers | Flow run history | Named owner approves in Teams before any BC write; covers decisions routed through OpsGrid only |
| Pricing / billing model | Copilot credits, prepaid or pay-as-you-go, pooled at the tenant level ($0.01 per credit pay-as-you-go, per Microsoft) | Copilot in Business Central: included with the BC license at no extra cost; fair-use policies, quotas, or pricing might be introduced later (Microsoft). Microsoft 365 Copilot is a separate product with its own licensing; see the credits billing article. | Copilot credits, same model as built-in agents; see how Copilot agents are billed | Premium connector class, per Microsoft's connector page | Active beta, pricing not published |
| Maturity status | GA, Nov 7, 2025 (PO matching GA Feb 6, 2026) | GA, established product | Public preview since Feb 6, 2026; release plan lists GA Oct 2026, not listed in 29.0 what's-new | GA, established product | Active beta, not GA |
The gap in that Maturity row is the one worth sitting with. One of the five, the Payables Agent, has been generally available for less than a year. Agent Designer is in public preview with no committed date: Microsoft's release plan lists October 2026 but won't commit to it holding, the plan page now carries the banner "As of October 2026, this content is archived and no longer maintained," and the update 29.0 what's-new page, last updated October 1, does not list Agent Designer. OpsGrid is in beta. A governance model built around all five assumes a stability only Copilot and Power Automate have earned.
Business Central agent governance has no shared model beyond the approval workflow
The assumption worth challenging: adding more AI coverage inside Business Central closes gaps. It closes capability gaps. It opens a coordination gap, because each tool answers accountability on its own terms. Microsoft built real controls: the approval workflow, an MCP Server Configuration parameter on the Power Automate connector, and a runtime that requires explicit user review for sensitive agent operations. Each operates one tool at a time. Nothing forces the Payables Agent's timeline and a Power Automate flow's run history into one format a compliance team, or an auditor, can read without translating each first.
OpsGrid gives every decision routed through it the same path. A Signal is detected in BC, Routed to one named owner, held for Approval before anything writes back (approve or reject in Teams), Executed only after that approval, and Audited. That sequence doesn't make OpsGrid better at reading an invoice than the Payables Agent, or better at answering a question than Copilot. Its scope is the decisions routed through it. A write made by the Payables Agent, a Power Automate flow or a person working in BC does not become an OpsGrid decision by itself.
The Decision Latency Diagnostic scores your Signal, Route, Approve, Execute, and Audit stages in 12 questions, across whichever of these tools are touching your BC data today.
Take the diagnostic →Which of the five fits the job you actually have
Frequently asked questions
What is Agent Designer in Business Central?
What are Copilot agents in Business Central?
What permissions do I need to create and test agents in Business Central?
Is Business Central's Agent Designer generally available yet?
Do Business Central's built-in AI agents require human approval before they act?
What's the difference between Business Central's Agent Designer and Microsoft Copilot Studio?
Is OpsGrid generally available for Business Central?
Business Central's approval workflow already names who approved a purchase document. By Microsoft's own wording, the Payables Agent's review confirmation is not an approval workflow, so the draft behind that approval has no such record. OpsGrid adds a named-owner approval for the decisions routed through it, and nothing more. That's not a knock on Microsoft's agents; each does its specific job. It's why "we added AI to Business Central" and "we can show an auditor who reviewed what the agent drafted" are still two separate projects.