Check a conversion you already have
You converted a bank statement somewhere else. It looks fine. That is the problem: a dropped row looks exactly like a statement that had one fewer transaction. Bring the original PDF and the file your converter gave you, and this page runs the one sum that settles it.
Opening balance + every transaction must equal the closing balance. Both numbers are printed on your statement, so the arithmetic either resolves to the cent or it does not. If it does not, you get the difference and the list of rows that are on the statement but missing from your file.
It does not matter which tool made the file
DocuClipper, MoneyThumb, a bank's own export, a spreadsheet you typed by hand: the check is arithmetic against your own statement. Your file is never compared with our output, so a difference of opinion between two converters proves nothing here. CSV, semicolon-separated and tab-separated files are all read, with either a single signed amount column or a debit and credit pair.
1. The original statement, as a PDF
No file chosen
2. The file your converter produced
No file chosen
What this page does not do
- It does not correct your file. It tells you whether it is sound and where it is not. Fixing a wrong file is a decision about your own books.
- It cannot catch a right amount on the wrong date beyond the date checks it runs. Arithmetic sees arithmetic. Where the check cannot run, it says so, and that is labelled as NOT FOUND. It is never a pass.
- Two errors that cancel out are caught only when your file carries a balance column. If it does, every row is walked against the one above it and the first row that stops following is named, so a fifty moved from one line to another shows up even though the total is unchanged. Without that column the totals are all there is to check, and the page says which of the two ran.
- It does not need an account, and it does not cost anything. This check is free, on any file, for as long as the site exists.