PocketSmith import: CSV, OFX and QIF bank files, step by step
PocketSmith imports transactions from bank files: OFX, QFX, QIF and CSV. It doesn't take PDF statements. Its Learn Centre recommends OFX, and for a CSV you tell PocketSmith which columns hold the date, amount and merchant, then save that as a CSV format for next time. Here's which file to use, the three places to import from, the overlap options that decide whether you get duplicates, how to get PDF statements in, and free CSV test files with known totals.
Short answer: in PocketSmith go to Manage → Account Summary and drag the file onto the account (or use Manage Account → Import bank file, or + Add → Quick import on the Transactions page). For a CSV, choose or create a CSV format and assign the Date, Amount and Merchant columns. Pick an overlap option, then click Import my transactions. Use OFX if your bank offers it. Free test files: a checking CSV (31 fictional transactions) and a credit card CSV (21), plus the same statements as OFX.
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 PocketSmith imports, so you can try an import into a new offline 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, Merchant, 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 |
| Credit card CSV | The same header, then the 21 lines of the matching fictional card statement, by date | 19 charges 1,939.94; 2 credits 1,542.18; 397.76 more owed |
| 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 card lines, as the converter writes them | As the credit card CSV |
The rows come from Utilly's fictional sample statements (explained on sample bank statement PDF), read by the same engine Utilly's converters use. Each CSV has three columns: the date with the month as a word (01 Sep 2026), because PocketSmith's Learn Centre says date formats "that contain any explicit month names e.g. '20 Dec 2014' or '5 March 2015' work fine"; the statement description as the merchant (commas and quote marks taken out); and the amount as one signed number with a period decimal. Money out is negative on both files, card charges included, which is how PocketSmith expects them: its example is an expense of -23.95 and a credit card repayment of 300.00. The files are plain ASCII text with Unix line endings, about 1.4 KB and 1 KB.
Date,Merchant,Amount
01 Sep 2026,ACH DEBIT GUSTO PAYROLL 0912,-6420.18
01 Sep 2026,STRIPE TRANSFER ST-K2M8Q4,3184.27
02 Sep 2026,CHECK 2041,-1850.00
2. Which file to import
PocketSmith's Learn Centre lists four accepted file types, OFX, QFX, QIF and CSV, and says "We recommend using OFX files when possible."
| Format | PocketSmith's Learn Centre says | What it means for you |
|---|---|---|
| OFX | "OFX files follow a defined specification, which means you do not need to provide PocketSmith with any additional information" | The best choice. With Quick import, PocketSmith "will attempt to automatically choose the right account" |
| QFX | "A QFX file is a standard OFX file", Intuit's version for Quicken: "Typically, QFX files are just as seamless to use as OFX files" | Use it like OFX |
| QIF | "an older standard format, compared to OFX", that "should be imported as easily as OFX and QFX" | Fine, and it can carry categories. PocketSmith guesses a QIF's date format, as with CSV |
| CSV | "You should only choose CSV files if OFX, QFX or QIF files are not available" | Works with any bank's CSV once you map its columns (section 4) |
| "We cannot import bank statements or PDF files, as this is a presentation format" | Convert the statement first (section 6) |
Bank files are also how you get history older than your bank feed: the Learn Centre notes that feeds "can sync back up to 90 days", and you can import older transactions from files.
3. Importing a bank file, step by step
Into a new account (best for a test, and for history you don't have yet):
- Go to Manage → Account Summary.
- Hover over New offline account, click From a file import and pick the bank. If the bank isn't listed, first click + New Bank in the left sidebar, enter its name, choose Accounts from a file import and save.
- Enter the account name, opening balance and account type, then click Save and continue.
- Drag and drop the file, or choose it.
- For a CSV, choose a saved CSV format or create one (section 4).
- Choose the import options (section 5), then Import my transactions and OK.
Into an existing account: on the Account Summary, drag the file onto the account, or open the account's Manage Account menu and choose Import bank file. Then the same CSV format and import option steps. If the account was updated by a bank feed, the Learn Centre says the feed "will need to be unlinked from the account before files are imported".
Several files at once: on the Transactions page, hover over + Add, click Quick import, drop the files in, match each file to its account, set the CSV formats and options, and click Start Import. New users can do the same from the welcome page with Upload your data, which opens the Quick Importer.
4. Setting up a CSV format
A CSV has no standard layout, so the first time you import one PocketSmith shows a sample of its rows and asks what each column is. You need to identify three:
| PocketSmith column | Required? | In the test CSV |
|---|---|---|
| Date | Yes | Column 1 (01 Sep 2026) |
| Amount | Yes | Column 3, one signed amount (negative = money out) |
| Merchant | Yes | Column 2, the statement description |
| Categories, Labels, Notes | Optional | Not in the file; leave other columns not assigned |
- "Any column that remains 'not assigned' will not be imported." You may need to scroll right to see every column.
- Save the format with a memorable name and it's offered for the next CSV with the same layout. Saved formats are under User preferences → Saved CSV formats, where the trash icon deletes one.
- If your file has a category column, assign it as Categories and the categories come in with the transactions. OFX files can't carry categories.
- Don't open the CSV in Excel first. The Learn Centre says Excel "will often automatically change the date formats", and an 'Invalid date' error "usually happens when uploading a CSV file that has been previously opened in Excel".
5. Overlap options and duplicates
When you import into an account that already has transactions, PocketSmith looks for ones on overlapping dates and lets you choose what to do:
| Option | What happens |
|---|---|
| Replace transactions on overlapping dates (recommended) | No transactions go missing, but it "replaces all existing transactions within the date range your bank file spans, not just the transactions that match ones in the file", and their edits (labels, notes) are lost |
| Leave transactions on overlapping dates out | Keeps what's there and skips any file transaction on a date that already has one, which "may lead to missing transactions" |
| Keep all transactions | "may result in duplicates"; PocketSmith doesn't recommend it |
The Learn Centre's tip: export from the date of the latest transaction already in the PocketSmith account, then import with Replace transactions on overlapping dates. Importing the same file twice, or two files whose dates cross, with Keep all is how duplicates happen.
There's one more checkbox, Amounts in the statement file are reversed, for files where expenses come in as income. It's mainly for credit card files whose provider writes charges as positive numbers. The test files don't need it.
6. PDF statements
PocketSmith says it can't import bank statements or PDF files. To bring in months you only have as PDF statements:
- Convert each statement with Utilly's bank statement PDF to OFX converter, the format PocketSmith recommends, 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 offline account first (section 7) and compare it with the statement.
- Import the rest, oldest first, with Replace transactions on overlapping dates if months touch.
Prefer CSV? Utilly's CSV download from the same preview (or bank statement to CSV) has Date, Description, Amount and Balance columns with numeric year-first dates. Assign Date, Description as Merchant and Amount, leave Balance not assigned, and check the months after the import, since PocketSmith works out numeric date formats itself. OFX avoids the question.
7. Checking the import against known totals
Import the test files into a new offline account (and the card file 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: an overlap option left some out, or a row didn't parse |
| Money out | 28,575.27 (20) | 1,939.94 (19) | A different total means a column was assigned 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 (re-import with Amounts reversed) |
| Dates | Sept 1–30, 2026 | Sept 1–30, 2026 | Other months mean the date format was guessed wrong |
| Statement balance | 12,418.36 → 13,440.52 | owed 2,846.12 → 3,243.88 | Set the test account's balance to match the statement |
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.
8. Problems and fixes
| Symptom | What PocketSmith's Learn Centre says |
|---|---|
| 'Invalid date' error on a CSV | Usually the file was opened in Excel first. Re-download it from the bank and upload it without opening it |
| 'Import failed due to date detection error' | Too few transactions to work out the date format; export a wider range of dates within the month |
| Transactions in the wrong months | A numeric date format was guessed wrong (common when every transaction falls on the same day of the month, or over a short span). Change the dates to a format with the month as a word, like '02 September 2014', in a plain-text editor, or use OFX |
| Expenses showing as income | Re-import on the Account Summary with Replace transactions on overlapping dates and Amounts in this statement file are reversed. Categories, labels, notes, attachments and splits on those transactions are lost |
| 'Data is malformed' | The file is incorrectly formatted; re-export it from the bank and don't open or edit it before importing |
| 'Import failed because there were no transactions to import' | Every date in the file already has transactions and Leave transactions on overlapping dates out was chosen; pick another overlap option, carefully |
| 'Import failed due to an unknown error' | Often the wrong saved CSV format was selected, or the file has formatting errors |
| Can't import into an account | If it was updated by a bank feed, unlink the feed before importing files |
Comparing apps? Monarch Money and YNAB import CSVs in their own layouts, Actual Budget also maps your columns, Firefly III takes CSV through its Data Importer, Spendee takes CSV or Excel files in its web app, Wallet by BudgetBakers takes CSV, Excel and OFX 2.2 files in its Web App, and desktop programs like KMyMoney, Moneydance and HomeBank take the same OFX, QIF and CSV files.
Get PDF statements into PocketSmith
PDF statements, downloaded or scanned, get a free preview with the balance check, no sign-up. Download OFX, the format PocketSmith recommends, or QIF. Already have a bank CSV? PocketSmith can map it, or turn it into OFX first. Files are processed in memory and not stored.
Utilly isn't affiliated with PocketSmith. The steps and quotes above are from PocketSmith's Learn Centre, checked November 18, 2026; the test files weren't imported into a live PocketSmith account, and screens may differ. Sources: Bank files: an introduction, Preparing your bank files & accepted file types, Importing bank files into PocketSmith, Transaction dates are incorrect, Expense transactions showing as income, Troubleshooting imports, Managing categories from bank files. If a screen differs, follow PocketSmith's current Learn Centre.
FAQ
What file types can PocketSmith import?
PocketSmith's Learn Centre lists four: OFX, QFX, QIF and CSV, and recommends OFX when possible. It says it cannot import bank statements or PDF files, because PDF is a presentation format.
How do I import a CSV into PocketSmith?
Go to Manage, Account Summary and drag the file onto the account (or use Manage Account, Import bank file, or Quick import on the Transactions page). Create a CSV format by assigning the Date, Amount and Merchant columns, choose an overlap option and click Import my transactions.
What columns does a PocketSmith CSV need?
You have to identify a Date, an Amount and a Merchant column. Categories, Labels and Notes columns are optional, and any column left not assigned isn't imported. Save the format to reuse it for the next file with the same layout.
How do I avoid duplicate transactions in PocketSmith?
When importing into an account that already has transactions, choose Replace transactions on overlapping dates, which PocketSmith recommends, and export from the date of the latest transaction already in the account. Note it replaces every existing transaction in the file's date range and their edits.
Why are my PocketSmith import dates wrong?
PocketSmith works out numeric date formats itself and can guess wrong, for example when all transactions fall on the same day of the month, or after Excel changed the dates. Dates with the month as a word, like 20 Dec 2014, work fine; or import OFX.
Can PocketSmith import a PDF bank statement?
No. Its Learn Centre says it cannot import bank statements or PDF files. Convert the PDF statement to OFX (the format PocketSmith recommends) or QIF first, then import that file.
Related guides
- How to import transactions into Monarch Money (CSV format, free template, old statements)
- YNAB CSV import: the format, a free template, and how to import past transactions
- KMyMoney import: CSV wizard, QIF and OFX files, step by step
- Moneydance import: CSV, QIF and OFX files, step by step, with free templates
- Free sample OFX file (bank and credit card), explained
- How to open an OFX, QFX or QIF file (Excel, Quicken, text)
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.