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

Actions

• Suggest Data

  Using the action Suggest Data, the data of the last one-time transaction (with the same account type/account number) can be suggested. The action only brings values if a Payment File has already been created for the combination of account type and account number. 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
 Working with Payment Imports

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

Data Structure

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

Basic workflow

1. Select NAVAX Payment > Imports on the starting page of Business Central or ☰ > NAVAX Payment > Imports if you are not in the Accountant role.
2. Click on the action Import.
3. Select the file you want to import.
4. The import is executed. If not all bank accounts have been detected automatically, click on Data and select the Bank Account manually.
5. As long as there is no journal/reconciliation line for an import entry, you can still delete the line. Click Import to re-import deleted data.
6. Click on the action Transfer.
7. Open the Journal to clear open entries or the Bank Account Reconciliation to match the data with your bank account.
8. You can then post the imported entries.

• Import payment files

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

     Tip

     Files can also be imported over the Dropzone for Bank Files by Drag & Drop. For more information, see Import Tasks, Import Payment File.
     The import is executed. If not all bank accounts have been detected automatically, click on Data and select the Bank Account manually.
  4. As long as there is no journal/reconciliation line for an import entry, you can still delete the line. Click Import to re-import deleted data.

• Transfer Transactions

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

  Note

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

  • Journal

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

  • Bank Account Reconciliation

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

Docs  /  NAVAX Payment  /  Tasks  /  Imports
 Import Payment File

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

   Note

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

   Note

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

   Note

   As long as there is no journal line or reconciliation line for an import line, you can delete the line. Click Import to re-import deleted data.

NCPI Dropzone for Bank Files FactBox

Functionality

Docs  /  NAVAX Payment  /  Tasks  /  Imports
 Applying Open Entries

1. If the journal is not yet open, select NAVAX Payment > Imports on the Business Central home page or ☰ > NAVAX Payment > Imports if you are not in the Accountant role. Select the desired import line and click on Open Journals.
2. Click on
   • NCP Imports > Import Suggest Application - All Lines, to create an automatic suggested application for all lines.
   • NCP Imports > Import Suggest Application - Line, to create an automatic suggested application for the marked line.
   The system attempts to determine the Account No. and the corresponding open entries based on various criteria.

   Note

   This only applies to those lines for which the Applied indicator is not set
   For lines that contain a value in the field Account No. , this value is used as a filter for the entry search. In the following sequence, the system attempts to determine a Account No. or Clearing Documents for each line:
   1. The system checks whether a Fixed Account Allocation exists for the line. Example In the Fixed Account Allocation, it is defined that G/L account 241203 is used if the Remittance Info contains the word "tax office". The first line contains this account. For more information, see Setup, Fixed Account Allocations.

      Note

      With G/L accounts, the description may not be written in the journal line. This is due to the setting Omit Default desc. in Jnl on the G/L account. The option specifies if the default description is automatically inserted in the Description field on journal lines created for this general ledger account.
   2. If the Remittance Info contains a Document No. of a receivable or External Document No. of a vendor invoice, this Document No. is searched for in the database. The appropriate customer or vendor is determined and the payment is applied. Example:: The Remittance Info of the third line contains a Document No.. Customer and document no. are assigned. The line is applied and automatically receives the indicator Applied.
   3. If the remittance Info contains a customer/vendor number, the system searches the database for a suitable customer/vendor number. Applying with an open entry is not possible because the document number is not known.

      Tip

      In order to still get a suggested application, the option Keep Account Allocation can be activated in the NCP Imports Setup, so that the customer/vendor is suggested for the line, even if no document is found. Example: The Remittance Info of the second line contains a number that is not found in the database. However, a customer with this number could be found. The customer is assigned to the line.
3. Click on the NCP Imports > Import Deviation - Set Filter button to only show lines that have not yet been fully applied or that have no G/L account entered in the Account No. field.
.

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

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. For more information, see Tasks, Imports, Working with Payment Imports.

• Account Card

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

Actions, Navigate

• Fixed Account Allocations

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

Docs  /  NAVAX Payment  /  Reports and Analysis  /  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. For more information, see Tasks, Imports, Import Payment File.
• Applying open entries. For more information, see Tasks, Imports, Applying Open Entries.
• Perform a reconciliation with your bank account. For more information, see Tasks, Imports, Bank Account Reconciliation.

Fields

Import Date	Shows when the data was imported.
Import Time	Shows when the data was imported.
Import User ID	Shows from which user the data was imported.
File Format	Shows the file format of the imported file.
Imported File	Shows the name of the imported file.
Archived Import File Exists	Shows you if an archived import file already exists.
No. of Data	Shows the number of imported data entries.
No. of Data without Bank Allocation	Shows the amount of data without bank assignment. Note If the bank allocation does not match during import, the bank allocation can be entered manually. To do this, open the NCP Imports Data either by clicking in the field or by selecting the action Navigate > Data.
Bank Account No.	If the NCP Imports data all have the same bank account, the bank account number is displayed here. If the accounts are different, no value is displayed. Note If a bank account is detected when importing a payment file, the system first checks whether fixed account allocations exist.
Bank Account Name	If the NCP Imports data all have the same bank account, the bank account name is displayed here. If the accounts are different, no value is displayed.
Bank Account IBAN	If the NCP Imports data all have the same bank account, the bank account name is displayed here. If the accounts are different, no value is displayed.
No. of Transactions	Shows the number of imported transactions.
Open Journal Lines	Shows if data has been transferred to an general journal and if there are open general journal lines. Note Depending on the setting used in the NCP Imports Setup, under the respective file format setting, this field may or may not be displayed. For more information, see the Business Central online help, at Working with General Journals.
Posted Journal Lines	Shows if data has been transferred to an general journal and general journal lines have been posted. Note Depending on the setting used in the NCP Imports Setup, under the respective file format setting, this field may or may not be displayed. For more information, see the Business Central online help, at Working with General Journals.
Open Reconciliations	Shows if data has been transferred to an reconciliation and if there are open reconciliation lines. Note Depending on the setting used in the NCP Imports Setup, under the respective file format setting, this field may or may not be displayed. For more information, see the Business Central online help, at Working with General Journals.
Posted Reconciliation Lines	Shows if data has been transferred to an reconciliation and reconciliation lines have been posted. Note Depending on the setting used in the NCP Imports Setup, under the respective file format setting, this field may or may not be displayed. For more information, see the Business Central online help, at Working with General Journals.
Posted Statements	Shows if data has been transferred to a bank account reconciliation and posted statements are available. Note Depending on the setting used in the NCP Imports Setup, under the respective file format setting, this field may or may not be displayed. For more information, see the Business Central online help, at Working with General Journals.
Posted Statement Lines	Shows if data has been transferred to a bank account reconciliation and if there are posted statement lines. Note Depending on the setting used in the NCP Imports Setup, under the respective file format setting, this field may or may not be displayed. For more information, see the Business Central online help, at Working with General Journals.
Message Date	Shows when the file was created (File info: CreDtTm).
Message Time	Shows when the file was created (File info: CreDtTm).
Message Recipient Name	Shows the name of the recipient of the file (file info: MsgRcpt Nm).
Additional Info.	Shows additional information (file info: AddtlInf).
Entry No.	Specifies the number of the entry that was assigned to it when it was created from the specified number series.

Actions, Process

• Import

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

• Export Archived Import File

  Starts the download of the archived import file.

Actions, Transfer

• Transfer

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

Actions, Report

• Import List

  This list shows information about the imported file.

Actions, Navigate

• Data

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

• Transactions

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

• Open Reconciliations

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

  Note

  This action is only available if the option Bank Acc. Reconciliation has been set up in the NCP Imports Setup, in the field camt.053 - Statement or MT940 - Account Statement.

• Open Journal Lines

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

  Note

  This action is only available if the option General Journal has been set up in the NCP Imports Setup, in the field camt.053 - Statement or MT940 - Account Statement.

• Posted Statement

  In this overview, the posted statements are listed.

  Note

  This action is only available if the option Bank Acc. Reconciliation has been set in the NCP Imports Setup, in the fields camt.053 - Account Statement, camt.054 - Debit Credit Notification, MT940 - Account Statement or Custom.

• Additional Info.

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

Import Data

Fields

Statement No.	Shows the bank statement number (file info: LglSeqNb). The lookup function opens the NCP Imports Data Card page, this provides a better overview of the bank statement.
Statement Date	Shows the date of the bank statement (file info: CreDtTm).
Statement from	Shows the statement period (file info: FrToDt FrDtTm).
Statement to	Shows the statement period (file info: FrToDt FrDtTm).
Bank Account No.	The import tries to determine a bank account for each data row based on various criteria. If not all bank accounts were suggested automatically, select the bank account number manually. The next time you import a file with the same criteria, the bank account is suggested.
Bank Account Name	If the NCP Imports data all have the same bank account, the bank account name is displayed here. If the accounts are different, no value is displayed.
Bank Account IBAN	If the NCP Imports data all have the same bank account, the IBAN is displayed here. If the accounts are different, no value is displayed.
No. of Balances	Shows the number of imported balances in the bank statement. The lookup function opens the NCPI Payment Import Balances page.
No. of Transactions	Specifies the number of imported transactions. The Lookup function opens the NCPI Payment Import Transactions page.
Open Journal Lines	Shows that data has been transferred to a journal and that there are open journal lines. The lookup function opens the corresponding journal. Note Depending on the setting used in the NCP Imports Setup, under the respective file format setting, this field may or may not be shown. For more information, see the Business Central online help, at Working with General Journals.
Posted Journal Lines	Shows if data has been transferred to a journal and journal lines have been posted. Note Depending on the setting used in the NCP Imports Setup, under the respective file format setting, this field may or may not be shown. For more information, see the Business Central online help, at Working with General Journals.
Open Reconciliation Lines	Shows if data has been transferred to a bank account reconciliation and open reconciliations exist. The lookup function opens the corresponding reconciliation. Note Depending on the setting used in the NCP Imports Setup, under the respective file format setting, this field may or may not be shown. For more information, see the Business Central online help, at Working with General Journals.
Posted Reconciliation Lines	Shows if data has been transferred to a bank account reconciliation and if there are posted reconciliation lines. Note Depending on the setting used in the NCP Imports Setup, under the respective file format setting, this field may or may not be shown. For more information, see the Business Central online help, at Working with General Journals.
Posted Statements	Shows if data has been transferred to a bank account reconciliation and posted statements exist. Note Depending on the setting used in the NCP Imports Setup, under the respective file format setting, this field may or may not be shown. For more information, see the Business Central online help, at Working with General Journals.
Posted Statement Lines	Shows if data has been transferred to a bank account reconciliation and posted statement lines exist. Note Depending on the setting used in the NCP Imports Setup, under the respective file format setting, this field may or may not be shown. For more information, see the Business Central online help, at Working with General Journals.
IBAN (Bank Account No.)	Shows the IBAN or account number of the imported data (file info: Acct Id IBAN (Acct Id Othr Id)).
SWIFT-Code (Bank Branch No.)	Shows the SWIFT code or the bank branch code of the imported data (file info: Acct Svcr FinInstnId BIC (Acct Svcr FinInstnId Othr Id)).
ISO Bank Currency Code	Shows the ISO bank currency code of the imported data (file info: Acct Ccy).
Additional Information	Shows additional information of the bank statement (file info: AddtlInf). The lookup function opens the NCP Imports Additional Information page.
Closing Booked last Statement	Shows the closing balance of the last booked account statement.
Sum Transaction Amount	Shows the total of the booking amounts from the imported bank file.
Closing Booked	Shows the current closing balance, reduced by the booking amounts from the imported bank file.
Entry No.	Shows the number assigned to the record. The application assigns a unique number to each record.
Import Entry No.	This field contains the number of the import.

Import Data, Actions

• Suggest Bank Account

  This function can help to suggest already used bank accounts.

• Transfer

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

• Balances

  The balances from the NCP Imports are listed here.

• Transactions

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

• Additional Info.

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

• Open Reconciliations

  This action opens the page Bank Account Reconciliations, where the transferred entries from import are listed, if any exist.

• Posted Statements

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

Import Balances

Import Transactions

Import Transactions, Actions

• Transfer 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. For more information, see Tasks, Imports, Working with Payment Imports.

• Remittance Info.

  Opens the overview of the Remittance Info lines for this Transaction. Each row in the NCP Imports window can contain several data entries, which in turn can contain several transactions. The transactions in turn can contain several remittance info. lines and charges.

• Charges

  Opens the overview of charges for this Transaction. Each row in the NCP Imports window can contain several data entries, which in turn can contain several transactions. The transactions in turn can contain several remittance info. lines and charges.

• Additional Info.

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

Import Charges

Import Remittance Infos

Import Additional Infos

Docs  /  NAVAX Payment  /  Archive  /  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. Tasks, Imports, Working with Payment Imports

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

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