Getting Started with Dynamic Tax

Dynamic tax is automatic tax collection that calculates the correct tax amount based on the shopper’s ZIP code, including state and local jurisdiction breakdowns. This helps you spend less time managing tax calculations manually while staying organized.

The feature uses Stripe’s tax API calculations powered by TaxJar. If you’d like to enable this in your account, contact Support at support@captura.io or connect with your CSM.

Once tax collection is enabled for your account:

1. In Workflow, go to Preferences > Tax Registrations

2. Add the jurisdictions where your studio collects tax.

This setup helps ensure orders are taxed correctly based on where shoppers are located.

You can access tax reporting in Workflow by navigating to:

Orders > Export > Tax Report

The report pulls directly from Stripe’s itemized export data. Because the information comes from Stripe’s API, report generation may take a little longer than other exports, especially during high-volume periods.

To ensure the most accurate reporting, we recommend waiting 2–3 business days before pulling reports that include very recent transactions.

The report includes a separate row for each tax jurisdiction, with details such as:

• jurisdiction_name — The name of the tax jurisdiction

• jurisdiction_level — The type of jurisdiction collecting the tax

• state_code — Two-letter ISO state or subdivision code

• country_code — Two-letter ISO country code

• filing_taxable_amount — Taxable amount in filing currency

• filing_non_taxable_amount — Non-taxable amount in filing currency

• filing_tax_amount — Tax collected for that jurisdiction

• subtotal — Combined taxable and non-taxable subtotal

• filing_total — Total amount including tax

• The filing_tax_amount column only reflects tax collected for that specific jurisdiction level.
  For example, a state-level entry includes only the state tax amount, not the total combined tax from county or city jurisdictions.

• Refunds are reflected based on the day they are processed.
  Example:

  • A $10 order placed on June 5 appears in reports covering June 5

  • If that same order is refunded on July 10, reports covering July 10 will show a -$10 adjustment

• Reports with an end date within the last week may show incomplete data while Stripe finalizes processing.