Bank connection is the smoothest way to feed transactions into WatchYour.money, but it is not the only way, and sometimes it is not available for your bank at all. That is where the CSV import comes in. Almost every bank and credit union lets you download your account history as a CSV file. WatchYour.money can read that file, map its columns to the right fields, and turn hundreds of past transactions into a clean, categorized history in a couple of minutes. This guide walks through the full process, from exporting the file at your bank to confirming a tidy import with no duplicates.
When to Use CSV Import
CSV import shines in three situations, and knowing which one you are in shapes how you approach the upload.
- Your bank is not supported for live connection. You still get full history and categorization, just on a schedule you control.
- You want to backfill history. Bank sync usually grabs the last 30 to 90 days. A CSV export can cover years, giving the AI more data to learn your patterns.
- You prefer manual control. Some users simply do not want a live connection, and CSV import respects that preference without sacrificing automation.
Step 1: Export the CSV From Your Bank
Log in to your online banking and find the export or download option, usually tucked into the transactions or statements area. Select the account and the date range you want, choose CSV as the format, and download the file.
Tips for a Clean Export
- Export one account at a time so the file stays focused.
- Pick a reasonable range, a full year is a good starting point for backfill.
- Open the file once before importing to confirm it has the columns you expect.
- Save the original somewhere safe; you may want it again if you ever need to re-import.
Step 2: Understand the Columns WatchYour.money Needs
Every bank labels columns differently, but the importer only cares about a handful of fields. During import you will map your bank's columns to these standard fields.
- Date — when the transaction occurred or posted.
- Description or merchant — the bank's memo line.
- Amount — the transaction value, including whether it is positive or negative.
- Optional fields — categories your bank assigns, balance after transaction, notes.
You do not need every optional field. The required ones are date, description, and amount.
Step 3: Start the Import in WatchYour.money
Open WatchYour.money and go to Transactions, then choose Import. Select the account you want the transactions to land in, or create a new manual account if this bank is brand new to the app. Drag and drop your CSV file into the upload area.
The Column Mapping Screen
WatchYour.money reads the header row and tries to guess which of your columns maps to each standard field. Review the guesses carefully. If the date is in an unexpected format, or if the amount column uses a separate sign column, adjust the mapping so the data lines up correctly.
Handling the Amount Column
This is the most common source of import errors. Some banks use a single column where expenses are negative and income is positive. Others split it into two columns, debits and credits, or use a separate column for the sign. The importer lets you tell it which convention your file uses so the final amounts come out correct.
Step 4: Preview and Confirm
Before anything is saved, the importer shows a preview of the first rows as they will appear once imported. Scan the preview for three things.
- Dates look right and are not shifted by a day or a month.
- Amounts have the correct sign — money leaving your account is negative.
- Descriptions are intact and not cut off or merged.
If anything looks wrong, step back to mapping and fix it. Once you confirm, the import runs, usually in seconds for a few hundred rows.
Step 5: Let AI Categorize the Batch
Once the transactions land, the AI categorization engine processes them in bulk. Most entries get a category within moments based on the merchant name and amount, exactly as it would for live transactions. Spend two minutes reviewing the results, fixing the occasional miscategorization, and the AI learns your preferences for next time.
Avoiding and Resolving Duplicates
Duplicate transactions are the main risk with CSV import, especially if you import overlapping date ranges or switch between manual and synced data. WatchYour.money handles this in two ways.
Automatic Deduplication
When you import transactions that overlap with existing ones, the importer compares date, amount, and description and flags likely duplicates before saving. You can choose to skip them or import anyway.
Manual Merge
If a duplicate slips through, open the Transactions list, select both copies, and merge them. The resulting transaction keeps the cleaner description and preserves any category or tag you already applied.
Best Practices for Recurring Imports
If your bank is not supported for live sync, you will likely import CSV files regularly. A few habits keep that process painless.
- Import on a fixed cadence, like the first of every month, so nothing falls behind.
- Use consistent date ranges that pick up where the last import ended to avoid gaps and overlaps.
- Keep your manual account separate from any synced account to prevent cross-contamination.
- Review the post-import summary each time to catch any mapping quirks specific to a new export.
Common Import Issues and Fixes
Dates Land in the Wrong Year
This usually means a date format mismatch, such as day-first versus month-first. Return to mapping and switch the date format, then re-preview.
Amounts Are All Positive
Your bank may use separate debit and credit columns or a sign column. Tell the importer about that structure during mapping so expenses become negative.
Some Transactions Are Missing
Check the original CSV for rows with unusual formats, blank amounts, or extra commas inside quotes. Clean those rows in a spreadsheet and re-import the fixed file.
FAQ
What file formats can I import?
WatchYour.money accepts CSV files, which is the universal export format offered by virtually every bank. If your bank exports in another format, open it in a spreadsheet application and save it as CSV before importing.
Will importing a CSV create duplicate transactions?
Not if the date ranges do not overlap. When ranges do overlap, the importer flags likely duplicates based on date, amount, and description, and lets you choose to skip them. Any duplicate that still slips through can be merged manually in the Transactions list.
Can I import transactions in a foreign currency?
Yes. Assign the account's currency when you create it, and imported amounts are stored in that currency. If your bank's CSV includes transactions in multiple currencies, consider splitting the file by currency into separate accounts for cleaner reporting.
Conclusion
CSV import is the reliable fallback when live bank connection is not an option, and it is the fastest way to backfill years of history so the AI has rich data to learn from. Map the columns carefully, preview before confirming, and let the categorization engine do the heavy lifting once the rows land.
If you want to bring your full financial history into one place, WatchYour.money makes CSV import straightforward with smart column mapping, duplicate detection, and automatic categorization. Upload your bank's export once and watch months of past spending turn into organized, searchable insight.