Exporting your transactions

There are two places to export from, and they behave differently, including by plan.

On the free plan, use the Transactions page. Its Export button works on every plan. The Data Export section in Settings is part of the paid plans and is not shown on the free plan, so the PDF statement, the category analysis and the full ZIP need a paid plan.

Neither route caps how often you export.

On the Transactions page, an Export button gives you CSV or Excel (XLSX) of the list as you have filtered it.
In Settings, under Data Export, you get the same transactions export plus three others: a PDF financial statement, a category analysis and a full ZIP of everything.

The four exports in Settings are not four formats of one thing.

Export Transactions: CSV or Excel

Either entry point writes the same file, in CSV or Excel (XLSX).

From the Transactions page, your filters come with it. The Export button carries the date range you have chosen (including a custom range and its dates), the account you have selected, the categories you have selected, and whether Show Duplicates is on. So filter the list until it shows what you want, then export it.

From Settings, you set the range there instead, independently of the list.

One thing to watch. If the range is all time, the export does not go back forever: it falls back to one year before the end date. To export more than a year, set the start date yourself.

The columns, in order

Fourteen columns, with the same names in every language because they are literal file headers:

Date, as YYYY-MM-DD.
Year, as a number, for pivoting.
Month, as YYYY-MM.
Description.
Amount, in the transaction’s own currency.
Currency.
Converted Amount (CUR), the same amount in your default currency, converted at the rate for that transaction’s date, so multi-currency data adds up. The header names the currency.
Category, as its slug. An uncategorised row reads uncategorized_income or uncategorized_expense rather than being left blank.
Account, the account name.
Account Type.
Balance, the running balance on that transaction.
Type.
Status.
Is Duplicate, true or false.

Duplicates are left out by default. A transaction you marked as a duplicate is not in the file unless you turn on Show Duplicates on the Transactions page before exporting, which is what sets the flag the export reads. When they are included, the Is Duplicate column tells you which they are.

Split parents are always left out. When you split a transaction, the export carries the parts rather than the original, because the parts hold the real amounts. Totals therefore add up once, not twice.

What the export leaves behind. A transaction can carry a Reference and Notes, but neither is among the fourteen columns, so they do not survive an export. If you keep important context in Notes, the export is not a complete record of it.

Generate Reports: the PDF statement

Financial Statement (PDF) produces a report with income, expenses and category breakdowns. Set a Date Range, then choose what goes in under Include Sections:

Include Income
Include Expenses
Include Accounts
Include Net Worth

Then Generate PDF. This is a formatted document for reading or printing, not a spreadsheet, so it is the wrong tool if you want to sort and filter rows.

Generate Reports: Category Analysis

“Export detailed spending breakdown by category with statistics and percentages.” Comes as CSV or Excel, with its own date range. Use this when you want totals per category rather than one row per transaction.

Full Data Export: everything, as a ZIP

Full Data Export (ZIP), via Download Complete Data, gives you all of your financial data as JSON in one archive: transactions, accounts, categories and the rest. This is the one to use for a backup, or to take your data elsewhere under GDPR portability.

Finthy warns you when you download it, and the warning is worth taking seriously: the file contains all of your sensitive financial information. Store it somewhere safe and delete it when you are done with it.

If an export fails

Each export reports its own failure and changes nothing when it fails, so you can simply try again. A very large date range on the PDF statement is the usual cause; narrow the range and generate it again.