Importing and Categorising Transactions

Open a bank account, choose Transactions, then click Import CSV. ForwardFi detects common date, payee, amount, debit, credit, description, reference, and transaction-ID columns. Confirm the suggested mapping and date format before reviewing the rows.

Files may contain up to 10,000 rows and must be no larger than 10 MB. ForwardFi stores normalized transactions and the mapping used, but does not retain the original CSV.

The review step identifies invalid rows, exact duplicates, possible duplicates, automatic category matches, and rows that still need a category. Exact duplicates are skipped. Possible duplicates are also skipped unless you explicitly include them.

Assign categories individually or in bulk. You can also add and edit transactions manually after the import. Mark transfers or excluded transactions so they do not affect spending totals.

Rules match the payee using contains, equals, starts-with, or ends-with. They are case-insensitive and run from top to bottom; the first match wins. Rules only fill uncategorised transactions unless you explicitly request a reapplication, so manual choices stay intact.

Imported and manual transactions describe the past. They do not update the account balance or reconcile scheduled forecast occurrences. Forecast rules and one-off forecast transactions continue to describe the future separately.