Share
ReportOur company is currently evaluating our approach to Sales and Use Tax within Dynamics 365 Finance, and I'm interested in hearing from organizations that have gone down either path.
We have nexus and sales activity in every U.S. state except Alaska and Hawaii, and we're evaluating whether to:
For those who chose the native D365 approach, I'd love to hear:
How many states/jurisdictions are you managing?
Given our nationwide footprint, I'm trying to understand where the practical tipping point is between "native D365 is sufficient" and "a tax engine becomes necessary."
Any lessons learned, regrets, cost considerations, or recommendations would be greatly appreciated.
Thanks
We have nexus and sales activity in every U.S. state except Alaska and Hawaii, and we're evaluating whether to:
- Configure and maintain Sales and Use Tax directly within D365 Finance
- Implement an ISV solution such as Avalara, Vertex, or another tax engine
For those who chose the native D365 approach, I'd love to hear:
How many states/jurisdictions are you managing?
- How much effort is required to maintain tax rates, jurisdictions, exemptions, and regulatory changes?
- Did you build internal processes for monitoring tax updates, or do you rely on a third-party rate service?
- How difficult is use tax management and reporting within D365?
- Have you experienced any audit challenges resulting from maintaining tax internally?
- Looking back, would you make the same decision again?
Given our nationwide footprint, I'm trying to understand where the practical tipping point is between "native D365 is sufficient" and "a tax engine becomes necessary."
Any lessons learned, regrets, cost considerations, or recommendations would be greatly appreciated.
Thanks
Categories:
I have the same question (0)
All responses (
Answers (
431
