D365 F&O 10.0.49: What Becomes Mandatory, and What You Can No Longer Turn Off

The 10.0.49 release notes are out, and the part that matters most to finance teams is buried in the feature lists rather than the headline announcements.

Thirty-four features become mandatory in this release. Four more are removed from Feature management altogether and become permanent components of the product. If your team has intentionally kept any of these switched off — because of a customization, an ISV conflict, or a process decision made two years ago — they will be enabled automatically, and nobody will ask you first.

Here is the full picture, so you do not have to click through the release notes yourself.

Key dates

• Preview: July 2026
• GA (self-update): September 2026
• GA (auto-update): October 2026
• Build: 10.0.2790

Your specific auto-update window is configured per environment in Lifecycle Services, so the October date is a guideline rather than your date. Check LCS rather than assuming.

One thing worth confirming early: this release is only optional if you are current. If you skipped 10.0.48, 10.0.49 is mandatory for you.

What's new

Budgeting — the major focus area this cycle

Budgeting gets the most substantial attention in 10.0.49:

• Accounting dates now advance automatically for budget-controlled requisitions and purchase orders when approval spills into a closed period
• Corruption detection in budget control tracking, so orphaned records surface before repairs rather than after
• General budget reservations post automatically after workflow approval, with an option to exclude closing-period transactions from outstanding encumbrance reports
• Budget check indicators are preserved after partial consumption and finalization

If your close process involves approvals that routinely straddle period boundaries, the first item alone is worth testing properly.

Cash and bank management

• Delayed settlement from journal posting, which lets payment journals post while settlements are queued separately
• Previews of automatic reconciliation matching results before posting
• Automatic clearing of bridged customer payments, plus faster bridge transaction selection during bank clearance

Other modules

• Line-level prepayment flow in accounts receivable
• Reporting currency adjustments and split handling in fixed assets
• Multi-element revenue allocation termination adjustments in subscription billing

Enabled by default — but still yours to disable

These arrive switched on. You can turn them off manually if they conflict with how you work.

Cash and bank management: bank FX revaluation automation, optimized auto-settlement, batch mode for Bank CODA transfer, bank account lifecycle management, time zone alignment in modern reconciliation, automatic vendor account matching, and account ID search on manual payment journals.

Everything else: payee names on payment information, AR/AP FX revaluation automation, settle with priority in AP, the non-retrievable purchase orders form in budgeting, and tax-exempt number validation on the Create Customer dialog.

Mandatory — no toggle

These cannot be disabled. This is the list to test against.

Cash and bank management: check number validation, cash position inquiry, cash control, exchange rate type handling, and advanced bank reconciliation behaviors.

Accounts receivable: customer and vendor netting, postdated check handling, and country-specific items for Italy, Norway, Poland, Brazil, and Eastern Europe.

Tax: batch tax hierarchy sync, VAT register date calculation, and reverse charge inheritance.

Additional mandatory updates land in accounts payable, budgeting, and general ledger.

Removed from Feature management entirely

Four features stop being features and become part of the product:

• Budget register entries page performance
• Encumbrance reconciliation
• Origin amount for sales tax specification report
• Delayed tax calculation on journal

What we would do before the update window

1. Confirm whether this release is optional for you. It is mandatory if you skipped 10.0.48.
2. Run a Feature management diff against the lists above. The question is not what changed in the product — it is what changed in your environment.
3. Regression test by module, in this order: budgeting, bank reconciliation, payment settlement, then tax.
4. Re-verify the integrations that break quietly — payment file generation, bank statement import, and tax reporting.
5. Validate customizations and ISV solutions against the platform update.
6. Schedule your update window around your financial close calendar, not around Microsoft's default dates. This is the step teams skip, and it is the one that turns a routine update into a bad week.

The part most teams get wrong

The instinct is to test all 34 mandatory features. That is the wrong shape of effort.

Most of those 34 will change nothing at all in your environment, because you were not using the affected process, or because you had already adopted the behavior. A handful will genuinely change how your system behaves — and those are almost always in the areas where someone made a deliberate configuration decision years ago that nobody has revisited since.

The work is identifying which handful. Everything after that is straightforward.

---

If you would rather not do that diff yourself, we can run it against your environment and hand you a targeted testing list instead of a 34-item checklist. It takes about half a day.

We also do a free Demo — bring any questions you have, whether it is this update or another pain point in your environment, and we will walk through what it actually takes to resolve it.