Why Does My Calculated Tax Differ from My Collected Tax?

Overview

If you're reviewing a filing and notice that your calculated tax does not match your collected tax, you're not alone.

These two amounts are generated differently, and in certain situations, they may vary. This article explains:

• What each amount represents

• How your remittance amount is determined

• Why differences occur

• What to review if you notice variances

What’s the Difference?

Collected Tax

This is the amount charged to your customer at checkout through your ecommerce platform (for example, Shopify).

It depends on your platform’s:

• Tax collection settings

• Product tax configuration

• Applied exemptions

• Discount treatment

• Marketplace handling

Calculated Tax

This is the tax liability determined based on:

• State and local tax rates

• Sourcing rules (origin or destination-based)

• Product taxability

• Nexus configuration

• Applied discounts

This represents what tax authorities require based on the transaction details.

How Is the Filing Amount Determined?

Your remittance depends on your configuration.

Default Filing Behavior (Compliance-First)

By default, Kintsugi files the higher of calculated or collected tax.

This approach helps ensure you do not under-remit tax if:

• Tax was not collected properly at checkout

• A product was misconfigured

• A taxable transaction was treated as non-taxable

“File Only What You've Collected” Setting

If you enable this option under:

Configuration → Settings

Your filings will reflect only the amount collected at checkout — even if calculated tax is higher.

Please note: If tax should have been collected but was not, filing only collected amounts may increase audit exposure.

The "Discrepancy" Myth: Why Kintsugi and Shopify Totals May Differ

Seeing a different number in Kintsugi than in your Shopify dashboard? This is usually a sign that everything is working correctly — not an error. A higher number in Kintsugi often means our system caught transactions that would have caused you to under-report, protecting you from back taxes and penalties.

The Top 3 Reasons for Differences

1. Late-Syncing Transactions

A transaction made late on the last day of the month may miss Shopify's internal reporting cutoff — but Kintsugi picks it up the next morning and includes it in your next filing. These "stragglers" are intentionally captured so nothing falls through the cracks.

2. Shipping vs. Billing Address

Shopify may default to a customer's billing address in its reports. Tax nexus, however, is almost always determined by where an order is shipped. Kintsugi re-categorizes transactions by shipping destination to make sure you're filing with the correct state.

3. Gross vs. Taxable Sales

Kintsugi accounts for adjustments, manual entries, and tax-exempt items that may be toggled differently — or not reflected at all — in your Shopify view. This makes the two totals look different, but Kintsugi's figure is the tax-accurate one.

PRO TIP: Check for prior period adjustments

Before approving a filing, look for any Prior Period Adjustments. If a transaction was missed in January, you'll see it appear in February's filing. This is not a duplication or an error — it's Kintsugi keeping your books accurate and up to date.

Common Reasons for Differences

Below are the most common causes of calculated and collected tax variances.

1. Discounts

Discounts reduce the taxable base. If your ecommerce platform and tax calculations apply discount logic differently, this may create small differences.

2. Product Tax Configuration

If a product is marked non-taxable in your ecommerce platform but taxable under state rules, calculated tax may be higher than collected tax.

3. Nexus Alignment

If nexus is enabled for a state, but tax collection is not properly enabled in your ecommerce platform, tax may not be collected at checkout even though tax is due.

4. Exemptions

For read-only integrations, exemptions must be configured in your ecommerce platform.

If an exemption is not properly applied:

• Tax may not be collected

• Or calculated tax may differ from collected tax

5. Marketplace Transactions

If a marketplace collects and remits tax on your behalf, treatment may differ from direct sales.

What If No Tax Was Collected, But Tax Was Remitted?

If:

• Collected tax shows $0

• Calculated tax exists

• And your filing is based on calculated tax

This means the transaction was taxable based on jurisdictional rules, but tax was not collected at checkout.

In this case, the remitted amount may be paid out-of-pocket to remain compliant.

To prevent this going forward, review your ecommerce platform’s tax collection settings and product configuration.

Does This Mean Something Is Misconfigured?

Not necessarily.

Variances can result from:

• Discount logic

• Rounding differences

• Platform tax overrides

• Product tax category alignment

• Exemption handling

If discrepancies are large or recurring, reviewing your configuration is recommended.

How to Reduce Future Variances

We recommend reviewing:

• Tax collection settings in your ecommerce platform

• Product tax categories

• Nexus configuration

• Exemption setup

• Discount application rules

Aligning these settings helps ensure consistency between calculated and collected tax.

Key Takeaway

Differences between calculated and collected tax are typically caused by platform configuration or checkout settings — not system errors.

Understanding your filing configuration and reviewing your ecommerce tax setup will help ensure accurate and consistent remittance.

Need Help?

For further concerns, we're always here to help. If you'd like help reviewing a specific filing period, please share the state and month in question, just reach out to us using the chat in the bottom right corner of your screen and our team can take a closer look.