Import bank transactions into QuickBooks without a bank feed
No connection, no problem. Convert any bank's PDF statement into a CSV or a real .QBO file and upload it straight into QuickBooks — for banks it can't connect, accounts you don't want to link, and historical months a feed won't reach. Balance-validated, any bank, Online or Desktop.
CSV or QBO · any bank · balance-validated · Online & Desktop
When a bank feed isn't the answer
QuickBooks nudges everyone toward bank feeds, and for a main, supported account that's fine. But feeds don't fit every case. Your bank or card might not be connectable — common for smaller, regional and international banks. You might not want to link an account at all. Or you might need months of history a feed simply won't pull, because it only reaches back about 90 days.
In all of these, the answer is to import the transactions from a file instead of connecting a feed. QuickBooks Online takes a CSV or a QBO file; Desktop takes QBO/QFX/OFX. The only missing piece is turning your PDF statement into one of those — which is exactly what FlowParse does, extracting every transaction and balance-validating it first.
Two files QuickBooks takes
Why import, not connect
From PDF to QuickBooks — no feed
1 · Upload the PDF
Any bank, digital or scanned, any number of pages.
2 · Convert & validate
Every transaction extracted, signed, and balance-checked — download a CSV or .QBO.
3 · Upload to QuickBooks
Transactions → Link account → Upload from file (Online) or Import Web Connect File (Desktop).
Which file to import
Both skip the feed. A CSV is simplest in QuickBooks Online — a plain Date, Description, Amount table you map at import. A QBO file is the cleaner choice for repeat imports and for Desktop, because each transaction carries a FITID that QuickBooks uses to skip duplicates. FlowParse builds both from one upload, so you choose per edition and per job.
The full trade-off is in CSV vs QBO for QuickBooks import, and every method sits in the complete import guide.
| Aspect | CSV | QBO |
|---|---|---|
| Online | Yes | Yes |
| Desktop | No | Yes |
| Duplicate protection | No | Yes (FITID) |
| Mapping needed | Yes | No |
| Best for | Simple one-off | Repeat / Desktop |
For the banks a feed can't reach
Because extraction is AI-based, FlowParse reads layouts QuickBooks has no feed for — and balance-validates every file so the import is complete and correct:
See the validation engine; reconciling a year? Use Smart Merge first.
Backfilling history without a feed
The single thing a bank feed can never do is reach into the past — it pulls roughly the last 90 days and no further. So if you're setting up books for a prior year, adding an account mid-stream, or catching up a late return, the import route isn't just an alternative to a feed, it's the only option. Convert each PDF month you hold and upload it as CSV or QBO to backfill QuickBooks before reconciling.
This is the bread-and-butter of catch-up bookkeeping, and it's where validation pays off most: across many months and accounts, the balance check confirms each period is complete before it lands, so the reconciliation that follows actually balances. To bring a whole year in as one clean set, consolidate the statements first, then import by period. The wider workflow is in the bank statement processing guide.
When importing beats connecting — for good
It's tempting to treat importing as a fallback for when a feed won't connect, but for a lot of people it's the better primary method. A live feed means handing your bank login to an aggregator, accepting whatever (often terse) descriptions it sends, and periodically re-authenticating when the connection drops. Importing keeps you in control: you decide which accounts QuickBooks sees, you bring in exactly the periods you want, and the transaction descriptions are the full text the bank printed — which makes QuickBooks' bank rules categorise more of them automatically.
There's also a data-quality argument. A feed posts transactions as they clear, sometimes with codes instead of names and occasionally missing or duplicating a line when the connection hiccups. A converted statement is the bank's own record of the period, and FlowParse balance-validates it (opening + transactions = closing) before you import, so you know it's complete. For an account where accuracy matters more than real-time convenience — anything that feeds a tax return or a reconciliation you sign off — importing a validated statement is the stronger choice.
None of this means abandoning feeds. The common pattern is a feed on the one or two main accounts that connect cleanly, and imports for everything else: the unsupported bank, the card you keep separate, the foreign account, and the history that predates the feed. The two approaches coexist — and the QuickBooks import guide covers exactly where each fits.
Three situations a feed can't cover
The unsupported bank. A business banks with a regional credit union or a niche provider QuickBooks simply has no connection for. There's no feed to wait on — the only route in is to import the statement. Converting the PDF to a CSV or QBO and uploading it brings every transaction in, with the balance validated so the account reconciles.
The account you won't link. Plenty of owners are uncomfortable connecting a particular account to an aggregator, or company policy forbids it. Importing lets them keep the account unlinked and still get its transactions into QuickBooks on their own terms — full control, no shared credentials.
The history before the feed. Setting up books for a prior year, or adding an account mid-stream, means months a feed will never pull because it reaches back only ~90 days. Those months exist only as PDF statements, and importing them is the sole way to backfill QuickBooks before reconciling. Bring a year in by consolidating first, then importing per period. The wider workflow is in the processing guide.
Who imports without a feed
Businesses on unsupported banks
Bring in statements from banks QuickBooks simply can't connect to.
Accountants
Import client history without linking every account or waiting on feeds.
Bookkeepers
Catch up months that predate a feed and reconcile cleanly.
QuickBooks Desktop users
Use QBO/Web Connect files where CSV and feeds aren't an option.
Privacy-conscious owners
Keep accounts unlinked and import statements on your own terms.
Catch-up & cleanup work
Backfill a prior year from PDFs before filing or handing off.
Frequently asked questions
Can I import bank transactions into QuickBooks without a bank feed?
Yes. Instead of connecting a live feed, you upload a file: a CSV (QuickBooks Online) or a QBO/Web Connect file (Online or Desktop). This is the standard route for banks QuickBooks can't connect to, accounts you'd rather not link, and historical months. FlowParse converts any PDF statement into either file.
How do I manually import transactions into QuickBooks Online?
Go to Transactions → Bank transactions → Link account → Upload from file, choose your CSV or QBO, select the account, map the columns for a CSV, and confirm. The transactions land in the For Review tab to categorise — no feed connection needed.
Why would I import instead of using a bank feed?
Three reasons: your bank or card can't connect, you don't want to link the account, or you need historical months a feed won't backfill (feeds reach back only ~90 days). Importing covers all three, and many people use a feed for the main account and imports for everything else.
What file does QuickBooks accept without a feed?
QuickBooks Online accepts CSV (3- or 4-column) and QBO/Web Connect files; QuickBooks Desktop accepts QBO/QFX/OFX. It can't read a PDF, so you convert the statement first. FlowParse outputs a clean CSV and a real .QBO file from one upload.
Will importing without a feed create duplicates?
Only if you overlap imports or re-import a period. A QBO file carries FITID transaction IDs so QuickBooks skips duplicates automatically; with CSV there's no ID, so import each period once. If a feed also exists, don't import dates it already covers.
Can I import statements from a bank QuickBooks can't connect to?
Yes — that's the main use. FlowParse uses AI extraction rather than per-bank templates, so any bank's PDF statement converts to a QuickBooks-ready CSV or QBO, including smaller, regional and international banks QuickBooks has no feed for.
Does this work for QuickBooks Desktop?
Yes. Desktop imports QBO/Web Connect files via Banking → Bank Feeds → Import Web Connect File. Since Desktop doesn't take plain CSV, converting your PDF to a .QBO file with FlowParse is the cleanest no-feed route.
How do I import historical transactions without a feed?
Convert each historical PDF statement and upload it as CSV or QBO. Because a feed only reaches ~90 days, this is the only way to backfill older months — and FlowParse converts any month you have a statement for.
Is the imported data accurate?
FlowParse reaches around 98% field-level accuracy and balance-validates every file (opening + transactions = closing) before you import, so a misread or missing line is flagged rather than silently added to QuickBooks.
Do I have to enter transactions by hand?
No. Manual keying is exactly what this avoids. FlowParse extracts every transaction from the PDF into the file, so QuickBooks loads them in one import — you only review the few fields the validation flags.
Can I import credit-card transactions without a feed?
Yes. Credit-card PDF statements convert the same way and import against the matching card account, with charges as money out and payments as money in so the balance reconciles.
Is it free to try?
You can convert within the monthly page allowance and preview the transactions first; QBO bank-feed file export and accounting exports are part of the paid plans for ongoing volume.
Where do imported transactions go in QuickBooks?
In QuickBooks Online they land in the For Review tab, where you categorise and match them before they're added to the register; in Desktop they appear in the Bank Feeds Center. Bank rules can auto-categorise recurring transactions.
What if my CSV won't import?
Usually it's extra header rows, mixed date formats, or amounts with symbols. FlowParse outputs a clean QuickBooks-ready CSV that avoids these. For a full list of fixes, see the guide to fixing QuickBooks bank import errors.
Can I do this at scale for many clients?
Yes. Accountants convert each client statement with validation on and import per account and period; the batch converter and the bank statement API handle higher volume without manual handling.