CSV import is useful for historical backfills, unsupported institutions, and manually managed accounts. Start with a small representative file when importing a new format.

Prepare the file

Export transactions from your bank as CSV. The file should contain:

  • one transaction per row;
  • a transaction date;
  • either a signed amount or separate money-in and money-out columns; and
  • a description or payee.

Remove headings, totals, and blank rows that are not transaction records. Do not alter amount signs unless you understand how the export represents income and spending.

Start the import

  1. Open Settings → Data → Import & export and select Import CSV.
  2. Choose the destination account.
  3. Upload the CSV file.
  4. Match the file columns to the Plutus fields.
  5. Check the date format, amount interpretation, and preview.
  6. Confirm the import when the sample rows look correct.

Review the preview

Check at least one income, one expense, and any unusual refund or transfer. A sign error can reverse the meaning of an entire import.

If the file contains both debit and credit columns, map each to its matching direction rather than combining them outside Plutus.

Confirm the result

After import, filter Transactions to the destination account and imported date range. Compare the number of rows and a few balances against the source statement.

Correct payees, categories, and transfers before creating automation rules from the imported data.

Common problems

  • Re-export the file if spreadsheet software changed dates or account numbers.
  • If every amount has the wrong sign, stop and undo the import if that option is available.
  • Avoid importing the same file twice. Use filters to check whether the date range is already present.
  • Split very large files into clear, non-overlapping periods when troubleshooting.

Next steps