Bank Statement Kit logo Bank Statement Kit Convert PDF

Wise Statement to CSV: Balances, Jars and Conversions

You need Wise transactions in a spreadsheet, and you need every movement accounted for — card spending, incoming payments from clients abroad, the currency conversions between your balances, and the fees Wise charges on top. Maybe it is a tax return, a mortgage file, a visa application, or a freelance business whose income arrives in three currencies.

The honest answer first: Wise has one of the better native exports in banking, and most of the time you should use it. This post covers when that is true, what to do when only a PDF exists, and how to prove the CSV you end up with actually matches the statement.

Quick answer

There are two ways to get Wise transactions into CSV:

  1. Wise's own statement export. From the web or the app you can generate a statement across the currencies and Jars you choose, for a period of up to 365 days, in a range of formats including CSV and XLSX. If you can log in, take this.
  2. Convert the PDF statement. Sometimes the PDF is all there is — an official statement produced for a lender or an immigration caseworker, a stamped and signed document, a period you exported once and saved, or a statement a client sent you. Upload it to a converter like BankStatementKit, which reads the transactions and balance-checks the output against the statement's own printed figures.

Rule of thumb: if you can log in and the period is within 365 days, export natively. If you are holding a PDF, convert the PDF.

Turn a Wise PDF into a verified CSV

Option 1: Wise's built-in statement download

If you have account access, this is the shortest route.

  1. Log in on the web, or open the app, and click your initials in the top corner.
  2. Choose Statements and reports, then Statements.
  3. Select the currencies and Jars you want covered, and the time period — up to 365 days at a time.
  4. Choose a format. The web offers PDF, XLSX, CSV, MT940, QIF and CAMT.053; the app offers PDF, CSV and XLSX. Confirm with your Wise password to download.

You can also start from a single currency or Jar: open it, use the three dots at the top right, and choose Statements and reports. If you need a stamped and signed document, there is an option for that, which requires address verification.

Where the built-in download stops

Wise's export is genuinely strong, and it still has edges:

Those cases all end in the same place: a PDF.

Option 2: Convert the Wise PDF statement to CSV

  1. Open the statement PDF. Ideally use one generated per currency balance rather than a merged multi-currency document.
  2. Upload it. The file is processed in memory and never written to disk. Supply a password at upload if the PDF is protected.
  3. The transactions are read into standard columns: Date, Narration, Reference, Value Date, Debit, Credit, Balance — with fees and conversions kept as their own rows.
  4. Check the verification label, then download the CSV.

Convert a Wise statement

Why Wise PDFs trip up generic converters

A Wise statement contains transaction types most bank statements do not, and that is where naive extraction fails.

Conversions are two rows, not one. When you move money from a EUR balance into a GBP balance, the statement records a debit against one balance and a credit against the other. A converter that treats the pair as a single transfer either drops one side or nets them into an amount that belongs to neither balance. Both halves have to survive, each in its own balance's ledger, or nothing reconciles.

Fees are separate line items. Wise itemises its charges rather than burying them in the exchange rate. Those fee rows are real debits and belong in the CSV. Converters that filter out anything that does not look like a merchant payment silently delete them, and the balance chain then breaks by exactly the fee amount — a small, plausible-looking difference that is easy to miss and painful to find later.

Each balance is its own statement. If you select several currencies or Jars at once, Wise returns a zip of separate statements rather than one combined ledger. Read as a flat list, the running balance jumps around as the document moves from one balance to the next. That is not corruption, it is the document design, and the extraction has to respect the section boundaries rather than assume a single continuous chain.

Prove the CSV matches the statement

This is the part most people skip, and the part that matters when someone else is going to read the file.

  1. The running balance chain. Within a single currency balance, the previous balance minus the debit plus the credit must equal the printed balance on each row. A dropped fee row or a missing half of a conversion breaks the chain at exactly the point it went wrong.
  2. The period's opening and closing balances. The statement states where the balance started and where it ended. Opening plus total credits minus total debits must equal closing, per currency.

Doing this by hand takes ten to fifteen minutes per statement, and multiplies by the number of currencies you hold. BankStatementKit runs both checks on every conversion and labels the result VERIFIED, DISCREPANCY or FAILED, with a discrepancy pinpointing the row where the numbers stop reconciling. There is more on the layout on the Wise statement converter page.

FAQ

Can I get more than 365 days of Wise history in one file?

Not in one export — Wise caps a statement at a 365-day period, so a multi-year request means several statements. Convert each one and concatenate the transaction rows in a spreadsheet. Verify each statement individually before you merge, because once they are stacked the balance chain no longer runs continuously.

Do currency conversions and Wise fees appear in the CSV?

They should, and that is the point. A conversion is a debit in one balance and a credit in another, and fees are itemised rows in their own right. If a converter drops either, the running balance stops agreeing with the statement — which is exactly what the verification check catches.

What about Jars?

Money moved into and out of a Jar appears in the statement as real transactions, and Wise lets you include specific Jars when you generate the statement. Whatever the PDF prints is what lands in the CSV, so if a Jar's movements are in the document they will be in your file.

Will the CSV import into Xero, QuickBooks or Excel?

The output is standard CSV with Date, Narration, Reference, Value Date, Debit, Credit and Balance columns. Those tools all accept a CSV transaction import with a column-mapping step. There is no direct QBO, OFX or CAMT export — if you need those, Wise's own web export offers them and is the better route.

Is uploading a bank statement safe?

BankStatementKit never stores your PDF — files are processed in memory and discarded. Conversion history is kept for 30 days and you can delete it at any time. Uploads are limited to 20MB or 50 pages, and scanned statements fall back to OCR automatically. Questions? Contact us.

The bottom line

If you can log in to Wise and your period fits inside 365 days, use Wise's own export — it is free, native, and it offers more formats than almost any bank. Convert the PDF when the PDF is the only artefact: official stamped statements, closed accounts, multi-year histories assembled from saved files, and statements other people send you. Either way, check per currency, and insist that the conversions and fee rows are still there.

Convert a Wise statement with the fees and conversions intact

Every conversion is balance-checked against the statement's own printed totals, and your first one is free with no account required.

Convert a Wise statement

← All guides