What import is for
If you would rather not type months of bank history by hand, the import tool turns a downloaded statement into real transactions in four short steps. It is built for CSV or Excel exports from your bank, not for connecting a live bank login — Rasa Money never asks for bank credentials.
Importing from a CSV or Excel file is a Pro capability. Use it when you are catching up a ledger, migrating from a spreadsheet, or loading a chunk of history into an account you already created.
Import shines when you already have months of CSV history from online banking or another spreadsheet-based tracker. It is faster than manual entry and still keeps you in charge of every row that becomes a transaction.
The path from file to ledger
You upload your file, check the columns, dates and amounts Rasa Money detected, pick which account the rows belong to, and review everything before anything is saved. Nothing is created until you say go on that final screen.
Rasa Money does a lot of the thinking for you: it suggests the column mapping and date format, proposes a category for each row, suggests tags from your own history, and spots payments that repeat so you can turn them into recurring series. Every one of these is a suggestion you can change.
Along the way you can map optional columns (notes, cheque numbers, status, and on Pro a Tags column) and, if the account has never had a transaction, align its opening balance to the statement.
Treat each import as a batch with a clear date range. Rasa Money flags rows that already exist in your ledger — same account, same day, same amount and type — and leaves them unselected, so re-importing an overlapping statement does not quietly double your history. When in doubt, import a shorter range first and confirm balances before loading the rest.
Where to start an import
Open Transactions and choose Import transactions. You can also start from an account: open the account card menu and choose Import into this account, and that account is already selected for you. Empty lists, the empty dashboard and the setup checklist offer the same shortcut.
What import will not do
Import does not continuously sync with your bank. Each run is a deliberate upload of a file you control. It also will not invent accounts for you — pick an existing account (or create one first) so balances stay coherent.
Rows you exclude on the review screen never become transactions. Invalid rows must be fixed or unchecked before you can finish.
It will not reconcile against a live bank feed or merge two accounts for you. Repeating payments are only suggested as recurring series — nothing becomes a series until you accept it. Import is deliberately file-based so you always know what entered the ledger.
Tips and what to read next
Start with a clean export from your bank for a single account and a date range you understand. If something fails, keep the file handy when you contact support.
For the wizard sequence, see What you will be asked at each step. For categories, see Letting AI suggest your categories. For repeating payments, see Finding repeating payments in your file. For labels, see Importing tags from your file. For prep tips, see Getting your file ready.
Keep the original bank file alongside the date you imported it. If a category or amount looks wrong a week later, that file is the fastest way to see whether the bank export or the mapping step caused it.