How to upload bank statements to QuickBooks Online: PDF, OFX or CSV

Three ways to get statement transactions into QuickBooks Online

If you are working out how to upload bank statements to QuickBooks Online, start with why the transactions are missing. When you connect a bank or credit card account, QuickBooks downloads transactions automatically, but only back to a certain date. Intuit’s help article on manually uploading transactions describes the manual route for two situations: the bank cannot be connected, or you need transactions from before the connection started.

QuickBooks Online then gives you two kinds of upload. You can upload an account statement as a PDF or image (JPG, PNG or HEIC), which QuickBooks reads with AI and shows in a side-by-side view for you to check. Or you can upload a list of transactions as a .csv, .txt, .qbo or .ofx file through Upload from file. A converter such as Fulla Ledger sits in front of the second route: it turns the PDF into an OFX or CSV file you have already reviewed.

PDF, OFX, CSV or QBO: which file should you upload?

Each route suits a different situation, and none of them is wrong. Choose based on how many statements you have, how you want to review them, and what your bank can export.

• PDF or image straight into QuickBooks Online: convenient for an occasional English-language statement. QuickBooks extracts the transactions, may flag items that need review, and shows a side-by-side view before you save.
• OFX from Fulla Ledger: useful when you want to check every row against its source page before import, convert up to 10 PDFs in one upload, handle scanned or password-protected statements, or send the same approved data to Excel or another system too. Labelled fields mean no column mapping.
• CSV: works when you need to edit the data in a spreadsheet first. QuickBooks expects either three columns (Date, Description, Amount) or four (Date, Description, Credit, Debit), so a richer CSV must be trimmed or mapped. The CSV to QBO guide covers that layout in detail.
• QBO Web Connect from your bank: Intuit suggests this format when your bank offers it. It is created by the bank; Fulla does not produce .qbo files.

Before you upload: limits and prerequisites

Intuit lists a few rules for transaction list uploads. The file must be in English and 350 KB or less, and you can include up to 1,000 lines per upload, one transaction per line. For larger histories, Intuit suggests shortening the date range and uploading in smaller batches; with Fulla, that means downloading one statement or a few months at a time instead of a full year in a single combined OFX.

Check your chart of accounts first so you do not create a duplicate bank account during the upload, and set up bank rules before uploading if you want QuickBooks to categorize the new transactions as they arrive. Most importantly, check the date range. If the account already has transactions, Intuit’s walkthrough recommends starting the new range the day after the last transaction already in QuickBooks, so the upload does not overlap what is there.

Prepare the OFX file in Fulla Ledger

Upload the statement PDF and wait for the draft rows. Open any row to see its source page and evidence box, and pay particular attention to amount signs, dates around page breaks and descriptions that wrap over several lines. Correct, split or merge rows until they match the statement, then approve the revision. The OFX export page describes the full file contents.

Fulla writes one account per OFX file and marks it as a bank or a credit card statement. Upload it into the matching type of account in QuickBooks; if you choose a checking account for a credit card file, or a savings account for checking transactions, QuickBooks may report that the uploaded file is of a different type than the selected account.

After the upload: review, categorize and reconcile

Uploaded transactions land on the Bank transactions page for review, the same place as bank feed transactions. QuickBooks may add details when it recognizes a description or when a bank rule applies. Match each transaction to an existing invoice, bill or expense where one exists, and categorize the rest.

Finish with a reconciliation. Use the ending balance and date printed on the PDF statement; the closing balance is also included in the OFX file. If the difference is not zero, compare the uploaded transactions with the approved rows in Fulla and the source PDF while the content is still available, because uploaded and derived financial content in Fulla expires 24 hours after the upload starts.

Fix common upload errors

Intuit’s guide to bank upload errors covers the messages you are most likely to see. The most common causes and fixes are:

• The uploaded file contains invalid transaction amount information: one of the amounts has 12 or more digits. Remove that transaction, enter it manually, and upload again.
• The uploaded file is of a different type than these accounts: you selected an account of a different type from the statement. Cancel and pick the right account.
• Parent account or sub-account error: if the related parent or sub-account is already connected to online banking, QuickBooks may refuse the upload. Intuit suggests temporarily disconnecting it, uploading, then reconnecting.
• The upload timed out or QuickBooks could not upload the file: wait a few minutes and try again.
• File too large or too many lines: split the history into shorter periods so each file stays within 350 KB and 1,000 lines.

Use a repeatable import acceptance check

Start with the fictional PDF and matching OFX or CSV below in a separate test account. The sample demonstrates Fulla export structure; it has not been independently verified in your QuickBooks subscription, region or account. The current Intuit documentation is linked below, and menu labels or import options can vary.

Record the selected account, date range, imported row count and signed total before accepting anything. Check for transactions already present through a bank feed or earlier upload. Review the destination result and reconcile through your normal bookkeeping process; a file accepted by the importer is not proof that every transaction is correct.