- Feature
- Multi-element revenue allocation (MERA) termination adjustment
- Availability
- Preview from September 2026; general availability planned for April 2027
- Industry focus
- Software-as-a-service and subscription businesses
For a SaaS company, revenue recognition is not a back-office detail. It is the number investors watch. Contracts commonly bundle software subscriptions, implementation services, training and support, each recognized on a different pattern. When a customer terminates early, the accounting has to unwind correctly, and that is where many revenue teams still rely on spreadsheets.
The industry challenge
Under revenue standards such as IFRS 15 and ASC 606, the transaction price of a multi-element contract is allocated across performance obligations, usually in proportion to standalone selling prices (SSP). Dynamics 365 Finance supports this through subscription billing and multi-element revenue allocation.
Terminations complicate things. If a customer ends a three-year contract after eighteen months, the remaining deferred revenue must be dealt with, any credit given to the customer must be allocated sensibly across the elements, and the revenue recognized so far may need adjusting. When the system does not apply allocation logic to terminations, revenue accountants calculate adjustments by hand, post manual journals and leave deferred revenue balances that need explaining at quarter end.
As churn, downgrades and renegotiations increase, that manual effort grows quickly, and so does the audit risk.
What Microsoft is delivering
Finance 10.0.49 introduces, in preview, MERA termination adjustment for subscription billing. When a contract is terminated, with or without a credit, MERA logic is applied so that remaining deferred revenue is cleared. Credits are allocated across elements based on SSP, and terminations without a credit generate adjustment entries.
The preview became available from September 2026, and Microsoft plans general availability for April 2027.
Where the value shows up
| Business area | Impact |
|---|---|
| Revenue accounting | Terminations follow the same allocation logic as the original contract |
| Deferred revenue | Remaining balances are cleared on termination instead of lingering |
| Close speed | Fewer manual calculations and journals at quarter end |
| Audit | A consistent, system-driven approach to termination accounting |
| Commercial flexibility | Finance can support early exits and credits without a spreadsheet for each case |
A worked scenario
(An illustrative example.) A B2B SaaS provider sells a bundle of platform subscription, onboarding services and premium support. A customer acquired by a competitor terminates after 14 months of a 36-month term, and the account team agrees a partial credit.
Today, the revenue accountant would work out the allocation of that credit across the three elements in a spreadsheet, post journals and document the reasoning. In a sandbox using the preview, the accountant processes the termination with the credit; the system allocates it by SSP and clears the remaining deferred revenue. The team compares the result with their manual method to validate it before planning production use after general availability.
Adoption considerations
- Treat it as a preview. Test thoroughly in a sandbox; plan production use around general availability.
- Check SSP data. Allocation depends on reliable standalone selling prices. Review them before relying on automated results.
- Involve technical accounting. Confirm that the system's approach matches your accounting policies and auditor expectations.
- Map commercial scenarios. List your common termination types: full, partial, with credit, without credit. Test each one.
- Plan the transition. Decide how terminations processed manually before adoption will be documented and reconciled.
The bottom line
In subscription businesses, terminations are routine, but their accounting has often been anything but. Applying multi-element allocation logic to terminations brings consistency and automation to one of the hardest parts of SaaS revenue accounting. It is still in preview, so now is the time to test it against real contracts. An experienced Dynamics 365 Finance adviser can help you validate the approach before general availability.
Sources: Microsoft: What's new or changed in Dynamics 365 Finance 10.0.49 · [Microsoft 365 roadmap item RM576638]()