What import is for
If you would rather not type months of bank history by hand, the import tool walks you through turning a downloaded statement into real transactions, one clear step at a time. 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.
Import 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, tell Rasa Money how to read its dates and amounts, 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.
Along the way you can map optional columns (notes, cheque numbers, status) and, if the account has never had a transaction, align its opening balance to the statement. There is also an optional AI helper that can suggest categories from descriptions so you are not tagging hundreds of rows by hand.
Treat each import as a batch with a clear date range. Overlapping imports of the same statement can create duplicates unless you exclude rows you already have. When in doubt, import a shorter range first and confirm balances before loading the rest.
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, predict future transactions, or merge two accounts for you. Those remain manual product workflows. 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 AI categorization, see Letting AI suggest your categories. 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.