Import data

Bring transactions in from your bank. Supported formats: QIF, OFX, CSV, MT940, and CAMT.053 (the ISO 20022 statement format Swiss and EU banks are migrating to).

Steps

1. Pick a parser or leave it on Auto — content sniffing usually nails it.
2. Pick a file or paste the content directly into the textarea.
3. Tap Parse. For CSV, a column-mapping panel appears; assign Date and Amount at minimum, then re-tap Parse.
4. Review the preview, pick the target account, tick or untick rows you want to skip, then commit.

Coming from another app

On the CSV mapping step, the Came from row recognises exports from other finance apps by their column headers and maps everything for you: YNAB, Actual Budget, Bluecoins, Wallet by BudgetBakers, Money Manager, 1Money, and Monefy. The matching preset auto-selects when the file's headers fit; the date-order and decimal chips stay editable because these apps export locale-dependent formats. Pick Custom to map columns by hand as before.

Duplicate detection

If an OFX row's FITID already exists in the target account, the preview tags it as duplicate and auto-skips it. Tap the row to override — useful when the bank reused an id on a fresh export.

Status after import

Imported rows land as unaccepted so they don't move the running balance until you've reviewed them. Open the transactions list and accept rows one by one or in bulk.

The reconciliation status follows the source file: bank-booked rows (CAMT.053, MT940) and rows your old app had marked cleared arrive as Cleared; pending bank entries arrive as Pending; everything else starts as Entered. Imports never create Reconciled rows — that state is reserved for statements you balance here.

Tips

• Use Start over at the bottom to wipe the wizard's state and restart without leaving the screen.
• The step badge in the top-right (Step N of 4) reflects where you are: Source → Map columns → Review → Done.