SimpliServDocs

Prepare and check a payment run

Collect open supplier invoices in the payment proposal, clear blocked invoices and check the credit transfer run safely

→ Open payment runs in SimpliServ · Open payment proposal

A credit transfer payment run bundles due supplier invoices for one execution date. It comes from the payment proposal and ends with a SEPA file that you upload to your online banking. This guide shows how to prepare and check the run; the operation in detail is in Create SEPA payment runs.

Before creating

Check:

  • The purchase invoices are approved; only approved invoices are payable.
  • Supplier data and IBAN are correct and there is no payment block.
  • A bank account with IBAN exists under Accounting → Bank as the debtor account.
  • Due date, cash discount period and desired execution date fit together.
  • Supplier credit notes are taken into account.

Evaluate the payment proposal

Open the proposal

Open Payment runs → New payment run → Credit transfer (payment proposal). Choose Execution date, Due until and the Debit account.

Check the key figures

Compare Payable total, Discount earned, number of payments and Not payable instead of just skimming the list.

Clear non-payable invoices

The Not payable tab shows the Reason per invoice, for example IBAN missing, Supplier blocked, Suspected duplicate or Already in a payment run. Fix opens the document or supplier directly.

Read the hints

In the Hints column, watch for IBAN differs from master data, Discount expires soon and Credit note available. You offset an available credit note directly from the row.

Create the run

Select the rows and choose Create payment run. Recipients, IBANs and amounts are frozen in the run. SimpliServ then opens the run's detail page.

Changed bank details are a common fraud pattern. If an invoice's IBAN differs from the supplier master data, SimpliServ requires an explicit confirmation. Only confirm once you have verified the new IBAN with the supplier through a known channel.

Status and responsibility

A credit transfer run goes through these statuses:

  • Draft: run created, items can still be removed.
  • Generated: SEPA file generated.
  • Downloaded: XML downloaded.
  • Submitted: marked as submitted.
  • Completed: run completed.

Generate SEPA file, Download XML and Mark as submitted are separate actions. A download is not a submission. Depending on the setting chosen when creating the run, invoices are settled on submission or only once the bank transaction is matched in bank reconciliation.

Troubleshooting

  1. Check execution date and debtor account.
  2. Open non-payable invoices one by one and fix the cause.
  3. Until submission, remove wrong items from the run or cancel the run with Cancel run; the invoices then reappear in the proposal. Do not transfer an already generated file to the bank anymore.
  4. If the bank rejects a transfer, mark the item as Not executed; the invoice can then be paid again.

Invoices already in a run are blocked in the next proposal as Already in a payment run. Still, do not create a second run before you have checked the first one and submitted or cancelled it.

Four-eyes check

If four-eyes approval is active, SimpliServ requires a second person's approval before the SEPA file is generated. Even without this setting it pays off:

  • Person A creates the run.
  • Person B compares documents, total and bank details.
  • Differences are commented on the document.
  • Only then is the file generated and transferred to the bank.

How is this guide?

On this page