To import a bank statement PDF into QuickBooks on Mac, convert the PDF to a CSV with Bank Statement PDF Converter, then upload the CSV in QuickBooks Online under Transactions → Bank transactions → Upload from file. Map Date, Description, and Amount in QBO's column-mapping dialog, and import. QuickBooks can't accept a PDF directly, and the QBO/QFX bank-feed format is reserved for bank-generated files — CSV is the right path when your starting point is a PDF statement.
1. The three QuickBooks import paths, honestly
QuickBooks has three ways to get bank transactions in, and only one of them actually fits a PDF-origin workflow:
- CSV — most flexible, always works with PDFs. A generic spreadsheet file with Date, Description, and Amount columns. You pick the columns in QBO's import dialog. This is the path for any statement that started life as a PDF.
- QBO / QFX / WebConnect — bank-generated only. Signed by the bank and downloaded from the bank's online banking portal. You cannot produce one from a PDF, because the signature is the point. If your bank offers QBO download, you'd use that instead of a PDF in the first place.
- IIF — legacy QuickBooks Desktop. Intuit's older flat file format for bulk imports. Not the right tool for bank transactions anymore and not used by QuickBooks Online. If you're on a Mac in 2026, you're almost certainly on QBO and can ignore IIF entirely.
For a Mac user with a PDF statement, the answer is always convert to CSV and upload to QBO.
2. A word on QuickBooks for Mac
Intuit discontinued QuickBooks Desktop for Mac several years ago and no longer sells or supports it. Every new Mac-based bookkeeping setup today uses QuickBooks Online, which runs in any Mac browser. If you're still on an older QuickBooks for Mac install, the rest of this guide targets QBO — the CSV dialog and column-mapping rules below are QBO's.
3. Convert the PDF statement to CSV
Install Bank Statement PDF Converter from the Mac App Store. Drag your statement PDF onto the window, review the extracted table against the original in the side-by-side view, then export as CSV.
A couple of settings worth checking before you export:
- Transactions-only mode on. Strips headers, account summaries, and disclosure text so the CSV is only transactions.
- Date format. QBO accepts both
MM/DD/YYYYandYYYY-MM-DD. Either works; pick the one your other tools expect. - Signed amounts. Export with a single
Amountcolumn where withdrawals/expenses are negative. This is QBO's preferred layout.
4. Column-mapping cheat sheet for QBO
Once you upload the CSV, QuickBooks Online asks which column in your file maps to which field in its database. Use this mapping:
| Your CSV column | QBO field | Required? |
|---|---|---|
Date | Date | Yes |
Description | Description | Yes |
Amount | Amount (signed single column) | Yes |
Memo (optional) | Memo / Notes | No |
Account (multi-account statements) | Not mapped — pick the matching QBO account at upload time | No |
Leave unused CSV columns (running balance, section type) unmapped. QBO only ingests what you tell it to.
5. The split-amount-column rule
QuickBooks Online supports two amount layouts. Pick one, don't mix:
- Single signed column. One
Amountcolumn. Deposits are positive (+3215.48), expenses and withdrawals are negative (−42.17). This is the default from our CSV export and the easier option for most bookkeepers. - Two separate columns. A
Credit(or Deposit) column and aDebit(or Withdrawal) column. Each row has a value in exactly one of the two columns, never both. Don't put a sign on these numbers — they're unsigned positives, and the column tells QBO the direction.
If QBO rejects the import with an amount error, the most common cause is mixing the two — a signed value in a Credit/Debit-style file, or values in both the Credit and Debit columns on one row.
6. Upload to QuickBooks Online
- In QuickBooks Online, go to Transactions → Bank transactions (or Banking, depending on your QBO edition — Intuit moves these labels around periodically).
- Click Upload transactions (or use the dropdown next to Link account and choose Upload from file). Exact wording varies by QBO edition and region.
- Drop in the CSV from the converter.
- Pick the QBO account these transactions belong to (for example, "Chase Checking (…4321)").
- In the column-mapping dialog, match Date, Description, and Amount using the cheat sheet above.
- Confirm the preview rows look right — dates, descriptions, signed amounts.
- Import.
The transactions land in the For review tab, where QBO tries to match them against existing rules or already-recorded entries. Categorize or add from there as usual.
7. Sample CSV that imports cleanly into QBO
Date,Description,Amount,Memo
2026-04-03,"Zelle payment to ALEX R",−120.00,
2026-04-05,"Online transfer from SAV ...4321",500.00,
2026-04-07,"TRADER JOE'S #114 CHICAGO IL",−42.17,
2026-04-15,"ACH credit PAYROLL CO DIR DEP",3215.48,
2026-04-22,"ATM withdrawal 233 N MICHIGAN AVE",−80.00,Three required columns, a fourth optional Memo, signed amounts, ISO dates. This is the shape QBO wants.
8. Troubleshooting common import errors
- "We couldn't read this file." Usually a file encoding problem — make sure the CSV is UTF-8 (the converter exports UTF-8 by default).
- "Amount format is invalid." Remove any currency symbols (
$) inside the Amount column. Don't put thousands separators inside number fields (3,215.48can trip QBO depending on locale). - "Too many transactions." QBO typically caps CSV imports at around 1,000 rows per file. For a very busy business account, split the CSV by half-month and run it twice (check Intuit's current documentation for the exact limit on your plan).
- Dates parsed wrong. If rows end up in 2006 instead of 2026, the date column is being read as two-digit year. Re-export with full four-digit year (
YYYY-MM-DD).
9. Automating monthly imports
Once the first month is in, the rest is a template:
- Save the CSV export settings in the Mac app so every month produces the same shape.
- Batch-convert multiple months at once if you're catching up — the converter runs a folder of PDFs in a single pass.
- Upload each CSV to QBO against the matching account. QBO remembers the column mapping from the previous upload.
For a deeper reconciliation workflow once the data is in QBO, see the month-end reconciliation guide.
Related guides
- Month-end reconciliation on Mac — running the close after import.
- Convert bank statement PDFs to Excel on Mac — the general workflow.
- Organize bank statements for tax season — the annual view.
Convert and import
Download Bank Statement PDF Converter on the Mac App Store and produce a QBO-ready CSV from your next statement in about a minute. The iPhone & iPad app exports CSV too if you'd rather convert on the go and upload from your desktop later.
FAQ
Can I import a PDF directly into QuickBooks?
No. QuickBooks Online does not accept a raw PDF as a bank transaction import. You need to convert the statement PDF into a CSV, QBO/QFX, or IIF file first. CSV is the most flexible starting point for PDF-origin statements because it doesn't require the bank to issue the file.
What's the difference between CSV, QBO, and IIF import in QuickBooks?
CSV is a generic spreadsheet format with manual column mapping — the best fit for PDF-origin data. QBO (also called QFX or WebConnect) is a bank-generated file signed by the bank; you can't produce one from a PDF. IIF is a legacy QuickBooks Desktop format for bulk imports and isn't the right tool for bank transactions anymore.
What columns does QuickBooks Online need in the CSV?
At minimum: Date, Description, and Amount. QBO supports two amount formats — a single signed column where expenses are negative and deposits are positive, or two separate columns (one for Credit/Deposit, one for Debit/Withdrawal). A Memo column is optional. The converter exports the signed-single-column format by default.
Does QuickBooks for Mac still work?
Intuit discontinued QuickBooks Desktop for Mac several years ago and new users are directed to QuickBooks Online. If you're still running an older QuickBooks for Mac installation, the CSV import path is different from QBO's and may not support banking imports at all — migrating to QBO is the recommended path for any Mac user today.
What if my CSV fails the QBO import?
The most common causes are date format (use MM/DD/YYYY or YYYY-MM-DD), amount format (don't mix currency symbols or commas inside numbers), and row count (QBO typically caps CSV imports at around 1,000 rows per file (check Intuit's current documentation)). Splitting a busy business statement into two CSVs and re-running the import usually fixes it.