A SEPA XML file for your bank
One pain.001.001.09 XML file with all your transfers, validated against the ISO schema. Upload it in your business online banking and approve the batch there. The skill never moves money itself.
It's the current SEPA standard. Business banks that import SEPA XML, in Austria and Germany for example, accept it, so you don't have to pick a bank-specific variant. N26 and Wise have no XML import. For them, the skill tells you so instead of building a CSV.
A preview of every payment
The skill first shows a preview: names, amounts, references, and the total. Umlauts become ae, oe, and ue, as SEPA requires. The skill writes the file only after you confirm.
What the SEPA file needs
Your company name and the IBAN the money leaves from. For each payment:
- The supplier and their IBAN
- The amount
- An invoice number as free text, up to 140 characters, or a structured payment reference, up to 35
How the XML is built and checked
A Node script in the skill builds the file. It sets the message ID and the control sum, counts the transactions, and checks every IBAN. If the script can't run, the skill builds no file. It never writes the XML itself.
Unpaid invoices and IBANs from Billpal
Ask for everything due by a date. The skill lists your unpaid incoming invoices from Billpal and fills in supplier IBANs. It subtracts linked credit notes. Invoices paid by direct debit, card, or PayPal are left out and listed, so you can add one back.
A supplier's IBAN is used without asking only if you entered or imported it yourself, or if it was on an earlier invoice from that supplier. After you confirm the transfers went out, the skill can mark those invoices as paid in Billpal.