Microsoft Dynamics 365 Finance and Operations version 10.0.49 is a major release and one that demands closer attention than many teams typically give a quarterly update. Beyond the new features, 10.0.49 carries a significant deprecation in Global Inventory Accounting, closes off escape routes for teams still relying on older behavior across cash management and receivables, and makes a long list of features permanently mandatory. For customers, partners, and IT teams, the planning work required for 10.0.49 is heavier than a standard release, and the testing scope follows accordingly.
This article provides a practical overview of what is included in 10.0.49, what is being deprecated or made mandatory, and what teams should consider validating before production deployment.
10.0.49 Release Overview
Dynamics 365 Finance and Operations 10.0.49 requires more deliberate planning than a routine quarterly update. Here are the key things your team should know going into this release.
Features becoming mandatory:
- Customer and vendor netting
- Cash position inquiry and cash control
- Advanced bank reconciliation behaviors, including automatic clearing of bridged transactions and use of the latest exchange rate to post bank transactions
- Exchange rate type enhancement for AP/AR foreign currency revaluation
- Maturity date validation for postdated checks
Features being deprecated:
- Global Inventory Accounting: end of support July 1, 2027
- RSAT support for on-premises deployments: ends May 15, 2027
- Asset Management mobile app: Microsoft distribution ends November 30, 2026
- Data Integrator templates for Field Service integration: no longer available after February 28, 2027
For organizations upgrading to 10.0.49, understanding where changes occur and validating the right areas is critical. The mandatory feature set in particular deserves targeted validation against complete business processes, not just confirmation that the toggle is gone.
Release Availability and Timeline
Dynamics 365 Finance and Operations version 10.0.49 follows Microsoft's standard , with staged availability to support preview, validation, and controlled rollout. Under this model, Microsoft releases four service updates annually in February, April, July, and October. Customers must take a minimum of two updates per year and can pause a maximum of one consecutive update. For answers to common questions about how this release process works, see the .
The availability timeline for 10.0.49 is:
- Preview of release: July 2026
- General availability (self-update): September 11, 2026
- First autoupdate (production): October 2, 2026
- Second autoupdate window: November 1, 2026
- End of service: May 21, 2027
Organizations that have not already configured their update window should do so in Lifecycle Services before autoupdate begins. Teams that need additional validation time should consider self-updating to 10.0.49 before the October autoupdate window to maximize their testing runway.
Learn more about .
Platform Updates in 10.0.49
The 10.0.49 platform update applies across all Dynamics 365 Finance and Operations applications and forms the technical foundation for the release.
Key platform themes include:
- Performance and reliability improvements
- Security, compliance, and governance enhancements
- Lifecycle Services and monitoring refinements
- Ongoing alignment with modern extensibility and integration models
Although platform updates are not always visible to users, they influence system behavior during upgrades and can impact integrations, background processing, and data handling.
Platform areas to validate:
- Batch jobs and long-running processes
- System performance during peak operational scenarios
- Integrations and inbound or outbound data flows
- Customizations and extensions following the upgrade
Finance Application Updates
10.0.49 delivers meaningful functional additions across Finance, with the most significant changes concentrated in budgeting, cash and bank management, and accounts receivable.
Budgeting
Microsoft adds several enhancements that improve how budget-controlled documents behave across fiscal periods and workflows.
- Automatic accounting date advancement ensures that purchase requisitions and purchase orders with workflow enabled automatically shift their accounting date when a fiscal period is closed or put on hold mid-workflow, preventing process failures during long-running approvals.
- Detect corruption in budget control tracking adds a diagnostic capability to identify orphaned budget tracking records and broken relieving relationships before repair, giving finance teams a way to confirm data integrity before the repair process runs.
- Automatically post general budget reservations using workflow removes the manual posting step after workflow approval, reducing delays for organizations processing budget reservations at scale.
- Option to exclude closing period transactions in the Outstanding encumbrance report gives public sector and budget-controlled organizations a cleaner year-end view of open commitments.
- Preserve budget check indicators for partially consumed and finalized documents ensures that budget check indicators remain visible on partially invoiced or consumed purchase orders after finalization, maintaining visibility into documents that have already affected the budget.
Budgeting areas to validate:
- Purchase requisition and purchase order workflows that span fiscal period boundaries
- Budget reservation posting and workflow approval sequences
- Year-end encumbrance reports and opening balance carry-forwards
- Budget check indicator visibility after partial invoicing and finalization
Cash and Bank Management
Cash and bank management receives several additions in 10.0.49, alongside a large set of features that become mandatory. Teams with custom settlement logic or bank integrations should treat this area as a priority.
New capabilities include:
- Delay settlement from journal posting allows payment journals to post successfully even when the related settlement cannot be completed at the time of posting, queuing settlement for background processing or manual completion.
- Preview automatic bank reconciliation matching results lets users review and approve reconciliation matching rule results before transactions are posted and marked as matched.
- Clear bridged customer payments automatically during bank reconciliation enables clearing of bridged transactions from centralized vendor payments through the bank reconciliation framework.
- Improved performance for selecting bridge transactions during the bank clearance process introduces filtering by bank account, counterparty, payment reference, check number, and date range before transactions load, reducing retrieval time in high-volume environments.
Cash and bank management areas to validate:
- Payment journal posting behavior, particularly for settlements that previously failed
- Bank reconciliation matching rule results and approval flows
- Bridged transaction clearing for centralized payment scenarios
- Bridge transaction filtering and performance in environments with large payment volumes
Accounts Receivable
- Line level prepayment flow introduces a new parameter on the Accounts Receivable parameters page that determines whether prepayments are calculated at the header level or line level when the Prepayment customer invoice feature is active.
Accounts receivable areas to validate:
- Prepayment calculations across header-level and line-level scenarios
- Customer settlement sequences, particularly those affected by mandatory netting and postdated check features
Fixed Assets
- Reporting currency handling for fixed asset splits maintains consistent reporting currency values when a fixed asset is split, carrying forward the applicable exchange rate information from the original asset.
- Fixed assets reporting currency adjustment (preview) enables generation, review, and posting of reporting currency adjustment entries for fixed assets.
- Populate reporting currency amounts for fixed asset income tax depreciation (India) calculates and displays reporting currency amounts for transactions generated through the depreciation proposal.
Electronic Reporting
Microsoft extends ER capabilities in 10.0.49 with several additions turned on by default:
- GS1 barcode formats: ER now generates GS1-128, GS1 DataMatrix, and GS1 QR Code natively without external libraries.
- DIV and MOD functions add integer division and remainder operations to the ER formula language, supporting pagination, packaging quantities, and check-digit calculations.
- Number of copies applied for ER destinations in Print management ensures that ER documents honor the copies count configured in Print management, as well as ad-hoc print dialogs.
- Optimize memory consumption for large ER executions reduces peak memory usage during reporting engine execution.
- Enhanced validation management for ER configurations enables validation of multiple configuration versions in a single operation with persistent validation history.
Regulatory
- Electronic reporting of transactions for France (e-Reporting) supports France's continuous transaction control reform, enabling companies to report business transactions to French tax authorities through an approved intermediary platform.
Features Becoming Mandatory in 10.0.49
The most operationally significant aspect of 10.0.49 for many teams is the number of features that become mandatory. These features can no longer be turned off in Feature management. If any custom logic, integrations, or configurations were built to work around these behaviors, those workarounds are no longer viable after this release.
The mandatory features span accounts payable, accounts receivable, and cash and bank management. Notable mandatory changes include:
- Customer and vendor netting
- Cash position inquiry and cash control
- Advanced bank reconciliation behaviors including automatic clearing of bridged transactions, enabling posting of new transactions in bank reconciliation, and use of the latest exchange rate to post bank transactions
- Exchange rate type enhancement for AP/AR foreign currency revaluation
- Maturity date validation for postdated checks
- Several regional features for Poland, Italy, Norway, Eastern Europe, and Brazil
Areas to validate before mandatory enforcement:
- Settlement logic across AR and AP, particularly for netting scenarios
- Bank reconciliation flows from statement import through posting
- Foreign currency revaluation calculations and exchange rate sourcing
- Regional tax and payment configurations where applicable
Features Removed from Feature Management
The following capabilities are now permanently embedded in Finance and no longer appear in Feature management. The off-switch is gone, but the functionality remains active:
- Budget register entries page performance enhancement
- Encumbrance reconciliation
- Calculate origin amount for sales tax specification by ledger transaction report
- Enable delayed tax calculation on journal
- Several Electronic Reporting caching and validation features
Teams should confirm that any testing or support documentation referencing these as toggleable features is updated accordingly.
Global Inventory Accounting Is Being Retired
The largest deprecation in 10.0.49 is Global Inventory Accounting. Microsoft has announced that GIA will reach end of support on July 1, 2027, and is being replaced by a new multi-ledger costing capability.
For organizations actively using GIA, this is not a feature-toggle exercise. A transition will affect inventory valuation and cost-of-goods-sold reporting, parallel accounting representations, reconciliation between inventory and the general ledger, historical reporting and opening balances, and any integrations or custom reporting built against GIA data.
If GIA is installed but unused, it should be excluded from future designs. If it is running in production, documentation of valuation models, reporting dependencies, and reconciliation requirements should begin now. July 2027 sounds distant until budgeting, design, testing, and audit approval enter the conversation.
Additional Deprecations Worth Tracking
Several nearby deprecations should be included in the same planning review as 10.0.49:
- Copilot sidecar follow-up questions: The preview capability that allowed follow-up questions in the Finance and Operations Copilot sidecar has been removed with no direct replacement. Any training materials, demos, or processes that reference this capability should be updated.
- Asset Management mobile app: Microsoft maintenance and distribution ends November 30, 2026. Existing installations can continue, but the app becomes an open-source sample, shifting ongoing maintenance responsibility to customers and partners.
- Data Integrator templates for Field Service integration: No longer available after February 28, 2027.
- RSAT support for on-premises deployments: Ends May 15, 2027.
Release Waves Are Ending: What That Means for Your Team
As 10.0.49 rolls out, Microsoft has made another significant announcement that directly affects how D365 teams plan and validate updates. Starting in September 2026, Dynamics 365, Power Platform, and Dataverse roadmap content is moving to the , replacing the twice-yearly release wave 1 and release wave 2 model with continuous publishing. New capabilities will be disclosed as plans are committed rather than held until the next scheduled wave, and Release Planner retires on November 15, 2026.
It is worth noting what is not changing: product release and deployment schedules remain in place, Message Center continues to deliver tenant-specific change notifications, and Microsoft Learn remains the home for product documentation. The AI at Work roadmap supports planning through filtered views, CSV exports, RSS subscriptions, and the Release Communications MCP Server for teams that want to query roadmap data directly into their own tools.
For validation teams, the practical impact is significant. Release waves gave organizations a fixed moment twice a year to gather stakeholders, assess impact, and plan testing. That checkpoint is gone. Teams now need a continuous process for monitoring the roadmap, triaging changes by business risk, and triggering validation when updates reach their environments.
We covered exactly how to build that process in a recent post:
Learn More About Testing Dynamics 365 Finance and Operations
As Dynamics 365 Finance and Operations continues to evolve under Microsoft's One Version model, testing plays a critical role in reducing upgrade risk and maintaining confidence in core business processes. With mandatory features across cash management and receivables, a major GIA deprecation, and a dense set of new budgeting and ER capabilities, the testing scope for 10.0.49 is broader than a typical quarterly update. Understanding where change occurs and validating complete end-to-end processes helps organizations adopt new releases with less disruption.
specializes in Dynamics 365 testing and supports organizations with upgrade readiness, release planning, and ongoing quality efforts. is purpose-built for Dynamics 365 Finance and Operations test cycles, validating complete end-to-end processes across user workflows, APIs, integrations, and data. For teams still on RSAT, Horizon offers one-click import and a familiar authoring experience, making it the lowest-friction replacement before .