Skip to main content

Import your bank's CSV

Load months of real history in one pass — map your bank's columns once, check the preview, then commit.

Updated Jul 30, 2026

On this page

Almost every bank lets you download your transactions as a CSV. Importing that file is the fastest way to give Fyncora enough history for budgets, reports and trends to mean anything.

Before you start: you'll need an account to import into and a CSV downloaded from your bank.

Upload the file

  1. Open Transactions and select Import.
  2. Leave the CSV tab selected.
  3. Choose the Account these transactions belong to.
  4. Optionally choose your Bank / Institution — a known bank auto-applies its format settings.
  5. Select the upload area and pick your file.
  6. Select Next.

You'll land on the Map Columns step with the first few rows of your file shown as a table.

Tip:

Tip: import one account at a time. The account you pick here applies to every row in the file, so a combined export needs splitting — or use Switch from another app, which resolves multiple accounts for you.

Map the columns

Fyncora guesses the common columns from their headers. Check each one and correct anything wrong.

  1. Confirm First row is header matches your file.
  2. Set the Date Column and the matching Date Format.
  3. Choose the Amount Mode — one signed amount column, or separate debit and credit columns.
  4. Set the Amount Column, or the Debit Column and Credit Column.
  5. Set the Description Column.
  6. Optionally map Merchant Column and External ID Column.
  7. Select Preview.

You'll see the preview step with counts for total rows, valid rows, invalid rows and duplicates.

Note:

Note: for European exports, set the Decimal Separator to a comma and pick the right Delimiter (many banks use semicolons). Getting these two wrong is the usual cause of amounts reading as zero or rows failing validation.

Tip:

Tip: if your bank includes a unique transaction reference, map it to External ID Column. It makes duplicate detection exact instead of approximate.

Check the preview, then commit

  1. Read the four counts — Total Rows, Valid, Invalid and Duplicates.
  2. Use Select All Valid or Deselect All, then tick or untick individual rows.
  3. Optionally set a category on rows in the preview table.
  4. Select Import N Transactions.

You'll see Import Complete! with how many were imported, skipped as duplicates, and skipped as invalid — plus a prompt if any of them look like bills you already track.

Warning:

Warning: a normal CSV import has no undo button. Check the preview before committing — especially that expenses and income are on the right sides. If you do import the wrong file, you can delete the transactions individually from Transactions.

Note:

Note: an import is capped at 5,000 rows. Split a larger export into several files.

How duplicates are detected

A row is flagged as a duplicate when its external ID already exists, or when its date, amount and description match a transaction already in that account. Flagged rows are unticked by default; tick one anyway and Fyncora will import it, because a genuine repeat purchase can look identical to a duplicate.

Every row is re-checked on the server when you commit, so nothing gets in on the strength of the preview alone.

FAQ

Can I import a PDF statement? There's a PDF tab, marked Beta, which supports a list of specific banks. CSV is the reliable route.

Will it create my categories? No — importing doesn't create categories. Rows arrive uncategorized unless you set a category in the preview, and you can categorize them afterwards. See Edit, categorize and tag transactions.

How are transfers handled? A bank CSV usually shows a transfer as an ordinary debit or credit on each account. Import them, then edit the pair if you want them recorded as a transfer.

I'm moving from another budgeting app. Use Switch from Mint, YNAB, Monarch or Copilot instead — it knows each app's columns and sign conventions.

Was this helpful?

Related

Still need help? Open a ticket.