Home » Citi statements » To Quicken
Get the Chrome extension See sample output
Citi combined statements keep checking, savings, and card sections labelled separately within the same PDF. Each section becomes its own sheet in the Excel output instead of one mixed table.
Quicken on the import side: Quicken (versions 2020 and later) requires a registered Financial Institution ID for Web Connect files. Bank2XL ships with FID 10000 and an Intuit-compatible BID, which Quicken treats as a generic OFX-compatible source. If your version refuses, update Quicken; older versions had stricter FID validation.
| Citi statement input | Bank2XL QFX output |
|---|---|
| Citi Priority Checking ****9301, monthly statement, $8,205.66 closing balance, 30 to 80 transactions a month, scanned or digital PDF. | One QFX document Quicken accepts directly, with each transaction's date, amount, description, and account type. Balance reconciliation status sits on the validation sheet of the matching Excel output if you want to double-check before importing. |
This happens when no existing Quicken account is set up to receive Web Connect imports. In Quicken, open the account, go to its settings, and change Online Services to allow Web Connect. Then retry the import.
Yes. Bank2XL detects the statement type and writes the CREDITCARDMSGSRSV1 section instead of BANKMSGSRSV1, which is what Quicken expects for credit cards. Same .qfx workflow.
Yes. Every conversion produces all formats at once: XLSX, CSV, QBO, OFX, QFX. Download whichever you need. Most users grab the QFX file for Quicken and keep the XLSX as a human-readable backup.