Dynamics 365 Business Central: Copilot and agents - Improve purchase order matching in Payables Agent

Dynamics 365 Business Central: Copilot and agents - Improve purchase order matching in Payables Agent is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: Launched.

This feature improves PO matching quality in Payables Agent and aligns draft finalization behavior with existing posting controls. The agent uses an enriched PO Lines list page during matching that includes these fields: Line Amount — enables matching on value, not just description and quantity. This field is especially valuable for service lines where quantity (often just 1) isn't a meaningful discriminator. Expected Receipt Date — helps the agent factor in timing when multiple PO lines could match. By using these fields, the agent can more reliably distinguish between similar-looking PO lines, which improves accuracy in first-pass matches. The agent now respects the app's Never block draft finalization setting in the Receipt on Invoice field on purchase orders. This change means the agent doesn't block draft finalization because a matched PO line isn't yet marked as received. Whether goods are received is a posting time control, not a draft time control. The "Receipt on Invoice" setting on the order governs this behavior at posting. The "Receipt on Invoice" field is already available on purchase orders. With this release, we're expanding this setting to more entities: A new vendor-level "Receipt on Invoice" setting is introduced and automatically applied to new purchase orders created for a vendor. A new PO-line-level "Receipt on Invoice" setting allows per-line override. The inheritance chain for the setting is vendor, then purchase order, and then purchase order line, but each level can override the parent. We've also improved draft warnings. When the agent creates a purchase invoice draft matched to a PO, the draft surfaces warnings based not just on quantity, but also on amount. The draft warnings are for information only and don't block finalization. For example, they warn about the discrepancies in the draft and you can decide how to proceed.

Wave 0 first: Security → GRC → Cost & Value → Licence → Adoption. Put this on the agent register with a named owner. Do not enable broadly until permissions, DLP, and reclaim rules exist.

12 Panes: 03 Horizon · 04 Security · 05 GRC · 09 Work & Skills

• Security: Assess exposure, Conditional Access, and agent/tool permissions.
• GRC: Update AI/agent register and evidence path; confirm DPIA triggers if personal data is in scope.
• FinOps: Forecast seat or credit impact; align to frozen value case.
• Adoption: Plan cohort messaging, clinics, and success measures.
• Comms: One story for board and staff — what changes, what does not, who owns risk.

• May improve productivity on a specific Microsoft 365 surface when permissions and data quality allow.
• Roadmap visibility helps Horizon planning without guessing dates.
• Agents can automate multi-step work inside existing Microsoft 365 permissions.

• Status and dates change; treat MRC as directional, not a contract.
• Enabling without Steady controls can amplify overshare or cost leakage.
• Agents act; over-privilege and ownerless agents create lasting exposure.

• MRC id: 573380
• Status: Launched
• Products: Dynamics 365 Business Central
• GA / disclosure: October CY2026
• Preview: —
• Platforms: Web
• Cloud instances: Worldwide (Standard Multi-Tenant)
• moreInfoUrls: —
• Open on Microsoft 365 Roadmap

Microsoft Release Communications / Microsoft 365 Roadmap (AI at Work). Content is subject to Microsoft API Terms of Use. Dates and status change; verify in the official roadmap before acting.