ocrsnip
No uploads · runs in this tab
ocrsnip
No uploads · runs in this tab
Your bank gave you a file built for accounting software you may not even own, and double-clicking it offers to install one. Drop it here and take a real .xlsx instead — amounts as numbers that add up, dates that cannot flip. Read on your computer, never uploaded.
| Date | Description | Amount |
|---|
Date, description, amount, type, cheque number and the transaction id the file carried. Amounts land as numbers, so a column of them sums; dates are written YYYY-MM-DD, which no spreadsheet can read the wrong way round. The workbook is built here in the tab — the spreadsheet library is fetched only when you press the button.
Both buttons are here. These are the four reasons people press the first one.
A CSV has no types: every figure arrives as text, and a column of text refuses to sum until someone converts it. In the workbook the amounts are already numbers, so the total appears the moment you select the column.
Opening a CSV in Excel runs an import guess, and 03/04 becomes 3 April or 4 March depending on the machine it is opened on. Dates here are written YYYY-MM-DD and stay that text in the cell — one reading, on every computer.
A transaction id like 0041703 is the one thing that ties a row back to the file it came from, and a CSV import is the classic way to lose it: Excel reads it as a number and drops the zeros. In the workbook it stays the text it is.
The old answer was: take the CSV, open it, save as .xlsx. That works, and it is still here as the second button. This one skips it.
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.
The file keeps two description fields and a sheet has one column. When both are present and differ, they are joined with an em dash, so nothing the bank wrote is quietly dropped.
Something else? Write to support@ocrsnip.com.
Yes, with no row limit and no account.
It is a bank statement written for accounting software rather than for a person: the same OFX document QuickBooks and Quicken import. Windows offers to install QuickBooks when you double-click one, because that is the program that registered the extension. Nothing is wrong with your file — it simply has no viewer.
Yes. It is an ordinary .xlsx with a single sheet called Transactions, which both open directly.
QuickBooks Online takes .csv, .qbo, .qfx and .ofx for bank feeds, not .xlsx — so for that, use the .csv button here, or feed it the original file. The workbook is for reading, checking and keeping, which is a different job.
No. It is read in this tab and the workbook is written here too. The only thing fetched over the network is the spreadsheet library, from this site, and only when you ask for .xlsx.