ocrsnip
No uploads · runs in this tab
ocrsnip
No uploads · runs in this tab
Your bank gave you a file built for accounting software, and you wanted a spreadsheet. Drop the .qbo, .ofx or .qfx and take the transactions as CSV — read here, on your computer, and never uploaded.
| Date | Description | Amount |
|---|
Date, description, amount, type, cheque number and the transaction id the file carried. Dates are written YYYY-MM-DD, which no spreadsheet can read the wrong way round.
Three letters, two dialects, one document.
Tags that are never closed and a header of key:value lines at the top. It is not valid XML, which is why an XML parser fails on exactly the files banks hand out most often. This page reads it as the text it is.
The same tags, written as proper XML. Both dialects come out as the same rows here.
OFX with a couple of extra tags for QuickBooks and Quicken. Nothing about the transactions differs, so both read exactly the same.
Each transaction carries an id its issuer used to avoid duplicates on import. It is kept in the CSV, because it is the only thing that lets you match a row back to the original file.
Something else? Write to support@ocrsnip.com.
Yes, with no row limit and no account.
Because a spreadsheet has one description column and the file has two fields. When both are present and differ, they are joined with an em dash so nothing the bank wrote is silently dropped.
Open the CSV in Excel or Numbers and save it as .xlsx — that is one step, and it saves every visitor here from downloading a spreadsheet library they may not need. If you want a proper workbook straight away, the bank statement converter builds one.
No. It is read in this tab and the CSV is written here too. The network panel stays empty while you convert.