SEPA XML for Transfers and Direct Debits | Nuxbe [ Skip to content ](#main-content) [ Nuxbe ](https://nuxbe.com/en) [ Home ](https://nuxbe.com/en) [ Flexible ](https://nuxbe.com/en/features/flexible) [ Open Source ](https://nuxbe.com/en/features/open-source) [ Industries ](https://nuxbe.com/en/industries) [ Modules ](https://nuxbe.com/en/modules) [ Premium ](https://nuxbe.com/en/premium) [ FAQ ](https://nuxbe.com/en/faq) [ Partners ](https://nuxbe.com/en/partners) [ Contact ](https://nuxbe.com/en/contact) EN DE [ Home ](https://nuxbe.com/en) [ Flexible ](https://nuxbe.com/en/features/flexible) [ Open Source ](https://nuxbe.com/en/features/open-source) [ Industries ](https://nuxbe.com/en/industries) [ Modules ](https://nuxbe.com/en/modules) [ Premium ](https://nuxbe.com/en/premium) [ FAQ ](https://nuxbe.com/en/faq) [ Partners ](https://nuxbe.com/en/partners) [ Contact ](https://nuxbe.com/en/contact) Payment Automation SEPA XML Export =============== Turn your payment runs into bank-ready SEPA files in a single step [ Contact ](https://nuxbe.com/en/contact) Payments Ready for the Bank --------------------------- The SEPA package generates standards-compliant XML files directly from your FluxERP payment runs – pain.001.003.03 for credit transfers and pain.008.003.02 for direct debits. Instead of typing transfers into your banking portal, export one file and upload it. Every payment run becomes a clean, auditable batch. ### Credit Transfers Generate pain.001 credit transfer files from outgoing payment runs. Supplier and amount data is pulled straight from the run, ready for upload to any SEPA-capable bank. ### Direct Debits Collect from customers with pain.008 direct debit files. Mandate and IBAN data is taken from the contact, so each batch is complete and correctly formatted. ### Bank-Ready Files Exported XML follows the SEPA pain standard, so files upload to your bank without conversion. Each run is reproducible and stays attached to its payment records. In practiceWhen the file is the right route -------------------------------- ### Supplier invoices in one go Due purchase invoices go into a payment run, the run becomes a file, the file goes into online banking. Instead of entering twenty transfers by hand you review one list and approve once. ### Collecting fees and subscriptions For direct debits Nuxbe splits the batches the way the scheme requires: one-off collections apart from recurring ones, core mandates apart from B2B mandates. Each batch gets its own execution date. ### When a banking interface is off the table Some companies will not hand account access to a third party, others bank with an institution that offers no usable interface. The file route still works there, because it assumes nothing beyond online banking that accepts SEPA XML. SetupNothing to configure, a few things to maintain ---------------------------------------------- The package ships neither a config file nor environment variables. It works purely from data already in the system: the client's bank details, the contacts' bank details and the positions of the payment run. Transfers need an IBAN on both sides. Direct debits add the signed mandate on the contact and the creditor identifier on the client, both mandatory parts of the scheme rather than an invention of the package. The export runs off the same button that otherwise executes a payment run. Nuxbe builds the file, offers it for download and moves the run to pending until the bank confirms execution. ### Requirements - Bank details with an IBAN on the client - An IBAN on the contact behind every position in the run - A signed mandate per customer for direct debits - A creditor identifier on the client - Online banking that accepts SEPA XML LimitsWhat the export deliberately does not do ---------------------------------------- What you get is a file, not a payment. Nuxbe talks to no bank here, and whether the file arrives and executes shows up in your online banking, not in the ERP. If you need that return channel, take the finAPI connection. Positions without an IBAN, and direct debits without a signed mandate, drop out of the batch silently. That is intentional, because one incomplete line would fail the whole file at the bank, but it does mean the total of the run deserves a look before you upload. The formats produced are pain.001.003.03 and pain.008.003.02 from the German DFÜ agreement. Instant payments and payments outside the SEPA area are not part of it. Free text is reduced to the permitted SEPA character set, which turns an umlaut into its two-letter form. All packages included --------------------- All premium packages are included in the Nuxbe license. Contact us for more information. [ Contact ](https://nuxbe.com/en/contact) Related pages --------------- [### Channel Manager Sell on marketplaces and price comparison sites from one catalogue, one stock figure and one order book. ](https://nuxbe.com/en/premium/channel-manager) [### Shopware 6 Connect your Shopware 6 store with Nuxbe and keep products, orders and customers in sync ](https://nuxbe.com/en/premium/shopware) [### WhatsApp Let customers reach you on WhatsApp and reply from the Nuxbe chat inbox ](https://nuxbe.com/en/premium/whatsapp) [### Office 365 Synchronization with Microsoft Office 365 for calendars, contacts, and more ](https://nuxbe.com/en/premium/office365) Nuxbe Open Source ERP system for modern businesses. ### Links [ GitHub ](https://github.com/Team-Nifty-GmbH/flux-core) [ Contact ](https://nuxbe.com/en/contact) ### Mobile App [ App Store ](https://apps.apple.com/de/app/nuxbe/id6754884170) [ Google Play ](https://play.google.com/store/apps/details?id=com.teamnifty.nuxbe) ### Legal [ Imprint ](https://nuxbe.com/en/imprint) [ Privacy Policy ](https://nuxbe.com/en/privacy) [ Terms and Conditions ](https://nuxbe.com/en/terms) [ Cookie Policy ](https://nuxbe.com/en/cookie-policy) © 2026 Nuxbe. All rights reserved.