Payment Platforms That Sync with QuickBooks, and How Far Back Each Goes

Short answer: Every payment platform sync into QuickBooks has a history limit, and they are not close to each other. Connect to PayPal 2.0 starts about 90 days back. The Square app reaches roughly 18 months. The Stripe connector imports up to two years. The Shopify connector starts up to 12 months back. None of them work with QuickBooks Desktop, and not one of these platforms produces a .QBO Web Connect file. Anything older than a platform's window has to arrive as a converted file.

This catches people out at the worst possible moment. You take on a new bookkeeping client in July, connect their apps, and discover the sync only reached back to April. Or you close a Square location and find the sync cannot see an account that no longer exists. The limits are all published, just never in one place, so here they are in one place.

Payment platform to QuickBooks: the reference table

Sync limits as published by Intuit's help documentation and the platforms themselves, checked July 2026. Apps change; verify the number in your own setup screen before you plan a cleanup around it.

Why do the sync windows differ so much?

Because each app was built by a different team against a different API, and the limit usually reflects what the platform is willing to serve rather than what QuickBooks is willing to store. PayPal's 2.0 app is the strictest of the group at roughly 90 days, which is also, not coincidentally, the same ceiling Intuit applies to bank feeds. Stripe's connector is the most generous at two years. Square lands in between at around 18 months.

The number that matters is the one in the setup dialog, and it appears exactly once. Most people click through it, accept the default, and only later notice that January is missing. Reconnecting rarely rescues you either, because the reconnect path is usually more restricted than the first connection was. PayPal will not let a reconnect go back further than six months.

Which payment platforms give you a QBO file?

None of them. That is worth stating plainly, because the search for a PayPal QBO or a Square QBO download consumes a lot of people's afternoons. PayPal exports CSV, tab-separated, a Desktop-only QuickBooks IIF for US accounts, and a Quicken QIF. Square exports CSV. Stripe and Shopify export CSV reports and PDF summaries. Web Connect, the .QBO format QuickBooks uses for bank feed imports, is a bank format, and these companies are not banks.

That leaves QuickBooks Desktop shops in an awkward spot, since Desktop has no native CSV import for bank activity and none of these apps run on it. Web Connect is the supported route in, so converting the PayPal statement to a QBO file or converting a Square statement to QBO is the practical path, not a workaround.

The IIF trap

PayPal's QuickBooks download looks like it solves this and does not. IIF is Intuit Interchange Format, a legacy Desktop-only text format for moving lists and journal entries. QuickBooks Online cannot open it. When Desktop accepts one, the entries post straight into the register rather than arriving in the For Review queue, which means bank rules do not fire, transactions are not matched against what is already there, and the duplicate check that a Web Connect import performs never runs. If you have ever imported an IIF and then spent an evening deleting doubled transactions one at a time, that is why.

What the sync cannot do at all

Set the history limits aside for a moment, because there are situations where no sync helps regardless of the window:

• A closed account. Shut the Square location or close the PayPal business account and there is nothing left to connect. The exports and statements you saved are the whole record.
• A client who will not share credentials. Bookkeepers get forwarded statements, not logins. That is normal and reasonable, and it means the file in your inbox is what you have to work with.
• QuickBooks Desktop. Every app in the table above is an Online product.
• A prior year being reopened. Amended returns, an audit, or a due-diligence request routinely reach back three or four years, well past every window in the table.

The fee problem is the same everywhere

All of these platforms deduct their fee before the money reaches your bank. A 100 dollar PayPal sale might deposit as 96.51. A day of 2,000 dollars in Square card sales might land as 1,940. If you book what arrived, revenue is understated by exactly the fees you paid, and the processing cost never shows up on the profit and loss. The 1099-K you receive reports gross, so the mismatch surfaces at tax time whether you planned for it or not.

The fix is structural, not clerical. Set the platform up as a bank account in QuickBooks, run gross sales, fees, and refunds through it, and treat the payout as a transfer into checking. Then the platform balance reconciles against the statement, and the deposit on the bank feed matches something instead of being posted to income a second time. Card spend is the mirror image of the same discipline, where every charge needs a document behind it, which is why plenty of teams now digitize the receipts that back up their expenses as the transactions land.

How to rebuild history past the sync window

1. Connect the app first, then look at the register and note the date of the oldest transaction it actually imported. That date, not the one in the marketing page, is your real boundary.
2. Pull statements or reports from the platform for every period before that date. PayPal generates reports up to seven years back, twelve months at a time. Square, Stripe, and Shopify hold their reports for as long as the account is open.
3. Convert each period to a QBO file and upload it, ending the file the day before the sync's oldest transaction so the two never overlap.
4. Watch the 1,000 transaction cap on a QuickBooks Online file upload. A busy month of card sales can approach it alone, so split by month rather than by year.
5. Reconcile each month against the closing balance on the statement. That is the only step that proves the rest of the work was right.

Banks have a ceiling too, and it is Intuit's

Worth knowing before you blame the platform: QuickBooks itself will not download transactions older than 90 days through any bank connection, no matter how much history the bank holds. That limit belongs to Intuit rather than to your bank, and it is explained in why QuickBooks only imports 90 days of transactions. Card issuers vary just as widely as payment platforms do, which is covered in which credit card issuers let you download a QBO file. For checking and savings, the bank statement to QBO converter does the same job as the pages above, and the QuickBooks import overview lays out every route in with its limits.

Last updated July 2026.