Dynamics 365 Finance can use agent business skills to prepare an expense report from receipts, reducing the employee’s work to reviewing and submitting the draft. This approach matters to finance teams, ERP administrators and organizations assessing AI-supported finance processes. Microsoft Events demonstrated the expense workflow as part of a session on agentic ERP in Dynamics 365.
The expense example connects an AI agent experience with Dynamics 365 business logic. Instead of entering every receipt detail through the ERP’s transactional interface, an employee supplies receipts to the agent, which prepares an expense report for review. The agent can extract receipt information, match receipts against credit card transactions recorded in the ERP and itemize expenses such as a hotel bill.
The session described this as a use of business skills: capabilities that expose ERP business logic for an agent to use. Microsoft’s presenter said the demonstration used an ERP plug-in in Copilot Cowork to recognize and call the skills. The emphasis is not just on producing text about an expense; the agent uses business operations to assemble a report that appears in Dynamics 365 for manager review.
The workflow also illustrates how employees could work outside the main ERP interface for some tasks. In the demo, the employee continued the conversation on a phone, photographed a missing receipt and added it to the report. After a policy check identified the need for a business justification on a hotel room-service item, the employee selected a justification before submitting.
This is relevant to finance and expense teams, Dynamics 365 Finance customers, and IT or ERP teams responsible for business process controls. The session positioned the approach for organizations that want to use agents in finance and operations while retaining their business rules and review steps. It also described Dynamics 365 as composable: organizations can implement the full suite or start with smaller parts of it.
The expense business skills shown in the session were in preview, with a sign-up form presented for access. The presenter also described Service Agent business skills as in preview. The demonstration used Copilot Cowork as its agent experience and said a Copilot Studio harness was planned for scenarios needing a more dedicated interface. The session did not establish a general release date or a licensing requirement, so teams should verify the current preview conditions before planning deployment.
A useful starting point is to identify a process with clear business value and establish how it works before introducing an agent. Adecco’s CTO described the company’s approach as configuring included agents for relevant use cases first, then building a small number of custom agents where packaged capabilities did not cover its needs. That experience supports a measured process-led evaluation rather than starting with an agent count target.
The demonstration began with an expense report for a business trip. The agent used receipts and ERP data to prepare the report, with the employee responsible for checking the result and completing required information. The sequence shows where automation can reduce manual entry without removing the employee’s review.
The session described the underlying architecture as investments in the ERP business logic and data layer, augmented by a semantic layer and business skills. It also discussed Model Context Protocol (MCP) servers as an API approach for agents to interact with that business logic. The stated aim is to let organizations use Microsoft or other agent experiences while connecting to the same business capabilities and controls.
The showcased business skills were in preview, so they should be treated as preview capabilities rather than a generally available production workflow. Organizations evaluating them should check the applicable preview access and assess the expense process against their own policies before relying on an agent-prepared report.
Automation does not remove the need for sound data, policies, permissions and governance. Adecco’s CTO cautioned that agents need defined boundaries, including when a person must make a decision. For expense management, the demo itself included employee review and a manager-review status. Those checks matter because agents operating in ERP processes can affect financial records and business decisions.
There is also a choice of working interface. The session showed Copilot Cowork and said Copilot Studio would provide a harness for more dedicated scenarios; the presenter also described business skills as usable with different agent harnesses. For organizations not ready to use the preview, the conventional Dynamics 365 transactional interface remains the alternative shown alongside the agent workflow. A sensible evaluation is to compare the existing steps, controls and outcomes before deciding whether the agent meaningfully improves the process.
In the demonstrated workflow, the employee provides receipt images and the agent extracts details, matches receipts to ERP credit card transactions and prepares a report. The employee checks the report, supplies required justifications and submits it.
The session described the expense business skills as being in preview and showed a sign-up form for access.
No. The employee reviewed and submitted the report in the demonstration, and Dynamics 365 showed it in review by the manager.
The session described business skills as usable through different agent harnesses. It demonstrated Copilot Cowork and said a Copilot Studio harness was planned for more dedicated scenarios.