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...
• Role Center Integration
  NAVAX Payment is integrated into the Finance, Accountant and Accounting Manager role but can also be accessed from any role via the Search function...

Setup

• General

• • Bank Account Setup
    On the NCP Bank Account Setup page, all bank accounts for the NAVAX Payments extension are managed. Here, you can add new bank accounts, edit or remove existing ones, and update important account data. The overview provides a clear display of all relevant bank information...
  • Vendor/Customer/Employee Bank Account
    In the Vendor/Customer Bank Account overview, you can manage the bank accounts associated with your vendors and customers. To access this overview, navigate to the vendor or customer list or card, and then select Vendor/Customer > Bank Accounts...
  • 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...
  • 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...
  • 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...
  • 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...
  • 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...
  • 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...
  • Imports Codes
    The NCP Import Codes are references to various types of transactions. Different code fields are filled depending on the imported file format...
  • NAVAX Dropzone Setup
    In the NAVAX Dropzone Setup page the settings and defaults for the different Dropzones are defined...
  • 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

• • Make Payment or Direct Debit Suggestions
    NAVAX Payment Exports allows you to create payments to vendors via a SEPA payment file from the payment journal. Similarly, you can create a payment file for direct debits to customers via the cash receipt journal...
  • Create Payment File
    This chapter describes how to create a payment file. Typically, the payment file must then be manually downloaded to be uploaded into your banking software...
  • Make One-Time Transfers
    With a one-time transfer, you can perform a transfer ad hoc without having to manage vendors/customers and external bank accounts. In the journals, it can be defined per line whether it is a one-time instruction...
  • Payment Notification E-Mail Suggestion
    A payment notification is a message to the payment recipient that contains details about the payments transferred or collected via a payment file. A payment notification is particularly useful for batch payments, as it helps the recipient correctly allocate the payments. By default, a payment notification is created when the purpose exceeds 140 characters...
  • Journals Exports
    The description on this help page applies to the Cash Receipt- and the Payment Journal and explains the extensions that NAVAX Payment Imports provides...

• Imports

• • Import Payment File
    This chapter describes the import functionality for bank statements in Business Central. This import functionality is integrated into the modules NAVAX Payment Transactions Imports and NAVAX konfipay Connector Import. Typically, bank statements are exported from banking software in a standard format and then manually imported into Business Central. NAVAX konfipay Connector Import can automate this manual step by directly importing bank statements into Business Central via the konfipay Online Payment Services...
  • Dropzone for Bank Files
    This chapter describes the functionality of the Dropzone for bank files in Business Central. The Dropzone is a feature that allows bank files to be imported quickly and easily via Drag & Drop. The file is automatically checked for validity and imported into Business Central...
  • Applying Open Entries
    With the journals, you can efficiently reconcile and close open entries based on the imported data. NAVAX Payment Imports supports you with the automatic application suggestion, which determines the best possible match based on defined criteria...
  • 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...
  • Journals Imports
    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

• Exports

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

• Imports

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

• Exports

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

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

Information for Developers

• Exports
  The following page lists events that are intended to help you integrate with NAVAX Payment Payment Exports...
• Imports
  The following page lists events that are intended to help you integrate with NAVAX Payment Payment Imports...
• 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...
• Event Request

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

• Release Notes

• • Overview
  • 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  /  General
 Role Center Integration

• Payment Journals and Cash Receipt Journals These actions guide you to the respective journals where you can export payment files (NAVAX Payment Exports) and/or match transactions from previously imported bank statements with entries in Business Central (NAVAX Payment Imports). For more information, see Tasks, Exports, Create Payment File. For more information, see Tasks, Imports, Applying Open Entries.
• Imports This action is available when NAVAX Payment Imports is installed and is used to import bank statements or transfer them to journals.
• Clearing Entries This action opens the overview of created payment files (NAVAX Payment Exports). For more information, see Archive, Exports, Clearing Entries.
• Administration This group contains the basic options for using NAVAX Payment.
  • Exports Setup The action opens the NAVAX Payment Exports Setup page where you can define the basic settings for using NAVAX Payment Exports. For more information, see Setup, Exports, Exports Setup.
  • Imports Setup The action opens the NAVAX Payment Imports Setup page where you can define the basic settings for using NAVAX Payment Imports. For more information, see Setup, Imports, Imports Setup.
  • Bank Account Setup With the action you define all necessary options on the bank accounts for using NAVAX Payment. For more information, see Setup, General, Bank Account Setup.
  • Pay with QR-Code The action opens the QR-Code Setup page where you can define the basic settings for using NAVAX Payment QR-Code. For more information, see Setup, General, Pay with QR-Code.

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

• Payment Status Entries

  Opens the overview of payment status entries for this bank account. For more information, see Archive, Exports, 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, Imports, 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, Exports, 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
 Vendor/Customer/Employee Bank Account

Set up bank accounts

Employees

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.

History, Actions

• NCP Payment Entries

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

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
 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
 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
 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 Payment Transactions
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	The field Batch Booking determines how the transactions are booked by the bank. By default, this field remains empty, and the indicator () is not written into the payment file. If you specify Yes or No, the indicator is set in the payment file to indicate whether it is a Batch Booking (Yes) or a Single Booking (No). Note Only if there is a corresponding agreement with the bank for single bookings, each transaction will be displayed individually on the client's account statement when specifying No. Otherwise, or by default, it is always a batch booking (default/pre-agreed: Yes).
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.

Special notes NON-SEPA Credit Transfers

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
 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  /  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
 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
 NAVAX Dropzone Setup

Docs  /  NAVAX Payment  /  Setup  /  Imports
 Fixed Account Allocations

Actions

• Dimensionen

  The Dimensions action allows you to set specific dimensions for fixed account allocations for NAVAX Payment Imports. Dimensions are data categories that can be used for analysis and reporting. They help to track and categorize transactions more accurately. For more information, see Work with dimensions

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
 Make Payment or Direct Debit Suggestions

Creating Payment Suggestion

1. Select Journal

   Select the desired journal to open it.

2. Open Payment Suggestion

   Click on the action Vendor Payment Suggestion in the NCP Exports group to suggest payments to vendors, or Employee Payment Suggestion to suggest payments to employees.

3. Start Payment Suggestion

   The page NCP Exports Payment Suggestion - Vendors or NCP Exports Payment Suggestion - Employees opens.

4. Adjust Options

   Enter the desired options. A description of the options can be found later in the chapter.

5. Confirm

   Click OK. The open entries are identified and written to the journal.

Creating Direct Debit Suggestion

1. Select Journal

   Select the desired journal to open it.

2. Open Direct Debit Suggestion

   Click on the action Customer Direct Debit Suggestion in the NCP Exports group to suggest direct debits for your customers.

3. Start Suggestion

   The page NCP Exports Direct Debit Suggestion - Customers opens.

4. Adjust Options

   Enter the desired options. A description of the options can be found later in the chapter.

5. Confirm

   Click OK. The open entries are identified and written to the journal.

Fill in Journal Lines, Options

Posting Date	Specifies the posting date for the journal lines. By default, the working date is entered, but you can change it. This field is transferred to the journal lines.
Consider Payment Discount Tolerance	If this checkbox is selected, the Payment Discount Tolerance Date of the entries is taken into account when calculating the balance, provided that the Block Payment Tolerance field is not set on the vendor/customer card. If the Find Cash Discount field is also selected, the search for possible (future) payments will filter not only by the payment discount date but also by the payment discount tolerance date.
Starting Document No.	Specifies the next available number in the number series for the journal batch associated with these journals. When you execute the payment suggestion, this is the document number that appears in the first line of the journal. You can also fill in this field manually. Note If the New Document No. per Line checkbox is not selected, this number is carried over to every line in the journal. Tip You can set up the number series on the General Journal Names page. This eliminates the need to manually enter document numbers, saving time and reducing errors.
New Doc. No. per Line	Specifies that the journal lines are numbered sequentially, starting from the number in the Starting Document No. field.
Gegenkontoart	Specifies the type of balancing account to which the posting should be made. It should either be a bank account or a general ledger account in connection with the NAVAX payment transactions. Note The value is derived from the settings for the journal and pre-filled. This field is carried over to all journal lines.
Bal. Account No.	Specifies the balancing account number that payments are posted to. You can enter the account number or select it from a drop-down list. Note The value is derived from the settings for the journal and pre-filled. This field is carried over to all journal lines.
Zahlungsart	Payment type of the journal lines. The following options are available: Direct Debit Suggestion (only for cash receipt journals) Non-SEPA Transfer SEPA Transfer SEPA Direct Debit (only for cash receipt journals) Note If the field is left empty, you must specify the payment type manually for each line in the journal. For the payment types SEPA Credit Transfer and SEPA Direct Debit, only lines with the ISO currency code "empty" or "EUR" are considered in the payment suggestion. If you select the option Credit Transfer Suggestion, the system attempts to create a transfer in the following order: SEPA Credit Transfer (if the rules for external bank account lookup are met (IBAN, Country/Region Code, SWIFT Code available) and the own bank account contains a SEPA Credit Transfer schema. For more information, see Bank Account Setup. Non-SEPA Credit Transfer, if the own bank account contains a Non-SEPA Credit Transfer schema. If you select the option Direct Debit Suggestion, existing transactions of the customer with this currency code are searched. The system attempts to create a Direct Debit in the following order: SEPA Direct Debit (if the rules for external bank account lookup are met and the own bank account contains a SEPA Direct Debit schema. For more information, see Bank Account Setup. If a transaction is found, the payment type and the external bank account code of the transaction are suggested. If no transaction is found, the system attempts to determine the external bank account and payment type based on the rules for external bank account lookup. The external bank account lookup, especially with the option Last Transaction/Main Bank Connection, in combination with Direct Debit/Transfer Suggestion, should provide optimal results in most cases. For more information, see NCP Exports Setup.
Foreign Currency Filter	Indicates that entries with ISO currency codes not equal to "empty" or "EUR" are filtered. For the payment type bank transfer suggestion and non-SEPA bank transfer, it is possible to set this field.
Vendor/Customer	In this filter area, you can narrow down the results of the payment suggestion by applying filters to the Customer/Vendor tables. Tip For example, if you want to create a payment suggestion for credit balances with your customers, you can set the filter on the customer card and select only those customers with credit balances. To do this, add the field Balance to the filter fields and set the filter to -10000..-1. For more information, see Sorting, Searching, and Filtering
Vendor/Cust. Ledger Entry	In this filter area, you can narrow down the results of the payment suggestion by applying filters to the Vendor/Customer Ledger Entry tables. For more information, see Sorting, Searching, and Filtering

Notes on Creating a Payment Suggestion

Docs  /  NAVAX Payment  /  Tasks  /  Exports
 Create Payment File

Creating a Payment File

1. Make Basic Settings

   Ensure that the basic settings have been configured in the NCP Exports Setup. For more information, see Setup, Exports, Exports Setup.

2. Create Journal Lines

   Use one of the following functions to create journal lines for exporting to the payment file:
   • Suggest Vendor Payments: Creates journal lines based on open vendor ledger entries.
   • Suggest Customer Payments: Creates journal lines based on open customer ledger entries.
   • Suggest Employee Payments: Creates journal lines for employee payments.
   Alternatively, you can manually create the journal lines. In this case, ensure that a valid value is entered in the NCP Payment Type field to correctly generate the payment file. For more information, see Tasks, Exports, Make Payment or Direct Debit Suggestions.

3. Check Lines

   Check the field NCP Payment File Status: 🗸 Ready: The required data is complete, and the payment file can be created. ✗ Check: The data is incomplete. Add the missing information. Clicking the button ✗ Check opens the page NCP Exports Payment Journal - Error Text, where possible errors are listed. This page can help you to quickly identify missing information.

   Tip

   The Payment Suggestion List can assist you in obtaining a clear overview of the suggested payment or direct debit lines. In the Payment Suggestion List, the individual journal lines and possible errors are listed, it can also be used for an approval process.

   Important

   In some scenarios, it is possible that the journal lines have the status ✗ Check, but a payment file can still be created.

4. Create Payment File

   Proceed as follows:
   1. In the journal, click the action Create Payment File.
   2. On the page that opens, adjust the desired options. You can adjust the following data, among others:
      • Execution Date: The date on which the bank should execute the payments.
      • Direct Debit Type and Execution Date for One-Time/First Direct Debit (only for SEPA direct debits).
      • Charges> (only available if the XML schema of the bank account supports fees).
      • Urgent Payment: Activate this option if you want to set the execution date to today.
      • Instant Payment: Activate this option if you want to create a payment file with transfers that are immediately credited to the recipient's bank account.
      • Show Summary: Activate this option if you want to see a summary of the created payment file. Here, the payment file can subsequently be exported or sent.
      • Send After Creation: Activate this option if you want to send the payment file to your bank via the konfipay Connector after creation.

5. Confirm

   Click the OK button to create the payment file. The payment file is created, and the Payment Status field is automatically set to File Created.

6. Export Payment File (optional)

   After creating the payment file, the page NCP Exports Payment File - Summary opens, provided it has been configured this way. Here, you can review the payment file and view the details. Click the button Export Payment File to export the payment file. This starts the download of the file to your computer, allowing you to import it into your bank's software.

   Note

   The payment file is created in XML format and can usually be directly imported into the bank's software.
   Alternatively, the payment file can also be sent directly to the bank if you have installed the NAVAX konfipay Connector Export extension. For more information, see the chapter Automatic Sending via konfipay (optional).

Automatic Sending via konfipay (optional)

Options - Enable Urgent Payment (optional)

Options - Instant Payment (optional)

Options - Show Summary (optional)

Possible Errors in Payment File Status

• The value for the field 'Document Type' in journal line no. 10000 must be Payment.

  The value for the field Document Type in the journal line is invalid. Ensure that the field is set to Payment unless the Collective Transaction option is enabled in the NCP Exports Setup under Payment File. When Collective Transaction is activated, payments and refunds are combined into a single line in the payment file. If this option is not enabled, each transaction must have Document Type set to Payment to avoid errors.

• The field 'Account No.', in journal line no. 1000 must not be empty.

  The line appears to be incorrectly filled out or no account number has been provided. Check the line and ensure that all required fields are completed.

• Journal line no. 0 must be applied.

  The line appears to have no entry applied. You can manually add this via the action Home, Apply Entries.

• The field 'Recipient Bank Account', in journal line no. 0 must not be empty.

  In the line, no recipient bank account was provided. Check the line and ensure that all required fields are completed.

• 'SEPA Direct Debit/SEPA Transfer/Non-SEPA Transfer' must have a value in 'NCP Bank Account Setup': 'Bank Account No.=BANK'. The value must not be null or empty

  The bank account setup is missing a value for one or more of the following fields: SEPA Direct Debit, SEPA Transfer, or Non-SEPA Transfer. To resolve this issue, open the bank account setup and ensure that all required fields are properly filled out. These fields are essential for generating the payment file and must not be empty.

• Missing Information in Vendor/Customer Bank Account. Please check the Vendor/Customer Bank Account for completeness.

  If this error occurs, the bank account must be checked for completeness. Check the following fields:
  • IBAN
  • SWIFT Code Not required in all countries, but necessary in most cases.
  • Bank Account Number Not required in all countries, mainly for international payments.
  • Bank Code Not required in all countries, mainly for international payments.
  • Country/Region Code
  Check the customer's bank details and ensure that all required fields are filled out.

• The field 'Direct Debit Mandate ID', in journal line no. 0 must not be empty.

  No SEPA Direct Debit Mandate ID was provided in the line, possibly no valid SEPA direct debit mandate is assigned. Check the customer's SEPA direct debit mandates and ensure that all required fields are filled out and the validity has not expired. For more information, see Setup, Exports, SEPA-Direct Debit-Mandates.

• The field 'NCP Direct Debit Type', in journal line no. 0 must not be empty.

  No direct debit type was provided in the line. Check the SEPA direct debit mandate and ensure that all required fields are filled out. For more information, see Setup, Exports, SEPA-Direct Debit-Mandates.

• The field 'NCP Direct Debit Sequence', in journal line no. 0 must not be empty.

  No direct debit sequence was provided in the line. Check the SEPA direct debit mandate and ensure that all required fields are filled out. For more information, see Setup, Exports, SEPA-Direct Debit-Mandates.

Payment File Summary

NCP Exports Payment File - Summary, Actions

• Export Payment File

  Use this action to export the previously created payment file. This starts the download of the file to your computer, allowing you to import it into your bank's software.

• View Payment File

  This action allows you to view the payment file created in the Payment Journal using the Create Payment File action in a text editor. The file is read-only and cannot be edited.

• Cancel Payment File

  This action allows you to cancel a created Payment File. The status of the associated Clearing Entry is set to canceled.

• Payment Entries

  Opens the overview of Payment Entries that reference this Clearing Entry. For more information, see Archive, Payment Entries.

• Bank Entries

  Opens the overview of Bank Entries that reference this Clearing Entry. For more information, see Bank Entries.

• Clearing List

  This list provides information about the created Clearing Entry.

• Advice Email Suggestion

  This list displays information about the created Payment Suggestion or the current situation (settlement, etc.) in the journal. For more information, see Tasks, Exports, Payment Notification E-Mail Suggestion.

• Notification

  The notification is helpful for the recipient to facilitate the allocation of the payment(s). This is especially useful in the case of a collective transfer. It is possible to send this notification via email. After the Payment File has been created, you can print the Notification or send it via email. For more information, see Tasks, Exports, Payment Notification E-Mail Suggestion.

Docs  /  NAVAX Payment  /  Tasks  /  Exports
 Make One-Time Transfers

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. E.g.: 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 Notification E-Mail Suggestion

Setting Up Payment Notification

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. Alternatively, the page can also be opened via the Clearing Entries.
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, you can review and, if necessary, correct the data. If all lines are correct, you can send the notifications using the Send All action. Alternatively, you can send only the selected notifications using the Send action.

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. Alternatively, the page can also be opened via the Clearing Entries.
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  /  Exports
 Journals Exports

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  /  Imports
 Import Payment File

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

Importing a Bank Statement File

1. Make Basic Settings

   Ensure that the basic settings in the NCP Imports Setup have been configured. It is important to define how to handle the individual file types. For more information, see Setup, Imports, Imports Setup.

2. Open the Imports Page

   On the homepage of your Microsoft Business Central, click on the action group NAVAX Payment, on the action Imports, or ☰ > NAVAX Payment > Imports if you are not in the Accountant role.

3. Import File

   Click on the action Import.

   Tip

   Files can also be imported via the drop zone for bank files using Drag & Drop. Simply drag the file into the Dropzone for Bank Files area (found in the fact boxes on the right side), and the import will start automatically. For more information, see Tasks, Imports, Dropzone for Bank Files.

4. Assign Bank Accounts (if necessary)

   The import is performed, loads the data into Business Central, and automatically assigns the bank account. Correct setup is required for this. For more information, see Setup, General, Bank Account Setup. If not all bank accounts were automatically identified, click on Data and manually select the Bank Account No. or use the action Suggest Bank Account. To do this, click on the action Data and select the Bank Account No. on the page that opens.

5. Review Imported Lines

   As long as no Journal Line/Matching Line exists for an import line, you can still delete the line or change the bank account. To re-import deleted data, repeat all steps and perform the Import again. Use the action Data to view the bank statement data. All relevant data is clearly listed here. With the action Transactions, you can call up an overview of the individual posting lines. This overview shows you all posting lines linked to the bank statement and can help with analysis or provide an overview of the bank statement positions.

   Note

   If a file has already been imported or a file with the same Message Reference is imported, a warning will be displayed. This warning can be ignored if you want to re-import the file. If you do not want to re-import the file, click No.

Automated Import with the NAVAX konfipay Connector

• Make Basic Settings

  Ensure that the basic settings in the NCP Imports Setup and konfipay Connector Setup have been configured. It is important that the konfipay Online Payment Services are correctly set up and the connection to the banking data centers works. It is also important to define how to handle the individual file types. For more information, see Setup, konfipay Connector, konfipay Connector Setup.

• Open the Imports Page

  On the homepage of your Microsoft Business Central, click on the action group NAVAX Payment, on the action Imports, or ☰ > NAVAX Payment > Imports if you are not in the Accountant role.

• Retrieve Account Transaction Entries

  If the account transaction entries are already available in Business Central, open the Account Transaction Entries page. If no account transaction entries have been imported yet, open the submenu of the Import action and select Retrieve Account Transaction Entries. A window will open where you can select the desired bank connection. Click OK to start the import. After the download is complete, the Account Transaction Entries page will automatically open, displaying all imported account transaction entries.

• Transfer Account Transaction Files

  Select the desired account transaction files and click on Transfer Account Transaction File to process the data further.

Docs  /  NAVAX Payment  /  Tasks  /  Imports
 Dropzone for Bank Files

Functionality

Docs  /  NAVAX Payment  /  Tasks  /  Imports
 Applying Open Entries

Performing Automatic Application

1. Transfer Transactions

   On the Imports page, click the Transfer action to transfer the imported data to the journal or bank reconciliation. Instructions on how to transfer bank transactions can be found in the chapter Tasks, Imports, Import Payment File. If the Trans. Charges field in the NCP Imports Setup is enabled, a line for the total charges per transaction will also be transferred. You can transfer the entire file, individual NCP Imports Data, or only specific NCP Imports Transactions.

2. Select Journal

   Select the desired journal to open it.

3. Process Imported Data

   In the journal, click
   • NCP Imports > Application Suggestions > Imports Suggest Application - All Lines to create an automatic application suggestion for all lines.
   • NCP Imports > Application Suggestions > Imports Suggest Application - Line to create an automatic application suggestion for the selected line.
   The system attempts to determine the account number and the associated open entries based on various criteria. Lines already marked as Applied are skipped.

4. Criteria for Application

   The following order is used to determine an account number or application entries for each line:

   1. Fixed Account Allocation

      If a Fixed Account Allocation is defined, it will be used. (+2000 points) Example: Account 241203 is automatically assigned if the remittance info or payment reference contains "Tax Office". For more information, see Setup, Fixed Account Allocations.

      Note

      For G/L accounts, it may happen that the description is not written into the journal line. This is due to the Omit Default Description in Journal setting on the G/L account. This option specifies whether the default description is automatically entered into the Description field of the journal lines created for this G/L account.

   2. Document Number or External Document Number

      If a Document Number or External Document Number is found in the remittance info or payment reference, it is matched with open entries. (+600 points) Example: A document number in the remittance info is assigned to an entry, and the line is applied.

   3. Customer/Vendor or Employee Number

      If a number matching a customer, vendor or employee is found, it is assigned. (+100 points) If a bank account is also found, it is assigned and increases the score. (+100 points)

      Note

      Application with open entries is not possible if no document number is present. If the Retain Account Allocations option is enabled in the NCP Imports Setup, the customer/vendor will be suggested for the line even if no document is found. However, this option may negatively affect the results of the automatic allocation.

   4. Other Criteria

      • Amount matches exactly (+100 points)
      • Payment tolerance or discount considered (+50 points)

5. Filter Lines (Optional)

   Click the NCP Imports > Deviation > Import Deviation - Set Filter button to display only lines that have not been fully applied or that do not have a G/L account entered in the Account No. field. Use the NCP Imports > Deviation > Import Deviation - Print action to print the filtered lines.

6. Use Analysis Window (Optional)

   The analysis window provides a detailed overview of the applied criteria and the scores achieved. It shows the matches found and the evaluation of each criterion. To use the analysis window, enable the Show Analysis Window option in the NCP Import Setup. After completing the application suggestion, the window will open automatically and can help to better understand the system's decision logic. However, the window should only be used for analysis purposes. For more information, see Reports and Analysis, Imports, Imports Allocation Analysis.

7. Delete Lines

   You can delete lines at any time as long as they have not been posted.

Important Notes

Fixed Account Allocations

Entries without any suggestion

• Entries with a posting date in the future.
• Blocked customers/vendors.
• Entries cannot be uniquely assigned, e.g., if multiple entries exist.
• Remaining amount does not match the amount from transaction.

  Note

  In this case, it may help to increase the Max. Application Tolerance Amount or to disable the option Check Application Amount in the NCP Imports Setup.

Manual Applications

Criteria and Scoring for the Application Suggestion

1. A Fixed Account Allocation is found ➟ +2000 points
2. Searches the value of the payment reference from the imported transaction in the Payment Reference of the entries ➟ +1000 points
3. Searches the value of the payment reference from the imported transaction in Document Numbers or External Document Numbers ➟ +600 points
4. Searches the value of the remittance info in the Payment Reference, Document Numbers, and External Document Numbers of the entries ➟ +600 points based on the degree of match (Only if it does not have a payment reference)
5. Searches account number in Customers/Vendors ➟ +100 points
6. Searches external account holder in Customers/Vendors ➟ +100 points
7. Searches payment reference in Customers/Vendors ➟ +300 points based on the degree of match
8. Searches remittance info in Customers/Vendors ➟ +300 points based on the degree of match (Only if it does not have a payment reference)
9. Found Customers/Vendors are blocked ➟ Not considered.
10. Found entry has a future posting date ➟ Not considered.
11. Found entry has the correct amount ➟ +100 points
12. Found entry has payment tolerance/discount on the amount ➟ +50 points

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
 Journals Imports

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  /  Exports
 Payment Statistics

Fields, General

Fields, Details

Docs  /  NAVAX Payment  /  Reports and Analysis  /  Imports
 Importlist

Docs  /  NAVAX Payment  /  Reports and Analysis  /  Imports
 Imports Allocation Analysis

Evaluation Scheme

1. A Fixed Account Allocation is found ➟ +2000 points
2. Searches the value of the payment reference from the import in the Payment Reference of the entries ➟ +1000 points
3. Searches the value of the payment reference from the import in Document Numbers or External Document Numbers ➟ +600 points
4. Searches the value of the purpose in the Payment Reference, Document Numbers and External Document Numbers of the entries ➟ +600 points according to the degree of match (Only if it has no payment reference)
5. Searches account number in Customers/Vendors ➟ +100 points
6. Searches external account holder in Customers/Vendors ➟ +100 points
7. Searches payment reference in Customers/Vendors ➟ +300 points according to the degree of match
8. Searches purpose in Customers/Vendors ➟ +300 points according to the degree of match (Only if it has no payment reference)
9. Found Customers/Vendors are blocked ➟ Not considered.
10. Found entry has a future date of the posting ➟ Not considered.
11. Found entry has correct amount ➟ +100 points
12. Found entry has payment tolerance/discount from the amount ➟ +50 points

Actions

• Transaction Card

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

• 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  /  Imports
 Import General Journal Deviation

Docs  /  NAVAX Payment  /  Archive  /  Exports
 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, Exports, Payment Entries.

• Clearing Entries

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

Docs  /  NAVAX Payment  /  Archive  /  Exports
 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, Exports, 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  /  Exports
 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, Exports, 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  /  Exports
 Payment Status Entries

Docs  /  NAVAX Payment  /  Archive  /  Imports
 Imports

• Import a payment file into Dynamics 365 Business Central and transfer it to a journal.
• 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.

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

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

  In some cases, it may happen that no bank account number can be automatically suggested. The action Suggest Bank Account then attempts to find a bank account based on the IBAN and SWIFT combination. If no bank account is found, the combination of bank account number and bank code is checked. If this is also unsuccessful, NCP Payment Imports takes the bank account from a previous import.

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

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

  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.

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

Docs  /  NAVAX Payment  /  Archive  /  Imports
 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  /  Information for Developers
 Exports

Table - NCPE Payment File Setup

• OnAfterCreateRemitInfoText

  This event is used to integrate custom logic when creating remittance information and, if necessary, to change the texts.

  [IntegrationEvent(false, false)]
  local procedure OnAfterCreateRemitInfoText(NCPPaymentRemittanceEntry: Record "NCP Payment Remittance Entry"; GenJournalLine: Record "Gen. Journal Line"; var TempRmtInfo: Text[140])
  begin
  end;

  Type	Name	Description
  Record "NCP Payment Remittance Entry"	NCPPaymentRemittanceEntry	The payment remittance entry that contains the information from imported file.
  Record "Gen. Journal Line"	GenJournalLine	The general journal line that is used to create the payment remittance entry.
  Text[140]	TempRmtInfo	[Pass by Reference] The generated remittance text that can be customized. This text is the result of the function.

Codeunit - NCPE Entry Calculation

• OnBeforeCalcVendLedgEntryStep1CheckOldVendLedgerEntry

  This event is triggered before checking the old vendor ledger entry in the procedure CalcVendLedgEntryStep1.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeCalcVendLedgEntryStep1CheckOldVendLedgerEntry(GenJournalLine: Record "Gen. Journal Line"; var TempOldVendorLedgerEntry: Record "Vendor Ledger Entry" temporary)
  begin
  end;

  Type	Name	Description
  Record "Gen. Journal Line"	GenJournalLine	The general journal line that is used to create the vendor ledger entry.
  Record "Vendor Ledger Entry" temporary	TempOldVendorLedgerEntry	[Temporary][Pass by Reference] The old vendor ledger entry that is used to calculate the new vendor ledger entry.

• OnBeforeCalcVendLedgEntryStep1OnBeforeFindVendLedgerEntry

  This event is triggered before finding the vendor ledger entry in the CalcVendLedgEntryStep1 procedure.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeCalcVendLedgEntryStep1OnBeforeFindVendLedgerEntry(var GenJournalLine: Record "Gen. Journal Line"; var ApplyingDate: Date; var TempOldVendorLedgerEntry: Record "Vendor Ledger Entry" temporary; var Result: Boolean; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Record "Gen. Journal Line"	GenJournalLine	[Pass by Reference] The general journal line that is used to create the vendor ledger entry.
  Date	ApplyingDate	[Pass by Reference] The applying date that is used to calculate the vendor ledger entry.
  Record "Vendor Ledger Entry" temporary	TempOldVendorLedgerEntry	[Temporary][Pass by Reference] The old vendor ledger entry that is used to calculate the new vendor ledger entry.
  Boolean	Result	[Pass by Reference] The result of the function that determines if the vendor ledger entry is found.
  Boolean	IsHandled	[Pass by Reference] Indicates if the vendor ledger entry is handled by custom code. The standard behavior will be skipped.

• OnBeforeCalcVendLedgEntryStep2

  This event is triggered before step 2 of the vendor ledger entry calculation is performed. It allows for the adjustment or verification of data before the actual calculation takes place. The event can be used to execute custom logic before step 2 of the vendor ledger entry calculation is performed.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeCalcVendLedgEntryStep2(var GenJournalLine: Record "Gen. Journal Line"; var AmountToApply: Decimal; var PmtTolAmtToBeApplied: Decimal; var RemainingAmount: Decimal; var LineAmount: Decimal; var LineDiscount: Decimal; var AppliedAmount: Decimal; var TempOldVendorLedgerEntry: Record "Vendor Ledger Entry" temporary; var OldVendorLedgerEntry: Record "Vendor Ledger Entry" temporary; Vendor: Record Vendor; var Completed: Boolean; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Record "Gen. Journal Line"	GenJournalLine	[Pass by Reference] The general journal line that is used to create the vendor ledger entry.
  Decimal	AmountToApply	[Pass by Reference] The amount that is applied to the vendor ledger entry.
  Decimal	PmtTolAmtToBeApplied	[Pass by Reference] The payment tolerance amount that is applied to the vendor ledger entry.
  Decimal	RemainingAmount	[Pass by Reference] The remaining amount that is applied to the vendor ledger entry.
  Decimal	LineAmount	[Pass by Reference] The line amount that is applied to the vendor ledger entry.
  Decimal	LineDiscount	[Pass by Reference] The line discount that is applied to the vendor ledger entry.
  Decimal	AppliedAmount	[Pass by Reference] The applied amount that is applied to the vendor ledger entry.
  Record "Vendor Ledger Entry" temporary	TempOldVendorLedgerEntry	[Temporary][Pass by Reference] The old vendor ledger entry that is used to calculate the new vendor ledger entry.
  Record "Vendor Ledger Entry" temporary	OldVendorLedgerEntry	[Temporary][Pass by Reference] The vendor ledger entry that is used to calculate the new vendor ledger entry.
  Record Vendor	Vendor	The vendor that is used to create the vendor ledger entry.
  Boolean	Completed	[Pass by Reference] Indicates if the calculation is completed.
  Boolean	IsHandled	[Pass by Reference] Indicates if the vendor ledger entry is handled by custom code. The standard behavior will be skipped.

• OnBeforeCalcCustLedgEntryStep1CheckOldCustLedgerEntry

  This event is triggered before checking the old customer ledger entry in the CalcCustLedgEntryStep1 procedure.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeCalcCustLedgEntryStep1CheckOldCustLedgerEntry(GenJournalLine: Record "Gen. Journal Line"; var TempOldCustLedgerEntry: Record "Cust. Ledger Entry" temporary)
  begin
  end;

  Type	Name	Description
  Record "Gen. Journal Line"	GenJournalLine	The general journal line that is used to create the customer ledger entry.
  Record "Cust. Ledger Entry" temporary	TempOldCustLedgerEntry	[Temporary][Pass by Reference] The old customer ledger entry that is used to calculate the new customer ledger entry.

• OnBeforeCalcCustLedgEntryStep1OnBeforeFindCustLedgerEntry

  This event is triggered before finding the customer ledger entry in the CalcCustLedgEntryStep1 procedure.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeCalcCustLedgEntryStep1OnBeforeFindCustLedgerEntry(var GenJournalLine: Record "Gen. Journal Line"; var ApplyingDate: Date; var TempOldCustLedgerEntry: Record "Cust. Ledger Entry" temporary; var Result: Boolean; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Record "Gen. Journal Line"	GenJournalLine	[Pass by Reference] The general journal line that is used to create the customer ledger entry.
  Date	ApplyingDate	[Pass by Reference] The applying date that is used to calculate the customer ledger entry.
  Record "Cust. Ledger Entry" temporary	TempOldCustLedgerEntry	[Temporary][Pass by Reference] The old customer ledger entry that is used to calculate the new customer ledger entry.
  Boolean	Result	[Pass by Reference] The result of the function that determines if the customer ledger entry is found.
  Boolean	IsHandled	[Pass by Reference] Indicates if the customer ledger entry is handled by custom code. The standard behavior will be skipped.

• OnBeforeCalcCustLedgEntryStep2

  This event is triggered before step 2 of the customer ledger entry calculation is performed. It allows for the adjustment or verification of data before the actual calculation takes place. The event can be used to execute custom logic before step 2 of the customer ledger entry calculation is performed.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeCalcCustLedgEntryStep2(var GenJournalLine: Record "Gen. Journal Line"; var AmountToApply: Decimal; var PmtTolAmtToBeApplied: Decimal; var RemainingAmount: Decimal; var LineAmount: Decimal; var LineDiscount: Decimal; var AppliedAmount: Decimal; var OldCustLedgerEntry: Record "Cust. Ledger Entry" temporary; Customer: Record Customer; var Completed: Boolean; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Record "Gen. Journal Line"	GenJournalLine	[Pass by Reference] The general journal line that is used to create the customer ledger entry.
  Decimal	AmountToApply	[Pass by Reference] The amount that is applied to the customer ledger entry.
  Decimal	PmtTolAmtToBeApplied	[Pass by Reference] The payment tolerance amount that is applied to the customer ledger entry.
  Decimal	RemainingAmount	[Pass by Reference] The remaining amount that is applied to the customer ledger entry.
  Decimal	LineAmount	[Pass by Reference] The line amount that is applied to the customer ledger entry.
  Decimal	LineDiscount	[Pass by Reference] The line discount that is applied to the customer ledger entry.
  Decimal	AppliedAmount	[Pass by Reference] The applied amount that is applied to the customer ledger entry.
  Record "Cust. Ledger Entry" temporary	OldCustLedgerEntry	[Temporary][Pass by Reference] The old customer ledger entry that is used to calculate the new customer ledger entry.
  Record Customer	Customer	The customer that is used to create the customer ledger entry.
  Boolean	Completed	[Pass by Reference] Indicates if the calculation is completed.
  Boolean	IsHandled	[Pass by Reference] Indicates if the customer ledger entry is handled by custom code. The standard behavior will be skipped.

Codeunit - NCPE Install

• OnBeforeInitLanguageRecords

  This event is executed before the initialization of the NCP language setup.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeInitLanguageRecords(var NCPLanguageSetup: Record "NCP Language Setup"; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Record "NCP Language Setup"	NCPLanguageSetup	[Pass by Reference] The NCP language setup that is used to initialize the language records.
  Boolean	IsHandled	[Pass by Reference] Indicates if the language records are handled by custom code. The standard behavior will be skipped.

• OnAfterInitLanguageRecords

  This event is executed after the initialization of the NCP language setup.

  [IntegrationEvent(false, false)]
  local procedure OnAfterInitLanguageRecords(var NCPLanguageSetup: Record "NCP Language Setup")
  begin
  end;

  Type	Name	Description
  Record "NCP Language Setup"	NCPLanguageSetup	[Pass by Reference] The NCP language setup that is used to initialize the language records.

• OnAfterInitSEPACountriesList

  This event is executed after the initialization of the SEPA countries/regions.

  [IntegrationEvent(false, false)]
  local procedure OnAfterInitSEPACountries(var TempCountryRegion: Record "Country/Region")
  begin
  end;

  Type	Name	Description
  Record "Country/Region"	TempCountryRegion	The country/region that is used to initialize the SEPA countries/regions.

Report - NCPE Suggest Vendor Payments

• OnBeforeOnPreReportEvent

  This event is triggered before the execution of the OnPreReport trigger.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeOnPreReportEvent(Vendor: Record Vendor; VendorLedgerEntry: Record "Vendor Ledger Entry")
  begin
  end;

  Type	Name	Description
  Record Vendor	Vendor	The vendor that is used to create the payment suggestion.
  Record "Vendor Ledger Entry"	VendorLedgerEntry	The vendor ledger entry that is used to create the payment suggestion.

• OnAfterPreReport

  This event is triggered after the execution of the OnPreReport trigger.

  [IntegrationEvent(false, false)]
  local procedure OnAfterPreReport(var Vendor: Record Vendor; var VendorLedgerEntry: Record "Vendor Ledger Entry")
  begin
  end;

  Type	Name	Description
  Record Vendor	Vendor	[Pass by Reference] The vendor that is used to create the payment suggestion.
  Record "Vendor Ledger Entry"	VendorLedgerEntry	[Pass by Reference] The vendor ledger entry that is used to create the payment suggestion.

• OnAfterIncludeVendor

  This event is triggered after a vendor is included in the payment suggestion. It allows customization or validation of the data after the vendor and its balance are considered.

  [IntegrationEvent(false, false)]
  local procedure OnAfterIncludeVendor(Vendor: Record Vendor; VendorBalance: Decimal; var Result: Boolean)
  begin
  end;

  Type	Name	Description
  Record Vendor	Vendor	The vendor that is used to create the payment suggestion.
  Decimal	VendorBalance	The balance of the vendor that is used to create the payment suggestion.
  Boolean	Result	[Pass by Reference] The result of the function that determines if the vendor is included in the payment suggestion.

• OnGetVendLedgEntriesOnBeforeLoop

  The event is triggered before the loop to process the vendor ledger entries begins. It allows customization or validation of the data before the actual processing of the entries starts.

  [IntegrationEvent(false, false)]
  local procedure OnGetVendLedgEntriesOnBeforeLoop(var VendorLedgerEntry: Record "Vendor Ledger Entry"; PostingDate: Date; LastDueDateToPayReq: Date; Future: Boolean; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Record "Vendor Ledger Entry"	VendorLedgerEntry	The vendor ledger entry that is used to create the payment suggestion.
  Date	PostingDate	The posting date that is used to create the payment suggestion.
  Date	LastDueDateToPayReq	The last due date that is used to create the payment suggestion.
  Boolean	Future	Indicates if the vendor ledger entry is in the future.
  Boolean	IsHandled	[Pass by Reference] Indicates if the vendor ledger entry is handled by custom code. The standard behavior will be skipped.

• OnBeforeHandledVendLedgEntry

  This event is triggered before the vendor ledger entry is processed. It allows customization or validation of the data before the actual processing of the entry starts.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeHandledVendLedgEntry(VendorLedgerEntry: Record "Vendor Ledger Entry"; LocGenJournalLine: Record "Gen. Journal Line"; HandledEntry: Boolean)
  begin
  end;

  Type	Name	Description
  Record "Vendor Ledger Entry"	VendorLedgerEntry	The vendor ledger entry that is used to create the payment suggestion.
  Record "Gen. Journal Line"	LocGenJournalLine	The general journal line that is used to create the vendor ledger entry.
  Boolean	HandledEntry	[Pass by Reference] Indicates if the vendor ledger entry is handled by custom code. The standard behavior will be skipped.

• OnAfterGetVendLedgEntries

  This event is triggered after the vendor ledger entries are processed. It allows customization or validation of the data after the actual processing of the entries is completed.

  [IntegrationEvent(false, false)]
  local procedure OnAfterGetVendLedgEntries(var VendorLedgerEntry: Record "Vendor Ledger Entry"; Vendor: Record Vendor; PostingDate: Date; LastDueDateToPayReq: Date; UsePriority: Boolean; UseDueDateAsPostingDate: Boolean; DueDateOffset: DateFormula; Positive: Boolean; Future: Boolean; PayableVendorLedgerEntry: Record "Payable Vendor Ledger Entry"; NextEntryNo: Integer)
  begin
  end;

  Type	Name	Description
  Record "Vendor Ledger Entry"	VendorLedgerEntry	The vendor ledger entry that is used to create the payment suggestion.
  Record Vendor	Vendor	The vendor that is used to create the payment suggestion.
  Date	PostingDate	The posting date that is used to create the payment suggestion.
  Date	LastDueDateToPayReq	The last due date that is used to create the payment suggestion.
  Boolean	UsePriority	Indicates if the priority is used to create the payment suggestion.
  Boolean	UseDueDateAsPostingDate	Indicates if the due date is used as the posting date to create the payment suggestion.
  DateFormula	DueDateOffset	The due date offset that is used to create the payment suggestion.
  Boolean	Positive	Indicates if the vendor ledger entry is positive.
  Boolean	Future	Indicates if the vendor ledger entry is in the future.
  Record "Payable Vendor Ledger Entry"	PayableVendorLedgerEntry	The payable vendor ledger entry that is used to create the payment suggestion.
  Integer	NextEntryNo	The next entry number that is used to create the payment suggestion.

• OnBeforeLoopPayableVendorLedgerEntry

  This event is triggered before the loop to process the payable vendor ledger entries begins. It allows customization or validation of the data before the actual processing of the entries starts.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeLoopPayableVendorLedgerEntry(var PayableVendorLedgerEntry: Record "Payable Vendor Ledger Entry"; var SummarizePerVend: Boolean);
  begin
  end;

  Type	Name	Description
  Record "Payable Vendor Ledger Entry"	PayableVendorLedgerEntry	The payable vendor ledger entry that is used to create the payment suggestion.
  Boolean	SummarizePerVend	[Pass by Reference] Indicates if the vendor ledger entries are summarized per vendor.

• OnBeforePayableVendorLedgerEntryLoop

  This event is triggered before the loop to process the payable vendor ledger entries begins. It allows customization or validation of the data before the actual processing of the entries starts.

  [IntegrationEvent(false, false)]
  local procedure OnBeforePayableVendorLedgerEntryLoop(var PayableVendorLedgerEntry: Record "Payable Vendor Ledger Entry"; var OriginalAmountAvailable: Decimal; var AmountAvailable: Decimal; var StopPayments: Boolean; Future: Boolean; Vendor: Record Vendor; SummarizePerVendor: Boolean; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Record "Payable Vendor Ledger Entry"	PayableVendorLedgerEntry	The payable vendor ledger entry that is used to create the payment suggestion.
  Decimal	OriginalAmountAvailable	[Pass by Reference] The original amount that is available for payment.
  Decimal	AmountAvailable	[Pass by Reference] The amount that is available for payment.
  Boolean	StopPayments	[Pass by Reference] Indicates if the payments are stopped.
  Boolean	Future	Indicates if the vendor ledger entry is in the future.
  Record Vendor	Vendor	The vendor that is used to create the payment suggestion.
  Boolean	SummarizePerVendor	Indicates if the vendor ledger entries are summarized per vendor.
  Boolean	IsHandled	[Pass by Reference] Indicates if the vendor ledger entry is handled by custom code. The standard behavior will be skipped.

• OnCopyPayVendorLedgerEntryFromVendorLedgerEntry

  This event is triggered when the payable vendor ledger entry is copied from the vendor ledger entry. It allows customization or validation of the data before the actual copying takes place.

  [IntegrationEvent(false, false)]
  procedure OnCopyPayVendorLedgerEntryFromVendorLedgerEntry(var PayableVendorLedgerEntry: Record "Payable Vendor Ledger Entry"; VendorLedgerEntry: Record "Vendor Ledger Entry");
  begin
  end;

  Type	Name	Description
  Record "Payable Vendor Ledger Entry"	PayableVendorLedgerEntry	The payable vendor ledger entry that is used to create the payment suggestion.
  Record "Vendor Ledger Entry"	VendorLedgerEntry	The vendor ledger entry that is used to create the payment suggestion.

• OnUpdateTempBufferFromVendorLedgerEntry

  This event is triggered when the temporary buffer is updated from the vendor ledger entry. It allows customization or validation of the data before the actual update takes place.

  [IntegrationEvent(false, false)]
  local procedure OnUpdateTempNCPEPaymentBufferFromVendorLedgerEntry(var TempNCPEPaymentBuffer: Record "NCPE Payment Buffer" temporary; VendorLedgerEntry: Record "Vendor Ledger Entry")
  begin
  end;

  Type	Name	Description
  Record "NCPE Payment Buffer" temporary	TempNCPEPaymentBuffer	[Temporary] The temporary buffer that is used to create the payment suggestion.
  Record "Vendor Ledger Entry"	VendorLedgerEntry	The vendor ledger entry that is used to create the payment suggestion.

• OnAfterLoopPayableVendorLedgerEntry

  This event is triggered after the loop to process the payable vendor ledger entries is completed. It allows customization or validation of the data after the actual processing of the entries is completed.

  [IntegrationEvent(false, false)]
  local procedure OnAfterLoopPayableVendorLedgerEntry(var Vendor: Record Vendor; var CurrencyBalance: Decimal; GlobalLastDueDateToPay: Date; PostingDate: Date; UsePaymentDisc: Boolean; LastPmtDiscDateToPay: Date; NCPPaymentType: Option)
  begin
  end;

  Type	Name	Description
  Record Vendor	Vendor	[Pass by Reference] The vendor that is used to create the payment suggestion.
  Decimal	CurrencyBalance	[Pass by Reference] The currency balance that is used to create the payment suggestion.
  Date	GlobalLastDueDateToPay	The global last due date that is used to create the payment suggestion.
  Date	PostingDate	The posting date that is used to create the payment suggestion.
  Boolean	UsePaymentDisc	Indicates if the payment discount is used to create the payment suggestion.
  Date	LastPmtDiscDateToPay	The last payment discount date that is used to create the payment suggestion.
  Option	NCPPaymentType	The payment type that is used to create the payment suggestion.

• OnAfterOnPostVendorDataItem

  This event is triggered after the vendor data item is posted. It allows customization or validation of the data after the actual posting of the data item is completed.

  [IntegrationEvent(true, false)]
  local procedure OnAfterOnPostVendorDataItem(var Vendor: Record Vendor;
                                              GenJournalLine: Record "Gen. Journal Line";
                                              GenJournalBatch: Record "Gen. Journal Batch";
                                              GenJournalTemplate: Record "Gen. Journal Template";
                                              BankPmtType: Enum "Bank Payment Type";
                                              NCPEPmtType: Option;
                                              PostingDate: Date;
                                              LastDueDateToPay: Date;
                                              UsePaymentDisc: Boolean;
                                              LastPmtDiscDateToPay: Date;
                                              GenJournalLineInserted: Boolean;
                                              LastLineNo: Integer;
                                              NextDocNo: Code[20];
                                              var Dialog: Dialog;
                                              BalAccountType: Enum "Gen. Journal Account Type";
                                              BalAccountNo: Code[20])
  begin
  end;

  Type	Name	Description
  Record Vendor	Vendor	[Pass by Reference] The vendor that is used to create the payment suggestion.
  Record "Gen. Journal Line"	GenJournalLine	The general journal line that is used to create the vendor ledger entry.
  Record "Gen. Journal Batch"	GenJournalBatch	The general journal batch that is used to create the vendor ledger entry.
  Record "Gen. Journal Template"	GenJournalTemplate	The general journal template that is used to create the vendor ledger entry.
  Enum "Bank Payment Type"	BankPmtType	The bank payment type that is used to create the payment suggestion.
  Option	NCPEPmtType	The NCPE payment type that is used to create the payment suggestion.
  Date	PostingDate	The posting date that is used to create the payment suggestion.
  Date	LastDueDateToPay	The last due date that is used to create the payment suggestion.
  Boolean	UsePaymentDisc	Indicates if the payment discount is used to create the payment suggestion.
  Date	LastPmtDiscDateToPay	The last payment discount date that is used to create the payment suggestion.
  Boolean	GenJournalLineInserted	[Pass by Reference] Indicates if the general journal line is inserted.
  Integer	LastLineNo	The last line number that is used to create the payment suggestion.
  Code[20]	NextDocNo	The next document number that is used to create the payment suggestion.
  Dialog	Dialog	[Pass by Reference] The dialog that is used to create the payment suggestion.
  Enum "Gen. Journal Account Type"	BalAccountType	The general journal account type that is used to create the payment suggestion.
  Code[20]	BalAccountNo	The general journal account number that is used to create the payment suggestion.

• OnBeforeCheckBalance

  This event is triggered before the balance is checked. It allows customization or validation of the balance before the actual check takes place.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeCheckBalance(Vendor: Record Vendor; Result: Boolean; IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Record Vendor	Vendor	The vendor that is used to create the payment suggestion.
  Boolean	Result	[Pass by Reference] The result of the function that determines if the balance is checked.
  Boolean	IsHandled	[Pass by Reference] Indicates if the balance is handled by custom code. The standard behavior will be skipped.

• OnBeforeNCPEGetExternalBankAccount

  This event is triggered before the external bank account is retrieved. It allows customization or validation of the external bank account before the actual retrieval takes place.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeNCPEGetExternalBankAccount(var GenJournalLine: Record "Gen. Journal Line";
                                                      TempNCPEPaymentBuffer: Record "NCPE Payment Buffer";
                                                      NCPEPmtType: Option " ","Direct Debit Suggestion","Credit Transfer Suggestion","Non-SEPA Credit Transfer",,"SEPA Credit Transfer","SEPA Direct Debit";
                                                      CountryRegion: Record "Country/Region";
                                                      NCPBankAccountSetup: Record "NCP Bank Account Setup";
                                                      NCPESetup: Record "NCPE Setup";
                                                      ExternalBankAccountCode: Code[20];
                                                      IsHandled: Boolean);
  begin
  end;

  Type	Name	Description
  Record "Gen. Journal Line"	GenJournalLine	The general journal line that is used to create the payment suggestion.
  Record "NCPE Payment Buffer"	TempNCPEPaymentBuffer	The temporary buffer that is used to create the payment suggestion.
  Option	NCPEPmtType	The NCPE payment type that is used to create the payment suggestion.
  Record "Country/Region"	CountryRegion	The country/region that is used to create the payment suggestion.
  Record "NCP Bank Account Setup"	NCPBankAccountSetup	The NCP bank account setup that is used to create the payment suggestion.
  Record "NCPE Setup"	NCPESetup	The NCPE setup that is used to create the payment suggestion.
  Code[20]	ExternalBankAccountCode	The external bank account code that is used to create the payment suggestion.
  Boolean	IsHandled	[Pass by Reference] Indicates if the external bank account is handled by custom code. The standard behavior will be skipped.

• OnBeforeUpdateGnlJnlLineDimensionsFromTempNCPEPaymentBuffer

  This event is triggered before the general journal line dimensions are updated from the temporary NCPE payment buffer. It allows customization or validation of the dimensions before the actual update takes place.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeUpdateGnlJnlLineDimensionsFromTempNCPEPaymentBuffer(var GenJournalLine: Record "Gen. Journal Line"; TempNCPEPaymentBuffer: Record "NCPE Payment Buffer" temporary; SummarizePerVend: Boolean)
  begin
  end;

  Type	Name	Description
  Record "Gen. Journal Line"	GenJournalLine	The general journal line that is used to create the payment suggestion.
  Record "NCPE Payment Buffer" temporary	TempNCPEPaymentBuffer	[Temporary] The temporary buffer that is used to create the payment suggestion.
  Boolean	SummarizePerVend	Indicates if the vendor ledger entries are summarized per vendor.

• OnMakeGenJnlLinesOnBeforeTempNCPEPaymentBufferInsertNonSummarize

  This event is triggered before the general journal lines are created from the temporary NCPE payment buffer. It allows customization or validation of the general journal lines before the actual creation takes place.

  [IntegrationEvent(false, false)]
  local procedure OnMakeGenJnlLinesOnBeforeTempNCPEPaymentBufferInsertNonSummarize(var TempNCPEPaymentBuffer: Record "NCPE Payment Buffer" temporary; VendorLedgerEntry: Record "Vendor Ledger Entry"; SummarizePerVend: Boolean; NextDocNo: Code[20])
  begin
  end;

  Type	Name	Description
  Record "NCPE Payment Buffer" temporary	TempNCPEPaymentBuffer	[Temporary] The temporary buffer that is used to create the payment suggestion.
  Record "Vendor Ledger Entry"	VendorLedgerEntry	The vendor ledger entry that is used to create the payment suggestion.
  Boolean	SummarizePerVend	Indicates if the vendor ledger entries are summarized per vendor.
  Code[20]	NextDocNo	The next document number that is used to create the payment suggestion.

• OnMakeGenJnlLinesOnBeforeUpdateTempNCPEPaymentBufferAmounts

  This event is triggered before the general journal lines are created from the temporary NCPE payment buffer. It allows customization or validation of the general journal lines before the actual creation takes place.

  [IntegrationEvent(false, false)]
  local procedure OnMakeGenJnlLinesOnBeforeUpdateTempNCPEPaymentBufferAmounts(var TempNCPEPaymentBuffer: Record "NCPE Payment Buffer" temporary; VendorLedgerEntry: Record "Vendor Ledger Entry"; SummarizePerVend: Boolean)
  begin
  end;

  Type	Name	Description
  Record "NCPE Payment Buffer" temporary	TempNCPEPaymentBuffer	[Temporary] The temporary buffer that is used to create the payment suggestion.
  Record "Vendor Ledger Entry"	VendorLedgerEntry	The vendor ledger entry that is used to create the payment suggestion.
  Boolean	SummarizePerVend	Indicates if the vendor ledger entries are summarized per vendor.

Report - NCPE Suggest Customer Payments

• OnBeforeOnPreReport

  This event is triggered before the report is run. It allows customization or validation of the data before the actual report is executed.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeOnPreReportEvent(Customer: Record Customer; CustLedgerEntry: Record "Cust. Ledger Entry")
  begin
  end;

  Type	Name	Description
  Record Customer	Customer	The customer that is used to create the payment suggestion.
  Record "Cust. Ledger Entry"	CustLedgerEntry	The customer ledger entry that is used to create the payment suggestion.

• OnAfterIncludeCustomer

  This event is triggered after the customer is included in the payment suggestion. It allows customization or validation of the data after the customer and its balance are considered.

  [IntegrationEvent(false, false)]
  local procedure OnAfterIncludeCustomer(Customer: Record Customer; CustomerBalance: Decimal; var Result: Boolean)
  begin
  end;

  Type	Name	Description
  Record Customer	Customer	The customer that is used to create the payment suggestion.
  Decimal	CustomerBalance	The balance of the customer that is used to create the payment suggestion.
  Boolean	Result	[Pass by Reference] The result of the function that determines if the customer is included in the payment suggestion.

• OnGetCustLedgEntriesOnBeforeLoop

  This event is triggered before the loop to process the customer ledger entries begins. It allows customization or validation of the data before the actual processing of the entries starts.

  [IntegrationEvent(false, false)]
  local procedure OnGetCustLedgEntriesOnBeforeLoop(var CustLedgerEntry: Record "Cust. Ledger Entry"; PostingDate: Date; LastDueDateToPayReq: Date; Future: Boolean; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Record "Cust. Ledger Entry"	CustLedgerEntry	The customer ledger entry that is used to create the payment suggestion.
  Date	PostingDate	The posting date that is used to create the payment suggestion.
  Date	LastDueDateToPayReq	The last due date that is used to create the payment suggestion.
  Boolean	Future	Indicates if the customer ledger entry is in the future.
  Boolean	IsHandled	[Pass by Reference] Indicates if the customer ledger entry is handled by custom code. The standard behavior will be skipped.

• OnAfterGetCustLedgEntries

  This event is triggered after the customer ledger entries are processed. It allows customization or validation of the data after the actual processing of the entries is completed.

  [IntegrationEvent(false, false)]
  local procedure OnAfterGetCustLedgEntries(var CustLedgerEntry: Record "Cust. Ledger Entry";
                                              Customer: Record Customer;
                                              PostingDate: Date;
                                              LastDueDateToPayReq: Date;
                                              UsePriority: Boolean;
                                              UseDueDateAsPostingDate: Boolean;
                                              DueDateOffset: DateFormula;
                                              Positive: Boolean;
                                              Future: Boolean;
                                              PayableCustLedgerEntry: Record "NCPE Payable Cust. Ledg. Entry";
                                              NextEntryNo: Integer)
  begin
  end;

  Type	Name	Description
  Record "Cust. Ledger Entry"	CustLedgerEntry	The customer ledger entry that is used to create the payment suggestion.
  Record Customer	Customer	The customer that is used to create the payment suggestion.
  Date	PostingDate	The posting date that is used to create the payment suggestion.
  Date	LastDueDateToPayReq	The last due date that is used to create the payment suggestion.
  Boolean	UsePriority	Indicates if the priority is used to create the payment suggestion.
  Boolean	UseDueDateAsPostingDate	Indicates if the due date is used as the posting date to create the payment suggestion.
  DateFormula	DueDateOffset	The due date offset that is used to create the payment suggestion.
  Boolean	Positive	Indicates if the customer ledger entry is positive.
  Boolean	Future	Indicates if the customer ledger entry is in the future.
  Record "NCPE Payable Cust. Ledg. Entry"	PayableCustLedgerEntry	The payable customer ledger entry that is used to create the payment suggestion.
  Integer	NextEntryNo	The next entry number that is used to create the payment suggestion.

• OnBeforePayableCustomerLedgerEntryLoop

  This event is triggered before the loop to process the payable customer ledger entries begins. It allows customization or validation of the data before the actual processing of the entries starts.

  [IntegrationEvent(false, false)]
  local procedure OnBeforePayableCustomerLedgerEntryLoop(var NCPEPayableCustLedgEntry: Record "NCPE Payable Cust. Ledg. Entry";
                                                          var OriginalAmountAvailable: Decimal;
                                                          var AmountAvailable: Decimal;
                                                          var StopPayments: Boolean;
                                                          Future: Boolean;
                                                          Customer: Record Customer;
                                                          SummarizePerCust: Boolean;
                                                          var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Record "NCPE Payable Cust. Ledg. Entry"	NCPEPayableCustLedgEntry	The payable customer ledger entry that is used to create the payment suggestion.
  Decimal	OriginalAmountAvailable	[Pass by Reference] The original amount that is available for payment.
  Decimal	AmountAvailable	[Pass by Reference] The amount that is available for payment.
  Boolean	StopPayments	[Pass by Reference] Indicates if the payments are stopped.
  Boolean	Future	Indicates if the customer ledger entry is in the future.
  Record Customer	Customer	The customer that is used to create the payment suggestion.
  Boolean	SummarizePerCust	Indicates if the customer ledger entries are summarized per customer.
  Boolean	IsHandled	[Pass by Reference] Indicates if the customer ledger entry is handled by custom code. The standard behavior will be skipped.

• OnCopyPayableCustLedgerEntryFromCustLedgerEntry

  This event is triggered when the payable customer ledger entry is copied from the customer ledger entry. It allows customization or validation of the data before the actual copying takes place.

  [IntegrationEvent(false, false)]
  procedure OnCopyPayableCustLedgerEntryFromCustLedgerEntry(var NCPEPayableCustLedgEntry: Record "NCPE Payable Cust. Ledg. Entry"; CustLedgerEntry: Record "Cust. Ledger Entry");
  begin
  end;

  Type	Name	Description
  Record "NCPE Payable Cust. Ledg. Entry"	NCPEPayableCustLedgEntry	The payable customer ledger entry that is used to create the payment suggestion.
  Record "Cust. Ledger Entry"	CustLedgerEntry	The customer ledger entry that is used to create the payment suggestion.

• OnBeforeCheckBalance

  This event is triggered before the balance is checked. It allows customization or validation of the balance before the actual check takes place.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeCheckBalance(Customer: Record Customer; Result: Boolean; IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Record Customer	Customer	The customer that is used to create the payment suggestion.
  Boolean	Result	[Pass by Reference] The result of the function that determines if the balance is checked.
  Boolean	IsHandled	[Pass by Reference] Indicates if the balance is handled by custom code. The standard behavior will be skipped.

• OnBeforeUpdateGnlJnlLineDimensionsFromTempNCPEPaymentBuffer

  This event is triggered before the general journal line dimensions are updated from the temporary NCPE payment buffer. It allows customization or validation of the dimensions before the actual update takes place.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeUpdateGnlJnlLineDimensionsFromTempNCPEPaymentBuffer(var GenJournalLine: Record "Gen. Journal Line"; NCPEPaymentBuffer: Record "NCPE Payment Buffer" temporary; SummarizePerCust: Boolean)
  begin
  end;

  Type	Name	Description
  Record "Gen. Journal Line"	GenJournalLine	The general journal line that is used to create the payment suggestion.
  Record "NCPE Payment Buffer" temporary	NCPEPaymentBuffer	[Temporary] The temporary buffer that is used to create the payment suggestion.
  Boolean	SummarizePerCust	Indicates if the customer ledger entries are summarized per customer.

• OnUpdateTempNCPEPaymentBufferFromCustomerLedgerEntry

  This event is triggered when the temporary buffer is updated from the customer ledger entry. It allows customization or validation of the data before the actual update takes place.

  [IntegrationEvent(false, false)]
  local procedure OnUpdateTempNCPEPaymentBufferFromCustomerLedgerEntry(var NCPEPaymentBuffer: Record "NCPE Payment Buffer" temporary; CustLedgerEntry: Record "Cust. Ledger Entry")
  begin
  end;

  Type	Name	Description
  Record "NCPE Payment Buffer" temporary	NCPEPaymentBuffer	[Temporary] The temporary buffer that is used to create the payment suggestion.
  Record "Cust. Ledger Entry"	CustLedgerEntry	The customer ledger entry that is used to create the payment suggestion.

Report - NCPE Create Payment File

• OnBeforeVendorRemittanceInfoInsert

  This event is triggered before the vendor remittance information is inserted. It allows customization or validation of the data before the actual insertion takes place.

  	
  [IntegrationEvent(false, false)]
  local procedure OnBeforeVendorRemittanceInfoInsert(var NCPPaymentRemittanceEntry: Record "NCP Payment Remittance Entry"; OldVendorLedgerEntry: Record "Vendor Ledger Entry")
  begin
  end;

  Type	Name	Description
  Record "NCP Payment Remittance Entry"	NCPPaymentRemittanceEntry	The NCPE payment remittance entry that is used to create the payment suggestion.
  Record "Vendor Ledger Entry"	OldVendorLedgerEntry	The old vendor ledger entry that is used to create the payment suggestion.

• OnBeforeCustomerRemittanceInfoInsert

  This event is triggered before the customer remittance information is inserted. It allows customization or validation of the data before the actual insertion takes place.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeCustomerRemittanceInfoInsert(var NCPPaymentRemittanceEntry: Record "NCP Payment Remittance Entry"; OldCustLedgerEntry: Record "Cust. Ledger Entry")
  begin
  end;

  Type	Name	Description
  Record "NCP Payment Remittance Entry"	NCPPaymentRemittanceEntry	The NCPE payment remittance entry that is used to create the payment suggestion.
  Record "Cust. Ledger Entry"	OldCustLedgerEntry	The old customer ledger entry that is used to create the payment suggestion.

• OnAfterCreateVendorRemittanceInfo

  This event is triggered after the vendor remittance information is created. It allows customization or validation of the data after the actual creation takes place.

  [IntegrationEvent(false, false)]
  local procedure OnAfterCreateVendorRemittanceInfo(GenJournalLine: Record "Gen. Journal Line"; var NCPPaymentRemittanceEntry: Record "NCP Payment Remittance Entry"; OldVendorLedgerEntry: Record "Vendor Ledger Entry"; NoOfRmtInfoTextLines: Integer; RmtInfLength: Integer)
  begin
  end;

  Type	Name	Description
  Record "Gen. Journal Line"	GenJournalLine	The general journal line that is used to create the payment suggestion.
  Record "NCP Payment Remittance Entry"	NCPPaymentRemittanceEntry	The NCPE payment remittance entry that is used to create the payment suggestion.
  Record "Vendor Ledger Entry"	OldVendorLedgerEntry	The old vendor ledger entry that is used to create the payment suggestion.
  Integer	NoOfRmtInfoTextLines	The number of remittance information text lines that are used to create the payment suggestion.
  Integer	RmtInfLength	The length of the remittance information that is used to create the payment suggestion.

• OnAfterCreateCustomerRemittanceInfo

  This event is triggered after the customer remittance information is created. It allows customization or validation of the data after the actual creation takes place.

  [IntegrationEvent(false, false)]
  local procedure OnAfterCreateCustomerRemittanceInfo(GenJournalLine: Record "Gen. Journal Line"; var NCPPaymentRemittanceEntry: Record "NCP Payment Remittance Entry"; OldCustLedgerEntry: Record "Cust. Ledger Entry")
  begin
  end;

  Type	Name	Description
  Record "Gen. Journal Line"	GenJournalLine	The general journal line that is used to create the payment suggestion.
  Record "NCP Payment Remittance Entry"	NCPPaymentRemittanceEntry	The NCPE payment remittance entry that is used to create the payment suggestion.
  Record "Cust. Ledger Entry"	OldCustLedgerEntry	The old customer ledger entry that is used to create the payment suggestion.

• OnGenJournalLineCheck

  This event is triggered before the check of the general journal line. It allows customization or validation of the general journal line before the actual check takes place.

  [IntegrationEvent(false, false)]
  local procedure OnGenJournalLineCheck(GenJournalLine: Record "Gen. Journal Line")
  begin
  end;

  Type	Name	Description
  Record "Gen. Journal Line"	GenJournalLine	The general journal line that is used to create the payment suggestion.

• OnBeforeLoopWriteXMLLine

  This event is triggered before the loop to write the XML line begins. It allows customization or validation of the data before the actual writing of the line starts.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeLoopWriteXMLLine(var TempNCPEXmlSchemaLine: Record "NCPE XML Schema Line" temporary; var GenJournalLine: Record "Gen. Journal Line"; Type: Option Header,OrderHeader,Line,OrderFooter,Footer; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Record "NCPE XML Schema Line" temporary	TempNCPEXmlSchemaLine	[Temporary] The temporary XML schema line that is used to create the payment suggestion.
  Record "Gen. Journal Line"	GenJournalLine	The general journal line that is used to create the payment suggestion.
  Option	Type	The type of the XML schema line that is used to create the payment suggestion.
  Boolean	IsHandled	[Pass by Reference] Indicates if the XML schema line is handled by custom code. The standard behavior will be skipped.

• OnBeforeWriteXMLLineToOutStream

  This event is triggered before the XML line is written to the output stream. It allows customization or validation of the data before the actual writing of the line takes place.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeWriteXMLLineToOutStream(var TempNCPEXMLSchemaLine: Record "NCPE XML Schema Line" temporary; var GenJournalLine: Record "Gen. Journal Line"; TXT: Text)
  begin
  end;

  Type	Name	Description
  Record "NCPE XML Schema Line" temporary	TempNCPEXMLSchemaLine	[Temporary] The temporary XML schema line that is used to create the payment suggestion.
  Record "Gen. Journal Line"	GenJournalLine	The general journal line that is used to create the payment suggestion.
  Text	TXT	The text that is used to create the payment suggestion.

• OnAfterPaymentFileCreatedOnBeforeShowSummary

  This event is triggered after the payment file is created and before the summary is shown. It allows customization or validation of the data after the actual creation of the file and before the summary is displayed.

  [IntegrationEvent(false, false)]
  local procedure OnAfterPaymentFileCreatedOnBeforeShowSummary(var SendingGenJournalLine: Record "Gen. Journal Line"; var NCPClearingEntry: Record "NCP Clearing Entry"; var AutoSend: Boolean; var ProgressDialog: Dialog)
  begin
  end;

  Type	Name	Description
  Record "Gen. Journal Line"	SendingGenJournalLine	The sending general journal line that is used to create the payment suggestion.
  Record "NCP Clearing Entry"	NCPClearingEntry	The NCPE clearing entry that is used to create the payment suggestion.
  Boolean	AutoSend	[Pass by Reference] Indicates if the payment file is sent automatically.
  Dialog	ProgressDialog	The progress dialog that is used to create the payment suggestion.

• OnAfterSetNotificationText

  This event is triggered after the notification text is set. It allows customization or validation of the data after the actual setting of the text takes place.

  [IntegrationEvent(false, false)]
  local procedure OnAfterSetNotificationText(var NotificationText: Text[50]; NCPLanguageSetup: Record "NCP Language Setup")
  begin
  end;

  Type	Name	Description
  Text[50]	NotificationText	The notification text that is used to create the payment suggestion.
  Record "NCP Language Setup"	NCPLanguageSetup	The NCPE language setup that is used to create the payment suggestion.

• OnAddRmtInfOnBeforeSetRemittanceInfo

  This event is triggered before the remittance information is set. It allows customization or validation of the data before the actual setting of the information takes place.

  [IntegrationEvent(false, false)]
  local procedure OnAddRmtInfOnBeforeSetRemittanceInfo(var NotificationText: Text[50]; var RmtInf: array[20] of Text[1024]; PmtNotificationNo: Code[20]; NCPEPaymentFileSetup: Record "NCPE Payment File Setup"; NCPLanguageSetup: Record "NCP Language Setup")
  begin
  end;

  Type	Name	Description
  Text[50]	NotificationText	[Pass by Reference] The notification text that is used to create the payment suggestion.
  array[20] of Text[1024]	RmtInf	[Pass by Reference] The remittance information that is used to create the payment suggestion.
  Code[20]	PmtNotificationNo	The payment notification number that is used to create the payment suggestion.
  Record "NCPE Payment File Setup"	NCPEPaymentFileSetup	The NCPE payment file setup that is used to create the payment suggestion.
  Record "NCP Language Setup"	NCPLanguageSetup	The NCPE language setup that is used to create the payment suggestion.

Docs  /  NAVAX Payment  /  Information for Developers
 Imports

Codeunit - NCPI Import

[IntegrationEvent(true, false)]
local procedure OnBeforeFindAndOpenCustomFormatPage(NCPIImportCustFormat: Record "NCPI Import Cust. Format"; var IsHandled: Boolean)
begin
end;

[IntegrationEvent(true, false)]
local procedure OnBeforeImportFile(GlobTempBlob: Codeunit "Temp Blob"; DefaultFileName: Text; WindowTitle: Text[250]; FilterString: Text[250]; var IsHandled: Boolean)
begin
end;

[IntegrationEvent(true, false)]
local procedure OnAfterImportFile(GlobTempBlob: Codeunit "Temp Blob"; DefaultFileName: Text)
begin
end;

[IntegrationEvent(true, false)]
local procedure OnBeforeInsertImport(NCPIImport: Record "NCPI Import")
begin
end;

[IntegrationEvent(true, false)]
local procedure OnAfterInsertImport(NCPIImport: Record "NCPI Import")
begin
end;

[IntegrationEvent(true, false)]
local procedure OnBeforeImportDataSuggestBankAccount(NCPIImportData: Record "NCPI Import Data"; var IsHandled: Boolean)
begin
end;

Codeunit - NCPI Import Delete Data

[IntegrationEvent(true, false)]
procedure OnBeforeDeleteData(var SetDeleteArchivedFiles: Boolean; var SuppressError: Boolean; var SuppressConfirm: Boolean)
begin
end;

[IntegrationEvent(true, false)]
procedure OnAfterGetEntriesToDeleteCounters(var ProgressDialog: Dialog; var TotalWindowCounter: Integer; var WindowCounter: Integer; var FromDate: Date; ToDate: Date)
begin
end;

[IntegrationEvent(true, false)]
procedure OnAfterDeleteArchivedFilesOnBeforeUpdateNCPISetup(var WindowCounter: Integer; TotalWindowCounter: Integer; var ProgressDialog: Dialog; var UpdateSetup: Boolean)
begin
end;

Codeunit - NCPI Import Functions

[IntegrationEvent(false, false)]
local procedure OnBeforeJnlMatchAutomaticallyHandleImportAllocBufferAccountTypeCustomer(CustLedgerEntry: Record "Cust. Ledger Entry"; TempNCPIImportAllocBuffer: Record "NCPI Import Alloc. Buffer" temporary; var GenJournalLine: Record "Gen. Journal Line"; var IsHandled: Boolean);
begin
end;

[IntegrationEvent(false, false)]
local procedure OnBeforeJnlMatchAutomaticallyHandleImportAllocBufferAccountTypeVendor(VendorLedgerEntry: Record "Vendor Ledger Entry"; TempNCPIImportAllocBuffer: Record "NCPI Import Alloc. Buffer" temporary; var GenJournalLine: Record "Gen. Journal Line"; var IsHandled: Boolean);
begin
end;

[IntegrationEvent(false, false)]
local procedure OnAfterCheckOtherRelationsCustLedgerEntry(var TempRelationsNCPIImportAllocBuffer: Record "NCPI Import Alloc. Buffer" temporary; var TempCustNCPIImportRemittanceInfo: Record "NCPI Import Remittance Info." temporary; var Rating: Integer)
begin
end;

[IntegrationEvent(false, false)]
local procedure OnAfterCheckOtherRelationsVendorLedgerEntry(var TempRelationsNCPIImportAllocBuffer: Record "NCPI Import Alloc. Buffer" temporary; var TempVendorNCPIImportRemittanceInfo: Record "NCPI Import Remittance Info." temporary; var Rating: Integer)
begin
end;

[IntegrationEvent(false, false)]
local procedure OnAfterCheckOtherRelationsEmployeeLedgerEntry(var TempRelationsNCPIImportAllocBuffer: Record "NCPI Import Alloc. Buffer" temporary; var TempEmployeeNCPIImportRemittanceInfo: Record "NCPI Import Remittance Info." temporary; var Rating: Integer)
begin
end;

Codeunit - NCPI Online

[IntegrationEvent(false, false)]
local procedure OnDownloadContentUnknownAddressIndex(var TempBlob: Codeunit "Temp Blob"; AddressIndex: Integer)
begin
end;

Docs  /  NAVAX Payment  /  Information for Developers
 konfipay

How errors are identified

Structure of the error codes

List of all error codes and error messages with explanation

Docs  /  NAVAX Payment  /  Information for Developers
 Event Request

Docs  /  NAVAX Payment  /  Appendix
 Data Structure

Exports

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

Imports