Free CSV to QIF Converter for Quicken
Turn a spreadsheet of transactions into a .QIF file that Quicken, GnuCash, Moneydance or Banktivity will import, with a category on every transaction and multi-line entries written as splits.
QIF will not read a transaction until it knows what kind of account it belongs to, and no spreadsheet column says. You answer that once, in the account type control, and every account block in the file is written with your answer.
Embed this converter on your website for freeChoose your file
Drop your CSV or Excel file here
Your file is never uploaded. We never receive it or store it.
A Spreadsheet Does Not Say What Kind of Account It Is
Most of how to create a QIF file from a spreadsheet is ordinary column work: the converter reads a date, an amount, a payee and the name of the account the money moved through, all of which your file already has. One thing no spreadsheet carries is what kind of account that is, and QIF wants it before it will read a single transaction, so the account type control answers it once for the whole file.
Once, for the whole file, is the part worth knowing. If your rows mix a checking account and a credit card, both account blocks come out with the same type on them. Convert the card rows as a second pass, or correct the one T line afterwards; a .qif is plain text and that line is four characters long.
Your categories still travel. A QIF file converter writes them onto each transaction as an L line and onto each split as an S line, which is where Quicken and GnuCash read them.
Your spreadsheet
| Bank account | Date | Amount |
|---|---|---|
| Checking | 03/04/2026 | -450.00 |
| Checking | 03/06/2026 | -22.10 |
| Visa | 03/07/2026 | -180.00 |
| Visa | 03/09/2026 | -64.00 |
Two accounts, named. No column says what kind they are.
The .qif it writes
| Line | Where it comes from |
|---|---|
| !Account | Opens a block for one account |
| NChecking | The name, read from your column |
| TBank | From the account type control, not from your file |
| ^ | Closes the account header |
| !Type:Bank | What follows belongs to that account |
| … | The two Checking rows |
| !Account | A second account, in the same file |
| NVisa | Its own name, from the same column |
| TBank | The same value again |
| ^ | Closes the account header |
| !Type:Bank | And the two Visa rows follow it |
A spreadsheet names an account. It does not say what kind of account it is, and QIF wants that before it will read a transaction. The control answers for the whole file at once, so a file holding a checking account and a credit card writes the same type onto both blocks.
Do You Actually Need QIF?
Worth two minutes before you convert anything: you may not need a QIF at all.
Use Direct CSV When It Fits
Current Quicken for Windows documents a direct CSV import for banking transactions, with a required column order. If your file can be shaped to that, importing the CSV straight is simpler than converting it. Try that first.
Use QIF When the Workflow Requires It
Choose QIF when the destination asks for it by name: GnuCash, Moneydance, Banktivity, an older Quicken file, or a third-party workflow built around it. Quicken itself calls QIF a legacy transfer format, and it is not automatically better than CSV.
How to Convert CSV to QIF
Four steps, and the spreadsheet never leaves your computer at any of them.
Drop Your Spreadsheet
A .csv, a .tsv, a tab-separated .txt, or an .xlsx or .xlsm workbook. A workbook holding more than one sheet asks which sheet the transactions are on.
.csv · .tsv · .txt · .xlsx · .xlsm
Say What the Rows Are
The transaction type the rows represent, and the account type every QIF block is written with. Month-first or day-first sits here too, and the options spell out what 03/04/2026 means each way.
asked, never guessed
Check the Mapping
Your header row is matched to date, amount, payee, memo, category and reference, and every column the converter matched for itself is badged as one. A field your file has no column for can take a fixed value instead.
auto-matched, yours to correct
Review, Then Download
The transaction count, the number of account blocks, the file size, every warning raised, and the first forty lines of the .qif itself, all before you take the file.
counted and shown first
What QIF Carries, and What It Cannot
Old, loosely specified, and it holds less than most people expect.
What It Carries
Date, amount, payee and memo. Cheque and reference numbers. A category per transaction. Splits with their own categories and memos. Cleared status, where your file marks it.
Dates Are the Thing to Get Right
QIF carries no declaration of its own date format, so 03/04/2026 is genuinely ambiguous and nothing in the value can settle it. The control asks rather than guesses, in its own words: month first, where that date is 4 March, or day first, where it is 3 April. The file is then written zero-padded and month-first either way.
Categories Travel on the Transaction
There is no category list at the top of the file. Each transaction carries its category as an L line and each split carries its own as an S line, which is where Quicken and GnuCash read them anyway.
What It Does Not Carry
Account numbers, because QIF names an account and stops there. Classes, jobs and departments. Items, quantities and unit prices. Attachments and audit history. Those columns are read and then left out rather than written somewhere nothing looks.
Stop Supplying What the Spreadsheet Leaves Out
The account type, the date order and the mapping are answered once here, and again next month.
| What you need | This converter | Autymate |
|---|---|---|
| One spreadsheet turned into a QIF | Free, now, and nothing to sign up for | Not what it is for |
| The same export every month | The same mapping rebuilt each time | Mapped once and reused for the next one |
| More than one account in one file | A separate pass per account type | Each account routed in its own right |
| The data before it was ever a spreadsheet | Whatever the export happened to give you | Read from the source system where the interfaces allow |
The File Arrives Without a Chart of Accounts
Writing the file is the easy half. What the receiving program does with it is the rest.
No Category List Travels With It
A QIF can open with a block listing every category the file uses. One built from a spreadsheet has none, because a CSV of transactions carries no chart of accounts to build it from. The control offering to write income and expense accounts as QIF categories has nothing to write.
Nothing Here Checks the Spelling
Category names are written exactly as your spreadsheet spells them. Two spellings of one category stay two, and most programs create a category they have not seen before rather than telling you they did. Fixing it in the sheet is cheaper than fixing it after the import.
Import a Short Range First
Every program reads QIF slightly differently, and signs are where they most often disagree. Import a single month, open one transaction next to the row it came from, and commit the rest once those two agree.
Common Questions
What people ask before they trust a converter with their accounting system.
Not always. Current Quicken for Windows documents a direct CSV import for banking transactions when the file follows its required column order, and where that fits your data it is the simpler path. Convert to QIF when the destination asks for QIF by name. Import behaviour also varies by Quicken product, version and account type, so the version you are running decides more here than the format does.
Drop the spreadsheet on this page, say what the rows are, check the column mapping it proposes, and download the .qif. That is the whole of how to convert CSV to QIF with this tool, and there is nothing to install. If you would rather write one by hand, a QIF is plain text: an account block, then one letter at the start of every line, with a caret on its own line closing each transaction.
Yes. An .xlsx or .xlsm workbook is read the same way a .csv is, and so are .tsv files and tab-separated .txt files. A workbook holding more than one sheet asks which sheet to read before anything is mapped.
You tell the converter which one it is, because nothing in the file can. The date format control offers month first, where 03/04/2026 is 4 March, and day first, where the same characters mean 3 April. Whichever you pick, the QIF is written month first and zero padded, which is the order QIF readers expect.
Yes. Rows are grouped by the account column you map, and each account gets its own block in the file. The type on those blocks comes from one control and applies to all of them, so a spreadsheet mixing a checking account and a credit card is better converted in two passes, one per type, than corrected afterwards.
Quicken, GnuCash, Moneydance, Banktivity, AceMoney and Money Manager EX all read QIF for ordinary banking transactions. A GnuCash QIF import asks which account the file belongs to and then offers to match the category names it finds against the ones you already use, so the L and S lines this converter writes are the part it reads.
No. The rows are read and the .qif is written inside the browser tab you are reading this in. Nothing is sent anywhere, so there is no retention window to ask about and no copy of your transactions for anyone to hold.
Offer the CSV to QIF Converter on Your Website
Your clients convert their files right on your site, free, without ever leaving it.
Free, with no sign-up
Copy the code and paste it. No account, no API key.
Client files stay private
Every file is converted in your visitor’s browser and never uploaded, not even to us.
Always up to date
Improvements reach your page automatically, and it sizes itself to fit.
Paste it into
Webflow
WordPress
Squarespace- Any HTML page
<div class="autymate-embed" data-tool="csv-to-qif-converter">
<p>CSV to QIF Converter · Powered by
<a href="https://www.autymate.com/tools/csv-to-qif-converter">Autymate</a></p>
</div>
<script async src="https://www.autymate.com/embed/v1.js"></script>Paste it where you want the converter to appear.
Written and maintained by The Autymate integrations team. We build and run accounting integrations for multi-location franchises, ISVs and bookkeeping firms: QuickBooks Desktop and Online, POS, payroll and ERP. These converters exist because we kept writing the same ones for customers, and there was no reason to keep them to ourselves.
Last reviewed
The Spreadsheet Was Already the Second Step
Something produced those rows before anyone saved them as a file: a bank, a point of sale, a payment processor, a payroll run, a system somebody exports every month. Tell us where the file comes from, what cleanup happens to it today, what has to receive it next, how often it repeats and how many accounts are involved.
Exact source access, fields, permissions, QuickBooks behaviour and service scope are confirmed during discovery.