KMyMoney import: CSV wizard, QIF and OFX files, step by step
KMyMoney imports bank and card transactions from OFX, QFX, QIF and CSV files, and can read a whole GnuCash file. Its handbook is clear about the order: "In general, it is preferable to import OFX", QIF "should be avoided wherever possible", and CSV goes through a wizard where you map your bank's columns yourself. Here's which file to use, each importer step by step, the CSV wizard page by page, how to get PDF statements in, and a free CSV test file with known totals.
Short answer: in KMyMoney choose File → Import → OFX..., QIF... or CSV..., pick the file and the account, then check the imported transactions in the ledger and accept them. Use OFX or QFX if your bank offers it. For a CSV, the wizard asks for the separator, the first and last lines to read, which column holds the date, payee and amount, and the date format, and can save all of that in a profile for next time. Free test files: a checking CSV (31 fictional transactions), and the same statement as OFX and QIF.
See the statement behind the test files
Open Utilly's fictional September 2026 checking statement: every line, the balance check from 12,418.36 to 13,440.52, and the CSV, QIF and OFX downloads. Free, because the data is made up. The checking test files on this page hold those same 31 lines, so you know exactly what an import should bring in.
1. The test files
These files hold Utilly's fictional September 2026 checking and credit card statements in formats KMyMoney imports, so you can try an import into a new test account and compare the result with known totals before you touch real data. No sign-up.
| File | What's in it | Known totals |
|---|---|---|
| Checking CSV | A Date, Payee, Amount header row, then the 31 lines of the fictional checking statement | 20 payments 28,575.27; 11 deposits 29,597.43; net +1,022.16 |
| Checking OFX / QIF | The same 31 lines as Utilly's converter writes them from the PDF statement | As the checking CSV |
| Credit card OFX / QIF | The 21 lines of the matching fictional card statement | 19 charges 1,939.94; 2 credits 1,542.18; 397.76 more owed |
The rows come from Utilly's fictional sample statements (explained on sample bank statement PDF), read by the same engine Utilly's converters use. The CSV has three columns: the date month first with slashes (09/01/2026), the bank's description as the payee (commas and quote marks taken out), and the amount as one signed number with a period decimal (negative = money out), which is what the wizard's Amount tab expects. The first line is a header, so set the Start line to skip it (section 5). The card statement comes as OFX and QIF only, since the handbook doesn't say which sign a credit card account's CSV amounts should use. The checking CSV is plain ASCII text with Unix line endings, about 1.4 KB.
Date,Payee,Amount
09/01/2026,ACH DEBIT GUSTO PAYROLL 0912,-6420.18
09/01/2026,STRIPE TRANSFER ST-K2M8Q4,3184.27
09/02/2026,CHECK 2041,-1850.00
2. Which format to import
The KMyMoney Handbook's chapter on importing and exporting covers a GnuCash importer, a QIF importer, an OFX importer, a CSV importer plugin and a Woob importer. For bank and card statements it ranks the file formats like this:
| Format | KMyMoney's handbook says | What it means for you |
|---|---|---|
| OFX / QFX | "In general, it is preferable to import OFX"; the OFX standard "is much more complete and robust than QIF" | The best choice. An extension of OFX or QFX "does not imply any particular difference in the content" |
| QIF | "Generally speaking, the QIF format should be avoided wherever possible", mainly because there's no transaction ID, so "matching duplicate transactions is haphazard at best" | Fine when OFX isn't offered, but check for duplicates when months overlap |
| CSV | Imported through the CSV Importer, a wizard; CSV files "are almost always available, sometimes described as Excel or spreadsheet files" | Works with your bank's own CSV: you map its columns once and save the setup as a profile |
Unlike some personal finance programs, KMyMoney doesn't need the CSV in a fixed layout of its own. Moving over from GnuCash? The handbook says the GnuCash importer reads the standard XML files GnuCash writes, but not database data, multi-book files, or an import into an existing KMyMoney file.
What's inside a QIF file, letter by letter, is on QIF format explained.
3. Importing an OFX or QFX file
- Download the file from your bank. The handbook says the download link on your bank's transactions page "may say OFX or QFX, or you may request the data for Quicken or Web Connect".
- Open the importer. Choose File → Import → OFX.... If OFX isn't in the Import menu, the OFX Importer plugin isn't installed or enabled (check Settings → Configure KMyMoney..., Plugins).
- Pick the account. "The first thing the importer will do is ask you into which account to import the transactions." If the file holds several accounts, you're asked once for each.
- Assign categories. Transactions KMyMoney couldn't categorize from your history show an exclamation mark on a yellow triangle in the ledger; edit each one to assign a category and the mark goes away.
Web Connect. Instead of saving the file, you can point your browser at KMyMoney when it asks what to open the downloaded OFX file with. KMyMoney then imports it into the file you have open, or the one you had open most recently. Direct Connect (downloading straight from the bank with Map to online account... and Account → Update account...) only works where the bank supports it, and the handbook warns that "No bank directly supports KMyMoney".
KMyMoney can't write OFX: the handbook says "It is currently not possible to export your data as an OFX file."
4. Importing a QIF file
- Open the importer. With a KMyMoney file open, choose File → Import → QIF... and browse to the file.
- Bank statement or history. KMyMoney asks whether this is a bank statement file or historic data exported from another program. "The default is to import a bank statement file", which is right for a converted statement; choose the other option when moving from your previous finance program.
- Choose a QIF profile. "In general, the default QIF profile should work with most QIF files." Click Import.
- Confirm the date format if asked. KMyMoney scans the file for its date and number formats, and asks you to pick one if the date format isn't clear. Utilly's QIF uses MM/DD/YYYY, month first.
- Pick or create the account. If KMyMoney can't tell which account the file belongs to, it asks you, and you can click Create for a new one.
- Review. A statement import statistics window appears at the end, and the new transactions are waiting in the ledger (section 6).
The handbook also notes that "KMyMoney expects files to be UTF8 encoded"; a QIF in another encoding may need converting first.
5. The CSV import wizard, page by page
Choose File → Import → CSV.... If CSV isn't listed, enable the CSV Importer under Settings → Configure KMyMoney..., Plugins. The wizard then walks through these pages:
| Page | What you set | For the test CSV |
|---|---|---|
| Start | The type of data (Banking, Investment, Currency prices or Stock prices), a profile name (type it and click Add, or pick a saved one), then Select File | Banking; any profile name, for example Test checking CSV |
| Separators | Encoding, Field Delimiter and Text Delimiter, normally detected for you. Changing the field delimiter resets any column choices | Comma; the quote mark as text delimiter |
| Rows | The Start line, so the importer skips header lines, and the End line, if there are footer lines to ignore | Start on the second line, after the header; end on the last line |
| Columns | Which column holds each field: Number, Date, Payee/Description, Category, Memo and Balance, plus the money. Use the Amount tab for one signed column, or the Debit/credit tab for separate Debit and Credit columns | Date = column 1, Payee/Description = column 2, Amount tab with column 3 |
| Formats | Decimal Symbol (auto, dot or comma), Thousands Symbol, and the Date format (the order of day, month and year) | Decimal dot; month, day, year |
| Finish | KMyMoney validates the values: numbers highlighted in green are fine, red means a setting is wrong. Click Import CSV and pick the account | Import into a new test checking account |
A few details from the handbook worth knowing before your first real file:
- Signs the wrong way round? On the Amount tab, a Debit/Credit Indicator column or an indicator string can mark which amounts are debits, and "if despite setting all the above values correctly, the amount imported is reversed from what it should be, check the Opposite signs checkbox."
- Keep the bank's text. You can use the same column for Payee/Description and Memo. The handbook suggests it, because "the incoming Payee/Description field might get completely changed on import when KMyMoney does transaction matching", and the memo keeps the original.
- Check the dates. The date order is set automatically, but in data where no day is higher than 12 a wrong order isn't caught: "you will simply get incorrect data". The test file runs to September 30, so the order is unambiguous.
- Save the setup. Click Finish at the end to keep your settings in the profile. Next time, tick Skip setup on the Start page and the wizard goes straight to the last page.
- The preview isn't editable. "The input file is never altered by the CSV Importer", and edits to the table on screen aren't kept; fix the file itself if a line is wrong.
Going the other way, File → Export → CSV... writes one account's transactions for a date range, with a comma, tab or semicolon as the separator.
6. Matching, duplicates and accepting transactions
After a QIF import, the handbook says the imported transactions "will be shown with a yellow background in the Ledgers View", and ones KMyMoney matched with a transaction already in your file are shown in light green (the colors can be changed). Every imported transaction carries an imported icon until you accept it in the ledger; after that it's no longer marked as imported.
Duplicates. Because a QIF has no transaction IDs, "KMyMoney attempts to get around this by looking for transactions that look similar to those you already have" and matches apparent duplicates. If two real transactions look alike and get matched, you can unmatch them later in the ledger. That missing ID is why the handbook says that if you can get the data some other way, like OFX, "always choose that option". Importing overlapping months? Check the light green matches before accepting.
7. PDF statements
The handbook's import chapter covers OFX, QIF, CSV, GnuCash and Woob and doesn't mention PDF. To bring in months you only have as PDF statements:
- Convert each PDF statement with Utilly's bank statement PDF to OFX converter, the format KMyMoney's handbook prefers, or PDF to QIF. Card statements work the same way. The free preview shows every line and whether the statement balances before you download.
- Import one month into a new test account first (section 8) and compare it with the statement.
- Import the rest with File → Import → OFX..., then check matches and accept the transactions.
Prefer CSV? Download Utilly's CSV from the same preview (or use bank statement to CSV). It has Date, Description, Amount and Balance columns with year-first dates: in the wizard, map Date, Description as Payee/Description, Amount on the Amount tab and, if you like, Balance, then set the date format to year, month, day.
8. Checking the import against known totals
Import the test files into a new account (and the card files into a new credit card account), never into an account you rely on, then compare:
| Check | Checking file | Credit card file | If it's wrong |
|---|---|---|---|
| Transactions | 31 | 21 | Fewer: some were matched as duplicates, or the Start or End line cut rows off |
| Money out | 28,575.27 (20) | 1,939.94 (19) | A different total means a column was mapped to the wrong field |
| Money in | 29,597.43 (11) | 1,542.18 (2) | Same as above |
| Change in balance | +1,022.16 | 397.76 more owed | The opposite sign means the amounts were read the wrong way round (Opposite signs, for a CSV) |
| Dates | Sept 1–30, 2026 | Sept 1–30, 2026 | Other months mean the wrong date order was set (month, day, year) |
| Statement balance | 12,418.36 → 13,440.52 | owed 2,846.12 → 3,243.88 | Start the test account at the opening figure |
The data is fictional (Example Community Bank and Sample Customer LLC don't exist; both statements say SAMPLE STATEMENT, FICTIONAL DATA FOR DEMONSTRATION ONLY). Replace every row before using a template for real.
9. Problems and fixes
| Symptom | What KMyMoney's handbook says |
|---|---|
| CSV, OFX or QIF missing from File → Import | The importer plugin isn't installed or enabled: check Settings → Configure KMyMoney..., Plugins, or get a later KMyMoney package |
| The CSV header row came in as a transaction, or you get a data error | Set the Start line past the header and the End line before any footer lines on the Rows page |
| Numbers show in red on the last page | The Start or End line, a column choice or the Decimal Symbol is wrong; go Back and fix it. The Decimal Symbol must match the file, not your locale |
| Spending came in as deposits | Tick Opposite signs on the Amount tab, or use the Debit/credit tab if the file has separate columns |
| Dates in the wrong months | Repeat the import with the date format set to the file's real order; KMyMoney can't catch a swap when no day is over 12 |
| Payee names changed after the import | Transaction matching can replace the payee; map the description to Memo as well |
| Duplicates after importing a QIF twice | QIF has no transaction IDs; unmatch or delete in the ledger, and prefer OFX for overlapping months |
| Transactions flagged with a yellow triangle after an OFX import | They need a category; edit each one in the ledger |
| Odd characters in a QIF | KMyMoney expects UTF8; convert the file's encoding first |
Comparing programs? GnuCash's CSV import also maps your bank's columns in a preview, HomeBank needs CSVs in its own eight-column layout, and Moneydance and Banktivity import the same OFX, QFX, QIF and CSV files, as does the budgeting app PocketSmith.
Get PDF statements into KMyMoney
PDF statements, downloaded or scanned, get a free preview with the balance check, no sign-up. Download OFX, the format KMyMoney's handbook prefers, or QIF. Already have a bank CSV? KMyMoney's wizard can map it, or turn it into OFX first. Files are processed in memory and not stored.
Utilly isn't affiliated with KMyMoney or KDE. The steps and quotes above are from the KMyMoney Handbook, checked November 18, 2026; the test files weren't imported into a live KMyMoney file, and screens may differ between versions. Sources: Importing and Exporting, OFX Importer, QIF Importer, CSV Importer Plugin. If a screen differs, follow KMyMoney's current handbook.
FAQ
What file formats can KMyMoney import?
KMyMoney's handbook covers importers for OFX (including QFX), QIF and CSV files, GnuCash XML files and Woob. For bank statements it says it is generally preferable to import OFX, and that QIF should be avoided where possible because it has no transaction IDs.
How do I import a CSV file into KMyMoney?
Choose File, Import, CSV. The wizard asks for the data type (Banking) and a profile name, then the separators, the start and end lines (to skip a header row), which columns hold the date, payee and amount, and the decimal symbol and date format. Click Import CSV and pick the account. If CSV isn't in the menu, enable the CSV Importer under Settings, Configure KMyMoney, Plugins.
Does KMyMoney need a special CSV format?
No. The CSV Importer maps your file's own columns: one Amount column or separate Debit and Credit columns, plus Date, Payee/Description, Memo and others. You can save the setup as a profile and skip the setup pages next time.
Why are my CSV amounts reversed in KMyMoney?
If amounts come in with the wrong sign after the columns are set correctly, the handbook says to check the Opposite signs checkbox on the Amount tab, or use the Debit/credit tab if your file has separate columns.
How does KMyMoney handle duplicate transactions?
KMyMoney looks for existing transactions that look similar to imported ones and matches them; matched transactions show in light green and new ones in yellow until you accept them. QIF files have no transaction IDs, so check matches when months overlap, and unmatch any wrong ones in the ledger.
Can KMyMoney import a PDF bank statement?
KMyMoney's import chapter covers OFX, QIF, CSV, GnuCash and Woob and doesn't mention PDF. Convert the PDF statement to OFX or QIF first, then import it with File, Import.
Related guides
- GnuCash CSV import: the format, a free template, and every step of the assistant
- HomeBank import: CSV format, QIF and OFX files, step by step
- Moneydance import: CSV, QIF and OFX files, step by step, with free templates
- QIF file format explained: every field, with a real example
- Free sample OFX file (bank and credit card), explained
- Catch-up bookkeeping: getting 12 months of bank statements into QuickBooks or Xero and reconciled
Related tools
- Bank reconciliation checker: compare a bank statement to your books and list missing, duplicate and mismatched transactions.
- Receipt to CSV: turn PDF or photo receipts and invoices into CSV, Excel, or QuickBooks and Xero bill imports.