Import a PDF Bank Statement into QuickBooks

Intuit's current documentation includes PDF and image statement uploads. If you already use QuickBooks Online, check that option before buying a conversion. It may handle the statement you need without an extra service. Direct import is especially worth trying for an ordinary English-language statement and a single account.

Sonomir is a separate workflow: read the PDF, inspect the extracted rows and arithmetic checks, and keep an Excel or accounting-format file outside QuickBooks. That can help when a client provides an archive of statements or you want to review the dates and amounts before an import. It does not connect to your bank, categorise expenses or replace reconciliation in your books.

The Online upload instructions were checked on 6 October 2026. This is a documentation check; Sonomir imports have not yet been tested inside QuickBooks.

Desktop's Web Connect route uses a .QBO file. Back up your company file, then choose File → Utilities → Import → Web Connect Files and select the download. Choose the matching bank or card account and review the imported rows. These steps were checked on 6 October 2026 against Intuit's Desktop guidance. Your installed version and bank-feed eligibility still matter.

For Online, open Bank transactions → Upload from file. Select the account and reviewed file, map fields if requested, then inspect the preview before accepting. CSV needs a three-column Date, Description, Amount layout or a four-column Date, Description, Credit, Debit layout, consistent dates, and a file within Intuit's size and row limits: 350 KB and 1,000 transactions.

Choose QuickBooks Online · 3 columns or · 4 columns in the CSV layout selector. Each file uses DD/MM/YYYY and at most 999 transactions plus its header. Files are also split at 350,000 UTF-8 bytes; multiple statements and split files download in one ZIP. The four-column option follows Intuit’s example: payments in Credit, deposits in Debit. Keep the full transaction CSV as your review copy. The bank statement to CSV page explains that preparation. QBO avoids a CSV mapping step, but it still needs review.

The QBO file uses Wells Fargo's bank code, 3000, because the PDF has no Web Connect institution identifier. QuickBooks may therefore display Wells Fargo even for a different source bank. Choose your own destination account; the label does not create a Wells Fargo connection. See the PDF to QBO page for the file structure, and fixing "unable to verify the Financial Institution information" if QuickBooks refuses the bank code.

If the preview shows a purchase as money received, inspect your CSV mapping and sign convention before continuing. Do not map Balance as Amount. Import one account and period at a time, and remove overlap with existing bank-feed transactions. Stable IDs in a repeated download do not guarantee a match to transactions already imported from another source.

Intuit documents the error "The uploaded file is of a different type than these accounts." Check that you chose the correct bank or credit-card account. Its upload troubleshooting guide also covers timeouts and invalid amounts. Keep the exact error and your product version when requesting help.

With the two daily free pages unused, a three-page statement needs one paid page, with downloads included: $0.25 at the $5-pack rate or $0.30 at the $3-pack rate. With no free pages remaining, it needs three paid pages. The smallest purchase is $3 for 50 credits, with credits left over kept in your wallet. A result that used only free pages charges 2 credits for CSV or QBO once per result.

A bank-issued QBO download is preferable when available because it avoids extracting transactions from a PDF. For regular high-volume conversions, subscriptions can be cheaper; ProperSoft also processes on your computer rather than uploading documents to a cloud model. Sonomir suits occasional PDFs that need a reviewed output.

Matching balances cannot rule out missing offsetting rows or incorrect descriptions. Compare the transaction count, dates and important amounts with the source before importing. The PDF statement workflow covers that review, and importing a PDF bank statement into QuickBooks compares Intuit's own PDF upload with CSV and QBO step by step. No "tested in QuickBooks" claim is made until a real import is recorded.

Upload a bank statement — the PDF your bank emailed, a scan, or phone photos of the pages — and every transaction comes back as a row: date, description, money out, money in, a signed amount and the running balance. Transactions from every page land in one table, so a twelve-page statement is one list, not twelve fragments to stitch together.

Then comes the part that matters: the tool checks its own work. It adds up what it read and compares the result with the balances printed on the statement. When they agree to the cent, the extracted amounts are consistent with those balances. Offsetting errors can still cancel out, so a passing check is a useful review aid, not proof of accuracy. When they do not, it tells you by how much and flags the rows where the running balance breaks, so you check three lines instead of three hundred.

Two independent checks run on every statement.

1. Opening + money in − money out = closing. The opening and closing balances are read from the statement's summary or its first and last lines. If the transactions read in between do not produce the closing balance exactly, something is missing or wrong, and the difference is shown.
2. Row by row. Where the statement prints a running balance, each one must equal the previous balance plus that line's money in minus its money out. A break points straight at the problem: the flagged row, or the one just above it.

The arithmetic is done in whole cents, never in floating point, so a check cannot pass by rounding. Statements listed newest-first are recognised, and so are card and loan statements, where the balance is money owed and runs the other way.

A passing check shows that the extracted amounts agree with the balances that were read. It cannot rule out offsetting errors, omitted pairs of transactions, or incorrectly read balances. Check dates and descriptions, compare the row count with the source, and review important amounts before importing.

The Excel workbook has three sheets:

• Transactions — one row per transaction, in the order printed, with the page it came from and a Check column that says why a row was flagged.
• Balance checks — each check, whether it passed, and the numbers behind it.
• Statement summary — bank, the last four digits of the account, period, currency, opening and closing balances, totals, and whether it reconciles.

Amounts are stored as numbers, not text, so SUM works straight away. Dates are written as year-month-day when the statement makes the year clear, which sorts correctly everywhere. Choose the full transaction CSV to keep the review columns, or a QuickBooks Online, Xero or YNAB CSV layout for its documented import fields. All layouts share one CSV purchase for the same result. Accounting layouts leave out balances and check notes; each statement has a separate file, and multiple files download as a ZIP.

Upload several PDFs at once — twelve monthly statements, say — and they come back in one workbook with a Statement column, plus a summary row for each.

A PDF downloaded from online banking often already contains its text. That text is read with its printed column positions before a model turns it into records. This avoids recognising letters and digits from pixels, but the model can still misinterpret a column or a wrapped description.

A scanned statement, or photos of printed pages, is read from the image. That works well on a flat, straight, well-lit page. It struggles with faint thermal-style printing, pages shot at an angle, and folds across the amount columns. The balance check is your safety net here: if a digit was misread, the running balance breaks at that row.

Photos uploaded together are treated as the pages of one statement, in the order you chose them. Each PDF is its own statement.

It is built for current, checking and savings account statements, and reads card and loan statements too. It is not built for investment or brokerage statements, where a row is a holding rather than a movement of cash. If your bank locks its statements with a password, enter it when the page asks: the PDF is unlocked in your browser, the password never leaves your device, and only the unlocked copy is uploaded. Without the password the tool cannot open it and will not try to get around it.

It has not been tested against a named list of banks, and this page will not pretend otherwise. Statement layouts vary enormously; what the tool offers instead is a result you can verify. If the checks pass, the extracted numbers agree with the balances read from the source. If they fail on your bank's layout, the job tells you so plainly.

We compared the model's extracted rows with labelled, fictional statements: separate debit and credit columns, signed amounts, German decimal commas, Indian number grouping, wrapped descriptions, a dense multi-page list, a credit card, scans and phone photos. These are synthetic examples, not a certification for any named bank.

The eight text-PDF cases and two scanned-PDF cases matched every labelled date, description, amount and direction in this run. A photographed statement lost a digit from two transaction descriptions even though its balance checks passed. Review the source rows, especially long reference numbers in photos. Results can vary between runs; this test does not establish an accuracy percentage for your files, mixed-currency support or successful imports into accounting software.

Compare QBO, QFX, OFX and QIF before importing. The Xero CSV page explains its preset, while password-protected statements covers opening a PDF with your own password. For spreadsheet review, use Google Sheets. Each route uses the same converter; no accounting-app import pass is claimed. Still need the statement itself? How to extract a bank statement covers downloading it from online banking, and getting a year of statements ready for your accountant covers tax-season batches.

Statements are sensitive, so here is exactly what happens. The uploaded file is sent to the reading model and deleted from storage when the job ends, whether it succeeded or not. Only the last four digits of an account number are kept. The transactions you see are stored with your job so the download still works if you come back later; use Delete this result to remove it sooner. Nothing you upload is ever published. To weigh this against other converters, see is it safe to use a bank statement converter?

The first 2 pages a day are free, with the balance checks, and you can copy every row you see. That is enough to see whether the tool reads your bank's layout correctly before you pay anything.

Past that, pages are $0.25 each (5 credits, at the $5-pack rate), and a statement with paid pages gets every download free: Excel, CSV, QBO, QFX, QIF and OFX. With the two free pages still available, a six-page statement costs 20 credits for the other four pages, workbook included. If you have no credits, the smallest purchase is $3 for 50 credits, before any applicable tax; the statement uses $1.20 of it and 30 credits remain. A statement that fits inside the free pages downloads as Excel or CSV free; QBO, QFX, QIF and OFX are 2 credits, once per job. Credits never expire, there is no subscription, and a job that fails is not charged.