Stripe Sub-Cent Pricing: Line Rounding and QuickBooks
Stripe prices below a cent but charges whole cents. Where it rounds, a worked invoice that's a cent off, tax, and what QuickBooks shows.
You price your API at $0.0004 a call. Stripe can't charge anyone $0.0004, because every charge has to be a whole number of cents. So somewhere between the price you set and the invoice your customer pays, Stripe rounds. Where it rounds decides whether your invoice matches the spreadsheet your finance team built, and whether the numbers you see in QuickBooks look like they multiply out.
Stripe's answer is specific: it rounds once per invoice line, after multiplying the quantity by the decimal price, and before adding the lines together. That one rule explains almost every "the invoice is off by a cent" question on usage-based and per-unit plans priced below a cent.
Usage invoices, synced line by line. With Acodei's Invoice Sync, a paid-plan feature, a finalized Stripe invoice becomes a QuickBooks invoice with every line reproduced as your mapping settings allow, and the payment is applied when the invoice is paid. Start a free trial.
This post covers how Stripe stores a sub-cent price, exactly where the rounding happens, a worked invoice where per-line rounding and a hand calculation disagree, what that does to tax, and what a QuickBooks invoice line can and can't tell you about the rate behind it.
How Stripe stores a price below one cent
A Stripe Price normally carries its amount in unit_amount, which Stripe's API reference defines as "A positive integer in the smallest currency unit (or 0 for a free price)". For US dollars the smallest unit is the cent, so unit_amount: 1000 is $10.00 and there is no way to write a fraction of a cent in that field.
The sub-cent field is unit_amount_decimal. Stripe describes it as "Same as unit_amount, but accepts a decimal value in the smallest currency unit with at most 12 decimal places." Two details in that sentence trip people up:
- The unit is still cents, not dollars. $0.0004 a call is
unit_amount_decimal: "0.04", four hundredths of a cent. Writing"0.0004"would price each call at one ten-thousandth of a cent, a hundred times less than you meant. - It is a string. The value is a decimal string, so
"0.04"keeps its exact digits instead of turning into a floating-point approximation on the way in.
You set one or the other, never both: "Only one of unit_amount and unit_amount_decimal can be set." Tiered prices get the same option per tier, with tiers.unit_amount_decimal for the per-unit rate and tiers.flat_amount_decimal for a tier's flat fee.
Once a Price exists, its amount is fixed. Stripe's guide to managing prices says that after you create a price "you can only update its metadata, nickname, and active fields." So a decimal price is a decision you make at creation, and changing it later means a new Price ID.
Where Stripe rounds: once per line
The rule sits in the "Rounding" section of the same Stripe guide:
"Rounding occurs on the line item level of your invoices. For example, if you create a price with
unit_amount_decimal = 0.05and a monthly subscription for that [price] withquantity = 30, rounding occurs after multiplying the quantity by the decimal amount. In this case, the calculated amount for the line item would be 0.05 * 30 = 1.5, which rounds up to 2 cents. If you have multiple line items, each is rounded up before summing up the total amount for the invoice."
Read that as three steps that always happen in the same order:
- Multiply first. Quantity times the decimal price, at full precision. Stripe doesn't round the price to a cent and then multiply.
- Round the line. The line's amount becomes a whole number of cents. On the invoice line item object, Stripe's reference defines
amountas an integer, "The amount, in the smallest currency unit." - Add the rounded lines. The invoice subtotal is the sum of already-rounded line amounts.
Stripe gives its reason in one line: "This ensures that customers are still charged an integer minor unit amount, as decimal amounts only apply for pricing." Decimal precision lives on the Price. Money that moves is always whole cents.
One honest caveat about direction. Stripe's example, 1.5 cents becoming 2, is a half-way case, and its wording says lines are "rounded up". The guide doesn't give an example of a line that lands at, say, 1.2 cents. If your plan regularly produces fractions below a half, run one test-mode invoice and look at the line amount before you write that assumption into a forecast.
A worked invoice where the hand calculation is off by a cent
Take an API company that bills three metered products monthly, each priced below a cent or at a fraction of one:
| Line | Price (unit_amount_decimal) | Usage | Quantity × price | Line amount |
|---|---|---|---|---|
| Standard API calls | 0.04 (= $0.0004) | 1,250,015 | 50,000.6 cents | 50,001 cents ($500.01) |
| Premium API calls | 0.25 (= $0.0025) | 82,002 | 20,500.5 cents | 20,501 cents ($205.01) |
| SMS sends | 0.75 (= $0.0075) | 4,002 | 3,001.5 cents | 3,002 cents ($30.02) |
| Invoice subtotal | 73,502.6 cents | 73,504 cents ($735.04) |
Every line here has a fraction of at least half a cent, so it rounds up under either reading of Stripe's wording. Stripe bills $735.04.
Now picture the reconciliation spreadsheet. Finance pulls the usage export, multiplies each count by its rate, adds the three results and rounds the total once: 73,502.6 cents, which is $735.03. The spreadsheet says $735.03. Stripe charged $735.04. Nobody made a mistake. The spreadsheet rounded once at the end, and Stripe rounded three times, once per line.
On one invoice that is a cent. Across 2,000 customers on the same plan it is a steady drift between the revenue you expect and the revenue you bill, and it always runs in the same direction when the fractions sit above a half. The fix isn't to correct Stripe. It's to make the spreadsheet round the way Stripe does: compute each line, round each line to the cent, then sum.
The second place a cent goes missing: the displayed rate
The same customer's QuickBooks invoice, or any report that shows a rate column, creates a different kind of confusion. Take the standard API line. Its amount is $500.01 for 1,250,015 calls. Divide one by the other and you get $0.00040000... with a long tail, not exactly $0.0004. Show that rate rounded to the cent and it reads $0.00. Show it to four places and 1,250,015 × $0.0004 is $500.006, which doesn't equal the $500.01 on the line either.
That isn't an error in either system. The line amount is the fact, rounded once by Stripe. The rate column is a description. When you audit a sub-cent invoice, tie out amounts, never quantity times the displayed rate. For the exact rate, go back to the Price in Stripe, or to the pricing.unit_amount_decimal value Stripe keeps on the invoice line.
Fractional quantities are a separate feature
Sub-cent pricing is about the price. Stripe also tracks fractional quantities on invoice lines, and the line item reference describes quantity_decimal as a "Non-negative decimal with at most 12 decimal places." Its older integer quantity field is defined as the quantity "with any decimal precision truncated." If you bill fractional units, such as 2.75 hours or 0.3 GB, read quantity_decimal, not quantity, when you check a line, or the arithmetic will look wrong for a different reason.
What per-line rounding does to tax
Tax rounding follows its own rule, and Stripe documents three cases in the same guide:
- Exclusive tax rates on lines: "Exclusive taxes are added to each line item amount, depending on the tax rate."
- Stripe Tax (automatic tax): "exclusive taxes are applied and rounded on the total of the invoice, including invoice level discounts."
- Manual tax rates: you choose. Stripe says you can "apply and round taxes for each line item, or apply and round taxes on the invoice subtotal" from the invoice settings page in the Dashboard.
So the line amounts are always rounded per line, while tax is rounded per line or on the total depending on how you calculate it. On the worked invoice above, with automatic tax, tax is computed on $735.04, the sum of the rounded lines, not on the unrounded $735.026. If your tax report recomputes tax from usage times rate, it inherits the same one-cent gap as the spreadsheet.
If you use Acodei with tax enabled, the rounding order matters for one more reason. Acodei's Invoice Sync compares the finished QuickBooks invoice to the Stripe invoice amount and requires an exact match, a check that applies only when tax is enabled. The amount it is checking against is Stripe's: rounded lines, then tax as Stripe computed it.
What reaches QuickBooks
A QuickBooks invoice line holds a product or service, a quantity, a rate and an amount. On a sub-cent Stripe line, the amount is the only one of those that is already settled, because Stripe has rounded it to whole cents before QuickBooks ever sees the invoice.
Here is what Acodei's Invoice Sync does with a usage invoice like the one above, grounded in our product documentation:
- When the Stripe invoice is finalized, Acodei creates a QuickBooks invoice that reproduces every line, and tax lines, as your mapping settings allow. When the invoice is paid, the payment is applied to that QuickBooks invoice.
- Quantity: by default each line is sent with a quantity of 1. Quantity Tracking pushes Stripe's quantities instead of a hard-coded 1. It is off by default, needs backend enablement, and isn't available with inclusive tax.
- Product: each line uses the product returned by Multiple Product Mapping if it is enabled, and the default product otherwise.
With Quantity Tracking off, the worked invoice arrives as three lines with a quantity of 1 each, at $500.01, $205.01 and $30.02, which is often the easiest form for a bookkeeper to read. With it on, the quantities reflect usage, and the rate column is subject to everything in the previous section: trust the amount.
Product mapping for usage lines
Usage lines vary in amount every month, which rules out one mapping technique. Acodei's Transaction Value mapping compares the gross amount to a fixed value you enter, so a line that is $500.01 this month and $512.37 next month will never match a value rule. Map usage products by Stripe Product ID instead. Acodei offers it two ways: with the pricing tier, which stores both the Product ID and the Price ID, or without it, which sends every price on a product to the same QuickBooks product. Our post on Stripe amounts product mapping can't reach covers the other line types where amount rules fail.
If a usage line matches no rule, Acodei uses the default product or raises a sync error, depending on your settings. A rule you add later affects future transactions. A failed one can be retried from the Sync Errors list, where the retry uses your updated rules.
Zero-decimal currencies
The smallest currency unit isn't a cent everywhere. In Japanese yen it is the yen itself, which is what makes JPY a zero-decimal currency. Acodei doesn't support zero-decimal currencies such as JPY, so if you sell sub-unit prices in yen, that revenue needs a different path into QuickBooks.
A checklist for sub-cent pricing
- Write the price in cents.
unit_amount_decimaltakes the smallest currency unit: $0.0004 is"0.04". - Model rounding per line. Any forecast, quote or reconciliation should round each line to the cent before summing, as Stripe does.
- Test the direction once. Stripe's example covers a half-cent. Run a test-mode invoice with a fraction below a half if your volumes produce one.
- Know your tax mode. Line rounding is fixed. Tax rounding depends on whether you use Stripe Tax or manual rates, and on your invoice settings.
- Audit amounts, not rates. On both Stripe and QuickBooks invoices, the line amount is the source of truth. The displayed rate is derived from it.
- Map usage by Product ID. Amount-based rules can't match a line whose amount changes every month.
- Read
quantity_decimalfor fractional units. The integerquantitytruncates.
For per-pack pricing rather than per-fraction pricing, Stripe's quantity transformation is the other tool, and it rounds the quantity, not the amount.
Frequently asked questions
What is unit_amount_decimal in Stripe?
It is the field on a Stripe Price that holds a unit price with fractions of the smallest currency unit. Stripe describes it as the same as unit_amount but accepting a decimal value in the smallest currency unit with at most 12 decimal places. A price of $0.0004 is written as "0.04", meaning four hundredths of a cent.
Can Stripe charge less than one cent?
Stripe can price a unit at less than a cent, but it can't charge a fraction of a cent. Stripe rounds each invoice line to a whole number of cents after multiplying the quantity by the decimal price. Stripe says this ensures customers are charged an integer minor unit amount, because decimal amounts only apply for pricing.
Why doesn't my Stripe invoice total match quantity times price?
Because Stripe rounds each line separately and then adds the rounded lines. If you multiply every line at full precision, add them and round once, you can land a cent or more away from Stripe's total. In Stripe's own example, 0.05 cents times 30 is 1.5 cents, which rounds up to 2 cents on the line.
How does Stripe round tax on sub-cent prices?
Line amounts are rounded per line first. With Stripe Tax, exclusive taxes are applied and rounded on the invoice total, including invoice-level discounts. With manual tax rates, you choose in the invoice settings whether to round tax per line item or on the invoice subtotal.
What quantity and rate does QuickBooks show for a sub-cent Stripe line?
With Acodei, each line is sent with a quantity of 1 by default, at the amount Stripe billed. With Quantity Tracking enabled, the line carries the Stripe quantity instead. Either way, treat the line amount as the source of truth, because a rate derived from a rounded amount won't multiply back out exactly.
The short version
Stripe lets you price below a cent and never charges below one. It reconciles the two by multiplying each line at full precision, rounding that line to the cent, and adding the rounded lines. Build your forecasts and reconciliations the same way, map usage products by ID rather than amount, and when a QuickBooks invoice looks a cent off from quantity times rate, check the amount: it is the number Stripe actually charged.
Every rounded line, on the right QuickBooks product. Acodei syncs finalized Stripe invoices into QuickBooks Online line by line, maps each line with your product mapping rules, and applies each payment to the invoice it paid. Start a free trial.
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
Advanced Product Mapping
Map Stripe products to QuickBooks with rule-based logic on product ID, price ID, metadata, and account. Set rule priority and extend mapping to refunds and fees.
Automated Invoice Sync
Bring Stripe invoices into QuickBooks and auto-apply payments and credit memos, with invoice numbering suffixes and quantity tracking to cut double-entry.
Multi-Currency Mastery
Sync Stripe transactions across currencies with automatic exchange rate handling and currency-specific customer records. Our team enables multicurrency on request, and zero-decimal currencies such as JPY are not supported.
Class Mapping
Map Stripe products to QuickBooks classes for scalable categorization and multi-entity reporting. Class tracking requires QuickBooks Online Plus or Advanced.
Historical Data Import
Backfill historical Stripe data into QuickBooks by month range. Preview volume and cost before syncing so reporting starts from a complete baseline.
How to Connect Stripe to QuickBooks Online
Connect Stripe to QuickBooks Online in minutes. Acodei links both accounts with secure OAuth and syncs payments, fees, refunds, and payouts automatically.
Reconcile Stripe Payments in QuickBooks
Reconcile Stripe in QuickBooks Online automatically. Acodei splits out fees, matches payouts to deposits, and keeps every charge audit-ready.
Get more operational finance guides like this one
We will only send high-value product and finance content.