Stripe Tax Rounding: Why QuickBooks Is a Cent Off

Stripe Tax, manual tax rates and QuickBooks each round tax at a different point. Where the stray cent comes from and how to reconcile it.

Acodei Content Team · 11/19/2026 · 14 min read

A $29.97 invoice with an 8.875% tax rate has two honest answers for its tax. Round each line's tax and add them up, and you get $2.65. Add the lines first and round once, and you get $2.66. Neither is a mistake. They are two different rounding rules, and Stripe, QuickBooks and your own spreadsheet don't all use the same one.

That is where most one-cent tax differences between Stripe and QuickBooks come from. Nobody miscalculated anything. Something rounded at a different point in the arithmetic, and a fraction of a cent became a whole one.

One rounding, recorded once. Acodei's Invoice Sync turns each finalized Stripe invoice into a QuickBooks invoice, with Stripe's tax on a liability product or mapped to your QuickBooks tax codes. Start a free trial.

This guide covers the three rounding rules you'll run into (Stripe Tax, Stripe's manual tax rates, and QuickBooks' own sales tax engine), works the same invoice through each of them, explains why inclusive prices push the stray cent into your net revenue instead of your total, and shows what reaches QuickBooks and how to handle the cent when it does show up.

Why tax rounding produces a cent at all

Tax is a percentage, and percentages of prices almost never land on a whole cent. A $19.99 item at 8.875% carries $1.7741125 of tax. You can't charge a customer a fraction of a cent, so every tax engine has to round, and it has to decide when:

  • Per line. Calculate the tax on each line, round each line's tax to the cent, then add the rounded amounts.
  • Per invoice. Calculate the tax on each line without rounding (or on the subtotal), add it up, then round once.

Rounding once is more accurate, because each rounding step can move the answer by up to half a cent. Round three lines separately and the errors can stack in the same direction. Round once and there's only one error, never more than half a cent.

The practical problem isn't accuracy. It's that two systems looking at the same invoice can each be correct by their own rule and still disagree by a cent. Over a month of invoices those cents add up to a liability account that won't tie to a filing report, an effective rate that reads 8.88% instead of 8.875%, or an invoice that someone flags in review because "the tax is wrong."

Rule 1: Stripe Tax rounds the total, then spreads it back over the lines

If you use Stripe Tax (automatic tax), you don't choose a rounding method. Stripe's documentation on how Stripe Tax calculates tax describes one fixed approach:

  • "Stripe Tax retains precision while calculating tax, then rounds tax amounts half up to the smallest currency unit when determining amounts to collect."
  • "For automatic tax, Stripe calculates tax across amounts that have the same applicable tax rate before rounding the total tax."
  • "Stripe then allocates the rounded tax total back to each line item."

The last step has a consequence that confuses people reading line detail. Stripe adds: "A line item might receive an adjustment of the smallest currency unit so that the line item amounts add up to the transaction total." So if you export the line items and recompute each line's tax yourself, one line can be a cent higher (or lower) than the rate says it should be. That isn't an error on the line. It's where Stripe put the cent so the lines sum to the invoice-level tax it calculated once.

Stripe's guide to tax rates on invoices states the same rule from the other side: "Invoices with automatic Stripe tax always sum up the tax amounts first and then round."

Rule 2: Stripe's manual tax rates let you pick

If you attach your own tax rates to invoices instead of using Stripe Tax, you do get a choice, and it lives in your invoice settings. Stripe's tax rates guide describes both options:

  • Line item level: "Round at the invoice line item level to the smallest currency unit before summing individual tax amounts across the entire invoice."
  • Invoice level: "Sum up all individual taxable amounts unrounded per tax rate. Combine them to a subtotal, apply the tax rate on the subtotal, and then round."

Stripe adds: "Select this configuration on the invoice settings page in the Dashboard. The rounding configuration is only available for invoices with manual tax rates."

That means one Stripe account can produce invoices rounded two different ways. Invoices with automatic tax round once per rate. Invoices with manual tax rates round however your invoice setting says. If you moved from manual rates to Stripe Tax partway through the year, your older invoices and your newer ones may follow different rules, and a reconciliation that assumes one rule will find cents on the other side.

Rule 3: QuickBooks rounds its own way when it calculates the tax

QuickBooks Online has its own answer for the tax it calculates. Intuit's article on rounding of sales tax in QuickBooks Online explains that automated sales tax uses a combined method: it rounds each line item's tax, rounds the total for each tax rate on the transaction, and then adjusts the line-level tax so the lines match that rounded total. Intuit also notes an exception: Arizona and Virginia are the only states that round their sales tax by line item.

Intuit's own example shows the gap. Six $10.00 items at 8.685% come to $0.87 of tax each when rounded per line, which is $5.22. The $60.00 total at 8.685% rounded once is $5.21. Intuit's article says invoice-level rounding is generally the more accurate of the two, because rounding happens only once.

So QuickBooks, like Stripe Tax, lands on the round-once answer for most invoices. That doesn't mean the two will always agree. QuickBooks calculates from its own rates, which may be broken into different components, and from the address on the QuickBooks transaction. Stripe calculates from its own. When both engines run on the same sale, a cent of difference is normal, not a sign that either one is broken.

One invoice, four answers

Here is a three-line invoice at a single 8.875% rate, exclusive of tax, worked through each rule.

LineAmountUnrounded taxTax rounded per line
Annual plan$19.99$1.7741125$1.77
Add-on A$4.99$0.4428625$0.44
Add-on B$4.99$0.4428625$0.44
Total$29.97$2.6598375$2.65
  • Manual tax rate, line item level: $1.77 + $0.44 + $0.44 = $2.65. Invoice total $32.62.
  • Manual tax rate, invoice level: $29.97 × 8.875% = $2.6598375, rounded to $2.66. Invoice total $32.63.
  • Stripe Tax: sums the amounts at the same rate first, so it lands on $2.66 too. The line detail still has to add up to $2.66, so Stripe allocates the extra cent to one of the lines. One add-on line can show $0.45 of tax where your own math says $0.44.
  • A spreadsheet that rounds each line: $2.65, and it disagrees with the invoice by a cent.

Every one of these is correct by its own rule. The fix isn't to find the "right" number. It's to know which rule produced the number you're looking at, and to compare like with like.

The effective rate that looks wrong

Rounding causes a second, quieter problem: the rate you back out of the numbers isn't quite the rate you charged.

Stripe's tax calculation docs give the clearest example. A tax-inclusive price of 79.20 EUR at 19% can't be split into a whole-cent net amount and a whole-cent tax amount that add up to 79.20 and reproduce 19% exactly. Stripe shows the two nearest candidates:

SubtotalTaxTotal
66.55 EUR12.64 EUR79.19 EUR
66.56 EUR12.65 EUR79.21 EUR

Neither totals 79.20. Stripe keeps the amount the customer paid and reports a 66.55 EUR subtotal with 12.65 EUR of tax. In Stripe's words, "Those rounded amounts make the tax rate appear to be 19.01%, even though the applied rate is 19%."

This is worth knowing before someone audits your QuickBooks file. If a reviewer divides each invoice's tax by its net amount and flags everything that isn't exactly 19%, they will flag a large share of perfectly correct invoices. The check that works is the reverse: multiply the net by the rate, round, and confirm you're within a cent. If you want to go deeper on where line amounts themselves get rounded, our post on Stripe sub-cent pricing covers rounding that happens before tax is even calculated.

Inclusive prices move the cent into revenue

With exclusive tax, the price is net and tax goes on top. A rounding difference changes the tax and the invoice total together, so it's visible: the customer pays a cent more or less.

With inclusive tax, the price already contains the tax and the total is fixed. Rounding can't change what the customer pays, so the cent has to come out of somewhere else, and that somewhere is the split between net revenue and tax. If you're not sure which behavior your prices use, our glossary entry on Stripe tax behavior explains the setting.

Stripe's tax rates guide shows exactly this with two inclusive lines at 10%:

LineGrossNet (unrounded)Tax (unrounded)Tax rounded per line
Line item 1$1,000.00$909.0909$90.9091$90.91
Line item 2$50.00$45.4545$4.5455$4.55
Total$1,050.00$95.46

Rounded per line, the invoice is $954.54 of net revenue and $95.46 of tax. Rounded once at the invoice level, the tax on $1,050.00 is $95.4545, which rounds to $95.45, leaving $954.55 of net. Same $1,050.00 from the customer either way. The cent moves between your revenue account and your tax liability.

That's why inclusive-tax setups produce more reconciliation noise than exclusive ones. Inclusive pricing is the norm in most VAT and GST countries, and every system that touches the invoice has to extract the tax from a gross amount instead of adding it to a net one. Any system that re-derives the split, instead of copying it, can land a cent away.

What reaches QuickBooks through Acodei

Acodei doesn't calculate tax. It reads the tax Stripe already calculated and records it in QuickBooks according to the approach you choose. Which approach you're on decides where rounding can still show up.

The tax product approach (most US companies). Acodei rolls all of Stripe's tax amounts into a single line on the QuickBooks invoice or receipt, using a non-inventory product mapped to a liability account. When Stripe calculates $2.66 of tax, the QuickBooks invoice gets a $2.66 tax line. QuickBooks isn't recalculating anything, so the one rounding that happened is Stripe's. You then file from Stripe's tax reports and pay from the liability account. For US QuickBooks companies this is usually the only workable method, because the QuickBooks Sales Tax Center doesn't allow third parties to create official tax rates.

Mapped QuickBooks tax codes (most non-US companies). With QuickBooks Tax Rate (Advanced), you map each Stripe tax rate ID (txr_...) to a QuickBooks tax code, and each product line syncs with the matching code. Where one Stripe line carries more than one rate, such as GST plus PST, you can map the combination to a QuickBooks group tax code so the total tax matches Stripe exactly. Our post on GST plus PST and QuickBooks group tax rates covers that case in detail.

Inclusive tax. When you choose inclusive in the Acodei dashboard, Acodei automatically turns on a manual inclusive tax calculation, which keeps QuickBooks invoice totals aligned with Stripe's final tax calculations. Acodei's documentation is also clear about the limit: partial and daily-summary scenarios can sometimes produce rounding differences.

Daily summaries. If you sync a daily summary instead of individual invoices, Acodei splits the summary into lines by product and tax rate, and for inclusive tax it does the breakdown at the summary level. Keep the arithmetic from earlier in mind here. A day's worth of invoices that were each rounded on their own won't always add up to the same tax as their combined total rounded once. That's the arithmetic behind the caveat above for inclusive daily summaries.

The validation check. When tax is enabled, Invoice Sync compares the final QuickBooks invoice with the Stripe invoice amount and checks that they match exactly. That check only applies with tax enabled. It's a comparison against Stripe's total, the amount Stripe already rounded.

Refunds. Refund through a Stripe credit note when you can. A credit note carries line-level tax detail, so the tax portion can be reduced in QuickBooks. A refund issued only against the payment, with no line breakdown, doesn't always show how much of it was tax.

How to reconcile a one-cent tax difference

Most cent-level tax gaps don't need fixing. They need classifying. Work through them in this order.

1. Find out which rule produced each number. Is the Stripe invoice on automatic tax or on a manual tax rate? If manual, which rounding level is your invoice setting on? Is the number you're comparing against from QuickBooks' own tax engine, from a spreadsheet, or from a tax line that came straight from Stripe? Most "mismatches" turn out to be two different rules applied correctly.

2. Compare at the level where rounding happened. Stripe Tax rounds once per rate on the invoice, so compare invoice-level tax per rate, not line-level tax. Recomputing each line and expecting it to match will fail on whichever line received the allocated cent.

3. Check the effective rate the right way round. Multiply net by rate and round. Don't divide tax by net and expect the exact rate. A 19% invoice that reads as 19.01% is normal.

4. Set a tolerance. On an invoice, a difference of a cent per tax rate is rounding. A difference of several dollars is not, and it's usually something else entirely: a tax line on the wrong product, a currency mismatch, a refund recorded without its tax, or a manual edit in QuickBooks.

5. Don't hand-edit a synced invoice to force a cent. Editing a QuickBooks invoice that Acodei created puts QuickBooks out of step with Stripe, and the next resync can overwrite it. Acodei's own guidance is to resync from the Data Feed rather than change synced transactions by hand.

6. Book an accumulated difference once, on purpose. If you file sales tax from QuickBooks' Sales Tax Center, Intuit lets you record a sales tax adjustment and lists Rounding as one of the reasons. Intuit also allows negative adjustment amounts, so one rounding account can absorb differences in either direction. If you track tax on a liability account and file from Stripe's reports instead, the equivalent is a small journal entry between the liability and a rounding account at period end, with a memo that says what it is. Either way, the goal is one visible line per period, not dozens of edited invoices.

Frequently asked questions

Why is Stripe's tax total one cent different from my calculation?

Because Stripe and your calculation round at different points. Stripe Tax calculates tax across amounts with the same rate before rounding, then rounds half up once. If you round each line's tax separately and add the results, you can land a cent away. Both answers are correct by their own rule.

Does Stripe round tax per line or per invoice?

It depends on how the tax was calculated. With Stripe Tax (automatic tax), Stripe always sums the amounts first and then rounds. With manual tax rates, you choose line item level or invoice level rounding on the invoice settings page in the Dashboard. The setting has no effect on invoices that use Stripe Tax.

Why does a line on my Stripe invoice show a cent more tax than the rate gives?

Stripe Tax rounds the tax total and then allocates it back to the line items. Stripe says a line item might receive an adjustment of the smallest currency unit so the lines add up to the transaction total. The extra cent on that line is where the rounding landed, not a calculation error.

How does QuickBooks Online round sales tax?

Intuit says QuickBooks Online's automated sales tax uses a combined method: it rounds each line, rounds each tax rate's total on the transaction, then adjusts line tax to match. Arizona and Virginia are the exception and round by line item. Intuit describes invoice-level rounding as generally more accurate because rounding happens once.

Should I fix one-cent tax differences in QuickBooks?

Not invoice by invoice. Confirm the difference is rounding (a cent per tax rate per invoice), then book the period's accumulated difference once. In the QuickBooks Sales Tax Center that's a sales tax adjustment with Rounding as the reason; on a plain liability account it's a small journal entry to a rounding account.

The short version

One-cent tax differences come from rounding at different points in the arithmetic, not from wrong rates. Stripe Tax always calculates across the same rate and rounds once, then spreads the rounded total back over the lines, which can put an extra cent on one line. Stripe's manual tax rates round per line or per invoice depending on your invoice setting. QuickBooks' automated sales tax uses its own combined method. With inclusive prices the total is fixed, so the cent moves between net revenue and tax instead. On Acodei's tax product approach, QuickBooks receives Stripe's already-rounded tax as a line amount. With mapped tax codes, group codes keep multi-rate lines matching Stripe, and the remaining risk sits in inclusive partial and daily-summary scenarios. Classify differences before fixing them, and book any accumulated rounding once per period.

Reconcile tax against one source. Acodei's Invoice Sync records each finalized Stripe invoice in QuickBooks, with its tax on a liability product or mapped to your QuickBooks tax codes. Start a free trial.

Share

Automate your Stripe to QuickBooks sync

Save hours every month. Acodei automatically syncs your Stripe transactions, invoices, and payouts to QuickBooks Online.

14-day free trial · card required · cancel anytime

How Acodei handles this in your stack

Stripe QuickBooks Integration

See how Acodei syncs Stripe payments, fees, refunds, invoices, and payouts into QuickBooks Online automatically.

Or go straight to a capability

Get more operational finance guides like this one

We will only send high-value product and finance content.