Import and clean data

Import CSV statements

Upload a statement file, map its columns once, review every row, and save the batch — nothing is written until you confirm.

Last updated 2026-09-11

Use this page to bring statement data into TallyFolio from CSV files — the normal way to load history in bulk. There is no bank connection: the file comes from you, downloaded from your own bank.

The flow is upload, map, review, commit. The file is parsed for your review and thrown away — it is never stored. Only rows you approve become transactions, saved together as one batch you can remove later in a single step if the import was wrong.

Before you start

  • Download a CSV statement from your bank's website. Files up to 10 MB are accepted.
  • The account the statement belongs to must already exist in TallyFolio.
  • Keep your own copy of the file — TallyFolio doesn't store it after parsing.

How to use it

  1. Open the Import page, upload the file, and pick the account it belongs to.
  2. Map the columns: tell TallyFolio which column holds the date, the amount, and the description. Every bank's CSV layout is different, and mapping isn't guaranteed to be right automatically — always spot-check a few rows. Save the mapping as an import profile so the next statement from this bank is one click.
  3. Review every row: fix categories, adjust transaction types, attach labels in bulk, and uncheck anything you don't want. Rows that look like transactions you already have are flagged as likely duplicates — flagged, not blocked, so the decision stays yours.
  4. Watch for rows marked Receipt. Those match a transaction you already recorded from a receipt: same account, same amount, within a week. They arrive unticked so the purchase isn't recorded twice, and you can tick one back on if it really is a separate charge.
  5. Check the direction shown beside each amount. A row that put money into the account reads +, one that took money out reads −, and money you moved between your own accounts — a credit-card payment, a transfer from savings — keeps whichever direction the statement gave it.
  6. Commit the import. All approved rows are saved together as one batch, and your category corrections are remembered as merchant rules for future imports.

After the import

  1. Skim the new transactions on the Transactions page and fix any category the merchant rules didn't cover.
  2. Use "apply to similar transactions" to fix a whole merchant's categorization in one pass if the import surfaced a recurring mistake.

What affects this page

  • Import profiles you saved — they pre-fill the column mapping per bank.
  • Merchant rules from past imports — they pre-assign categories to familiar merchants.
  • Transactions you already have — each incoming row is compared against them so likely duplicates get flagged.

What does not affect this page

  • Your bank — nothing is fetched from it and nothing is sent to it. The CSV is the only input.
  • Your ledger, until you commit — parsing and reviewing writes nothing.
  • The uploaded file's future — it's read in memory for the review and discarded; it never becomes part of your stored data.

Common mistakes

  • Importing the same statement twice and approving the flagged duplicates. Read the flags before committing.
  • Mapping the amount column with the wrong sign convention and saving expenses as income. Check a few rows in the review step — this is the single most common import mistake. It also flips the direction of transfers and card payments, so the account balance ends up moving the wrong way.
  • Skipping the review. The review is where categories, types, and labels get set while the context is fresh.
  • Assuming every column mapped correctly because the preview looked plausible. Verify dates and amounts against the statement before committing.

FAQ

Does TallyFolio connect to my bank?
No, never. You download the CSV from your bank yourself and upload it here. No bank credentials are ever asked for.
Why are my amounts inverted after import?
The amount column was mapped with the opposite sign convention — some banks export expenses as negative, others as positive. Remove the batch from Settings, re-import with the corrected mapping, and update your saved profile.
Can I undo an import?
Yes. Each import is saved as one batch, and the Data section of Settings can remove an entire batch's transactions in a single step.
Are duplicate rows blocked automatically?
No — they're flagged for your decision. Some legitimate charges look identical (two same-day coffees), so TallyFolio highlights suspected duplicates instead of silently dropping them.

Where this lives in the app

Related articles

  • Transactions

    Every money movement in TallyFolio is a transaction. Learn the types, the statuses, and how to keep them categorized.

  • Labels

    Labels group transactions and assets by trip, project, or event — without changing any of the math.

  • Export your data

    Download your record as CSV files, restore core data from a TallyFolio export ZIP, or export just the filtered view you're looking at.

  • File receipts from your email

    Hand an assistant a routine that turns receipt emails into drafts you confirm. It uses its own email access; TallyFolio never touches your mail.