The Dynamics 365 Wave 2 2026 release arrives in an unprecedented context: it is the last wave published under the traditional model. Starting in October 2026, Microsoft is retiring the biannual release-plan cycle in favour of a continuous AI at Work roadmap. The functional content of this wave is anything but minor, however: accounting automation, AI agents moving to GA, European e-invoicing compliance, and intelligent warehouse management. Here is a structured overview for CIOs and application owners.
Context: the end of the classic release-wave model
For years Microsoft organised its Dynamics 365 releases in two annual waves: Wave 1 (April to September) and Wave 2 (October to March). Release plans were published on Microsoft Learn with precise preview and GA dates.
Since September 2026 that model has been retired. New features for Dynamics 365, Power Platform, and Dataverse are now published directly on the AI at Work roadmap. The Release Planner site will be decommissioned on 15 November 2026. Existing wave release plans remain available as a historical reference (Microsoft Learn, Release Plans announcement).
What this means in practice for your organisation:
- No more bi-annual grouped previews: features arrive continuously, filterable by product and date on the new roadmap.
- RSS subscriptions per product replace the wave-PDF monitoring routine.
- The concept of “feature preview” (sandbox testing before mandatory GA) still applies, but timelines must be evaluated feature by feature rather than by wave.
For the October 2026 – March 2027 release period, all features planned in Wave 1 2026 that had not yet reached GA now apply. The sections below cover the most impactful items for Finance, Supply Chain, and Business Central teams.
Dynamics 365 Finance: priority updates
Account Reconciliation Agent: AI-driven bank reconciliation
The highest-visibility feature for accounting teams in this period is the Account Reconciliation Agent, which reached GA in late September 2026 (Microsoft Learn, Enhancements to Account reconciliation agent, Wave 1 2026). This AI agent compares bank statement lines with ledger entries, identifies discrepancies, and proposes matching rules. The goal: reduce manual month-end reconciliation work.
Important for multi-entity organisations: the feature supports automatic clearing of centralized bridged vendor payments. Vendor payments routed through a central entity are cleared automatically during bank reconciliation, without manual entry.
This is not full automation. The agent proposes; the team approves. For organisations processing several hundred lines per period, the time saving is material. The prerequisite remains data quality: clean bank data and a well-structured chart of accounts.
Reconciliation preview: test before you commit
A complementary feature available in preview since August 2026: preview of automatic reconciliation results before applying them. Previously, the matching algorithm applied its rules directly — errors were hard to detect before posting.
The preview mode lets the team see the algorithm’s proposals in a dedicated interface, approve or reject them line by line, and then apply them in bulk. Activate this in sandbox as soon as possible to validate the behaviour against your own data.
European E-Invoicing Compliance: France and the broader EU mandate
For organisations with European entities, one of the most strategically important features of 2026 is e-invoicing and e-reporting compliance, which reached GA for France on 24 July 2026 (Microsoft Learn, Meet requirements for e-invoicing and e-reporting in France). The French implementation covers structured electronic invoice issuance via the Chorus Pro platform, VAT e-reporting to the DGFiP, and integration within the unified Electronic invoicing service of Dynamics 365 Finance.
More broadly, the EU’s push toward mandatory B2B e-invoicing is accelerating: Germany’s B2X mandate (Xrechnung/Peppol), Poland’s KSeF platform, Italy’s Sistema di Interscambio, and Belgium’s Hermes system are all converging on structured-invoice requirements. The same Electronic invoicing service framework in Dynamics 365 Finance underpins country-specific adapters across the EU.
If your Dynamics 365 Finance deployment covers entities in any of these jurisdictions and you have not yet activated the relevant adapter, this should be your immediate priority. Regulatory deadlines for mandatory electronic invoicing vary by country and are phased progressively.
Fixed asset transfers between legal entities
For multi-entity groups, a practical addition: fixed asset transfer between legal entities with reporting currency adjustment reaches GA in September 2026 (Microsoft Learn, Transfer fixed assets between legal entities). Previously this type of operation required manual journal entries in both entities, with risk of depreciation and valuation discrepancies.
The feature automates the full accounting flow: disposal in the source entity, acquisition in the target entity, and reporting-currency adjustment. Relevant for intragroup restructurings and internal asset disposals.
Rental model support
New to the Finance 2026 perimeter: rental business model support. Dynamics 365 Finance now includes a framework for managing leased assets — tracking rented assets, recognising recurring revenue, and managing lease contracts. This addresses organisations operating on usage-based or asset-heavy models (Microsoft Learn, Finance 2026 Wave 1 overview).
Dynamics 365 Supply Chain Management: operations updates
AI explanations for forecast accuracy: finally, legibility
One of the most practically useful additions on the Supply Chain side: Understand forecast accuracy with AI explanations (GA: October 2026, Microsoft Learn, SCM planned features Wave 1 2026). Previously a forecast deviation was visible on dashboards but had no contextual explanation.
This feature adds an AI explanation layer: why a specific SKU diverged from actuals, which factors contributed to the gap (seasonality, promotions, supply incidents). The aim is to make forecast-review cycles faster and better documented. No configuration is required — the feature is automatically enabled for users.
In preview since late July 2026, it reaches GA on 1 October. If you are on a production tenant with Planning Optimization active, it will be available automatically.
Warehouse management: dynamic item placement
Enhance warehouse efficiency with dynamic item placement reaches GA in October 2026 (Microsoft Learn, SCM planned features). This feature automatically reorganises picking locations based on actual throughput, shipment profiles, and handling constraints. The system recommends optimal locations during replenishment cycles.
For high-SKU-count warehouses, the benefit is twofold: reduced picking travel and better utilisation of storage capacity. It requires upfront configuration by an administrator (location profiles, placement rules) before it is available to warehouse staff.
Supplier Engagement: a dedicated supplier portal
Manage supplier relationships with Supplier Engagement: this advanced feature has been available in preview since July 2026, with GA planned for March 2027 (Microsoft Learn). It provides a collaborative space where suppliers access their purchase orders directly, confirm delivery dates, and submit acknowledgements.
Its Q1 2027 GA date places it outside the immediate wave window. Do not activate it in production yet: it is in preview, and preview features can behave unexpectedly with production data. This is a feature to test in sandbox with a few pilot suppliers.
Procurement Agent: impact analysis for PO changes
Manage the downstream impact of PO changes with Procurement Agent impact analysis has been available in preview since late April 2026. For each purchase order change (quantity, date, price), the agent analyses downstream impact: linked production orders, planned requirements, logistics milestones. It generates an impact report that the procurement manager reviews before confirming the change.
This feature must be configured and enabled by an administrator. Its GA date has not yet been announced on the published roadmap: monitor via the AI at Work roadmap.
Dynamics 365 Business Central 29: SMB updates
Business Central 29, the version corresponding to the October 2026 wave, delivers several concrete improvements.
Payables Agent: autonomous AP processing for SMBs
The standout feature of Business Central 29 for accounting teams: the Payables Agent. It automates end-to-end supplier invoice processing — reading incoming invoices, identifying vendors and account lines, and preparing invoices for human approval. Copilot integration assists with purchase-order matching (activebs.com, Business Central 29).
This is automation designed with mandatory human validation in the loop. The agent does not post autonomously: it prepares and submits for approval. For an SMB processing 20 to 200 supplier invoices per month, this represents a measurable time saving on incoming accounting mail.
Multichannel order processing
Business Central 29 introduces automated handling of incoming orders across multiple channels: email, Teams, Shopify, and EDI. Orders received by email or via e-commerce platforms are parsed automatically, created in the system, and submitted for validation. Shopify integration gains depth: B2B catalogue management per account, AI-based VAT line matching, synchronisation of exchanges, returns, and credit notes.
For distributors and wholesalers working with customers across multiple channels, this feature reduces manual re-entry and order-creation errors.
Redesigned reporting: packs and change logs
Two practical improvements for finance and management-control teams:
Report packs: it is now possible to group multiple financial reports (income statement, balance sheet, cash flow) into a single PDF exported in one operation. No more manual, report-by-report exports before each board meeting.
Financial report change logging: the history of changes to financial report structures, rows, and formulas is now logged. For organisations subject to audit, this provides useful traceability for justifying the evolution of reporting formats.
Carbon footprint and sustainability: a foundation for ESG reporting
Business Central 29 extends carbon-footprint tracking to fixed assets and service invoices. Footprints can be calculated using specific methods (exact factor, formula). For SMBs feeding a group-level CSRD report or a Scope 3 report for large enterprise customers, this is structured data built directly into the ERP.
Technical alert: SOAP API retirement
A critical notice for technical teams: SOAP APIs are permanently removed in Business Central 29. Any integration built on these protocols must migrate to REST OData v4 APIs. If your organisation uses third-party connectors or custom developments on SOAP, this migration is a blocking prerequisite for upgrading to version 29.
Features to monitor but not activate immediately
Preview features: regression risk
The following features are in preview at the start of Wave 2 2026 and must not be activated in production environments:
- Supplier Engagement (Supply Chain): preview, GA March 2027. Sandbox testing only.
- Procurement Agent impact analysis: preview, no GA date announced. Sandbox use recommended.
- Delay settlement from journal posting (Finance): preview since August 2026, GA not announced. This feature modifies the base behaviour of the payment journal; validate carefully against your specific processes.
- Invoice capture enhancements and Subscription billing enhancements (Finance): in preview since September 2026, GA not yet published.
Activation checklist for production tenants
Before activating any new feature on your production Dynamics 365 environment, apply this sequence systematically:
- Sandbox first: enable the feature in your test environment with a recent copy of production data.
- Test against your specific use cases: do not limit yourself to standard Microsoft documentation scenarios. Test your local configurations, extensions, and integrations.
- Validate impact on existing integrations: accounting automation features can modify the output of flows toward BI tools, third-party ERPs, or HR systems. Verify expected outputs.
- Train key users before deployment: AI agents (Account Reconciliation Agent, Payables Agent) change working habits. Activating without training generates resistance and validation errors.
- Communicate to business teams: for every feature in the “Users, automatically” activation category, brief affected teams in advance. Some modify the interface or the default behaviour of forms.
Recommended deployment timeline for CIOs
October–November 2026: priority actions
- Account Reconciliation Agent (Finance): GA, activate in sandbox then production after testing.
- E-invoicing compliance (Finance): GA since July 2026 for France; check status for other EU jurisdictions your deployment covers. If not yet activated, treat as urgent.
- Forecast accuracy AI explanations (SCM): enabled automatically, no action required.
- Dynamic item placement (SCM Warehouse): GA October 2026, administrator configuration required.
- Business Central 29 (BC): automatic update in cloud environments. Verify that your extensions are compatible before moving to production.
December 2026–January 2027: roadmap monitoring migration
With the Release Planner shutting down on 15 November 2026, reconfigure your monitoring process:
- Subscribe to the RSS feed of the AI at Work roadmap filtered by Dynamics 365 Finance, Supply Chain, or Business Central depending on your scope.
- Export the roadmap to CSV at regular intervals to track GA date changes.
- Update your change-management processes: internal communication on new features must become more reactive, since releases are no longer grouped.
Role of the Microsoft partner consultant
For features requiring configuration (warehouse dynamics, AI agents with custom rules, Supplier Engagement), your partner consultant’s involvement is recommended. Correct activation depends on your tenant parameterisation, your ISV extensions, and your customised workflows.
For automatically-enabled features, a business-process impact assessment is usually sufficient to validate without external intervention.
To go further in the Dynamics 365 ecosystem, see our guide on Microsoft Copilot for Finance in Dynamics 365, our comparison of IFS Cloud vs Dynamics 365 Supply Chain Management for industrial mid-market organisations, and our analysis of SAP S/4HANA Cloud vs Oracle Fusion vs Dynamics 365 Finance.
