SimpliServDocs

Create SEPA payment runs

Bundle SEPA direct debits for customer invoices and SEPA credit transfers for purchase invoices, generate the XML, download it and record it as submitted

→ Open payment runs in SimpliServ · Open SEPA settings

A payment run bundles many payments into one SEPA file for your online banking. SimpliServ knows two directions, each with its own tab:

  • Direct debits: collect due customer invoices with a SEPA mandate.
  • Credit transfers: pay approved purchase invoices and other liabilities by credit transfer (pain.001).

SimpliServ generates the file; you upload it to your bank portal and the bank executes it.

The list needs payment_runs.view. Creating, submitting, cancelling and deleting runs requires payment_runs.create, generating and downloading the SEPA file payment_runs.export.

Direct debit payment run

Prerequisites: the SEPA creditor data (creditor ID, name, IBAN, BIC) are stored in the SEPA settings, and the customers have an active SEPA mandate with IBAN.

Prepare the run

Click New payment run → Direct debit, choose the Collection date and click Prepare payment run. SimpliServ collects the matching open invoices.

Read the hints

Invoices without a mandate or IBAN are skipped; the count appears as a warning. If first direct debits fall short of the mandate's pre-notification period, SimpliServ warns you as well. For business direct debits (B2B), SimpliServ creates a separate second run, which you open via Open B2B run.

Generate and download the SEPA file

Check the items on the detail page (debtor, mandate reference, sequence type, amount, invoice) and click Generate SEPA file. If creditor data is missing, a hint leads straight to the SEPA settings. Then download the file with Download XML and submit it in your online banking.

Mark as submitted

As soon as the bank has the file, click Mark as submitted and confirm. Only then are the related invoices marked as paid.

Mark as submitted is not a bank import. It only confirms in SimpliServ that you handed the file to the bank. If a direct debit comes back, the item list shows it in the Return column.

A direct debit run in status draft or generated can be deleted. After submission it stays as a record.

Credit transfer payment run

Open the payment proposal

Click New payment run → Credit transfer (payment proposal), or select invoices in the purchase invoice list and choose Payment proposal.

Set the criteria

Choose Execution date, Due until, the Debit account and optionally individual suppliers. Take cash discounts pays the reduced amount while a cash discount period is running, Include VAT payments adds a VAT liability to the tax office.

Check the proposal

The Payable tab shows recipient, document, due date, open amount, cash discount, payment amount, IBAN, remittance information and hints such as a different IBAN or a credit note that can be offset. Under Not payable you find blocked invoices with the reason, for example missing or invalid IBAN, payment block, suspected duplicate, non-euro invoice or collection by direct debit.

Create the run

Select the rows and choose Create payment run. In the dialog you set when payments are recorded (When the bank line arrives or When submitted), whether the bank should make a Batch booking, and you can add saved payees without an invoice. If an IBAN differs from the supplier data, you must confirm it first.

Generate, download, submit

On the detail page Generate SEPA file, then Download XML, upload it in online banking and finish with Mark as submitted.

As long as the run has not been submitted, you remove individual items via the row menu or cancel the whole run with Cancel run; the invoices then reappear in the payment proposal. If the bank rejects a submitted transfer, mark the item as Not executed; the invoice can then be paid again.

If four-eyes approval is active, generating the file first requests approval from a second person.

Payment run status

StatusMeaning
DraftItems prepared, no file generated yet.
GeneratedSEPA XML was created and can be downloaded.
DownloadedFile was downloaded from SimpliServ.
CollectedDirect debit run marked as submitted; invoices count as paid.
SubmittedCredit transfer run marked as submitted.
CompletedCredit transfer run completed.
FailedGeneration or processing could not be completed.

Payees and settings

In the Payees tab you create templates for recurring free payments, for example social security contributions: name, IBAN, BIC and a reference pattern, optionally as a structured creditor reference. Via Settings you set the default payment term, the confirmation requirement for a changed IBAN, the tax office's bank details and the tolerances for matching against purchase order and goods receipt.

Details and follow-up checks

The detail page shows run data (number, date, items, total amount) and technical details such as message ID, pain format, direct debit type and the times of generation, download and submission. After submission, check:

  • Invoice status and open amount
  • Number of items and total amount against the bank log
  • Message ID and download time

How is this guide?

On this page