ValidateFin

MT940 — closing balance does not reconcile

A statement whose closing balance does not follow from opening ± movements. This is deliberately a warning, not a blocking error: the file is still readable and a human must decide whether the bank or the export is at fault.

SWIFT MT940 — Valid

A statement whose closing balance does not follow from opening ± movements. This is deliberately a warning, not a blocking error: the file is still readable and a human must decide whether the bank or the export is at fault.

SWIFT MT940 statement SWIFT MT940 SWIFT MT940Expected result: Valid — 1 warnings

What this file shows

A statement whose closing balance does not follow from opening ± movements. This is deliberately a warning, not a blocking error: the file is still readable and a human must decide whether the bank or the export is at fault.

The defects it carries

  • BalanceStatement 1/1: opening ± turnover (1100) ≠ closing balance (9999.99).

Quoted verbatim from the validator, not paraphrased.

Last verified: License: CC-BY-4.0
Download the file Open the matching validator

Every party, IBAN and amount below is fictitious. The IBANs are structurally valid — they pass the mod-97 check — but they belong to no real account.

File content

:20:BROKEN
:25:DE44500105175407324931
:28C:1/1
:60F:C240601EUR1000,00
:61:2406020602C100,00NTRFNONREF
:86:Test
:62F:C240602EUR9999,99
-

How we know these results hold

Every file in this library is run through the site's own validator on each build. The expected result stated above is asserted by an automated test — if a file stopped matching what this page claims, the build would fail. Two inherited fixtures were repaired this way before publication: three IBANs failed the mod-97 check and several names used characters outside the basic SEPA character set.

SWIFT MT940 statement

All sample fileshttps://validatefin.com/samples/mt940/07-broken-balance.txt