pain.001.001.03 — invalid IBAN
A pain.001 carrying a creditor IBAN whose two check digits fail the ISO 7064 mod-97 test. Everything else in the file is correct, so the validator reports exactly one error.
pain.001.001.03 — Invalid
A pain.001 carrying a creditor IBAN whose two check digits fail the ISO 7064 mod-97 test. Everything else in the file is correct, so the validator reports exactly one error.
What this file shows
A pain.001 carrying a creditor IBAN whose two check digits fail the ISO 7064 mod-97 test. Everything else in the file is correct, so the validator reports exactly one error.
| Transactions | 1 |
|---|---|
| Total | €1,000.00 |
| Scheme | SEPA |
| Date in the file | 2026-02-25 |
The defects it carries
- IBANInvalid IBAN for creditor Creancier IBAN Errone: FR0030003000209876543210093
Quoted verbatim from the validator, not paraphrased.
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
<?xml version="1.0" encoding="UTF-8"?>
<!--
ValidateFin sample file - SEPA Credit Transfer, pain.001.001.03.
Expected validation result: INVALID - exactly one error.
Deliberate defect: the creditor IBAN fails the ISO 7064 mod-97 checksum.
All parties and account numbers are fictitious.
Reference page: https://validatefin.com/en/resources/samples/sepa-pain001-invalid-iban
License: CC-BY-4.0
-->
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<CstmrCdtTrfInitn>
<GrpHdr>
<MsgId>MSG-ERR-IBAN-001</MsgId>
<CreDtTm>2026-02-23T10:00:00</CreDtTm>
<NbOfTxs>1</NbOfTxs>
<CtrlSum>500.00</CtrlSum>
<InitgPty>
<Nm>Societe Test IBAN Invalide</Nm>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>PMT-ERR-IBAN-001</PmtInfId>
<PmtMtd>TRF</PmtMtd>
<NbOfTxs>1</NbOfTxs>
<CtrlSum>500.00</CtrlSum>
<PmtTpInf>
<SvcLvl>
<Cd>SEPA</Cd>
</SvcLvl>
</PmtTpInf>
<ReqdExctnDt>2026-02-25</ReqdExctnDt>
<Dbtr>
<Nm>Societe Test IBAN Invalide</Nm>
</Dbtr>
<DbtrAcct>
<Id>
<!-- IBAN debiteur valide -->
<IBAN>FR7630006000011234567890189</IBAN>
</Id>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<BIC>BNPAFRPP</BIC>
</FinInstnId>
</DbtrAgt>
<CdtTrfTxInf>
<PmtId>
<EndToEndId>E2E-ERR-IBAN-001</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="EUR">500.00</InstdAmt>
</Amt>
<CdtrAgt>
<FinInstnId>
<BIC>SOGEFRPP</BIC>
</FinInstnId>
</CdtrAgt>
<Cdtr>
<Nm>Creancier IBAN Errone</Nm>
</Cdtr>
<CdtrAcct>
<Id>
<!-- IBAN invalide : checksum mod-97 incorrect (00 au lieu de 76) -->
<IBAN>FR0030003000209876543210093</IBAN>
</Id>
</CdtrAcct>
<RmtInf>
<Ustrd>Test IBAN invalide</Ustrd>
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>
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.
SEPA Credit Transfer (pain.001)
- pain.001.001.03 — valid credit transfer
- pain.001.001.09 — valid, hybrid address
- pain.001.001.03 — CtrlSum mismatch
- pain.001.001.03 — NbOfTxs mismatch
- pain.001.001.03 — unstructured address after 2026-11-15
- pain.001.001.11 — valid, fully structured address, executed after 2026-11-15
- pain.001.001.09 — valid, two payment batches with different execution dates
- pain.001.001.03 — nine-character BIC
- pain.001.001.03 — accent and ampersand outside the SEPA character set
- pain.001.001.03 — 250 transfers, high-volume payroll run
- pain.001.001.03 — unstructured address, executed before 2026-11-15 (warning only)