EskerNews

Esker Brings Supplier Payment Risk Checks Into Microsoft Copilot

Esker has announced a Microsoft Copilot integration that lets finance teams examine supplier payment risks, investigate the invoices involved and initiate follow-up work through its source-to-pay platform. Announced on November 18, the experience brings interactive Esker interfaces into Copilot while leaving business workflows and process controls in Esker.

The integration gives finance leaders a way to move from a question about payment exposure to the records behind it within the same conversation. According to Esker, users can explore affected suppliers and invoices, then initiate relevant activities through established workflows. The announcement does not describe Copilot independently authorizing or executing supplier payments.

Esker brings supplier payment risk checks and invoice investigation into Microsoft Copilot, with follow-up actions handled through existing finance workflows.

Following payment risk down to the invoice

A companion explanation by Catherine Dupuy-Holdich, Esker’s source-to-pay product manager, illustrates how the experience works. A CFO asks the Esker Synergy Agent about upcoming supplier payments in Copilot. An interactive dashboard then displays potential late-payment exposure, with access to the suppliers and individual invoices requiring attention.

The example shows €1.6 million in exposure across 23 invoices. These are figures in Esker’s illustrative scenario, not reported customer results or evidence of savings delivered by the integration.

The experience uses MCP Apps, an extension of the Model Context Protocol that supports interactive application interfaces inside compatible AI environments. Esker describes dashboards, tables, charts and forms appearing within a conversation, giving users a way to examine financial information beyond a text response.

The product team also outlines possible uses involving blocked invoices, supplier spending and purchase-request status. Its discussion extends to order-to-cash scenarios, including overdue receivables and credit reviews. Those examples are presented as potential applications of the approach, rather than confirmation that every described function is available through the announced Copilot integration.

Where the controls remain

Esker says its platform continues to provide the business context, workflows, process controls and governance behind the Copilot experience. The intended operational benefit is fewer application changes between identifying a payment issue and starting the work needed to address it. The announcement provides no measured reduction in investigation time or customer deployment results.

The arrangement follows the architecture discussed in ERP News’ interview with Esker executive Jean-Jacques Bérard on governed autonomous finance. Bérard explained that an agent’s proposed action must pass identity checks, permissions, business rules, validations and approval boundaries before execution. Cases outside policy or with significant consequences are escalated to a person.

In that interview, Bérard also distinguished the responsibilities of ERP and the surrounding finance applications. ERP remains the authoritative record for financial data and accounting entries, while Esker coordinates work such as document interpretation, exception resolution, communications and approvals. The Copilot announcement adds a specific interface through which users can access selected Esker capabilities.

Finance leaders want more AI involvement, with limits

Esker’s earlier research provides context for that emphasis on control. Its 2026 Global Finance AI Trust Index found that 66% of respondents wanted finance decisions to be primarily AI-guided or AI-enabled within the following year. That finding describes respondents’ intentions, not the proportion of finance decisions already being made by AI.

The company surveyed 338 finance leaders in August 2026. The sample included 137 CFOs in the United States, United Kingdom, European Union, Australia and Canada, plus 201 other finance leaders at director level or above in the United States and United Kingdom. The results reflect that respondent group’s reported views and experiences, rather than an independent assessment of Esker’s products.

Integration was a practical obstacle: 42% cited insufficient connections between finance systems and AI tools as a barrier to expanding AI’s decision-making role. Data quality was cited by 48%.

For organizations evaluating the Copilot experience, commercial and deployment details remain unresolved in the public announcement. Esker does not specify a general-availability date, pricing, required Copilot edition or regional rollout. Its product explanation also states that support for particular AI clients, interfaces and actions depends on the capabilities available and validated for each integration.

ERP News Editorial Team
+ posts

We cover ERP and enterprise technology for the people who select, implement, and run these systems.

Pitch a guest article or work with our editorial team on a news story, customer case study, or executive interview.

Editorial Calendar · Pitch a Guest Article · Commission a Story

Advertising Options · ERP News Magazine · ERPNews.com

Editorial Inquiries · [email protected]

Copyright & Usage · Our original editorial content is produced by the ERP News Editorial Team, with expertise in ERP and enterprise technology.

© ERP News. All rights reserved. Except as permitted by law, reproduction, republication, and redistribution require prior written permission or a licence from ERP News, along with clear attribution to ERP News as the source.

ERP News Content Licensing · License full-text ERP News articles for your internal research tools, delivered through a private JSON feed. [email protected]

Shares: