About Statement Converter

Every bank exports a different shape, and accounting apps want their own. Statement Converter reads the statement you have, lets you map its columns to date, payee, amount, and category once, and then writes the format your app imports. The mapping is remembered per bank, so the second statement from the same account takes seconds.

The statement is parsed in the browser. Account numbers and balances are never sent to a server.

How to use it

  1. Open the statement. A CSV or a text-based PDF both work.
  2. Tell it which column is the date, which is the amount, and how the bank marks money out versus money in.
  3. Check the parsed preview. Sign, date format, and split debit and credit columns are the usual fixes.
  4. Pick an output: CSV, QIF, OFX, or a preset for YNAB, Actual, or GnuCash.
  5. Download the file and import it in your app.

Common questions

Does it read scanned PDF statements?

Only statements where the text is real text, not an image. A scanned page has no characters to read. Export a CSV from your online banking instead when you can.

Which apps do the presets target?

YNAB, Actual Budget, and GnuCash have named presets. QIF and OFX cover Quicken, Moneydance, Banktivity, and most others. Plain CSV covers the rest.

Are my transactions uploaded?

No. Parsing and format conversion run in the page. There is no account and no server that sees the data.

Can it handle more than one account in a file?

Split the file by account first, or run it once per account. Each run produces one output file.

Why are some amounts positive that should be negative?

Banks disagree on the sign convention. Use the money in and money out column setting, or flip the sign in the preview, before export.