Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Some of the functionality described in this release plan has not been released. Delivery timelines may change and projected functionality may not be released (see Microsoft policy). Learn more: What's new and planned
| Enabled for | Public preview | General availability |
|---|---|---|
| Users by admins, makers, or analysts | Nov 2025 | - |
Business value
By making the Payables Agent more aware of the context of your historical purchase invoices, its matching accuracy and the granularity of draft suggestions improve. As a result, you receive suggestions that are more relevant to the specific invoice you’re working on. This reduces the need for manual corrections, since the agent’s recommendations become more closely aligned with your company’s Payables Agent processing history, saving you time.
Feature details
It's at the core of the Payables Agent to suggest invoice drafts as accurately as possible. Ideally, the accounts payable team doesn't have anything—or very little—to change on the purchase document drafts that the agent creates. The agent relies on its purchase invoice processing history, meaning the details of previously processed invoices and how they were handled. For example, if you previously used the agent to register an electrician bill on a certain G/L account, the agent in many cases suggests that same G/L account for similar invoices from the same vendor.
The key word here is "similar." As part of making the agent more intelligent, it now considers more information to determine the context and similarity of historical invoices and how that compares to the invoice currently being processed. This context could include other text on the invoice header or footer, other line descriptions, and so on. By increasing the agent's understanding of context, the agent is more likely to distinguish invoices that—on the surface—look the same but aren't. In these cases, for example, an electrician bill requires a different G/L account if the delivered electrician service is for a manufacturing asset in the manufacturing facility, not for putting up new lamps in the office building.
This enhanced contextual awareness requires no extra setup to the agent and allows the agent to better distinguish scenarios, improve matching, and draft invoices more successfully.
Geographic areas
Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.
Language availability
Visit the Explore Feature Language report for information on this feature's availability.