Statement file formats explained
What each bank statement file type is, which carry running balances, and why a text PDF is the last resort for importing into a budget.
Get a Wise account statement or transaction history as a CSV file and import it into Tally, where each currency becomes its own account.
Wise lets you download a CSV two ways: an account statement for one or more currencies, or a transaction history from the Transactions tab on the website. Tally reads both. For budgeting, the account statement is usually the better choice, because it carries a running balance.
Wise’s help article “How do I download a statement?” says you can download statements for your currencies and jars for “a 365-day period at a time”, from the website or the app. For longer stretches you download several statements. It lists the formats on the website as PDF, XLSX (Excel), CSV, MT940, QIF or CAMT.053, and in the app as PDF, CSV and XLSX (Wise: download a statement, checked 8 October 2026).
The article gives two routes to the same place:
You can select several currencies at once, and depending on the file size Wise either downloads straight away or emails you a link. Wise’s page also says you may be asked for your Wise password. Wise’s screens change, so follow the current help page if yours looks different.
Wise’s help article “How do I download my transaction history?” says to go to the Transactions tab on the website, use Filters to narrow the list, then choose Export and pick CSV or PDF. It says this is available on the website and not in the mobile app, that you can cover up to a 365-day period, and that download links expire after 7 days (Wise: download transaction history, checked 8 October 2026).
The statement article adds a useful difference: regular statements show transactions in your Wise currency balances, while the Transactions page can also include activity done through external payment methods.
Pick the account statement as a CSV if you want the most useful import. Pick the transaction history CSV if you want activity that a statement leaves out.
| Account statement (CSV) | Transaction history (CSV) | |
|---|---|---|
| Where | Statements and reports | Transactions tab, then Export (website only) |
| Running balance | Yes, so safe to spend has a starting point | Check your file |
| Tally reads it | Yes | Yes |
Tally also reads a US-date variant of the account statement. You do not need to change anything. It looks inside the file to see which layout it has.
For why separate accounts matter, read how to budget in two currencies.
Yes. Because Wise gives each transaction an ID, Tally uses that ID to recognize a row it has already seen, so a second import of an overlapping period skips those rows. See how Tally catches duplicate transactions.
One caution: if you import the same Wise balance once as a statement and once as a transaction history, check that you did not end up with two accounts. Pick one format per account and keep it.
For a first import, download a year at a time and import each file. After that, a monthly download is enough. Overlapping dates are safe.
Wise offers QIF, MT940 and CAMT.053 on the website. Tally reads QIF, but it has no reader for MT940 or CAMT.053, so use CSV for Wise. QIF files often lack a running balance, which safe to spend needs. More in statement file formats explained.
No. This guide just covers how to export your own data from a Wise account you already have. Tally is not affiliated with Wise, and Tally is still in development with no public sign-up.
Here is what happens when you import it: format detection, duplicate checks and one account per currency.