πŸ”€ MT940 Diff

Your bank re-sent the statement. Compare the two files and see precisely what moved β€” which entries appeared, which disappeared, and whether the balances still agree.

Your statement stays on your device. This page reads the files with JavaScript in your browser. Nothing is uploaded, and it keeps working with your network disconnected.
πŸ“„
First file the original
Drop it here or click to browse
πŸ“„
Second file the one to check
Drop it here or click to browse

β€œWe have re-sent the statement”

Your bank sends a corrected file and says nothing more useful than that. Somewhere in a few hundred entries, something changed. Opening the two files side by side in a text editor does not help: the bank re-issues its own references on a re-send, so a plain text diff lights up on every single line.

This compares the two files as statements, not as text. It tells you which transactions are in one and not the other, and how the balances moved.

Nothing is uploaded. This page is JavaScript running on your machine. Load it, disconnect from the internet, and it still works β€” which is the only honest way to hand a tool a live bank statement.

How transactions are matched

Entries are matched on value date, signed amount (in whole cents), counterparty IBAN and name, end-to-end reference, and the purpose text. The bank's own reference is deliberately excluded β€” it changes on a re-send, and matching on it would report that every entry in the file is both added and removed.

Repeats are counted, not collapsed

The comparison counts occurrences rather than treating each file as a set of unique entries. If a €5 fee appears twice in the first file and three times in the second, that is reported as exactly one addition β€” not three, and not zero. Getting this wrong is the standard way a diff tool quietly misleads you about a statement full of identical small charges.

Balances are compared separately

Transactions and balances can disagree, and when they do it is worth knowing. Each account's first opening balance and last closing balance are compared across the two files, however many pages the statement arrived in. Two files with identical transactions but different closing balances is a meaningful and alarming result, and it is shown as one.

When this is the right tool

  • A bank re-sent a statement and you need to know what actually changed before re-importing
  • Two exports of overlapping date ranges and you want the difference, not the union
  • Before and after a correction β€” confirm the bank changed only what it said it changed
  • Two systems disagree about what a day contained, and each produced a statement file

How to compare two files

1

Add the original

Drop the first file into the left box β€” usually the copy you already imported.

2

Add the new one

Drop the re-sent or corrected file into the right box.

3

Compare

You get a verdict, a side-by-side summary, the balance comparison, and the two lists of entries that appear in only one file.

Frequently Asked Questions

No. Both files are read and compared in your browser. Neither is sent anywhere.
They contain the same transactions and the same balances. The size difference will be line endings, spacing, or the bank’s own references β€” none of which change what the statement says about your money.
Because a re-sent statement has fresh bank references on every line, so a text diff marks every line as changed. Comparing the parsed statements ignores that noise and surfaces the entries that genuinely differ.
You can, but read the result carefully. MT942 is an intraday report with a floor limit, so it deliberately omits entries below that limit β€” the differences it reports are the format working as designed, not missing transactions.
Two at a time here. To combine many files into one and have the result re-checked, use the MT940 Merger.