NAVAX Payment

Manual

☰ Contents

General

• NAVAX Payment
  Welcome to the help page of NAVAX Payment. This page provides you with comprehensive information and support for our payment solutions, including NAVAX Payment Exports and NAVAX Payment Imports. Our goal is to enable you to seamlessly and efficiently manage your payment transactions. The modules NAVAX Payment Exports and NAVAX Payment Imports, as well as their NAVAX konfipay Connector extension, are available separately...

Setup

• General

• • Bank Account Setup
    In the NCP Bank Account Setup window, all bank accounts required for payment processing with NAVAX Payment are stored and managed. Here, you can add new bank accounts, edit or remove existing accounts, and update important account details. The overview provides a clear and structured representation of all relevant bank information to make payment processing efficient and transparent...
  • Bank Codes
    In the page NCP Bank Codes you can manage the bank codes. You have the possibility to import bank codes easily and comfortably from 3 banking institutions...
  • Vendor/Customer Bank Account
    In the Creditor/Debtor Bank Account Overview, you can assign your creditor and debtor bank accounts. You can access the overview by clicking on Navigate > Creditor/Debtor > Bank Accounts on the Creditor or Debtor list or the corresponding card...
  • Countries/Regions
    In this overview you can setup and manage settings for countries and regions to use them for payment transactions...
  • Pay with QR-Code
    With the NCP Pay with QR Code function you can create a QR code that can then be placed on your invoices - whether digital or paper. The customer thus saves the tedious typing of data and also does not run the risk of entering incorrect data. This also makes it easier to apply payments later that were imported into Business Central via bank account statement...

• Exports

• • Exports Setup Wizard
    Before the NAVAX Payment Exports 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 NAVAX Payment Exports...
  • Exports Setup
    Before the NAVAX Payment Exports extension can be used, it must be set up...
  • 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...
  • Language Setup
    All necessary settings for the individual language codes are set up here. Also the Payment Notification Texts and the SEPA Mandates Texts can be stored or set up here...
  • SEPA-Direct Debit-Mandates
    With the authorization of your customer, you can collect payments directly from the customer's bank account...

• Imports

• • Imports Setup Wizard
    Before NAVAX Payment Imports can be used, its basic functionality must be set up. In the window NCP Imports Setup the general settings and defaults are defined...
  • Imports Setup
    Before NAVAX Payment Imports can be used, its basic functionality must be set up. In the window NCP Imports Setup the general settings and defaults are defined...
  • NAVAX Dropzone Setup
    In the NAVAX Dropzone Setup page the settings and defaults for the different Dropzones are defined...
  • Customs Formats
    You can define a special format for the payment file if the existing standard formats do not meet the requirements of your bank...
  • Imports Codes
    The NCP Import Codes are references to various types of transactions. Different code fields are filled depending on the imported file format...
  • 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...

• konfipay Connector

• • konfipay Connector Setup
    Here, the general settings and default settings for the konfipay Connector are defined. konfipay offers a REST-compliant web service as a communication interface, which can be integrated by Microsoft Dynamics Business Central to automate business processes...
  • konfipay Connector Access Data
    konfipay Connector operates exclusively in conjunction with a validated Finmatics account...

Tasks

• Exports

• • Working with Payment Exports
    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. NAVAX Payment Exports 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...
  • Make Payment Suggestions
    You start the Payment Suggestion in a Payment Journal (Payment Journals and Cash Receipt Journals)...
  • Create Payment File
  • Payment/Cash Receipt Journals Export
    The documentation on this page applies to the payments and cash receipt journals...
  • 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...
  • 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...
  • Payment Notification E-Mail Suggestion
    With a payment notification, you can document which open entries you want to pay or collect in the payment file after you have created the payment file. A payment notification is useful (especially for collective transfers) to make it easier for the recipient to identify the payments...

• Imports

• • Working with Payment Imports
  • Import Payment File
  • Applying Open Entries
  • 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...
  • Payment/Cash Receipt Journals Import
    The description on this help page applies to the Cash Receipt- and the Payment Journal and explains the extensions that NAVAX Payment Imports provides...

• Pay With QR Code

• • Create invoices for paying by QR code
    The NAVAX Payment has been extended with the functionality Pay with QR Code, NCP Pay with QR Code generates a standardized QR code, also called EPC QR Code, which can be scanned by many banking apps, enabling it to automatically fill in payment details such as recipient, amount, IBAN, BIC and the remittance info. This QR code created by NCP Pay with QR Code can then be placed on your invoices. This saves the customer the tedious task of typing in the data, and also means that they do not run the risk of entering incorrect data...

Reports and Analysis

• Payment Statistics
  This page views a line for each Payment File that was created from the journal...
• Importlist
• Imports Allocation Analysis
  If the indicator Show Analysis Window is set in the NCP Imports 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...
• Import General Journal Deviation

Archive

• Vendor/Customer and Bank Ledger Entries
• Clearing Entries
  In the window NCP Clearing Entries the history of all created payment files are listed...
• Payment Entries
  The action Create Payment File in the Payment Journals creates a NCP Clearing Entry with status Created, which contains information about the payment file...
• Payment Status Entries
  After a payment file is created, it can be directly transmitted to the bank using the konfipay Connector Export extension. During this process, a payment status entry is created to reflect the status from konfipay in Business Central...
• Imports
  On this page you can see the overview of the imported bank files. For each of the imported files a Import line is created, these in turn can have several transaction lines and remittance info lines...
• Account Transaction Entries
  An account transaction file is a file that contains all the transactions of a bank account, including the resulting balance. A special variant is the electronic account statement, where the account statement data, for example in online banking, is provided in file format...
• konfipay Connector Service Log Entries
  In modern web development, web services play a central role by enabling communication and data exchange between different applications and systems. These interactions leave behind extensive log entries that provide valuable information for monitoring, troubleshooting, and optimizing the services. Therefore, a structured and well-documented table for web service log entries is essential to ensure the integrity and efficiency of the web services...

Appendix

• Data Structure
• Delete Data
• QR-Code Document Data
  Payments with QR Code generates a standardized QR Code, also called Girocode or EPC QR Code, this QR Code created by NCP Pay with Code can then be placed on your invoices...
• konfipay Bank Account List
  On the konfipay Bank Account List page, all bank accounts available for synchronization in konfipay are displayed. This page opens when you click the Import Bank Accounts button on the Bank Account Setup page...
• NAVAX License Management
  The NAVAX License Management page (in older versions NAVAX License Overview or NCEX License Overview) displays the current license status of the NAVAX extensions...
• Information for Developers
  Auf der folgenden Seite sind Events aufgelistet die Ihnen dabei helfen sollen, Integrationen in NCPE Zahlungsverkehr Export und NCPI Zahlungsverker Import einzubinden...
• Installation Notes
• Possible Error messages konfipay
  Error messages occasionally occur due to a faulty file structure or more often due to missing bank authorizations. More rarely, connection interruptions or general transmission errors to the bank server are the cause. konfipay contains a sophisticated warning and notification system for this purpose...
• Release Notes
• Release Notes Payment Exports
• Release Notes Payment Imports
• Release Notes konfipay Connector Export
• Release Notes konfipay Connector Import

Docs  /  NAVAX Payment  /  General
 NAVAX Payment

Export of payment files

• Create and export payment files:

  Create payment files in the required formats and export them. Additionally, the file can be transmitted directly to your bank via the NAVAX konfipay Connector. Supported Formats:
  • Non-SEPA Credit Transfer
  • SEPA Credit Transfer
  • SEPA Direct Debit

• Simplified payment processing:

  Use simplified processes to minimize manual interventions and increase accuracy.

• Compliance with standards:

  Ensure that all payments comply with applicable legal and regulatory requirements.

Import of account transactions

• Import and process incoming payments:

  Import incoming payments and process them directly in your system. Supported Formats for NAVAX Payment Imports:

  • 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

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

    - provides information about upcoming and posted transactions and their details.

  • MT940

    - includes posted transactions on the relevant accounts. File (MT=Message Type) corresponds to a bank statement in electronic form. It contains all relevant information on bank transactions made in the SWIFT standard for the electronic transfer of account statement data.

• Automatic reconciliation with open entries:

  Automate the reconciliation of incoming payments with open invoices to simplify accounting and reduce errors.

• Efficient management of incoming payments:

  Keep track of your incoming payments and efficiently manage them in your system.

NAVAX konfipay Connector

• Consolidate financial accounting and payment processing in one system

  Integrating financial accounting and payment processing into a single system allows for seamless management of all financial processes. This leads to significant efficiency gains and better control over company finances.

• Simplified payment processing:

  Payments are transmitted from Microsoft Business Central to konfipay, reducing manual input and errors.

• Track and monitor financial transactions in real-time:

  Users can track the status of their payments in real-time, providing better control and transparency over financial transactions.

• Support multiple payment methods:

  The konfipay Connector supports various payment methods, including bank transfers, direct debits, and SEPA transactions.

• Security and compliance:

  The konfipay Connector ensures that all payments are processed securely and in compliance with current legal regulations.

konfipay - Online Payment Services

Navigation

Tell me what you want to do

Installation Notes

Docs  /  NAVAX Payment  /  Setup  /  General
 Bank Account Setup

www.konfipay.de

Home, Actions

• Import Bank Accounts

  Use the Import Bank Accounts action to import bank accounts from konfipay into Business Central. This function allows you to automatically transfer existing bank accounts from the konfipay system to your Business Central environment. This saves time and reduces errors as the account data does not need to be manually entered. During the import process, all relevant bank information is transferred and stored in Business Central, allowing you to work with synchronized data immediately.

  Note

  After importing a bank account, you still need to specify the bank account posting group on the bank account card, otherwise, there may be an error when posting.

• Download Acc. Transaction Entries

  Use this action to initiate the process of retrieving and importing account statement files from konfipay into Business Central. This converts the selected bank account's statement data into a format suitable for Business Central. After the import, the data is available as an XML file, which can then be further processed using the NCPI Payment Import.

Navigate, Actions

• Payment Journals

  Opens the most recently used cash receipt journal where you can register direct debits to customers.

• Payment Output Journals

  Opens the most recently used payment journal where you can register transfers to creditors.

• NCP Imports

  In the Payment Import window, you can import files, transfer data to payment journals or bank account reconciliations, and manage the associated journals and reconciliations. Depending on the setup, different actions and fields will be displayed.

• Agreement Document

  The action opens the agreement document in konfipay that was signed during the setup of the bank account. If the agreement document has not been imported yet, the download will be performed automatically. The agreement document defines the permissions the user receives and how access to the various functions and services of konfipay is regulated. This is particularly important for the security and protection of sensitive financial data. It establishes the legal framework under which the user can use the services of the bank or payment service provider. By signing the agreement document, the user commits to comply with certain standards and rules in handling the offered services. This creates binding obligations and ensures smooth payment processes.

Posten, Actions

• Clearing Entries

  Displays the clearing entries for this bank account. When creating a payment file, a clearing entry is generated for each record. For more information, see Archive, Clearing Entries.

• Payment Status Entries

  Opens the overview of payment status entries for this bank account. For more information, see Archive, Payment Status Entries.

• Account Transaction Entries

  Opens the overview of imported account transaction entries from konfipay. These account transaction entries can then be imported into the NCPI Import page. For more information, see Archive, Account Transaction Entries.

Bank Account, Actions

• Bank Account Card

  Use this action to open the Bank Account Card where you can set the data for this bank account.

• Bank Account Information

  This action lists all the information from konfipay related to this bank account. This function can be used to synchronize the data in Business Central with the data in konfipay.

Bank Account Setup Card

Import, Fields

Acc. Transaction File Format	Specifies in which Camt format the account transactions should be requested from konfipay.
Autom. File Acknowledge	Specifies that after successfully retrieving the account transaction entries from konfipay, the corresponding account transaction file should be automatically marked as confirmed. The file will not be downloaded again during the next retrieval from konfipay. The initial value of the field is Yes. For more information, see Transaction view

Home, Actions

• Download Acc. Transaction Entries

  This action initiates the import of the account statement files available for the selected bank account from konfipay.

Navigate, Actions

• Cash Receipt Journals

  Creates an incoming payment journal line for the bank account, for example, to record a payment received.

• Payment Journals

  Opens the list of outgoing payment journal lines where you can register payments to creditors.

• Payment Import

  In the Payment Import window, you can import files, transfer data to journal lines or bank account reconciliations, and manage the associated journal lines and reconciliations. Depending on the setup, different actions and fields will be displayed.

• Agreement Document

  The action opens the konfipay participation agreement that was signed during the setup of the bank account. If the participation agreement has not been imported yet, the download will be performed automatically.

Entry, Actions

• Clearing Entries

  Displays the clearing entries for this bank account. When creating a payment file, a clearing entry is generated for each record. For more information, see Archive, Clearing Entries.

• Account Transaction Entries

  Opens the overview of imported account statements from konfipay. These bank account statement lines can then be imported into the NCPI Import page.

• Payment Status Entries

  The action opens the overview of payment status entries for this bank account.

Bank Account, Actions

• Bank Account Card

  Displays or sets detailed information about your bank account, such as the IBAN and SWIFT code or bank account number, the currency to be used, and general data.

• Update Account Balance

  Synchronizes the account balance in Business Central with konfipay Online Payment Services.

• Retrieve Bank Account Information

  Lists all information from konfipay related to this bank account. This function can be used to synchronize the data in Business Central with the data in konfipay.

Docs  /  NAVAX Payment  /  Setup  /  General
 Bank Codes

Actions

• Download

  The campaign starts the download of the current bank codes directly from the selected main banks.
  • Österreichischen National Bank
  • Deutschen Bundesbank
  • SIX Interbank Clearing AG
  You need these bank codes to use the NAVAX Payment Exports. When you start the download, you will be asked from which bank the bank codes should be imported. Select an institution or import from all three.

  Note

  If there are already data records in the NCP Bank Code table, you will be asked how to proceed. You have the choice of how to handle the import of the data, The following options are available:

  • Create only new records - this option only creates new data records.
  • Create new records & overwrite existing data records - overwrites or updates the existing codes

  Note

  Please note that an online connection is established when downloading the bank codes.

• Import

  This action starts the import of bank codes from a JSON file. These can be codes from older systems that you have already configured and exported using the export function.

  Note

  If there are already data records in the NCP Bank Code table, you will be asked how to proceed. You have the choice of how to handle the import of the data, The following options are available:

  • Create only new records - this option only creates new data records.
  • Create new records & overwrite existing data records - overwrites or updates the existing codes

• Export

  Exports all bank codes from your database to a JSON file. This exported file can be used for importing into other databases.

  Note

  Please note that older versions of NCP Payment Export cannot be imported with the exported files in JSON format.

Docs  /  NAVAX Payment  /  Setup  /  General
 Vendor/Customer Bank Account

Set up bank accounts

Actions

• Direct Debit Mandates

  Display the direct debit mandates that you have set up to reflect agreements with debtors for the direct collection of payments from their bank account, or edit them.

• Payment Entries

  This lists all the payment entries for this bank account. For more information, see Archive, Payment Entries.

Docs  /  NAVAX Payment  /  Setup  /  General
 Countries/Regions

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.

• Initialize SEPA Countries

  With this action, all SEPA Countries are automatically created. If the entry already exists, a message is displayed to decide whether the value should be adopted.

Docs  /  NAVAX Payment  /  Setup  /  General
 Pay with QR-Code

Actions

• Bank Accounts

  In the window Bank Account Setup, all bank accounts that are required for payment transactions are stored or managed.

• Payment Methods

  Set up the payment terms that you select from customer cards or sales documents to define when the customer must pay, such as within 14 days.

Setting up a payment method for Pay with QR Code

Set up an bank account for using Pay with QR Code

Docs  /  NAVAX Payment  /  Setup  /  Exports
 Exports Setup Wizard

Page, XML Schemas Setup

Page, SEPA Countries Setup

Page, Bank Codes Setup

Page, Bank Account Setup

Page, Language Setup

Finish Setup

Docs  /  NAVAX Payment  /  Setup  /  Exports
 Exports Setup

Set Up Email

Actions

• Bank Account Setup

  In the window NCP Bank Account Setup, all bank accounts required for NAVAX Payment are defined or managed. For more information, see Setup, Bank Account Setup.

• Bank Codes

  In this window, the Branch Codes and the SWIFT Codes of the banks are defined or managed. For more information, see Setup, Bank Codes.

• XML Schemas

  XML schemas are required for SEPA and non-SEPA files creation. The assignment of the schemes to the individual bank accounts can be done in the NCP Bank Account Setup page. For more information, see Setup, Exports, XML Schemas.

Setup, Actions

• 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, General, 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, Exports, Language Setup.

• Update Bank Code URLs

  Fills or updates the bankcode URL fields. The up-to-date URL's are entered in the corresponding fields, this data is permanently updated on www.navax.app and offered as download.

System, Actions

• NAVAX License Management

  Opens the NAVAX License Management which displays the current license status of the NAVAX extensions. For more information, see Appendix, NAVAX License Management.

• Send Pmt. Notification Test Message

  This action, gives you the possibility, to test the settings of the payment notice e-mail functionality. If the function is called, the e-mail address to which the payment notice test message is to be sent must be specified in the field Test message to.

• Delete Data

  By creating a payment file, an entry is made in the clearing entries. The created payment file is also saved there. If necessary, you can use this action to remove the archived payment files from the clearing items.

  Note

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

Docs  /  NAVAX Payment  /  Setup  /  Exports
 XML Schemas

Fields

Type	Specifies the type of XML schema. Possible values are: SEPA Credit Transfer, SEPA Direct Debit and Non-SEPA Credit Transfer
Code	Specifies the code of the XML schema. This code meets the SEPA standard of the schema. You can find more information on this on Stuzza
ISO Country Code	Specifies the countries for which the schema is valid. Some countries have different requirements of the ISO standard.
Description	The field Description is a combination of the abbreviation of the field Type, the ISO country code and the rulebook version of the schema. This only applies to downloaded schemas. If you have created a schema yourself, the Description is assigned by you.
IBAN Only possible	The field IBAN Only possible indicates that the schema also supports transactions without the specification of SWIFT Code.
Dom. IBAN Only	The field IBAN Only possible indicates that the schema also supports transactions without the specification of SWIFT Code. If Dom. IBAN Only is set, domestic transactions are also allowed without SWIFT Code.
Int. IBAN Only	The field IBAN Only possible indicates that the schema also supports transactions without the specification of SWIFT Code. If Int. IBAN Only is set, foreign transactions are also allowed without SWIFT Code.
IBAN or Bank Account No. possible	The field IBAN or Bank Account No. possible indicates that the schema also supports transactions without IBAN.
IBAN or Bank Account No.	The field IBAN or Bank Account No. possible indicates that the schema also supports transactions without IBAN. If IBAN or account number is set, the account number of the recipient bank is written to the payment file if no IBAN exists.
Address Specification possible	Indicates that the schema supports address information.
Originator Address	The field Address Specification possible views whether the scheme supports address data. The field Originator Address specifies whether the address data of the originator, which was stored in the NCP Exports Setup, should be written to the payment file.
Recipient Address	The field Address Specification possible indicates that the scheme supports address data. The field Recipient Address specifies the address data of the recipient that should be written to the payment file.
Batch Booking	Specifies how the transaction is posted on the bank side. That is, whether it is a collective posting ('Yes') or an individual posting ('No').
Extended Character Set	Specifies whether the extended character set will be enabled. In general, the following characters are allowed: abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789 /-?:()., "space". Until now, the following additional characters were allowed for Austrian bank accounts: &; In addition, the following characters were automatically converted: < became "&lgt;" > became "&gt;" & became "&amp;" " became "&quot;" became "&apos;" If the field is set, the above conversion is performed in this schema. If the Extended Character Set field is not set, the & character is automatically converted to +, all other characters are replaced by a space. all other characters are replaced by a space. You can configure the character set by means of the action Allowed Character Set. For more information, see SEPA Requirements for an Extended Character Set (UNICODE Subset) - Best Practices
Umlaut Conversion	Specifies whether to use umlaut conversion when creating a payment file. Some banking institutions do not allow the use of umlauts. The conversion will: Ä or ä to an Ae or ae Ü or. ü to an Ue or ue Ö or ö to an Oe or oe
Charges Selection possible	Indicates that the schema allows the specification of charges.
Urgent Payment possible	Indicates that the schema supports urgent payments.
Instant Payment possible	Indicates that the schema supports instant payments.
Date of Specification	Specifies the date of the specification.
Last Date Modified (Schema Lines)	Shows whether, and if so, when the schema lines were last changed.
In Use	Indicates that the scheme is in use.

Setup, Actions

• Download

  Via the action Download you can download or update schemata templates.

• Import

  With the import function schemas can be imported.

• Export

  With the export function schemas can be exported.

• Init Allowed Characters

  Using this action you can change the Allowed Character Set value, for all XML Schemas, to the default.

XML Schema Card, Actions

• &Copy from

  With Copy from you can create a copy of an existing schema and then edit it.

• Allowed Characters

  With this action you can configure the allowed characters that are valid for use in payment files. This is necessary if your bank allows a different character set than the SEPA standard.

• Init Allowed Characters

  Using this action you can change the Allowed Character Set value to the default.

Docs  /  NAVAX Payment  /  Setup  /  Exports
 Language Setup

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.

Docs  /  NAVAX Payment  /  Setup  /  Exports
 SEPA-Direct Debit-Mandates

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

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.

Docs  /  NAVAX Payment  /  Setup  /  Imports
 Imports Setup Wizard

Seite Import Codes Download

Finish setup

Docs  /  NAVAX Payment  /  Setup  /  Imports
 Imports Setup

Actions

• Bank Account Setup

  In the window NCP Bank Account Setup all bank accounts that are required for NAVAX Payment are stored or managed. For more information, see General Setup, Bank Account Setup.

• Bank Codes

  In this window, the Branch Codes and the SWIFT Codes of the banks are defined or managed. For more information, see Setup, Bank Codes.

Setup, Actions

• Import Codes

  Using this action, the window NCP 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, Actions

• 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, Delete Data.

• NAVAX License Management

  Opens the NAVAX License Management which displays the current license status of the NAVAX extensions. For more information, see Appendix, NAVAX License Management.

Docs  /  NAVAX Payment  /  Setup  /  Imports
 NAVAX Dropzone Setup

Docs  /  NAVAX Payment  /  Setup  /  Imports
 Customs Formats

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 NCP Imports 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 NCP Imports can be set up. These files can be imported from other systems that you have already configured and exported using the export function.

• Export

  Use this action to export a custom format to a file. This exported file can be used for import into other databases.

Docs  /  NAVAX Payment  /  Setup  /  Imports
 Imports Codes

1. Go to NCP Payment > Setup > Imports > 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:

Actions, Setup

• 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

  With the Import action, the codes can be imported from a file. These can be codes from older systems that you have already configured and exported using the export function.

• Export

  With the Export action, the codes can be exported to a file. This exported file can be used for import into other databases.

Docs  /  NAVAX Payment  /  Setup  /  Imports
 Fixed Account Allocations

Actions

• Dimensions

  View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history.

Docs  /  NAVAX Payment  /  Setup  /  konfipay Connector
 konfipay Connector Setup

konfipay Wiki - Mandantenverwaltung

Actions

• Check Connection

  Tests the connection to konfipay with the specified settings.

• Service Log

  Opens the list of konfipay log entries.

• Web Frontend

  The action opens a new browser window with the selected konfipay portal. Here you can set up konfipay directly.

Setup, Actions

• Bank Account Setup

  In the window ''Bank Account Setup'', all bank accounts that are required for payment transactions are stored or managed.

• Import Setup

  Before the NCPI Payment Import can be used, its basic functionality must be set up. In the NAVAX Imports Setup window, you define the general settings and defaults.

• Export Setup

  Before the NAVAX Payment Exports can be used, its basic functionality must be set up. In the NCP Exports Setup window, you define the general settings and defaults.

• Bank Codes

  This action opens the page where bank data can be managed or set up per SWIFT code and bank branch number.

• Currency Exchange Rate Services

  View or edit the setup of the services that are set up to fetch updated currency exchange rates when you choose the Update Exchange Rates action.

System, Actions

• NAVAX License Management

  Opens the NAVAX License Management which displays the current license status of the NAVAX extensions.

Docs  /  NAVAX Payment  /  Setup  /  konfipay Connector
 konfipay Connector Access Data

How do I request my konfipay access?

Contact

Docs  /  NAVAX Payment  /  Tasks  /  Exports
 Working with Payment Exports

• Making a payment suggestion

  To create a payment proposal, proceed as follows:
  1. In the role center, klick NAVAX Payment > Payment Journal or Cash Receipt Journal or ☰ > NAVAX Payment > Payment Journal or Cash Receipt Journal if you are not in the Accountant role.
  2. Click on Suggest Payments (Suggest Customer Payments or Suggest Vendor Payments) The Vendor Payment Suggestion or Customer 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 Tasks, Exports, 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, Exports, Create Payment File.

• Transferring Payment File to Bank

  If you also use the konfipay Connector extension, you can transfer the payment file to the bank using konfipay. To do this, click on the action Transfer Payment File in the journal. Information on how to retrieve the status of the sent payment file can be found in the Payment Status Entries section.

• 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 NAVAX Payment - Clearing Entries
    • in the Bank Account
    • in the Payment Entries
    • or in the Journal
    For more information, see Archive, 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 NAVAX Payment - Clearing Entries and then the action Payment Entries
    • in the Bank Account
    • in the Payment Entries
    • or in the Journal
    • on Customer or Vendor with the action Payment Entries
    For more information, see Archive, 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.

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

• Payment Status Entry

  If the payment file was transmitted to the bank using the konfipay Connector, a Payment Status Entry is created. Since it sometimes happens that the bank does not process the payment file immediately, you can monitor the payment status through the Payment Status Entry.

Docs  /  NAVAX Payment  /  Tasks  /  Exports
 Make Payment Suggestions

Docs  /  NAVAX Payment  /  Tasks  /  Exports
 Create Payment File

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 Setup, Exports, 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.

Docs  /  NAVAX Payment  /  Tasks  /  Exports
 Payment/Cash Receipt Journals Export

Fields

The table includes following fields:

Posting Date	Specifies the posting date for the entry. Note Please note - it may or may not be the date ON WHICH the payment is posted. This field is copied from the payment suggestion, it is also taken into account when determining the discount.
Document Type	Specifies the type of document that the entry on the journal line is.
Document No.	The document numbers are numbered in ascending order by the payment suggestion. If a Start from Document No. is set in the payment suggestion, this is used for the first journal line.
External Document No.	Specifies a second document number. This usually refers to the numbering system used by the customer or vendor.
Account Type	Specifies the account type for the field Account No.. The following values are available: G/L Account Customer Vendor Bank Account Fixed Asset IC Partner Employee Note If you fill the journal by payment suggestion then only customer and vendor appears in the Account Type.
Account No.	Specifies the account number that the entry on the journal line will be posted to. Note This field is copied from the payment suggestion.
Recipient Bank Account	Specifies the bank account that the amount will be transferred to after it has been exported from the payment journal. Tip Learn here how to set a preferred option for the payment journal lines, if for example: a vendor has one or more bank accounts:: For more information, see Set up a preferred vendor bank account You can do the same for customers, the Preferred Bank Account Code field can also be found on the customers card in the Payments section.
Message to Recipient	Specifies the message exported to the payment file when you use the Export Payments to File function in the Payment Journal window.
Description	Specifies the description of the entry. Note This field is copied from the payment suggestion.
Currency Code	Specifies the code of the currency for the amounts on the journal line.
Payment Method Code	Specifies how to make payment, such as with bank transfer, cash, or check.
Amount	Specifies the total amount (including VAT) that the journal line consists of.
Amount (LCY)	Specifies the total amount in local currency (including VAT) that the journal line consists of.
Bal. Account Type	Specifies the type of account that a balancing entry is posted to, such as BANK for a cash account. Note This field is copied from the payment suggestion.
Bal. Account No.	Specifies the number of the general ledger, customer, vendor, or bank account that the balancing entry is posted to, such as a cash account for cash purchases. Note This field is copied from the payment suggestion.
Applied (Yes/No)	Specifies if the payment has been applied.
Applies-to Doc. Type	Specifies the type of the posted document that this document or journal line will be applied to when you post, for example to register payment.
Applies-to Doc. No.	Specifies the number of the posted document that this document or journal line will be applied to when you post, for example to register payment.
Applies-to Doc. Due Date	Specifies the due date from the Applies-to Doc. on the journal line.
Payment Type	Specifies the payment typ for the journal line. The following values are available: Non-SEPA Credit Transfer SEPA Credit Transfer SEPA Direct Debit Note The field Payment Type can already be filled by the payment suggestion. You can only change the value, in a standard setup, as long as the indicator Payment Created is not set.
Payment File Status	Specifies whether the line is ready to be exported to a payment file. 🗸 Ready indicates that the line is ready. ✉ Sent indicates that the line was sent via konfipay Connector. ✗ Check indicates that not all necessary values are missing in the line. Note Dieser Status verhindert nicht die weitere Verarbeitung, er dient nur zur Information dass die Zeile kontrolliert werden muss. 🖫 Created indicates that the line has already been exported. Tip Via the DrillDown function you can open an overview of the error messages.
Direct Debit Mandate ID	Specifies the identification of the direct-debit mandate that is being used on the journal lines to process a direct debit collection. Note This field is only available in the cash receipt journal.
Direct Debit Type	Specifies the direct debit type for the transaction. Note This field is only available in the cash receipt journal. The value of the mandate in the Direct Debit Mandate ID field is automatically applied into this field.
Direct Debit Sequence	Specifies the direct debit sequence Options: One-Off Recurrent First Last Note This field is only available in the cash receipt journal. The value of the mandate is automatically applied in this field.
Original Direct Debit Sequence	The field Original Direct Debit Sequence is being filled if the sequence is changed automatically by the file creation. If the transaction is cancelled, the direct debit sequence is reset. Note This field is only available in the cash receipt journal. The value of the mandate is automatically applied in this field.
Date of Mandate	This field will be filled when you enter the Recipient Bank Account field or via the payment suggestion and can be changed in the journal if necessary. The default value is based on the field Date of Signature from the customer bank account card. Note This field is only available in the cash receipt journal.
Payment Reference	Payment reference of the vendor (in the payment journal) or the customer (in the cash receipt journal).
One-Time Transfer	This is the indicator for a one-time instruction. Note This field is being filled by the system when a one-time bank transfer is set up. For more information, see One-Time Transfer.
Payment Status	If the file has already been created, this field is automatically filled with the option File Created.
konfipay Zahlungsstatus	Shows the status of a payment file transmitted to Konfipay. Use the AssistEdit function to access an overview of Payment Status Entries. The status can be queried at any time via the Konfipay connector, either using the Check Payment File Status action or on the Payment Status Entries page using the Update Payment Status action.
No. of Payment Entries	Number of payment entries for this journal line.
Execution Date	Date on which the payment will be executed.
Pmt. Notification	If a payment notification exists for this line, the field is automatically filled with the option "Yes". For more information, see Create Payment Notification.
Pmt. Notification No.	The number of the notification. This number is obtained from a number series that you have set up in the NCP Exports Setup in the field Payment Notification Numbers. For more information, see NCP Exports Setup - Create Payment Files.
Pmt. Notification Printed	Indicates that the payment advice note has already been printed. Note This indicator is automatically set when you execute the Payment Notification E-Mail Suggestion and print the Payment Notification after creating the Payment File.
Pmt. Notification E-Mail Sent	Kennzeichen, dass das Avis bereits versendet wurde. Note This indicator is automatically set when you execute the Payment Notification E-Mail Suggestion and send the Payment Notification vie e-mail after creating the Payment File.
Bank Payment Type	Specifies the code for the payment type to be used for the entry on the journal line. Note This field is only available in the payment journal. This field is copied from the payment suggestion.
Correction	Specifies the entry as a reversal entry. This only causes the entry to be viewed on the "wrong" side with a negative sign on various analyses.
Collective Transaction No.	This field is hidden by default. If the indicator Collective Transaction is not set in the NCP Exports Setup (For more information, see NCP Exports Setup.), collective transactions are not executed. Lines with the same collective transaction number are combined anyway. Note The aggregation only takes place if the following fields are the same for the rows: Payment type, Account Type, Account Number, Recipient Bank Account, Currency Code, Direct Debit Type, Direct Debit Sequence, Mandate ID, Date of Mandate. Lines with payment reference are always exported separately.

NCP Exports, Actions

• Suggest Vendor Payments

  This action determines open Vendor Ledger Entries according to your settings and inserts them in the journal to proceed the payment transaction. For more information, see Tasks, Suggest Payments.

• Suggest Customer Payments

  This action determines open Customer Ledger Entries according to your settings and inserts them in the journal to proceed the payment transaction. For more information, see Tasks, Suggest Payments.

• Payment Suggestion List

  Click on the action Payment Suggestion List to view the report. The payment suggestion list displays all lines waiting for payment and a summary of the amounts, grouped by bank account and message type.

• Create Payment File

  The action creates a payment file based on the lines in the journal. For more information, see Tasks, Create Payment File.

• Void Payment File

  With this action you can void a previously created payment file. The already exported file can no longer be deleted by the application (has to be done manually), but the journal lines can now be modified and you can create a new, corrected payment file.

• Payment File Test Report

  You can click on the action Payment File Test Report to check with preview whether all required informations have been entered. The report is especially helpful when you are making payments for the first time. You will then see an overview of all missing details. However, you can also try to create the payment file without this test report and correct any error messages manually.

• Clearing Entries

  When a payment file is created, an entry per file, with the status of the file is created in the Clearing Entry table. This action opens the overview of these entries. For more information, see History, Clearing Entries.

• Print Clearing List

  Runs a report that displays detailed information about the created payment file.

• Payment Statistics

  This action opens a page with information about the payment file. One line is printed for each payment file created from the journal. For more information, see Reports and Analysis, Payment Statistics.

• Notification E-Mail Suggestion

  The payment notification is useful to help the recipient to assign the payment(s). This is particularly true in the case of a collective transfer. Once the payment file has been created, you can send the payment notification by e-mail. Using the action Payment Notification E-mail Suggestion, a suggestion is first created. This suggestion will not be saved, but newly created each time you call the Payment Notification E-mail Suggestion. For more information, see Tasks, Notification E-Mail Suggestion.

• Print Notification

  The payment notification is useful to help the recipient to assign the payment(s). This is particularly true in the case of a collective transfer. Once the payment file has been created, you can send the payment notification by e-mail. Using the action Payment Notification E-mail Suggestion, a suggestion is first created. This suggestion will not be saved, but newly created each time you call the Payment Notification E-mail Suggestion. For more information, see Tasks, Notification E-Mail Suggestion.

• Renumber Document Numbers

  If you delete lines in the journal, gaps will occur in the document numbers. If this is a problem, click on the action Renumber Document Numbers. The document number is renumbered for all lines in the journal where neither Check Printed nor Payment File Created is set.

  Note

  Document Numbers that have been used in other suggestions are not renumbered.

• Retrieve Payment File Status

  With this action you can retrieve the status of a sent payment file via the konfipay Connector.

Docs  /  NAVAX Payment  /  Tasks  /  Exports
 One-Time Transfer

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.

Docs  /  NAVAX Payment  /  Tasks  /  Exports
 Payment File Summary

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.

• Show Payment File

  This action can be used to show the payment file that you have created in the payment journal with the action Create Payment File in a text editor. The file cannot be edited.

• 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 Archive, 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 Archive, 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.

Docs  /  NAVAX Payment  /  Tasks  /  Exports
 Payment Notification E-Mail Suggestion

Send Payment Notification E-Mail

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.

   Tip

   If it is desired that some Pmt. Notifications are not sent, you can remove them from the list and then continue working with the function Send All.

Print Payment Notification

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.

Docs  /  NAVAX Payment  /  Tasks  /  Imports
 Working with Payment Imports

• camt.52
• camt.53
• camt.54
• Custom

Data Structure

NCP Imports
NCP Imports Data
NCP Imports Transactions
NCP Imports Remittance Info. NCP Imports Charges

Basic workflow

1. Select NAVAX Payment > Imports on the starting page of Business Central or ☰ > NAVAX Payment > Imports if you are not in the Accountant role.
2. Click on the action Import.
3. Select the file you want to import.
4. The import is executed. If not all bank accounts have been detected automatically, click on Data and select the Bank Account manually.
5. 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.
6. Click on the action Transfer.
7. Open the Journal to clear open entries or the Bank Account Reconciliation to match the data with your bank account.
8. You can then post the imported entries.

• Import payment files

  To import a payment file provided by the bank
  1. Select NAVAX Payment > Imports on the starting page of Business Central or ☰ > NAVAX Payment > Imports if you are not in the Accountant role.
  2. Click on the action Import.
  3. Select file you want to import.

     Tip

     Files can also be imported over the Dropzone for Bank Files by Drag & Drop. For more information, see Import Tasks, Import Payment File.
     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.

• Transfer Transactions

  During the transfer, for each NCP Imports Transaction a corresponding line is created in the Journal or in the Bank Account Reconciliation. If the field Trans. Charges in the NCP Imports 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 NCP Imports Data, or just individual NCP Imports 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 NCP Imports > 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.

Docs  /  NAVAX Payment  /  Tasks  /  Imports
 Import Payment File

1. Select NAVAX Payment > Imports or on the start page of Business Central: ☰ > NAVAX Payment > Imports if you are not in the Accountant role.
2. Then click on the action Import.
3. Select the file you want to import.

   Note

   You define the possible file types in the NCP Imports Setup
4. The import is performed and loads the file in Business Central. If not all bank accounts were determined automatically, click Data and select the Bank Account Number manually.

   Note

   The next time you import a file with the same criteria, the bank account will be suggested automatically.

   Note

   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.

NCPI Dropzone for Bank Files FactBox

Functionality

Docs  /  NAVAX Payment  /  Tasks  /  Imports
 Applying Open Entries

1. If the journal is not yet open, select NAVAX Payment > Imports on the Business Central home page or ☰ > NAVAX Payment > Imports if you are not in the Accountant role. Select the desired import line and click on Open Journals.
2. Click on
   • NCP Imports > Import Suggest Application - All Lines, to create an automatic suggested application for all lines.
   • NCP Imports > 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.

      Note

      With G/L accounts, the description may not be written in the journal line. This is due to the setting Omit Default desc. in Jnl on the G/L account. The option specifies if the default description is automatically inserted in the Description field on journal lines created for this general ledger account.
   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.

      Tip

      In order to still get a suggested application, the option Keep Account Allocation can be activated in the NCP Imports Setup, so that the customer/vendor is suggested for the line, even if no document is found. 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 NCP Imports > Import Deviation - Set Filter button to only show lines that have not yet been fully applied or that have no G/L account entered in the Account No. field.
.

Docs  /  NAVAX Payment  /  Tasks  /  Imports
 Bank Account Reconciliation

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.

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

Actions, Process

• Suggest Lines

  Create bank account ledger entries suggestions and enter them automatically.

• Import Data Card

  The Data from the NCP Imports is displayed here. Each row in the NCP Imports 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 Setup, Imports, 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.

Docs  /  NAVAX Payment  /  Tasks  /  Imports
 Payment/Cash Receipt Journals Import

Aktions, NCP Imports

• Import Suggest Application - All Lines

  Use this function to create balance suggestions for all lines in this journal that have not been balanced already. If the option Display analysis window is set in the NCP Imports Setup, a page with the information of the preselection is displayed. If the window is closed with OK, the suggestion is copied to the journal.

  Note

  It is generally recommended to activate the window for analysis tasks. The reason for this is that at the time of confirmation with OK it is no longer possible to guarantee that all entries are still available and open for balancing. An error message or a notice may be shown that another user has changed data or that balancing can no longer set.

• Imports Suggest Application - Line

  Use this function to suggest a application for the selected line. If the option >Display analysis window is set in the NCP Imports Setup, a page with the information of the preselection is displayed. If the window is closed with OK, the suggestion is copied to the journal.

  Note

  It is generally recommended to activate the window for analysis tasks. The reason for this is that at the time of confirmation with OK it is no longer possible to guarantee that all entries are still available and open for balancing. An error message or a notice may be shown that another user has changed data or that balancing can no longer set.

• Imports Fixed Account Allocations

  If the balance suggestion should always assign specific transactions to a fixed G/L account, customer, vendor or bank account, you can set up fixed account allocations for this. Fixed account allocations are maintained or created in the NCP Imports Setup window, but can also be accessed via the journal or bank account reconciliation.

• Imports Deviation - Set Filter

  This action sets filters on the journal lines for which full adjustment is not possible.

• Imports Deviation - Remove Filter

  This action deletes the filters on the journal lines for which full adjustment is not possible.

• Imports Deviation - Print

  This list will show all journal lines for which the allocations has not been completely set.

• Imports Transaction Card

  Opens the import transaction card in which all important information about the Transaction from the NCP Imports is clearly displayed.

Docs  /  NAVAX Payment  /  Tasks  /  Pay With QR Code
 Create invoices for paying by QR code

Creating an invoice for paying with QR code

1. Create an invoice, either a sales invoice or a service invoice
.
2. Select the customer for which the invoice should be created
.
3. Check the Payment Method, this must have the NCP Pay with QR-Code flag enabled. If there is no payment form yet, create one. For more information, see Setup, Pay with QR Code. section Setup a Payment Method for Pay with QR Code.
4. You can specify which of your bank accounts to use for generating the Pay with QR Code code, to do this select the desired account in the Company Bank Account Code field.

   Tip

   You can also store a bank account to be used by default for QR code creation, to do this go to the Bank Account Setup and specify a bank account by activating the Bank Account for Pay with QR Code box.
5. It is recommended to fill one of the fields Your Reference or External Document Number to be able to create a unique reference for the QR code. Using this QR code, you can then assign the payments to the customer ledger entries. NAVAX Payment Imports can help you do this. For more information, see Setup, Pay with QR Code.
.
6. Post the invoice. If Pay with QR code active in the QR Code Setup is enabled, a QR code document data entry will be created and the generated reference will be written to the customer ledger entry. It is possible to configure the generation of the reference text according to your requirements, For more information, see Setup, Pay with QR Code.
.

Docs  /  NAVAX Payment  /  Reports and Analysis
 Payment Statistics

Fields, General

Fields, Details

Docs  /  NAVAX Payment  /  Reports and Analysis
 Importlist

Docs  /  NAVAX Payment  /  Reports and Analysis
 Imports Allocation Analysis

Actions

• Transaction Card

  Opens the import transaction card in which all important information about the Transaction from the NCP Imports is clearly displayed. For more information, see Tasks, Imports, Working with Payment Imports.

• 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, Imports, Fixed Account Allocations.

Docs  /  NAVAX Payment  /  Reports and Analysis
 Import General Journal Deviation

Docs  /  NAVAX Payment  /  Archive
 Vendor/Customer and Bank Ledger Entries

Bank Account Ledger Entries

Bank Account Ledger Entries, Actions

• Payment Entries

  Opens the overview of the Payment Entries with reference to this Bank Account Ledger Entry. For more information, see Archive, Payment Entries.

• Clearing Entries

  Opens the overview of the Clearing Entries with reference to this Bank Account Ledger Entry. For more information, see Archive, Clearing Entries.

Docs  /  NAVAX Payment  /  Archive
 Clearing Entries

Actions, Payment File

• 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 Tasks, Exports, Create Payment File.

• Show Payment File

  This action can be used to show the payment file that you have created in the payment journal with the action Create Payment File in a text editor. The file cannot be edited.

• Void Payment File

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

• Send Payment File

  With this action, you can send the payment file that you created before via Create Payment File. The payment file will be send to konfipay which will check and transmit the file to the bank.

• Check Payment Status

  With this action, you can retrieve the status of a sent payment file.

Actions, Reports

• Clearing List

  This List contains information about the Clearing Entries.

Actions, Notification

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

Actions, Entry

• Payment Entries

  Opens the list of Payment Entries that refers to this Clearing Entry. For more information, see Archive, Payment Entries.

• Bank Account Ledger Entries

  Opens the overview of the Bank Account Ledger Entries that refer to this Clearing Entry.

• Payment Status Entries

  The action opens the overview of payment status entries for this bank account.

Docs  /  NAVAX Payment  /  Archive
 Payment Entries

Actions

• Navigate

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

• Payment Remittance Entries

  Opens the overview of the Payment Remittance Entries with reference to this NCP Payment Entry.

• 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 Archive, Clearing Entries.

Payment Remittance Entries

Payment Remittance Entries, Actions

• Navigate

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

Docs  /  NAVAX Payment  /  Archive
 Payment Status Entries

Docs  /  NAVAX Payment  /  Archive
 Imports

• Import a payment file into Dynamics 365 Business Central and transfer it to a journal. For more information, see Tasks, Imports, Import Payment File.
• Applying open entries. For more information, see Tasks, Imports, Applying Open Entries.
• Perform a reconciliation with your bank account. For more information, see Tasks, Imports, Bank Account Reconciliation.

Fields

Import Date	Shows when the data was imported.
Import Time	Shows when the data was imported.
Import User ID	Shows from which user the data was imported.
File Format	Shows the file format of the imported file.
Imported File	Shows the name of the imported file.
Archived Import File Exists	Shows you if an archived import file already exists.
No. of Data	Shows the number of imported data entries.
No. of Data without Bank Allocation	Shows 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 NCP Imports Data either by clicking in the field or by selecting the action Navigate > Data.
Bank Account No.	If the NCP Imports 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 Name	If the NCP Imports 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 IBAN	If the NCP Imports 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 Transactions	Shows the number of imported transactions.
Open Journal Lines	Shows 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 NCP Imports 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 Lines	Shows if data has been transferred to an general journal and general journal lines have been posted. Note Depending on the setting used in the NCP Imports 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 Reconciliations	Shows if data has been transferred to an reconciliation and if there are open reconciliation lines. Note Depending on the setting used in the NCP Imports 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 Lines	Shows if data has been transferred to an reconciliation and reconciliation lines have been posted. Note Depending on the setting used in the NCP Imports 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 Statements	Shows if data has been transferred to a bank account reconciliation and posted statements are available. Note Depending on the setting used in the NCP Imports 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 Lines	Shows 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 NCP Imports 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 Date	Shows when the file was created (File info: CreDtTm).
Message Time	Shows when the file was created (File info: CreDtTm).
Message Recipient Name	Shows the name of the recipient of the file (file info: MsgRcpt Nm).
Additional Info.	Shows additional information (file info: AddtlInf).
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 Tasks, Imports, Working with Payment Imports.

• Export Archived Import File

  Starts the download of the archived import file.

Actions, Transfer

• Transfer

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

Actions, Report

• Import List

  This list shows information about the imported file.

Actions, Navigate

• Data

  Here the Data from the NCP Imports are listed. Each line in the NCP Imports window can contain several data lines, which in turn can contain several transactions. The transactions, in turn, can contain several remittance lines and charges.

• Transactions

  Here the Transactions from the NCP Imports are listed. Each line in the NCP Imports window can contain several data lines, which in turn can contain several transactions. The transactions, in turn, can contain several remittance lines and charges.

• 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 NCP Imports Setup, in the field camt.053 - Statement or MT940 - Account 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 NCP Imports Setup, in the field camt.053 - Statement or MT940 - Account 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 NCP Imports Setup, in the fields camt.053 - Account Statement, camt.054 - Debit Credit Notification, MT940 - Account Statement or Custom.

• Additional Info.

  Opens the card with the additional information from the Group Header (GrpHdr) of the import.

Import Data

Fields

Statement No.	Shows the bank statement number (file info: LglSeqNb). The lookup function opens the NCP Imports Data Card page, this provides a better overview of the bank statement.
Statement Date	Shows the date of the bank statement (file info: CreDtTm).
Statement from	Shows the statement period (file info: FrToDt FrDtTm).
Statement to	Shows 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 Name	If the NCP Imports 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 IBAN	If the NCP Imports data all have the same bank account, the IBAN is displayed here. If the accounts are different, no value is displayed.
No. of Balances	Shows the number of imported balances in the bank statement. The lookup function opens the NCPI Payment Import Balances page.
No. of Transactions	Specifies the number of imported transactions. The Lookup function opens the NCPI Payment Import Transactions page.
Open Journal Lines	Shows that data has been transferred to a journal and that there are open journal lines. The lookup function opens the corresponding journal. Note Depending on the setting used in the NCP Imports 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 Lines	Shows if data has been transferred to a journal and journal lines have been posted. Note Depending on the setting used in the NCP Imports 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 Lines	Shows if data has been transferred to a bank account reconciliation and open reconciliations exist. The lookup function opens the corresponding reconciliation. Note Depending on the setting used in the NCP Imports 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 Lines	Shows 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 NCP Imports 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 Statements	Shows if data has been transferred to a bank account reconciliation and posted statements exist. Note Depending on the setting used in the NCP Imports 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 Lines	Shows if data has been transferred to a bank account reconciliation and posted statement lines exist. Note Depending on the setting used in the NCP Imports 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 Code	Shows the ISO bank currency code of the imported data (file info: Acct Ccy).
Additional Information	Shows additional information of the bank statement (file info: AddtlInf). The lookup function opens the NCP Imports Additional Information page.
Closing Booked last Statement	Shows the closing balance of the last booked account statement.
Sum Transaction Amount	Shows the total of the booking amounts from the imported bank file.
Closing Booked	Shows the current closing balance, reduced by the booking amounts from the imported bank file.
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.

Import Data, Actions

• Suggest Bank Account

  This function can help to suggest already used bank accounts.

• Transfer

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

• Balances

  The balances from the NCP Imports are listed here.

• Transactions

  The transactions from the NCP Imports are listed here. Each row in the NCP Imports window can contain multiple data rows, which in turn can contain multiple transactions. The transactions, in turn, can contain multiple payment remittance entries and expenses.

• Additional Info.

  Öffnet die Karte mit den Zusatzinformationen aus dem Group Header (GrpHdr) des Imports.

• Open Reconciliations

  This action opens the page Bank Account Reconciliations, where the transferred 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.

Import Balances

Import Transactions

Import Transactions, Actions

• Transfer

  Allows lines from the NCP Imports 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 option Transfer Charges in the NCP Imports 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 NCP Imports Data, or just individual NCP Imports Transactions. For more information, see Tasks, Imports, Working with Payment Imports.

• Remittance Info.

  Opens the overview of the Remittance Info lines for this Transaction. Each row in the NCP Imports 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.

• Charges

  Opens the overview of charges for this Transaction. Each row in the NCP Imports 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.

• Additional Info.

  Opens the overview with the Additional Information for the selected transaction. (Stm/Rpt/Ntfctn)

Import Charges

Import Remittance Infos

Import Additional Infos

Docs  /  NAVAX Payment  /  Archive
 Account Transaction Entries

Process, Actions

• Transfer Account Transaction File

  The action loads the account transaction File. If the Automatic Import after Download setting is enabled in NCP Imports Setup, the file is immediately imported into NCPI Import.

• Acknowledge Account Transaction File

  The action acknowledges the account transaction file. Acknowledged account transaction entries can only be deleted through the konfipay portal.

• Delete Acknowledged Account Transaction Entry

  The action allows you to delete acknowledged account transaction entries. Acknowledged account transaction entries can only be restored through the konfipay portal. You can delete either all or selected records.

Related, Actions

• NCP Imports

  In the NCP Imports window, you can import files, transfer data to journals or bank account reconciliations, and manage the associated journals and reconciliations. Different actions and fields are displayed, depending on the setup. Tasks, Imports, Working with Payment Imports

Docs  /  NAVAX Payment  /  Archive
 konfipay Connector Service Log Entries

Actions

• Show Request/Response

  View detailed information about what has been sent to and returned from the service. The information can be useful for technical support.

Docs  /  NAVAX Payment  /  Appendix
 Data Structure

Exports

NCP Clearing Entries
NCP Payment Entries
NCP Payment Remittance Entries NCP Payment Posting Entries

Imports

NCP Imports
NCP Imports Data
NCP Imports Transactions
NCP Imports Remittance Info. NCP Imports Charges

Docs  /  NAVAX Payment  /  Appendix
 Delete Data

Exports

Imports

Docs  /  NAVAX Payment  /  Appendix
 QR-Code Document Data

Fields

Document Type	Shows the Document Type of the Document for which the QR Code Document Data entry was created. The following options are available: Sales Invoice Service Invoice
Document No.	Shows the Document No. of the document associated with this QR Code Document Data entry.
IBAN	Shows the IBAN of the recipient with which the QR Code Document Data entry was created.
SWIFT/BIC	Shows the SWIFT/BIC of the recipient used to create the QR Code Document Data entry (required in version 001; optional in version 002 within the EEA).
Receiver Name	Shows the receiver's name that was used when creating the QR Code Document Data entry.
Reference Text	Shows the Reference Text that was used when the QR Code Document Data entry was created.
Amount	Shows the Amount that was used to create the QR Code Document Data entry.
Currency Code	Shows the Currency that was used when creating the QR Code Document Data entry.
Purpose Code	Shows the Purpose Code that was used when creating the QR Code Document Data entry (max. four-digit code analogous to the text key according to DTA method, optional). The purpose code corresponds to the text key known from the DTA procedure in order to be able to classify transfers and direct debits automatically. Payers and payees, as well as the payment service providers involved in payment processing, can use a purpose code to automatically identify payments (e.g., salary payments) and use the information, for example, for the automated calculation of account maintenance fees or the granting of overdraft facilities. Regular payments, such as salaries or capital-forming payments, should therefore always be made using a purpose code. For more information, see Purpose-SEPA-Codes
QR-Code Id.	Shows the unique Id. that was generated when the QR Code Document Data entry was created.
QR-Code Size"	Shows the QR Code Size of the QR Code Document Data entry. The following values are available for selection: Small Medium Large
Version	Shows the Version of the QR Code Document Data entry. If Version 001 is selected, the BIC must be specified. With Version 002 the BIC is optional to specify or to leave blank.
Function	Shows the Function that was used to create the QR Code Document Data entry. The function is defined by the key value: SCT - SEPA Credit Transfer
Display	Shows the Display of the QR Code Document Data entry. This Introduction will be displayed to the user after the code has been captured and will provide a brief textual explanation of what they are about to initiate. This text is not reflected in the data transferred in the payment transaction.
Text	Shows the Message of the QR Code Document Data entry. This Message will be displayed to the user after the code has been captured and will provide a brief textual explanation of what they are about to initiate. This text is not reflected in the data transferred in the payment transaction.
Data	Displays the data used to generate the QR code. Click the field to display the formatted text in a new window.
QR-Code	Shows the generated QR Code of the QR Code Document Data Entry.

Actions

• Show Document

  Opens the page for the selected document.

Docs  /  NAVAX Payment  /  Appendix
 konfipay Bank Account List

Actions

• Open konfipay Bank Accounts

  The action opens the konfipay Portal with the list of bank accounts. An appropriate permission is required to open this overview.

Docs  /  NAVAX Payment  /  Appendix
 NAVAX License Management

Trial Version

Request License

Activate/Update License

Terms & Conditions

https://www.navax.app/EULA.php?L=en

Data Security

https://www.navax.app/privacyStatement.php?L=en

Submit Rating

Docs  /  NAVAX Payment  /  Appendix
 Information for Developers

Docs  /  NAVAX Payment  /  Appendix
 Installation Notes

Publish and Install the Extension

[Microsoft Learn] Business Central - Publishing and Installing an Extension

Dependencies

• NAVAX Payment Base

  ID: 35bfcd3e-32be-4797-bc00-d873d28542ad

• NAVAX Extension Base

  ID: 2f4cb42d-6e2a-4708-a5e2-3ec5f32f20e9 For more information, see [Docs] NAVAX Extension Base - General

• NCPK konfipay Connector Base

  ID: 4d356001-b546-444b-ab32-9374839fbca3

On-Premises

• 1001710 NCPE Payments Export by NAVAX
• 1001730 NCPI Payments Import by NAVAX
• 1010860 Extension Base by NAVAX

• 70714845 NAVAX konfipay Connector Export
• 70714840 NAVAX konfipay Connector Import

External Addresses

• https://portal.konfipay.de, https://dzbank.konfipay.de, https://portal.konfipay.ch

  For the use of konfipay Online Payment Services to communicate with the bank, access to https://portal.konfipay.de must be granted.

  Public IP of portal.konfipay.de and dzbank.konfipay.de for firewall whitelisting:

  Inbound: 20.61.2.93, Port: TCP/443 Outbound: 20.107.20.80, Port: TCP/443 Depending on the konfipay instance, the outgoing IP address for the connection to bank data centers may vary.

  Public IP of portal.konfipay.ch for firewall whitelisting:

  Inbound: 164.128.146.116, Port: TCP/443 Outbound: 164.128.146.116, Port: TCP/443 Depending on the konfipay instance, the outgoing IP address for the connection to bank data centers may vary.

  Checking the connection to https://portal.konfipay.de, https://dzbank.konfipay.de or https://portal.konfipay.ch using PS:

  Test-NetConnection [konfipay.de/konfipay.ch] -port 443 (PS must be performed with the M-Tier service user)

• https://www.navax.app

  For licensing, calling the online help and performing some actions, access to https://www.navax.app must be granted.
  
  Public IP from www.navax.app for setting firewall access:
  94.136.22.236, Port: TCP/443
  
  Checking the connection to https://www.navax.app using PS:
  Test-NetConnection navax.app -port 443
  (PS must be performed with the M-Tier service user)
  
  CRL Servers
  In addition, the following CRL Servers must also be accessible for the certificate check:
  https://certificates.godaddy.com/*
  http://crl.godaddy.com/*
  or their IP: 192.124.249.36

• https://qr01.navax.com:8080

  To create the QR Codes via the CreateQRCodeRedSoft function, access to https://qr01.navax.com:8080 must be granted.
  
  Checking the connection to https://qr01.navax.com:8080 using PS:
  Test-NetConnection qr01.navax.com -port 8080
  (PS must be performed with the M-Tier service user)

Docs  /  NAVAX Payment  /  Appendix
 Possible Error messages konfipay

How errors are identified

Structure of the error codes

List of all error codes and error messages with explanation

Docs  /  NAVAX Payment  /  Appendix
 Release Notes

Payment Exports

Payment Imports

konfipay Connector Export

konfipay Connector Import

Docs  /  NAVAX Payment  /  Appendix
 Release Notes Payment Exports

Version 21.2.2.3

• Modifications

• • Order of the fields SWIFT Code and IBAN changed on the Vendor/Customer Bank Account List and Vendor/Customer Bank Account Card pages.

• Corrections

• • When using the Business Central standard functionality Apply Entries with NAVAX Payment Exports installed, a permission error occurred if the user was not assigned the NCPE permission.
  • Fixed an error in the calculation of the discount tolerance. If the discount tolerance was not activated in the General Ledger Setup (no discount tolerance period specified or 0D set) and the following constellations occurred:
    • Discount date and discount tolerance date are the same both discount and discount tolerance were posted, leaving the payment entry with an open balance.
    • Discount tolerance date is after the discount date discount date has passed and discount tolerance date applies - the discount tolerance was posted with the amount of the discount, even though the discount tolerance amount = 0 was entered in the entry.
  • In the vendor payment suggestion, the bank accounts were not filled if the Preferred Bank Account field was filled in the entry.
  • In the vendor payment suggestion, entries were not suggested because the filter on the Exported to Payment File field or the value was set incorrectly.
  • After executing a payment suggestion, an incorrect message was displayed at the end. The message was confusing as it stated that there could still be suggestions with other currencies.

Version 21.2.2.2

• Modifications

• • Update of the NAVAX Payments Base extension.
  • NAVAX Extension Base extension update.
    For more information, see [Docs] NAVAX Extension Base - Release Notes

• Corrections

• • When applying vendor/customer ledger entries, an error message occurred due to missing permissions if the user was not assigned the permission set NCPE, NAVAX Payment Exports.

Version 21.2.2.1

• Improvements

• • The action Show Payment File has been added to the page NCP Exports Payment File - Summary. For more information, see Tasks, Exports, Payment File Summary.

• Modifications

• • When using direct debit mandates for multiple bank accounts, it is now ensured that the specific values of the respective mandate are used in the payment suggestion instead of adopting the values of the master mandate.

Version 21.2.2.0

• Improvements

• • The setup of the placeholder character for the SEPA Direct Debit Mandate ID Separator has been added to the NCP Exports setup. For more information, see Setup, Exports, SEPA-Direct Debit-Mandates.
  • When using master mandates, the values of the master mandate are now entered or exported in the payment suggestion and in the create payment file function.
  • Actions for creating and canceling payment files as well as displaying the payment statistics have been added to the three-dot menus in the journal lines.
  • XML Schema SDD - AT - Rulebook 2023 - Version 4 has been added to the download.

• Modifications

• • Removal of obsolete code parts.

• Corrections

• • When using the function Renumber Document Numbers, it could happen that numbers were assigned twice if lines with the status Payment File Status Created were already present in the journal lines.
  • Correction in the XML Schema SDD - AT - Rulebook 2023 - Version 2 of the node <ReqdColltnDt>.
  • If the main bank account of a customer/vendor was changed via the journal lines, the field Preferred Bank Account Code on the customer/vendor was not updated. This led to incorrectly filled bank accounts and payment methods in the Payment Suggestion.
  • When exporting payment files, the field Exported in Payment File in the journal lines and the customer/vendor entries was not set correctly. An entry was marked as exported even though there was still an open balance.

Version 21.2.1.1

• Modifications

• • The functionality for employee payments has been removed from NCP Payment Exports.
  • When creating a payment file, only the part of the direct debit mandate ID that is before the underscore (“_”) is now exported. This additional functionality allows the same direct debit mandate ID to be used for multiple customers.

• Corrections

• • The journal line check in the payment suggestions has been revised. Now, all journals are automatically checked, and already suggested or balanced entries are listed in an overview. The option Check Other Journal Batches has been removed.
  • The document type in the payment suggestion list was not translated into the respective user language for lines of a overpayment.
  • In the payment suggestion list, the incorrect amount was printed in case of overpayment.

Version 21.2.1.0

• New Product Name

• • The NCPE Payments Export extension has been renamed to NAVAX Payment Exports.

• Improvements

• • Menu structure in the accountant role center tidied up.

• Modifications

• • The logo of the extension has been changed.

• Corrections

• • The payment suggestions ignored entries with document type Refund when the option Check Other Journal Batches was activated.
  • In the Payment Suggestion List, a line of type Payment was printed if a suggested document was within the Discount Tolerance.
  • If a bank account was specified in the NCP Preferred Bank Account Code field on a purchase invoice, it was not included in the entries when posting.
  • Correction of the text af the error message that occurred when checking the payment status in a ledger entry line that had already been exported or sent.

Version 21.2.0.4

• Improvements

• • Redesign of the menu structure in the payment journal pages and cash receipt journal pages.

• Modifications

• • If a value was entered in the Creditor/Customer Entry in the Recipient Bank Account field, it was previously ignored in the payment suggestion. The logic of bank account determination in the payment suggestion has now been revised: If a value is present in the Recipient Bank Account field, it will be used. Additionally, the bank account determination for debtor entries has been expanded to consider a direct debit mandate ID selected in the documents, which overrides everything else. If neither applies, the bank account will be searched based on the External Bank Account Search option in the NCPE Payments Export Setup.
  • Removal of obsolete code parts.
  • User experience improvements.

• Corrections

• • After creating a payment file, before the NCPE Payment File - Summary page was opened, a message with an additional placeholder appeared.
  • If the option Check Other Ledger Sheet Names was activated during the payment proposal, it led to an error message if the Payment File Status for an entry in another ledger sheet was already set to File Created

Version 21.2.0.3

• Corrections

• • During the installation of NCP Payment Base, an entry was mistakenly created in the license management. This error has been fixed, and an update routine has been created to delete the entry.

Version 21.2.0.2

• Modifications

• • The customer and vendor bank account cards have been revised so that the fields IBAN and SWIFT Code are no longer displayed as mandatory.
  • The check in the payment and cash receipt journal has been revised. For non-SEPA transfers, the fields IBAN and SWIFT Code are no longer required, which correctly reflects the status.

• Corrections

• • Under certain constellations, there were data locks in the Payment Journal page, which prevented further work.

Version 21.2.0.1

• Corrections

• • The option Check Other Journal Batches in the NCPE Suggest Customer Payments or NCPE Suggest Vendor Payments was not taken into account.
  • When creating a direct debit or payment suggestion with the option Incl. Debtors with Credit Balance - Total or Incl. Creditors with Credit Balance - Total, some creditors/debtors were not taken into account even though they did not have a credit balance.

Version 21.2.0.0

• Important

  For On-Premises an update of the License or the following granules is required:

  • 1001710 NCPE Payments Export by NAVAX

• Improvements

• • Preparation for integration of konfipay Connector
  • Change in the payment method field in the ledger entries. Now only the available payment methods are displayed in the respective ledger entry.
  • The download of bank codes has been improved. Previously, it was necessary to maintain the URLs for downloading the bank codes before the download could be initiated. This has been simplified by automatically starting the download as soon as the bank code download is triggered.
  • The download of bank codes now occurs in JSON format to improve download performance.
  • New option "Summary after creation" added to the NCPE setup. For more information, see Setup, Exports, Exports Setup.
  • For creditor/customer bank accounts, the SWIFT code field has been expanded with a lookup to the SWIFT Codes table.
  • New option "Yes - Structured" added to recipient address in the XML schemas. This is required to comply with the new specification of the SEPA schemas implementing the ISO20022 standard.
  • Functionality to display the payment file in the clearing entries added.

• Modifications

• • NAVAX Extension Base extension update.
    For more information, see [Docs] NAVAX Extension Base - Release Notes
  • The customer payment suggestion in the payment journal page has been renamed to Customer Direct Debit suggestion.
  • The payment file status field in the ledger entry lines is no longer displayed in bold and red as it caused confusion, if a line needs to be checked, it is now displayed in yellow.

• Corrections

• • When downloading bank codes from multiple sources, the source was not indicated in the notifications or error messages. This has now been corrected as it is very helpful for analysis to know which source caused an event.
  • Some tooltips have been corrected.
  • Filters have been applied to the debtor payment suggestion for creditor entries.
  • Revision of the update or display of the payment status in the payment ledger entries.

Version 21.1.7.3

• Modifications

• • NAVAX Extension Base extension update.
    For more information, see [Docs] NAVAX Extension Base - Release Notes

• Corrections

• • There was an error during posting or preview posting in the Cash Receipt Journals when a Refund was present in the lines.

Version 21.1.7.2

• Modifications

• • Download URLs for the Bank Codes have been updated.

• Corrections

• • In the payment and cash receipt journals, the field Payment File Status showed Check if no SWIFT Code was specified on the customer/vendor bank account, even though the XML schema used, which was specified on the bank account, had Dom. IBAN Only enabled. In the SEPA region, specifying the SWIFT Code is generally not necessary.

Version 21.1.7.1

• Note

  This version is also available as a downgrade version for Business Central 20 and 19.

• Corrections

• • The function Consider Payment Discount Tolerance considered the discount tolerance date but did not reduce the amount in the ledger entry by the discount.

Version 21.1.7.0

• Important

  For On-Premises an update of the License or the following granules is required:

  • 1001710 NCPE Payments Export by NAVAX

• Improvements

• • The logic behind the Payment File Status field has been improved in the Gen. Journal Line table. The settings and parameters of the bank account are now also taken into account.
  • On the pages Payment Journal and Cash Receipt Journals the info box Payment File Error has been added. This info box shows the errors per journal line that would prevent the payment file from being exported.
  • In the NCPE Payments XML Schemas the Extended Character Sets have been extended for all XML schemas, the characters äüöÄÜÖß have been added since most banks accept these characters in the payment files.
  • In NCPE Suggest Vendor Payments and NCPE Suggest Customer Payments, the options Consider Payment Discount Tolerance have been added. Previously, the value of the Pmt. Discount Date field from the entry was taken into account. For more information, see Tasks, Exports, Make Payment Suggestions.
  • New option Without Reductions added to the reports NCPE Suggest Vendor Payments and NCPE Suggest Customer Payments. The indicator is used to ensure that entries that would reduce the amount (credit memos, reductions) are not included in the payment suggestion. For more information, see Tasks, Exports, Make Payment Suggestions.

• Modifications

• • Calling up the pages Bank Account Setup and Pay with QR-Code from the role center has been changed. Previously, the pages were opened in view mode, so editing had to be activated on the pages before settings or changes could be applied.
  • NAVAX Extension Base extension update.
    For more information, see [Docs] NAVAX Extension Base - Release Notes

• Corrections

• • In the payment suggestions, refunds were suggested although the option Summarize per Vendor/Customer was activated, so an error occurred when creating the payment file.
  • After calculating the payment suggestion, vendors/customers which had a credit balance in total (e.g. an invoice has already been posted but not yet due in this payment suggestion) were incorrectly included in the suggestion and written as refunds in the journal, which blocked the creation of a payment file.
  • In the NCPE Payments Export Setup an incorrect report was specified as Pmt. Notification Report ID, this has been corrected and an upgrade routine has been created to correct the report ID. The initial value has also been corrected.
  • Error in the creation of the QR code when the function Pay with QR-Code was activated. If no default bank account was set up for payments with QR code, the process was canceled after selecting the bank account to be used for QR code creation.
  • Due to the installation of the extension, the totals were not always printed on the A4 documents when using the RDLC report layouts.
  • If the option Summarize Per Vendor/Customer has been selected in the payment suggestion, the dimensions have not been transferred consistently to the journal lines.
  • In the assisted setup, the name of the field Creditor Identifier (CI) was previously County.

Version 21.1.6.5

• Improvements

• • Improvement of user experience - actions in the Payment- and Cash Receipt Journal pages have been reorganized.
  • Improvement for developers: The propagateDependencies option is now set.

• Modifications

• • Update of the NCP Payments Base extension.

Version 21.1.6.4

• Corrections

• • When creating a Purchase Invoice with a Payment Method linked to a G/L account to automatically apply the invoice immediately with a payment during the posting process, the vendor ledger entries of the invoice have been posted with balance 0 but are incorrectly posted with Open=YES.

Version 21.1.6.3

• Improvements

• • It is now possible to block collective transactions at vendor level. If the Collective Transaction Not Allowed option is activated for a vendor, no collective transactions will be created for the vendor in the Payment Journal.

• Corrections

• • Error correction of the collective transactions functionality. In report 70322082 NCPE Create Payment File, the variable AllowCollectiveTransactions could be changed via an event. Setting it to false had an impact on Collective Transactions in conjunction with Payment Reference or One-Time Transfers.

Version 21.1.6.2

• Corrections

• • In the report Payment Suggestion List, the payment discount is shown twice because the payment discount tolerance was calculated incorrectly although a payment discount was already granted.
  • Obsolete events have been revised. The OnUpdateTempPaymentBufferFromCustomerLedgerEntry and OnBeforeUpdateGnlJnlLineDimensionsFromTempPaymentBuffer events in the NCPE Suggest Customer Payments report are available again.
  • When importing data (SEPA schemes, bank codes), the number of overwritten data records was not displayed correctly.

Version 21.1.6.1

• Corrections

• • Payment discount tolerance was drawn incorrectly although a discount was to be granted if the Block Payment Tolerance value was changed on the customer/vendor.
  • GUI improvements in Cash Receipt and Payment Journals concerning the Payment File Status.
  • The import function Initialize SEPA Countries has been redesigned. Previously, there was a query for changes to the NCP SEPA field. This is not necessary as it is a field of the NCP Payments app and can therefore be overwritten.
  • The value of the field Payment File Status was determined incorrectly when the function Summarize per Customer/Vendor was selected in the payment suggestion.

Version 21.1.6.0

• Important

  For On-Premises an update of the License or the following granules is required:

  • 1001710 NCPE Payments Export by NAVAX

• Improvements

• • On the NCPE Payments XML Schema or NCPE Payments XML Schemas page a new action Allowed Character Set has been added. With this action you can configure the allowed characters which are valid for the purpose in the payment file. This is necessary if your bank allows a different character set than the standard of the SEPA scheme.
  • A new field Umlaut Conversion has been added to the NCPE Payments XML Schema table. This can be used to control whether or not umlauts should be converted for usage purposes. The conversion converts e.g.: an Ä to an Ae.
  • New field Pmt. Notification Report ID added in the NCPE Export Setup. With this, a possibility was created to define own report layouts for the payment notifications.
  • New fields Payment Notification Report ID, Clearing List Report ID, SEPA Mandate Report ID, Zlg. Default List Report ID and their captions have been added to the NCPE Export Setup. Herewith a possibility was created to deposit own report layouts for the printouts.
  .
  • When updating and reinstalling, the NCP SEPA indicator in the Countries/Regions table were updated each time, this has now been disabled - so installation should be faster.

• Modifications

• • Some actions have been renamed and rearranged in the payment journals.
  • The action Initialize NCP SEPA Countries on the page Countries/Regions has been redesigned. The function now creates a record if it does not exist. If an entry exists, the record will be updated.

• Corrections

• • Actions and fields of NCPE Payments Export and NCPI Payments Import have been moved. Before it was not possible to use Business Central standard for e.g.: Payment File Export if NCPI Payment Import was installed. The same applies to NCPE Payments Export.
  • The payment file status field was not updated after creating a payment file. The error has been fixed.
  • Actions in the payment journals were cleaned up.
  • The captions in the NCPE Initial Setup Wizard were not translated into German.
  • In the NCPE Initial Setup Wizard, the link to the NCP Payment Language Setup was incorrect, the Languages page was opened instead of this page.
  • The action Initialize NCP SEPA Countries on the page Countries/Regions has been renamed to Initialize SEPA Countries.

Version 21.1.5.0

• Improvements

• • The Check Other Journal Batches option has been added to the payment suggestions. If this option is enabled, entries that are already in other journals will not be taken into account and will be skipped. This prevents the journal lines from being edited more than once.
  • Payment and cash receipt journals have been improved. It is now easier to see if journal lines are ready to be exported to a payment file or if values are still missing. With the newly added Payment File Status field, you can see at first glance whether a line is ready for payment file export. If one or more errors occur in the line, an overview with the errors can be opened using DrillDown.
  • The Preferred Bank Account Code field on Accounts Payable or Accounts Receivable is now filled with the bank account that is marked as Main Bank Account. If you change the value for Preferred Bank Account Code, the Main Bank Account flag on the bank account will be automatically adjusted.
  • When creating a purchase document, the Preferred Bank Account Code field will be prefilled if a bank account code has been specified on the vendor. The bank account that is stored on the purchase document will then be taken into account in the payment suggestion and written in the journal line.

• Modifications

• • NAVAX Extension Base extension update.
    For more information, see [Docs] NAVAX Extension Base - Release Notes
  • The External Bank Account Code field has been removed from the accounts payable, accounts receivable and journal. entries. Instead of the External Bank Account Code, the Recipient Bank Account field from standard is now used. An upgrade routine to convert to the new field is run during installation to prevent data loss.
  • The field Mandat ID was removed from the journal lines because there is the field Direct Debit Mandate ID in the standard and this can also be used. An upgrade routine has also been created to upgrade the field during installation.
  • Bankcodes Download URL's updated and provided as download.

• Corrections

• • Layout der Zahlungsvorschlagsliste korrigiert. Es wurde eine zusätzliche Seite ausgegeben da die Seitenränder nicht korrekt waren.

Version 21.1.4.0

• Business Central Update

• Improvements

• • Tooltips on the XML Schema Lines page have been improved so that the description of the columns is now more understandable. This should make editing the schemas easier.
  • Actions structure has been improved. The new action groups introduced with Business Central have been integrated into the current version of NCPE Payments Export and the menu structure has been improved.

• Corrections

• • The Incl. Vendors with Credit or Incl. Customers with Credit functions in the payment suggestion reports did not work properly.
  • When opening the NCPE Initial Setup Wizard for the first time, an error occurred stating that the record does not exist.
  • The NCPE Initial Setup Wizard was created several times in the GuidedExperience, which caused the NCPE Payment Setup and the Setup Wizard are shown more than once.
  • An error in the NCPE Mail Management codeunit has been fixed. This prevented the automatic update of Business Central when NCPE Payments Export was installed.

Version 20.1.3.2

• Corrections

• • Error in payment suggestions, creditor and debtor payment suggestion created wrong applications and entries.
  • The calculation of the payment tolerance when executing the payment suggestion incorrectly calculated the discount, which caused the wrong suggestion to be written in the journal.
  • Missing options in the payment suggestion reports have been readded.

Version 20.1.3.1

• Corrections

• • When posting Sales Documents, a message appears that a customer entry could not be found if there is no NCP Pay with QR Code setup.

Version 20.1.3.0

• Business Central Update

• Corrections

• • The table relation of the External bank Account Code field in the Vendor Ledger Entry table has been corrected.

• Improvements

• • The possibility to select a layout has been added to the report NCPE Payment Suggestion List. It is now possible to decide via the Report Layout Selection page whether the payment suggestion list should be printed in portrait or landscape format.
  • The Execution Date used in the payment proposals can now be pre-configured in the NCPE setup as Date Formula.
  • For Non SEPA transfers, address data for the receiving bank is also required in many countries, this has now been added to the XML Schemas so that it can be included in the schemas.
  • For OnPrem installations, events have been created, providing a way when creating SEPA XML files to allow a default location without download with query.
  • The Payment Notification Texts have been extended by a text editor, so now texts copied from e.g. Word can be pasted into the text editor.
  • On the page Countries/Regions the action NCP Initialize SEPA countries was added to enable the subsequent automatic setup of the SEPA countries. Use this action if the SEPA column has no values. Normally all SEPA countries are set up automatically during the installation of NCPE Payments Export, but in some constellations it is still necessary to set them up again automatically.
  • A new function has been integrated in NCP, this allows to add a QR Code to invoices for the functionality Pay with QR-Code.
  • In NCPE Setup an action has been added which allows to update the bank code URL's. The action starts the download of the URL's from www.navax.app, the data is continuously updated so that the latest URL's can always be fetched.
  • Progress indicators built into all relevant functions. These include the payment suggestions and the payment file creation.

• Modifications

• • NAVAX Extension Base extension update.
    For more information, see [Docs] NAVAX Extension Base - Release Notes
  • The fields, Incl. Customers with neg. Balance and Incl. Vendors with pos. Balance, in the NCPE Setup, have been renamed to Incl. Customers with Credit and Incl. Vendors with Credit, for better understanding.
  .
  • Necessary code updates for the new Business Central release.

Version 19.1.2.0

• Improvements

• • New fields, Incl. Customers with neg. Balance and Incl. Vendors with pos. Balance, added in the NCPE setup. These are used to exclude debtors/creditors with credit balance in the payment suggestion.
  • The recipient of the e-mail is now entered in the payment entry after sending a payment notification. This is possible since an update from Microsoft.
  • Payment Notification layout improved.

• Corrections

• • In the payment suggestion for certain constellations there was still an error message: "Currency" does not exist. Identified fields and values: Code = ''. This has been fixed.
  • Translation of the Document Type column in the Payment Suggestion List report has been corrected and layout has been changed for a better overview.
  • Error message during payment suggestion: Too many key fields were specified, therefore "SEPA Direct Debit Mandate" could not be retrieved. The number of fields in the primary key is 1. The function call has been changed.
  • Error in function call of the payment notification report corrected. It happened that the payment notification numbers are different than the ones in the e-mails to the customers..

Version 19.1.1.0

• Business Central Update

• Improvements

• • NCP bank codes are also inserted on the employee page.
  • Deprecated email features (SMTP Mail) are removed from NCPE Payments Export as they will soon be unavailable in Business Central, instead the advanced email features are used.

• Modifications

• • Bank Codes Download URL's updated.
  • Actions and fields related to licensing have been removed from NCPE Payments Export as they have all been added centrally in the NCEX Extension Base extension.

• Corrections

• • When updating the exchange rate, an error occurred regarding the currency with code '', this was fixed and an upgrade routine was created. Added the new field ISO LCY Code in the NCPE Payments Export Setup, this field is now used instead of the record in the currency table and should be filled before use, this does not apply to new installations. For new installations the field will be automatically filled with EUR if in the General Ledger Setup in the LCY Code field the value EUR or EURO has been specified. For more information, see Setup, Payments Export Setup.
  • When creating payment advices for customers who had not specified a language code, the error message "Invalid language code specified: 0." appeared.
  • The error in the payment suggestion has been corrected, it prevented the external bank account code from being correctly assigned in the journal.
  • The Payment Suggestion List has been edited to show longer descriptions, previously the lines were truncated.

Version 18.1.0.0

• Corrections

• • Fixed an error when sending notification emails via the new email features.

• Modifications

• • NAVAX Extension Base extension update.
    For more information, see [Docs] NAVAX Extension Base - Release Notes

Version 18.0.0.2

• Corrections

• • Quality of live update.

Version 18.0.0.0

• Business Central Update

• Improvements

• • Added Brexit XML Schema support
  • Introduced the new onboarding feature of Dynamics 365 Business Central to all pages where it makes sense.
  • Some Events added for extensibility.
  • The new Email feature from Dynamics 365 Business Central is now used to send the Payment Notification emails.

• Modifications

• • Code requirements for Dynamics 365 Business Central version 18 implemented.
  • Permission sets converted to the new permission objects.
  • Bank Codes Download URL's updated.
  • Changed UI of the Assisted Setup.
  • Changed the behavior how the UI shows messages to the user - we now showing Notifications instead of message boxes to the user.

• Corrections

• • The menus in the Payment and the Cash Receipt Journals was broken and now these are fixed.
  • The Payment Type field in Payment and Cash Receipt Journal was not filled correctly. Now the field will be filled as expected.
  • Keys renamed in several tables.
  • The address checks in the One Time Transfer page now working correct.

Version 17.0.0.0

• Business Central Update

• 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 Dynamics 365 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 email 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.

Version 16.0.0.0

• Initial Version

Docs  /  NAVAX Payment  /  Appendix
 Release Notes Payment Imports

Version 21.2.1.0

• New Product Name

• • The NCPI Payments Import extension has been renamed to NAVAX Payment Imports.

• Improvements

• • Menu structure in the accountant role center tidied up.
  • A new feature has been added that displays a message and overview when the automatic application skips entries because they already exist in other journal pages. This helps users avoid duplicate entries and maintain an overview of their transactions.
  • In the Payment Journal and Cash Receipt Journal pages, the Apply Suggested Application - line action has been integrated in the "Show more options" (three dots ⋮) menu.
  • In the Apply Vendor Entries and Apply Customer Entries pages, the fields NCP Imports Payment Reference, NCP Imports Remittance Info., and NCP Imports Additional Information have been added. Additionally, the Import Transaction Card action has been added. This facilitates manual follow-up of reconciliation suggestions.

• Modifications

• • The logo of the extension has been changed.