Before the NAVAX Payment Exports extension can be used, it must be set up.
In the window NCP Exports Setup, the general settings and defaults are defined.
Fields, General
LCY Code
Shows the currency code for the local currency. This value has been stored in the General Ledger Setup.
ISO LCY Code
Specifies the ISO LCY Code, this will be pre-filled with EUR when LCY Code is set to EUR or EURO in the General Ledger Setup and the field has not yet been configured.
Fields, Suggest Payments
In the section Suggest Payments the settings for the creation of the Payment Suggestions are defined.
Due Date Calculation
Specifies a date formula with which the Last Due Date field in the Payment Suggestion should be suggested. The date is calculated based on the work date.
Discount Date Calculation
Specifies a date formula with which the field Last Discount Date in the Payment Suggestion should be suggested. The date is calculated based on the work date.
Posting Date Calculation
Specifies a date formula with which the field Posting Date in the Payment Suggestion should be suggested. The date is calculated based on the work date.
Execution Date Calculation
The execution date is calculated as follows: For urgent payments, the date is set to today. Otherwise the date is set to the next day, unless it is a SEPA direct debit in combination with direct debit type CORE - basic direct debit, in this case the date is set to Today + 2 days.
SEPA Direct Debit Mandate ID Separator
Against the bank, the same mandate ID can be used for multiple customers/vendors. To use the same ID for multiple customers/vendors in payment transactions, you can specify a separator and a unique identifier. The separator and all subsequent characters will not be exported.
Enter the separator here. Use this special character when naming the mandate ID. When the setup is initialized, the value for the separator is empty.
Note
By default, this field is hidden and can be displayed using the Personalize function.
External Bank Account Search
Specifies how the field External Bank Account Search (vendor/customer bank account) is determined in the general ledger lines for the Payment Suggestion.
The following applies to all options: If the vendor/customer item contains a value in the field 'External Bank Account Search', this value is suggested.
Incl. Customers with Credit
Specifies that customers with credit should be included in the payment suggestion.
Incl. Vendors with Credit
Specifies that vendors with credit should be included in the payment suggestion.
Fields, Originator
In the section Originator Setup the settings for the export file are defined. When the payment file is exported, this data is exported to make you or your company identifiable as the ordering party. When you start the wizard for the first time, the values from the company data are used as default values for this step.
Name
Specifies the originator name.
Name 2
Specifies the originator name 2.
Address
Specifies the originator address.
Address 2
Specifies the originator address 2.
Post Code
Specifies the originator post code.
City
Specifies the originator city.
Country/Region Code
Specifies the country code of the ordering party used in payment transactions.
Creditor Identifier (CI)
The SEPA Direct Debit Scheme (SDD), requires the mandatory specification of a Creditor Identifier, Creditor ID or CID with each direct debit. This ID is stored in this field.
Fields, Create Payment File
Create Bal. Account Line
Specifies whether an offsetting entry line is to be created for the balanced account lines when the payment file is created.
An offsetting entry line will only be created if there is more than one journal line for an offsetting entry line.
For different document types, the offsetting entry line will only be created if all journal lines involved have a Applies-to Doc. No. set.
If this is the case, the Document Type will be set to Payment for all affected journal lines.
These changes will be saved. If the transaction is cancelled, the Document Type will be reset to the original value.
Modify allowed after File Created
With this option you can determine whether the payment data can still be manipulated after file creation.
Summary after creation
On this page you can specify whether a summary of the payment file should be shown after the payment file has been created.
In the summary, you have the option to either import the created file into your banking software using the Export Payment File action or send it directly via NAVAX konfipay Connector to konfipay with the Transfer Payment File action to forward it to your bank.”
Payment Notification Nos.
Here the payment notification number series is set up.
Pmt. Notification Report ID
Specifies the ID of the report that is printed when you print the payment notification.
Tip
Here you can enter your own report layout if the standard report does not meet your requirements.
By default, the report with the ID 70322078 - NCP Exports Pmt. Notification is entered here.
Pmt. Notification Report Caption
Specifies the name of the report that is printed when you print the payment notification.
Payment Type
Specifies the payment method for which the settings apply. The settings must be defined for all payment types that are in use.
The following options are available:
Non-SEPA Credit Transfer
SEPA Credit Transfer
SEPA Direct Debit
Bank Account No.
Specifies the bank account to which the settings apply. The setting is optional.
If no bank account is specified, the settings are valid for all bank accounts for which no special settings exist.
File Name
Specifies the name to be used to save the payment file.
The following placeholders can be used in the File Name field:
%1,%2,%3,%4,%5 Date of creation (day,week,month,year,year 4 digits)
%6 Bank Account No.
%7 File Reference (Message Reference)
%8 Clearing Entry No.
%9 User-ID
%10 Payment Type
Remittance Info. Length
Shows the maximum number of characters for the payment remittance information.
Remittance Info.
Specifies the structure and values for the remittance information in the payment file.
The following Wildcards can be used in this field.
%1 Document Type
%2 External Document No. (if available) or Document No.
%3 External Document No.
%4 Document No.
%5 Currency
%6 Amount
%7 Discount
%8 Vendor or Customer Number
%9 Our Bank Account No.
%10 Gen. Journal Line Description
%11 Document Date
%12 Payment Text (from Journal Line)
Note
The Payment Text field is hidden in Payment and Cash Receipt Journals to use it, add the field to the page using the Personalize function.
Tip
Use brackets, for example [Discount:% 7], if you want to output the text only if the placeholder has a value.
You can determine the maximum number of characters for the placeholder by specifying a numerical value within angle brackets immediately after the placeholder. Example %1<2> or [Note: %10<15>].
Collective Transaction
Specifies whether transactions should be combined when the payment file is created. They are then sent to the bank as collective transactions.
When submitting transactions to the bank, they can be consolidated for more efficient and cost-saving processing. This is done by bundling posting lines that have the same creditor, customer, or bank account number, the same external bank account code, and the same currency code into a collective transaction.
However, there are certain types of transactions, such as individual transfers and transfers with a payment reference, that are excluded from this consolidation. Credits that are balanced with a document number are also considered if the collective transaction results in a positive amount, which also applies to direct debits.
The use of this functionality is advisable when the options to summarize per creditor or debtor are not selected in the payment proposal. If booking lines have been consolidated into a collective transaction, the resulting payment item receives a corresponding label. The description of the payment item is supplemented with collective transaction.
Note
The fields for the document number and booking date are only filled in if all booking lines within the collective transaction match. If there are differences, these fields remain empty.
Always Create Notification
Specifies whether a payment notice should always be generated when the payment file is created, regardless of if the payment remittance information can be transmitted in completely form or not.
Fields, Pmt. Notification E-Mail
Edit before sending
If this option is enabled, the notification e-mails can be edited with the e-mail editor before sending.
Note
This option is only available if the Email features active option is enabled.
HTML Formatted
This value specifies that the payment notification e-mail message should be sent in HTML format.
Sender Name
Here the sender name of the payment notification e-mail message is specified. This is the name the recipient of the e-mail can see in his e-mail program.
This option is only available if the Email features active option is disabled.
CC E-Mail
Here the CC e-mail of the payment notification e-mail message is specified.
BCC E-Mail
Here the BCC e-mail of the payment notification e-mail message is specified.
This allows you to specify the period for deleting the data via NCP Exports - Delete Data. Only data that is at least 6 months old can be deleted. If the field is empty, the minimum period is used.
Last Date Archived Files deleted
Shows the date on which NCP Exports - Delete Data were last executed.
Archived Files deleted until
Specifies the date until which archived files were deleted from the clearing entries.
Actions
Bank Account Setup
In the window NCP Bank Account Setup, all bank accounts required for NAVAX Payment are defined or managed.
For more information, see Setup, Bank Account Setup.
Bank Codes
In this window, the Branch Codes and the SWIFT Codes of the banks are defined or managed.
For more information, see Setup, Bank Codes.
XML Schemas
XML schemas are required for SEPA and non-SEPA files creation. The assignment of the schemes to the individual bank accounts can be done in the NCP Bank Account Setup page.
For more information, see Setup, Exports, XML Schemas.
Payment Notification Texts und SEPA Mandate Texts are displayed and managed in the Language Setup window for each language code.
For more information, see Setup, Exports, Language Setup.
Update Bank Code URLs
Fills or updates the bankcode URL fields.
The up-to-date URL's are entered in the corresponding fields, this data is permanently updated on www.navax.app and offered as download.
System, Actions
NAVAX License Management
Opens the NAVAX License Management which displays the current license status of the NAVAX extensions.
For more information, see Appendix, NAVAX License Management.
Send Pmt. Notification Test Message
This action, gives you the possibility, to test the settings of the payment notice e-mail functionality. If the function is called, the e-mail address to which the payment notice test message is to be sent must be specified in the field Test message to.
Delete Data
By creating a payment file, an entry is made in the clearing entries. The created payment file is also saved there. If necessary, you can use this action to remove the archived payment files from the clearing items.
Setup, General, Bank Account Setup In the NCP Bank Account Setup window, all bank accounts required for payment processing with NAVAX Payment are stored and managed. Here, you can add new bank accounts, edit or remove existing accounts, and update important account details. The overview provides a clear and structured representation of all relevant bank information to make payment processing efficient and transparent...
Setup, General, Bank Codes In the page NCP Bank Codes you can manage the bank codes. You have the possibility to import bank codes easily and comfortably from 3 banking institutions...
Setup, General, Countries/Regions In this overview you can setup and manage settings for countries and regions to use them for payment transactions...
Setup, Exports, XML Schemas The EU and the EPC (European Payments Council) are intent on using the XML format as a standard in European payment transactions. At the moment, efforts are being made to minimize the numerous different national variants of payment transaction solutions and ultimately to eliminate them completely. The XML format should replace all other formats in order to standardize the processing of transactions on a technical level Europe-wide. This format is to be introduced and accepted as a standard both in the interbank sector and by customers...
Setup, Exports, Language Setup All necessary settings for the individual language codes are set up here. Also the Payment Notification Texts and the SEPA Mandates Texts can be stored or set up here...
Tasks, Exports, Payment Notification E-Mail Suggestion With a payment notification, you can document which open entries you want to pay or collect in the payment file after you have created the payment file. A payment notification is useful (especially for collective transfers) to make it easier for the recipient to identify the payments...
Appendix, NAVAX License Management The NAVAX License Management page (in older versions NAVAX License Overview or NCEX License Overview) displays the current license status of the NAVAX extensions...