Still on the Table: Dynamics 365 Finance 2025 Release Wave 2 Features Your Team Is Probably Underusing

Posted on: June 11, 2026 | By: Kyle Valerio | Microsoft Dynamics AX/365, Microsoft Dynamics AX/365|Microsoft Dynamics Manufacturing

The 2025 release wave 2 for Dynamics 365 Finance covers the new functionality Microsoft delivered to market between October 2025 and March 2026. Each release wave represents roughly six months of planned investment, and this one continues a clear trajectory for the product. As finance organizations scale to meet growing complexity, spanning global entities, evolving regulations, and rising performance demands, the role of finance has expanded well beyond closing the books. Teams are now expected to move faster, manage risk more proactively, and adapt as conditions change.

This release reflects that shift. Microsoft’s focus is on global-scale finance and what it describes as agentic operations. In practice that means deepening multi-entity capabilities, accelerating period-end close through more flexible hierarchies, and continuing to build automation and AI agents into everyday finance work. The most significant change for organizations running complex, multi-company structures is the new journal framework and accounting rules engine, so that is where this overview begins.

The New Journal Framework and Accounting Rules Engine: More Flexibility, Less Customization

Journals are the foundation of how transactions are recorded, and for years the logic that controlled them was rigid enough that organizations routinely turned to customizations and workarounds to make it fit their structure. The new journal framework and accounting rules engine change that balance. They give you the flexibility to configure finance processes across legal entities to match your specific organization or industry, and they do it through configuration rather than custom code.

What the new journal framework changes

The framework rebuilds how journals are imported, validated, and posted, and the practical differences show up quickly in a multi-entity environment:

• Multi-company journals. Users can enter vouchers spanning multiple companies within a single journal, governed by their security access. Intercompany and cross-entity activity that used to require separate journals can be handled in one place.
• Voucher-level processing. Validation, approvals, and posting can begin at the journal level but execute per voucher. If one voucher has an issue, the rest are not held up, which improves both accuracy and throughput.
• Stronger performance on large journals. Import, validation, and posting are faster, which matters most during high-volume periods and at period-end close.
• Voucher types and clearer visibility. Specific voucher types categorize transactions for better tracking and lifecycle management, addressing a long-standing gap in transaction visibility.
• Simplified reversals. Correcting entries is more straightforward than in the prior model.

What the accounting rules engine adds

The accounting rules engine sits alongside the framework and centralizes how postings are determined. Instead of posting logic being scattered and difficult to trace, a single configuration page brings posting account setup together and enforces consistent rules for general ledger postings. Two aspects stand out for finance and audit teams:

• Centralized, consistent posting rules. A unified setup page improves consistency and visibility, so the same logic applies across the organization rather than being maintained in several places.
• Versioning and traceability. Each transaction links to the posting rule that produced it, and rule changes are versioned and documented. That creates a clear audit trail, strengthens governance, and reduces the posting errors that surface as adjustments during an audit.

A practical walkthrough for a multi-entity team

Consider a finance team responsible for several legal entities that share most of their chart of accounts but differ in a few posting requirements. Under the older model, accommodating those differences often meant per-entity customizations and manual checks. With the new approach, the team defines posting rules once on the centralized accounting rules page, sets the variations where entities genuinely diverge, and lets the engine apply that logic consistently wherever it posts.

Day to day, an accountant can record activity that touches more than one company in a single multi-company journal rather than rekeying the same entry across entities. Validation and posting run per voucher, so a problem in one line does not stall the batch. When auditors later ask why a particular transaction posted the way it did, the versioned rule history answers the question directly, without a manual reconstruction of how the setup looked at the time.

The net effect is the theme Microsoft is emphasizing across the release: more flexibility to fit your structure, with far less reliance on customization to get there. It is worth noting that the framework is being rolled out in stages, building on the foundation introduced earlier in 2025, with support for broader account types such as vendor, customer, and asset journals on the roadmap. Checking the release plan for the current state of each piece is the best way to confirm what is available in your environment.

Other Headline Capabilities

Beyond the journal framework, several additions reinforce the same direction of more automation and better global-scale support.

• Agentic bank reconciliation. Reconciliation is one of the more repetitive parts of the close. AI agents take on more of the matching, and finance teams can preview matching results before posting, review exceptions, and make corrections without creating reversal entries. The result is fewer errors and faster statement processing.
• Support for stocked items with project. Organizations that run project-based work alongside inventory get tighter handling between the two, which previously had to be managed more separately.
• Continued country and region coverage. Microsoft keeps extending localization and regulatory coverage, underpinning the broader goal of supporting global operations.

The Three Investment Areas

Microsoft organizes the release around three areas of investment. Each covers a distinct part of the Finance application, and understanding the distinction makes it easier to identify which updates are relevant to your operation.

Business Performance

The business performance suite brings analytics, planning, and insights together as an extensible solution on a single platform. The intent is to let teams continuously plan, act, and analyze their financial and operational data rather than treating those activities as separate, periodic exercises. The features here concentrate on business performance planning and business performance analytics.

For many organizations, planning and reporting live in tools that sit apart from the ERP, which means data has to be exported, reconciled, and refreshed by hand each cycle. Consolidating these functions on one platform reduces that friction and keeps the numbers used for planning aligned with the numbers in the system of record.

Core Financials

Core financials investments add enhancements to the financial capabilities most teams rely on every day. They strengthen end-to-end business processes across the ERP, increase automation, and improve reporting and analytics. A central theme is reducing the time it takes to complete the financial close, which remains one of the most visible measures of a finance team’s efficiency. The journal framework and accounting rules engine described above are among the most prominent core financials investments in this wave.

Globalization Studio

Customers in more than 210 countries and regions use Dynamics 365 Finance to meet local tax and regulatory requirements. Globalization Studio provides out-of-the-box localizations and continuous regulatory updates across multiple countries, regions, and languages, which means much of the work of staying compliant in a given market is handled within the platform rather than through custom development.

Through no-code and low-code services, it also allows customers and partners to automate complex tax and regulatory compliance scenarios and extend localizations with minimal effort. It is built to support modern, digitally driven regulatory models, such as real-time reporting and electronic invoicing mandates, and to keep pace with compliance requirements as they evolve worldwide. Microsoft’s strategic focus for this area includes:

• Expanding and modernizing global country and region coverage.
• Unifying tax determination, calculation, posting, and regulatory reporting.
• Increasing automation to reduce compliance effort and operational cost.
• Enabling flexible, extensible integration models.
• Improving scalability, maintainability, and reuse across regulatory configurations.

The combined effect is a platform designed to help organizations stay compliant as regulations change, while simplifying setup and supporting scalable global operations. Microsoft also maintains a searchable record of planned and released regulatory updates, which is useful for tracking what is coming for the specific countries you operate in.

Notes for Application Administrators

Not every feature in a release behaves the same way at rollout. Some reach users automatically, while others have to be turned on deliberately. Knowing which is which is an important part of planning a smooth adoption.

• User-impacting features enabled automatically. These are delivered to users without any action on your part, but they still merit a review by application administrators. Looking at them ahead of time supports orderly change management and helps the team onboard new capabilities without surprises. In the release plan, they are tagged “Users, automatically.”
• Features that must be enabled by administrators. These require an administrator, maker, or business analyst to enable or configure them before users can access them. Because they are off by default, they are easy to overlook unless someone reviews the plan and decides which ones to switch on. They are tagged “Users by admins, makers, or analysts.”

A practical step is to review the release plan against your current configuration, note which automatic features are arriving, and decide which optional features are worth enabling for your users.

---

---