PDF to QFX Converter

QFX is Quicken's name for a Web Connect file: OFX, the format banks use for transaction downloads, plus a bank code that Quicken reads before importing. It is the file Quicken asks for when you download transactions from a bank's website, and the only file Quicken uses for Web Connect.

When all you have is the PDF (statements older than the bank's download window, a closed account, a statement someone sent you), this page reads every transaction and writes the QFX file the bank would have given you: dates, signed amounts, descriptions, a transaction ID per line and the closing balance.

Quicken's own support pages say it does not support QFX files made by third-party conversion software, PDF converters included. In practice such files usually import, but if one fails, Quicken's support cannot help with it. The QFX file's layout here has been compared with banks' own files; imports into Quicken itself have not yet been tested and recorded. The first 2 pages are free, so check that your Quicken accepts the file before paying for a long statement.

The file carries bank code 3000, the one in Wells Fargo's Web Connect files, because a PDF has none of its own. Quicken may show Wells Fargo as the institution. Link the import to your own account; nothing is sent to or from Wells Fargo.

Quicken for Windows:

1. Convert the statement, check the summary says it reconciles, and download the QFX file.
2. Choose File → File Import → Web Connect File, select the .qfx file and choose OK.
3. Link it to an existing account, or create a new one. Do not set the account up for online banking with the institution Quicken names.

Quicken for Mac:

1. Choose File → Import → Bank or Brokerage File (OFX, QFX) and select the file.
2. On the Choose Your Accounts screen, pick the account to import into.

Import into a new or empty account first if you can, compare the ending balance with the statement, then move the transactions where they belong.

QFX is what current Quicken expects from a bank, and each transaction carries an ID so importing the same file twice does not duplicate it. QIF is older and plain text; which account types accept a QIF import has changed across Quicken versions, and it has no transaction IDs. Use QFX first. If your Quicken refuses it, the QIF download comes from the same checked transactions, and Quicken for Mac also accepts the plain OFX download through the same menu.

• OL-221: Quicken's support links this to the computer's date and time settings. Correct the system clock and import again.
• Transactions land in the wrong account: Quicken matched the file to an account already linked to bank code 3000. Choose the account by hand during the import.
• "No new transactions": Quicken already has every transaction ID in the file, usually because the same file was imported before.

A typical 3-page statement costs 7 credits on a day when your 2 free pages are unused (one paid page at 5 credits, plus 2 for the QFX file), or 17 credits otherwise: about $0.35 or $0.85 at the $5-pack rate. The smallest purchase is $3 for 50 credits. Heavy users may do better with a subscription converter such as ProperSoft or MoneyThumb, and ProperSoft runs entirely on your own computer.

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. The CSV holds only the Transactions table, one rectangular sheet, because that is what accounting software expects to import.

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 already contains its text. That text is read in place, with each amount kept in the column it was printed in, which is why this path is the most accurate: the tool never has to guess whether 42.35 was money in or money out.

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.

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.

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 5 credits each, and the Excel download is 4 credits once per job. With the two free pages still available, a six-page statement uses 20 credits for processing plus 4 for the workbook. If you have no credits, the smallest purchase is $3 for 50 credits, before any applicable tax; 26 credits remain after that job. Credits never expire, there is no subscription, and a job that fails is not charged.