Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Recorded 17 Nov 2026 at 04:55 UTC. This is what ChangeIntel recorded, including the title, summary, facts and links. It is not a statement of the source's current position. See the latest record.

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

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 vend…

What changed

  1. Availability target: Not stated → October CY2026
  2. Availability target: October CY2026 → Not stated
  3. Availability target: Not stated → October CY2026
  4. Availability target: October CY2026 → Not stated
  5. Availability target: Not stated → October CY2026
  6. Availability target: October CY2026 → Not stated
Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (71)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 17 Nov 2026 · 04:55:19 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  2. 16 Nov 2026 · 02:39:04 UTC General availability targetNot stated → October CY2026
  3. 16 Nov 2026 · 02:39:04 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  4. 16 Nov 2026 · 02:39:04 UTC Source coverage: microsoft-365-roadmapCurrent
  5. 16 Nov 2026 · 02:39:04 UTC Link: Dynamics 365 Business Central/roadmap?topic=Dynamics%20365%20Business%20Central&period=all#items → No longer listed in this observation
  6. 16 Nov 2026 · 02:39:04 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  7. 16 Nov 2026 · 02:39:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573380
  8. 16 Nov 2026 · 02:39:04 UTC SummaryThis feature improves PO matching quality in Payables Agent and aligns draft finalization behavior with existing posting controls. → 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 vend…
  9. 16 Nov 2026 · 01:34:04 UTC General availability targetOctober CY2026 → Not stated
  10. 16 Nov 2026 · 01:34:04 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  11. 16 Nov 2026 · 01:34:04 UTC Source coverage: merill-message-center-archiveCurrent
  12. 16 Nov 2026 · 01:34:04 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  13. 16 Nov 2026 · 01:34:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573380 → No longer listed in this observation
  14. 16 Nov 2026 · 01:34:04 UTC Link: Dynamics 365 Business Central/roadmap?topic=Dynamics%20365%20Business%20Central&period=all#items
  15. 16 Nov 2026 · 01:34:04 UTC SummaryThis 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 vend… → This feature improves PO matching quality in Payables Agent and aligns draft finalization behavior with existing posting controls.
  16. 16 Nov 2026 · 01:23:36 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  17. 5 Nov 2026 · 18:04:05 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  18. 5 Nov 2026 · 17:01:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  19. 4 Nov 2026 · 15:02:25 UTC General availability targetNot stated → October CY2026
  20. 4 Nov 2026 · 15:02:25 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  21. 4 Nov 2026 · 15:02:25 UTC Source coverage: microsoft-365-roadmapCurrent
  22. 4 Nov 2026 · 15:02:25 UTC Link: Dynamics 365 Business Central/roadmap?topic=Dynamics%20365%20Business%20Central&period=all#items → No longer listed in this observation
  23. 4 Nov 2026 · 15:02:25 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  24. 4 Nov 2026 · 15:02:25 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573380
  25. 4 Nov 2026 · 15:02:25 UTC SummaryThis feature improves PO matching quality in Payables Agent and aligns draft finalization behavior with existing posting controls. → 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 vend…
  26. 4 Nov 2026 · 13:26:53 UTC General availability targetOctober CY2026 → Not stated
  27. 4 Nov 2026 · 13:26:53 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  28. 4 Nov 2026 · 13:26:53 UTC Source coverage: merill-message-center-archiveCurrent
  29. 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  30. 4 Nov 2026 · 13:26:53 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573380 → No longer listed in this observation
  31. 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365 Business Central/roadmap?topic=Dynamics%20365%20Business%20Central&period=all#items
  32. 4 Nov 2026 · 13:26:53 UTC SummaryThis 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 vend… → This feature improves PO matching quality in Payables Agent and aligns draft finalization behavior with existing posting controls.
  33. 4 Nov 2026 · 13:10:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  34. 4 Nov 2026 · 11:04:04 UTC General availability targetNot stated → October CY2026
  35. 4 Nov 2026 · 11:04:04 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  36. 4 Nov 2026 · 11:04:04 UTC Source coverage: microsoft-365-roadmapCurrent
  37. 4 Nov 2026 · 11:04:04 UTC Link: Dynamics 365 Business Central/roadmap?topic=Dynamics%20365%20Business%20Central&period=all#items → No longer listed in this observation
  38. 4 Nov 2026 · 11:04:04 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  39. 4 Nov 2026 · 11:04:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573380
  40. 4 Nov 2026 · 11:04:04 UTC SummaryThis feature improves PO matching quality in Payables Agent and aligns draft finalization behavior with existing posting controls. → 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 vend…
  41. 4 Nov 2026 · 10:01:18 UTC General availability targetOctober CY2026 → Not stated
  42. 4 Nov 2026 · 10:01:18 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  43. 4 Nov 2026 · 10:01:18 UTC Source coverage: merill-message-center-archiveCurrent
  44. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  45. 4 Nov 2026 · 10:01:18 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573380 → No longer listed in this observation
  46. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365 Business Central/roadmap?topic=Dynamics%20365%20Business%20Central&period=all#items
  47. 4 Nov 2026 · 10:01:18 UTC SummaryThis 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 vend… → This feature improves PO matching quality in Payables Agent and aligns draft finalization behavior with existing posting controls.
  48. 4 Nov 2026 · 07:16:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  49. 3 Nov 2026 · 10:16:39 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  50. 3 Nov 2026 · 09:13:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  51. 28 Oct 2026 · 08:37:56 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/microsoft-365/roadmap?id=573380 → https://www.microsoft.com/en-us/microsoft-365/roadmap?id=573380
  52. 26 Oct 2026 · 18:49:55 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  53. 26 Oct 2026 · 17:48:57 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  54. 26 Oct 2026 · 06:24:14 UTC Link: Microsoft 365 Message Center Archive by Merill Fernandohttps://mc.merill.net/message/RM573380
  55. 25 Oct 2026 · 20:06:13 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  56. 25 Oct 2026 · 18:13:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  57. 24 Oct 2026 · 11:31:34 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  58. 24 Oct 2026 · 09:51:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  59. 23 Oct 2026 · 09:33:49 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  60. 23 Oct 2026 · 08:31:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  61. 22 Oct 2026 · 18:42:24 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  62. 22 Oct 2026 · 17:41:25 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  63. 21 Oct 2026 · 20:45:25 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  64. 21 Oct 2026 · 19:44:24 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  65. 18 Oct 2026 · 14:54:30 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  66. 15 Oct 2026 · 14:22:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  67. 15 Oct 2026 · 13:21:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  68. 15 Oct 2026 · 12:20:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  69. 15 Oct 2026 · 11:19:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  70. 14 Oct 2026 · 11:54:40 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  71. 14 Oct 2026 · 11:22:42 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 17 Nov 12:19 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current