Sales tax setup in Dynamics 365 Finance

US-style sales tax is fundamentally different from European-style VAT. Where VAT is harmonised across countries with standard rates, sales tax in the US is fragmented — 45 states, thousands of local jurisdictions (county, city, special districts), each with their own rates, taxable categories, and exemptions. Dynamics 365 Finance supports US sales tax natively and integrates with Avalara and Vertex for the deep complexity most US operations face.

The F&O native engine. The native sales tax engine works through:

• Sales tax authorities — the regulator (state, county, city). Each has a tax-payment recipient configured.
• Tax codes — specific rates for specific authorities. e.g. NY State 4%, NYC City 4.5%, NY MCTD 0.375%.
• Tax groups — bundles of tax codes that combine for a given customer / location. A New York City customer gets the NY State + NYC + MCTD group.
• Item sales tax groups — bundles of tax codes that apply to a given item. Most goods are taxable; some (groceries, prescription drugs in many states) are exempt.
• Intersection — the customer's tax group × the item's item tax group = which tax codes actually apply.
• Settlement periods — when each authority's tax is settled and remitted.

The challenge of US sales tax. Sourcing — which jurisdiction applies — depends on whether the state uses origin-based sourcing (where the seller is located) or destination-based sourcing (where the customer receives). Most states are destination-based; this means a single seller must compute tax based on the customer's address, with potential exposure across thousands of jurisdictions.

Nexus. A seller has tax nexus in a state — and must collect tax there — if they have physical presence, economic presence (revenue / transaction thresholds, post-South Dakota v Wayfair 2018), or specific business activities. Determining nexus is a tax-advisory question; F&O collects tax in jurisdictions configured to be in scope.

Why Avalara / Vertex. The native engine handles tax computation if you maintain the rates and rules manually. For a seller selling into 5 states with 10 jurisdictions, manual maintenance is feasible. For a seller selling nationwide, with rates that change frequently, with product-specific taxability rules, and with exemption certificate management — manual maintenance is infeasible. Avalara and Vertex are tax-engine SaaS platforms that maintain the rates / rules and provide API-level tax computation.

The integration pattern with Avalara / Vertex.

1. F&O has a configured Avalara / Vertex connector.
2. At sales-order creation (and re-validation at posting), F&O calls Avalara / Vertex with the transaction details: ship-to address, ship-from address, products, customer category, exemption certificate ID.
3. Avalara / Vertex returns the tax computation: which authorities, which rates, which exemptions, total tax.
4. F&O stores the tax computation on the transaction.
5. At posting, the tax posts to the standard sales tax accounts but with the Avalara / Vertex breakdown.
6. Periodic returns: Avalara / Vertex can file directly to authorities (Avalara Returns) or provide return-prep data for the seller's tax team.

Exemption certificates. Many B2B transactions are exempt — wholesalers, manufacturers, resellers, non-profits, government. Exemption certificates document the buyer's exempt status. Avalara CertCapture / Vertex Returns / similar tools manage the certificate lifecycle — capture, verification, expiry, renewal, audit.

Special rules.

• Tax holidays — states declare temporary exemptions for specific products in specific periods (back-to-school, hurricane preparedness).
• Tax-included pricing — some B2C scenarios price tax-inclusive; F&O supports though most B2B is tax-exclusive.
• Marketplaces — sellers via Amazon / eBay / Walmart marketplaces typically have the marketplace collect tax on their behalf; the seller's F&O records the marketplace-collected tax separately.
• Digital goods — taxability varies wildly by state for digital products and services.

Compliance and audits. US sales tax audits are rigorous. Documentation requirements:

• Every taxable transaction with full breakdown.
• Every exempt transaction with the supporting certificate.
• Periodic returns filed on time per authority.
• Reconciliation between collected tax and paid tax.

Operational reality. US-based F&O implementations almost always integrate with Avalara or Vertex. The native engine is functional but isn't built for nationwide US complexity at scale. Plan for the integration from day one.