For finance teams, the proposed benefit is straightforward: bring more complicated duty calculations into Business Central rather than relying on manual adjustments or external calculations. That is Microsoft’s intended outcome, however—not a measured reduction in accounting work.
What Microsoft is planning
The roadmap describes calculations using different tax bases, thresholds, quantities, percentages, or combinations of those factors. It names three supported approaches:
- Specific
- Ad valorem
- Hybrid
The listed deployment scope is the web platform in Worldwide (Standard Multi-Tenant) environments, covering preview and general-availability release stages. The announcement does not establish on-premises availability, an exact delivery day, or a required Business Central version.
The important boundary is between naming a calculation method and documenting how it works. The feature description does not supply formulas, configuration screens, calculation order, or details about rounding, exemptions, and caps. Consequently, it is too early to turn this announcement into a reliable setup guide—or declare that it handles a particular jurisdiction’s rules.
This builds on an existing excise-tax framework
Business Central already has documented excise-tax configuration. Microsoft Learn’s Set up excise tax guidance describes tax bases including weight, sugar content, active content, volume, pure alcohol (ABV), and quantity. Administrators configure tax types, duty rates, and the relevant items or fixed assets before calculating duties. These are existing framework capabilities, not a confirmed specification for the forthcoming calculation methods.
There is also a separate development worth keeping distinct. Microsoft’s update 29.0 documentation lists Calculate multiple excise duties per item, roadmap ID 573306, as a public-preview feature in Business Central’s 2026 release wave 2. That is not item 573614. Supporting several duties on an item and expanding the methods used to calculate duties are related improvements, but they are not interchangeable announcements.
Microsoft’s current setup documentation adds a practical upgrade detail: version 29 and later move existing item excise-tax configuration to the Excise Taxes page automatically, without requiring users to recreate it. It also distinguishes items, which can have multiple excise-tax types, from fixed assets, which can have only one. Neither fact establishes that the newly announced complex calculation methods are available in version 29.
What finance and IT teams should do next
The sensible preparation is a requirements review, not a production configuration change.
For organizations considering this feature, our recommendation is to assemble representative calculations and expected results before evaluating a preview:
- Identify external calculations. Record where staff currently use spreadsheets, manual adjustments, or other systems.
- Document the inputs. Include the quantities, percentages, tax bases, and threshold conditions each scenario needs.
- Define acceptance cases. Include ordinary transactions and boundary cases around thresholds or rate changes.
- Keep deployment questions separate. Confirm the eventual version, enablement requirements, and environment eligibility when Microsoft publishes implementation guidance.
This is preparation advice, not a Microsoft-published procedure for item 573614.
The promising part of this announcement is its focus on calculation flexibility rather than merely adding another tax field. The unanswered question is how much of an organization’s real-world duty logic that flexibility will cover. Until the detailed behavior is documented and tested, treat this as a feature to evaluate—not a reason to retire existing calculation controls.