Stripe Invoice Quantity in QuickBooks: Why It Says 1

You sell 12 seats at 40 dollars each. Stripe's invoice says what you would expect: quantity 12, unit price 40, total 480. The invoice syncs into QuickBooks, the 480 lands on the right income account, the deposit reconciles, and the month closes clean.

Open that QuickBooks invoice and look at the Qty column. It says 1.

Not 12. One line, quantity 1, the full 480 sitting in the amount. The money is right. The seat count is gone, and it went quietly, because nothing in your close process reads the Qty column.

Start a free trial and see how your Stripe invoices post into QuickBooks.

The two-sentence version

Acodei's default writes a hard-coded 1 into the quantity field on every synced invoice line. There is a setting that changes it, it is not self-serve, and one common tax configuration rules it out entirely.

Everything below is what that costs, how to tell in five minutes whether it is costing you anything, and the detail about Stripe quantities that catches people out even after they turn the setting on.

Read the setting backwards and it tells you the default

Acodei documents an invoice quantity setting in two places, and both describe it by what it changes rather than by what happens without it.

The admin feature list calls the toggle Enable Qty tracking on Invoice, and describes it in one line: "Writes Stripe quantity (not hard-coded '1')." The typical reason to turn it on is given as "Inventory or unit-based reporting in QBO," with one dependency noted: "Incompatible with inclusive tax invoices."

The Invoice Sync documentation lists the same thing under advanced configuration as Quantity Tracking: "Pushes Stripe quantities instead of hard-coded 1 per line. Not available with inclusive tax. Requires backend enablement." Its default value is listed as Off.

Read either description backwards and you have the default behavior. Off is the documented default, and off means the line carries a hard-coded 1.

Why the money still reconciles, and why that is the problem

If the quantity were wrong in a way that moved the dollars, you would have found it in week one. A 480 dollar invoice arriving in QuickBooks as 40 dollars is the kind of error that surfaces the first time someone compares Stripe's payout to the deposit.

That is not what happens. Invoice Sync is documented as reproducing "every line-item, and tax lines, as allowed by the user's mapping settings," and the value of the line comes across intact. Your revenue is right, your A/R is right, your deposit matches, and your accountant has no reason to look further.

Acodei's own validation works the same way. The Invoice Sync documentation lists a check that compares "the final invoice generated in QuickBooks to ensure it matches the Stripe invoice amount exactly," and it qualifies that check as "only applicable if tax is enabled." Note what is being compared: an amount. A quantity mismatch has nothing in that check to trip.

So the default fails in the one direction nothing in your process is watching. Every dollar-denominated control agrees. The unit columns are the only place the difference exists, and unit columns are read by people doing analysis, not by people doing reconciliation. Those are usually different people, often looking months apart.

Three places it actually costs you

1. Inventory quantities and cost of goods sold

This is the expensive one, and it is the reason the toggle's documented use case leads with the word "Inventory."

QuickBooks Online moves inventory on the quantity of a sales line, not on its dollar value. Intuit is explicit that "COGS is debited only when you sell inventory items on invoices or sales receipts. At the same time, the Inventory Asset account is credited," and that the amount moved is "Number of Items Sold x Average Cost of Item." Intuit's costing article makes the same point from the other direction: "QuickBooks Online will always consider the first units purchased (First In) to be the first units sold (First Out)."

Every one of those mechanisms takes units as its input.

Sell 12 units on a Stripe invoice that syncs as quantity 1, and QuickBooks relieves inventory for one unit. Eleven units of cost stay sitting in the Inventory Asset account instead of moving to COGS. Your revenue is complete and your cost of sale is not, so gross margin comes out too high. Meanwhile quantity on hand drifts up against reality by 11, and it drifts in the same direction every single time, so the gap grows monotonically rather than averaging out.

The month you finally catch it is the month you count the shelf. The Inventory Valuation Summary report shows "the quantity on hand, value, and average cost for each product," and it will disagree with your physical count by an amount nobody can explain from the transactions, because every transaction looks individually correct.

2. Unit-based reporting

Intuit's Sales by Product/Service Detail report shows "your sale transactions by product or service," and its QTY column is where most people go to answer how many of something they sold.

With the default in place, that column is not a unit count. It is a count of invoice lines. Ten invoices for 3 licenses each and ten invoices for 300 licenses each produce the same number: 10.

The number is not obviously broken, which is what makes it dangerous. It is a plausible integer that shows up in the right place on a real report, and it will be quietly wrong for as long as nobody compares it against Stripe.

3. Anything priced per unit

Stripe describes quantity on a subscription as "per-seat licensing, which has a linear cost increase: 10 uses incurs a cost of 10 times the base price." That linearity is the whole point of the model, and it is exactly the information that a hard-coded 1 discards.

Divide revenue by units in QuickBooks and you are not getting average selling price. You are getting average invoice line value, which for a per-seat business is a number about your customer sizes rather than about your pricing. Cohort work, price-increase analysis, and anything that needs revenue per seat all inherit the error.

The five-minute check

You do not need to reason about your configuration. You can look.

1. Open any recent Stripe-originated invoice in QuickBooks Online. Look at the Qty column on a line you know represents more than one unit. If it reads 1 while the rate reads the full line value, you have the default.
2. Run Sales by Product/Service Detail for a full month. The QTY column is not on by default: choose Customize, open Rows/Columns, tick QTY, then run the report.
3. Compare the QTY total for one product against the same month in Stripe. If the QuickBooks number matches your invoice line count rather than your unit count, that confirms it.

If step 3 comes out equal to your unit count, quantity tracking is already on for your account and there is nothing here for you to do.

Turning it on, and the one condition that decides whether you can

Two things to know before you ask.

It is not a checkbox you can find. The Invoice Sync documentation says quantity tracking "requires backend enablement," and it appears in Acodei's advanced feature set rather than being documented as a self-serve dashboard option. Enabling it means asking support, not hunting through your account.

Inclusive tax rules it out. Both Acodei sources say so plainly: "Not available with inclusive tax" and "Incompatible with inclusive tax invoices." If your Stripe prices are tax-inclusive, which is common in VAT and GST markets, this setting is not available to you. That constraint is worth understanding on its own terms, and we wrote up what inclusive versus exclusive tax changes about your QuickBooks records separately rather than repeating it here.

There is one documented exception on the tax side that people miss. Acodei's tax documentation records that quantity tracking and Stripe Tax can be used together for United States companies: "U.S.-based companies using Stripe Tax can enable Invoice Quantity Tracking as well." If you are US-based on Stripe Tax with exclusive pricing, being on Stripe Tax is not the blocker you might assume it is.

So the decision comes down to two questions in order. Are your Stripe prices tax-inclusive? If yes, stop, this setting is not on the table. If no, ask support to enable it.

The part that surprises people after they turn it on

Quantity tracking gives you the quantity on the Stripe line item. That is not always the same number as the count of the thing you sell, and the gap is deliberate.

Stripe supports quantity transformation, which lets you "instruct Stripe to transform the quantity before applying the per unit cost." Stripe's own worked example is a suite that charges 10 dollars for every 5 users: 6 users is reported to Stripe as a quantity of 2, and 3 users is reported as a quantity of 1. The billing is correct. The quantity on the invoice line is a billing unit, not a headcount.

There is a precision detail in the same territory. Stripe's invoice line item object documents quantity as "quantity of units for the invoice line item in integer format, with any decimal precision truncated," and holds the full value separately in quantity_decimal. Usage-based lines are where fractional quantities show up, so if you bill on gigabytes or fractional hours, the integer field is a rounded version of what you actually metered.

None of this is an argument against turning quantity tracking on. It is an argument for knowing which number you are about to start reporting on. If your Stripe prices use quantity transformation, the QuickBooks Qty column will faithfully reproduce Stripe's billing quantity, and building a seat-count dashboard on top of it will give you a number that is correct and not the one you wanted.

What about invoices you already synced

Changing a setting is not the same as restating history, and it is worth being precise about the difference rather than optimistic.

Acodei documents a resync as the way an already-synced record gets rebuilt: the resync action deletes the invoice and payment and adds them again. Its stated best practice is to "resync from the Data Feed instead of manually altering transactions in QBO," which is also the answer to the tempting shortcut of opening a synced invoice and typing the quantity in by hand. We covered how resyncing a Stripe invoice actually behaves in more detail elsewhere.

What Acodei's documentation does not state is what a resync produces for historical invoices under a setting that was off when they were first written. That is a question worth asking support directly before you plan a backfill around the answer, especially if the months in question are closed.

The pragmatic path for most businesses: turn it on, let it apply going forward, and treat the historical period as a known gap in unit reporting rather than something to restate.

One scoping note

Everything above concerns the invoice workflow, where Stripe invoices become QuickBooks invoices and payments. The setting is named for it, and Acodei documents it under Invoice Sync's advanced configuration.

If your account posts sales as receipts rather than invoices, the documented behavior above does not describe your records, and the right move is to ask support what your setup writes rather than assume the invoice behavior transfers. The broader map of which sync settings change presentation and which change your numbers is in our rundown of Acodei's sync settings and what each one does to your books.

Frequently asked questions

Does a quantity of 1 mean my revenue in QuickBooks is wrong?

No. The line amount carries the full value of the line, so income, A/R, and your deposit reconciliation are unaffected. What the default costs you is the unit columns: inventory quantities, cost of goods sold on inventory items, and any report that counts units rather than dollars.

Can I turn on quantity tracking myself?

No. Acodei's Invoice Sync documentation states that quantity tracking "requires backend enablement," and the toggle sits in the admin feature set rather than in your dashboard. Contact support to have it enabled on your account.

Can I use quantity tracking with inclusive tax?

No. Both Acodei sources state the incompatibility directly: "Not available with inclusive tax" and "Incompatible with inclusive tax invoices." Being on Stripe Tax is a separate question, and Acodei's tax documentation records that "U.S.-based companies using Stripe Tax can enable Invoice Quantity Tracking as well."

Will enabling it fix invoices that already synced with quantity 1?

Acodei documents resync as the mechanism for rebuilding an already-synced record, and it recommends resyncing from the Data Feed rather than editing transactions in QuickBooks by hand. What a resync produces for historical invoices under a newly enabled setting is not something the documentation states, so confirm it with support before planning a backfill.

Why does my QuickBooks quantity not match my seat count even with tracking on?

Most likely because your Stripe price uses quantity transformation. Stripe transforms the quantity before applying the per unit cost, so a price billed per 5 users reports 6 users as a quantity of 2. QuickBooks receives Stripe's billing quantity, which is the right number for revenue and the wrong number for headcount.

Which product does the synced line use?

The product comes from your mapping rules. Acodei's Invoice Sync documentation states that each invoice line uses the product returned by Multiple Product Mapping when it is enabled, and the default product otherwise. That is a separate concern from quantity, and we explain the rule engine in our guide to multiple product mapping.

The short version

The default is a hard-coded 1, it is invisible to every dollar-based check you run, and it costs you exactly the reporting that made you set up products in QuickBooks in the first place. Five minutes with the Qty column tells you where you stand.

If your Stripe prices are tax-exclusive and units matter to you, this is a one-message fix. If they are tax-inclusive, it is a constraint worth designing around rather than discovering during a stock count.

Start a free trial and see exactly how your Stripe invoices land in QuickBooks before you commit to anything.

Sources: Stripe's invoice line item object and subscription quantities documentation; Intuit on inventory assets and cost of goods sold tracking, inventory valuation methods, and reports for sales and inventory status.