How to import bank statements into an iPhone expense tracker

Starting an expense tracker does not have to mean retyping every purchase from last month. A statement import can give you a useful starting point, especially when you want your history without a continuing bank connection.

FinTracker reads CSV files and text extracted from PDFs locally, then asks you to review the transactions. The useful result is a record you can reconcile, not simply a large number of imported rows.

Start with a short CSV export

Download a week or month of transactions from your bank or previous tracker. Choose CSV if available: its rows and columns are usually easier to inspect than a page layout. Keep the original file so you can compare it with the import.

For a harmless first attempt, download our sample CSV. It contains three invented euro transactions. Its technical headers are Date, Description, Amount, and Currency; leave those labels and ISO dates unchanged when trying the sample.

Date,Description,Amount,Currency
2026-10-01,Sample salary,2000.00,EUR
2026-10-02,Sample groceries,-42.50,EUR
2026-10-03,Sample coffee,-4.50,EUR

Negative amounts in this sample are expenses; the positive amount is income. A bank export may instead use separate debit and credit columns. FinTracker recognizes several English and German header patterns, but it does not understand every bank's naming or file layout. Work on a copy if you need to prepare a simpler file.

Open the file in FinTracker

Open the scan entry, choose Files, and select your CSV or PDF. Review the parsed rows before confirming. You can include or exclude rows and change categories. Nothing is imported until you approve the selection.

A small import you can check

1. 01
   Incoming payment+€2,000.00 · Sample salary2026-10-01 · Check that the direction is income.
2. 02
   Outgoing payment−€42.50 · Sample groceries2026-10-02 · Review the category and statement currency.
3. 03
   Another purchase−€4.50 · Sample coffee2026-10-03 · Include it only if it is not already recorded.

An active trial or subscription is required for importing and editing records. File parsing is local. Suggested exchange rates, if requested for foreign currencies, need an internet connection; optional online AI features have their own data flow. Importing a statement does not grant FinTracker ongoing access to your bank.

Check five things before you confirm

1. Dates: verify an unambiguous transaction, especially if the file uses day/month rather than month/day.
2. Direction: check salary, purchases, and refunds so income has not become spending.
3. Currency: choose the statement currency for amounts without a detected code. Review foreign-currency rates where relevant.
4. Categories: replace rough suggestions with categories you will actually use.
5. Completeness: compare row counts and totals with the same period in the original file.

The review lets you select rows and categories, but it is not a general spreadsheet editor. If a date or amount was parsed incorrectly, cancel and fix a copy of the source file, or leave that row out and enter it manually. The parser skips rows it cannot read cleanly; an import can look plausible while still missing purchases.

Treat duplicate flags as a starting point

FinTracker marks likely duplicates using the day, amount, and payment direction. Those rows start unticked. Check them rather than automatically including everything: two identical coffee purchases can be real, while a manually logged lunch may also appear in the statement.

Begin with a small date range and avoid overlapping exports until you understand the result. Keep card repayments, account transfers, and actual purchases distinct so the same spending is not counted twice. Our no-bank-connection guide explains the ongoing review habit.

If a PDF does not import properly

A text-based PDF is different from a scanned image. Try selecting a transaction line in the PDF. If there is no readable text, the statement-file reader cannot extract transactions from that file. Complex columns or unusual line breaks can also prevent clean parsing.

Ask your bank for CSV, export a simpler period, or add the missing entries manually. Receipt scanning is a separate workflow described in the receipt guide. Do not assume that a photograph of a full statement will behave like a structured CSV import.

Turn the history into a useful plan

After confirming, compare the saved transactions with the source once more. Keep statement files somewhere appropriate for financial information, and remove temporary copies when you no longer need them.

Use the category totals to build a simple monthly budget, then track savings goals alongside it. You can continue with manual or voice entry and import another short period later. Explore FinTracker to see how local tracking fits your routine.