Stripe gives you CSV reports and a legacy IIF file buried in Legacy Exports. It does not produce a .QBO, and QuickBooks Online cannot read an IIF at all. Upload your Stripe payout report or balance statement here and get a real Web Connect QBO that both versions of QuickBooks import. Start free, no credit card.
Last updated July 2026
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF, MT940
Uploading...
Upload the Stripe payout report, balance report, or statement PDF to BankXLSX and choose QBO as the download format. Stripe offers no QBO download of its own: its reports come as CSV, plus an IIF file for QuickBooks Desktop that QuickBooks Online cannot open and that bypasses the bank feed even in Desktop. The converted QBO imports into your Stripe clearing account exactly like a bank download, for any period Stripe recorded.
Stripe documents every cent it moves, then hands it over in two formats, neither of which QuickBooks treats as a bank feed.
Stripe reports export as CSV from the Dashboard. The only accounting-specific file it offers is an IIF, downloadable from Legacy Exports. Web Connect is not on the menu, so if your accountant asked for a QBO, Stripe has no way to hand you one.
Stripe's own documentation says it plainly: you cannot import IIF files into QuickBooks Online. The IIF exists for QuickBooks Desktop, which leaves every QuickBooks Online user with a CSV and no supported file route.
Even in Desktop, an IIF posts entries straight into the register rather than dropping them into the For Review queue. Bank rules never fire, nothing gets matched against existing transactions, and the duplicate protection a Web Connect import gives you simply is not there.
The Stripe connector for QuickBooks Online lets you pick a start date up to about two years back. That covers most cleanups, and none of the older ones. A three-year catch-up, or a closed Stripe account, is outside what the app will import.
Stripe deducts its per-charge fee, then nets out refunds and disputes, before the payout lands. So the bank deposit never equals your gross charges, and booking the deposit as revenue understates income and hides the processing cost.
A single Stripe payout covers many charges across a rolling window. Without the charge-level detail behind it, nobody can tell which sales a given deposit represents, and reconciliation stalls on exactly that question.
Upload the Stripe report and get a valid Web Connect file, for any period, with the fee kept as its own line.
You get an actual .qbo with the structure QuickBooks expects, which is what Desktop needs and what QuickBooks Online treats as the cleanest upload it takes. No IIF workarounds.
A report carries no sync window with it. Convert a period from three years ago, or rebuild a Stripe account you have since closed, without the connector deciding how far back you may go.
The Stripe fee stays its own line rather than being netted into the charge, so revenue books at gross and the processing fee books as the expense it is.
Refunds, disputes, and dispute fees come across with the right sign, so the Stripe balance in QuickBooks tracks the balance Stripe shows.
Each payout stays intact as its own transaction, which is what lets you match a Stripe payout to the deposit sitting on your bank feed.
256-bit encryption in transit, and you can delete your uploaded files whenever you want.
No software to install and no credit card to start.
In the Stripe Dashboard open Reports, or open Balance and export the payout report for the period you need. A statement a client forwarded works just as well. Drag the file into the box above.
Tip: The payouts report carries the gross, the fee, and the net.
Once the transactions are read, pick QBO as the download format. QFX, OFX, CSV, and Excel sit next to it.
Tip: Pick QFX if the target is Quicken.
QuickBooks Online: Transactions, Bank transactions, Upload from file. Desktop: File, Utilities, Import, Web Connect Files. Select the Stripe clearing account, which most books set up as a bank account.
Tip: One account per file.
Stripe is the checkout for a large share of US SaaS companies, agencies, marketplaces, and subscription businesses. It records the charge, the fee, the refund, and the dispute in full detail, and then pays out a batched net figure that tells your bank almost nothing. Everything an accountant needs lives on the Stripe side of that gap.
The client sends the Stripe report, not the Dashboard login. Convert whatever period you were handed and post it correctly, without waiting on access you may never get.
Recurring charges, prorations, refunds, and failed payments all need to survive into the books at gross, not collapse into a single monthly deposit.
The sync stops around two years back. A longer rebuild has to come in as converted reports, month by month.
Stripe offers Desktop only a legacy IIF that skips the review queue. Web Connect is the supported route in, and a converted report is a proper Web Connect file.
Yes, through three routes, and they are not equivalent. The Stripe connector for QuickBooks Online syncs live and reaches about two years back. Stripe's own IIF file works only in QuickBooks Desktop and only as a journal-style import. And a converted Stripe report produces a Web Connect .QBO that either version imports properly, for any period. The route you pick decides how much history you get and whether the fee survives as its own line.
| Path | File or method | History reach | Works with QuickBooks Desktop? |
|---|---|---|---|
| Stripe connector for QuickBooks Online | Live app sync | Start date up to about two years back | No, QuickBooks Online only |
| Stripe Dashboard reports | CSV | Any period | Not as a bank feed |
| Stripe legacy export | IIF, from Legacy Exports | Any period | Desktop only, and it bypasses the review queue |
| Converted Stripe report | A real .QBO Web Connect file | Any period | Yes |
The shape of this is familiar from every bank and every processor: the live connection owns the current period, and everything behind it has to arrive as a file. Stripe just adds a twist, because the only accounting file it ships is a format from the 1990s that half of QuickBooks cannot open.
No. Stripe exports its reports as CSV, and offers an IIF file for QuickBooks Desktop under Legacy Exports in the Dashboard. There is no Web Connect option anywhere. Stripe's documentation is direct about the consequence: IIF files cannot be imported into QuickBooks Online, and it points users to third-party integrations instead. So a QBO has to be produced by converting the report.
Because IIF was never a banking format. Intuit Interchange Format is a Desktop-only text format built for moving lists and journal entries, and QuickBooks Online cannot open it at all. When Desktop does take one, the entries post straight into the register instead of arriving in the For Review queue, so your bank rules never run, nothing is matched against existing transactions, and the duplicate protection of a Web Connect import is absent. It is the difference between filing transactions and importing a bank feed.
Because Stripe nets everything out before it pays. A payout is gross charges, minus the per-transaction processing fee, minus refunds issued in that window, minus disputes and dispute fees. So 10,000 dollars of charges might deposit around 9,660. Book the deposit as revenue and you understate income by the fee and never record the processing cost, which quietly distorts margin all year.
Yes, as a clearing account of the bank type. Charges and fees post into it, payouts leave it, and each payout then matches the deposit on your real bank feed as a transfer between two accounts. That structure also makes the Stripe balance meaningful, because money customers have paid but Stripe has not yet released sits in the clearing account rather than being invisible until it lands.
Duplicates happen when a live sync and a converted file overlap. Open the Stripe clearing account register, find the oldest transaction the app brought in, and end your converted file the day before it. Load history behind the sync, never on top of it. If you are rebuilding a busy year of charges, check how many transactions QuickBooks accepts at once first, because a QuickBooks Online upload caps at 1,000 lines and a year of Stripe charges clears that easily.
The same upload produces more than a QuickBooks file. Take XLSX or CSV instead with the Stripe statement to Excel converter when you want to sort and total a year for a tax return. The step-by-step version of this page is how to import Stripe transactions into QuickBooks, and if the deposit that does not match your charges is what sent you here, why ecommerce sales never match the bank deposit works through the arithmetic. The sibling processor pages are Shopify statement to QBO, PayPal statement to QBO, and Square statement to QBO, and the general case is the bank statement to QBO converter.
If you already pulled a Stripe CSV report and simply need it in Web Connect form, a dedicated CSV to QBO converter does that one job. When statements from several institutions are all heading into the same QuickBooks file, a purpose-built bank statement to QuickBooks converter runs the PDF to QBO workflow across all of them.
Yes. The Stripe connector syncs into QuickBooks Online and reaches about two years back. Stripe also offers an IIF file that only QuickBooks Desktop reads. For older periods, or for a clean Desktop import, convert the Stripe report to a QBO Web Connect file and import it into your Stripe clearing account.
No. Stripe exports reports as CSV and offers an IIF file under Legacy Exports for QuickBooks Desktop. Web Connect is not offered, so the only way to get a .QBO out of Stripe data is to convert the report or statement.
No. Stripe's own documentation states that IIF files cannot be imported into QuickBooks Online. IIF is a QuickBooks Desktop format, and even there it posts entries directly into the register instead of arriving in the For Review queue as a bank feed would.
About two years. When you connect the app you choose a start date, and roughly 24 months is the limit on historical transactions. Anything older, including a closed Stripe account, has to come in as a converted file.
Stripe deducts its per-charge processing fee, refunds, and disputes before releasing the payout, so the bank deposit is always less than gross charges. Booking the deposit as revenue understates income and leaves the processing cost off your books entirely.
Yes, as a clearing account of the bank type. Charges and fees post into it and payouts leave it, which lets you match each Stripe payout against the deposit on your real bank feed as a transfer rather than double counting revenue.
Book the charge at gross and the Stripe fee as a separate merchant fee expense. Recording only the net that landed understates revenue and hides the processing cost. A converted report keeps the charge and the fee on separate lines so both post correctly.
The same report as XLSX or CSV instead.
The store platform whose sync stops at one year.
The processor that never made a QBO file at all.
Convert any bank statement to a QBO file.
Every QuickBooks import path, and the limits on each.
Z tej samej rodziny narzędzi
Get started converting bank statements to spreadsheets.
USD
per month
billed as
$288 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion across your team with automation.
USD
per month
billed as
$888 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise-grade bank statement conversion and controls.
USD
per month
billed as
$ yearly
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
