Would you like to know what has changed in the extension? Below you'll find an overview of the new features and changes made in the updates.
Version 21.2.2.4
as of Business Central 21 2024/12/12
Modifications
Update of the NAVAX Payments Base extension.
The resourceExposurePolicy settings of the extension have been changed.
The SWIFT Code and IBAN fields on the pages Vendor/Customer Bank Account List and Vendor/Customer Bank Account Card have been moved to the NAVAX Payment Base.
Corrections
Fixed an error that considered payment discount tolerance in posting, but not in the payment suggestion list and the payment file.
In the payment suggestion list, the totals did not show the respective bank account, instead they showed Other.
The formatting of the cash discount amount in the payment suggestion list has also been corrected.
Version 21.2.2.3
as of Business Central 21 2024/10/28
Modifications
Order of the fields SWIFT Code and IBAN changed on the Vendor/Customer Bank Account List and Vendor/Customer Bank Account Card pages.
Corrections
When using the Business Central standard functionality Apply Entries with NAVAX Payment Exports installed, a permission error occurred if the user was not assigned the NCPE permission.
Fixed an error in the calculation of the discount tolerance.
If the discount tolerance was not activated in the General Ledger Setup (no discount tolerance period specified or 0D set) and the following constellations occurred:
Discount date and discount tolerance date are the same both discount and discount tolerance were posted, leaving the payment entry with an open balance.
Discount tolerance date is after the discount date discount date has passed and discount tolerance date applies - the discount tolerance was posted with the amount of the discount, even though the discount tolerance amount = 0 was entered in the entry.
In the vendor payment suggestion, the bank accounts were not filled if the Preferred Bank Account field was filled in the entry.
In the vendor payment suggestion, entries were not suggested because the filter on the Exported to Payment File field or the value was set incorrectly.
After executing a payment suggestion, an incorrect message was displayed at the end. The message was confusing as it stated that there could still be suggestions with other currencies.
When applying vendor/customer ledger entries, an error message occurred due to missing permissions if the user was not assigned the permission set NCPE, NAVAX Payment Exports.
Version 21.2.2.1
as of Business Central 22 2024/10/01
Improvements
The action Show Payment File has been added to the page NCP Exports Payment File - Summary.
For more information, see Tasks, Exports, Payment File Summary.
Modifications
When using direct debit mandates for multiple bank accounts, it is now ensured that the specific values of the respective mandate are used in the payment suggestion instead of adopting the values of the master mandate.
Version 21.2.2.0
as of Business Central 21 2024/09/27
Improvements
The setup of the placeholder character for the SEPA Direct Debit Mandate ID Separator has been added to the NCP Exports setup.
For more information, see Setup, Exports, SEPA-Direct Debit-Mandates.
When using master mandates, the values of the master mandate are now entered or exported in the payment suggestion and in the create payment file function.
Actions for creating and canceling payment files as well as displaying the payment statistics have been added to the three-dot menus in the journal lines.
XML Schema SDD - AT - Rulebook 2023 - Version 4 has been added to the download.
Modifications
Removal of obsolete code parts.
Corrections
When using the function Renumber Document Numbers, it could happen that numbers were assigned twice if lines with the status Payment File Status Created were already present in the journal lines.
Correction in the XML Schema SDD - AT - Rulebook 2023 - Version 2 of the node <ReqdColltnDt>.
If the main bank account of a customer/vendor was changed via the journal lines, the field Preferred Bank Account Code on the customer/vendor was not updated. This led to incorrectly filled bank accounts and payment methods in the Payment Suggestion.
When exporting payment files, the field Exported in Payment File in the journal lines and the customer/vendor entries was not set correctly. An entry was marked as exported even though there was still an open balance.
Version 21.2.1.1
as of Business Central 21 2024/09/13
Modifications
The functionality for employee payments has been removed from NCP Payment Exports.
When creating a payment file, only the part of the direct debit mandate ID that is before the underscore (“_”) is now exported. This additional functionality allows the same direct debit mandate ID to be used for multiple customers.
Corrections
The journal line check in the payment suggestions has been revised. Now, all journals are automatically checked, and already suggested or balanced entries are listed in an overview. The option Check Other Journal Batches has been removed.
The document type in the payment suggestion list was not translated into the respective user language for lines of a overpayment.
In the payment suggestion list, the incorrect amount was printed in case of overpayment.
Version 21.2.1.0
as of Business Central 21 2024/08/22
New Product Name
The NCPE Payments Export extension has been renamed to NAVAX Payment Exports.
Improvements
Menu structure in the accountant role center tidied up.
Modifications
The logo of the extension has been changed.
Corrections
The payment suggestions ignored entries with document type Refund when the option Check Other Journal Batches was activated.
In the Payment Suggestion List, a line of type Payment was printed if a suggested document was within the Discount Tolerance.
If a bank account was specified in the NCP Preferred Bank Account Code field on a purchase invoice, it was not included in the entries when posting.
Correction of the text af the error message that occurred when checking the payment status in a ledger entry line that had already been exported or sent.
Version 21.2.0.4
as of Business Central 21 2024/08/01
Improvements
Redesign of the menu structure in the payment journal pages and cash receipt journal pages.
Modifications
If a value was entered in the Creditor/Customer Entry in the Recipient Bank Account field, it was previously ignored in the payment suggestion. The logic of bank account determination in the payment suggestion has now been revised: If a value is present in the Recipient Bank Account field, it will be used. Additionally, the bank account determination for debtor entries has been expanded to consider a direct debit mandate ID selected in the documents, which overrides everything else. If neither applies, the bank account will be searched based on the External Bank Account Search option in the NCPE Payments Export Setup.
Removal of obsolete code parts.
User experience improvements.
Corrections
After creating a payment file, before the NCPE Payment File - Summary page was opened, a message with an additional placeholder appeared.
If the option Check Other Ledger Sheet Names was activated during the payment proposal, it led to an error message if the Payment File Status for an entry in another ledger sheet was already set to File Created
Version 21.2.0.3
as of Business Central 21 2024/07/23
Corrections
During the installation of NCP Payment Base, an entry was mistakenly created in the license management. This error has been fixed, and an update routine has been created to delete the entry.
Version 21.2.0.2
as of Business Central 21 2024/07/05
Modifications
The customer and vendor bank account cards have been revised so that the fields IBAN and SWIFT Code are no longer displayed as mandatory.
The check in the payment and cash receipt journal has been revised. For non-SEPA transfers, the fields IBAN and SWIFT Code are no longer required, which correctly reflects the status.
Corrections
Under certain constellations, there were data locks in the Payment Journal page, which prevented further work.
Version 21.2.0.1
as of Business Central 21 2024/07/03
Corrections
The option Check Other Journal Batches in the NCPE Suggest Customer Payments or NCPE Suggest Vendor Payments was not taken into account.
When creating a direct debit or payment suggestion with the option Incl. Debtors with Credit Balance - Total or Incl. Creditors with Credit Balance - Total, some creditors/debtors were not taken into account even though they did not have a credit balance.
Version 21.2.0.0
as of Business Central 21 2024/06/21
Important
For On-Premises an update of the License or the following granules is required:
1001710 NCPE Payments Export by NAVAX
Improvements
Preparation for integration of konfipay Connector
Change in the payment method field in the ledger entries. Now only the available payment methods are displayed in the respective ledger entry.
The download of bank codes has been improved. Previously, it was necessary to maintain the URLs for downloading the bank codes before the download could be initiated.
This has been simplified by automatically starting the download as soon as the bank code download is triggered.
The download of bank codes now occurs in JSON format to improve download performance.
New option "Summary after creation" added to the NCPE setup.
For more information, see Setup, Exports, Exports Setup.
For creditor/customer bank accounts, the SWIFT code field has been expanded with a lookup to the SWIFT Codes table.
New option "Yes - Structured" added to recipient address in the XML schemas. This is required to comply with the new specification of the SEPA schemas implementing the ISO20022 standard.
Functionality to display the payment file in the clearing entries added.
The customer payment suggestion in the payment journal page has been renamed to Customer Direct Debit suggestion.
The payment file status field in the ledger entry lines is no longer displayed in bold and red as it caused confusion, if a line needs to be checked, it is now displayed in yellow.
Corrections
When downloading bank codes from multiple sources, the source was not indicated in the notifications or error messages. This has now been corrected as it is very helpful for analysis to know which source caused an event.
Some tooltips have been corrected.
Filters have been applied to the debtor payment suggestion for creditor entries.
Revision of the update or display of the payment status in the payment ledger entries.
There was an error during posting or preview posting in the Cash Receipt Journals when a Refund was present in the lines.
Version 21.1.7.2
as of Business Central 21 2024/04/11
Modifications
Download URLs for the Bank Codes have been updated.
Corrections
In the payment and cash receipt journals, the field Payment File Status showed Check if no SWIFT Code was specified on the customer/vendor bank account, even though the XML schema used, which was specified on the bank account, had Dom. IBAN Only enabled.
In the SEPA region, specifying the SWIFT Code is generally not necessary.
Version 21.1.7.1
as of Business Central 21 2024/02/19
Note
This version is also available as a downgrade version for Business Central 20 and 19.
Corrections
The function Consider Payment Discount Tolerance considered the discount tolerance date but did not reduce the amount in the ledger entry by the discount.
Version 21.1.7.0
as of Business Central 21 2024/02/12
Important
For On-Premises an update of the License or the following granules is required:
1001710 NCPE Payments Export by NAVAX
Improvements
The logic behind the Payment File Status field has been improved in the Gen. Journal Line table. The settings and parameters of the bank account are now also taken into account.
On the pages Payment Journal and Cash Receipt Journals the info box Payment File Error has been added. This info box shows the errors per journal line that would prevent the payment file from being exported.
In the NCPE Payments XML Schemas the Extended Character Sets have been extended for all XML schemas, the characters äüöÄÜÖß have been added since most banks accept these characters in the payment files.
In NCPE Suggest Vendor Payments and NCPE Suggest Customer Payments, the options Consider Payment Discount Tolerance have been added. Previously, the value of the Pmt. Discount Date field from the entry was taken into account.
For more information, see Tasks, Exports, Make Payment Suggestions.
New option Without Reductions added to the reports NCPE Suggest Vendor Payments and NCPE Suggest Customer Payments. The indicator is used to ensure that entries that would reduce the amount (credit memos, reductions) are not included in the payment suggestion.
For more information, see Tasks, Exports, Make Payment Suggestions.
Modifications
Calling up the pages Bank Account Setup and Pay with QR-Code from the role center has been changed. Previously, the pages were opened in view mode, so editing had to be activated on the pages before settings or changes could be applied.
In the payment suggestions, refunds were suggested although the option Summarize per Vendor/Customer was activated, so an error occurred when creating the payment file.
After calculating the payment suggestion, vendors/customers which had a credit balance in total (e.g. an invoice has already been posted but not yet due in this payment suggestion) were incorrectly included in the suggestion and written as refunds in the journal, which blocked the creation of a payment file.
In the NCPE Payments Export Setup an incorrect report was specified as Pmt. Notification Report ID, this has been corrected and an upgrade routine has been created to correct the report ID. The initial value has also been corrected.
Error in the creation of the QR code when the function Pay with QR-Code was activated. If no default bank account was set up for payments with QR code, the process was canceled after selecting the bank account to be used for QR code creation.
Due to the installation of the extension, the totals were not always printed on the A4 documents when using the RDLC report layouts.
If the option Summarize Per Vendor/Customer has been selected in the payment suggestion, the dimensions have not been transferred consistently to the journal lines.
In the assisted setup, the name of the field Creditor Identifier (CI) was previously County.
Version 21.1.6.5
as of Business Central 21 2023/11/17
Improvements
Improvement of user experience - actions in the Payment- and Cash Receipt Journal pages have been reorganized.
Improvement for developers: The propagateDependencies option is now set.
Modifications
Update of the NCP Payments Base extension.
Version 21.1.6.4
as of Business Central 21 2023/09/25
Corrections
When creating a Purchase Invoice with a Payment Method linked to a G/L account to automatically apply the invoice immediately with a payment during the posting process, the vendor ledger entries of the invoice have been posted with balance 0 but are incorrectly posted with Open=YES.
Version 21.1.6.3
as of Business Central 21Important Update 2023/08/07
Improvements
It is now possible to block collective transactions at vendor level. If the Collective Transaction Not Allowed option is activated for a vendor, no collective transactions will be created for the vendor in the Payment Journal.
Corrections
Error correction of the collective transactions functionality. In report 70322082 NCPE Create Payment File, the variable AllowCollectiveTransactions could be changed via an event. Setting it to false had an impact on Collective Transactions in conjunction with Payment Reference or One-Time Transfers.
Version 21.1.6.2
as of Business Central 21Important Update 2023/06/26
Corrections
In the report Payment Suggestion List, the payment discount is shown twice because the payment discount tolerance was calculated incorrectly although a payment discount was already granted.
Obsolete events have been revised. The OnUpdateTempPaymentBufferFromCustomerLedgerEntry and OnBeforeUpdateGnlJnlLineDimensionsFromTempPaymentBuffer events in the NCPE Suggest Customer Payments report are available again.
When importing data (SEPA schemes, bank codes), the number of overwritten data records was not displayed correctly.
Version 21.1.6.1
as of Business Central 21Important Update 2023/06/15
Corrections
Payment discount tolerance was drawn incorrectly although a discount was to be granted if the Block Payment Tolerance value was changed on the customer/vendor.
GUI improvements in Cash Receipt and Payment Journals concerning the Payment File Status.
The import function Initialize SEPA Countries has been redesigned. Previously, there was a query for changes to the NCP SEPA field. This is not necessary as it is a field of the NCP Payments app and can therefore be overwritten.
The value of the field Payment File Status was determined incorrectly when the function Summarize per Customer/Vendor was selected in the payment suggestion.
Version 21.1.6.0
as of Business Central 21 2023/06/07
Important
For On-Premises an update of the License or the following granules is required:
1001710 NCPE Payments Export by NAVAX
Improvements
On the NCPE Payments XML Schema or NCPE Payments XML Schemas page a new action Allowed Character Set has been added. With this action you can configure the allowed characters which are valid for the purpose in the payment file. This is necessary if your bank allows a different character set than the standard of the SEPA scheme.
A new field Umlaut Conversion has been added to the NCPE Payments XML Schema table. This can be used to control whether or not umlauts should be converted for usage purposes. The conversion converts e.g.: an Ä to an Ae.
New field Pmt. Notification Report ID added in the NCPE Export Setup. With this, a possibility was created to define own report layouts for the payment notifications.
New fields Payment Notification Report ID, Clearing List Report ID, SEPA Mandate Report ID, Zlg. Default List Report ID and their captions have been added to the NCPE Export Setup. Herewith a possibility was created to deposit own report layouts for the printouts.
.
When updating and reinstalling, the NCP SEPA indicator in the Countries/Regions table were updated each time, this has now been disabled - so installation should be faster.
Modifications
Some actions have been renamed and rearranged in the payment journals.
The action Initialize NCP SEPA Countries on the page Countries/Regions has been redesigned. The function now creates a record if it does not exist. If an entry exists, the record will be updated.
Corrections
Actions and fields of NCPE Payments Export and NCPI Payments Import have been moved. Before it was not possible to use Business Central standard for e.g.: Payment File Export if NCPI Payment Import was installed. The same applies to NCPE Payments Export.
The payment file status field was not updated after creating a payment file. The error has been fixed.
Actions in the payment journals were cleaned up.
The captions in the NCPE Initial Setup Wizard were not translated into German.
In the NCPE Initial Setup Wizard, the link to the NCP Payment Language Setup was incorrect, the Languages page was opened instead of this page.
The action Initialize NCP SEPA Countries on the page Countries/Regions has been renamed to Initialize SEPA Countries.
Version 21.1.5.0
as of Business Central 21 2023/03/27
Improvements
The Check Other Journal Batches option has been added to the payment suggestions. If this option is enabled, entries that are already in other journals will not be taken into account and will be skipped. This prevents the journal lines from being edited more than once.
Payment and cash receipt journals have been improved. It is now easier to see if journal lines are ready to be exported to a payment file or if values are still missing. With the newly added Payment File Status field, you can see at first glance whether a line is ready for payment file export. If one or more errors occur in the line, an overview with the errors can be opened using DrillDown.
The Preferred Bank Account Code field on Accounts Payable or Accounts Receivable is now filled with the bank account that is marked as Main Bank Account. If you change the value for Preferred Bank Account Code, the Main Bank Account flag on the bank account will be automatically adjusted.
When creating a purchase document, the Preferred Bank Account Code field will be prefilled if a bank account code has been specified on the vendor. The bank account that is stored on the purchase document will then be taken into account in the payment suggestion and written in the journal line.
The External Bank Account Code field has been removed from the accounts payable, accounts receivable and journal. entries. Instead of the External Bank Account Code, the Recipient Bank Account field from standard is now used. An upgrade routine to convert to the new field is run during installation to prevent data loss.
The field Mandat ID was removed from the journal lines because there is the field Direct Debit Mandate ID in the standard and this can also be used. An upgrade routine has also been created to upgrade the field during installation.
Bankcodes Download URL's updated and provided as download.
Corrections
Layout der Zahlungsvorschlagsliste korrigiert. Es wurde eine zusätzliche Seite ausgegeben da die Seitenränder nicht korrekt waren.
Version 21.1.4.0
as of Business Central 21 2022/11/30
Business Central Update
Improvements
Tooltips on the XML Schema Lines page have been improved so that the description of the columns is now more understandable. This should make editing the schemas easier.
Actions structure has been improved. The new action groups introduced with Business Central have been integrated into the current version of NCPE Payments Export and the menu structure has been improved.
Corrections
The Incl. Vendors with Credit or Incl. Customers with Credit functions in the payment suggestion reports did not work properly.
When opening the NCPE Initial Setup Wizard for the first time, an error occurred stating that the record does not exist.
The NCPE Initial Setup Wizard was created several times in the GuidedExperience, which caused the NCPE Payment Setup and the Setup Wizard are shown more than once.
An error in the NCPE Mail Management codeunit has been fixed. This prevented the automatic update of Business Central when NCPE Payments Export was installed.
Version 20.1.3.2
as of Business Central 20Important Update 2022/09/06
Corrections
Error in payment suggestions, creditor and debtor payment suggestion created wrong applications and entries.
The calculation of the payment tolerance when executing the payment suggestion incorrectly calculated the discount, which caused the wrong suggestion to be written in the journal.
Missing options in the payment suggestion reports have been readded.
Version 20.1.3.1
as of Business Central 20Important Update 2022/08/25
Corrections
When posting Sales Documents, a message appears that a customer entry could not be found if there is no NCP Pay with QR Code setup.
Version 20.1.3.0
as of Business Central 20 2022/08/12
Business Central Update
Corrections
The table relation of the External bank Account Code field in the Vendor Ledger Entry table has been corrected.
Improvements
The possibility to select a layout has been added to the report NCPE Payment Suggestion List. It is now possible to decide via the Report Layout Selection page whether the payment suggestion list should be printed in portrait or landscape format.
The Execution Date used in the payment proposals can now be pre-configured in the NCPE setup as Date Formula.
For Non SEPA transfers, address data for the receiving bank is also required in many countries, this has now been added to the XML Schemas so that it can be included in the schemas.
For OnPrem installations, events have been created, providing a way when creating SEPA XML files to allow a default location without download with query.
The Payment Notification Texts have been extended by a text editor, so now texts copied from e.g. Word can be pasted into the text editor.
On the page Countries/Regions the action NCP Initialize SEPA countries was added to enable the subsequent automatic setup of the SEPA countries. Use this action if the SEPA column has no values. Normally all SEPA countries are set up automatically during the installation of NCPE Payments Export, but in some constellations it is still necessary to set them up again automatically.
A new function has been integrated in NCP, this allows to add a QR Code to invoices for the functionality Pay with QR-Code.
In NCPE Setup an action has been added which allows to update the bank code URL's. The action starts the download of the URL's from www.navax.app, the data is continuously updated so that the latest URL's can always be fetched.
Progress indicators built into all relevant functions. These include the payment suggestions and the payment file creation.
The fields, Incl. Customers with neg. Balance and Incl. Vendors with pos. Balance, in the NCPE Setup, have been renamed to Incl. Customers with Credit and Incl. Vendors with Credit, for better understanding.
.
Necessary code updates for the new Business Central release.
Version 19.1.2.0
as of Business Central 19Important Update 2022/03/31
Improvements
New fields, Incl. Customers with neg. Balance and Incl. Vendors with pos. Balance, added in the NCPE setup. These are used to exclude debtors/creditors with credit balance in the payment suggestion.
The recipient of the e-mail is now entered in the payment entry after sending a payment notification. This is possible since an update from Microsoft.
Payment Notification layout improved.
Corrections
In the payment suggestion for certain constellations there was still an error message: "Currency" does not exist. Identified fields and values: Code = ''. This has been fixed.
Translation of the Document Type column in the Payment Suggestion List report has been corrected and layout has been changed for a better overview.
Error message during payment suggestion: Too many key fields were specified, therefore "SEPA Direct Debit Mandate" could not be retrieved. The number of fields in the primary key is 1. The function call has been changed.
Error in function call of the payment notification report corrected. It happened that the payment notification numbers are different than the ones in the e-mails to the customers..
Version 19.1.1.0
as of Business Central 19 2022/02/25
Business Central Update
Improvements
NCP bank codes are also inserted on the employee page.
Deprecated email features (SMTP Mail) are removed from NCPE Payments Export as they will soon be unavailable in Business Central, instead the advanced email features are used.
Modifications
Bank Codes Download URL's updated.
Actions and fields related to licensing have been removed from NCPE Payments Export as they have all been added centrally in the NCEX Extension Base extension.
Corrections
When updating the exchange rate, an error occurred regarding the currency with code '', this was fixed and an upgrade routine was created. Added the new field ISO LCY Code in the NCPE Payments Export Setup, this field is now used instead of the record in the currency table and should be filled before use, this does not apply to new installations. For new installations the field will be automatically filled with EUR if in the General Ledger Setup in the LCY Code field the value EUR or EURO has been specified.
For more information, see Setup, Payments Export Setup.
When creating payment advices for customers who had not specified a language code, the error message "Invalid language code specified: 0." appeared.
The error in the payment suggestion has been corrected, it prevented the external bank account code from being correctly assigned in the journal.
The Payment Suggestion List has been edited to show longer descriptions, previously the lines were truncated.
Version 18.1.0.0
as of Business Central 18 2021/08/10
Corrections
Fixed an error when sending notification emails via the new email features.
Introduced the new onboarding feature of Dynamics 365 Business Central to all pages where it makes sense.
Some Events added for extensibility.
The new Email feature from Dynamics 365 Business Central is now used to send the Payment Notification emails.
Modifications
Code requirements for Dynamics 365 Business Central version 18 implemented.
Permission sets converted to the new permission objects.
Bank Codes Download URL's updated.
Changed UI of the Assisted Setup.
Changed the behavior how the UI shows messages to the user - we now showing Notifications instead of message boxes to the user.
Corrections
The menus in the Payment and the Cash Receipt Journals was broken and now these are fixed.
The Payment Type field in Payment and Cash Receipt Journal was not filled correctly. Now the field will be filled as expected.
Keys renamed in several tables.
The address checks in the One Time Transfer page now working correct.
Version 17.0.0.0
as of Business Central 17 2020/12/01
Business Central Update
Improvements
Installation routine (new installation) now creates the required standard entries in the tables: Languages, Countries/Regions, SEPA Mandate Text Lines and Payment File Setup.
For more information, see Export Einrichtung, Zahlungsverkehr Export Einrichtungsassistent.
Modifications
Captions of some fields corrected.
Code requirements for Dynamics 365 Business Central version 17 implemented.
Functions that are no longer needed are marked as obsolete - they will be deleted in a future release.
Bank Codes Download URL's updated.
In the Assisted Setup on the SMTP Mail Setup page a button has been added to access the standard SMTP settings. Now you can change the email settings without leaving the wizard.
The Overview of Available XML Schemas in the NCPE Payments Bank Account Setup now only views the relevant schemas according to the country code assigned to the bank account.
Text of the AssisstEdit message boxes for the fields "File name" and "Remittance" has been made more readable.
Error in the XML Schema card where the fields IBAN Only possible, IBAN or Account Number possible, Address possible, Charges possible and Urgent Payment possible were not filled correctly (the options were filled incorrectly according to the available schema).
For more information, see Export Einrichtung, Zahlungsverkehr XML Schemata.
Display error when AssisstEdit the "File Name" field in the "Payment File" section of the NCPE Export Setup page.
Release Notes Payment Exports
