Skip to main content

Edit payment transaction settings

Updated over 2 months ago

Select Organisation > Master data > Banks > Edit payment transaction settings.

In the payment transaction settings, you can make the following settings that affect payment transactions.

image-20250819-140814.png

Payment transactions - General

  • Create payment advice note from
    Specify from how many items per target bank a payment advice note should be created for notification. This depends on how much text you transmit in the purpose. As a rule, an AVIS is recommended from 3 or more items.

  • Separate transfers to a target bank account by personal account number
    A transfer normally includes payments from a payment run that have the same target bank account, house bank account and value date. Use this setting to add the personal account as an additional criterion.

  • Remove account statement
    Should it be possible to remove uploaded statements (mt940, camt53) or can they only be hidden when inactive?

  • Limit account statement turnover preview
    In the account statement overview, the display of individual account statement transactions is omitted. Instead, the total number of unprocessed, i.e. still open lines of the account statement, as well as the number of posted and inactive lines in the statement are displayed.
    This increases the overview of the form and significantly reduces the loading time of the account statements.

Payment transactions - output format of the payment advices

  • PDF system format or customised layout
    You can find more information on creating a customised layout in the document layouts section.

Payment transactions - purpose

Depending on the selection - purpose or payment reference - different options are then offered (shown side by side in the image above)

  • Determine from which elements the purpose of use should be generated.
    This is filled in the XML file generated in the payment and direct debit run if a payment reference is not transmitted at the same time.

Payment transactions - payment reference

  • Determine from which data field the payment reference is filled. If a payment reference is transmitted, no payment reference is transmitted as the reference specified by the supplier is unique for the supplier.

image-20250819-141054.png

Payment transactions - Posting bank transactions

  • Posting bank transactions
    Set a posting text proposal for posting bank transactions.

  • Do not post payment list
    Normally, when the payment list is created, a posting is triggered via vendor to the house bank's transit account. This automatically clears the open item. Here you can select "Yes" to suppress this automatic process.

Payment transactions - IBAN and SEPA support

  • SEPA Creditor ID
    Here you store your creditor ID centrally. You store the mandate reference yourself at the contact in the customer role.

Payment transactions - automatic generation of SEPA mandate references

  • To make mandate references distinguishable, specify here the basis on which the printout is generated.

Payment transactions - SEPA expert settings

  • Show as batch booking on the bank side
    The term "batch booking" refers to the "payment collector". By ticking the checkbox, you instruct your bank to execute the payment run as a collective collection or collective transfer. The account transactions only show the total, which you normally post against the transit account, resulting in a zero balance. See also: Do not post payment list.

  • BIC is a mandatory entry
    In the EU, it has been sufficient to enter the IBAN since 2016; this is different for non-EU countries (e.g. Switzerland).
    Tick the checkbox if the BIC is to be checked.

  • Address is a mandatory entry
    If you tick the checkbox, the full address of the beneficiary (or debited party) is a prerequisite for executing the payment run (Contact, General role, Main address: Street, postcode, city, country).

Did this answer your question?