Feedback|  Print Manual

NCP Payments



Manual


2021/03/05

Contents



General

Setup

    General

    • Bank Account Setup
    • Bank Codes
    • Customer Bank Account List
    • Vendor Bank Account List
    • Countries/Regions

    Export

    • Payment Export Setup Wizard
    • Payments Export Setup
    • XML Schemas
    • XML Schema Values
    • Language Setup
    • SEPA Mandates Text Lines
    • SEPA-Direct Debit-Mandates

    Import

    • Payment Import Setup Wizard
    • Payments Import Setup
    • Customs Formats
    • Importcodes
    • Fixed Account Allocations

Tasks

    Export

    • Working with Payments Export
    • Payment Journals
    • Make Payment Suggestions
    • Create Payment File
    • One-Time Transfer
    • Payment File Summary
    • Payment Notification E-Mail Suggestion

    Import

    • Working with Payments Import
    • Import Payment File
    • Applying Open Entries
    • Bank Account Reconciliation

Reports and Analysis

  • Payment Statistics
  • Importlist
  • Import Allocation Analysis
  • Import General Journal Deviation

Archive

  • Customer Ledger Entries
  • Vendor Ledger Entries
  • Employee Ledger Entries
  • Bank Account Ledger Entries
  • Clearing Entries
  • Payment Entries
  • Payment Remittance Entries
  • Payment Posting Entries
  • Import
  • Import Data
  • Import Balances
  • Import Transactions
  • Import Charges
  • Import Additional Infos
  • Import Remittance Infos

Appendix

  • Payments Export - Delete Data
  • Payments Import - Delete Data
  • Release Notes


General

Der NCP Payments consists of 2 modules and extends Dynamics 365 Business Central with the capability to create payment files for submitting to your bank and to import from your bank. The two modules NCPE Payments Export and NCPI Payments Import are available separately.

Export

NCPE Payments Export extends Dynamics 365 Business Central with the capability to create payment files for submitting to your bank. The module 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. Supported Formats:
  • Non-SEPA Credit Transfer
  • SEPA Credit Transfer
  • SEPA Direct Debit

Note

SEPA Direct Debit is only possible for customers.

Import

NCPI Payments Import extends Dynamics 365 Business Central with the functionality to import payment files from your bank. Supported Formats:
  • 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.

Navigation

NCPE Payments Export and NCPI Payments Import are integrated in the Accountant role and in the Accounting Manager role. Fields, actions, pages and reports originating from the NCPE Payments Export extension are identified by the abbreviation NCPE. NCPE stands for NAVAX Consulting Payments Export. Fields, actions, pages and reports originating from the NCPI Payments Import extension are identified by the abbreviation NCPI. NCPI stands for NAVAX Consulting Payments Import. This additional identification allows the windows and functions belonging to the NCP Payments to be clearly distinguished from the Dynamics 365 Business Central Standard Payments module and other extensions (which may use similar names and designations). The search terms "ncp", "ncpe" and "ncpi" are also recognized by "Tell me what you want to do". This allows very fast access to the individual areas of the NCP Payments.


Setup,
General,
Bank Account Setup

In the window NCP Payments Bank Account Setup, all bank accounts that are required for payment transactions are entered or managed here.

Fields

Bank Account No.Specifies the bank account number.
Bank Account NameShows the bank account number.
Bank Account Country-/RegioncodeView the country-/region code of the bank account.

Note

The field country/region code must be specified with the current bank account so that the account can be used for payment transactions.
Bank Account IBANShows the IBAN of the bank account.
SEPA Credit Transfer SchemaSpecifies which payments XML schema should be used for the SEPA credit transfer. For more information, see Setup, XML Schemas.
SEPA Direct Debit SchemaSpecifies the payment transaction XML Schema to be used for SEPA Direct Debit. For more information, see Setup, XML Schemas.
Non-SEPA Credit Transfer SchemaSpecifies the payment transaction XML schema to be used for the non-SEPA transfer. For more information, see Setup, XML Schemas.
Originator IDSpecifies the originator ID for the payment transaction XML schemas if required.

Note

Only fill the originator ID if it is permitted or required in the XML file after consultation your bank.
Originator ID IssuerSpecifies the issuer of the originator ID for the payment transaction XML schemas if required.

Note

Only specify the issuer of the originator ID if specification in the XML file is permitted or required after consultation your bank.
Charge Account No.Specifies the expense account for the direct transfer of expenses to a ledger sheet, or the indirect transfer to a ledger sheet via bank account reconciliation.

Action

  • Bank Account Card

    This action opens the Bank Account Card where you can specify the details for this bank account.
  • Clearing Entries

    Clearing Entries for the bank account are displayed here. When you create a payment file, a Clearing Entry is created for each record. For more information, see Archive, Clearing Entries.


Setup,
General,
Bank Codes

In the page NCP Payments 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.

Fields

SWIFT/BIC CodeSpecifies the SWIFT code of the bank.
BAnk Branch No.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 CodeSpecifies 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

Actions

  • Download

    This action starts the download of predefined Bank Codes which you need for the NCP payments export. These bank codes are imported from 3 different bank institutions, including the European Central Bank, the Austrian National Bank and the Deutsche Bundesbank. When you start the download, you will be asked from which bank institution the bank codes should be imported or if All should be imported from all institutions at the same time.
  • Download - Save as

    Use this action to save the downloaded file to a location on your computer without importing the changes into Business Central, you download the data directly from the respective bank institutions. The export of your bank codes is started using the action Export. This allows you to export the existing entries in the table Bank Codes to a XML file, which you can also edit manually at any time.
  • Import

    This action starts the import of existing bank codes from an XML file, these can be codes from older systems that you have already configured and exported using the export function.
  • Export

    Exports all bank codes from your database. This exported file can be used for import into other databases.


Setup,
General,
Customer Bank Account List

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 CodeSpecifies 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 Accountin this field, the bank account can be marked as main bank account.

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.
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.

Actions

  • Direct Debit Mandates

    View or edit the direct debit mandates. The direct debit mandates reflect your agreement with customers to collect invoice payments from their bank account.
  • Payment Entries

    All Payment Entries to this Bank Account are listed here.


Setup,
General,
Vendor Bank Account List

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 CodeSpecifies the country/region of the address.

Note

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 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 Accountin this field, the bank account can be marked as main bank 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.

Aktionen

  • Payment Entries

    All Payment Entries to this Bank Account are listed here.


Setup,
General,
Countries/Regions

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.

Fields

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.
ISO-CodeSpecifies 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 CodeSpecifies a three-digit code number defined in ISO 3166-1.
Address FormatSpecifies 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.

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.
Contact Adress FormatSpecifies where you want the contact name to appear in mailing addresses.
Intrastat CodeSpecifies an Intrastat Code for the country/region you are trading with. For more information, see Intrastat on Business Central online help.
VAT SchemeSpecifies the national body that issues the VAT registration number for the country/region in connection with electronic document sending.

Actions

  • Custom Address Format

    Define the scope and order for fields that make up the country/region address.
  • VAT Reg. No. Formats

    Specifies that the tax registration number for an account, such as customer, corresponds to the standard format for tax registration numbers in an account's country/region.


Setup,
Export,
Payments Export Setup Wizard

Before the NCPE Payments Export (NCPE Payments Export) 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.

Note

You can skip individual steps at any time and complete the configuration at a later time in the NCPE Payments Export Setup.

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.
Creditor Identifier (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.

Page, XML Schemas 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.

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 NCPE 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.

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.

Fields, Payment File Setup

Define here the necessary settings for the creation of the Payment File.
Create Bal. Account LineHere 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.
Sender NameHere 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.
HTML FormattedThis 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.

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

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 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 NCPE Payments Export Setup.


Setup,
Export,
Payments Export Setup

Before the NCPE Payments Export (NCPE Payments Export) 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 CalculationSpecifies 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 CalculationSpecifies 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 CalculationSpecifies 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 SearchSpecifies 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.

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.
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/Region CodeSpecifies 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.
Create Bal. Account LineHere 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. 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 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: %10<15>].
    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 NotificationSpecifies 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

    In the section Pmt. 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.
    HTML FormattedThis 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.

    Fields, Bank Codes Resources

    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.
    EZB Bank Codes URLSpecifies the URL for the download of the bankcodes from European Central Bank
    OENB Bank Codes URLSpecifies the URL for the download of the bankcodes from European Central Bank.
    DBB Bank Codes URLSpecifies the URL for the download of the bankcodes from German National Bank.
    For more information, see Setup, Bank Codes.

    Setup, Actions

    • Bank Accounts

      In the window NCP Payments Bank Account Setup, all bank accounts required for payment transactions are defined or managed. For more information, see Setup, Bank Account Setup.
    • Bank Codes

      In this window, the Bank 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 the creation of SEPA and non-SEPA files. The assignment of the schemes to the individual bank accounts can be done in the Payments Bank Account Setup. For more information, see Setup, XML Schemas.
    • Currencies

      Using this action the currencies can be set up.
    • Countries/Regions

      Using this action, countries/regions can be set up. For more information, see Setup, Countries/Regions.
    • Languages

      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, Languages.

    System, Fields

    License StatusDisplays the license status of the Extension.

    Important

    The trial version of an extension expires in 30 days. After that the functions of the extension can only be used with a valid license. Please note that the licensing process may take some time. The license can be requested or checked via the action What's New?. This opens a browser window. Click on Send License Request to send an E-Mail with your request. In the next few days you will receive an E-Mail with further information. As soon as the licensing has been completed, the license can be activated via the Update License action.

    Note

    The licence must be updated once a year via the Update License action. The update is only possible or necessary within the last 30 days before the license expires, or afterwards. Within the last 30 days before the license expires, notes are displayed.
    Serial No.Specifies the serial number of the Extension.
    VersionSpecifies the currently installed version of the Extension.
    Delete Data Date CalculationThis 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 deletedShows the date on which Payments Export - Delete Data were last executed.
    Archived Files deleted untilSpecifies the date until which archived files were deleted from the clearing entries.

    System, Actions

    • What's New?

      Via What's New? you have access to additional information, documents and resources of the Extension.
    • Update License

      Updates the License of the Extension or checks if it is up to date.
    • Version History

      Views the history, where you can see, which version of the Extension was installed.
    • 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.

      Note

      The files can no longer be exported.
      For more information, see Appendix, Payments Export - Delete Data.
    

    Setup,
    Export,
    Payments 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. 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 CodeSpecifies 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 possibleThe field IBAN Only possible indicates that the schema also supports transactions without the specification of SWIFT Code.
    Dom. IBAN OnlyThe 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 OnlyThe 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.
    IBAN or Bank Account No. possibleThe 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 possibleIndicates that the schema supports address information.
    Originator AddressThe 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 NCPE Payments Export Setup, should be written to the payment file.
    Recipient AddressThe 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 BookingSpecifies 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 SetSpecifies if the expanded character set should be activated.
    Charges Selection possibleIndicates that the schema allows the specification of charges.
    Urgent Payment possibleIndicates that the schema supports urgent payments.
    Date of SpecificationSpecifies the date of the specification.
    Last Date Modified (Schema Lines)Shows whether, and if so, when the schema lines were last changed.
    In UseIndicates that the scheme is in use.

    Actions

    • Download

      This action starts the download of predefined XML schemas which are required for the NCPE Payments Export. These XML schemas are constantly updated and provided.
    • Download - Save As

      Use this action to save the downloaded XML file to a location on your computer without importing the content into your Business Central. This can help you to do necessary modifications for your bank directly in this file before you import it into the database with the action Import.
    • Import

      This action starts the import of existing XML schemas from a XML file. These can be codes from older systems that you already have configured and exported using the export function.
    • Export

      Exports all XML schemas from your database. The exported file can be used for import into other databases.
    

    Setup,
    Export,
    XML Schema Values

    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 NCPE 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.
    

    Setup,
    Export,
    Languages

    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.

    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.

    Fields

    Language CodeSpecifies 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 NameViews the description for the language.
    Linked Language CodeUsing 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 ExistsViews 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.
    Pmt. Notification Payment File TextSpecifies 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.
    Pmt. Notification E-Mail SubjectSpecifies 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.

    Actions

    • Pmt. Notification E-Mail Text

      You can use this action to configure the texts in different languages for the payment notification e-mail messages.
    • SEPA Mandates Text

      With this action the mandate text lines can be defined in different languages. For more information, see Setup, SEPA Mandates Text Lines.
    

    Setup,
    Export,
    SEPA Mandate Text Lines

    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):
    Language CodeDirect Debit TypeDirect Debit Sequence
    of the customerof the mandateof the mandate
    of the customerof the mandate"All"
    of the customer"All"of the mandate
    of the customer"All""All"
    linked language codeof the mandateof the mandate
    linked language codeof the mandate"All"
    linked language code"All"of the mandate
    linked language code"All""All"
    without language codeof the mandateof the mandate
    without language codeof the mandate"All"
    without language codeof the mandateof the mandate
    without language codeof the mandate"All"

    Fields

    Direct Debit TypeSpecifies the direct debit type for which the text is valid.
    Direct Debit SequenceSpecifies the direct debit sequence for which the text is valid.
    TextSpecifies the text for the mandate.
    

    Setup,
    Export,
    Direct Debit Mandates

    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.

    Note

    SEPA direct debits can only be executed for documents with the currency EURO.
    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.

    Fields

    IDSpecifies the ID of the direct debit mandate.
    Direct Debit TypeSpecifies that the mandate is a CORE - basic direct debit, a B2B - company direct debit or a COR1 - basic direct debit with reduced processing time.
    Final DD CreatedSpecifies when the final direct debit was created for this mandate.
    First Direct Debit CreatedSpecifies that the first direct debit was created for this mandate.
    Mandate Form PrintedSpecifies 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 ExistsShows the number of payment entries (regardless of the direct debit sequence) for the mandate.
    Customer Bank Account CodeSpecifies customer bank account that the direct-debit mandate is activated for. The field is filled automatically.
    Date of SignatureSpecifies 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 the Valid To field has been exceeded.

    Actions

    • Print Mandate Form

      Use this action to print a form that you can then hand over to the customer. It is used to confirm the agreement with the customer to collect his payments within a certain period of time by signing it. For more information, see Direct Debit Mandate Form.
    

    Setup,
    Import,
    Payments Import Setup

    Before NCPI Payments Import (NCPI Payments Import) can be used, its basic functionality must be set up. In the window NCPI Payments Import Setup the general settings and defaults are defined.

    Note

    The import must be set up separately for each company.

    Note

    You can skip individual steps at any time and complete the configuration at a later time in the NCPE Payments Export Setup.

    Fields, Page Import Settings

    In the area Import you define which files are allowed for import and where the data should be transferred to.
    camt.052 - Account ReportSpecifies if and where the camt.052 - Account Report files can be imported and transferred The following options are available:
    • empty: no import possible, in the import selection dialog the option, camt.52 - Account Report, does not appear
    • Import Only: it is possible to import a camt.52 file, but not to transfer it to an journal or bank account reconciliation
    camt.53 - StatementIndicates whether, and if so, where the camt.053 - Statement files can be imported and transferred. The following options are available:
    • empty: no import possible, in the import selection dialog the option, camt.53 - Statement, does not appear.
    • Import Only: it is possible to import a camt.53 file, but not to transfer it to an journal or to the bank account reconciliation.
    • General Journal: it is possible to import a camt.53 file and transfer the imported lines to a General Journal.
    • Bank Acc. Reconciliation: the import of a camt.53 file is possible and the imported lines can be transferred to the bank account reconciliation
    camt.54 - Debit Credit NotificationSpecifies if and where the camt.054 - return data files can be imported and transferred. The following options are available:
    • empty: no import possible, in the import selection dialog the option, camt.54 - Debit Credit Notification, does not appear.
    • Import Only: it is possible to import a camt.54 file, but not to transfer it to an journal or to the bank account reconciliation.
    • General Journal: it is possible to import a camt.54 file and transfer the imported lines to a General Journal.
    CustomSpecifies if and where the Custom Files can be imported and transferred. The following options are available:
    • empty: no import possible, in the import selection dialog the option, Benutzerdefiniert, does not appear.
    • General Journal: the import of a custom file is possible and the imported lines can be transferred to a General Journal.
    For more information, see Setup, Custom Formats.
    Custom Formats ExistsShows if custom formats are available.
    Standard Import FileSpecifies which file type should be pre-selected during import.

    Note

    If no value is selected and the field remains empty, no value is preselected.

    Fields, Page Transfer Settings

    The section Transfer determines the field values in the Journal or the Bank Account Reconciliation. In addition, you can specify here whether Charges should also be transferred or considered.
    Trans. Posting DateSpecifies the value with which the entry date is to be filled when it is transferred to an general journal or to the bank account reconciliation. The following options are available:
    • Posting Date/Value Date (Import)
    • Value Date/Posting Date (Import)
    • Posting Date (Import)
    • Value Date (Import)
    • Workdate
    Trans. Document DateIndicates if and with what value the document date should be filled when it is transferred to an General Journal or to the Bank Account Reconciliation. The following options are available:
    • Posting Date/Value Date (Import)
    • Value Date/Posting Date (Import)
    • Posting Date (Import)
    • Value Date (Import)
    • Arbeitsdatum
    Trans. Document No.Specifies if the document number is to be filled in, and if so, with what value when it is transferred to an General Journal or to the Bank Account Reconciliation. The following options are available:
    • Statement No.
    Trans. External Document No.Specifies if the External Document No. should be filled, and if so, with which value when it is transferred to an General Journal or to the Bank Account Reconciliation. The following options are available:
    • Statement No.
    Trans. DescriptionSpecifies if the description is to be filled in, and if so, with which value when it is transferred to an General Journal or to the Bank Account Reconciliation. The following options are available:
    • Remittance Info.
    • Transaction Description
    • External Account Holder
    Trans. AmountSpecifies if the amount should be filled up with a value when it is transferred to an General Journal or to the Bank Account Reconciliation. The following options are available:
    • Order Amount/Transaction Amount: Initial amount, if available, otherwise transaction amount
    • Transaction Amount
    Trans. ChargesSpecifies if the expenses should also be transferred to the General Journal or to the Bank Account Reconciliation.
    Source Code from ImportShows the settings in the source code setup. You can click on the AssistEdit button and select an source code in the Trans. Payment Import to Gen. Jnl page.
    Source Code from Bank Acc. ReconciliationShows the settings in the origin code setup.

    Fields, Page Matching/Application Settings

    The setting in the section Matching/Application determine the behavior of the matching or application suggestion. For more information, see Tasks, Applying Open Entries.
    Document No. Alloc. AccuracyThis can have an impact on automatic assignment of the customer ledger entry. The following options are available:
    • Sharp (Identical Value) The system searches for the exact value of the document number of the customer ledger entry.
    • Fuzzy (Incl. values without special characters) The system first searches for the exact value of the customer ledger entry document number. If nothing is found, the system then searches for the document number without special characters.
    Fixed Account Allocations ExistsIndicates that fixed allocations to accounts exist.

    Note

    This indicator is set automatically if allocations exist.
    For more information, see Import Setup, Fixed Account Allocations.
    Show Analysis WindowSpecifies whether a window containing detailed information about the matching should pop up. If you close the window with OK, the suggestion is copied to the journal line or the bank account reconciliation.

    Note

    Use this indicator for information purposes only. To perform a application, this indicator must be deactivated.
    For more information, see Import Allocation Analysis.
    Matching Date Tolerance (Days)If you specify a value here, the automatic bank account reconciliation lines will only suggest bank account entries for which the posting date does not differ further from the transaction date.
    Check Application AmountSpecifies whether the action Import Suggest Application in the journal should only suggest open journal lines where the remaining amount matches the amount from the import. With the fields Application Tolerance % and Max. Application Tolerance Amount you can specify a tolerance for this check.
    Application Tolerance %Tolerance for the application in percent. The amount of the open entry can differ from the imported amount by the percentage in the field Application Tolerance %, but at most by the amount in the field Max. Application Tolerance Amount.

    Seite Import Codes Download

    The payments import codes are references to various types of transactions. Depending on the imported file format, different code fields are filled in.\nBy default, the table of import codes is empty. You can import the latest import codes via download or import codes from a file. Using the action Download import codes... the codes and their description can be downloaded or updated. For more information, see Import Setup, Import Codes.

    Finish setup

    If you click on Finish the settings will be saved in the table NCPE Payments Export Setup.
    

    Setup,
    Import,
    Payments Import Setup

    Before NCPI Payments Import (NCPI Payments Import) can be used, its basic functionality must be set up. In the window NCPI Payments Import Setup the general settings and defaults are defined.

    Fields, Import

    In the area Import you define which files are allowed for import and where the data should be transferred to.
    camt.052 - Account ReportSpecifies if and where the camt.052 - Account Report files can be imported and transferred The following options are available:
    • empty: no import possible, in the import selection dialog the option, camt.52 - Account Report, does not appear
    • Import Only: it is possible to import a camt.52 file, but not to transfer it to an journal or bank account reconciliation
    camt.53 - StatementIndicates whether, and if so, where the camt.053 - Statement files can be imported and transferred. The following options are available:
    • empty: no import possible, in the import selection dialog the option, camt.53 - Statement, does not appear.
    • Import Only: it is possible to import a camt.53 file, but not to transfer it to an journal or to the bank account reconciliation.
    • General Journal: it is possible to import a camt.53 file and transfer the imported lines to a General Journal.
    • Bank Acc. Reconciliation: the import of a camt.53 file is possible and the imported lines can be transferred to the bank account reconciliation
    camt.54 - Debit Credit NotificationSpecifies if and where the camt.054 - return data files can be imported and transferred. The following options are available:
    • empty: no import possible, in the import selection dialog the option, camt.54 - Debit Credit Notification, does not appear.
    • Import Only: it is possible to import a camt.54 file, but not to transfer it to an journal or to the bank account reconciliation.
    • General Journal: it is possible to import a camt.54 file and transfer the imported lines to a General Journal.
    CustomSpecifies if and where the Custom Files can be imported and transferred. The following options are available:
    • empty: no import possible, in the import selection dialog the option, Benutzerdefiniert, does not appear.
    • General Journal: the import of a custom file is possible and the imported lines can be transferred to a General Journal.
    For more information, see Setup, Custom Formats.
    Custom Formats ExistsShows if custom formats are available.
    Standard Import FileSpecifies which file type should be pre-selected during import.

    Note

    If no value is selected and the field remains empty, no value is preselected.

    Fields, Transfer

    The section Transfer determines the field values in the Journal or the Bank Account Reconciliation. In addition, you can specify here whether Charges should also be transferred or considered.
    Trans. Posting DateSpecifies the value with which the entry date is to be filled when it is transferred to an general journal or to the bank account reconciliation. The following options are available:
    • Posting Date/Value Date (Import)
    • Value Date/Posting Date (Import)
    • Posting Date (Import)
    • Value Date (Import)
    • Workdate
    Trans. Document DateIndicates if and with what value the document date should be filled when it is transferred to an General Journal or to the Bank Account Reconciliation. The following options are available:
    • Posting Date/Value Date (Import)
    • Value Date/Posting Date (Import)
    • Posting Date (Import)
    • Value Date (Import)
    • Arbeitsdatum
    Trans. Document No.Specifies if the document number is to be filled in, and if so, with what value when it is transferred to an General Journal or to the Bank Account Reconciliation. The following options are available:
    • Statement No.
    Trans. External Document No.Specifies if the External Document No. should be filled, and if so, with which value when it is transferred to an General Journal or to the Bank Account Reconciliation. The following options are available:
    • Statement No.
    Trans. DescriptionSpecifies if the description is to be filled in, and if so, with which value when it is transferred to an General Journal or to the Bank Account Reconciliation. The following options are available:
    • Remittance Info.
    • Transaction Description
    • External Account Holder
    Trans. AmountSpecifies if the amount should be filled up with a value when it is transferred to an General Journal or to the Bank Account Reconciliation. The following options are available:
    • Order Amount/Transaction Amount: Initial amount, if available, otherwise transaction amount
    • Transaction Amount
    Trans. ChargesSpecifies if the expenses should also be transferred to the General Journal or to the Bank Account Reconciliation.
    Source Code from ImportShows the settings in the source code setup. You can click on the AssistEdit button and select an source code in the Trans. Payment Import to Gen. Jnl page.
    Source Code from Bank Acc. ReconciliationShows the settings in the origin code setup.

    Fields, Matching/Application

    The setting in the section Matching/Application determine the behavior of the matching or application suggestion. For more information, see Tasks, Applying Open Entries.
    Document No. Alloc. AccuracyThis can have an impact on automatic assignment of the customer ledger entry. The following options are available:
    • Sharp (Identical Value) The system searches for the exact value of the document number of the customer ledger entry.
    • Fuzzy (Incl. values without special characters) The system first searches for the exact value of the customer ledger entry document number. If nothing is found, the system then searches for the document number without special characters.
    Fixed Account Allocations ExistsIndicates that fixed allocations to accounts exist.

    Note

    This indicator is set automatically if allocations exist.
    For more information, see Import Setup, Fixed Account Allocations.
    Show Analysis WindowSpecifies whether a window containing detailed information about the matching should pop up. If you close the window with OK, the suggestion is copied to the journal line or the bank account reconciliation.

    Note

    Use this indicator for information purposes only. To perform a application, this indicator must be deactivated.
    For more information, see Import Allocation Analysis.
    Matching Date Tolerance (Days)If you specify a value here, the automatic bank account reconciliation lines will only suggest bank account entries for which the posting date does not differ further from the transaction date.
    Check Application AmountSpecifies whether the action Import Suggest Application in the journal should only suggest open journal lines where the remaining amount matches the amount from the import. With the fields Application Tolerance % and Max. Application Tolerance Amount you can specify a tolerance for this check.
    Application Tolerance %Tolerance for the application in percent. The amount of the open entry can differ from the imported amount by the percentage in the field Application Tolerance %, but at most by the amount in the field Max. Application Tolerance Amount.

    Setup, Actions

    • Bank Accounts

      In the window NCP Payments Bank Account Setup all bank accounts that are required for payment transactions are stored or managed. For more information, see General Setup, Bank Account Setup.
    • Import Codes

      Using this action, the window Payments Import Codes can be opened. When a file is imported, different code fields are filled, depending on the imported file format. Here you can enter a more detailed description for these code fields. Using the action Download the codes and their description can be downloaded or updated. For more information, see Import Setup, Import Codes.
    • Currencies

      By using the action the currencies can be set up.
    • Countries/Regions

      By using this action the countries/regions can be set up. For more information, see General Setup, Countries/Regions.

    System, Fields

    License StatusDisplays the license status of the Extension.

    Important

    The trial version of an extension expires in 30 days. After that the functions of the extension can only be used with a valid license. Please note that the licensing process may take some time. The license can be requested or checked via the action What's New?. This opens a browser window. Click on Send License Request to send an E-Mail with your request. In the next few days you will receive an E-Mail with further information. As soon as the licensing has been completed, the license can be activated via the Update License action.

    Note

    The licence must be updated once a year via the Update License action. The update is only possible or necessary within the last 30 days before the license expires, or afterwards. Within the last 30 days before the license expires, notes are displayed.
    Serial No.Specifies the serial number of the Extension.
    VersionSpecifies the currently installed version of the Extension.
    Delete Data Date CalculationThis 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 deletedShows the date on which Payments Export - Delete Data were last executed.
    Archived Files deleted untilSpecifies the date until which archived files were deleted from the clearing entries.

    System, Actions

    • What's New?

      Via What's New? you have access to additional information, documents and resources of the Extension.
    • Update License

      Updates the License of the Extension or checks if it is up to date.
    • Version History

      Views the history, where you can see, which version of the Extension was installed.
    • 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.

      Note

      The files can no longer be exported.
      For more information, see Appendix, Payments Import - Delete Data.
    

    Setup,
    Import,
    Payments Import - Custom Formats

    You can define a special format for the payment file if the existing standard formats do not meet the requirements of your bank. In the setup (Payments Import Setup) you define what user-defined formats can be used for. During import (Import Payment File) you can then select the option Custom Format.

    Fields

    CodeSpecifies the code for the custom format.
    DescriptionSpecifies a description for the custom format.
    ActiveSpecifies whether the custom format is completely set up and active. Only active formats can be used in payments import.
    Bank Account No.Specifies the bank account number for whom the format is valid.
    Bank Account NameShows the bank account name.

    Note

    This field is filled in automatically if you enter the Bank Account No..
    Bank Account IBANShows the bank account IBAN.

    Note

    This field is filled in automatically if you enter the Bank Account Number.
    SeparatorSpecifies the separator symbol for the fields.
    Start DelimiterSpecifies the start delimiter for the fields.
    End DelimiterSpecifies the end character for the fields.
    Decimal SeparatorSpecifies the decimal separator for the fields.
    No. of FieldsShows the number of existing fields for this format.

    Note

    If you click in the field you will open the page Payments Import Custom Format Fields. For more information, see Payments Import Custom Format Fields.
    No. of Assigned Import FieldsShows the number of assigned import fields for this format.

    Note

    If you click in the field you will open the page Payments Import Custom Format Fields. For more information, see Payments Import Custom Format Fields.
    File StructureShows the file structure with the separators of the import format.

    Actions

    • Fields

      Shows the list of the configured fields of the custom format, you can make the settings regarding the fields here.
    • Suggest Fields

      With the function Suggest fields, the fields can be automatically read or suggested from the CSV file (header line). Each field in the file that is to be imported into the payments import must then be assigned to a field number of the import.

    Actions, Setup

    • Import

      This action imports a file with a user defined format in CSV format. The file must start with a header line containing the field names. A row or record cannot be longer than 1024 characters. After creating a format and setting up the separators used in the CSV file, the fields of the file and their assignment to the payments import can be set up.
    • Export

      Use this action to export a custom format to a file.
    

    Setup,
    Import,
    Import Codes

    The Payments Import Codes are references to various types of transactions. Different code fields are filled depending on the imported file format. The table of Import Codes is empty by default. You can import the latest Import Codes via download or import the codes from a file.
    1. Go to NCP Payments > Setup > Import Setup > Setup > Import Codes.
    2. You have the following options:
      • Click on Download to download the latest import codes.
      • Click Import to import the file NCP1600_ImportCodes.xml
      • Click Export to export all records to one file. (You do not have the option to select individual records only).
    3. If import codes already exist, you can choose (during download and import) to create new records only or to overwrite existing records as well. After the download/import the import codes are displayed:

    Fields

    TypeSpecifies the type of the code. The following options are available:
    • SWIFT Transaction
    • Transaction
    • Domain Transaction
    • Family Transaction
    • Sub-Family Transaction
    • Return Reason
    CodeSpecifies a code for the import code. The code must be unique - a code may not be used twice in a table. You can set up as many import codes as you like.
    DescriptionDescription of the import code.

    Actions

    • Download

      The Download action can be used to download or update the codes.
    • Download - Save as

      With the action Download - Save as the codes can be downloaded and saved. No changes in the database will be made.
    • Import

      Using the Import action, the codes can be imported from a file.
    • Export

      Using the Export action, the codes can be exported to a file.
    

    Setup,
    Import,
    Fixed Account Allocations

    If a bank account is determined when importing a payment file (Import Payment File), the system first checks whether fixed account allocations exist. If there are any, this bank account is used.

    Fields

    Search Order No.Specifies the priority for the search.
    Search forSpecifies the value being searched for.
    Search inSpecifies the area in the import where the search for value is located or where to search.
    Account TypeSpecifies the account type.
    Account No.Specifies the account number.
    

    Tasks,
    Export,
    Work with Payments Export

    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.

    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.
    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.
      2. Click on OK and 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.
    • Payment Posting 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.
    

    Tasks,
    Export,
    Zlg.-Eing. Buch. und Zlg.-Ausg. Buch.-Blätter

    Die Beschreibung auf dieser Hilfe Seite gilt für das Zlg.-Eing. Buch.- und das Zlg.-Ausg. Buch.-Blatt.

    Felder

    Die Tabelle enthält folgende Felder bzw. Spalten:
    BuchungsdatumDatum mit dem die Zahlung gebucht wird.

    Note

    Bitte beachten – es kann, muss aber nicht das Datum sein, AN DEM die Zahlung gebucht wird.

    Note

    Dieses Feld wird aus dem Zahlungsvorschlag übernommen, es wird auch bei der Ermittlung des Skontos berücksichtigt.
    Belegnr.Die Belegnummern werden durch den Zahlungsvorschlag aufsteigend nummeriert. Wenn im Zahlungsvorschlag eine Start von Belegnr. gesetzt ist, wird diese für die erste Buchungszeile verwendet.
    Externe BelegnummerGibt eine zweite Belegnummer an. Diese bezieht sich meist auf das vom Debitor bzw. Kreditor verwendete Nummerierungssystem.
    KontoartGibt die Kontoart des Feldes Kontonr. an. Folgende Optionen sind verfügbar:
    • Sachkonto
    • Debitor
    • Kreditor
    • Bankkonto
    • Anlage
    • IC-Partner
    • Mitarbeiter

    Note

    Wenn sie das Buch.-Blatt mittels Zahlungsvorschlag befüllen dann kommen in der Kontoart nur Debitor und Kreditor oder Mitarbeiter vor.
    Kontonr.Gibt die Kontonummer an, auf die der Posten der Buch.-Blattzeile gebucht wird.

    Note

    Dieses Feld wird durch den Zahlungsvorschlag gefüllt.
    BeschreibungGibt die Beschreibung des Postens an.

    Note

    Dieses Feld wird durch den Zahlungsvorschlag gefüllt.
    WährungscodeGibt den Währungscode für die Beträge in der Buch.-Blattzeile an.
    ZahlungsformcodeGibt an, wie die Zahlung erfolgen soll, z. B. per Überweisung, Bargeld oder Scheck.
    BetragGibt den Gesamtbetrag (inkl. MwSt.) für die Buch.-Blattzeile an.
    Betrag (MW)Gibt den Gesamtbetrag (inkl. MwSt.) in Mandantenwährung für die Buch.-Blattzeile an.
    GegenkontoartArt des Gegenkontos (Sachkonto, Bankkonto).

    Note

    Dieses Feld wird vom Zahlungsvorschlag gefüllt.
    Gegenkontonr.Nummer des Gegenkontos auf das gebucht werden soll.

    Note

    Dieses Feld wird vom Zahlungsvorschlag gefüllt.
    Ausgeglichen (Ja/Nein)Gibt an, ob die Zahlung ausgeglichen wurde.
    Ausgleich mit BelegartGibt die Art des gebuchten Belegs an, mit dem dieser Beleg oder die Buch.-Blattzeile beim Buchen ausgeglichen wird, z. B. zum Registrieren der Zahlung.
    Ausgleich mit Belegnr.Gibt die Nummer des gebuchten Belegs an, mit dem dieser Beleg oder die Buch.-Blattzeile beim Buchen ausgeglichen wird.
    Fälligkeitsdatum für Ausgleich mit BelegGibt das Fälligkeitsdatum aus dem Beleg von Ausgleich mit Belegnr. an.
    ZahlungsartArt der Zahlung. Folgende Optionen stehen zur Verfügung:
    • Non-SEPA Überweisung
    • SEPA-Überweisung
    • SEPA-Lastschrift

    Note

    Das Feld Zahlungsart kann bereits durch den Zahlungsvorschlag befüllt werden. Sie können bei einer Standardeinrichtung den Inhalt nur ändern, solange das Kennzeichen Zahlung erstellt nicht gesetzt ist.
    Externer BankkontocodeIn dieses Feld wird automatisch das einzige bzw. das Hauptbankkonto des Debitors bzw. Kreditors geschrieben.

    Note

    Sie können hier das gewählte Konto ändern bzw. nachträglich ein Konto wählen.
    Mandat IDMandats-ID für die betreffende Transaktion.

    Note

    Dieses Feld ist nur im Zlg.-Eing.Buch.-Blatt verfügbar.
    LastschriftartArt des Einzugs, mit der die Transaktion durchgeführt wurde.

    Note

    Dieses Feld ist nur im Zlg.-Eing.Buch.-Blatt verfügbar. In dieses Feld wird automatisch der Wert des Mandats im Feld Mandat ID übernommen.
    LastschriftsequenzLastschriftsequenz Optionen:
    • Einmalig
    • Wiederkehrend
    • Erster
    • Letzter

    Note

    Dieses Feld ist nur im Zlg.-Eing.Buch.-Blatt verfügbar. In dieses Feld wird automatisch der Wert des Mandats übernommen.
    Urspr. LastschriftsequenzDas Feld Urspr. Lastschriftsequenz wird befüllt, wenn sich die Sequenz durch die Dateierstellung automatisch ändert. Wird die Transaktion annulliert, wird die Lastschriftsequenz wieder zurückgesetzt.

    Note

    Dieses Feld ist nur im Zlg.-Eing.Buch.-Blatt verfügbar. In dieses Feld wird automatisch der Wert des Mandats übernommen.
    Mandat erteilt amDieses Feld wird bei der Eingabe des Feldes Externer Bankkontocode bzw. über den Zahlungsvorschlag befüllt und kann im Buch.-Blatt bei Bedarf geändert werden. Die Vorbelegung erfolgt aufgrund des Feldes SEPA Mandat erteilt am aus der Debitoren Bankkontokarte.

    Note

    Dieses Feld ist nur im Zlg.-Eing.Buch.-Blatt verfügbar.
    ZahlungsreferenzZahlungsreferenz des Kreditors (im Ausgangsbuchblatt) bzw. des Debitors (im Eingangsbuchblatt).
    EinmalanweisungKennzeichen für eine Einmalanweisung.

    Note

    Dieses Feld wird automatisch befüllt, wenn eine Einmalüberweisung eingerichtet wird.
    For more information, see Einmalanweisung.
    ZahlungsstatusWenn die Datei bereits erstellt wurde, wird dieses Feld automatisch mit der Option Datei erstellt befüllt.
    Anzahl ZahlungspostenAnzahl der Zahlungsposten dieser Zeile.
    DurchführungsdatumDatum, an dem die Zahlung durchgeführt wird.
    AvisWenn für die Zeile ein Avis vorhanden ist, wird das Feld automatisch mit der Option "Ja" befüllt. For more information, see Avis erstellen.
    Avisnr.Die Nummer des Avis. Diese Nummer wird aus einer Nummernserie die sie in der NCPE Zahlungsverkehr Export Einrichtung im Feld Avisnummern eingerichtet haben entnommen. For more information, see NCPE Zahlungsverkehr Export Einrichtung - Zahlungsdatei erstellen.
    Avis gedrucktKennzeichen, dass das Avis bereits gedruckt wurde.

    Note

    Dieses Kennzeichen wird automatisch gesetzt wenn sie nach dem Erstellen der Zahlungsdatei den Avis E-Mail Vorschlag ausführen und die Avis drucken.
    Avis E-Mail gesendetKennzeichen, dass das Avis bereits versendet wurde.

    Note

    Dieses Kennzeichen wird automatisch gesetzt wenn sie nach dem Erstellen der Zahlungsdatei den Avis E-Mail Vorschlag ausführen und die Avis E-Mails versenden.
    BankkontozahlungsartBankkontozahlungsart für die Erstellung eines Schecks.

    Note

    Dieses Feld ist nur im Zlg.-Ausg.Buch-Blatt verfügbar. Dieses Feld wird aus dem Zahlungsvorschlag übernommen.
    StornoGibt den Posten als Stornoposten an. Dies bewirkt lediglich, dass der Posten auf diversen Auswertungen auf der „falschen“ Seite mit negativem Vorzeichen angezeigt wird.
    Sammeltransaktionsnr.Dieses Feld ist standardmäßig ausgeblendet. Wenn das Kennzeichen Sammeltransaktion in der Zahlungsverkehr Export Einrichtung nicht gesetzt ist (For more information, see Zahlungsverkehr Export Einrichtung.), werden Sammeltransaktionen nicht durchgeführt. Zeilen mit derselben Sammeltransaktionsnr. werden trotzdem zusammengefasst.

    Note

    Die Zusammenfassung erfolgt nur, wenn bei den Zeilen folgende Felder gleich sind: Zahlungsart, Kontoart, Kontonummer, Externer Bankkontocode, Währungscode, Lastschriftart, Lastschriftsequenz, Mandat ID, Mandat erteilt am. Zeilen mit Zahlungsreferenz werden immer einzeln exportiert.

    Aktionen

    • Kreditoren Zahlungsvorschlag

      Diese Aktion ermittelt offene Kreditorenposten laut ihren Vorgaben und stellt sie in das Buch.-Blatt, um den Zahlungsverkehr durchzuführen. For more information, see Aufgaben, Zahlungsvorschlag.
    • Debitoren Zahlungsvorschlag

      Diese Aktion ermittelt offene Debitorenposten laut ihren Vorgaben und stellt sie in das Buch.-Blatt, um den Zahlungsverkehr durchzuführen. For more information, see Aufgaben, Zahlungsvorschlag.
    • Mitarbeiter Zahlungsvorschlag

      Diese Aktion ermittelt offene Mitarbeiterposten laut ihren Vorgaben und stellt sie in das Buch.-Blatt, um den Zahlungsverkehr durchzuführen. For more information, see Aufgaben, Zahlungsvorschlag.
    • Zahlungsvorschlagsliste

      Klicken Sie auf die Aktion Zahlungsvorschlagsliste, um den Bericht anzuzeigen. Die Zahlungsvorschlagsliste zeigt, alle zur Zahlung anstehenden Zeilen und eine Zusammenfassung der Beträge, gruppiert nach Bankkonto und Nachrichtenart.
    • Zahlungsdatei erstellen

      Die Aktion erstellt eine Zahlungsdatei basierend auf den Zeilen im Buch.-Blatt. For more information, see Aufgaben, Zahlungsdatei erstellen.
    • Zahlungsdatei annullieren

      Mit dieser Aktion können sie eine zuvor erstellte Zahlungsdatei wieder annullieren. Die bereits exportierte Datei kann von der Anwendung zwar nicht mehr gelöscht werden (muss manuell durchgeführt werden), aber die Buch.-Blattzeilen können nun korrigiert werden und sie können eine korrigierte Zahlungsdatei erstellen.
    • Zahlungsdatei Testbericht

      Sie können auf die Aktion Zahlungsdatei Testbericht klicken um mit der Vorschau zu überprüfen, ob alle erforderlichen Angaben vorhanden sind. Der Bericht ist vor allem dann hilfreich, wenn sie die Zahlungen erstmals durchführen. Sie sehen dann alle fehlenden Einrichtungen im Überblick. Sie können aber auch versuchen, die Zahlungsdatei ohne diesen Testbericht zu erstellen und eventuell auftretende Fehlermeldungen einzeln zu beheben.
    • Clearingposten

      Wenn eine Zahlungsdatei erstellt wird, dann wird in der Tabelle Clearingposten pro Datei ein Eintrag mit dem Status der Datei erstellt. Mit dieser Aktion öffnen sie die Übersicht dieser Posten. For more information, see Historie, Clearingposten.
    • Clearingliste drucken

      Startet einen Bericht, der detaillierte Informationen zur erstellten Datei ausgibt.
    • Zahlungsstatistik

      Mit dieser Aktion wird eine Seite mit Informationen zur Zahlungsdatei geöffnet. Hier wird pro Zahlungsdatei, die aus dem Buch.-Blatt heraus erstellt wurde, eine Zeile angezeigt. For more information, see Berichte und Analysen, Zahlungsstatistik.
    • Avis E-Mail Vorschlag

      Der Avis ist hilfreich, um, dem Empfänger die Zuordnung der Zahlung (en) zu erleichtern. Dies gilt vor allem im Fall einer Sammelüberweisung. Nachdem die Zahlungsdatei erstellt wurde, können sie das Avis per E-Mail verschicken. Über die Aktion Avis E-Mail Vorschlag wird zuerst ein Vorschlag erstellt. Dieser Vorschlag wird nicht gespeichert, sondern bei jedem Aufruf von Avis E-Mail Vorschlag neu generiert. For more information, see Aufgaben, Avis E-Mail Vorschlag.
    • Avis drucken

      Der Avis ist hilfreich, um dem Empfänger die Zuordnung der Zahlung(en) zu erleichtern. Dies gilt vor allem im Fall einer Sammelüberweisung. Nachdem die Zahlungsdatei erstellt wurde, können sie das Avis drucken. Über die Aktion Avis drucken wird ein Bericht zum Ausdrucken des Avis gestartet. For more information, see Aufgaben, Avis E-Mail Vorschlag.
    • Belegnummern neu nummerieren

      Wenn Sie im Buch.-Blatt Zeilen löschen, entstehen Lücken bei den Belegnummern. Wenn sie dies stört, klicken sie auf die Aktion Belegnummern neu nummerieren. Bei allen Zeilen des Buch.-Blatts, bei denen weder Scheck gedruckt noch Zahlungsdatei erstellt gesetzt ist, wird die Belegnummer neu vergeben.

      Note

      Belegnummern, die in anderen Vorschlägen verwendet wurden, werden dabei nicht erneut vergeben.
    

    Tasks,
    Export,
    Making Payment Suggestions

    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:

    Find Payments:

    .
    Last Payment DateThe 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 DiscountsIndicator 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 DateIndicator 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 DateIf 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 PriorityIndicator 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.

    Note

    This field is only available for payment suggestions in payment journals.
    Payments to vendors are made (ranked according to vendor priority) until the amount is used up.

    Summarize Results:

    Summerize per VendorIndicator that the lines are summarized per vendor (and currency).

    Note

    This field is only available for payment suggestions in payment journals.
    Summerize per CustomerIndicator that the lines are summarized per customer (and currency).

    Note

    This field is only available for payment suggestions in cash receipt journals.
    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.

    Note

    This field is only available if the indicator Summerize per Vendor or Summerize per Customer is set.

    Fill in Journal Lines:

    Posting DateDate on which the payments are posted. This field is transferred to the journal lines.
    Consider Payment Discount ToleranceIndicator 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.
    Starting Document No.Document number for the first line of the payment suggestion.

    Note

    If the indicator New Doc. No. per Line is not set, this number is applied to every journal line.
    New Doc. No. per LineIndicates 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

    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.

    Note

    The value is taken from the settings for the journal and is predefined. This field is applied to all journal lines.
    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)

    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.
    . 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 most cases. For more information, see NCPE Payments Export Setup.
    Foreign Currency FilterIndicator that the filter is applied to items with ISO currency codes other than 'blank' or 'EUR'.
    Without ReductionsIndicator that entries that would reduce the amount (credit memos, refunds) are not included in the payment suggestion.
    Customer/Vendor/EmployeeIn this filter pane, you can limit the results of the payment suggestion by setting filters on the customer/vendor/employee tables. You can find further information on this under Sorting, Searching, and Filtering
    Customer Ledger Entry/Vendor Ledger Entry/Employee Ledger EntryIn 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
    

    Tasks,
    Export,
    Creating Payment Files

    To create a Payment File go through these steps:
    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 NCPE Payments Export Setup.
    

    Tasks,
    Export,
    One-Time Transfer

    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.
    Bank Post Code CodeSpecifies the post code of the bank.
    Bank CitySpecifies the city of the bank.
    Bank Country/Region CodeSpecifies the country/region code of the bank.

    Fields, Recipient Data

    Recipient NameSpecifies the name of the recipient.

    Note

    If nothing is specified, the data from vendor/customer/employee will be written to the payment file.
    Recipient Name 2Specifies an addition to the name of the recipient.

    Note

    If nothing is specified, the data from vendor/customer/employee will be written to the payment file.
    Recipient AddressSpecifies the address of the recipient.

    Note

    If nothing is specified, the data from vendor/customer/employee will be written to the payment file.
    Recipient Address 2Specifies an addition to the address of the recipient.

    Note

    If nothing is specified, the data from vendor/customer/employee will be written to the payment file.
    Recipient Post CodeSpezifies the post code of the recipient.

    Note

    If nothing is specified, the data from vendor/customer/employee will be written to the payment file.
    Recipient CitySpecifies the city of the recipient.

    Note

    If nothing is specified, the data from vendor/customer/employee will be written to the payment file.
    Recipient Country/Region CodeSpecifies the country/region code of the recipient.

    Note

    If nothing is specified, the data from vendor/customer/employee will be written to the payment file.

    Actions

    • Suggest Data

      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.
    

    Tasks,
    Export,
    Payment File Summary

    After the action Create Payment File in the Journal has been successfully completed and a Payment File is created, the page Payment File Summary opens. Here, you can see, information about the created payment file, you can see at a glance which settings used and the amount for which the file was created. In addition, you can also see how many payment notifications have been created and whether the payment notifications have all been printed or sent.

    Fields

    Entry No.Views the entry number assigned to the clearing entry.
    Creation DateViews the date when the payment file was created.
    Payment TypeViews the payment type of the payment file.
    Bank Account No.Views the bank account number for which the payment file was created.
    File Reference (Message Reference)Views the reference of the payment file.

    Note

    The reference is generated from the current date and time when the payment file is created.
    AmountViews the total of the amounts from all payment items.
    Amount (LCY)Views the total of the amounts, in local currency, from all payment items.
    No. of Payment EntriesViews the number of payment entries relating to this clearing entry.
    No. of Pmt. NotificationsViews the Number of notifications relating to this clearing entry.
    Pmt. Notifications not Printed/SentViews the Number of printed notifications relating to this clearing entry.
    No. of Bank Account EntriesViews the Number of bank account entries relating to this clearing entry.

    Actions

    • Export Payment File

      With this action you can export the already created payment file. This will start the download of the file to your computer to import it into the banking software of your bank.
    • Void Payment File

      With this action a created Payment File can be voided. The status of the related Clearing Entry is set to Voided.
    • Payment Entries

      Opens the overview of the Payment Entries that refer to this Clearing Entry. For more information, see Payment Entries.
    • Bank Account Ledger Entries

      Opens the overview of the Bank Account Ledger Entries that refer to this Clearing Entry. For more information, see Bank Account Ledger Entries.
    • Clearing List

      This list gives you information about the created Clearing Entry.
    • Suggest E-Mail Notifications

      This list provides information about the created Payment Suggestion or the current situation (clearing etc.) in the journal.
    • Notification

      A payment notification is useful (especially for collective transfers) to make it easier for the recipient to identify the payments. After the Payment File has been created, you can print the Notification or send it by e-mail.
    

    Tasks,
    Export,
    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. 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.

    Note

    In the NCPE 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 NCPE Payments Export Setup.

    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.
    

    Tasks,
    Import,
    Working with Payments Import

    With this module you can import and process payment files provided by your bank. The following formats are supported:
    • camt.52
    • camt.53
    • camt.54
    • Custom

    Data Structure

    Each row in the window NCPI Payments Import can contain several Data entries, which in turn can contain several Transactions. The transactions, in turn, can contain several Remittance Infos. and Charges. Depending on the imported file format, different fields are filled or used. During the transfer, for each NCPI Payments Import Transaction a corresponding entry is created in the Journal or in the Bank Account Reconciliation. If the field Trans. Charges in the Payments Import Setup is set to Yes, a line is also created in the Journal or in the Bank Account Reconciliation for the total expenses per transaction. You can either transfer the entire imported file, or individual Payments Import Data, or just individual Payments Import Transactions.

    Note

    As long as a line has not been posted, it can be deleted at any time in the General Journal or in the Reconciliation. Click on Transfer if you wish to transfer the deleted line again.
      Import
        Import Data
          Import Transactions
            Import Remittance Info. Import Charges

    Basic workflow

    1. Select NCP Payments > Import or on the starting page of Business Central: Tasks > Payments Import.
    2. Click on the action Import.
    3. Select which type of file you want to import (e.g. camt.053 statement).

      Tip

      You can import a file by drag and drop, drag the file to the button Choose...
      The import is executed. If not all bank accounts have been detected automatically, click on Data and select the Bank Account manually.
    4. As long as there is no journal/reconciliation line for an import entry, you can still delete the line. Click Import to re-import deleted data.
    5. Click on the action Transfer.
    6. Open the Journal to clear open entries or the Bank Account Reconciliation to match the data with your bank account.
    7. You can then post the imported entries.
    1. Import payment files

      To import a payment file provided by the bank
      1. Select NCP Payments > Import or on the starting page of Business Central: Tasks > Payments Import.
      2. Click on the action Import.
      3. Select which type of file you want to import (e.g. camt.053 statement). The import is executed. If not all bank accounts have been detected automatically, click on Data and select the Bank Account manually.
      4. As long as there is no journal/reconciliation line for an import entry, you can still delete the line. Click Import to re-import deleted data.
      For more information, see Import Tasks, Import Payment File.
    2. Transfer

      During the transfer, for each Payments Import Transaction a corresponding line is created in the Journal or in the Bank Account Reconciliation. If the field Trans. Charges in the Payments Import Setup is set to Yes, a line is also created in the Journal or in the Bank Account Reconciliation for the total of the Charges per transaction. You can either transfer the entire imported file, or individual Payments Import Data, or just individual Payments Import Transactions.

      Note

      As long as a line has not been posted, it can be deleted at any time in the General Journal or in the Reconciliation. Click on Transfer if you wish to transfer the deleted line again.
      • Journal

        In the Journals you can apply and close Open Entries on the basis of the imported data. Once the data has been transferred, click on Navigieren > Electronic Payments > Payments Import > Import Suggest Application - All Lines in the General Journal to create an automatic application suggestion. The suggestion attempts to determine the Account No. and the corresponding open entries, based on various criteria. The suggestion only considers lines for which no application has been defined. For lines that contain a value in the field Account No., this value is used as a filter for the entry search. The field Import Source Code on the journal lines views if the line has been created from a transaction, from expenses, or indirectly through a bank account reconciliation line. Click on Import Deviation - Set Filter to view only the entries that have not yet been completely cleared. Import Deviation - Remove Filter removes the filter. For more information, see Import Tasks, Applying Open Entries.
      • Bank Account Reconciliation

        Bank account reconciliation enables customers to reconcile their Business Central bank account with the imported statement files. After the data has been transferred, the imported statement lines are displayed in the left part of the window. The right pane views the bank account entries. Click on Automatic Match to perform an automatic matching of the two sides. If there are statement lines that cannot be fully reconciled with the Bank Account Ledger Entries (automatically or manually), the reason may be that the corresponding payments have not yet been posted. Use the action Transfer to General Journal to transfer the unreconciled amount, viewed in the Difference field, to an journal for posting. The field Import Source Code in the bank statement lines views that the line was created from a transaction or from charges. For more information, see Import Tasks, Bank Account Reconciliation.
    

    Tasks,
    Import,
    Import Payment File

    To import a payment file supplied by the bank:
    1. Select NCP Payments > Import or on the start page of Business Central: Tasks > Payments Import.
    2. Then click on the action Import.
    3. Select which type of file you want to import (e.g. camt.053 Account Statement).

      Note

      You define the possible file types in the Payments Import Setup

      Tip

      You can import a file by drag and drop, drag the file to the button Choose...
      The import is performed. If not all bank accounts have been automatically determined, click on Data and select the Bank Account No. manually.

      Note

      The next time you import a file with the same criteria, the bank account will be suggested automatically.
    4. As long as there is no journal line or reconciliation line for an import line, you can delete the line. Click Import to re-import deleted data.
    

    Tasks,
    Import,
    Applying Open Entries

    You can clear and close open entries in the journals based on the imported data:
    1. If the journal is not yet open, select NCP Payments > Import or on the Business Central home page: Tasks > Payments Import. Select the desired import line and click on Open Journals.
    2. Click on
      • Navigate > Electronic Payments > Payments Import > Import Suggest Application – All Lines, to create an automatic suggested application for all lines.
      • Navigate > Electronic Payments > Payments Import > Import Suggest Application – Line, to create an automatic suggested application for the marked line.
      The system attempts to determine the Account No. and the corresponding open entries based on various criteria.

      Note

      This only applies to those lines for which the Applied indicator is not set
      For lines that contain a value in the field Account No. , this value is used as a filter for the entry search. In the following sequence, the system attempts to determine a Account No. or Clearing Documents for each line:
      1. The system checks whether a Fixed Account Allocation exists for the line. Example: In the Fixed Account Allocation, it is defined that G/L account 241203 is used if the Remittance Info contains the word "tax office". The first line contains this account. For more information, see Setup, Fixed Account Allocations.
      2. If the Remittance Info contains a Document No. of a receivable or External Document No. of a vendor invoice, this Document No. is searched for in the database. The appropriate customer or vendor is determined and the payment is applied. Example:: The Remittance Info of the third line contains a Document No.. Customer and document no. are assigned. The line is applied and automatically receives the indicator Applied.
      3. If the remittance Info contains a customer/vendor number, the system searches the database for a suitable customer/vendor number. Applying with an open entry is not possible because the document number is not known. Example: The Remittance Info of the second line contains a number that is not found in the database. However, a customer with this number could be found. The customer is assigned to the line.
    3. Click on the button Navigate > Electronic Payments > Payments Import > Import Deviation - Set Filter to display only those rows that have not yet been fully applied or that are in the field Account No. No G/L Account
    4. .

    Important

    You can delete a line at any time if it has not yet been posted.
    

    Tasks,
    Import,
    Bank Account Reconciliation

    You must regularly reconcile your bank, receivables, and payables accounts by applying payments recorded in the bank to their related open (unpaid) invoices and credit memos or other open entries in Business Central. You can perform this task on the Payment Reconciliation Journal page, for example, by importing a bank statement file or feed to quickly register the payments. Payments are applied to open customer or vendor ledger entries based on matches between payment text and entry information. You can review and change automatic applications before you post the journal. You can choose to close any open bank account ledger entries related to the applied ledger entries when you post the journal. The bank account is automatically reconciled when all payments are applied. You can use the Bank Account Reconciliation to reconcile your Business Central bank account with the imported statement data:
    1. Go to Tasks > Bank Account Reconciliation or enter the term in What do you want to do?
    2. Create a new Bank Account Reconciliation using the + icon at the top center of the page.
    3. Select the Bank Account Number of your own bank account.
    4. If no number is generated automatically, enter a Statement No..
    5. Click on Process > Suggest Lines
    6. In the window that opens, enter the period in the field Start Date or End Date and click on OK. The imported lines are displayed on the left, the bank account ledger entries on the right.
    7. You have the following options.
      • Click Match Automatically to perform an automatic match of the two sides.
      • Select two lines and click Match Manually to match two lines.
      • Click Remove Match to remove the link.

      Note

      If statement lines cannot be completely reconciled with the bank account ledger entries (automatically or manually), it is possible that the corresponding payments have not yet been posted. Use the function Transfer to General Journal to transfer the unreconciled amount displayed in the field Difference to a journal for posting.

    Troubleshooting

    Difference Reason Resolution
    A transaction in the internal bank account
    is not on the bank statement.
    The bank transaction did not occur
    although a posting was made in
    Business Central.
    Make the missing money transaction (or
    prompt a debitor to make it), and then
    reimport the bank statement file or enter
    the transaction manually.
    A transaction on the bank statement
    does not exist as a document or journal
    line in Business Central.
    A bank transaction was made without a
    corresponding posting in Business Central,
    for example a journal line posting for an
    expense.
    Create and post the missing entry. For
    information on a quick way to initiate this, see
    unter To create missing ledger entries to match
    bank transactions with
    in Business Central Online Help.
    A transaction in the internal bank
    account corresponds to a bank
    transaction but some information is too
    different to give a match.
    Information, such as the amount or the
    customer name, was entered differently in
    connection with the bank transaction or the
    internal posting.
    Review the information, and then manually
    match the two. Optionally, correct the
    information mismatch.
    You must resolve the differences, for example by creating missing entries and correcting non-matching information, or by making missing money transactions, until the bank account reconciliation is completed and posted. You can fill in the Bank Statement Lines pane on the Bank Acc. Reconciliation page in the following ways:
    • Automatically, by using the Import Bank Statement function to fill in the Bank Statement Lines pane with bank transactions according to an imported file or stream provided by the bank.
    • Manually, by using the Suggest Lines function to fill in the Bank Statement Lines pane according to invoices in Business Central that have outstanding payments.
    You can find more information at, reconcile bank accounts in the Business Central Online Help.

    Fields

    The table contains the following fields or columns:
    Bank Account No.Specifies the number of the bank account that you want to reconcile with the bank's statement.
    Statement No.Specifies the number of the bank account statement.
    Statement DateSpecifies the date on the bank account statement.
    Import Additional Info.Specifies additional information from the payments import. Click on the field to display all additional information.
    Balance Last StatementSpecifies the ending balance shown on the last bank statement, which was used in the last posted bank reconciliation for this bank account.
    Statement Ending BalanceSpecifies the ending balance shown on the bank's statement that you want to reconcile with the bank account.
    Payment ImportSpecifies that data was imported via the payment transaction import.
    Bank Statement LinesFor more information, see Bank Statement Lines.
    Open Journal LinesSpecifies the number of journal lines for this bank account reconciliation.
    Balance (Bank Statement Lines)Specifies a balance, consisting of the Balance Last Statement field, plus the balance that has accumulated in the Statement Amount field.
    Total Balance (Bank Statement Lines)Specifies the accumulated balance of the bank reconciliation, which consists of the Balance Last Statement field, plus the balance in the Statement Amount field.
    Total Difference (Bank Statement Lines)Specifies the total amount of the Difference field for all the lines on the bank reconciliation.
    Balance (Bank Account Ledger Entries)Specifies the balance of the bank account since the last posting, including any amount in the Total on Outstanding Checks field.
    Total on Outstanding Checks (Bank Account Ledger Entries)Specifies the part of the bank account balance that consists of posted check ledger entries. The amount in this field is a subset of the amount in the Balance field under the right pane in the Bank Acc. Reconciliation window.
    Balance To Reconcile (Bank Account Ledger Entries)Specifies the balance of the bank account since the last posting, excluding any amount in the Total on Outstanding Checks field.

    Actions, Process

    • Suggest Lines

      Create bank account ledger entries suggestions and enter them automatically.
    • Import Data Card

      The Data from the Payments Import is displayed here. Each row in the Payments Import window can contain multiple data lines, which can contain multiple Transactions. The Transactions, themselves, can contain multiple Payment Remittance Lines and Charges.

    Actions, Matching

    • Match Automatically

      Automatically search for and match bank statement lines.
    • Match Manually

      Manually match selected lines in both panes to link each bank statement line to one or more related bank account ledger entries.
    • Remove Match

      Remove selection of matched bank statement lines.
    • Import Fixed Account Allocations

      If the applied amount should always assign certain transactions to a fixed G/L account, customer, vendor or bank account, you can set up fixed account allocations. Fixed account allocations are generally managed or created in the Payment Import Setup window, but can also be configured via the journal or bank account reconciliation. For more information, see Import Setup, Fixed Account Allocations.

    Actions, Posting

    • Transfer to General Journal

      Transfer the lines from the current window to the general journal.
    • Post

      Finalize the document or journal by posting the amounts and quantities to the related accounts in your company books.
    • Post & Print

      Finalize and prepare to print the document or journal. The values and quantities are posted to the related accounts. A report request window where you can specify what to include on the print-out.
    • Open Journals

      Open a journal based on the journal batch.
    

    Reports and Analysis,
    Payment Statistics

    This page views a line for each Payment File that was created from the journal.

    Fields, General

    Credit Transfer (LCY)Views the credit transfer amount in local currency.
    Direct Debit (LCY)Views the direct debit amount in local currency.
    Total Payments (LCY)Views the total amount of payment transactions in local currency.
    Other (LCY)Views all other amounts in local currency.
    Total (LCY)Views the total amount in in local currency.

    Fields, Details

    Payment TypeViews the payment type used in the transaction.
    Bank Account No.Views the bank account number for which the payment file was created.
    Currency CodeViews the currency for which the payment file was created.
    AmountView the total amount per payment type.
    Amount (LCY)View the total amount, in local currency, per payment type.
    

    Reports and Analysis,
    Import List

    From the Payments Import window, you can print the imported data or the imported statement.

    Print

    Additional Info.Specifies if additional informations in the list should also be printed.
    Transaction DescriptionSpecifies if transaction descriptions in the list should also be printed.
    Return ReasonSpecifies if return reasons in the list should also be printed.
    Payment ReferenceSpecifies if payment references in the list should also be printed.
    External Account HolderSpecifies if the external bank account holder in the list should also be printed.
    Order Amount DeviationSpecifies if order amount deviations in the list should also be printed.
    ChargesSpecifies if charges in the list should also be printed.
    Remittance Info.Specifies if remittance informations in the list should also be printed.
    

    Reports and Analysis,
    Import Allocation Analysis

    If the indicator Show Analysis Window is set in the Payments import Setup, the system does not carry out a comparison of the Remittance Info when you execute the function Apply Entries in the journal. Instead, this window shows how the application is performed.

    Important

    Use this indicator for information purposes only. To carry out applying, this indicator must be deactivated.
    .

    Fields

    Position IDUsed to identify the line. Position IDs are used in the Delete Reason field to indicate conflicts or reasons that are related to other lines.
    Line InformationViews information about this record.
    Account TypeViews the account type.
    Account No.displays the account number.
    Ledger Entry No.Views the ledger entry number of the current allocation entry.
    DeletedShows that no allocation was created.
    Delete Reason (no assignment)Shows the reason why no assignment was made.
    Posting DateShows the posting date.
    AmountShows the amount.
    Remaining AmountShows the remaining amount.
    Search ParameterShows the search parameter.
    Amount RatingShows the rating used to search for the amount.
    Payment ReferenceShows the payment reference found of the transaction. For more information, see History, Import Remittance Entries.
    Payment Reference EntryShows the payment reference found.
    Remittance InfoShows the payment remittance info found of the transaction. For more information, see History, Import Remittance Entries.
    Document Search forShows which value was searched for.
    Document Found in Shows where the searched value was found.
    Document RatingThe rating for the search for the document number.
    Account Search orShows which value was searched for.
    account Found inShows where the searched value was found.
    External IBAN (Account Number)Shows the IBAN or account number of the transaction.
    External SWIFT Code (BLZ)Shows the SWIFT code or BLZ of the transaction.
    External Account HolderShows the name of the account holder of the transaction.
    Ext. Account Info foundShows whether a bank account was found based on the account information of the transaction.
    Account RatingShows the rating for the search for the amount.
    RatingShows the total rating for the assignment.

    Actions

    • Transaction Card

      Opens the import transaction card in which all important information about the Transaction from the Payments Import is clearly displayed. For more information, see Import Tasks, Working with Payments Import - Structure.
    • Account Card

      View or change detailed information about the record on the document or journal line.
    • .

    Actions, Navigate

    • Fixed Account Allocations

      If the applying suggestion should always assign certain transactions to a fixed G/L account, customer, vendor or bank account, you can set up fixed account allocations for this. For more information, see Setup, Fixed Account Allocations.
    

    Reports and Analysis,
    Import Gen. Journal Deviation

    Options

    Include Lines without DeviationSpecifies if also lines without deviation should be printed in the report.
    

    Archive,
    Customer Ledger Entries

    The page is extended by NCPE Payments Export with the following fields:

    Fields

    Payment ReferenceSpecifies a payment reference which is suggested for the payment suggestion in the payment journal. You can change or delete the contents of the field.
    External Bank Account CodeSpecifies the bank account reference which is suggested in the payment suggestion in the payment journal. You can change or delete the contents of the field.
    

    Archive,
    Vendor Ledger Entries

    The page was extended with the following NCPE Payments Export fields:

    Fields

    Payment ReferenceSpecifies a payment reference which is suggested for the payment suggestion in the payment journal. You can change or delete the contents of the field.
    External Bank Account CodeSpecifies the bank account reference which is suggested for the payment suggestion in the payment journal. You can change or delete the contents of the field.
    

    Archive,
    Employee Ledger Entries

    The page is extended by NCPE Payments Export with the following fields:

    Fields

    Payment ReferenceSpecifies a payment reference which is suggested for the payment suggestion in the payment journal. You can change or delete the contents of the field.
    

    Archive,
    Bank Account Ledger Entries

    When you post the journal after checking the payments, a Bank Account Ledger Entry will be created. Using the action Bank Account Ledger Entries on the page Clearing Entries you can view this entry.

    Fields

    Posting DateSpecifies the posting date for this entry.
    Document TypeSpecifies the document type on the bank account ledger entry. The document type will be payment or refund, or the field is empty.
    Document No.Specifies the document number of the bank account ledger entries.
    Bank Account No.Specifies the number of the bank account used for the entry.
    DescriptionSpecifies the description of the bank account ledger entries.
    AmountSpecifies the amount of the entry in the applicable foreign currency.
    Bal. Account TypeSpecifies the type of account to which an balancing entry is posted, for example, BANK for a cash account.
    Bal. Account No.Specifies the number of the G/L, customer, vendor or bank account that the offsetting entry is posted to, for example, a cash account for cash purchases.
    OpenSpecifies whether the amount on the bank account entry has been fully applied to or if there is still a remaining amount that must be applied to.
    No. of Payment EntriesNumber of payment entries that refer to this bank account ledger entry.
    Entry. No.Specifies the number of the entry, as assigned from the specified number series when the entry was created.

    Aktionen

    • Reverse Transaction

      Undo an erroneous journal posting. You can find further information on this topic at Reverse Transactions
    • Navigieren

      Finds all entries and documents that exist for the document number and posting date of the selected entry or document.
    • Payment Entries

      All payment entries for this bank account ledger entries are listed here.
    • Clearing Entries

      All clearing entries for this bank account ledger entry are listed here.
    • Check Ledger Entries

      View check ledger entries resulting from posting transactions in a payment journal for the relevant bank account.
    • Dimensions

      View or edit dimensions, such as a area, project, or department, that you can assign to sales or purchasing documents to distribute costs and analyze transaction progress. (Alt-D)
    • Set Dimension Filter

      Limit the entries using the specified dimension filter.

      Note

      If you use a large number of dimension combinations, this feature may not work and may result in a message that SQL Server only supports up to 2100 parameters.
    

    Archive,
    Clearing Entries

    In the window NCP Clearing Entries the history of all created payment files are listed. The action Create Payment File in the Payment Journals creates a Clearing Entries with status Created, which contains information about the file. Furthermore, a payment entry is created for each individual transaction. Structure:
      NCP Clearing Entries
        NCP Payment Entries
          NCP Payment Remittance Entries NCP Payment Posting Entries
    If the journal is posted, the status is set to Posted and the corresponding bank account ledger entry can be displayed using the action Bank Account Ledger Entries. If the file is cancelled, the status is set to Cancelled.

    Fields

    StatusShows the status for the Clearing Entry. Options:
    • Created - Indicates that the payment file was created.
    • Voided - Indicates that the payment file was canceled.
    • Posted - Indicates that the journal was posted.
    Payment TypeShows the payment type of the payment type.
    Bank Account No.View the bank account number for which the payment file was created.
    Archived Payment File existsSpecifies if an archived payment file is available.
    Creation DateView the date when the payment file was created.
    No. of Payment EntriesNumber of all Payment Entries that refer to this Clearing Entries.
    No. of Pmnt. NotificationsNumber of all payment notification e-mails that refer to this Clearing Entries.
    Pmt. Notifications not Printed/SentViews how many Payment Notifications remain to be printed or sent by e-mail.
    No. of Bank Account Ledger EntriesShows the number of Bank Account Ledger Entries that refere to this Clearing Entry
    AmountShows the total amount from the Payment Entries that refer to this Clearing Entry.
    Amount (LCY)Shows the total amount in local currency from the Payment Entries that refer to this Clearing Entry.
    File Reference (Message Reference)View the reference of the payment file. The reference is generated from the current date and time when the payment file is created.
    Entry No.Views the entry number assigned to the Clearing Entry. The application assigns a unique number to each Clearing Entry.

    Actions

    • Export Payment File

      The action Create Payment File in the payment journal creates a Payment File and a Clearing Entry with status Created, which contains information about the file. With the action Export payment File, this Payment File can be exported at a later time. In the summary, all information on the created clearing item is displayed. The payment file can be made available for the bank software via Export payment file. The payment file can also be exported at a later time from the Clearing Entries. For more information, see Create Payment File.
    • Void Payment File

      With this action a created Payment File can be voided. The status of the related Clearing Entries is set to Voided.
    • Clearing List

      This List contains information about the Clearing Entries.
    • Notification E-Mail Suggestion

      This list shows information on the payment suggestion created, or the current situation (clearing etc.) in the journal page.
    • Notification

      The payment notification is useful to help the recipient to assign the payment(s). This is especially important in the case of a Collective Transfer. It is also possible to send this notification by e-mail. After the payment file has been created, you can print the Notification or send it by e-mail.
    • Payment Entries

      Opens the list of Payment Entries that refers to this Clearing Entry. For more information, see Payment Entry.
    • Bank Account Ledger Entries

      Opens the overview of the Bank Account Ledger Entries that refer to this Clearing Entry. For more information, see Bank Account Ledger Entries.
    

    Archive,
    Payment Entries

    The action Create Payment File in the Payment Journals creates a NCP Clearing Entries with status Created, which contains information about the file. Furthermore, a payment entry is created for each individual transaction. Structure:
      NCP Clearing Entries
        NCP Payment Entries
          NCP Payment Remittance Entries NCP Payment Posting Entries
    If the journal is posted, the status is set to Posted and the corresponding bank account ledger entry can be displayed using the action Bank Account Ledger Entries. If the file is cancelled, the status is set to Cancelled.

    Fields

    StatusShows the status for the payment entry. Options:
    • Created - Indicates that the payment file was created.
    • Voided - Indicates that the payment file was canceled.
    • Posted - Indicates that the journal was posted.
    Payment TypeViews the payment type of the created payment file.
    Bank Account No.View the bank account number for which the payment file was created.
    No. of Payment Posting EntriesShows the number of payment posting entries for the current payment entry.
    Posted with Document No.Shows the first value of the payment posting entries.

    Note

    If Navigate is called directly from the payment entry and there are several payment posting entries for the payment entry, Navigate is called with the first data record found.
    Posted with Posting DateShows the first value of the payment posting entries.

    Note

    If Navigate is called directly from the payment entry and there are several payment posting entries for the payment entry, Navigate is called with the first data record found.
    No. of Bank Account EntriesViews the number of Bank Account Ledger Entries for the current entry.
    DescriptionView the description from the journal.
    Execution DateViews the desired execution date for the transaction.
    Urgent PaymentViews information indicating whether the payment file was created with the Urgent Payment option.
    Pmt. NotificationAfter a payment file has been created, this field views if a payment notification exists for the NCP Payment Entry. If the Payment Remittance cannot be transferred completely when the payment file is created, a payment notification is created. You can also use additional parameters to set up the system to create a payment notification every time you create a payment file.

    Note

    The payment notification is useful to help the recipient to assign the payment(s). This is particularly relevant in the case of a collective transfer. It is possible to send the payment notification via e-mail.
    Payment Notification No.After a payment file has been created, the number of the payment notifications is displayed in this field, in case a payment notification exists for the created Payment Entry.
    Pmt. Notification PrintedViews that a payment notification is printed.
    Pmt. Notification E-Mail SentShows that the notification was sent by e-mail
    Pmt. Notification E-Mail Sent ToShows the recipient E-Mail adress of the notification e-mail.
    Pmt. Notification E-Mail DateShows when the notification was sent by e-mail.
    Pmt. Notification E-Mail TimeShows when the notification was sent by e-mail.
    No. of Remittance EntriesShows the number of remittance entries for the current entry.
    Currency CodeViews the currency code of the transaction.
    AmountShows the amount for the transaction.
    Amount (LCY)Shows the amount for the transaction in LCY.
    Account TypeShows the type of account for the transaction. Options:
    • Customer
    • Vendor
    • Bank Account
    • Employee
    Account No.Shows the account number used for the transaction.
    External Bank Account CodeShows which bank account of customer/vendor/employee is used for the transaction.
    One-Time TransferIndicate that the payment entry was a one-time transfer.
    External IBANShows the IBAN used by the customer/vendor/employee.
    External SWIFT CodeShows the SWIFT-Code used by the customer/vendor/employee.
    External Bank Account No.Shows the bank account of customer/vendor/employee used for the transaction.
    External Bank Branch No.Shows the Bank Branch No. used by the customer/vendor/employee.
    Direct Debit TypeShows which settings for the direct debit type were used to create the payment file.
    Direct Debit SequenceShows which settings for the direct debit type were used to create the payment file.
    Mandate IDShows which settings for the mandate id were used to create the payment file. For more information, see Sepa Mandates.
    Date of MandateShows which settings for the mandate were used to create the payment file. For more information, see Sepa Mandates.
    Payment ReferenceShows the payment reference of the transaction.
    ChargesDas Feld Spesen ist nur dann verfügbar, wenn die Zahlungsart und/oder das XML-Schema des Bankkontos Spesen unterstützt. For more information, see Setup, XML-Schemas.

    Actions

    • Navigate

      Sucht alle Posten und Belege, die für die Belegnummer und das Buchungsdatum laut dem ausgewählten Posten oder Beleg vorhanden sind.
    • Remittance Entries

      All payment remittance entries to the payment entry are listed here.
    • Bank Account Ledger Entries

      Opens the overview of all Bank Account Ledger Entries with reference to this NCP Payment Entry.
    • Clearing Entries

      Opens the overview of the NCP Clearing Entries with reference to this NCP Payment Entry. For more information, see History, NCP Clearing Entries.
    

    Archive,
    Payment Remittance Entries

    The action Create Payment File creates a Clearing Entry with status Created. This entry contains information about the file. In addition, a Payment Entry and a Payment Remittance Entry are created for every single transaction. These contain information about which entries were cleared by the payment. Structure:
      NCP Clearing Entries
        NCP Payment Entries
          NCP Payment Remittance Entries NCP Payment Posting Entries

    Fields

    Document TypeViews the document type of the remittance entry.
    Document No.Views the document number ot the remittance entry.
    Posting DateDate on which the document was posted.
    External Document No.Specifies an additional document number. This usually refers to the numbering system by the customer or vendor.
    Remittance Info.Views the remittance info (which was stored in the NCPE Payments Export Setup).
    Currency CodeViews the currency code used when posting the entry.
    AmountViews the posted amount for the entry.
    DiscountViews the discount of the entry that has been discounted.
    Entry No.Views the entry number that was assigned to the payment remittance entry. The application assigns a unique number to each payment remittance entry.

    Actions

    • Navigate

      Finds all entries and documents that exist for the document number and posting date of the selected entry or document.
    

    Archive,
    Payment Posting Entries

    When you post the payments, the NCP Clearing Entry are written to the NCP Payment Posting Entry and the Status of the Clearing Entry is set to Posted. Structure:
      NCP Clearing Entries
        NCP Payment Entries
          NCP Payment Remittance Entries NCP Payment Posting Entries

    Fields

    Document No.Views the document number of the Payment Entry.
    Posting DateViews the date when the entry was posted.

    Actions

    • Navigate

      Finds all entries and documents that exist for the document number and posting date of the selected entry or document.
    

    Archive,
    Import

    Hier wird pro importierten Datei eine Zeile angelegt, diese wiederum können mehrere Transaktionszeilen und Verwendungszweckzeilen haben. Structure:
      Import
        Import Data
          Import Transactions
            Import Remittance Info. Import Charges

    Fields

    Import DateShows when the data was imported.
    Import TimeShows when the data was imported.
    Import User IDShows from which user the data was imported.
    File FormatShows the file format of the imported file.
    Imported FileShows the name of the imported file.
    Archived Import File ExistsShows you if an archived import file already exists.
    No. of DataShows the number of imported data entries. For more information, see History, Import Data.
    No. of Data without Bank AllocationShows the amount of data without bank assignment.

    Note

    If the bank allocation does not match during import, the bank allocation can be entered manually. To do this, open the Payments Import Data either by clicking in the field or by selecting the action Navigate > Data.
    Bank Account No.If the payments import data all have the same bank account, the bank account number is displayed here. If the accounts are different, no value is displayed.

    Note

    If a bank account is detected when importing a payment file, the system first checks whether fixed account allocations exist.
    Bank Account NameIf the payments import data all have the same bank account, the bank account name is displayed here. If the accounts are different, no value is displayed.
    Bank Account IBANIf the payments import data all have the same bank account, the bank account name is displayed here. If the accounts are different, no value is displayed.
    No. of TransactionsShows the number of imported transactions. For more information, see History, Import Transactions.
    Open Journal LinesShows if data has been transferred to an general journal and if there are open general journal lines.

    Note

    Depending on the setting used in the NCPI Payments Import Setup, under the respective file format setting, this field may or may not be displayed.
    For more information, see the Business Central online help, at Working with General Journals.
    Posted Journal LinesShows if data has been transferred to an general journal and general journal lines have been posted.

    Note

    Depending on the setting used in the NCPI Payments Import Setup, under the respective file format setting, this field may or may not be displayed.
    For more information, see the Business Central online help, at Working with General Journals.
    Open ReconciliationsShows if data has been transferred to an reconciliation and if there are open reconciliation lines.

    Note

    Depending on the setting used in the NCPI Payments Import Setup, under the respective file format setting, this field may or may not be displayed.
    For more information, see the Business Central online help, at Working with General Journals.
    Posted Reconciliation LinesShows if data has been transferred to an reconciliation and reconciliation lines have been posted.

    Note

    Depending on the setting used in the NCPI Payments Import Setup, under the respective file format setting, this field may or may not be displayed.
    For more information, see the Business Central online help, at Working with General Journals.
    Posted StatementsShows if data has been transferred to a bank account reconciliation and posted statements are available.

    Note

    Depending on the setting used in the NCPI Payments Import Setup, under the respective file format setting, this field may or may not be displayed.
    For more information, see the Business Central online help, at Working with General Journals.
    Posted Statement LinesShows if data has been transferred to a bank account reconciliation and if there are posted statement lines.

    Note

    Depending on the setting used in the NCPI Payments Import Setup, under the respective file format setting, this field may or may not be displayed.
    For more information, see the Business Central online help, at Working with General Journals.
    Message DateShows when the file was created (File info: CreDtTm).
    Message TimeShows when the file was created (File info: CreDtTm).
    MEssage Recipient NameShows the name of the recipient of the file (file info: MsgRcpt Nm).
    Additional Info.Shows additional information (file info: AddtlInf). For more information, see History, Import Additional Info..
    Entry No.Specifies the number of the entry that was assigned to it when it was created from the specified number series.

    Actions, Process

    • Import

      Click Import to import the file provided by your bank. As long as there are no journal lines or reconciliations for the imported entry, the line can be deleted at any time. Click on Import if you want to re-import the deleted data. For more information, see Import Tasks, Working with Payments Import - Import Payment File.
    • Export Archived Import File

      Starts the download of the archived import file.

    Actions, Transfer

    • Transfer

      With this option, entries from the payments import can be transferred to a journal. During the transfer, a corresponding entry is created for each payments import transaction in the Journal or in the Bank Account Reconciliation. If the field Trans. Charges is set to Yes in the Payments Import Setup, an entry is also created for the total charges per transaction. You can either transfer the entire imported file, or individual Payments Import Data, or just individual Payments Import Transactions. For more information, see Import Tasks, Working with Payments Import - Transfer.

    Actions, Report

    • Import List

      This list shows information about the imported file.

    Actions, Navigate

    • Data

      Here the Data from the Payments Import are listed. Each line in the Payments Import window can contain several data lines, which in turn can contain several transactions. The transactions, in turn, can contain several remittance lines and charges. For more information, see History, Import Data.
    • Transactions

      Here the Transactions from the Payments Import are listed. Each line in the Payments Import window can contain several data lines, which in turn can contain several transactions. The transactions, in turn, can contain several remittance lines and charges. For more information, see History, Import Transactions.
    • Open Reconciliations

      Shows the list with Open Reconciliations if such exist. In the lines you can see the number of open reconciliations in the field Open Reconciliation Lines.

      Note

      This action is only available if the option Bank Acc. Reconciliation has been set up in the Payments Import Setup, in the field camt.053 - Statement.
    • Open Journal Lines

      Opens the open journal lines. In the journal it is possible to clear and close open entries based on the imported data.

      Note

      This action is only available if the option General Journal has been set up in the Payments Import Setup, in the field camt.053 - Statement.
    • Posted Statement

      In this overview, the posted statements are listed.

      Note

      This action is only available if the option Bank Acc. Reconciliation has been set in the Payments Import Setup, in the fields camt.053 - Account Statement, camt.054 - Debit Credit Notification or Custom.
    • Additional Info.

      Öffnet die Karte mit den Zusatzinformationen aus dem Group Header (GrpHdr) des Imports. For more information, see Historie, Import Zusatzinformationen.
    

    Archive,
    Import Data

    Each line in the window NCPI Payments Import can contain several Data lines, which in turn can contain several Transactions. The transactions, in turn, can contain several Remittance Entries and Charges. Depending on the imported file format, different fields are filled or used. During the transfer, for each NCPI Payments Import Transaction, a corresponding entry is created in the journal or in the Reconciliation. If the field Transf. Charges in the Payments Import Setup is set to Yes, a entry is also created in the for the total charges per transaction. You can either transfer the entire imported file, or individual Payments Import Data, or just individual Payments Import Transactions.

    Note

    As long as a line has not been posted, it can be deleted at any time in the Journal or in the Reconciliation. Click on Transfer if you wish to transfer the deleted row again.
    Structure:
      Import
        Import Data
          Import Transactions
            Import Remittance Infos Import Charges

    Fields

    Statement No.Displays the statement number (file info: LglSeqNb).
    Statement DateDisplays the statement date (file info: CreDtTm).
    Statement fromShows the statement period (file info: FrToDt FrDtTm).
    Statement toShows the statement period (file info: FrToDt FrDtTm).
    Bank Account No.The import tries to determine a bank account for each data row based on various criteria. If not all bank accounts were suggested automatically, select the bank account number manually. The next time you import a file with the same criteria, the bank account is suggested.
    Bank Account NameIf the payments import data all have the same bank account, the bank account name is displayed here. If the accounts are different, no value is displayed.
    Bank Account IBANIf the payments import data all have the same bank account, the IBAN is displayed here. If the accounts are different, no value is displayed.
    No. of BalancesShows the number of imported balances.
    No. of TransactionsSpecifies the number of imported transactions. For more information, see History, Import Transactions.
    Open Journal LinesShows that data has been transferred to a journal and that there are open journal lines.

    Note

    Depending on the setting used in the NCPI Payments Import Setup, under the respective file format setting, this field may or may not be shown.
    For more information, see the Business Central online help, at Working with General Journals
    Posted Journal LinesShows if data has been transferred to a journal and journal lines have been posted.

    Note

    Depending on the setting used in the NCPI Payments Import Setup, under the respective file format setting, this field may or may not be shown.
    For more information, see the Business Central online help, at Working with General Journals
    Open Reconciliation LinesShows if data has been transferred to a bank account reconciliation and open reconciliations exist.

    Note

    Depending on the setting used in the NCPI Payments Import Setup, under the respective file format setting, this field may or may not be shown.
    For more information, see the Business Central online help, at Working with General Journals
    Posted Reconciliation LinesShows if data has been transferred to a bank account reconciliation and if there are posted reconciliation lines.

    Note

    Depending on the setting used in the NCPI Payments Import Setup, under the respective file format setting, this field may or may not be shown.
    For more information, see the Business Central online help, at Working with General Journals
    Posted StatementsShows if data has been transferred to a bank account reconciliation and posted statements exist.

    Note

    Depending on the setting used in the NCPI Payments Import Setup, under the respective file format setting, this field may or may not be shown.
    For more information, see the Business Central online help, at Working with General Journals
    Posted Statement LinesShows if data has been transferred to a bank account reconciliation and posted statement lines exist.

    Note

    Depending on the setting used in the NCPI Payments Import Setup, under the respective file format setting, this field may or may not be shown.
    For more information, see the Business Central online help, at Working with General Journals
    IBAN (Bank Account No.)Shows the IBAN or account number of the imported data (file info: Acct Id IBAN (Acct Id Othr Id)).
    SWIFT-Code (Bank Branch No.)Shows the SWIFT code or the bank branch code of the imported data (file info: Acct Svcr FinInstnId BIC (Acct Svcr FinInstnId Othr Id)).
    ISO Bank Currency CodeShows the ISO bank currency code of the imported data (file info: Acct Ccy).
    Additional InformationShows additional information (file info: AddtlInf). For more information, see History, Import Additional Info.
    Entry No.Shows the number assigned to the record. The application assigns a unique number to each record.
    Import Entry No.This field contains the number of the import.

    Actions, Process

    • Suggest Bank Account

      This function can help to suggest already used bank accounts. For more information, see Setup, Bank Accounts.

    Actions, Transfer

    • Transfer

      With this option, entries from the payments import can be transferred to a journal. During the transfer, a corresponding entry is created for each payments import transaction in the Journal or in the Bank Account Reconciliation. If the field Trans. Charges is set to Yes in the Payments Import Setup, an entry is also created for the total charges per transaction. You can either transfer the entire imported file, or individual Payments Import Data, or just individual Payments Import Transactions. For more information, see Import Tasks, Working with Payments Import - Transfer.

    Actions, Navigate

    • Balances

      The balances from the payments import are listed here. For more information, see History, Import Balances.
    • Transactions

      The transactions from the payments import are listed here. Each row in the Payments Import window can contain multiple data rows, which in turn can contain multiple transactions. The transactions, in turn, can contain multiple remittance entries and expenses. For more information, see History, Import Transactions.
    • Open Reconciliations

      This action opens the page Bank Account Reconciliations, where the transfered entries from import are listed, if any exist.
    • Posted Statements

      This action opens the page Bank Account Statement that shows the posted statements that previously was imported and posted.
    • Additional Info.

      Öffnet die Karte mit den Zusatzinformationen aus dem Group Header (GrpHdr) des Imports. For more information, see Historie, Import Zusatzinformationen.
    • Card

      Opens the card for the selected record.
    

    Archive,
    Import Balances

    The balances from the payments import are displayed here.

    Fields

    TypeShows the type of balance (file info: Tp CdOrPrtry Cd).
    AmountShows the amount (file info: Amt).
    ISO Currency CodeShows the ISO Currency Code of the balance (file info: Ccy)
    PositiveShows whether the balance is positive or negative (file info: CdtDbtInd).
    DateShows the date of the balance (file info: Dt Dt).
    

    Archive,
    Import Transactions

    Each line in the window NCPI Payments Import can contain several Data lines, which in turn can contain several Transactions. The transactions, in turn, can contain several Remittance Entries and Charges. Depending on the imported file format, different fields are filled or used. During the transfer, for each NCPI Payments Import Transaction, a corresponding entry is created in the journal or in the Reconciliation. If the field Transf. Charges in the Payments Import Setup is set to Yes, a entry is also created in the for the total charges per transaction. You can either transfer the entire imported file, or individual Payments Import Data, or just individual Payments Import Transactions.

    Note

    As long as a line has not been posted, it can be deleted at any time in the Journal or in the Reconciliation. Click on Transfer if you wish to transfer the deleted row again.
    Structure:
      Import
        Import Data
          Import Transactions
            Import Remittance Info Import Charges

    Fields

    External Account HolderShows the name of the account holder of the imported transaction (file info: RltdPties Dbtr Nm/RltdPties Cdtr Nm).
    External Account Holder AddressShows the address of the account holder of the imported transaction (file info: RltdPties Dbtr PstlAdr AdrLine/RltdPties Cdtr PstlAdr AdrLine).
    External IBAN (Bank Account No.)Shows the IBAN or account number of the imported transaction (file info: RltdPties DbtrAcct Id IBAN/RltdPties CdtrAcct Id IBAN (RltdPties DbtrAcct Id Othr Id/RltdPties CdtrAcct Id Othr Id)).
    External SWIFT-Code (Bank Branch No.)Shows the SWIFT code or bank branch no. of the imported transaction (file info: RltdAgts DbtrAgt FinInstnId BIC/RltdAgts CdtrAgt FinInstnId BIC (RltdAgts DbtrAgt FinInstnId Othr Id/RltdAgts CdtrAgt FinInstnId Othr Id)).
    Order AmountShows the order amount of the imported transaction (file info: AmtDtls InstdAmt Amt).
    Order ISO Currency CodeShows the ISO currency code of the order amount of the imported transaction (file info: AmtDtls InstdAmt Ccy).
    Currency FactorShows the currency factor of the imported transaction. When the transaction entry is transferred to an journal, the amount of the order is converted with the currency factor in case of foreign currency (file Info: Ccy/AmtDtls TxAmt CcyXchg XchgRate).
    PositiveShows if the imported transaction is positive or negative (file info: CdtDbtInd).
    Reversal PostingSpecifies if the imported transaction is a chargeback (return-credit/direct debit and reversal) (file info: RvslInd).
    Posting StatusShows the posting status of the transaction (file info: Sts).
    Posting DateShows the posting date of the imported transaction (file info: BookgDt Dt).

    Note

    Depending on the settings used in the NCPI Payments Import Setup, under Transfer, this field is filled with the appropriate values For more information, see Import Setup - Fields, Transfer..
    Value DateShows the value date of the imported transaction (file info: ValDt Dt).

    Note

    Depending on the settings used in the NCPI Payments Import Setup, under Transfer, this field is filled with the appropriate values For more information, see Import Setup - Fields, Transfer..
    Open Journal Line ExistsShows if the data has been transferred to an journal and if there is an open journal line.
    Journal Line PostedShows if the data has been transferred to an journal and the journal line row has been posted.
    Open Recon. Line ExistsShows if the data has been transferred to an reconciliation and if there is an open reconciliation line.
    Posted Statement Lines ExistsSpecifies if the data has been transferred to a bank account reconciliation and a posted statement line exists.
    No. of ChargesShows the number of charges. For more information, see History, Import Charges.
    Open Charge Journal Line ExistsShows if the charges have been transferred to an journal and if there is an open journal line.
    Open Charge Reconciliation Line ExistsShows if the charges have been transferred to an reconciliation and if there is an open reconciliation line.
    Posted Charge Journal Line ExistsShows if the charges have been transferred to an journal and if the journal line has been posted.
    Posted Charge Reconciliation Line ExistsShows if the charges have been transferred to an reconciliation and if the reconciliation line has been posted.
    No. of Remittance Info. LinesSpecifies the number of remittance information lines.
    Remittance Info.Shows a part of the remittance info (file info: RmtInf Ustrd). For more information, see History, Import Remittance Info.
    Payment ReferenceShows the payment reference of the imported transaction (file info: RmtInf Strd CdtrRefInf Ref).
    Transaction Reference (Sender Reference)Shows the Transaction Reference (Client Reference) of the imported transaction (file info: Refs EndToEndId >>> [TransactionReference]).
    Order Reference (Batch Control No.)Specifies the order reference (payment info id) of the imported transaction (file info: Refs PmtInfId >>> [OrderReference]).
    File Reference (Message Reference)Displays the file reference (message reference) of the imported transaction. (file info: Refs MsgId >>> [FileReference]).
    Transaction CodeDisplays the transaction code (file info: BkTxCd Prtry Cd). These are import codes for transaction types that may appear in the import files. These should be set up before you start with importing. For more information, see Import Setup, Import Codes.
    Transaction Code DescriptionShows the transaction code Description of the corresponding import code. For more information, see Import Setup, Import Codes.
    SWIFT Transaktion CodeShows the SWIFT transaction code (file info: BkTxCd Prtry Cd). These are import codes for transaction types that may appear in the import files. These should be set up before you start with importing. For more information, see Import Setup, Import Codes.
    SWIFT Transaction Code DescriptionShows the SWIFT transaction code description of the corresponding import code. For more information, see Import Setup, Import Codes.
    Primanota No.Shows the primanota number of the imported transaction.
    Additional Info.Shows additional information about the imported transaction. For more information, see History, Additional Info..
    Return Reason CodeShows the return reason code of the imported transaction (file info: RtrInf Rsn Cd). These are import codes for transaction types that may appear in the import files. These should be set up before you start with importing. For more information, see Import Setup, Import Codes
    Return Reason DescriptionShows the Return Reason Description of the imported transaction. These are import codes for transaction types that may appear in the import files. These should be set up before you start with importing. For more information, see Import Setup, Import Codes.
    Mandate IDDisplays the Mandate ID of the imported transaction (file info: Refs MndtId). For more information, see Export Setup, SEPA Mandates.
    Check No.Shows the check number of the imported transaction (file info: Refs ChqNb).
    Entry No.Shows the entry number assigned to the record. The application assigns a unique number to each record.
    Data Entry No.This field contains the entry number of the data record.
    Import Entry No.This field contains the entry number of the import.

    Actions, Transfer

    • Transfer

      Allows lines from the payments import to be transferred to an journal. During the transfer, for each payment transaction import, a corresponding line is created in the Journal or in the Reconciliation. If the field Transfer Charges in the Payments Import Setup is set to Yes, an entry is also created in the journal or in the reconciliation for the total charges by each transaction. You can either transfer the entire imported file, or individual Payments Import Data, or just individual Payments Import Transactions. For more information, see Import Tasks, Working with Payments Import Import - Transfer.

    Actions, Navigate

    • Remittance Info.

      The remittance info. of the payments import is displayed here. Each row in the Payments Import window can contain several data entries, which in turn can contain several transactions. The transactions in turn can contain several remittance info. lines and charges. For more information, see History, Import Remittance Info..
    • Charges

      The charges from the payments import are displayed here. Each row in the Payments Import window can contain several data entries, which in turn can contain several transactions. The transactions in turn can contain several remittance info. lines and charges. For more information, see History, Import Charges.
    • Additional Info.

      Opens the card with the additional information from the group header (GrpHdr) of the import. For more information, see History, Import Additional Info..
    • Card

      Opens the card for the selected record.
    

    Archive,
    Import Charges

    The charges from the payments import are displayed here. Structure:
      Import
        Import Data
          Import Transactions
            Import Remittance Infos Import Charges

    Fields

    CodeShows the code of the charges (file info: Tp Prtry Id).
    AmountShows the amount (file info: Amt).
    ISO Country CodeShows the ISO Currency Code of the balance (file info: Ccy)
    PositiveShows whether the balance is positive or negative ( file info: CdtDbtInd).
    Total ChargesShows the total charges amount of the transaction.
    Open Journal Line existIndicates that data has been transferred to a journal and that there is an open journal entry.
    Posted Journal Line existIndicates that data has been transferred to a journal and the journal entry has been posted.
    Open Reconciliation Line existIndicates that data has been transferred to a bank account reconciliation journal and there is an open journal entry.
    Posted Reconciliation Line existIndicates that data has been transferred to a bank account reconciliation journal and the journal entry has been posted.
    

    Archive,
    Import Additional Info

    Additional information from the import transactions are listed here.

    Fields

    Additional Info.Specifies the additional information from the payments import.
    

    Archive,
    Import Remittance Info.

    The remittance info. of the payments import is viewed here. Structure:
      Import
        Import Data
          Import Transactions
            Import Remittance Info. Import Charges

    Fields

    Remittance Info.Shows a part of the intended use.

    Appendix,
    Payments Export - Delete Data


    Not Found


    The requested topic was not found on this server.
    

    Appendix,
    Payments Import - Delete Data

    Importing a file creates an entry in the NCPI Payments Import. The imported file is also saved there. With this action, the archived import files can be removed from the payments import if necessary.

    Note

    • The period for deleting the data can be specified in the NCPI Payments Import Setup in the field Delete Data Date Calculation.
    • Only data that is at least 6 months old can be deleted. If the field is empty, the minimum period is used.

      Options

      Delete Archived FilesSpecifies, whether the archived data should be deleted.
      

      Appendix,
      Release Notes

      Would you like to know what has changed in NCPE Payments Export und NCPI Payments Import? Below you'll find an overview about new features and changes that has been done in the updates.

      NCPE 17.0.0.0

        Improvements

      • Installation routine (new installation) now creates the required standard entries in the tables: Languages, Countries/Regions, SEPA Mandate Text Lines and Payment File Setup. For more information, see Export Einrichtung, Zahlungsverkehr Export Einrichtungsassistent.
      • Modifications

      • Captions of some fields corrected.
      • Code requirements for Business Central Version 17 implemented.
      • Functions that are no longer needed are marked as obsolete - they will be deleted in a future release.
      • Bank Codes Download URL's updated.
      • In the Assisted Setup on the SMTP Mail Setup page a button has been added to access the standard SMTP settings. Now you can change the e-mail settings without leaving the wizard.
      • The Overview of Available XML Schemas in the NCPE Payments Bank Account Setup now only views the relevant schemas according to the country code assigned to the bank account.
      • Text of the AssisstEdit message boxes for the fields "File name" and "Remittance" has been made more readable.
      • Corrections

      • Bug in Assisted Setup fixed. For more information, see Export Einrichtung, Zahlungsverkehr Export Einrichtungsassistent.
      • Error in the XML Schema card where the fields IBAN Only possible, IBAN or Account Number possible, Address possible, Charges possible and Urgent Payment possible were not filled correctly (the options were filled incorrectly according to the available schema). For more information, see Export Einrichtung, Zahlungsverkehr XML Schemata.
      • Display error when AssisstEdit the "File Name" field in the "Payment File" section of the NCPE Export Setup page.

      NCPI 17.0.0.0

        Improvements

      • Assisted Setup added.
      • Modifications

      • Captions of some fields corrected.
      • Code requirements for Business Central Version 17 implemented.
      • Functions that are no longer needed marked as obsolete - they will be deleted in one of the next releases.
      • Corrections

      • Report rendering error of report "Import Deviation - Print".

      NCPE 16.0.0.0

      n/a

      NCPI 16.0.0.0

      n/a
        Feedback|  Print Manual
      DE|EN Imprint