The payment transaction settings influence the payment runs, both for transfers and direct debits.
The data can also be changed via Organization > Master data > Edit payment transaction settings .
Account statements
Account statement - Removal permitted
Specify whether uploaded statements (mt940, camt53) may be removed or whether they can only be made inactive and therefore hidden.Account statement - limit sales preview
If you activate this function, the individual sales of the account statement are not displayed in the account statement overview. Instead, the total number of unprocessed, i.e. still open, lines of the account statement and the number of posted and inactive lines in the statement are displayed. This improves the overview of the form and considerably reduces the loading time of the account statements.
Payment run settings
Complete main address is mandatory
If this function is activated, the complete address of the beneficiary (or debited party) is a prerequisite for executing the payment run.
The main address can be found in Contact > Role General, Main address: Street, zip code, city, country.BIC is mandatory, even with a valid IBAN
In the EU, it has been sufficient to enter the IBAN since 2016; this is different for non-EU countries (e.g. Switzerland). By activating, the BIC is also checked when the payment run is created.Default value for payment-inf-ID
βAdopt due date as value date
You can adopt the net due date as the value date. You can switch the setting separately for credit transfers and direct debits.Mandate reference is mandatory for direct debits
The activated function checks whether there is a valid mandate reference, which you can find in the debtor.
The collection is not executed without a valid mandate reference.Set EndtoEnd Reference (EREF) for direct debits
The EREF is a unique ID for a payment within the SEPA area that is similar to a consignment number. It identifies a SEPA payment from ordering party to recipient and enables automatic allocation, even for returns. Setting the EREF is optional.
Intended use and payment reference
First decide whether you want to transmit the purpose of payment or the payment reference, the latter is widely used in Austria. Depending on your selection, you can then make different specifications.
Use payment reference
You can transmit the payment reference in the field provided (to be entered in the invoice receipt book or via Posting details > Open items > Edit) or alternatively the document text (posting text). Please note that the document text often also contains internal data in practice.Use purpose
You can create the VWZ from the customer number, external document number, the posting line text and the OP text. Please note that the latter can also contain internal data in practice, which is why we recommend the external document number and the customer number. You can enter the latter in the respective customer or vendor role.
Payment advice settings
Create payment advice notes from how many line items
Specify from how many items per target bank a payment advice note should be created for notification. As a rule, a payment advice note is recommended for 3 or more items. This depends on how much text you send in the note to payee.Output format (layout)
Decide whether you want to create your PDF advice note in the standard system format or on the basis of an individual layout.
With the system format, you can then define the font size and specify which information should be included in an item.
With the individual layout, you can define and edit the document layout. You can find more information on creating an individual layout in the document layouts section.
Payment file and export
Individual payment records per person account
By activating this option, you can separate transfers to a target bank account by person account number. Normally, a transfer includes payments from a payment run that have the same target bank account, house bank account and value date. With this setting, you add the personal account as an additional criterion.Output as ...
Define the "payment collector" behind the term "batch booking". By selecting the checkbox, you instruct your bank to execute the payment run as a batch booking or batch 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.Generate SEPA files for finAPI (file splitting)
β
Posting the payment run
Post payment run
Activate this function to trigger a posting via vendor to the house bank's transit account when generating the payment list. This automatically clears the open item.Posting text
Define the posting text for the posting to the transit account.
Direct debits and mandate references
SEPA creditor ID of your own company
You store your creditor ID centrally here.Always create SEPA mandate reference when creating a customer
If this function is activated, a mandate reference is automatically created for a new customer.Generate mandate reference with which feature
To make mandate references distinguishable, specify here the basis on which the value is generated. You store the mandate reference itself at the contact in the customer role.
Sequence behavior for direct debits
The sequence type (FRST (first), RCUR (recurring), OOFF (one-off) and FNAL (last)) informs the bank about the nature of the mandate and the sequence of transactions, which is relevant for correct processing by the bank. The sequence can be predefined by the sequence behavior.
SEPA expert settings
SEPA version - default
If necessary, you can revert to an older SEPA version here. The recommended setting Current version means that you always use the latest version offered.
This means that you can simply continue working with updates and do not have to make any settings to stay up to date.
β
