96

This idea is created by Tax Calculation service product team to understand the market requirements for Microsoft to build an external interface with tax rate providers for countries with complex tax jurisdictions and tax rates.


 


Please vote for this idea if you need this feature in your project.


 


It will be much appreciated if you can post a comment to share why you need this feature and what the current pain points are in your business in this area.


 


Thanks


Eric


 

Category: Tax
STATUS DETAILS
Completed
Ideas Administrator

The functionality is available from the 10.0.39 version: Connect to an external tax solution provider via the Universal Tax Rate API - Finance | Dynamics 365 | Microsoft Learn

Comments

E

I've been implementing sales tax in the US, and this issue always comes up. We ended up pointing to ISV, however, the product could facilitate this as MS is investing in the tax calculation service.

Category: Tax

E

I think this is a regional requirement for the USA.Other than the USA that has many, and frequently changing rates, no other country I ever implemented in had the same scenario and the same business need.For tax rates that may change (maybe) once every 5 years, there is no need for online rate provider.I implemented so far VAT/Sales tax in North America, Europe, South East Asia, and ANZ - none of them had any requirement coming even close to requiring a "rate provider"

Category: Tax

E

This would be a huge benefit for us (Patagonia). We use an ISV solution for taxes in North America. It's been painful for years. The ISV we use has a solid SaaS platform for tax calculations, but they aren't experts at integrating that into D365. We've had to reverse engineer and help fix various aspects of their solution over the last 4 years. Things are somewhat stable (albeit not that performant) in HQ, but we're still struggling with retail.For example, in retail, buy online and return in store does not work when returning in a different state. The ISV is just getting a fix to this in the next month or two, after we reported it a couple years ago. We as a company have to work with the IRS to consistently fix these tax issues and it costs us a LOT of money to cover/correct the differences. Multiple headcount on our accounting team, unhappy business users, incorrect taxes for customers, and a boatload of BA/Dev time to try to fix things. Not only that, but we can't even use offline mode for mPOS due to issues in the ISV's solution. Same applies to moving to CommerceSDK - we're stuck on RetailSDK until the ISV supports the new packaging model.Requiring an ISV focused on providing tax services to be experts in D365's sprawling infrastructure and development ALM to get a vaguely workable omnichannel solution is a black eye on D365 F&O and Commerce. Let the SaaS companies focus on providing tax solutions. Give them (or partners) an easy way to hook into the tax engine.

Category: Tax