Supplier invoices
A weekly or monthly run of approved invoices to the same group of suppliers, with amounts and references that change each time.
Payments in SEPA Generator Pro
SEPA bulk payments to the people you pay every month.
Keep suppliers and contractors as saved beneficiaries, repeat last month's payment batch, check what changed, and export one SEPA Credit Transfer file for your bank's file upload.
14 days · No credit card · No account required.
Payment runs that come back every month.
Keying twenty or two hundred transfers into online banking is slow and error-prone. A bulk file lets your bank take them all at once; Pro helps you prepare that file the same way each time.
Contractors and freelancers
Regular payouts to contractors whose bank details you want to keep once, check, and not retype.
Operational payouts and salary files
Refunds, commissions, or the transfer file for a salary run whose net amounts come from your payroll provider.
From beneficiaries to the bank upload.
-
Add or import beneficiaries.
Enter them once or import them from CSV, XLS, or XLSX. IBAN and BIC are checked as they are saved.
-
Prepare a batch.
Choose the paying account and execution date, then add beneficiaries with amounts and payment references.
-
Review it.
Check the count and total. Errors block export; changed bank details and possible duplicates need your confirmation.
-
Repeat it next time.
“Repeat as new batch” copies an exported batch into a new draft. The original stays unchanged.
-
Export the XML.
Pro writes the pain.001 file and validates it against the bundled official schema.
-
Upload it yourself.
Use your bank's usual online banking or file-upload channel, and approve the batch there as you do today.
-
Keep the record.
The export history keeps the exact file and its details, with your own “uploaded to bank” note.
Bank-detail safeguards
A changed IBAN never slips through quietly.
Changed supplier bank details are a classic way for a payment to go to the wrong account. Pro cannot know whether a change is genuine, so it makes sure that you see it.
- An import never overwrites a saved beneficiary's IBAN or BIC; a row with different details is blocked for you to resolve.
- A repeated batch uses each beneficiary's current saved details, not the ones from the earlier file.
- Review lists beneficiaries whose bank details differ from the last file they were paid in and asks you to confirm them.
- Possible duplicate payments are flagged and must be confirmed.
- Once exported, a batch is locked; to change it, repeat it as a new batch.
Confirm any change of bank details with the supplier through a channel you trust before you export.
Community or Pro for bulk payments?
Both create SEPA Credit Transfer files. The difference is whether your payment data lives in a spreadsheet or in a workspace.
One-off files: Community, free
Convert a CSV or Excel sheet into pain.001 XML with IBAN, amount, and control-total checks. Free forever and open source. Read about the pain.001 generator, CSV to SEPA XML, or Excel to SEPA XML.
Recurring runs: Pro
Saved beneficiaries, repeatable batches, bank-detail safeguards, and export history, plus Direct Debit collections and XML tools in the same app.
What Pro leaves to your bank and payroll tools.
- Pro does not connect to your bank or transmit payments; you upload and approve each file.
- It does not execute or schedule transfers.
- It does not approve invoices, calculate payroll, or produce payslips.
- It does not reconcile bank statements.
- A schema-valid file is not a guarantee: acceptance can still depend on your bank, its upload channel, and the message version it requires.
Payments data stays in a local workspace on your computer, with optional encrypted backups. See data and backups in Pro. Collecting money from customers instead? See SEPA Direct Debit software.
Bulk payment questions
What is a SEPA bulk payment file?
It is one SEPA Credit Transfer XML file, in the pain.001 format, that contains many transfers from the same account. Most business online banking lets you upload such a file and approve the whole batch at once instead of keying each transfer.
Can I use SEPA Generator Pro to pay salaries?
Pro can prepare the transfer file for a salary run once you know the net amounts. It does not calculate pay, tax, or social contributions and does not produce payslips; that stays with your payroll software or provider.
What happens if a supplier changes their IBAN?
Update the beneficiary in Pro. The next batch you prepare or repeat uses the new details, and review asks you to confirm the change before the file can be exported. An import never overwrites a saved IBAN or BIC by itself; a mismatching row is blocked for you to look at.
Can I pay from more than one company account?
Yes. Each batch is paid from a debtor profile that you choose, and you can keep several profiles. Beneficiaries are shared, so the same supplier can be paid from any of them.
Which pain.001 version will Pro export?
pain.001.001.09 by default, with pain.001.001.03 and pain.001.001.02 available for banks that still require them. Your bank tells you which version and upload channel it expects.
Do I need Pro for a single payment file?
Not necessarily. If you only need to convert one CSV or Excel file into SEPA Credit Transfer XML now and then, the free Community Edition does that. Pro is for teams that pay the same people repeatedly and want saved beneficiaries, repeatable batches, and an export history.
Build next month's payment run once.
Download Pro, start the free trial when you are ready, and prepare a real batch from a copy of your supplier list.
14 days · No credit card · No account required.
The 14-day free trial includes every Pro feature, with no credit card and no account. Nothing is charged automatically when the trial ends. A license is required to keep using Pro after the trial: €119/year, an annual subscription with 3 device activations. Your local data is never deleted. See Pro pricing.