Importing a Bank Statement

If your bank isn't supported by Plaid, or you'd simply rather not connect it, you can bring transactions in yourself by uploading a CSV or Excel file. It takes a few extra minutes compared to bank sync, but gives you the same clean result.

The four-step wizard

1. Attach file: drag a file in or browse for one. CSV, XLSX, and XLS are all supported.
2. Account & format: choose which account the transactions belong to, the date format your file uses, and whether amounts are a single column (positive for credits, negative for debits) or split across separate Received and Spent columns.
3. Column mapping: tell Fyscal which column in your file is the date, which is the amount (or received/spent), and which is the description.
4. Review & import: see a summary of total rows, rows skipped for having no value, and rows with problems, before anything actually gets imported.

All-or-nothing validation

If even one row has a real problem, like a date Fyscal can't parse or an amount that isn't a number, nothing gets imported until you fix it. This is deliberate: it's safer to catch a formatting issue before 500 transactions land in your ledger than to clean it up after. Rows that are simply blank, both inflow and outflow empty or zero, are quietly skipped instead of counted as errors.