Stop watching your Stripe income pile up under "Unspecified". sush.io assigns QuickBooks classes as it syncs — one per transaction, or one per line, with a class mapped to each Stripe product.
You set up classes in QuickBooks Online to see revenue by product line, location, program or fund. Then your payment processor sends over a wall of undifferentiated income. If the sync that creates those entries doesn't set a class, every dollar Stripe collects lands under "Unspecified" — and your class-based P&L stops being usable exactly where your revenue actually comes from.
The usual workaround makes it worse. Opening each transaction and re-selecting the product to make a class appear rewrites the line rate to that item's default sales price in QuickBooks. A $1,500 charge quietly becomes $150 — understating both your revenue and the deposit it reconciles against. Classification you have to do by hand is classification that damages your books.
Every entry sush.io posts carries its class from the moment it's created — sales receipts, invoices and deposit lines alike. No monthly clean-up pass, no reclassification job, nothing to reopen in QuickBooks.
Pick the level that matches how you report. One class for the whole transaction, or a class on each line — so a single Stripe charge covering two revenue streams splits across two classes in your P&L.
sush.io lists the products from your Stripe catalog and you assign a QuickBooks class to each one. From then on, the class follows the product automatically — new customers, new charges, new months, no upkeep.
Unmapped products, refunds, discount lines and anything ambiguous keep your default class instead of being classified at random. Amounts, items and tax are never rewritten to make a class fit.
Both are set in the same two-minute step of the setup wizard, and both can be changed later without re-connecting anything.
The class goes on the transaction header. The simplest setup when one Stripe account maps to one class — a single location, a single department, a single fund.
Requires class tracking enabled in QuickBooks Online.
Set a default class, then map individual Stripe products to their own class. Each line of the QuickBooks entry gets the class of the product it sells; anything unmapped uses the default.
Requires "assign classes to transaction lines" enabled in QuickBooks Online.
sush.io reads your Stripe catalog and shows it next to your QuickBooks class list. Pick a class per product, save, and every future charge for that product carries it.
QuickBooks deposits have no class field on the header, so the class has to be written on every single line — and it is: sales, Stripe fees, adjustments. The bank side of your books gets classified too, not just the revenue side. See the full Stripe sync →
Class tracking and tax handling are applied on the same entry: net revenue on the right income account, tax on its own line with the matched code, and the class where it belongs. One sync, both dimensions correct.
See how tax sync works →One flat price: $7.40/month, billed yearly at $89. Unlimited transactions, full history, class tracking and taxes included — no add-ons. See pricing →
Class tracking is also available on the Braintree + QuickBooks automation.
Yes. Classes are applied automatically to the entries sush.io creates in QuickBooks Online — on the whole transaction, or line by line. Stripe and Braintree automations both support class tracking.
Yes. In line-by-line mode, sush.io lists your Stripe products and you pick a QuickBooks class for each one. Products you don't map fall back to your default class.
No — and you shouldn't. Re-selecting a product on an existing QuickBooks line resets its rate to the item's default sales price, which silently changes the amount. sush.io writes the class when the entry is created, so nothing has to be touched afterwards.
Yes. QuickBooks deposits have no header-level class field, so sush.io writes the class on each deposit line — sales, Stripe fees, adjustments — instead of relying on QuickBooks to fill it in.
Class tracking must be turned on in your QuickBooks account, and "assign classes to transaction lines" is required for per-product mapping. sush.io reads those preferences directly and warns you if a class is configured but tracking is off in QuickBooks.
No. Classes are written when an entry is created, so mapping changes affect new syncs, not entries already in QuickBooks. You can change your mapping at any time and it takes effect on the next sync.
Your default class is used. sush.io resolves the product from the Stripe transaction and never guesses: if two mapped products share the same name, or a charge carries no product information at all, the transaction falls back to the default class rather than being classified at random.
More questions? Browse the documentation or contact us — a real person answers.