BofA and Navy Federal Dropped QFX: How to Import CSV into Quicken

If your Quicken register has a hole in it and your bank no longer offers a QFX download, the way back is Quicken's own CSV import. It works, but only if the file matches one exact ten-column layout, and no bank's CSV export comes out in that layout. Quicken also never checks a CSV for duplicates. This guide covers the layout, how to reshape your bank's file into it, and what to do when the missing months are older than anything your bank will still export as CSV.

What changed at Bank of America and Navy Federal

For years the fix for a missed month was simple: log into the bank, download a Web Connect (.QFX) file for the missing dates, open it in Quicken. That route is gone at two large institutions.

• Bank of America ended OFX service, including Web Connect QFX files, on September 30, 2025, leaving Express Web Connect+ as the only Quicken connection (Quicken Community: 9/30/25 Bank of America - OFX Discontinued). Users report that a fresh connection or catch-up update only brings in about the last 90 days.
• Navy Federal Credit Union members began reporting in April 2026 that the Quicken download option had disappeared (Quicken Community, April 2026), and by August 2026 more members reported that NFCU's new online banking had dropped .qfx downloads altogether (Quicken Community, August 2026).

Both banks still let you download transactions as CSV and statements as PDF. Those two formats are now your raw material.

First, work out which gap you have

The right fix depends on how old the missing transactions are, so date the hole before you touch a spreadsheet.

How far back CSV downloads reach differs by bank and account type, so check the date picker in your bank's download screen. PDF statements usually go back years further than CSV history, which is why the last row matters: for older gaps, the statement is the only record left.

The one layout Quicken for Windows accepts

Quicken for Windows is strict about the CSV it will read, and its help page spells the format out (Quicken Help: Import transactions from .CSV file). The first seven columns must be present in exactly this order, even when some are empty. The last three are optional.

The import lives at File > File Import > Banking Transactions > From (.CSV) File, and the same window has a Create Sample File button. Generate the sample and paste your data into it rather than building the header row by hand.

Reshaping your bank's CSV into that layout

A bank CSV usually has the right information in the wrong shape. Typically you get a date, a description and either one amount column or separate withdrawal and deposit columns, often with a running balance and extra reference fields. In Excel or Google Sheets:

1. Delete what Quicken doesn't take. Running balance, reference numbers and type codes go. Don't paste a balance column into Amount by mistake.
2. Get to one signed Amount column. If the bank splits withdrawals and deposits into columns C and D, add a column with =IF(C2<>"",-ABS(C2),ABS(D2)) and paste it back as values. Quicken treats a number with no sign as positive, so an unsigned withdrawal turns into a deposit.
3. Check the sign on credit cards. Card exports often show purchases as positive numbers. Quicken's rule is that a positive amount increases net worth, so in a card account a purchase must be negative and a payment positive. If yours comes in reversed, multiply the column by -1.
4. Add the empty columns in their places. Insert blank FI Payee and Debit/Credit columns around Amount, and a Category column after them, so that Account lands in column 7.
5. Fill Account with the exact Quicken account name on every row. If the name doesn't match an account in your file, Quicken will ask whether to ignore those rows, add them to an existing account or create a new one.
6. Fix the dates. They must be full mm/dd/yyyy dates. Format the column as mm/dd/yyyy before saving so Excel doesn't write 2025-05-31 or a serial number.
7. Save as CSV UTF-8. Payees containing commas will be quoted automatically, which Quicken expects.

When the gap is older than the CSV window: use the PDF statements

Past the CSV window, the monthly PDF statement is the only record of those transactions, and it has to become a spreadsheet before any of the steps above apply. You could retype it, or paste it from the PDF and watch every column collapse into one. The quicker route is to extract the transaction table directly.

ExtractMyStatement's converter does this in your browser. The PDF is read on your device and never uploaded, which matters for a document with your account number on it. A few things about how it handles statements are worth knowing before you import the result into Quicken:

• It needs a digital PDF. Statements downloaded from online banking have a text layer and work. A scanned paper statement is a picture of text, and the converter will tell you it can't read it.
• It starts at the first dated row. The account summary box at the top of the statement is skipped, and multi-line descriptions are merged into one Payee cell.
• It drops summary and footer lines. Rows containing words such as "total", "beginning balance" or "page" are left out so balance lines don't land in your register. A merchant whose name contains one of those words can be skipped too, so add up the Amount column and compare it with the statement's totals before you import.
• Dates often lack a year. Many statements print 10/03 rather than 10/03/2025, and the CSV keeps what the statement shows. When Excel opens that CSV it quietly fills in the current year, which is wrong for an old statement. Fix it with a helper column such as =DATE(2025,MONTH(A2),DAY(A2)), and watch December-to-January statements, where the year changes partway through.
• You can fix things before export. Every cell and header in the preview is editable, and junk rows can be deleted, so renaming the headers to Date, Payee and Amount there saves a step later.

Convert one statement per missing month (multi-page statements come out as a single table), export each as CSV, then paste them into one sheet and follow the reshaping steps above. If you'd rather do the reshaping by hand in a workbook, our guide to converting a bank statement to Excel covers the Excel side.

Before you click Import

CSV import is less forgiving than the QFX route it replaces, and Quicken says so plainly: it does not match transactions against what's already in the register, so every row is added as new, and importing the same file twice creates duplicates. Three habits prevent most of the cleanup:

• Back up the Quicken file first (File > Backup and Restore). Restoring a backup is far easier than deleting 200 duplicate rows.
• Trim the overlap. Delete any rows dated on or after the first transaction your bank connection already downloaded, so the CSV fills only the gap.
• Re-enter transfers yourself. CSV import doesn't create transfers between accounts, even with a bracketed [Checking] category. A credit card payment imports as a plain expense in one account, so link the two sides by hand afterwards.

After the import, open the register, click the gear icon and choose Update Balance if the ending balance doesn't match your statement.

On a Mac or in Simplifi

The ten-column layout above is the Windows format. Quicken for Mac and Quicken Simplifi each have their own CSV import with their own template, and Quicken for Mac offers a sample file in its import dialog. Download that sample and match its columns rather than assuming the Windows layout carries over. The rest of this guide applies unchanged: one signed amount, full dates, no balance column, and PDF statements as the source for anything older than the bank's CSV history.

Questions readers ask after doing this

Should I buy a CSV-to-QFX converter instead? On Windows you mostly don't need one, because Quicken reads CSV directly once it's in the right layout. A converter is mainly worth it if you want Quicken's QFX duplicate matching, or if you'll be filling gaps every month.

Will this mess up my tax records? Not if the CSV ties to the statement. The PDF statement stays the record of what happened, and the CSV is just how it gets into Quicken. If you're pulling a year of history for a tax preparer anyway, our guide to exporting bank statements for taxes covers what to keep, and sorting freelance income from a statement CSV covers splitting out 1099 income once the data is in a spreadsheet.

My bank's CSV only covers 18 months, but I need three years. Then the last 18 months come from the CSV and everything before that from the PDF statements. Start with the oldest missing statement, import it, confirm the balance lines up, and only then do the next month. A mistake caught after one month is a five-minute fix. Caught after thirty-six, it's an afternoon.

Next step: find the date of the last transaction in your Quicken register, then open your bank's download screen and see whether that date is inside the CSV window. That one check tells you which of the two paths above you're on.