NCP Payment Export Setup Wizard
NCPE Payments Export Setup
Bank Account Setup
Bank Codes
XML Schemas
XML Schema Values
Countries/Regions
Language Setup
SEPA Mandates Text Lines
Customer Bank Account List
Vendor Bank Account List
SEPA-Direct Debit-Mandates
Export Tasks
Working with Payments Export
Payment Journals
Make Payment Suggestions
One-Time Transfer
Create Payment File
Payment File Summary
Payment Notification E-Mail Suggestion
NCP Payments is integrated in the financial management of Business Central. The extension
NCP Payments consists of 2 modules, which are available separately, and adds the following
functions to Business Central:
Export
NCPE Payments Export (NCPE Payments Export by NAVAX) extends Dynamics 365 Business
Central with the capability to create payment files for submitting to your bank. NCP Payments
Export works with payment suggestions (and direct debit suggestions) based on open entries of
vendors and customers to create a payment file. This file can then be transferred to your bank
via the banking software.
The following formats are supported:
Non-SEPA-Credit Transfer
SEPA-Credit Transfer
SEPA-Direct Debit
Import
NCPI Payments Import (NCPI Payments Import by NAVAX) extends Dynamics 365 Business
Central with the functionality of importing the payment files that you can download from your
bank to use in Business Central in a payment book sheet.
The following formats are supported:
camt.052 - includes the balance report and the intraday sales. This includes debits and
credits to the corresponding accounts. The camt.052 message also contains details of the
individual transactions on the accounts.
camt.053 - provides information about posted transactions on the relevant accounts. It
contains the posted transactions, details of the corresponding postings, and the balance
notifications for the accounts.
camt.054 - informs about upcoming and posted transactions and their details.
To be able to use the extension NCPE Payments Export, some settings must be done. The
module comes with a Assisted Setup that helps to configure the necessary parameters for use.
To do this, go to Setup and Extensions > Assisted Setup from the role center and select the
entry NCPE Payments Export Setup. The step-by-step wizard guides you through the setup.
Navigation
The NCPE Payments Export or NCPI Payments Import is integrated in the roles of Accountant
and Accounting Manager.
Actions, pages and reports that originate from the extension NCPE Payments Export (NCPE
Payments Export by NAVAX) will be "Tell me what you want" recognized.
Use the search term "Payments Export" or the alternative search terms "ncpe", "sepa" and/or
"navax".
Actions, pages and reports that originate from the extension NCPI Zahlungsverkehr Import
(NCPI Payments Import by NAVAX) will be "Tell me what you want" recognized.
Use the search term "Payments Export" or the alternative search terms "ncpe" and/or "navax".
Before the NCP Payments Export (NCPE Payments Export by NAVAX) can be used, its basic
functionality must be set up. This wizard will help you to setup the necessary parameters by
walking through them step by step, so you can immediately start working with the NCP Payments Export.
In the following section the steps with the parameters are explained.
Fields, Page Originator Setup
In the section Originator Setup the settings for the export file are defined that specify the
originator. If the payment file is exported then this is the data that is that makes your company
identifiable as the ordering party. When you start the wizard for the first time, the values from
the company information are used for this step.
NameSpecifies the originator name.
Name 2Specifies an addition to the originator name.
AddressSpecifies the address of the originator.
Address 2Specifies an addition to the address of the originator.
Post CodeSpecifies the post code of the originator.
CitySpecifies the city of the originator.
Country/Region CodeSpecifies the country/region code of the originator used in payment
transactions.
CreditorIdentifier(CI)The SEPA Direct Debit Scheme (SDD), requires the mandatory provision of a
Creditor Identifier, Creditor ID or CID with each direct debit. This ID is stored
in this field.
With next you get to the next setup page of the wizard.
Note
You can skip individual steps at any time and complete the configuration at a later time in the
NCP Payments Export Setup.
XML Schemas are required for the generation of SEPA and non-SEPA files. With this wizard you
can import predefined schemas.
In order to be able to use them for the export of the payment file for your bank, you must
assign the XML Scheme to a bank. The association of the schemas
to the individual bank accounts is done in the Bank Account Setup which you will find later
within the wizard. With the action
Download XML Schemas the download and import into the database is started.
Page, SEPA Countries Setup
With this wizard page you can set up the SEPA countries in the countries/regions table. The
field "SEPA" is set, which is used to identify the participating SEPA countries based on a list of all
participating countries. With the action Setup SEPA Countries the setup is started.
Page, Bank Codes Setup
With this wizard, you can import bank codes from 3 different sources. You have the choice to
download the data from the specific banking institutions or from all of them together. The
sources of the data are the European Central Bank, the Austrian National Bank or the Deutsche
Bundesbank. This download creates records in the table Bank Codes.
Page, Bank Account Setup
In this step the Bank Account Setup can be completed. If you click on the action Open Bank
Account Setup, the page will open where you can enter your bank details and link the XML
Schemas that you want to use.
For more information, see Setup, Bank Account Setup.
Note
The XML Schemas can change or be supplemented in the future. We provide the latest
rulebooks online, these updates and changes can be downloaded
in the NCP Payments Export Setup using the action XML Schemas. In the opened page click
the action Download in the XML Schemas setup.
For more information, see Setup, XML Schemas.
Define here the necessary settings for the creation of the Payment File.
CreateBal.AccountLineHere you can configure whether an balanced account line should be
created.
Modify allowed after
"File Created"
With this option you can determine whether the payment data can still be
manipulated after creation.
Payment Notification
Nos.
Here the payment notification number series is set up.
The action Payment File Setup creates default entries that are not assigned to a specific
account. A line is created in the table Payment File Setup for each Payment Type.
For more information, see Setup, Payment File Setup.
Fields, Payment Notification E-Mail Setup
Use this wizard to configure the necessary parameters for sending the notification e-mails.
SenderNameHere the sender name of the payment notification e-mails is specified. This is also
the name the recipient of the e-mail can see in his e-mail program.
Sender E-MailThe sender e-mail of the payment notification e-mails is specified here.
CC E-MailHere the CC e-mail of the payment notification e-mails is specified.
BCC E-MailHere the BCC e-mail of the payment notification e-mails is specified.
HTMLFormattedThis value specifies that the payment notification e-mails should be sent in HTML
format.
With the action Send Test Message an E-Mail can be sent to check the settings.
Page, Language Setup
All the necessary settings for the individual language codes, as well as notification texts and the
SEPA mandate texts will be set up on this page. Values can be suggested for the language setup
Note
Before you can send a test message or use the notification e-mail functionality, you must first
complete the SMTP Mail Setup. You can find information about this in the Business Central
Online Help under Set Up E-Mail
via the action Initialize Languages. In most cases, no language code is stored for vendors and
customers. You should therefore also set up a record without a language code.
Finish Setup
If you click on Finish the configuration will be written into the table NCP Payments Export
Setup.
Before the NCPE Payments Export (NCPE Payments Export by NAVAX) extension can be used, it
must be set up.
In the window NCPE Payments Export Setup, the general settings and defaults are defined.
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 formular with which the field Posting Date in the Payment Suggestion
should be suggested. The date is calculated based on the work date.
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.
Important
The trial version expires in 30 days.
After that, the functions of NCPE Payments Export (NCPE Payments Export by NAVAX) can only
be used with a valid license.
Please note that the licensing process may take some time.
The license can be applied for or verified using the action What's New?.
A browser window is opened.
Then click on Send License Request to send an e-mail with your request.
In the following days you will receive an e-mail with further information.
As soon as the licensing is completed (or if a license already exists), the license can be updated
using the action Update License.
For more information, see Update License..
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.
NameSpecifies the originator name.
Name 2Specifies the originator name 2.
AddressSpecifies the originator address.
Address 2Specifies the originator address 2.
Post CodeSpecifies the originator post code.
CitySpecifies the originator city.
Country/RegionCodeSpecifies 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
In the section Create Payment File and Payment File the settings for the different payment files
are defined. You can set up one bank account per payment type that uses this setting. If the
field Bank account number leaved blank, then this setting applies globally for all bank
accounts.
CreateBal.AccountLineHere you can select if a balancing account line should be created.
Modify allowed after
"File Created"
With this option you can determine whether the payment data can still be
manipulated after file creation.
Payment Notification
Nos.
Here the payment notification number series is set up.
Payment TypeSpecifies the payment method for which the settings apply. The settings
must be defined for all payment types that are in use.
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 NameSpecifies 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. LengthShows 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-/Customer-/Employee-Number
%9 Our Bank Account No.
%10 Gen. Journal Line Description
%11 Document Date
%12 Payment Text
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:
Collective TransactionSpecifies whether transactions with the same vendor/customer/bank
account number, external bank account code, and currency code should
be combined when the payment file is created. They are then sent to the
bank as collective transactions.
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, Pmnt. Notification E-Mail
In the section Pmnt. Notification E-Mail, the settings for the notification e-mail sending are
configured. If you have created a Payment File you can view a list of possible payment
notification e-mails on the page NCP Payment File - Summary with the action Payment Notification E-Mail Suggestion. The parameters you set up in this section will be used as the
default value for sending.
HTMLFormattedThis value specifies that the payment notification e-mail message should be sent
in HTML format.
Sender NameHere 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.
SenderE-MailHere the sender e-mail of the payment notification e-mail message is specified.
CC E-MailHere the CC e-mail of the payment notification e-mail message is specified.
BCC E-MailHere the BCC e-mail of the payment notification e-mail message is specified.
For more information, see Tasks, Payment Notification E-Mail Suggestion.
In the section Bank Codes Resources the sources for the Download of the bank codes are
defined. You can start the Download through assisted setup or on the Bankcodes page.
EZBBankCodesURLSpecifies the URL for the download of the bankcodes from European Central
Bank
OENB Bank Codes
URL
Specifies the URL for the download of the bankcodes from European Central
Bank.
DBB Bank Codes
URL
Specifies the URL for the download of the bankcodes from German National
Bank.
VersionSpecifies the currently installed version of the Extension.
Serial No.Specifies the serial number of the Extension.
License
Status
Displays the license status of the Extension.
Delete
Data Date
Calculation
This allows you to specify the period for deleting the data via Payments Export - 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 Payments Export - Delete Data were last executed.
Archived
Files
deleted
until
Specifies the date until which archived files were deleted from the clearing entries.
Bevor der NCPI Zahlungsverkehr Import (NCPI Payments Import by NAVAX) verwendet werden
kann, muss dessen grundlegende Funktionalität eingerichtet werden.
Im Fenster NCPI Zahlungsverkehr Import Einrichtung werden die allgemeinen Einstellungen
und Vorgaben festgelegt.
TODO
Important
Die Testversion läuft in 30 Tagen ab.
Danach können die Funktionen von NCPI Zahlungsverkehr Import (NCPI Payments Import by
NAVAX) nur mehr mit einer gültigen Lizenz genutzt werden.
Beachten Sie, dass der Lizenzierungsprozess einige Zeit dauern kann.
Die Lizenz kann über die Aktion What's New? beantragt bzw. überprüft werden.
Dabei wird ein Browserfenster geöffnet.
Klicken Sie anschließend auf Lizenzanfrage senden um eine E-Mail mit Ihrer Anfrage zu senden.
In den nächsten Tagen erhalten Sie eine E-Mail mit weiteren Informationen.
Sobald die Lizenzierung abgeschlossen ist (oder wenn bereits eine Lizenz vorhanden ist, kann
die Lizenz über die Aktion Lizenz aktualisieren aktualisiert werden.
Weitere Informationen dazu finden Sie unter Lizenz aktualisieren.
In the page NCP Payment Transactions Bank Codes you can manage the bank codes. You have
the possibility to import bank codes easily and comfortably from 3 banking institutions.
Note
If there are already records in the table NCP Bank Code you will be asked how to proceed. You
have different possibilities how the import the data are to be handled.
Specifies the bank branch no. of the bank. If the data was imported via Download, the
bank branch no., if available, is only imported and viewed for austrian and german bank
institutes.
NameSpecifies the name of the bank institute.
ISO
Country
Code
Specifies the ISO code for the country or region of the bank.
AdressSpecifies the address of the bank. If the data was imported via the Download, the
address, if available, is only imported and viewed for austrian institutes.
Post CodeSpecifies the postal code of the bank.
CitySpecifies the city of the bank.
CountySpecifies the federal region or country of the bank. If the data was imported using the
Download, the county, if available, is imported and viewed only for austrian banks.
Telefon No.Specifies the phone number of the bank. If the data was imported via the Download,
the telephone number, if available, is only imported and viewed for austrian banks.
Fax No.Specifies the fax number of the bank. If the data was imported via the Download, the
fax number, if available, is only imported and viewed for austrian banks.
E-MailSpecifies the e-mail address of the bank. If the data was imported via the Download,
the e-mail address, if available, is only imported and viewed for austrian banks.
WebsiteSpecifies the website address of the bank. If the data was imported via the Download,
the website address, if available, is only imported and viewed for austrian banks.
InformationContains further information about the bank. With Download of the German bank
codes, the short name of the bank is entered in this field. With the Download of the
Austrian bank codes you can see if the bank is the main bank or a branch. This makes it
easier to find out whether it is a branch or the main bank
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.
Use this page to manage the XML schemas that are required for exporting the payment file.
These schemas are used to map the data from Business Central to the fields in the XML schema
file.
Fields
TypeSpecifies the type of XML schema. Possible values are: SEPA Credit Transfer, SEPA
Direct Debit and Non-SEPA Credit Transfer
CodeSpecifies the code of the XML schema. This code meets the SEPA standard of the
schema. You can find more information on this on Stuzza
ISO Country
Code
Specifies the countries for which the schema is valid. Some countries have different
requirements of the ISO standard.
DescriptionThe field Description is a combination of the abbreviation of the field Type, the ISO
country code and the rulebook version of the schema. This only applies to
downloaded schemas. If you have created a schema yourself, the Description is
assigned by you.
IBAN Only
possible
The field IBAN Only possible indicates that the schema also supports transactions
without the specification of SWIFT Code.
Dom. IBAN
Only
The field IBAN Only possible indicates that the schema also supports transactions
without the specification of SWIFT Code. If Dom. IBAN Only is set, domestic
transactions are also allowed without SWIFT Code.
Int. IBAN
Only
The field IBAN Only possible indicates that the schema also supports transactions
without the specification of SWIFT Code. If Int. IBAN Only is set, foreign transactions
are also allowed without SWIFT Code.
The field IBAN or Bank Account No. possible indicates that the schema also supports
transactions without IBAN.
IBAN or
Bank
Account No.
The field IBAN or Bank Account No. possible indicates that the schema also supports
transactions without IBAN. If IBAN or account number is set, the account number of
the recipient bank is written to the payment file if no IBAN exists.
Address
Specification
possible
Indicates that the schema supports address information.
Originator
Address
The field Address Specification possible views whether the scheme supports address
data. The field Originator Address specifies whether the address data of the
originator, which was stored in the NCP Payments Export Setup, should be written to
the payment file.
Recipient
Address
The field Address Specification possible indicates that the scheme supports address
data. The field Recipient Address specifies the address data of the recipient that
should be written to the payment file.
Batch
Booking
Specifies how the transaction is posted on the bank side. That is, whether it is a
collective posting ('Yes') or an individual posting ('No').
Extended
Character
Set
Specifies if the expanded character set should be activated.
Charges
Selection
possible
Indicates that the schema allows the specification of charges.
Urgent
Payment
possible
Indicates that the schema supports urgent payments.
Date of
Specification
Specifies the date of the specification.
Last Date
Modified
(Schema
Lines)
Shows whether, and if so, when the schema lines were last changed.
On this page you will find a list with the available values you can use for XML Schemas. The
fields are assigned to the lines on the page NCP Payments XML Schemas.
For more information, see XML Schemas.
Fields, General
ValueView the placeholder or value that can be used in the XML Schema.
DescriptionView further information about the value.
In this overview you can setup and manage settings for countries and regions.
For more information, see Change basic settings on Business Central online help.
Use this setup page to define the settings for the individual countries/regions for your business.
CodeSpecifies the country/region of the address.
NameSpecifies the name of the country/region.
ISOCode
Specifies a two-letter country code defined in ISO 3166-1.
SEPASpecifies that the country or region participates in SEPA. SEPA (Single Euro Payments Area)
aims to use the same procedures and standards for euro payments. If this check mark is
not correctly set, no SEPA file can be created for the customers and vendors to which it
applies.
ISO
Numeric
Code
Specifies a three-digit code number defined in ISO 3166-1.
Address
Format
Specifies the format of the address that is displayed on external-facing documents. You
link an address format to a country/region code so that external-facing documents based
on cards or documents with that country/region code use the specified address format.
Contact
Adress
Format
Specifies where you want the contact name to appear in mailing addresses.
Intrastat
Code
Specifies an Intrastat Code for the country/region you are trading with.
For more information, see Intrastat on Business Central online help.
VAT
Scheme
Specifies the national body that issues the VAT registration number for the country/region
in connection with electronic document sending.
Actions
Note
If the County field is filled in, then the county will be printed above the country/region
unless you select the City+County+Post Code option.
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. With the Supported Setup, values can be suggested for the setup.
Fields
Language
Code
Specifies the code for the language. If you want to perform setup for vendors and
customers who have not defined a language code, leave this field blank. Click the field
to view the existing language codes in the Language table.
Language
Name
Views the description for the language.
Linked
Language
Code
Using the field Linked language code allows you to link texts from another language
code. This means that the text is not set up with the current language code, but with a
linked code.
SEPA
Mandates
Text Exists
Views if there is a SEPA mandate text for this language setting or not. Click on the field
or on the SEPA Mandate Text action to view the text.
Pmnt.
Notification
Payment
File Text
Specifies the text to be used for the payment notification in the payment file. The
following placeholders can be used in the Payment Notification Text in Payment File
field: %1 Payment Notification No.
Pmnt.
Notification
E-Mail
Subject
Specifies the text that is to be used for the subject of a notification e-mail. The
following placeholders can be used in the Notification E-mail Subject field: %1
Notification No.
Note
In most cases, no language code is stored with the vendors and vendors. Therefore, you should
also set up a data record without language code.
Before executing a SEPA direct debit, you must have an agreement with the business partner. To
do this, you create a SEPA mandate form. You define the text modules for this form as SEPA
mandate text.
The best suitable text block is determined in the following order (the first one found is used):
In the Customer Bank Account List you can create the bank accounts of your customers. You
can access the overview by clicking on Customers-list or -card on Navigate > Customer > Bank Accounts.
For more information, see Setup Bank Accounts on Business Central online help.
Fields
CodeSpecifies a code to identify this customer bank account. You can use the same
code to link each customer to their bank account (for example, BANKACC1).
NameSpecifies the name of the bank where the customer's bank account is managed.
Country-/Region
Code
Specifies the country/region of the address. This field is important, for example, to
check if SEPA transactions are allowed for this account.
IBANSpecifies the bank account's international bank account number.
SWIFT-CodeSpecifies the SWIFT code (international bank identifier code) of the bank where
the customer has the account.
Phone No.Specifies the telephone number of the bank where the customer has the bank
account.
ContactSpecifies the name of the bank employee regularly contacted in connection with
this bank account.
Main Bank
Account
in this field, the bank account can be marked as main bank account.
SEPA MandatesShows the number of SEPA mandates for this bank account. If you click on the
number, you will get the details of these SEPA mandates.
For more information, see SEPA Mandates.
Note
If a customer has defined more than one bank account, this indicator identifies the
bank account as the default for payment suggestions, for example.
In the Vendor Bank Account List you can create the bank accounts of your vendors. You can
access the overview by clicking on Vendors-list or -card on Navigate > Vendor > Bank Accounts.
For more information, see Setup Bank Accounts on Business Central online help.
Fields
CodeSpecifies a code to identify this vendor bank account. You can use the same code
to link each vendor to their bank account (for example, BANKACC1).
NameSpecifies the name of the bank where the vendor's bank account is managed.
Country-/Region
Code
Specifies the country/region of the address.
IBANSpecifies the bank account's international bank account number.
SWIFT-CodeSpecifies the SWIFT code (international bank identifier code) of the bank where
the vendor has the account.
Phone No.Specifies the telephone number of the bank.
ContactSpecifies the name of the bank employee regularly contacted in connection with
this bank account.
Main Bank
Account
in this field, the bank account can be marked as main bank account.
Note
This field is important, for example, to check if SEPA transactions are allowed for
this account.
Note
If a vendor has defined more than one bank account, this indicator identifies the
bank account as the default for payment suggestions, for example.
With the authorization of your customer, you can collect payments directly from the customer's
bank account.
In order to be able to process Direct Debits you set up the customer's payment method. Finally,
set up the direct debit mandate that corresponds to your agreement with the customer to
collect payments within a certain period of time.
To advise the bank to transfer the payment amount from the customer's bank account to your
company's account, create a direct debit posting that contains information about bank
accounts, the sales invoices that are affected, and the direct debit payment instruction. You then
export an XML file based on the direct debit entry and send it to your bank for processing.
Before you can create an XML file with the payment data, you must perform the following setup
steps:
Set up the bank account to which the collected amounts from your customers should be
posted.
For more information, see Setup, Bank Account Setup.
Set up the payment method of the customer.
Set up the direct debit mandate that corresponds to your agreement with the customer to
direct debit his payments within a certain period of time.
Note
SEPA direct debits can only be executed for documents with the currency EURO.
Specifies that the mandate is a CORE - basic direct debit, a B2B - company direct
debit or a COR1 - basic direct debit with reduced processing time.
FinalDDCreatedSpecifies when the final direct debit was created for this mandate.
First Direct Debit
Created
Specifies that the first direct debit was created for this mandate.
Mandate Form
Printed
Specifies that the mandate form has been printed for this mandate. This field is
set if you called the action Print Mandate Form and you printed the form.
Valid FromSpecifies the date when the direct-debit mandate starts.
Valid ToSpecifies the date when the direct-debit mandate ends.
Payment Entries
Exists
Shows the number of payment entries (regardless of the direct debit sequence)
for the mandate.
Customer Bank
Account Code
Specifies customer bank account that the direct-debit mandate is activated for.
The field is filled automatically.
Date of
Signature
Specifies when the direct-debit mandate was signed by the customer.
Payment TypeSpecify that the agreement covers several (recurring) or a single (one-off) direct
debit.
BlockedSpecifies that the mandate is locked. This is set if, for example, a customer has
been declared as insolvent.
ClosedSpecifies that the direct-debit mandate is closed, for example because the date in
When you make payments to vendors or customers or gather open entries, you post the
respective payment entries in a payment or cash receipt journal. These journals have been
optimized for applying and executing payments. They contain several powerful features, such as
the Payment Suggestion function, which helps you to find outstanding payments and insert
them into a payment or cash receipt journal. NCPE Payments Export extends this functionality
to enable you to process your payment transactions quickly, easily and in a customer-friendly
manner, in compliance with national and international standards. You can export data to a
Payment File from a payment or cash receipt journal.
Below you will find instructions on how to do this.
In both cases the following steps will lead you to your goal:
Making a payment suggestion
To create a payment proposal, proceed as follows:
1. In the role center, klick - NCP Payments - Payment Journal or Cash Receipt Journal.
2. Click on Suggest Payments (Suggest Customer Payments, Suggest Vendor Payments
or Suggest Employee Payments)
The Vendor Payment Suggestion, Customer Payment Suggestion or Employee
Payment Suggestion window opens.
3. Enter the desired parameters.
4. Click on OK.
The outstanding entries are determined and written to the journal.
For more information, see Payment Journal.
For more information, see Tasks, Make Payment Suggestions.
Creating a Payment File
To create a Payment File, follow these steps:
1. Click (in the journal) on the action Create Payment File.
Note
You initiate payments to vendors and customers (for example, credit memos) in the payment
journal.
In the cash receipt journal, you initiate the collection of payments from customers.
2. Click on OKand confirm the message. The payment file is created.
For more information, see Tasks, Create Payment File.
Getting Payment Information
In the following section you will learn how to get information about the entries in the
journal or the created Payment Files.
The Payment Statistic
With the action Payment Statistics, a new page is opened. In the page, a line per
payment file that was created from the journal is listed.
For more information, see REports and Analysis, Payment Statistics.
Clearing Entries
When a payment file is created, a clearing entry is being created.
To display the clearing entries, proceed as follows:
With the action Clearing Entries you open the overview of the Clearing Entries for
the respective bank account. You will find the action:
via the role centre under NCP payments - Clearing Entries
in the Bank Account
in the Payment Entries
or in the Journal
For more information, see History, Clearing Entries.
Payment Entries
When creating the Payment Files, Payment Entries are being created.
You can open payment entries in the following areas:
via the role centre under NCP payments - Clearing Entries and then the action
Payment Entries
in the Bank Account
in the Payment Entries
or in the Journal
on Customer/Vendor/Employee with the action Payment Entries
For more information, see History, Payment Entries.
Payment Remittance Entries
Payment entries are created when a payment file is created. They contain information
about which entries were cleared by the payment.
1. Open the Payment Entries as described above.
2. Click on the button Remittance Entries.
An overview of the entries, that were generated for the bank account when the
payment file was created, is displayed.
For more information, see History, Payment Remittance Entries.
When you post the journal, a Payment Posting Entry is created, which contains
information about the posting.
You can access this overview by clicking on the No. of Pmt. Posting Entries field in the
Payment Entry list.
For more information, see History, Payment Posting Entries.
The document numbers are numbered in ascending order by the payment
suggestion. If a Start from Document No. is set in the payment suggestion, this is
used for the first journal line.
External
Document
No.
Specifies a second document number. This usually refers to the numbering system
used by the customer or vendor.
Account
Type
Specifies the account type for the field Account No..
The following values are available:
G/L Account
Customer
Vendor
Bank Account
Fixed Asset
IC Partner
Employee
Account
No.
Specifies the account number that the entry on the journal line will be posted to.
DescriptionSpecifies the description of the entry.
Note
Please note - it may or may not be the date ON WHICH the payment is posted.
Note
This field is copied from the payment suggestion, it is also taken into account
when determining the discount.
Note
If you fill the journal by payment suggestion then only customer and vendor or
employee appears in the Account Type.
Specifies the code of the currency for the amounts on the journal line.
Payment
Method
Code
Specifies how to make payment, such as with bank transfer, cash, or check.
AmountSpecifies the total amount (including VAT) that the journal line consists of.
Amount
(LCY)
Specifies the total amount in local currency (including VAT) that the journal line
consists of.
Bal.
Account
Type
Specifies the type of account that a balancing entry is posted to, such as BANK for
a cash account.
Bal.
Account
No.
Specifies the number of the general ledger, customer, vendor, or bank account
that the balancing entry is posted to, such as a cash account for cash purchases.
Applied
(Yes/No)
Specifies if the payment has been applied.
Applies-to
Doc. Type
Specifies the type of the posted document that this document or journal line will
be applied to when you post, for example to register payment.
Applies-to
Doc. No.
Specifies the number of the posted document that this document or journal line
will be applied to when you post, for example to register payment.
Applies-to
Doc. Due
Date
Specifies the due date from the Applies-to Doc. on the journal line.
Payment
Type
Specifies the payment typ for the journal line.
The following values are available:
Non-SEPA Credit Transfer
SEPA Credit Transfer
SEPA Direct Debit
The unique or main bank account of the customer and vendor is automatically
filled in this field.
Mandate IDSpecifies the mandate identification number.
Direct
Debit Type
Specifies the direct debit type for the transaction.
Direct
Debit
Sequence
Specifies the direct debit sequence
Options:
One-Off
Recurrent
First
Last
Original
Direct
Debit
Sequence
The field Original Direct Debit Sequence is being filled if the sequence is changed
automatically by the file creation. If the transaction is cancelled, the direct debit
sequence is reset.
Date of
Mandate
This field will be filled when you enter the External bank account code field or via
the payment suggestion and can be changed in the journal if necessary.The
default value is based on the field Date of Signature from the customer bank
account card.
The field Payment Type can already be filled by the payment suggestion. You can
only change the value, in a standard setup, as long as the indicator Payment
Created is not set.
Note
Here you can change the selected account or afterwards select an account.
Note
This field is only available in the cash receipt journal.
Note
This field is only available in the cash receipt journal.
The value of the mandate in the Mandate ID field is automatically applied into this
field.
Note
This field is only available in the cash receipt journal.
The value of the mandate is automatically applied in this field.
Note
This field is only available in the cash receipt journal.
The value of the mandate is automatically applied in this field.
Note
This field is only available in the cash receipt journal.
Payment reference of the vendor (in the payment journal) or the customer (in the
cash receipt journal).
One-Time
Transfer
This is the indicator for a one-time instruction.
For more information, see One-Time Transfer.
Payment
Status
If the file has already been created, this field is automatically filled with the option
File Created.
No. of
Payment
Entries
Number of payment entries for this journal line.
Execution
Date
Date on which the payment will be executed.
Pmt.
Notification
If a payment notification exists for this line, the field is automatically filled with the
option "Yes". For more information, see Create Payment Notification.
Pmt.
Notification
No.
The number of the notification. This number is obtained from a number series that
you have set up in the NCP Payments Export Setup in the field Payment Notification Numbers. For more information, see NCP Payments Export Setup Create Payment Files.
Pmt.
Notification
Printed
Indicates that the payment advice note has already been printed.
Pmt.
Notification
E-Mail Sent
Kennzeichen, dass das Avis bereits versendet wurde.
Bank
Payment
Type
Specifies the code for the payment type to be used for the entry on the journal
line.
Note
This field is being filled by the system when a one-time bank transfer is set up.
Note
This indicator is automatically set when you execute the Payment Notification EMail Suggestion and print the Payment Notification after creating the Payment
File.
Note
This indicator is automatically set when you execute the Payment Notification EMail Suggestion and send the Payment Notification vie e-mail after creating the
Payment File.
Note
This field is only available in the payment journal. This field is copied from the
CorrectionSpecifies the entry as a reversal entry. This only causes the entry to be viewed on
the "wrong" side with a negative sign on various analyses.
Collective
Transaction
No.
This field is hidden by default. If the indicator Collective Transaction is not set in
the Payments Export Setup (For more information, see Payments Export Setup.),
collective transactions are not executed. Lines with the same collective transaction
number are combined anyway.
Actions
Suggest Vendor Payments
This action determines open Vendor Ledger Entries according to your settings and inserts
them in the journal to proceed the payment transaction.
For more information, see Tasks, Suggest Payments.
Suggest Customer Payments
This action determines open Customer Ledger Entries according to your settings and
inserts them in the journal to proceed the payment transaction.
For more information, see Tasks, Suggest Payments.
Suggest Employee Payments
This action determines open Employee Ledger Entries according to your settings and
inserts them in the journal to proceed the payment transaction.
For more information, see Tasks, Suggest Payments.
Payment Suggestion List
Click on the action Payment Suggestion List to view the report. The payment suggestion
list displays all lines waiting for payment and a summary of the amounts, grouped by
bank account and message type.
Create Payment File
The action creates a payment file based on the lines in the journal.
For more information, see Tasks, Create Payment File.
Void Payment File
payment suggestion.
Note
The aggregation only takes place if the following fields are the same for the rows:
Payment type, Account Type, Account Number, External Bank Account Code,
Currency Code, Direct Debit Type, Direct Debit Sequence, Mandate ID, Date of
Mandate. Lines with payment reference are always exported separately.
With this action you can void a previously created payment file. The already exported file
can no longer be deleted by the application (has to be done manually), but the journal
lines can now be modified and you can create a new, corrected payment file.
Payment File Test Report
You can click on the action Payment File Test Report to check with preview whether all
required informations have been entered.
The report is especially helpful when you are making payments for the first time. You will
then see an overview of all missing details. However, you can also try to create the
payment file without this test report and correct any error messages manually.
Clearing Entries
When a payment file is created, an entry per file, with the status of the file is created in the
Clearing Entry table. This action opens the overview of these entries.
For more information, see History, Clearing Entries.
Print Clearing List
Runs a report that displays detailed information about the created payment file.
.
Payment Statistics
This action opens a page with information about the payment file. One line is printed for
each payment file created from the journal.
For more information, see Reports and Analysis, Payment Statistics.
Notification E-Mail Suggestion
The payment notification is useful to help the recipient to assign the payment(s). This is
particularly true in the case of a collective transfer. Once the payment file has been
created, you can send the payment notification by e-mail. Using the action Payment
Notification E-mail Suggestion, a suggestion is first created. This suggestion will not be
saved, but newly created each time you call the Payment Notification E-mail Suggestion.
For more information, see Tasks, Notification E-Mail Suggestion.
Print Notification
The payment notification is useful to help the recipient to assign the payment(s). This is
particularly true in the case of a collective transfer. Once the payment file has been
created, you can send the payment notification by e-mail. Using the action Payment
Notification E-mail Suggestion, a suggestion is first created. This suggestion will not be
saved, but newly created each time you call the Payment Notification E-mail Suggestion.
For more information, see Tasks, Notification E-Mail Suggestion.
Renumber Document Numbers
If you delete lines in the journal, gaps will occur in the document numbers. If this is a
problem, click on the action Renumber Document Numbers. The document number is
renumbered for all lines in the journal where neither Check Printed nor Payment File
Created is set.
Note
Document Numbers that have been used in other suggestions are not renumbered.
You start the Payment Suggestion in a Payment Journal. Depending on which suggestion you
start, the Vendor Payment Suggestion, Customer Payment Suggestion, or Employee Payment
Suggestion window opens.
The parameters define how the open entries are determined for the payment suggestion, how
they are grouped by customer, vendor, or employee, and which data is written to the journal
lines.
The following section describes the available parameters:
LastPaymentDateThe payment suggestion only considers entries whose due date is before or on
this date.
Only entries for which no value is entered in the field On Hold are taken into
account.
Find Payment
Discounts
Indicator that the payment discount date is taken into account when searching
for available payments. Instead of the field Last Due Date, the field Last Payment Discount Date is taken into account.
Last Payment
Discount Date
Indicator that the payment discount date is taken into account when searching
for possible payments.
Instead of the field Last Due Date, the field Last Cash Discount Date is taken
into account.
If the indicator Consider Payment Discount Tolerance is set, the payment is also
taken into account for the payment discount tolerance.
Last Payment
Discount Date
If the indicator Find Payment Discount is set, this field (and not the field Last Due Date) is taken into account for filtering by payment discount date. If the
field is empty, the field Last Due Date is used to find the items.
Use Vendor
Priority
Indicator that the Priority field on the vendor card determines the order in which
the vendor entries are suggested for payment.
This field is available only for payment suggestions in payment journals.
Payments are made until the amount in the field Available Amount (LCY) is
consumed.
Available Amount
(LCY)
Amount available for payments to vendors.
Payments to vendors are made (ranked according to vendor priority) until the
amount is used up.
Summarize Results:
Note
This field is only available for payment suggestions in payment journals.
SummerizeperVendorIndicator that the lines are summarized per vendor (and currency).
Summerize per
Customer
Indicator that the lines are summarized per customer (and currency).
By DimensionSelect the dimensions by which you want to group the payment
suggestions. It is possible for the same combination of
Customer/Vendor
Combination of Dimension Values
and Currency
to create a line.
Fill in Journal Lines:
Posting DateDate on which the payments are posted.
This field is transferred to the journal lines.
Consider Payment Discount
Tolerance
Indicator that the cash discount tolerance date of the individual entries
is also taken into account when the payment suggestion is created.
You can set the indicator Block Payment Tolerance on the vendor or
customer card to block the payment discount tolerance for specific
vendors/customers.
StartingDocumentNo.Document number for the first line of the payment suggestion.
NewDoc.No.perLineIndicates that the journal lines are numbered sequentially (starting
from the number in the field Starting Document No.).
Bal. Account TypeType of balancing account (G/L account, bank account).
Note
This field is only available for payment suggestions in payment journals.
Note
This field is only available for payment suggestions in cash receipt journals.
Note
This field is only available if the indicator Summerize per Vendor or
Summerize per Customer is set.
Note
If the indicator New Doc. No. per Line is not set, this number is
applied to every journal line.
Note
The value is taken from the settings for the journal and is predefined.
This field is applied to all journal lines.
Bal. Account No.Number of the balancing account to which the posting is to be
posted.
You can enter the account number or select from a drop down list.
Payment TypePayment type for the journal lines.
The following options are available:
Direct Debit Suggestion (only available in cash receipt journals)
Non-SEPA Credit Transfer
SEPA Credit Transfer
SEPA Direct Debit (only available in cash receipt journals)
.
If you select the option Credit Transfer Suggestion, the system will try
to create a credit transfer in the following order
SEPA Credit Transfer (if the rules of the external bank account
search apply (IBAN, country/region code, SWIFT code available)
and the company's bank account contains a SEPA credit transfer
scheme.
For more information, see Bank Account Setup.
Non-SEPA Credit Transfer if your bank account has a non-SEPA
credit transfer scheme.
If you choose the option Direct Debit Suggestion, the system searches
for existing transactions of the customer with this currency code. The
system tries to create a Direct Debit in the following order
SEPA Direct Debit (if the rules of the external bank account
search apply and the company's bank account contains a SEPA
Direct Debit Scheme.
For more information, see Bank Account Setup.
If a transaction is found, the payment type and the external bank
account code of the transaction are suggested. If no transaction is
found, the system tries to determine the external bank account and
payment type according to the rules of the external bank account
search.
The external bank account search, especially with the option Last Transaction/Main Bank Account, in combination with direct
debit/credit transfer suggestion, should provide the best results in
Note
The value is taken from the settings for the journal and is predefined.
This field is applied to all journal lines.
Note
If the field is empty, you must manually specify the payment type in
the journal for each line.
For the SEPA Credit Transfer and SEPA Direct Debit payment types,
only lines with the ISO currency code "blank" or "EUR" are included in
the payment suggestion.
In this filter pane, you can limit the results of the payment suggestion
by setting filters on the customer ledger entry/vendor ledger
entry/employee ledger entry tables. You can find further information
on this under Sorting, Searching, and Filtering
You can use a one-time statement to execute a bank transfer ad hoc without having to manage
vendors/customers and external bank accounts. In the Journals you can define per line if it is a
One-Time Transfer. To open the page One-Time Transfer click on the field One-Time Transfer
(if no one-time payment has been defined yet, the value of the field is No), the page opens and
you can set up the bank account for this transfer.
Field, External Bank Account
IBANSpecifies the bank account information of the customer/vendor/employee. Using
the External Bank Account Card action in the journal pages, you can now also
create a one-time payment transaction if no external bank account code is
specified..
SWIFT CodeSpecifies the bank account information of the customer/vendor/employee.
Bank Branch
No.
Specifies the Bank Branch No.
Bank NameSpecifies the name of the bank.
Bank AddressSpecifies the address of the bank.
Bank Address 2Specifies an addition to the address of the bank.
Using the action Suggest Data, the data of the last one-time transaction (with the same
account type/account number) can be suggested. The action only brings values if a
Payment File has already been created for the combination of account type and account
number. If, for example, a one-time payment transaction is defined for a line of the type
G/L account and a payment file is created, this data can be suggested for the same G/L
account in the next one-time payment transaction.
1. Click (in the journal) on the action Create Payment File.
In the page that opens, specify which lines are to be exported to the Payment File. Select
the required lines. Some of the data in the selected lines can still be changed when the
payment file is created:
Specify the Execution Date on which the bank should proceed the payments.
The fields Direct Debit Type and Execution Date One-Off/First Direct Debit can
only be changed for the payment type "SEPA Credit Transfer".
The field Charges can only be changed if the XML schema of the bank account
supports charges..
For more information, see XML-Schemas.
2. If you activate the checkbox Urgent payment, the execution date is set to the current
day. If Urgent Payment is not activated, the execution date is set to the following day. For
SEPA direct debits with the direct debit type "CORE - basic direct debit", the execution
date is set to the current day + 2 days.
3. Click on OK and confirm the message.
The payment file is created. The Payment Status field is automatically set to Created for all
lines exported to the payment file.
Transactions with the same currency codes, debit types, debit sequences and execution
date are combined in one file.
Note
When the Collective Transaction option is active in the NCPE Payment Export Setup window,
journal lines are summarized in the payment file. In this way, they can also perform the
collection of a credit memo. If an invoice with a higher absolute amount is to be cleared, the
credit memo can also be cleared in the collective transaction. However, the amounts are posted
separately in the payment journal.
For more information, see NCP Payments Export Setup.
Nachdem die Aktion Zahlungsdatei erstellen im Buch.-Blatt erfolgreich durchgeführt wurde
und eine Zahlungsdatei erstellt, öffnet sich die Seite Zahlungsdatei Zusammenfassung. Hier
erscheinen Informationen über die erstellte Zahlungsdatei, sie können auf einem Blick sehen mit
welchen Einstellungen und welchen Betrag die Datei erstellt wurde. Zusätzlich können sie auch
sehen, wieviele Avisos erstellt und ob die Avisos alle gedruckt bzw. gesendet wurden.
Felder
Lfd. Nr.Zeigt die Postennummer an, die dem Clearingposten zugeordnet wurde. Die
Anwendung ordnet jedem Clearingposten eine eindeutige Nummer zu.
ErstellungsdatumZeigt das Datum der Erstellung der Zahlungsdatei an
ZahlungsartZeigt die Zahlungsart der Zahlungsdatei an.
BankkontonummerZeigt die Bankkontonummer an, für welche die Zahlungsdatei erstellt wurde.
Dateireferenz
(Nachrichtenreferenz)
Zeigt die Referenz der Zahlungsdatei an.
BetragZeigt die Summe der Beträge aus den Zahlungsposten.
Betrag (MW)Zeigt die Summe der Beträge in Mandantenwährung aus den
Zahlungsposten.
Anzahl
Zahlungsposten
Anzahl aller Zahlungsposten die sich auf diesen Clearingposten beziehen.
Anzahl AvisAnzahl aller Avis E-Mails die sich auf diesen Clearingposten beziehen.
Avis nicht
gedruckt/gesendet
Anzahl aller gedruckten Avis die sich auf diesen Clearingposten beziehen.
Anzahl BankpostenAnzahl aller Bankposten die sich auf diesen Clearingposten beziehen.
Note
Die Referenz wird beim Erstellen der Zahlungsdatei aus dem aktuellen Datum
und der aktuellen Uhrzeit generiert.
Mit dieser Aktion können sie die zuvor erstellte Zahlungsdatei exportieren. Dies startet
den Download der Datei auf ihren Computer um sie dann in die Banksoftware ihrer Bank
zu importieren.
Zahlungsdatei annullieren
Mit dieser Aktion kann eine erstellte Zahlungsdatei annulliert werden. Der Status des
Zugehörigen Clearingposten wird auf annulliert gesetzt.
Zahlungsposten
Öffnet die Übersicht über die Zahlungsposten die zu diesem Clearingposten verweisen.
For more information, see Zahlungsposten.
Bankposten
Öffnet die Übersicht über die Bankposten die zu diesem Clearingposten verweisen.
For more information, see Bankposten.
Clearingliste
Mit dieser Liste erhalten sie Informationen zu dem erstellten Clearingposten.
Avis E-Mail Vorschlag
Diese Liste zeigt Informationen zum erstellten Zahlungsvorschlag bzw. zur aktuellen
Situation (Ausgleich usw.) im Buch.-Blatt an.
Avis
Der Avis ist hilfreich, um den Empfänger die Zuordnung der Zahlung(en) zu erleichtern.
Dies gilt insbesonders im Fall einer Sammelüberweisung. Es ist möglich, diese
Benachrichtigung per E-Mail zu senden. Nachdem die Zahlungsdatei erstellt wurde, kann
man den Avis drucken, oder per E-Mail verschicken.
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.
By default, a payment notification is created if the remittance info is longer than 140 characters.
In this case, a reference to the payment notification is written to the payment file.
The payment notification field is set automatically for the line.
Send Payment Notification E-Mail
To send a payment notification suggestion via e-mail, the following steps must be done:
1. Click on the action Notification E-Mail Suggestion - you will find the action in the
Payment File - Summary, which opens after creating the Payment File, in the journal or in
the Clearing Entries list.
2. Select the checkbox Include Accounts without Pmt. Notification E-Mail if you also want
to include customers and vendors without payment notification e-mail in the report.
3. Set the required filters.
4. Confirm your selection with OK.
5. In the window that opens, the data can still be checked and adjusted if necessary. If all
lines are correct, the selected payment notification can be sent using the action Send.
Alternatively, with Send All the e-mails can be sent to all proposal lines.
Print Payment Notification
To print the payment notification e-mail suggestion:
1. Click on the action Notification E-Mail Suggestion - you will find the action in the
Payment File - Summary, which opens after creating the Payment File, in the journal or in
the Clearing Entries list.
2. Select the checkbox Include Accounts without Pmt. Notification E-Mail if you also want
to include customers and vendors without payment notification e-mail in the report.
3. Set the required filters.
4. Click the Preview button to check the result of the filtering.
Click the Print button to print the report or save it to a file.
Note
In the NCP Payments Export Setup, you can specify that a payment notification should always
be created. You also define the payment notification texts in the setup.
For more information, see NCP Payments Export Setup.