Before you import a bank statement CSV

The bank's export is worth checking first

Your bank may offer a download your accounting app accepts: CSV, QBO, QFX or OFX. Checking before converting a PDF may save an extraction step. Keep the PDF too, so you can compare its printed dates, transaction details and balances with the imported data.

For a PDF or scan, extraction can help, but check your accounting app first: Intuit documents PDF and image statement uploads in QuickBooks Online. The same checks apply however the transactions were extracted.

Edit dates and columns in a working copy so you have an untouched source to return to. For help on a public forum, use a fabricated example with the same formatting problem. Never post real client statements.

Make sure you're checking the right period

A statement period isn't always a calendar month. Before comparing rows, note the account identifier, start and end dates, currency, and opening and closing balances from its heading. Different accounts, cards and currencies need separate checks.

• The first and last transactions should agree with the PDF. An unfamiliar date needs a look at the bank's printed period and posting rules, not immediate deletion.
• Fees, interest, refunds and adjustments can appear on any page, including continuation pages, so check them all. Repeated headings and page subtotals aren't transactions.
• Printed transaction counts give you something to compare; without them, compare rows page by page. Matching counts don't prove the amounts are right.
• Gaps or overlaps need investigating before you merge periods. For the same account, one period's closing balance should match the next opening balance.

A card purchase on January 31 may post in February. Use the date field your destination requires, but keep both transaction and posted dates in your review copy when available.

Your spreadsheet can change the data

CSV is plain text, without reliable column types, so Excel can reinterpret it on opening. Rather than trusting a double-click, use Data → From Text/CSV to inspect the preview, import identifiers as text and choose the date interpretation.

• 03/04/2026 can mean March 4 or April 3. Resolve that from the source before choosing a format your importer accepts. Changing the display format won't fix a wrongly parsed date.
• Missing years come from the statement period, not today, so take particular care with December-to-January statements.
• Excel can remove leading zeros or round references beyond 15 significant digits. Re-import the untouched source as text if that happens, because formatting afterward won't restore lost digits.
• Currency symbols, spaces and separators can leave amounts stored as text and silently omitted from totals. After converting them to plain numbers, add a test value to confirm that the column total actually changes.

The signs depend on the account

QuickBooks Online accepts a three-column file (Date, Description, Amount) or a four-column file (Date, Description, Credit, Debit). In Intuit's single Amount column example, money leaving a bank account is negative. Credit cards differ: payments can be negative because they reduce what you owe. Intuit says to select the credit card account, not a bank account, when uploading.

Two statement transactions, one outgoing and one incoming, let you check the direction in the preview. If every amount is reversed, QuickBooks Online offers a reverse all values option on its amount-check screen. If only some are reversed, the mixed conventions need correcting in the source file instead.

A matching balance isn't the end of the check

The balance check is opening balance + sum of all transactions = closing balance. When running balances are printed, you can check each row too. Here's how that works in a fictional March 2026 checking statement, not a real customer's statement.

The transactions sum to 1,200.00 - 1,150.00 - 86.45 + 42.50 - 29.00 - 12.00 = -34.95. Opening 2,400.00 plus -34.95 is 2,365.05, matching the printed closing balance. With a zero difference, nothing is obviously missing.

Now see what happens with three mistakes in that file:

• In case A, look for a row equal to the difference, because running balances match through row 5, then stop short of the printed 2,365.05.
• In case B, half of 85.00 is 42.50, one row's amount. Flipping a sign changes the total by twice that amount.
• Case C passes because the errors cancel (+18.00 and -18.00). Running balances are wrong at rows 3 and 4, then match again at row 5.

A nonzero difference gives you a starting point: look for a row equal to it or half of it. Even at zero, you need to compare rows with the source and check printed running balances, because errors could cancel out. A difference divisible by 9, like 18.00 above, can hint at transposed digits, but it's only a hint.

Don't add an adjustment row to force a match, because it can hide the missing, duplicated or misread row you need to find. Intuit's reconciliation guidance warns against adjustments that hide the cause.

Fit the file around what's already in your books

Your file might continue after the last transaction in the books or add history before the first. Either way, its first and last dates need to fit: overlaps can import transactions twice, while a file that stops short leaves a gap. That's why Intuit's manual upload guidance advises checking what's already there before choosing download dates.

• Sorting by date makes matching dates, descriptions and amounts easier to compare. But two identical rows may be two real purchases, such as two coffees on one day, so check the statement before deleting either.
• When you combine months, each closing balance should match the next opening balance.
• Intuit lists a QuickBooks Online maximum of 350 KB and 1,000 lines per list upload. Split longer histories at month boundaries, not halfway through a day.

The preview is another chance to catch errors

QuickBooks Online's preview lets you choose the date format, map columns and check positive and negative amounts. Compare the first and last transaction, one refund and one payment with the statement to check those choices. If possible, import a short period first so mistakes are easier to find and undo.

These arithmetic checks test the file, but reconciliation tests your books. After importing, you still need to match and categorize transactions, then reconcile to the bank statement.

A short checklist for your working copy

1. Keep the original untouched while you check a copy, one account, currency and period at a time.
2. Set column types on import, using the statement to resolve dates rather than trusting the spreadsheet's interpretation.
3. Use one outgoing and one incoming row to confirm the signs, then compare every page, including the first and last rows.
4. Compare opening + transactions with closing, then look for a row equal to any difference or half of it. Printed running balances let you check rows too.
5. Once you've checked overlaps and gaps, review the preview and try a short import before reconciling.

If the bank only gives you a PDF

Some banks only provide PDFs. If your QuickBooks Online account offers PDF or image uploads, try that first: it shows extracted data beside the original for review, though you still need to check the result.

If you need a spreadsheet, CSV, QBO or OFX instead, you can convert the PDF with AnyStatement. Transactions link back to their source lines, and balances that don't add up are flagged at the row. Keep spot-checking the source, because agreeing totals don't prove every row is right.