Bank Statement PDF to QFX for Quicken

Quicken won’t read a PDF or a plain .ofx — it imports its own Web Connect .qfx, and only if the file checks out. This builds one that clears Quicken’s “can’t verify the financial institution” wall — from a digital or scanned statement.

No signup to tryQuicken Windows & MacDuplicate-safeFree to start

Click to upload or drag and drop

Supported formats:

PDF

PNG

JPEG

TIFF

Up to 25MB · PDF → QFX

Secure & Encrypted Conversion

All uploads are encrypted for your security

Trouble converting a file? Tell us — we fix issues fast. Report it

How it works

How to convert a bank statement PDF to QFX

Upload your statement

Add your statement PDF — from online banking or a scan of a paper copy. Nothing to install.

AI reads every transaction

Dates, payees and amounts are pulled line by line and each gets a unique ID so Quicken won't double-import.

Download a .qfx file

A well-formed Quicken Web Connect file with the financial-institution details Quicken checks for.

The output

What a Quicken-ready .qfx looks like

A .qfx is a Web Connect (OFX/SGML) file — note the FI block and per-transaction FITIDs. Toggle from the run-together statement to the actual file you'll import.

statement.qfx

Messy PDFClean .qfx

OFXHEADER:100
DATA:OFXSGML
VERSION:102

<OFX>
 <SIGNONMSGSRSV1><SONRS>
  <FI><ORG>TableSense.ai<FID>3000</FI>
  <INTU.BID>3000
 </SONRS></SIGNONMSGSRSV1>
 <BANKMSGSRSV1><STMTTRNRS><STMTRS>
  <CURDEF>USD
  <BANKTRANLIST>
   <STMTTRN>
    <TRNTYPE>CREDIT
    <DTPOSTED>20240305
    <TRNAMT>1850.00
    <FITID>20240305-1
    <NAME>Payroll Deposit
   </STMTTRN>
   <STMTTRN>
    <TRNTYPE>DEBIT
    <DTPOSTED>20240307
    <TRNAMT>-64.20
    <FITID>20240307-1
    <NAME>Shell Gas
   </STMTTRN>
  </BANKTRANLIST>
 </STMTRS></STMTTRNRS></BANKMSGSRSV1>
</OFX>

Why QFX

Built the way Quicken expects

Quicken is fussy about Web Connect files — it checks the financial institution and rejects anything malformed. This export is shaped to clear those checks.

Quicken reads it natively

Quicken imports .qfx directly (it won't take a plain .ofx) — no conversion gymnastics on your end.

Passes Quicken's FI check

Carries valid financial-institution attributes, so you sidestep 'unable to verify the financial institution'.

No duplicate transactions

Every transaction gets a unique FITID, so re-importing the same period won't double your register — unlike QIF.

Quicken on Windows & Mac

Imports through File → Import → Bank or Brokerage File on either platform.

Scanned PDFs & any bank

OCR lifts text from scans and phone photos, so an image-based statement still yields a Quicken-ready .qfx.

Clean dates & amounts

Normalized so Quicken won't choke on a stray date format or number.

'Quicken is unable to verify the financial institution' — why it happens

It’s the most common QFX headache, and it’s not really about your bank. Quicken checks a .qfx for recognised financial-institution details and well-formed structure; if either is off — an unregistered FI or a stray syntax error — it refuses the file outright.

TableSense writes the .qfx to spec with valid FI attributes and clean tags, which is exactly what Quicken looks for — so the import goes through instead of stalling on that message.

QFX, OFX, QBO or QIF — which one for Quicken?

For Quicken, the answer is QFX. Quicken won’t import a plain .ofx; QFX is its Web Connect flavour with the extra tags Quicken requires. QBO is the QuickBooks version (wrong app), and QIFstill imports but can’t prevent duplicates the way QFX’s FITIDs do. So QFX is the cleanest, safest path into Quicken.

Importing

Import your .qfx into Quicken

The same path on Windows and Mac.

Quicken (Windows & Mac)

File → Import → Bank or Brokerage File (OFX, QFX) → choose your .qfx, then pick an existing account so transactions land where you expect.

Before you import

Select an existing account rather than “add a new account,” and import each account’s statement into its own register to keep things tidy.

Heading somewhere other than Quicken? Try QBO for QuickBooks, OFX, or a plain CSV.

Your statements stay private. Uploads are encrypted, the .qfx is generated from the extracted transactions, your file isn’t kept longer than the job needs, and you can try it without an account.

Any bank

A .qfx from any bank's statement

Whether it's a US checking statement or an international credit-card PDF, the AI follows the document's own layout — so the .qfx comes out valid regardless of the issuer.

ChaseBank of AmericaWells FargoCitiCapital OneUS BankPNCHSBCBarclaysNatWestLloydsRBCTD BankHDFCICICISBIAxis BankANZCommonwealth BankDBS+ any bank worldwide

FAQ

Frequently asked questions

QWill the .qfx file import into Quicken on Windows and Mac?

Yes. In Quicken, go to File → Import → Bank or Brokerage File (OFX, QFX), pick the .qfx, and choose an existing account rather than adding a new one. It works the same on Windows and Mac.

QI get 'Quicken is unable to verify the financial institution' — does this fix it?

That error fires when the file's financial-institution details aren't recognised or the file has a syntax error. This converter writes a clean, well-formed Web Connect file with valid FI attributes, which is exactly what Quicken checks — so it imports instead of erroring.

QQFX or OFX — which one does Quicken use?

Quicken imports QFX, not a plain .ofx — QFX is the Quicken flavour of OFX with extra attributes Quicken looks for. So always choose QFX for Quicken.

QWhat's the difference between QFX and QBO?

Same OFX family, different app: QFX is for Quicken, QBO is for QuickBooks. Use QFX here for Quicken; pick the QBO converter if your destination is QuickBooks.

QWill importing create duplicate transactions?

No. Each transaction carries a unique FITID, so if you re-import an overlapping period Quicken recognises and skips the duplicates — something the older QIF format can't do.

QWhy does Quicken show a different bank name on import?

The .qfx includes a financial-institution ID, and Quicken shows the matching label. It's cosmetic — your transactions still import into the account you choose.

QCan I convert a scanned bank statement to QFX?

Yes. Scans and photos have no selectable text, so TableSense runs OCR first, then builds the .qfx — image-based statements convert fine.

QIs it free to convert a bank statement to QFX?

You can try it with no signup; the free tier covers occasional conversions, and paid plans add volume and batch capacity.

QWhat happens to my statement after the .qfx is built?

Uploads are encrypted, the .qfx is generated from the extracted transactions, the file isn't kept past the job, and no account is needed to try it.

QCan I unlock a password-protected PDF?

Yes. A locked PDF prompts you for the password to open it (used only for that), then the .qfx is created normally.

QWill a non-US or multi-currency statement import into Quicken?

Yes — any country's statement works and the currency is detected and written into the .qfx (CURDEF), so non-US accounts import correctly.

QWhich banks work with the QFX converter?

Any bank, anywhere — extraction follows each statement's own layout instead of a fixed template, so even non-English formats produce a valid .qfx.

QCan I convert several statements for Quicken at once?

Yes on paid plans — batch a stack of statements across accounts in one go, handy for catching a Quicken file up after months away.

QHow accurate is the .qfx output?

High on digital and scanned statements, though no tool is flawless on every layout — check the transaction count and tie to the closing balance before you import.

Keep going