Online SEPA XML validator — Free test
Test and validate a SEPA XML file (pain.001 / pain.008): checks on NbOfTxs, CtrlSum, IBAN, BIC and ISO 20022 consistency. camt.053 examples included.
Upload an XML file
Why use a SEPA XML validator?
Our tool checks your XML against SEPA and ISO 20022 rules for the pain.001 (credit transfers) and pain.008 (direct debits) formats.
Checks performed
- Message type detection: pain.001 / pain.008 / camt.053
- Comparison of declared NbOfTxs vs counted transactions
- Comparison of declared CtrlSum vs sum of amounts
- IBAN and BIC format check (FR length, SWIFT structure)
For strict XSD validation, contact us — we can load local schemas and enable full checking.
ISO 20022 XML file examples (pain.001, pain.008, camt.053)
Download compliant ISO 20022 XML file examples to understand the expected structure or to test the validator above.
See also: detailed pain.001 vs pain.008 comparison and FAQ.
- pain.001 example (SEPA credit transfer) — SEPA credit transfer order, 2 transactions, valid IBAN/BIC.
- pain.008 example (SEPA direct debit) — SEPA CORE direct debit order, with mandate and references.
- camt.053 example (account statement) — ISO 20022 bank account statement, with opening/closing balances and entries.
What is a camt.053 file?
camt.053 (Bank-to-Customer Statement) is the ISO 20022 message banks use to send an electronic account statement: opening (OPBD) and closing (CLBD) balances, and entry details (Ntry) with amount, direction (CdtDbtInd), booking date and transaction references.
Unlike pain.001 and pain.008, which are payment orders sent by the company to its bank, camt.053 flows the other way: the bank sends it to its customer for bank reconciliation (often via EBICS or an online portal). Our validator recognizes camt.053 and clearly identifies it; detailed validation of its content (balances, entries) is not yet available — contact us if you need this.
Ready to simplify your SEPA payments?
+300 companies use EasyBankFlow