In development MRC 574128

Dynamics 365 Business Central: Ecommerce - [US] Match Shopify tax lines to tax jurisdictions

Business Value Reduce repetitive tax setup when you import Shopify orders that contain multiple United States tax jurisdictions. Shopify Tax Matching suggests how free-text tax lines map to configured tax jurisdictions and keeps you in control of exceptions before you create sale

Dynamics 365 Business Central 03 Horizon04 Security

DIGITAL SKILL WORKS LTD / 12 PANES

GA / disclosure April CY2027
Preview October CY2026
Platforms Web

What it is

Dynamics 365 Business Central: Ecommerce - [US] Match Shopify tax lines to tax jurisdictions is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: In development.

What it does

Business Value Reduce repetitive tax setup when you import Shopify orders that contain multiple United States tax jurisdictions. Shopify Tax Matching suggests how free-text tax lines map to configured tax jurisdictions and keeps you in control of exceptions before you create sales documents. Details The Shopify Tax Matching capability is available in public preview for organizations in the United States that use the Shopify connector. When standard tax-area mapping doesn't resolve an imported order, the capability uses AI to suggest tax jurisdictions based on Shopify tax-line titles and rates, configured tax jurisdictions, and limited ship-to location information. You can review each suggestion, confidence level, explanation, and rate before approving the final mapping. Configure which matches require review and whether the capability can create missing tax jurisdictions and tax areas. Unidentified jurisdictions and rate differences always require review. Shopify Tax Matching maps imported tax descriptions to tax setup. It doesn't calculate tax, determine tax liability, file tax returns, or replace professional tax advice.

Why you should care

Board

Track as Horizon signal; decide whether it changes Wave 0 priority or stays on the watchlist.

CISO

Confirm identity, data access, and overshare exposure before enabling for broad cohorts.

CFO

Map licence or consumption impact to the frozen value case; avoid seat spray.

Adoption

Pilot with a named cohort and measure changed work, not vanity clicks.

Suggested action

Wave 0 first: Security → GRC → Cost & Value → Licence → Adoption. Add to Horizon watchlist with an owner. Pilot only after Steady controls for the affected surface are in place.

12 Panes: 03 Horizon · 04 Security

Communication needed

  • Security: Assess exposure, Conditional Access, and agent/tool permissions.
  • GRC: Update AI/agent register and evidence path; confirm DPIA triggers if personal data is in scope.
  • FinOps: Forecast seat or credit impact; align to frozen value case.
  • Adoption: Plan cohort messaging, clinics, and success measures.
  • Comms: One story for board and staff — what changes, what does not, who owns risk.

Benefits

  • May improve productivity on a specific Microsoft 365 surface when permissions and data quality allow.
  • Roadmap visibility helps Horizon planning without guessing dates.

Risks

  • Status and dates change; treat MRC as directional, not a contract.
  • Enabling without Steady controls can amplify overshare or cost leakage.
  • Preview or rolling features can change behaviour; fence exploration on Pane 12 Frontier.

Source

Microsoft Release Communications / Microsoft 365 Roadmap (AI at Work). Content is subject to Microsoft API Terms of Use. Dates and status change; verify in the official roadmap before acting.

Back to roadmap intel