Stripe Automated Sales Tax Filing: Review It Before the 6th

If you use Stripe's automated sales tax filing, TaxJar files your US returns for you, and you get a short window each month to check the numbers before anything is filed. Stripe can start processing filings as early as the 7th. Any change you need has to be requested before 6 PM Eastern on the 6th. Miss that window and the return goes in as Stripe has it, and your QuickBooks sales tax liability account is left to explain the difference.

Most people approve the summary without opening it. That works until a month when the filing and the books disagree: a sale made outside Stripe, a subscription that never moved to Stripe Tax, or a refund whose tax never left the liability account. Each of these is easier to fix in the five days before the filing than in the months after it.

This guide is the bookkeeper's review of Stripe's automated sales tax filing. It covers what the monthly summary shows and what it leaves out, why the filed amount won't equal the tax you collected, and how to tie each filing to the QuickBooks liability account. A worked September example carries the numbers all the way to the bank debit.

Start a free trial if you want the Stripe Tax on your sales to land in a QuickBooks liability account you can check against every filing.

How Stripe's automated sales tax filing works each month

Stripe's filing documentation describes a monthly cycle with three fixed points:

1. The summary email. "Each month, before your tax filing begins processing," Stripe emails a summary of your upcoming filings to the address on your TaxJar account. It lists the locations where you're signed up for automated filing and links to the details.
2. The change deadline. To change an upcoming filing, you submit a request "before the 6th of the month at 6 PM ET," using Request changes on that location and period. TaxJar replies to the same email address within three business days.
3. Processing. Stripe "automatically begins processing filings as early as the 7th of the month," and emails you when each filing is complete.

You can open the same details without the email. In the Stripe Dashboard, go to Tax, then Overview, and under Automatic filing with Stripe choose the location and period.

Some background on who this applies to. Automated filing runs through TaxJar, a Stripe company, and needs a Tax Complete subscription. It is available in all 46 US locations with a state-level sales and use tax. TaxJar remits from a US bank account you provide, not from your Stripe balance. That last point matters later, when the payment shows up in QuickBooks.

The review window is short on purpose. If you're the person who closes the books, block time for it in the first days of every month, the same way you'd block time for a bank reconciliation.

What the filing review shows, and what it leaves out

For each location and period, Stripe shows "key totals such as total sales, tax collected, and estimated tax due." Below the totals is the list of transactions included in the filing, with filters to find specific ones. Stripe's own instruction is direct: "review your data for accuracy and completeness before Stripe begins filing for you."

Accuracy is the easy half. Completeness is where filings go wrong, because Stripe only files what Stripe Tax calculated. Its documentation lists the common transactions that won't be included:

• manual invoices created in Stripe without Stripe Tax applied
• transactions using manual tax rates
• sales processed before Stripe Tax was enabled on your account
• existing subscriptions that have not yet been migrated to Stripe Tax

Add one more group that never reaches Stripe at all: sales made somewhere else. A market stall, a wholesale order invoiced by hand, a second storefront on another platform. If your state expects those sales on the same return, the filing is short unless you add them.

Two checks catch most of it. First, look for anything you charged tax on that didn't go through Stripe Tax: old subscriptions are the usual suspect. Second, compare the filing against the QuickBooks account the tax actually sits in, which is the subject of the next two sections.

If you want the line-level detail, Stripe's instructions are to export it: Quick actions, then Export transactions, choose the state, set the time zone to UTC, and pick Itemized export. Expect a small mismatch even then. Stripe notes that some transactions for a location can be filed separately. Local amusement taxes are its example, and they can sit in the export but outside the state return.

Why the filed amount won't match the tax you collected

Stripe says it files "based on the amount of tax you actually collected," and then lists the reasons the amount filed and remitted can still vary slightly. Each one has a QuickBooks consequence.

Reason	What Stripe does	What it means in QuickBooks
Prepayments	Prior prepayments reduce what you owe for the period; prepayments currently due increase it	The bank debit won't equal the period's tax. Track prepayments separately so the liability account still ties out.
Timely filing discounts	Stripe applies a state's discount automatically when calculating what it will file	You pay less than you collected. The difference stays in the liability account until you clear it.
Jurisdiction rounding	Each tax authority applies its own rounding rules on the return	Cents of difference, more visible with many low-priced sales. Clear them; don't chase them.
Refunds	Deducted from gross sales in the filing period when the refund occurred, regardless of the original sale date	Lines up with QuickBooks, which records the refund when the money moves.
Excess refunds	If refunds exceed sales in a period, Stripe carries the excess forward to the next period	A location can file at zero while QuickBooks shows tax coming back out. The credit is used up in later periods.
Incomplete addresses	Listed by Stripe as a source of variance	Usually small. Worth a look if one location's number looks off.

The refund row is the one that surprises people, because Stripe's location reports do the opposite. A location report puts a refund back in the period of the original sale. Automated filing deducts it in the period the refund happened. If you've been reconciling against Stripe Tax location reports, stop for automated filings. Reconcile against the filing details for that location and period instead. Our guide to refunding a sale after you filed its sales tax walks through what that difference does to an already-filed quarter.

Tying the filing to your QuickBooks sales tax liability account

On a US QuickBooks company, Acodei's documentation is clear about where Stripe Tax goes. Intuit's rules limit US accounts to the Tax Product method: you create a non-inventory product, for example "Sales Tax," tied to a liability account. Acodei then rolls all Stripe Tax on a synced invoice or receipt into a single line on that product. For the state-by-state split, Acodei points you to Stripe's own reports, and you pay what you owe from that liability account. (The setup is in Stripe Tax in QuickBooks Online.)

That design has one consequence for the review: one QuickBooks account holds the tax for every state. The liability account doesn't know California from Texas. Stripe does, so the per-location check happens in Stripe, and the total is what you tie to QuickBooks.

The comparison works like this:

1. In QuickBooks, run a transaction report on the liability account for the filing period. Separate the credits (tax on sales) from the debits (tax on refunds, payments, adjustments).
2. In Stripe, open the filing details for every location due this month and add up the tax each will file on, before discounts and prepayments.
3. Compare the period's net sales tax activity in QuickBooks with that total.

Two things make step 3 harder than it sounds. Locations can have different filing frequencies, so a month where only your monthly states file will leave the quarterly states' tax sitting in the account. Compare like with like: this month's QuickBooks activity against this month's filings, plus the tax for locations that file later. And your books may date a transaction in your own time zone, while Stripe's Tax Overview always uses UTC. In US time zones, a sale late in the evening on the last day of the month can already be the next month in Stripe.

What's left after those adjustments is the list of things to fix before the 6th. The next section shows what that list looks like with real numbers.

A worked review: one September filing, three differences

A small business is registered in one state and files monthly through Stripe. Its books are on QuickBooks Online, with Stripe Tax posting to a liability account called Sales Tax Payable. On October 2 the summary email arrives, and the bookkeeper sets the September filing next to the account's September activity.

	Amount
QuickBooks, Sales Tax Payable, September
Tax on September sales (credits)	$4,212.40
Tax taken back out for September refunds (debits)	($64.00)
Net September activity	$4,148.40
Stripe filing details, September
Tax collected	$4,146.40
Refunds deducted in September	($82.00)
Tax the filing is based on	$4,064.40
Difference	$84.00

The bookkeeper filters the filing's transaction list and the liability register, and the $84.00 breaks into three items.

$42.00: a sale that never touched Stripe. The business sold at a trade show and recorded the sale in QuickBooks by hand, tax included, to the same liability account. Stripe can't file what it never saw. Fix: under Transactions in this filing, choose Import and upload the sale using Stripe's CSV import format. The filing rises to $4,106.40.

$18.00: a refund whose tax stayed in QuickBooks. A September sale was refunded directly on the payment rather than through a credit note. Stripe deducted the tax. In QuickBooks the refund came through, but the $18.00 of tax was never taken out of the liability account. Acodei's documentation notes that payment-only refunds don't always carry the tax detail, so tax may need a manual adjustment. Fix: a journal entry that debits Sales Tax Payable $18.00 and credits the revenue account the refund reduced. September activity falls to $4,130.40.

$24.00: a sale on the wrong side of midnight UTC. An invoice finalized at 9:30 PM Eastern on September 30 is October 1 in UTC. The books carry it in September; Stripe's UTC view puts it in October. Fix: nothing. Note it, and expect it to reverse when October is filed.

After the two fixes, the books show $4,130.40 against a filing based on $4,106.40, and the $24.00 gap is explained. No change request was needed because the bookkeeper caught the import before processing started.

Then the filing runs. Suppose the state offers a timely filing discount and Stripe applies $20.00 of it. The estimated tax due, and the bank debit, is $4,086.40. In QuickBooks, after the debit is recorded against the liability account, September's activity leaves $44.00: the $20.00 discount and the $24.00 sale that belongs to October's filing. A journal entry moves the $20.00 to the income account your accountant chooses for filing discounts. The $24.00 stays put, because you still owe it.

Every dollar left in the account now has a name. That is the test of a finished review.

Fixing what you find before the 6th

Most problems fall into four groups. Here is what to do with each.

Sales from outside Stripe. Import them into the filing using Import under Transactions in this filing, or from Tax, Quick actions, Import transactions. Stripe's import page sets the CSV format. Do it during the review, while the period is still open for changes.

Transactions Stripe Tax didn't calculate. Manual invoices without Stripe Tax, manual tax rates, and unmigrated subscriptions all stay out of the filing. For this month, use Request changes to tell TaxJar what's missing, before 6 PM Eastern on the 6th. For future months, fix the source: turn on automatic tax for those invoices and migrate the subscriptions so next month's filing includes them.

Anything else that looks wrong in Stripe's numbers. A transaction in the wrong location, a total that doesn't match what you can see in the transaction list. That's what Request changes is for. Describe the problem precisely: the transaction, the amount, the location and period. TaxJar responds within three business days, so if you find the problem on the 5th, the reply may come after processing starts. Review early.

Problems that only exist in QuickBooks. A payment-only refund whose tax stayed in the liability account, a sale entered twice by hand, tax posted to the wrong account. None of these touch the filing. Fix them in QuickBooks so the liability account tells the truth when the debit arrives.

If you find a whole period that was never filed, that is a different request. TaxJar can file overdue returns, but you have to ask for it separately.

After TaxJar files: recording the payment in QuickBooks

TaxJar remits the tax from the US bank account on your filing setup, so the payment never passes through Stripe. Stripe's advice is to keep enough in that account to cover your sales tax liabilities. In QuickBooks, the payment shows up as a debit in that bank account's feed.

Categorize that debit to the sales tax liability account. Don't also write a check for the same payment, or the liability is cleared twice. Match each debit to the filing it pays, by location and period.

Then look at what's left. If the debit was smaller than the tax collected because of a discount, prepayment, or rounding, the difference stays in the account until you clear it. Move discounts and rounding to the accounts your accountant picks, and record any prepayment the way you've agreed to track it. If a location carried refunds forward, its debit may be zero while QuickBooks shows tax already removed for those refunds. The account will look short until later filings use up the credit, so note the carried-forward amount in your working papers.

You can see completed filings in your TaxJar filing history. Save the filing details alongside the month's QuickBooks reconciliation, so whoever reviews the books later can see which number went to the state.

For a deeper look at why Stripe's tax numbers and QuickBooks drift apart over time, see why the Stripe Tax report and QuickBooks don't match.

A monthly review checklist

1. When the summary email arrives, open each location's filing details under Tax, Overview, Automatic filing with Stripe.
2. Run the QuickBooks liability account's transactions for the same period.
3. Add up the tax every location will file on and compare it with the period's net activity in QuickBooks.
4. Allow for locations that file on a different frequency, and for sales near midnight UTC.
5. List every remaining difference by transaction.
6. Import sales made outside Stripe into the filing.
7. Use Request changes for anything missing from or wrong in Stripe's numbers, before 6 PM Eastern on the 6th.
8. Fix QuickBooks-only problems, such as payment-only refunds whose tax stayed in the liability account.
9. When the debit arrives, categorize it to the liability account, once.
10. Clear discounts and rounding, note carry-forwards and timing items, and save the filing details.

Frequently asked questions

When does Stripe start processing automated sales tax filings?

Stripe says it automatically begins processing filings as early as the 7th of the month. It sends a summary of upcoming filings before processing starts, and you can review the same details under Tax, then Overview, then Automatic filing with Stripe. You get an email when each filing is complete.

How do I change an automated filing before Stripe files it?

Open the details for the location and period and select Request changes, then describe what needs to change. Stripe's deadline is before 6 PM Eastern on the 6th of the month. TaxJar replies to the email on your TaxJar account within three business days, so submit early rather than on the last day.

Why is the amount Stripe filed different from the sales tax I collected?

Stripe files based on the tax you actually collected, but the amount filed and paid can differ because of prepayments, timely filing discounts, each jurisdiction's rounding rules, refunds deducted in the period they happened, excess refunds carried forward, and incomplete customer addresses. The leftover difference stays in your QuickBooks liability account until you clear it.

Does Stripe's automated filing include sales I made outside Stripe?

Not unless you add them. Stripe only files transactions where Stripe Tax calculated the tax. You can import sales from other platforms into a filing using Stripe's CSV import, from the filing details or from Tax, then Quick actions, then Import transactions. Do it during the review window.

How do I record the TaxJar sales tax payment in QuickBooks?

TaxJar pays from the US bank account on your filing setup, so the payment appears in that bank account's feed in QuickBooks, not in Stripe. Categorize the debit to your sales tax liability account. Don't also enter a check for the same payment, or you will clear the liability twice.

Where this leaves you

Automated filing takes the return off your desk. It doesn't take the review off your desk. The summary arrives every month, the window closes on the 6th, and the only way to know the filing is right is to compare it with the account the tax is sitting in.

Acodei's part is getting the Stripe side into that account: on a US QuickBooks company it rolls the Stripe Tax on your synced invoices and receipts into the tax product you tie to your liability account. That leaves one number in QuickBooks to check against Stripe's filings each month, and a short list of exceptions to clear before the 6th.

Start a free trial and connect your Stripe account to QuickBooks Online.