Skip to main content

sales-tax-config

Copy--- id: sales-tax-configuration title: Sales Tax Configuration Guide sidebar_label: Sales Tax Configuration description: Comprehensive guide for configuring and managing sales tax across different sales channels and return scenarios. last_update: date: 2024-02-06 author: Matt Pendergraft​

Sales Tax Configuration Guide

Overview​

This guide explains how sales tax is handled across different sales channels and return scenarios. Understanding these concepts is crucial for proper tax reporting and reconciliation.

Key Concepts
  • Tax calculations occur at the line item level
  • Returns can create tax rate mismatches between stores
  • Web orders use different tax calculation methods than in-store orders

Basic Tax Structure​

Line Item Tax Details​

Each line item in ORDERDETAIL stores:

  • Individual tax amounts (tax1, tax2, tax3)
  • Tax definition ID (taxdefid)
  • Line total amount (linetot)

Store Tax Configuration​

Current implementation uses a 1:1 mapping:

Store ID = Tax Rate Code = Tax Definition ID
Example: Store 101 → Tax Rate 101 → Tax Definition 101
caution

This simple mapping system may need revision if more complex tax scenarios are required in the future.

Return Processing​

How Returns Affect Numbers​

When a return is processed:

  • ✅ Salesperson's sales volume is adjusted down
  • ❌ Store's sales volume remains unchanged
  • 💰 Customer receives exact tax amount from original purchase

Cross-Store Returns​

Returns processed at a different store than the original purchase create reporting complexities:

  1. Different tax rates between stores create reconciliation variances
  2. Original store information may be lost for non-taxed items
  3. Tax liability accounts require manual adjustments
Tax Rate Mismatches

Cross-store returns with different tax rates will create variances in tax reporting. These variances are expected and should be monitored.

Web Orders​

Tax Calculation Flow​

  1. Initial order:

    • Avalara calculates tax through Shopify
    • System uses these calculated values

  2. Order modifications:

    • System recalculates using ZIP code-based tax rates
    • Creates potential mismatch with Avalara

Reconciliation Options​

  • Generate report of modified web orders
  • Manually adjust values in Avalara
  • Best for low volume of changes

Option 2: Full Replacement​

  • Export complete ORDERDETAIL data for web sales
  • Replace Avalara data entirely
  • Provides better audit trail but requires more maintenance
Recommended Approach

For most scenarios, Option 1 (Manual Adjustment) is preferred due to:

  • Lower operational overhead
  • Reduced risk of data synchronization issues
  • Simpler implementation

Troubleshooting​

Finding Original Store Information​

To trace original store for returns:

orderdetail.taxctrlid → odreturns.pretaxctrl → orderdetail.branchid

Common Issues​

  1. Missing original store information for non-taxed items
  2. Tax rate mismatches between original and return stores
  3. Avalara/Shopify synchronization discrepancies

Additional Resources​

  • Contact technical support for assistance with tax definition setup
  • Review accounting documentation for G/L reconciliation procedures
  • Consult Avalara documentation for web order tax calculations
note

Always test tax configuration changes in a staging environment before applying to production.