Free desktop app · Community Edition

Generate SEPA XML from CSV and Excel files.

SEPA Generator converts CSV, XLS, and XLSX payment files into validated pain.001.001.02 SEPA Credit Transfer XML. It checks your input data before generation and reports clear errors when something needs to be corrected.

Runs locally on your computer. Your payment files are not uploaded to a server. Read the privacy note.

Open source · Apache-2.0 license · Windows ZIP and universal JAR available

SEPA Generator desktop app main screen SEPA Generator desktop app main screen
Format
pain.001.001.02
Input files
CSV · XLS · XLSX
Processing
Local desktop app
Validation
IBAN · SIRET · Amounts · Dates
License
Apache-2.0
Distribution
Windows ZIP · Universal JAR

A focused desktop tool for SEPA payment file generation.

Prepare SEPA Credit Transfer XML files from spreadsheet exports with a simple local workflow.

CSV and Excel input

Import payment data from CSV, XLS, or XLSX files exported from accounting, payroll, or internal business tools.

Local desktop app

Generation happens on your computer. Your payment files stay local and are never sent to an online service.

Built-in validation

The app checks required payment data before generating the XML file, helping you catch common input errors early.

Windows and Java versions

Use the Windows portable package or the universal JAR version, depending on your environment.

See the app in action.

A simple desktop interface for selecting your input file, generating the SEPA XML, editing settings, and reading validation errors.

SEPA Generator settings screen SEPA Generator settings screen
Configurable settings
SEPA Generator showing a clear validation error message SEPA Generator showing a clear validation error message
Clear validation errors

Designed to generate valid pain.001.001.02 SEPA XML.

SEPA Generator is not just a raw XML exporter. It validates the input file, debtor configuration, execution date, transaction fields, IBAN checksums, payment amounts, identifiers, and remittance information before generating the XML file.

What is checked

Input and output files, supported extensions, debtor information, debtor IBAN and BIC, initiating party SIRET, creditor name and IBAN, transaction amount, execution date, end-to-end identifier, and remittance information are checked before generation.

Bank acceptance

Generated files follow the pain.001.001.02 SEPA Credit Transfer format. Banks may still apply additional acceptance rules, supported-version restrictions, or custom checks, so your first production file should be tested with your banking portal or bank support team.

Download the Community Edition.

The free Community Edition is distributed through GitHub Releases for transparency. You can download the Windows portable package, the universal JAR, or inspect the source code.

Frequently asked questions

Is SEPA Generator free?

Yes. The Community Edition is free and open source under the Apache-2.0 license.

Does it upload my payment file?

No. SEPA Generator is a desktop app that runs locally on your computer. Your payment files are not uploaded to any server.

Will my bank accept the generated file?

SEPA Generator is designed to produce valid pain.001.001.02 SEPA Credit Transfer XML. However, banks can apply their own acceptance rules or version restrictions, so you should test your first generated file with your bank before production use.

Can it support other PAIN versions?

The Community Edition currently focuses on pain.001.001.02. Other PAIN versions, bank-specific profiles, or professional workflows may be considered depending on user needs.

Professional use cases

Need a custom SEPA workflow?

The Community Edition focuses on local CSV and Excel to pain.001.001.02 generation. For professional workflows, future work may include bank-specific validation profiles, custom ERP export mapping, other PAIN versions such as pain.001.001.03 or pain.001.001.09, structured address preparation, batch generation, and clearer diagnostics for rejected files.

If your current SEPA tool is missing a specific feature, or if your bank rejects files that look valid, you can contact me to discuss the workflow.

Professional workflow topics

  • Bank-specific validation
  • ERP export mapping
  • Other PAIN versions
  • Structured addresses
  • Batch generation
  • Rejected-file diagnostics

Need help with SEPA XML generation?

Get in touch if you need another PAIN version, bank-specific validation, custom input mapping, batch workflows, or support for a professional SEPA payment process.