Import bank statements into QuickBooks Online: CSV guide

For a US QuickBooks Online account, upload a reviewed CSV through Bank transactions, map its columns, then check the selected entries before completing the upload. Both the three-column and four-column CSV layouts belong to Online. QuickBooks Desktop Web Connect instead uses a bank-provided .qbo file; it is a different route.

Choose the Online upload that fits your source

Start with your bank's own transaction download if it covers the account and period you need. A PDF conversion is unnecessary when a suitable native file is already available.

Intuit's current US manual-upload instructions also offer PDF and image statement uploads. Those documents are sent to Intuit for AI processing, with possible expert review. CSV remains an option when you want to prepare and inspect transaction rows yourself.

For the documented CSV route, keep the English-language file within 350 KB and each upload within 1,000 transaction lines. Split a larger working copy into non-overlapping parts and track which part was uploaded; splitting does not remove the need to check existing records.

Prepare a signed-amount CSV for Online

The official format guide describes Date, Description, Amount and a separate four-column Date, Description, Credit, Debit layout. This guide follows the single-Amount layout.

For a checking-account upload, use a negative Amount for a payment and a positive Amount for a deposit. Select a credit-card destination for card transactions and verify its direction against the source.

Intuit currently recommends consistent dd/mm/yyyy dates. Prepare a working copy using the shared CSV guide for delimiters, quoting and source preservation.

Upload, map and select the transactions

Follow the current Online upload flow:

1. Open All apps → Accounting → Bank transactions and choose the account tile.
2. Open the Link account dropdown and select Upload from file.
3. Select the CSV, choose Continue, and confirm its destination account.
4. Map the date, description and amount columns. Check a known receipt and payment against the original before continuing.
5. Select the entries to upload, then continue through Yes → Done.

A successful upload is not completed bookkeeping. Matching links an entry to an existing record; categorizing can create a new one. Check the suggestion before posting. Review overlaps with existing feeds and prior uploads rather than relying on a promise of automatic duplicate prevention.

Use the manual upload review sheet for notes, not as an import file. Follow Intuit's error-specific guidance before retrying; do not bulk-delete existing books to force a fresh upload.

Exclude a downloaded observation or delete a book entry?

After an upload, identify which object is duplicated before choosing an action. Intuit's exclusion guidance concerns a downloaded bank item; its void-or-delete guide concerns an accounting transaction. These are not interchangeable cleanup buttons.

Intuit says exclusion moves the downloaded item to Excluded and keeps it from appearing as an account-register or report entry. Its documented Undo route returns an excluded download for review. Deleting an accounting transaction removes that record apart from the audit trail; do not treat this as the same reversible input decision. The exclusion guide also warns that deleting an unadded download rather than excluding it can allow it to download again.

For a synthetic example, the bank has one $42 payment, the register has its existing check, and two input observations arrived through a feed and a CSV. Inventory the one bank event, one existing accounting object and two input observations separately. The correct number of accounting payments is not established by the number of imported rows. Do not delete the existing check simply because two pending observations look alike.

Open Bank transactions to record the observed status, then Chart of accounts → View register to inspect the existing accounting object without using Delete or Undo during collection. Hand the source references, relationship and reconciliation status to the responsible reviewer. A personal payment is not automatically a candidate for exclusion: the official guidance notes that omitting a real bank event can prevent agreement with the statement.

Synthetic review case. The values are teaching data, not a vendor export or an import file.

Review a rule suggestion separately from a posted refund

In QuickBooks Online US, an imported bank observation, a rule suggestion and an existing book entry are different objects. If a suspected refund is categorized as new income, preserve the original refund/merchant evidence and the related posted entry before deciding what should change. A positive amount or merchant name alone cannot identify a refund or its accounting treatment.

Intuit’s bank-rule instructions distinguish original Bank text from simplified Description. A transaction uses one rule, with rule order affecting priority. Record the current direction, account, conditions, field choice, order and Auto-post setting, then inspect currently visible rule/auto-post candidates in Bank transactions. Do not create, edit or test a rule to reconstruct its former behavior. Auto-post can run on sign-in, upload and rule creation/editing, so entering the company is not guaranteed to be a state-free diagnostic exercise.

For an authorized historical review, Intuit’s Audit log guide requires admin access and an active subscription. Use settings, Audit log, and the user/date/event filters, then inspect the relevant event’s history. The log retains two years and shows 150 records at a time. An individual transaction’s Audit history requires full access and is available through More actions; Show all and Compare provide different views of changes.

Keep three questions separate in the handoff: what is currently suggested, what already exists in the books, and which available history supports a particular change. A system-user event can come from several automated actions; it does not by itself identify a particular bank-rule version. Current rule settings and visible candidates cannot establish a complete population of historical refunds. Route missing history and proposed corrections to the authorized accountant instead of posting another income or refund entry merely to make the balance agree.

Build the affected-record list before requesting a correction

Start with the original payment and the suspected refund as separate source events. Record the bank account/period, debit reference, refund credit reference and merchant document or order reference that supports their relationship. Keep the existing book-entry identity and its observed status separately. A matching amount, a positive sign or the current rule’s conditions is not a verified payment–refund link or proof that the rule created the entry.

Use one row per observed candidate in the handoff. Include the source references, the evidence linking—or failing to link—the original payment, the related book entry, available change-history reference, current suggestion versus already-posted status, uncertainty and responsible reviewer. Classify the documentary relationship, not the accounting correction:

These identifiers are constructed teaching data, not QuickBooks fields or a tested company file. “Confirmed” describes only the stated source relationship; it does not establish rule causation, tax treatment, duplicate income or permission to change the books. Keep missing history explicit and hand the list to the authorized accountant without executing Delete, Undo, re-posting or a rule change.

This rule/history branch was checked against official US instructions on October 17, 2026.

Keep Desktop Web Connect separate

Intuit's Desktop bank-feed instructions call for a backup and a bank-downloaded QuickBooks Web Connect .qbo file. Other Desktop data-import features have their own requirements; these instructions concern the Web Connect bank-feed route.

LocalExtract exports CSV, not .qbo. Renaming a CSV extension does not create a Web Connect file. Use the bank's actual .qbo download or investigate a separate supported conversion workflow before using Desktop.

If you only have a PDF and choose the CSV route, LocalExtract parses one PDF at a time on your device and exports date,description,amount. Inspect and prepare that file for the importer. PDF parsing and OCR are local; importing the resulting CSV sends its rows to QuickBooks. Account and periodic Pro checks still need a network. Download LocalExtract.

Official instructions checked October 15, 2026.

Correction, October 15, 2026: updated the Online PDF/image option and CSV layouts; separated Desktop Web Connect from the Online upload workflow.

Added source-object review checked October 16, 2026.