A finance dashboard pairs Copilot’s supplier-risk analysis with invoice exceptions, supplier records, approval workflows, and secure data integrations.
Esker has put a source-to-pay (S2P) experience inside Microsoft Copilot. It is aimed at finance teams that want to chase down supplier-payment risks without leaving the chat window. The announcement is vendor-led, so the details are thin in places. It is still a useful example of where Copilot's extensibility is heading, and it raises questions IT admins should ask early.

A finance dashboard pairs Copilot’s supplier-risk analysis with invoice exceptions, supplier records, approval workflows, and secure data integrations. What Esker announced​

Esker announced on November 18, 2026 a new experience that brings its source-to-pay capabilities directly into Microsoft Copilot. It is powered by Model Context Protocol (MCP) Apps technology. IT Brief and CFOtech Asia, two sister publications, carried the same story on November 19.

Esker's pitch is that instead of a simple AI-generated answer, its conversational interface surfaces the business context needed to investigate issues in depth and start informed actions. Esker lists four claimed benefits:

  • Visibility: spot potential supplier-payment risks and understand their impact.
  • Faster investigation: explore affected suppliers, invoices and related information through interactive Esker interfaces inside Copilot.
  • Insight to action: start follow-up activities through Esker's established workflows.
  • Less app switching: work in an environment employees already use.

Esker's own blog gives an illustrative scenario in which a CFO could ask whether any supplier payments are at risk this week. It also suggests an AP manager could ask which invoices are blocked and why, with Esker displaying exceptions, workflow information and invoice details. These are hypothetical examples, not customer results.

Copilot is the front door, not the vault​

The key architectural point is that nothing moves into Microsoft. Copilot provides a new entry point, while Esker remains the underlying platform responsible for business context, workflows, process controls and governance. In other words, Copilot is a new front end. The system of record and its guardrails stay with Esker.

That matters in finance. Supplier payments and procurement are tightly governed, and as IT Brief notes, companies have been cautious about AI that moves from recommendations into direct action, especially where audit trails, approvals and policy checks apply.

Why MCP Apps matter​

Plain MCP lets a server expose tools and data to an AI assistant, but responses are text and structured data. MCP Apps, per the project's overview, is an extension that lets servers deliver interactive interfaces such as dashboards, forms and approval workflows. Hosts render those interfaces in sandboxed iframes. If a host doesn't support apps, the tools still work but return text instead of a UI.

Microsoft's Copilot Studio documentation, last updated November 17, 2026, adds platform-specific limits that readers should know:

  • MCP apps are supported in Microsoft 365 Copilot and Copilot Studio preview chat. They are not supported in Teams or web chat.
  • Connecting an MCP server does not create an app. The server must declare a UI resource for a tool.
  • The host renders the app in a sandboxed, cross-origin iframe with content security policy restrictions. The app has no direct access to the host page or credentials. Tool calls and resource reads remain subject to connection, authentication and runtime checks.
  • Some capabilities are not supported. These include tool-cancellation notifications, file downloads and MCP logging notifications. Cancelling an app-originated operation is not supported end to end, so an operation might keep running after the app closes.

These are general Microsoft platform details. They do not describe Esker's own configuration, and nothing in the evidence confirms which of these Copilot surfaces Esker's experience runs on.

What the announcement doesn't say​

The release leaves a lot unanswered. It does not give pricing, supported Copilot plans, regions, required Esker editions, setup steps, the authentication model or audit-log behaviour. It also does not say exactly which actions users can trigger. There are no measured gains in investigation time or error rates, and no customer case study. Treat "faster" and "less friction" as vendor claims.

CFOtech and IT Brief also repeat an Esker statistic that 66% of finance leaders want decision-making in their teams to be primarily AI-guided or AI-enabled within a year, drawn from the company's Global Finance AI Trust Index. That figure is not in the Copilot press release, and no sample size or methodology was supplied. Treat it as company marketing research rather than a settled benchmark.

Quotes and attribution​

Matthias Goehler, Esker's chief product officer, framed the move as shifting enterprise AI from generating answers to enabling action, while keeping the controls financial processes require. Chantrelle Nielsen, group program manager for Copilot Ecosystem at Microsoft, said connecting Copilot with business applications is key to bringing AI into the flow of work. Both are promotional statements, not independent validation of effectiveness or security.

What IT and finance teams should ask​

If you run a Microsoft 365 tenant and finance wants this, the practical questions are about governance:

  1. Which Copilot surface and licence? Microsoft's own support is limited to Microsoft 365 Copilot and Copilot Studio preview chat. Ask Esker which one it targets.
  2. How is identity handled? Ask how Copilot users map to Esker permissions, and whether a user can see supplier or invoice data they couldn't see in Esker directly.
  3. Which actions write data? Ask what follow-ups can be started from chat, which need approval, and where they are logged.
  4. What data goes to Copilot? Ask what is exchanged with the model context, and whether it fits your data-handling policy.
  5. What happens on failure or cancellation? Given Microsoft's documented cancellation limits, ask how half-finished operations are handled.

Bottom line​

For Windows and Microsoft 365 shops, the news is less about Esker than about the pattern. Vendors are using MCP Apps to turn Copilot into a shell for line-of-business tools. The finance use case is sensible because the controls stay in the source system, but the real test is permissions, approvals and audit trails, and the announcement doesn't cover those. Until Esker publishes them, this is a promising interface change, not a proven control improvement.

 

References

  1. Esker brings source-to-pay risk checks into Copilot IT Brief UK 2026-11-19T16:45:00+00:00
  2. Esker brings source-to-pay risk checks into Copilot - CFOtech Asia CFOtech Asia 2026-11-19T16:45:00+00:00
  3. Esker brings source-to-pay risk checks into Copilot cfotech.ca