Which ISO 20022 SEPA schema version should your batch use?
Choose pain.001.001.03 (credit transfer) or pain.008.001.02 (direct debit) for universal compatibility across legacy European bank portals, or select pain.001.001.09 and pain.008.001.08 when your bank requires the 2019 ISO 20022 rulebooks where BIC is optional.
Standardized XML messaging removes manual bank-portal re-entry for payroll and supplier runs. Under EU Regulation No 260/2012 on SEPA Requirements, euro credit transfers and direct debits across the Single Euro Payments Area must use ISO 20022 XML message formats with IBAN-only addressing.
| Schema version | Payment type | BIC requirement | Typical bank support |
|---|---|---|---|
pain.001.001.03 |
Credit transfer | Optional in most portals | Classic EU bank default |
pain.001.001.09 |
Credit transfer | Optional (2019 schema) | Modern DK, NL, AT, FR portals |
pain.008.001.02 |
Direct debit | Optional in most portals | Classic CORE and B2B |
pain.008.001.08 |
Direct debit | Optional (2019 schema) | Modern 2019 direct debit portals |
Comparing pain.001.001.03 and .09 credit transfers
Credit transfers instruct your bank to push EUR funds to employees or vendors. Message IDs and End-to-End IDs allow up to 35 characters, while unstructured Remittance reference notes allow up to 140 characters. For single-invoice payment slips rather than batch XML files, you can create SEPA credit transfer QR codes for individual invoices.
Direct debit pain.008.001.02 versus .08 and optional BIC rules
Direct debits collect funds from customers under a signed mandate using either CORE (consumer and business) or B2B (business-only, no refund right) schemes. Each row requires a Mandate ID and Mandate signed date alongside the creditor’s SEPA Creditor ID.
Converting CSV or Excel payment batches into bank-ready XML
Drop a .csv or .xlsx spreadsheet into Import rows from CSV or Excel (.xlsx) or click Download sample CSV to match the expected column headers. While the editor renders the first 60 rows for interactive review, all imported rows are written into the final .xml download.
As described by European Central Bank SEPA Payment Standards, SEPA harmonizes euro-denominated clearing across participating European countries under shared technical rulebooks. Computing GrpHdr and PmtInf control sums in integer cents prevents floating-point penny mismatches that trigger immediate bank rejections.
Splitting mixed FRST, RCUR, OOFF, and FNAL sequence types
European clearing houses reject pain.008 files that combine FRST, RCUR, OOFF, and FNAL transactions inside one <PmtInf> block. This generator automatically groups rows by sequence type into separate <PmtInf> blocks, each carrying its own exact transaction count and control sum. Businesses billing in Switzerland can also use a Swiss QR-bill generator for CHF and EUR payment slips.
Transliterating diacritics and recalculating Mod-97 Creditor IDs
Enabling Transliterate accents and umlauts to strict SEPA character set converts characters like ä, ö, ü, and ß into ae, oe, ue, and ss. For direct debits, Recalculate Mod-97 check digits computes valid EPC262-08 Creditor Identifier check digits while excluding the 3-character business code in positions 5 through 7.
Validating existing SEPA XML files and exporting to Excel
Switch the Mode toggle to Validate & view SEPA XML to run the built-in SEPA XML validator on any existing pain.001 or pain.008 file up to 25 MB. The inspector verifies declared header and batch control sums against summed transaction amounts, checks every IBAN checksum, and flags missing direct-debit mandate fields before upload.
Tip: After generating a batch, click Inspect and verify generated XML on the result card to audit every PmtInf block and export a spreadsheet copy for finance sign-off.
Exporting validated rows with Download CSV or Download Excel (.xlsx) gives controllers a readable audit trail without opening raw XML in a text editor. Recent European rules under EU Regulation 2024/886 on Instant Credit Transfers reinforce standardized ISO 20022 validation and payee verification across payment service providers. Once your bank settles the batch and returns an end-of-day statement, convert it with CAMT.053 to CSV & Excel for reconciliation.
Why generate SEPA XML files locally in your browser?
Every XML build, IBAN check, and spreadsheet import runs 100% locally in your browser with 0 bytes uploaded to external servers. Using a private SEPA XML generator without server upload keeps payroll salaries, vendor IBANs, and customer direct-debit mandates strictly on your own device.
Protecting payroll IBANs and direct debit mandates offline
Because no external server processes your payment file, you can prepare confidential treasury batches even on restricted corporate networks. You can also verify 8- and 11-character ISO 9362 BIC codes locally before uploading batches when older bank portals require counterparty BICs.
All XML serialization runs inside a dedicated Web Worker, keeping the interface responsive even when importing spreadsheets with hundreds of supplier or employee rows across multiple European countries and SEPA clearing zones.
Once you download the .xml file and close the tab, no payment data remains cached on any remote server, and you can immediately inspect the output structure before uploading it to your corporate banking portal. Using 0 KB of external cloud storage protects sensitive European payroll and vendor batches during routine treasury operations and monthly accounting closes.
Bank-specific dialect checks and treasury compliance framing
This tool builds and validates standard ISO 20022 SEPA XML structures for operational convenience and does not constitute certified banking, legal, or treasury compliance advice. Individual banks occasionally enforce proprietary country extensions or cut-off rules, so test small batches in your bank’s portal and consult your treasury advisor or bank relationship manager before live payroll or supplier runs.