Banktivity import: CSV, QIF and OFX files, import rules and Quicken, step by step
Banktivity imports bank and card transactions from OFX, QFX, QIF and CSV files, plus QMTF transfer files from Quicken for Mac, and can build a whole new ledger from a Quicken, Microsoft Money or other program's export. The format you pick decides how much work the import is: an OFX or QFX file goes straight in, a QIF may ask you to confirm its date format, and a CSV makes you label every column. Here's which file to use, each step as Banktivity's own help describes it, how import rules clean up what comes in, how to get old PDF statements in, and free files with known totals to test with first.
Short answer: in Banktivity for Mac choose File → Import Transactions, click "Import File", select the file and choose the account it goes into. Use OFX, QFX or QIF if your bank offers one, and CSV only if it doesn't: Banktivity's help says the first three "contain the most comprehensive transaction data." For a CSV, label each column (Amount, or Withdrawal and Deposit); unlabelled columns are skipped. Moving from Quicken? Start a new ledger with File → New Ledger and choose "Import from Other Software". 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
Banktivity doesn't publish a template file for imports. These files hold Utilly's fictional September 2026 checking and credit card statements in formats Banktivity imports, so you can try an import into a 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 | The 31 lines of the fictional checking statement: Date, Description, Amount, no header row | 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. In the CSV, dates are month first with slashes (09/01/2026), the description is the bank's text with commas and quote marks taken out, and Amount is one signed number with a period decimal: positive for a deposit, negative for a payment. There's no header row, because Banktivity's help doesn't say whether the importer skips one. The card statement comes as OFX and QIF only, since Banktivity's help doesn't say which sign a card CSV's amounts should use. The checking CSV is plain ASCII text with Windows line endings, about 1.4 KB.
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
09/02/2026,ACH DEBIT AUSTIN ENERGY UTIL,-412.66
2. Which format to import
Banktivity's help lists five file formats it imports transaction data from:
| Format | How Banktivity's help describes it | What the import asks you |
|---|---|---|
| OFX | Open Financial Exchange, "most commonly used by Microsoft Money" | Which Banktivity account the transactions go into |
| QFX | Quicken File Exchange, "also known as Web Connect format" | The account |
| QIF | Quicken Interchange Format | The account, and the date format if the dates are ambiguous |
| QMTF | Quicken Mac Transfer Format, "used by Quicken Essentials and Quicken for Mac 2015+" | The accounts to set up, and the date format if needed |
| CSV | Comma-Separated Values, "most commonly used with Excel and other spreadsheet programs" | A label for every column, the date format if ambiguous, and the account |
When you download from your bank's website, Banktivity's support article says: "If the OFX, QIF or QFX file format is available, choose one of those options as they contain the most comprehensive transaction data. If neither of those are available, choose the CSV format." Two CSV limits from the help: "Banktivity cannot import investment data from CSV files", and split transactions can't come in from a CSV either.
Banktivity can also bring transactions in without a file: its Direct Access subscription service (fees apply), Direct Download over the OFX protocol (Mac only, fewer banks, fees may apply), or the built-in web browser, which imports what you download from your bank's site. This guide is about files. If your bank only gives you a CSV, Utilly's CSV to OFX and CSV to QIF converters turn it into one of the richer formats.
3. Importing an OFX, QFX or QIF file
For accounts you've already set up in Banktivity:
- Download the file from your bank's website. Banktivity's support article suggests saving it to the Desktop on your Mac.
- In Banktivity choose File → Import Transactions, click "Import File" and select the file.
- If the file holds one account, choose the Banktivity account from the popup menu (the support article calls it the "import into:" drop down, so check it's the right account). If the file holds several accounts, choose a destination for each, or set it to "Do Not Import", then click Continue.
- If a QIF's dates are ambiguous, Banktivity asks you to choose the date format first. Utilly's QIF files write dates as MM/DD/YYYY.
A number appears next to each account in the sidebar showing how many transactions were imported. If you're starting a brand new ledger from a file instead, use "Import from Other Software" (section 5).
Shortcuts. You can make Banktivity the default app for QIF, OFX, QFX, QMTF or CSV files: select one in the Finder, choose File → Get Info, pick Banktivity under Open With and click "Change All". Then double-clicking a downloaded file starts an import. On iPhone and iPad, Banktivity imports QIF, QFX, OFX and CSV files sent from the Files app or a Mail attachment, and asks which account to import into if a ledger is open.
What's inside a QIF file, letter by letter, is on QIF format explained.
4. Importing a CSV file
- Choose File → Import Transactions, click "Import File" and select the CSV. Banktivity accepts "CSV files that use commas or semicolons as delimiters".
- Banktivity asks you to label each column. Drag the edges of the window until you can see every column, then "Click the heading above each column and choose a label for the data contained in that column."
- For the amounts: if the file has one amount column, give it the "Amount" label. If it has two (money out and money in), label them "Withdrawal" and "Deposit". The test CSV here has one signed Amount column.
- Click OK. If the dates are ambiguous, choose the date format; for the test CSV it's month, day, year.
- Choose the destination account and continue.
The rule people miss: "Any columns that are not assigned a label will not be imported." Banktivity remembers your labels based on the account selected when you chose File → Import Transactions, so the next CSV from the same bank is quicker. It "can only import standard transactions from CSV files", so a CSV can't carry splits, and it can't carry investment data.
5. Moving from Quicken, Microsoft Money or other software
To start Banktivity from another program's data, choose File → New Ledger, name the ledger, and choose "Import from Other Software". Then export from the old program as Banktivity's help describes:
| Coming from | What to export |
|---|---|
| Quicken for Mac 2015 or later, Quicken Essentials | File → Export → Quicken 2007 Transfer File, saved as a QMTF file. First shorten any category names over 55 characters; subcategories export as Category:Subcategory1:Subcategory2 and that whole string counts |
| Quicken for Mac 2007 or earlier | File → Export → To QIF |
| Quicken for Windows | Open any closed accounts, then export a QIF, all data in a single file if possible. If offered, choose "Loose" rather than "Strict", and nothing labelled "for Mac". Copy the file to your Mac |
| Microsoft Money | Open any closed accounts, then export each account to its own QIF file, loose format if offered, named exactly after the account it came from (mismatched names cause errors, particularly with transfers) |
| Other software | Open any closed or hidden accounts and export a QIF, a single file if possible |
Click "Choose File" and select the file (Shift-click to select several QIF files). Banktivity lists the accounts it found: tick the ones you want, rename them or change their account type or currency if needed, and click "Import Selected Accounts". With several QIF files, Banktivity works through one file at a time. Quicken's export cuts account names to 31 characters, but you can rename them during the import.
6. What happens during the import, and reviewing it
Every file import goes through the same steps:
- Duplicates. Banktivity compares incoming transactions with the ones already in the account and discards duplicates. Where there's no download metadata, it "checks for amounts that match exactly and dates that are no more than 7 days apart." Matched transactions get a Match badge.
- Cleared. Transactions that were imported or matched are marked Cleared.
- Transfers. Incoming lines that match a transfer in another account are linked and get Transfer badges. To stop this, choose Banktivity → Settings and uncheck "Automatically match transfers between accounts".
- Import rules then clean up payees and assign categories (section 7).
To review, select the account, click the arrow next to the Transactions button above the register and choose "Group New and Uncleared Transactions". Everything added, matched or connected to a transfer in the last import floats to the top. If two copies of a transaction got through, drag one onto the other to merge them; the merged transaction keeps the details of the one you dropped onto. To see a transaction as it was originally imported, double-click it and click the i button between the date and payee.
7. Import rules
Import rules "allow you to clean up this extraneous information and assign categories automatically during an import." You mostly don't set them up by hand:
- When you edit an imported transaction, the editor shows a "Create Import Rule" checkbox. Leave it ticked, fix the payee and category, and save: Banktivity creates a memorized payee with an import rule. For file imports, the rule looks for matching payees. If other transactions in the account have the same payee, Banktivity offers to change them too.
- To see and edit the rules, click Configuration in the sidebar, then Payees, Schedules & Rules, then Import Rules. Click Edit on a payee to see its rules, and use + and − to add or remove them.
- Rules are regular expressions; Banktivity says they "follow Apple's NSRegularExpression syntax", matched against the incoming payee and note joined by a hyphen. For a payee that changes with the date or store location, its help suggests a pattern like
APL ITUNES.*(the payee name followed by a period and an asterisk). - Import rules only apply to non-investment transactions, and changes to them only affect the next import, not transactions already in your accounts.
- To stop automatic rules, choose Banktivity → Settings and uncheck "Automatically create import rules when editing transactions".
8. PDF statements
Banktivity's import help lists QMTF, QFX, OFX, QIF and CSV and doesn't mention PDF. Banks often keep years of PDF statements but only offer a few months as downloads, so convert the PDFs first:
- Convert each PDF statement with Utilly's bank statement PDF to OFX converter 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 test account first (section 9) and compare it with the statement. If Banktivity asks about a QIF's dates, Utilly's QIF uses MM/DD/YYYY.
- Import the rest with File → Import Transactions, then review with Group New and Uncleared Transactions (section 6). Banktivity screens out duplicates where months overlap, but check the group anyway.
Prefer CSV? Utilly's standard CSV has a fourth Balance column and year-first dates. Leave the Balance column unlabelled so it isn't imported, and pick the matching date format if asked. The OFX or QIF route skips the labelling altogether.
9. Checking the import against known totals
Import the test files into a test account (and the card files into a test 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: a column wasn't labelled, or Banktivity treated some lines as duplicates of ones already in the account |
| Money out | 28,575.27 (20) | 1,939.94 (19) | A different total means a column got the wrong label |
| 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 |
| Dates | Sept 1–30, 2026 | Sept 1–30, 2026 | Other months mean the wrong date format was chosen |
| 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.
10. Problems and fixes
| Symptom | What Banktivity's help says |
|---|---|
| A CSV column (payee, memo) is missing after import | "Any columns that are not assigned a label will not be imported." Import again and label it |
| CSV has separate money-out and money-in columns | Label them "Withdrawal" and "Deposit"; a single amount column gets "Amount" |
| Splits or investment transactions didn't come in from a CSV | CSV imports carry standard transactions only, and no investment data. Use OFX, QFX or QIF |
| Dates in the wrong months | For QIF, QMTF and CSV files with ambiguous dates, Banktivity asks for the date format. Choose the one the file uses (MM/DD/YYYY for Utilly's files) |
| Transactions went into the wrong account | Check the account popup ("import into:") before importing; for files with several accounts, set a destination for each or "Do Not Import" |
| Duplicates after importing overlapping files | Banktivity screens most out. Drag one copy onto the other to merge, and choose download dates that don't overlap what you've already imported |
| A line was wrongly matched as a transfer | Banktivity → Settings, uncheck "Automatically match transfers between accounts" |
| An import rule renames or categorises the wrong transactions | Edit or remove the rule under Configuration → Payees, Schedules & Rules → Import Rules, or untick "Create Import Rule" when editing |
| Account or category names cut short after a Quicken move | Quicken limits exported account names to 31 characters (rename them during the import); keep category names to 55 characters before exporting |
| Transfers wrong after a Microsoft Money move | Name each QIF file exactly after the account it came from |
| Want to see what the bank file originally said | Double-click the transaction and click the i button between the date and payee |
Comparing programs? Moneydance's import ranks the same formats, HomeBank recommends OFX and needs CSVs in its own layout, and Quicken has its own CSV layouts.
Get PDF statements into Banktivity
PDF statements, downloaded or scanned, get a free preview with the balance check, no sign-up. Download OFX or QIF, formats Banktivity's help ranks above CSV. Already have a bank CSV? Turn it into OFX or QIF. Files are processed in memory and not stored.
Utilly isn't affiliated with Banktivity or IGG Software. The steps and quotes above are from Banktivity's help and support articles, checked November 14, 2026; the test files weren't imported into a live Banktivity ledger, and screens may differ between versions. Sources: How do I import transactions from my bank or other financial software?, How do I import transactions from a QMTF, QFX, OFX, QIF, or CSV file?, How do I use the built-in web browser to download transactions?, How do I review transactions after an import?, How do I use import rules?, Creating a New Ledger in Banktivity, How to use Manual/Web Downloads in Banktivity. If a screen differs, follow Banktivity's current help.
FAQ
What file formats can Banktivity import?
QMTF (Quicken for Mac 2015+ and Quicken Essentials), QFX, OFX, QIF and CSV, according to Banktivity's help. Its download articles say to pick OFX, QIF or QFX when your bank offers them, because they hold the most complete transaction data, and CSV only if none of those is available.
How do I import a CSV file into Banktivity?
Choose File, Import Transactions, click Import File and select the CSV. Click the heading above each column and choose a label: Amount for a single amount column, or Withdrawal and Deposit for two. Columns without a label aren't imported. Click OK, confirm the date format if Banktivity asks, and choose the destination account.
How do I import transactions from Quicken into Banktivity?
Create a new ledger with File, New Ledger and choose Import from Other Software. From Quicken for Mac 2015 or later, export with File, Export, Quicken 2007 Transfer File (QMTF); from Quicken for Mac 2007 or earlier, File, Export, To QIF; from Quicken for Windows, a Loose QIF of all accounts. Choose the file, tick the accounts and click Import Selected Accounts.
What are import rules in Banktivity?
Rules that clean up payee names and assign categories as transactions come in. When you edit an imported transaction with Create Import Rule ticked, Banktivity saves a memorized payee with a rule. You can edit the rules, which are regular expressions, under Configuration, Payees, Schedules & Rules, Import Rules. They apply to non-investment transactions and only to future imports.
Does Banktivity remove duplicate transactions when importing?
It screens them out automatically. Without download metadata it treats amounts that match exactly with dates no more than 7 days apart as a match. If it misses one, drag one transaction onto the other to merge them.
Can Banktivity import split transactions or investments from a CSV?
No. Banktivity's help says only standard transactions can be imported from CSV files, not split transactions, and that Banktivity can't import investment data from CSV files. Use OFX, QFX or QIF for those.
Can Banktivity import a PDF bank statement?
Banktivity's import help lists QMTF, QFX, OFX, QIF and CSV and doesn't mention PDF. Convert the PDF statement to OFX, QIF or CSV first, then import that file with File, Import Transactions.
Related guides
- Moneydance import: CSV, QIF and OFX files, step by step, with free templates
- QIF file format explained: every field, with a real example
- How to import a CSV file into Quicken (Windows, Mac and Simplifi)
- Free sample OFX file (bank and credit card), explained
- How to open a .QIF file (Quicken, Xero, GnuCash, Excel or no Quicken)
- 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.