pain.001.001.03 — valid credit transfer
A valid SEPA credit transfer in pain.001.001.03: three transfers totalling 1 580.00 EUR, matching control totals, IBANs that pass the mod-97 check and names inside the basic SEPA character set.
pain.001.001.03 — Valid
A valid SEPA credit transfer in pain.001.001.03: three transfers totalling 1 580.00 EUR, matching control totals, IBANs that pass the mod-97 check and names inside the basic SEPA character set.
What this file shows
A valid SEPA credit transfer in pain.001.001.03: three transfers totalling 1 580.00 EUR, matching control totals, IBANs that pass the mod-97 check and names inside the basic SEPA character set.
| Transactions | 3 |
|---|---|
| Total | €1,580.00 |
| Scheme | SEPA |
| Date in the file | 2026-02-25 |
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: VALID — 3 transfers, 1 580.00 EUR.
No postal address is supplied, which is allowed: the EPC structured-address rule
only applies to an address that is present.
Names and remittance text stay inside the basic SEPA character set: no accented
letters, no ampersand, no em dash. Only a-z A-Z 0-9 / - ? : ( ) . , ' + space.
All parties and account numbers are fictitious.
Reference page: https://validatefin.com/en/resources/samples/sepa-pain001-v03-valid
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-TEST-001-20260223</MsgId>
<CreDtTm>2026-02-23T10:00:00</CreDtTm>
<NbOfTxs>3</NbOfTxs>
<CtrlSum>1580.00</CtrlSum>
<InitgPty>
<Nm>ACME Corporation SA</Nm>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>PMT-001-20260223</PmtInfId>
<PmtMtd>TRF</PmtMtd>
<NbOfTxs>3</NbOfTxs>
<CtrlSum>1580.00</CtrlSum>
<PmtTpInf>
<SvcLvl>
<Cd>SEPA</Cd>
</SvcLvl>
</PmtTpInf>
<ReqdExctnDt>2026-02-25</ReqdExctnDt>
<Dbtr>
<Nm>ACME Corporation SA</Nm>
</Dbtr>
<DbtrAcct>
<Id>
<IBAN>FR7630006000011234567890189</IBAN>
</Id>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<BIC>BNPAFRPP</BIC>
</FinInstnId>
</DbtrAgt>
<CdtTrfTxInf>
<PmtId>
<EndToEndId>E2E-001-FOURNISSEUR-A</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="EUR">1000.00</InstdAmt>
</Amt>
<CdtrAgt>
<FinInstnId>
<BIC>SOGEFRPP</BIC>
</FinInstnId>
</CdtrAgt>
<Cdtr>
<Nm>Fournisseur Alpha SARL</Nm>
</Cdtr>
<CdtrAcct>
<Id>
<IBAN>FR0430003000209876543210093</IBAN>
</Id>
</CdtrAcct>
<RmtInf>
<Ustrd>Facture FA-2026-0142 du 01/02/2026</Ustrd>
</RmtInf>
</CdtTrfTxInf>
<CdtTrfTxInf>
<PmtId>
<EndToEndId>E2E-002-PRESTATAIRE-B</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="EUR">480.00</InstdAmt>
</Amt>
<CdtrAgt>
<FinInstnId>
<BIC>CMCIFRPP</BIC>
</FinInstnId>
</CdtrAgt>
<Cdtr>
<Nm>Prestataire Beta SAS</Nm>
</Cdtr>
<CdtrAcct>
<Id>
<IBAN>FR3314508600001234567890150</IBAN>
</Id>
</CdtrAcct>
<RmtInf>
<Ustrd>Facture PB-2026-0089 - Honoraires janvier 2026</Ustrd>
</RmtInf>
</CdtTrfTxInf>
<CdtTrfTxInf>
<PmtId>
<EndToEndId>E2E-003-LOYER-BUREAU</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="EUR">100.00</InstdAmt>
</Amt>
<CdtrAgt>
<FinInstnId>
<BIC>AGRIFRPP</BIC>
</FinInstnId>
</CdtrAgt>
<Cdtr>
<Nm>SCI Immobiliere du Centre</Nm>
</Cdtr>
<CdtrAcct>
<Id>
<IBAN>FR7117206005509876543210014</IBAN>
</Id>
</CdtrAcct>
<RmtInf>
<Ustrd>Loyer bureau - mars 2026</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.09 — valid, hybrid address
- pain.001.001.03 — CtrlSum mismatch
- pain.001.001.03 — invalid IBAN
- 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)