Skip to content
Create account or Sign in
The Stripe Docs logo
/
Ask AI
Create accountSign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
APIs & SDKsHelp
Overview
Billing
OverviewAbout the Billing APIs
Subscriptions
Invoicing
Usage-based billing
Quotes
Customer management
Billing with other products
Revenue recovery
Automations
Scripts
Test your integration
Tax
Overview
Use Stripe Tax
Tax rates
Manage compliance
    Monitor your obligations
    Register
    File and Remit
    Import transactions
    Reporting
      Choose which report to use
      Reconcile reports
Reporting
Overview
Select a report
Configure reports
Reports for multiple accounts
Reports API
Revenue recognition
Data
Overview
Query business data
Analytics API
Sigma
Data Pipeline
Next generation of Data PipelineDatabase
Import external data
United States
English (United States)
  1. Home/
  2. Revenue/
  3. Manage compliance

Tax reporting

Learn about different reporting available in Stripe Tax.

Note

Log in or sign up for Stripe to enable Stripe Tax.

Stripe Tax provides reports of completed transactions, and it provides three different kinds of reports:

  1. Itemized exports show a detailed view of completed transactions for all locations, or a country or state.
  2. Summarized exports show an aggregated view of completed transactions by location.
  3. Location reports show an aggregated view of completed transactions for your registrations in the US and Canada.

To access these reports, go to the Locations page on the Dashboard. For help deciding which report to use, see Choose a report. To understand how numbers relate across reports, see Reconcile numbers across tax reports.

In May 2024, we updated jurisdictions in our location reports, itemized exports, and summarized exports for increased consistency across Stripe Tax. These changes include:

  • Splitting some jurisdictions into multiple sub-jurisdictions
  • Changing the names of some jurisdictions

As a result, jurisdiction names in transactions before and after May 2024 might not be identical.

Exports

Exports are CSV files that contain details of completed transactions where you enabled Stripe Tax.

Transactions appear in reports with a delay, typically within one day after completion.

Tax calculation amounts are recorded in the integration currency, which can differ from the presentment currency, the settlement currency, and the tax authority’s local filing currency. When using Prices, the integration currency is the currency of the Price object. When the integration currency differs from the filing currency, Stripe Tax converts amounts using available exchange rates at the time of the transaction to calculate the filing currency.

Export reports allow you to view amounts in both the integration and filing currencies.

Itemized exports

Itemized exports contain a detailed view of the line item level tax breakdown for every transaction. You might have multiple rows per line item if you have multiple jurisdictions imposing tax. This amount of detail can help with filing tax in jurisdictions that require more details in tax reports. Itemized exports contain cleansed addresses. In the US, the zip code might be only the 5-digit code, not the zip+4.

Itemized exports also contain non-taxable transactions. Non-taxable transactions are transactions in locations where you’re not registered, in locations that Stripe Tax doesn’t support, or locations where no jurisdiction imposes tax. You can filter out these transactions by selecting Exclude non-taxable transactions when exporting.

You can also filter transactions by jurisdiction before exporting. This helps reduce the size of large export files and eliminates the need to manually filter data after downloading. Jurisdiction filters are especially useful for EU OSS registrations (which include multiple countries) or regions with limited registration options. If you have only one registered jurisdiction, it’s automatically pre-selected. You can clear this selection to include transactions from all jurisdictions, including locations where you’re not registered.

Sub-state level reporting
United States

Use itemized exports for US states that require sub-state level reporting.

One Stop Shop (OSS)
EU

If you’ve registered for the One Stop Shop (OSS) within the European Union, you can download an itemized export of all your EU transactions. This export can assist in preparing your VAT OSS return. Itemized exports include non-taxable transactions (unless purposely excluded) and domestic transactions, which you don’t need to report in an OSS return. Make sure to filter out domestic transactions in your export.

Download example CSV file

Column Reference

The itemized export contains the following columns.

Column nameTypeExampleDescription
idTextin_1ABCdefGH123456, myOrder_123The container identifier. This ID represents the object that triggered the creation of the tax transaction.
tax_transaction_idTexttax_1ABCdefGH123456The unique identifier for the tax transaction.
reversal_original_tax_transaction_idTexttax_1XYZabcDE654321The ID of the original tax transaction that was reversed when transaction_type is reversal.
providerTextstripe, amazon, shopifyThe origin of the tax transaction. This will be stripe for Stripe transactions or the platform specified in an import for third-party transactions.
typeTextinvoice, payment_intent, checkoutThe type of object that triggered the creation of the tax transaction. Possible values are checkout, credit_note, external, invoice, payment_intent, and refund.
transaction_typeTexttransaction, reversalThe type of tax transaction. The transaction reverses an earlier transaction when transaction_type is reversal. Possible values are transaction and reversal.
transaction_date_utcDate and time (yyyy-MM-dd HH:mm:ss)2024-06-07 18:07:21The time at which the tax liability is assumed or reduced, in UTC.
tax_date_utcDate and time (yyyy-MM-dd HH:mm:ss)2024-06-07 18:07:21The time at which effective tax rules and rates were applied to the tax transaction, in UTC.
transaction_dateDate and time (yyyy-MM-dd HH:mm:ss)2024-06-07 11:07:21The time at which the tax liability is assumed or reduced, in the requested timezone.
tax_dateDate and time (yyyy-MM-dd HH:mm:ss)2024-06-07 11:07:21The time at which effective tax rules and rates were applied to the tax transaction, in the requested timezone.
effective_at_utcDate and time (yyyy-MM-dd HH:mm:ss)2024-06-07 18:07:21The time at which the tax transaction was created, in UTC.
payment_intent_idTextpi_1ABCdefGH123456The ID of the Payment Intent associated with the tax transaction.
line_item_idTextil_1ABCdefGH123456, myLineItem_123The ID of the line item associated with the tax transaction line item (for example, an invoice line item ID when the tax transaction type is invoice).
subtotalDecimal number10.00The line item subtotal amount. This includes taxes when tax_behavior is inclusive.
totalDecimal number10.80The line item total amount inclusive of tax.
tax_behaviorEither inclusive or exclusiveexclusiveTaxes are included in subtotal when tax_behavior is inclusive and excluded from subtotal when tax_behavior is exclusive.
tax_codeTexttxcd_10000000The product tax code associated with the tax transaction line item.
jurisdiction_nameTextCALIFORNIA, NEW YORKThe name of the jurisdiction that imposed the tax.
jurisdiction_levelEither country, state, county, city, or districtstate, countyThe level of the jurisdiction that imposed the tax.
country_codeText (ISO 3166-1 alpha-2)US, CA, GBThe country of the jurisdiction where tax was imposed. This is a code that represents the line item’s origin country for origin-based tax collection or the item’s destination country for destination-based tax collection.
state_codeText (ISO 3166-2 without country prefix)CA, NY, TXThe state, county, province, or region of the jurisdiction where tax was imposed. This is a code without the country prefix that represents the line item’s origin state for origin-based tax collection or destination state for destination-based tax collection. This value isn’t guaranteed to be set when jurisdiction_level is country.
taxabilityEither taxable or nontaxabletaxableIndicates whether the line item is taxable in the applicable jurisdiction.
taxability_reasonEither customer_exempt, not_collecting, not_subject_to_tax, jurisdiction_unsupported, not_supported, product_exempt, product_exempt_holiday, reduced_rated, standard_rated, reverse_charge, zero_rated, taxable_basis_reduced, portion_standard_rated, portion_reduced_rated, portion_product_exempt, or proportionally_ratedstandard_ratedThe reason for the taxability in the applicable jurisdiction.
tax_rateDecimal number0.08, 0.0625The tax rate percentage as a decimal (for example, 0.08 for 8%). Rounded to 6 decimal places.
tax_typeEither sales_tax, use_tax, vat, gst, pst, hst, qst, ct, sst, rst, jct, igst, lease_tax, communications_tax, amusement_tax, service_tax, gross_receipts_communications_tax, or service_communications_taxsales_tax, vat, gstThe type of imposed tax. This value isn’t guaranteed to be set for taxability_reason values of not_collecting, not_subject_to_tax, reverse_charge or not_supported.
tax_nameTextValue-added tax (VAT)A human-readable name of the imposed tax.
quantity_decimalDecimal number1.5, 2The number of units being purchased or reversed when the transaction_type is reversal.
currencyText (ISO 4217)usd, eur, gbpThe three-letter ISO 4217 code for the currency in which amounts are defined. This is the integration currency, which can differ from the tax authority’s local filing currency.
gross_amountDecimal number10.00The gross amount exclusive of tax.
taxable_amountDecimal number10.00The amount of the line item that is considered taxable.
non_taxable_amountDecimal number0.00The amount of the line item that is considered non-taxable.
tax_amountDecimal number0.80The amount of tax calculated for the applicable jurisdiction.
filing_currencyText (ISO 4217)usd, eur, gbpThe three-letter ISO 4217 code for the local currency used by the applicable tax authority. Filing amounts are expressed in this currency. This value may be empty for taxability_reason values of not_supported, not_subject_to_tax, and not_collecting.
filing_exchange_rateDecimal number1.0The exchange rate used to convert currency to the tax authority’s local filing currency. This value isn’t guaranteed to be set for taxability_reason values of not_supported, not_subject_to_tax, and not_collecting.
filing_tax_amountDecimal number0.80The amount of tax calculated for the line item, expressed in the tax authority’s local filing currency. This is empty when filing_currency is empty.
filing_taxable_amountDecimal number10.00The amount of the line item that is taxable, expressed in the tax authority’s local filing currency. This is empty when filing_currency is empty.
filing_non_taxable_amountDecimal number0.00The amount of the line item that is non-taxable, expressed in the tax authority’s local filing currency. This is empty when filing_currency is empty.
customer_tax_idText, list of Tax ID type & value pairs[["de_vat", "DE123456789"], ["us_ein", "12-3456789"]]The customer’s tax IDs associated with the tax transaction.
origin_resolved_address_line1Text510 Townsend StThe line 1 of the tax transaction’s origin address as determined by Stripe Tax (for example, street, PO Box, or company name).
origin_resolved_address_line2TextSuite 200The line 2 of the tax transaction’s origin address as determined by Stripe Tax (for example, apartment, suite, unit, or building).
origin_resolved_address_cityTextSan FranciscoThe city, district, suburb, town, or village of the tax transaction’s origin address as determined by Stripe Tax.
origin_resolved_address_stateText (ISO 3166-2 without country prefix)CA, NYThe state, county, province, or region of the tax transaction’s origin address as determined by Stripe Tax.
origin_resolved_address_postal_codeText94103The ZIP or postal code of the tax transaction’s origin address as determined by Stripe Tax.
origin_resolved_address_countryText (ISO 3166-1 alpha-2)US, CAThe country of the tax transaction’s origin address as determined by Stripe Tax.
destination_resolved_address_line1Text123 Main StThe line 1 of the customer’s address as determined by Stripe Tax using available customer details (for example, street, PO Box, or company name).
destination_resolved_address_line2TextApt 4The line 2 of the customer’s address as determined by Stripe Tax using available customer details (for example, apartment, suite, unit, or building).
destination_resolved_address_cityTextLos AngelesThe city, district, suburb, town, or village of the customer’s address as determined by Stripe Tax using available customer details.
destination_resolved_address_stateText (ISO 3166-2 without country prefix)CA, NYThe state, county, province, or region of the customer’s address as determined by Stripe Tax using available customer details.
destination_resolved_address_postal_codeText90001The ZIP or postal code of the customer’s address as determined by Stripe Tax using available customer details.
destination_resolved_address_countryText (ISO 3166-1 alpha-2)US, CAThe country of the customer’s address as determined by Stripe Tax using available customer details.
performance_location_resolved_address_line1Text123 Main StThe line 1 of the tax location address as determined by Stripe Tax (for example, street, PO Box, or company name).
performance_location_resolved_address_line2TextApt 4The line 2 of the tax location address as determined by Stripe Tax (for example, apartment, suite, unit, or building).
performance_location_resolved_address_cityTextLos AngelesThe city, district, suburb, town, or village of the tax location address as determined by Stripe Tax.
performance_location_resolved_address_stateText (ISO 3166-2 without country prefix)CA, NYThe state, county, province, or region of the tax location address as determined by Stripe Tax.
performance_location_resolved_address_postal_codeText90001The ZIP or postal code of the tax location address as determined by Stripe Tax.
performance_location_resolved_address_countryText (ISO 3166-1 alpha-2)US, CAThe country of the tax location address as determined by Stripe Tax.
invoice_idTextin_1ABCdefGH123456The ID of the invoice associated with the tax transaction.
invoice_numberTextABC123A unique, identifying string that appears on emails sent to the customer for the invoice, only available when invoice_id is present.
customer_idTextcus_1ABCdefGH123456The ID of the customer record associated with the transaction.
customer_nameTextJenny RosenThe customer’s current full name or business name, only available when customer_id is present.
customer_emailTextjenny.rosen@example.comThe customer’s current email address, only available when customer_id is present.
customer_taxability_overrideEither customer_exempt, reverse_charge, or nonenoneThe customer’s tax status used for taxability of the tax transaction.
product_idTextprod_ABC123xyz456The ID of the product associated with the transaction line item.
product_nameTextPremium PlanThe current name of the product associated with the transaction line item, only available when product_id is present.

Metadata allows for supplementary information to be attached to each transaction. The Itemized export supports the following metadata sections. Each metadata key you select will appear as a column using the section[key] naming format. For example, if you select the order_id key from credit_note_metadata, the resulting column will be named credit_note_metadata[order_id].

  • Credit Notes (credit_note_metadata)
  • Invoices (invoice_metadata)
  • Payment Intents (payment_metadata)
  • Refunds (refund_metadata)
  • Tax Transactions (tax_transaction_metadata)

Summarized exports

Summarized exports contain an aggregated view of transactions per jurisdiction. In certain cases, such as when currencies or tax rates vary, you might have multiple rows per jurisdiction.

All columns account for negative line items generated as a result of subscription prorations or credits for unused time. This helps reconcile your summarized and itemized exports.

Summarized exports don’t contain non-taxable transactions, unlike itemized exports.

You can also filter transactions by jurisdiction before exporting. This helps reduce the size of large export files and eliminates the need to manually filter data after downloading. Jurisdiction filters are especially useful for EU OSS registrations (which include multiple countries) or regions with limited registration options. If you have only one registered jurisdiction, it’s automatically pre-selected. You can clear this selection to include transactions from all jurisdictions.

Regional considerations

Use this export for country-level filings and VAT OSS, and for simpler US states.

Download example CSV file

Column Reference

The summarized export contains the following columns. Some columns aggregate only one type of tax transaction. For a definition of transaction types, see transaction_type in the itemized export column reference.

Column nameTypeExampleDescription
transaction_date_start_utcDate and time (yyyy-MM-dd HH:mm:ss)2024-01-01 00:00:00The start of the date range for tax transactions included in this aggregation, in UTC.
transaction_date_startDate and time (yyyy-MM-dd HH:mm:ss)2024-01-01 00:00:00The start of the date range for tax transactions included in this aggregation, in the requested timezone.
transaction_date_end_utcDate and time (yyyy-MM-dd HH:mm:ss)2024-01-31 23:59:59The end of the date range for tax transactions included in this aggregation, in UTC.
transaction_date_endDate and time (yyyy-MM-dd HH:mm:ss)2024-01-31 23:59:59The end of the date range for tax transactions included in this aggregation, in the requested timezone.
transaction_currencyText (ISO 4217)usd, eur, gbpThe three-letter ISO 4217 code for the currency in which amounts are defined. This is the integration currency, which can differ from both the settlement currency and the tax authority’s local filing currency.
filing_currencyText (ISO 4217)usd, eur, gbpThe three-letter ISO 4217 code for the local currency used by the applicable tax authority. Filing amounts are expressed in this currency.
country_codeText (ISO 3166-1 alpha-2)US, CA, GBThe country of the jurisdiction where tax was imposed. This is a code that represents the line item’s origin country for origin-based tax collection or the item’s destination country for destination-based tax collection.
state_codeText (ISO 3166-2 without country prefix)CA, NY, TXThe state, county, province, or region of the jurisdiction where tax was imposed. This is a code without the country prefix that represents the line item’s origin state for origin-based tax collection or destination state for destination-based tax collection. This value isn’t guaranteed to be set when jurisdiction_level is country.
jurisdiction_nameTextCALIFORNIA, NEW YORKThe name of the jurisdiction that imposed the tax. Transactions are grouped by jurisdiction for aggregation.
jurisdiction_levelEither country, state, county, city, or districtstate, countyThe level of the jurisdiction that imposed the tax. Transactions are grouped by jurisdiction level for aggregation.
tax_rateDecimal number0.08, 0.0625The tax rate percentage as a decimal (for example, 0.08 for 8%). Rounded to 6 decimal places.
total_salesDecimal number500.00The sum of sales amounts excluding tax. This represents the total gross sales for the jurisdiction. Aggregates transaction transactions only.
totalDecimal number540.00The sum of sales transaction amounts including tax. This represents the total amount charged to customers. Aggregates transaction transactions only.
total_sales_refundedDecimal number5.00The sum of refund amounts excluding tax. This represents the total amount refunded to customers, not including the tax portion. Aggregates reversal transactions only.
total_tax_refundedDecimal number0.40The sum of tax amounts refunded. This represents the total tax portion of refunds. Aggregates reversal transactions only.
total_tax_collectedDecimal number39.60The sum of tax amounts collected. This represents the total tax liability before refunds. Aggregates transaction transactions only.
total_taxable_salesDecimal number495.00The sum of taxable amounts. This represents the portion of sales that were subject to tax. Aggregates transaction transactions only.
total_nontaxable_salesDecimal number0.00The sum of non-taxable amounts. This represents the portion of sales that were not subject to tax. Aggregates transaction transactions only.
filing_total_salesDecimal number500.00The sum of sales amounts excluding tax expressed in the tax authority’s local filing currency. This represents the total gross sales for the jurisdiction in the filing currency. Aggregates transaction transactions only.
filing_total_taxable_salesDecimal number495.00The sum of taxable amounts expressed in the tax authority’s local filing currency. This represents the portion of sales that were subject to tax. Aggregates transaction transactions only.
filing_total_nontaxable_salesDecimal number0.00The sum of non-taxable amounts expressed in the tax authority’s local filing currency. This represents the portion of sales that were not subject to tax. Aggregates transaction transactions only.
filing_total_tax_collectedDecimal number39.60The sum of tax amounts collected expressed in the tax authority’s local filing currency. This represents the total tax liability before refunds. Aggregates transaction transactions only.
filing_total_sales_refundedDecimal number5.00The sum of refund amounts excluding tax expressed in the tax authority’s local filing currency. This represents the total amount refunded to customers, not including the tax portion. Aggregates reversal transactions only.
filing_total_tax_refundedDecimal number0.40The sum of tax amounts refunded expressed in the tax authority’s local filing currency. This represents the total tax portion of refunds. Aggregates reversal transactions only.
filing_total_taxable_refundedDecimal number5.00The sum of taxable refund amounts expressed in the tax authority’s local filing currency. This represents the taxable portion of refunds. Aggregates reversal transactions only.
filing_tax_payableDecimal number39.20The net tax liability (tax collected minus tax refunded) expressed in the tax authority’s local filing currency. This represents the amount owed to or refundable from the tax authority.

Imports

You can import transaction data from third-party platforms into Stripe Tax using CSV files. This lets you consolidate sales data from multiple platforms to get a unified view of your tax obligations.

By importing your external platform transactions, you can:

  • Eliminate the need to reconcile and aggregate across different platforms.
  • Stay compliant by having the most accurate view of your tax obligations.
  • Make informed decisions about tax registration requirements.

Learn more about importing transactions

Location reports

Location reports provide a summary of transaction and refund data aggregated for specific locations. Every location report follows the filing and formatting requirements of the location it’s generated for, and aligns with the specific filing periods of its online filing portal. You can select the frequency and period within the report, as determined by the location.

Stripe provides location reports for the US and Canada. You can only view location reports in the Dashboard and can’t download them.

Stripe Tax currently doesn’t support use cases beyond your transaction data, such as credits, prepayments, discounts, and so on. As a result, the final numbers for your business’s filing might vary.

Caution

  • Location reports include transactions starting from January 1, 2023, and support fiscal annual periods from 2024 onward. To access your transaction data from 2022, use itemized or summarized exports.

  • Location reports don’t include imported transactions. If you’ve imported third-party transaction data, use the itemized or summarized exports to view that data.

Refunds

Location reports include refunds associated with an original transaction in the same period as the original transaction, even if the refund occurred much later. This can affect the aggregated amounts in a report. Stripe doesn’t allow the reassigning of refunds to alternate periods.

Partial Stripe Tax API refunds

If you refund a tax amount such that the total tax is no longer proportional to the subtotal, your tax reporting can be unreliable. It won’t automatically adjust the taxable and nontaxable amounts, and won’t reflect the reason for the tax reversal (such as product exempt, customer exempt, or reverse charge). We recommend not refunding partial line item tax amounts. Instead, fully reverse the transaction and create a new one with appropriate inputs for an accurate tax calculation.

Tax types

Location reports support sales or use tax types only.

For more detailed breakdowns including other tax types, use itemized exports.

Location specific considerations

The locations listed below have additional report considerations:

  • Alaska
  • Arizona
  • Florida
  • Hawaii
  • Illinois
  • Kentucky
  • Tennessee
  • Washington

Access data using exports and reports

Itemized and summarized exports

  1. Go to the Locations page on the Dashboard.
  2. Click Export transactions.
  3. Specify the date range and time zone.
  4. Optionally, filter by jurisdiction to export transactions from specific locations only.
  5. Select either Itemized export or Summarized export. If you selected Itemized export:
    1. Select the Columns you want.
    2. Select whether to Exclude non-taxable transactions or not.
  6. Click Export. The export might need time to process.

Itemized exports by location

  1. Go to the Locations page on the Dashboard.
  2. Click the location you want to generate an export for.
  3. Click Export transactions.
  4. Specify the date range and the time zone.
  5. Select the Columns you want
  6. Select whether to Exclude non-taxable transactions or not.
  7. Click Export. The export might need time to process.

Location reports

  1. Go to the Locations page on the Dashboard.
  2. Click the location whose location report you want to access.
  3. Select the Frequency.
  4. Select the Period.

Scheduled Tax reports

Stripe can generate your Tax reports on a schedule.

Itemized and summarized exports

  1. Go to the Locations page on the Dashboard.
  2. Click Export transactions.
  3. Click Schedule…
  4. Select the Schedule you want to receive your reports by: Daily, Weekly, or Monthly. To disable scheduled reports, select None.
  5. Select Columns for Itemized tax transactions. We recommend exporting All columns for completeness.
  6. Click Save.

Itemized exports by location

  1. Go to the Locations page on the Dashboard.
  2. Click the location you want to schedule Tax reports for.
  3. Click Export transactions.
  4. Click Schedule…
  5. Select the Schedule you want to receive your reports by: Daily, Weekly, or Monthly. To disable scheduled reports, select None.
  6. Select Columns. We recommend exporting All columns for completeness.
  7. Click Save.

Location reports

You can’t schedule location reports.

Giving access to your accountant

If you want to give access to your accountant or other trusted third parties to access your Tax reports, you can invite them as a team member.

After you invite them, your accountant (or others) can perform the same steps described above to access location reports, itemized, and summarized exports.

Security tip

Give your users the smallest set of permissions possible that they can still perform their duties with.

For accessing Tax reports, we recommend the View Only role. See user roles to learn what this role can and can’t do.

Tax calculations recorded in reports

Stripe Tax exports include transactions created using Stripe Tax API and operations on Stripe objects with automatic_tax[enabled]=true.

Note

We consider transactions effective on the date they finalize and we don’t recalculate taxes afterwards.

The following operations increase the balance of total tax reported:

  • The customer completes a payment in a Checkout Session. This also applies to Checkout Sessions created through Payment Links.
  • Finalizing an invoice. This applies to one-off invoices and recurring (subscription) invoices. Invoice finalization happens when the state of the invoice transitions from a draft to an open state. This transition happens before the invoice is paid.
  • Transitioning the state of an invoice from uncollectible to paid through the Pay Invoices API.
  • Voiding a credit note.
  • Creating a tax transaction using the Stripe Tax API.

The following operations decrease the balance of total tax reported:

  • Voiding an invoice.
  • Marking an invoice as uncollectible.
  • Creating a credit note.
  • Creating a refund of a charge associated with an invoice or a Checkout Session.
  • Creating a reversal of a tax transaction using the Stripe Tax API.

The following operations aren’t reflected in Tax reports:

  • Disputes that are upheld by the cardholder’s bank. Stripe Tax doesn’t decrease the balance of the collected total tax. For example, for a disputed transaction with an amount of 100 USD and exclusive tax of 10 USD, Tax reports still reflect the total tax collected as 10 USD.
  • Refunds of uncaptured amounts of a payment. This can happen when performing a partial capture for payments of Checkout sessions using capture_method=manual. When the capture amount is lower than the original amount, Stripe Tax doesn’t reduce the total balance of the collected tax.

Tax data in Sigma and Data Pipeline

If you want to create tailored reports for your specific needs, sign up for Sigma or Data Pipeline. For guidance on querying and creating custom tax data reports, see our guide on Querying Tax data.

See also

  • Set up Stripe Tax
  • Products, prices, tax codes, and tax behavior
  • Registering for tax
  • Tax filing and remittance
Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Chat with Stripe developers on Discord.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc
On this page