Quicken CSV formatter

The blank columns matter

Quicken's CSV import instructions require the first seven column positions in this order: Date, Payee, FI Payee, Amount, Debit/Credit, Category, Account. Tag, Memo and Chknum are optional final columns. This formatter always writes all ten, including a header, so an unmapped optional field stays empty rather than shifting the next field left.

Date, Payee, Amount and Account must contain data in every row. Dates become MM/DD/YYYY. Amounts use a decimal point and an ASCII minus sign for negative values, without grouping or currency symbols. Quicken says unsigned amounts are positive. FI Payee is ignored by its importer; its guide recommends leaving Debit/Credit blank and using signed amounts instead. Both columns remain present here.

The target Account comes from the exact name you enter, not from an inferred bank identifier. Quicken says an account name it cannot find prompts a choice to ignore the rows, add them to an existing account or create an account. Compare the name with your own data file before importing. No currency field is included in this layout, so confirm the destination account uses the source currency.

Three fictional rows, the same net amount

Load example uses USD +1,250.00 from Client A, -42.25 for office supplies and +15.00 for a refund. All three rows remain, in source order, with a net of +1,222.75. The first data row is 10/01/2026,Client A,,1250.00,,,Everyday,,,. There are ten cells; Everyday is the seventh. The second row keeps check number 0007 as text.

The formatter can read either one signed amount column or separate debit and credit columns. Choose their meaning explicitly, particularly for card exports. For split columns, a populated zero is still a value: rows with both sides populated need review, not an automatic guess about which side to ignore. Decimal places are your choice from zero through six, a limit of this tool rather than a documented Quicken precision limit.

Optional categories, tags and memos are copied, not classified. Quicken documents Category:Subcategory and tag1:tag2 syntax. Its guide also says that a bracketed category such as [Checking] does not make CSV import create a transfer. This tool leaves that text intact and does not manufacture a second transaction.

Do not import the same rows twice

Quicken's guide says CSV imports do not check for or match existing transactions: every row is added to the register. Two identical rows in the file are retained here and flagged for your review. This tool cannot see what is already in Quicken, so a clean preview is not duplicate prevention.

Back up your data file before trying an import. Start with one reviewed date range that does not overlap your register. In Quicken, the documented path is File > File Import > Banking Transactions > From (.CSV) File. That menu also offers Create Sample File. Compare its sample with your download if you are unsure which layout your installed version expects.

This formatter was not tested in live Quicken. It prepares the published Windows banking layout, not a guarantee of destination acceptance. There is no compatibility claim for Mac, Simplifi, investment transactions or older versions without that import menu. After importing, compare the new register entries and reconcile separately. A file-format check is not statement arithmetic, bookkeeping reconciliation or document authentication.

Fix uncertain source rows before downloading

Use one UTF-8 CSV or text file up to 5,000,000 bytes and 10,000 data rows. Comma, semicolon, tab and pipe separators are supported. Choose the date order and number separators yourself; a date such as 03/04/2026 does not establish which part is the month. The displayed cutoff controls two-digit years. Any removed time or weekday suffix is reported, not hidden.

Blank records, repeated headers, subtotal candidates, malformed amounts and mixed account or currency labels block the entire import download. No partial net is presented as a complete result. Zero is a valid amount. Replacement characters also block output because the original text may have been decoded incorrectly. Correct a working copy and keep your original file.

Confirm that the source contains posted transactions only, and that the mapped date is the posted date. If it contains pending transactions, prepare a posted-only working copy first. The tool does not decide whether a pending row later became a posted one, check statement coverage or create opening-balance entries. The earliest and latest supplied dates describe these rows, not complete account history.

The import file omits source columns that are not part of the chosen output. Their column numbers are listed before approval; the separate review CSV retains every parsed source cell, including the header and any problem records, with its physical source line. The report also records mappings, conventions, net amount when valid, duplicate notices, changed text and approval state. It is a review document, not another file to import into Quicken.

Keep check numbers as text and your source unchanged

CSV can preserve the characters 0007 without forcing another app to treat them as text. Microsoft's automatic-conversion guide explains that opening a CSV can remove leading zeros or truncate long numerical text. Avoid opening and resaving an import file casually. If you need to inspect it in Excel, control the column types or the documented conversion settings rather than using a formula such as ="0007".

The downloads prefix formula-like text with an apostrophe and show how many cells change. Parsed numeric amounts, including negative ones, are not prefixed. The output preview shows the exact protected text. An Account or Category that needs protection requires a separate acknowledgement because the prefix can change a destination name. Correct the source instead if that is not the name you intend.

OWASP's CSV injection guidance warns that no sanitization method is universal and spreadsheet save/reopen operations can remove protection. Treat files from unknown sources carefully even after formatting. The review CSV contains source details from unused columns too; read it before sending it to anyone.

Your file and the values you enter are processed in this browser tab. They are not uploaded or sent to analytics. We do not save them between visits. Downloads you choose to save remain on your device.

Use Clear to remove the active input and settings. Back navigation can restore uncleared input, and Clear is not a secure memory wipe. Downloads create new files without overwriting your source.

What the format is based on

We opened Quicken's CSV instructions on October 17, 2026. Its page has no visible update stamp in the article body; the HTML page-last-modified metadata says April 14, 2026. Microsoft's conversion page was opened the same day and has ms.date metadata of October 15, 2025. OWASP's guidance showed no visible update date. Quoting and record writing follow the shared parser and writer based on RFC 4180, dated October 2005.

The fictional example was recomputed with exact decimals. Automated checks cover the documented ten-column order, dates, signs, text protection and blocked output for unresolved rows. They do not establish how a live Quicken installation will interpret every value. Use the native sample file and review your register.

If the bank only gives you PDFs

First check whether the bank has a native CSV export for the missing period. You can also prepare a small number of rows manually. If only PDFs remain, AnyStatement can extract transaction data with source-line review, then you can check those rows before formatting them here. That conversion is a separate upload workflow, not part of this free browser-local tool.