SimpliServDocs

Understanding SEPA payment runs

Bundle direct debits and credit transfers, generate the SEPA file and document the submission traceably

→ Open payment runs · Check SEPA settings

A payment run bundles payments into one SEPA file. There are two kinds, each with its own tab: Direct debits collect customer invoices via mandate, Credit transfers pay approved purchase invoices from the payment proposal. The list shows number, status, items, amount and creation time per run.

Prepare

  • For direct debits: check the SEPA creditor data in the SEPA settings. Every invoice needs an active SEPA mandate with IBAN.
  • For credit transfers: create a bank account with IBAN as debtor account and check the supplier IBANs.
  • Choose the date so it fits the payment term, pre-notification and bank processing time.
  • After creating, read the hints about skipped or non-payable invoices.

Invoices without a mandate or IBAN are not collected silently. SimpliServ reports them as skipped when preparing.

Lifecycle

Draft → Generated → Downloaded → Collected (direct debit) or Submitted → Completed (credit transfer)

Mark as submitted is a business step. For direct debits, the linked invoices are marked as paid afterwards. Only do it after actually handing the file to the bank.

A payment run is not a test run. Before submitting, spot-check recipient, mandate reference or IBAN, amount and date, and store the XML file securely.

The step-by-step guide is in Create a payment run and export the SEPA file, all details in Create SEPA payment runs.

How is this guide?

On this page