Change Log
On this page, you will find a list, with descriptions of changes for the current and previous versions of Collection Management.
Bemærk
From December 2020 and forth the changelog for Collection Management is only available in English.
Collection Management 2025 R2 (27.1.0.233538)
The changes described here, applies for Microsoft Dynamics 365 Business Central Version 14 through to Version 25.
Changes to the Mastercard Betalingsservice
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | When a Customer Agreement Card is marked as Completed and has a Customer Bank Account Code applied, the system currently requires a SE/CVR number on the Customer Card. This requirement is not necessary.  | 70760 | 
Changes to the ePay / Bambora
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Agreement import may time out if the process takes longer than 100 seconds. | 69879 | 
Collection Management 2025 R2 (27.0.0.210493)
The changes described here, applies for Microsoft Dynamics 365 Business Central Version 14 through to Version 25.
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| General Application | An event has been implemented that allows applying custom values to email notification templates. | 68761 | 
| General Application | An event has been implemented that allows making changes before the system imports a new setup file. | 68943 | 
Changes to the Danske Bank Collection Service
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Collection Journal – Using the method 'Send OIOXML Credit Memo (No Cash Back)' caused a validation error stating it could not be used. Fixed. | 69048 | 
Changes to the ePay / Bambora
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Bambora/ePay – Agreement import could get out of sync if subscriptions were deleted directly in ePay. Fixed. | 69879 | 
Collection Management 2025 R1 (26.04 / 26.4.0.348574)
The changes described here, applies for Microsoft Dynamics 365 Business Central Version 14 through to Version 25.
Changes to Danske Bank Collection Service
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Collection Agreement Import Journal – Importing more than 10,000 agreements may cause an error if one or more agreement deactivation lines are included. Fixed. | 68946 | 
Collection Management 2025 R1 (26.03 / 26.3.0.276361)
The changes described here, applies for Microsoft Dynamics 365 Business Central Version 14 through to Version 25.
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| General Application | Support for the standard Business Central Billing module has been introduced. | 67172 | 
Collection Management 2025 R1 (26.02 / 26.2.0.247502)
The changes described here, applies for Microsoft Dynamics 365 Business Central Version 14 through to Version 25.
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| General Application | Support for prepayment Invoices and credit memos has been added. | 65885 | 
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Exporting multiple lines from a Mastercard Betalingsservice Collection Journal results in an error: 'Microsoft.Dynamics.Nav.Types.Exceptions.NavNCLArgumentException' was thrown.  | 66502 | 
Collection Management 2025 R1 (26.00 / 26.0.0.194495)
The changes described here, applies for Microsoft Dynamics 365 Business Central Version 14 through to Version 25.
Changes to the Danske Bank Collection Service (DBCS)
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Collection Journal - If a credit memo is merged with an invoice, the collection method is not correctly updated. This causes a validation error because the amount ends up with the wrong sign. | 63927 | 
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Collection Journal – The function “Test Reporting” throws an error if a customer name exceeds 50 characters. | 63588 | 
| Collection Systems | Collection Journal - The function "Suggest Customer Collections..." can't create lines when a filter is applied and multible payment methods are used. Code was missing in BC15-> | 63634 | 
Collection Management 2024 R2 (25.03 / 25.3.0.294318)
The changes described here, applies for Microsoft Dynamics 365 Business Central Version 14 through to Version 25.
Changes to the Mastercard Betalingsservice
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Collection Import Journal – The system now supports MasterCard Betalingsservice payment slip status reports (0686 files). | 62124 | 
Collection Management 2024 R2 (25.02 / 25.2.0.292854)
The changes described here, applies for Microsoft Dynamics 365 Business Central Version 14 through to Version 25.
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Fixed an issue where notification messages using "Limit to Document No." with two collections containing multiple entries were missing the text "Invoice" in the second line. | 62352 | 
Collection Management 2024 R2 (25.01 / 25.1.0.219777)
The changes described here, applies for Microsoft Dynamics 365 Business Central Version 14 through to Version 24.
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | An event has been implemented to determine how to approve and export the collection journal lines and/or allow for rendering messages in the client. | 60378 | 
Changes to the Danske Bank Collection Service (DBCS)
| Function Area | Description | ID | 
|---|---|---|
| Collection System | DBCS - When communicating with Danske Bank, they may return an error message that Collection Management cannot handle. This issue has now been addressed by presenting the message to the customer. | 60788 | 
Collection Management 2024 R2 (25.00 / 25.0.0.194194)
The changes described here, applies for Microsoft Dynamics 365 Business Central Version 14 through to Version 24.
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| General Application | Collection Management 2024 R2 (25.00) – Is the last version with support for Business Central April 2019 (BC v14). | |
| Collection Systems | An event has been implemented to modify the address information when exporting collection lines for the Collection Journal. | 58521 | 
Changes to the Mastercard Betalingsservice
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Job Query - CCM BS Import Payment Batch Job throws an error when the currency code imported in the Collection Import Journal doesn’t match the currency code in the Collection Journal. | 59681 | 
Changes to the Bambora/ePay
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | An event has been implemented to manage which Collection Agreement Journal lines are to be exported by the Job Queue Entry 'CCM Bambora Send Agr. Batch Job.' | 59168 | 
| Collection Systems | An event has been implemented to manage which Collection Agreement Journal Batches are to be exported by the Job Queue Entry 'CCM Bambora Send Agr. Batch Job.'" | 59168 | 
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Manually importing the Collection Management setup file does not create the email templates that the customer creates themselves. | 58793 | 
Collection Management 2024 R1 (24.03 / 24.3.0.742346)
The changes described here, applies for Microsoft Dynamics 365 Business Central Version 14 through to Version 24.
Changes to the Mastercard Betalingsservice
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Collection Import Journal - The function "Import Payment File" throws an error, if the payment files containing rejected status lines (0237): The length of the string is 128, but it must be less than or equal to 10 characters." | 59323 | 
Collection Management 2024 R1 (24.02 / 24.2.0.722447)
The changes described here, applies for Microsoft Dynamics 365 Business Central Version 14 through to Version 24.
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| General Application | Collection Journal - The function "Suggest Customer Collections..." can't create lines when a filter is applied and multible payment methods are used. | 57536 | 
Changes to the Mastercard Betalingsservice
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Using multiple payment methods with different PBS vendor numbers but the same customer group number results in all collections being processed under the first PBS vendor number. | 57442 | 
Changes to the Nordea
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Changes to the Nordea SEPA Direct Debit record format for March 2024 have been implemented. | 58326 | 
Collection Management 2024 R1 (24.01 / 24.1.0.615506)
The changes described here, applies for Microsoft Dynamics 365 Business Central Version 14 through to Version 24.
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| General Application | When activating the Collection System, a new Job Queue Entry is created. This entry can automate the Suggest Collection from the Collection Journals, creating Collection Journal entries for open customer ledger entries related to Collection Management.  | 55287 | 
| General Application | When activating the Collection System, a new Job Queue Entry is created. This entry can renumber the line numbers in the Collection Journals when a large number of lines are posted through batch posting.  | 55362 | 
| General Application | Running our Assisted Setups is now possible with a technical partner license. | 53640 | 
Changes to the Mastercard Betalingsservice
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Attaching two documents consecutively, where their combined size exceeds 70 KB, results in an error. | 51793 | 
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| General Application | In the Collection Journal, lines that are sent may encounter a Collection Management validation error. | 55529 | 
Collection Management 2024 R1 (24.00 / 24.0.0.572527)
The changes described here, applies for Microsoft Dynamics 365 Business Central Version 14 through to Version 24.
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| General Application | Currently, Collection Management supports BC v14 and the three latest versions of Business Central.  This will change with the release of Collection Management 2025 R1 (26.00) in April 2025. Collection Management 2025 R1 (26.00) and all future versions from then on will only support the three latest versions of Business Central. The next version of Collection Management – Collection Management 2024 R2 (25.00) – will be the last version with support for Business Central April 2019 (BC v14).  | |
| General Application | The Collection Journal now includes an automated feature for handling unpaid customer Collections. By specifying a duration in days, any Collections not settled within this period will be automatically removed from the Journal.  | 49833 | 
| General Application | The Page Extensions App for BC13 and BC14 has been removed, as page changes now is made in FOB's | 53161 | 
| Collection Systems | An event hook has been added, allowing users to bypass the function that attaches PDF files to notification emails and access the customer ledger entry to modify the temporary file specifying which files are attached.  | 53629 | 
| Collection Systems | An event hook has been added to be triggered when posting a sales document, allowing for the modification of the Collection System before the Collection Journal line is created | 53299 | 
| Collection Systems | New event hooks have been added:  1. Alter the Customer information, used for validation when posting a document. 2. Alter the Customer information, exported in the Collection files.  | 53875 | 
Changes to the Mastercard Leverandørservice
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Debitor Reimbursed Collections (0530) results in a incorrect Document Type. | 54353 | 
Changes to the MobilePay
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Support for MobilePay Invoice and Subscription has been discontinued due to MobilePay's transition to a new API. | 53489 | 
Changes to the Nets SEPA Direct Debit
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Support for Nets SEPA Direct Debit has been discontinued due to Nets closing the solution. | 48679 | 
Changes to the Mastercard Betalingsservice
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Deactivation of the minimal notification, when using email, is now possible, using the standard notification template instead. | 51793 | 
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| General Application | The 'Manage Lines with Closed Entries' feature within the Collection Journal now includes the capability to handle Credit Memos. | 52497 | 
| General Application | The "Create Collection Agreement" function failed to consider the configuration that prevents updating the Customer's Payment Method. | 54241 | 
| Collection Systems | Collection Journal: Suggest Customer Collections, doesn't create lines for all open Customer Ledger Entries. | 53573 | 
Collection Management 2023 R2 (9.01 / 9.1.0.431886)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 23.
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| General Application | When exporting reminders from the Collection Journal in which the due date has been modified, the corresponding Customer Ledger Entry doesn't get updated with the new due date. | 50233 | 
| Collection System | Mastercard Betalingsservice - Using email notifications, where an external document number is included, the 60-character limit can be exceeded. In this case, the amount will be removed from the lines where the total characters surpass 60.  | 50520 | 
| Collection System | A validation has been implemented to ensure the character set adheres to Mastercard's updated scheme validation requirements when transmitting files. | 50615 | 
Collection Management 2023 R2 (9.00 / 9.0.0.399565)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 23.
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| General Application | Only shared dimension values will be applied to the posted entries in the Collection Journal when lines are consolidated. | 31119 | 
| General Application | The validation for posting documents related to Collection Management failed to check if a required Collection Method was applied. | 45027 | 
| General Application | Previously in the Collection Journal, entries used their creation date as the "Document date". Now, the "Document date" is set as the payment date. | 47842 | 
| General Application | Fixed an issue where applying a value to the "Urgent Collection Method" field on the "Collection Method" page resulted in an incorrect due date on the "Collection Journal line" when the urgent method is triggered. | 50027 | 
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| General Application | Creating an agreement will now set the payment method on customers when the option "Update Customer Payment Method" is applied on Collection Management Setup. | 13499 | 
| General Application | Tiles have been updated to provide a more accurate view of the current lines in the Collection Journals. | 28233 | 
| General Application | When activating a Collection System, a new Job Queue Entry will be created. The Job Queue Entry will import information on collected or paid collections/payments. (Automating the Collection Import Journal) (Not created for Bambora) | 31356 | 
| General Application | To help users quickly identify imported mandates that require attention, a new tile has been added to the Role Center highlighting mandates with errors. To help users quickly identify imported mandates that require attention, new tiles have been added to the Role Center. These tiles highlight mandates with errors and Agreement Import/Export Journals with failed lines.  | 41966 | 
| General Application | The function 'Update Customers/Open Entries/Documents' will only perform a process on Customers who have a default agreement with a status of 'OK'. | 46221 | 
| General Application | New filter possibilities added to the "Suggest Customer Collections..." function. Now you can add filters for Customer Ledger Entries. | 46921 | 
| General Application | When activating the Collection System, a new Job Queue Entry is created. This entry automates the import/export of agreement information to and from the Collection System provider.  | 47737 | 
Changes to the Mastercard Leverandørservice
| Function Area | Description | ID | 
|---|---|---|
| Collection System | The processing of statuses for canceled collections has been improved. The final status for the line will now be displayed as "Stopped." | 49224 | 
| Collection System | Debitor Reimbursed collections resultes in a incorrect sign. | 49241 | 
Changes to the Mastercard Betalingsservice
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Support for status files 0621 has now been added to update the status of agreement mandates. | 38408 | 
| Collection System | When importing an agreement from the Collection System Provider, the event related to the agreement is now logged as an entry on the Agreement Card. | 45431 | 
| Collection System | Vendor agreement deactivations are given an incorrect agreement status, rendering the agreements unusable. | 49470 | 
Changes to the Bambora
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Using HTML code in mail templates is made possible for the Collection System Bambora. | 21765 | 
Collection Management 2023 R1 (8.03 / 8.3.0.274384)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 22.
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Collection Management App Onprem (Local app handling) reports an error when trying to access the local dll's | 47237 | 
| General Application | Posting the Collection Journal may result in an error where the document number isn't posted in the correct order throwing an error. | 47482 | 
Collection Management 2023 R1 (8.02 / 8.2.0.232541)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 22.
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Companies with Collection Management installed but not activated may experience errors with MobilePay when creating invoices or accessing the Payment Services page. | 46596 | 
Collection Management 2023 R1 (8.01 / 8.1.0.229473)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 22.
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Nordea:"When importing payment files, it's possible that the first digit in the amount may be lost, and the payment type may be changed from credit to debit, or vice versa." | 44648 | 
Collection Management 2023 R1 (8.00 / 8.0.0.211454)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 22.
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Mastercard Leverandørservice - Stopping a send Collection results in a schema validation error. | 44648 | 
| Collection System | Mastercard Leverandørservice - has updated its payment files to provide more detailed information about transactions. Specifically, they now include information on transactions that were rejected and reimbursed. | 45412 | 
| Collection System | Bambora - Invoice validation for the field Subscription was not working. | 45111 | 
| Collection System | MobilePay - The function "Change to MobilePay" throws an error when trying to send an e-mail notification (Update status), this is due to the wrong Payment method code applied to the Collection Entry. | 46267 | 
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| General Application | Collection Management is now available on our New demo portal, with a demo of the Collection systems; - Danske Bank: Collection Service / SEPA Direct debit - Mastercard Leverandørservice / Betalingsservice / SEPA Direct Debit.  | 41910 | 
Changes to the Handelsbank SEPA Direct Debit
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Jyske Bank has acquired Handelsbanken in Denmark, and as a result, support for Handelsbanken SEPA Direct Debit has been discontinued. | 43694 | 
Changes to the Mastercard Leverandørservice / Betalingsservice
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Imported agreement events are now logged as agreement entries for the individual agreement card. | 13481 | 
Changes to the Mastercard Betalingsservice
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Sending FIK collections to Customers outside Denmark where a CVR number is applied to the Customer card is now possible. | 43876 | 
Changes to the MobilePay
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Adding a QR code to your invoices is now possible through MobilePay Invoice. | 44512 | 
Collection Management 2022 R2 (7.02 / 7.2.0.95911)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 21.
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Worldline/Bambora - Canceling subscriptions will result in an incorrect index number so that some new agreements won't be imported. | 43242 | 
Collection Management 2022 R2 (7.01 / 7.1.0.90360)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 21.
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Mastercard Betalingsservice - Customer rejections performed before the due dates will result in the status "Reimbursed" instead of "Rejected". | 42938 | 
| Collection System | Danske Bank SEPA Direct Debit - Using PM and CM in the same base results in a Collection Management error when updating status and imported files that relate to Payment Management. | 43066 | 
Changes to the MobilePay module
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Invoices can now be resent without the system adding a dot to the invoice number each time. | 42774 | 
| Collection System | Support for MobilePay subscription announced changes implemented on 01-01-2023. | 41958 | 
Collection Management 2022 R2 (7.00 / 7.0.0.33914)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 21.
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| General Application | Using multiple Collection Journals may result in an error where the Collection Entry Log number has already been used. | 38321 | 
| General Application | Installing Collection Management without the proper license causes an error when the program tries to access the Assisted setup for the product. | 38514 | 
| General Application | Using the function "Modify Posting Date" from the Collection Journal could alter the posting date for lines sent. This will result in the lines being validated again, giving the line a new due date and losing the information of it awaiting a reply from the Collection System provider.  | 38940 | 
| Collection Systems | Notification of canceled transactions is now supported. | 40320 | 
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| General Application | Option to specify a Payment Method, which, when Deactivating an Agreement, is applied to the Customer Card, Open Ledger Entries, and the corresponding Documents. | 13489 | 
| General Application | A new field, "Alternative Journal line description," has been added to the Collection Journal Setup page, making it possible to specify a predefined text for the Collection Journal lines description field. | 13523 | 
| General Application | Performance optimized for the function "Update Customers/Open Entries/Documents," ensuring not to go through entries for unmarked made selections. | 34764 | 
| General Application | New feature - Collection Management now manages the process needed to handle reversed transactions for the Collection Systems. | 34796 | 
| General Application | An event hook has been added to alter a Gen. Journal line when using the function "Update Collection Jnl. Status" from the Collection Import Journal when a Refund line is created. | 34807 | 
| General Application | An event hook has been added to alter a Gen. Journal line before a Collected line is modified. | 34819 | 
| General Application | An event hook has been added to alter a Gen. Journal line before creating a Balance Entry line. | 34850 | 
| General Application | New event hooks have been added: 1. Alter Customer notification lines by adding lines after the Header line and Document no line. 2. Import Customer CVR-no. or CPR-no. from other fields instead of the current Customer CVR-no. field.  | 40262 | 
Collection Management 2022 R1 (6.03.00 / 6.3.0.0)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 20.
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Nordea SEPA Direct Debit - Collection Vendor numbers can consist of up to 35 characters, but we only allow 10. | 38528 | 
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| General Application | Performance - The function "Suggest Customer Collections" from the Collection Journal has been code reviewed, giving it a performance improvement of up to 79% (The performance increase will be highest for BC15 and newer.) | 35055 | 
Changes to the Mastercard Betalingsservice
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | An event hook has been added to alter the Customer data specified for the creation of BS agreements and Collections. | 90534 | 
Collection Management 2022 R1 (6.02.00 / 6.1.0.2)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 20.
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| General Application | Posting Gen. Journal Lines unrelated to Collection Management triggers unnecessary code that slows the system down. | 32387 | 
Collection Management 2022 R1 (6.01.00 / 6.1.0.1)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 20.
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| General Application | Sending mail notifications is not possible for BC 20 Cloud (BC 2022 Wave 1) | 32463 | 
Collection Management 2022 R1 (6.01.00 / 6.1.0.0)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 20.
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| General Application | Sending mail notifications where the posted documents are applied with long external document numbers can cause an error. | 31844 | 
| General Application | Lines transferred from a Collection import Journal to a General Cash Receipt Journal Will be applied with the default Collection agreement for the Customer. This makes it possible to import the lines into the Collection Journal for Collection or reimbursement.  | 32034 | 
| Collection Systems | DBCS - Importing a Payment file can result in a string overflow. | 31889 | 
| Collection Systems | Mastercard SEPA Direct Debit - Reimbursed collections are imported with an incorrect amount sign. | 31836 | 
| General Application | Collection Journal lines that have been sent, can be validated again, causing them to get a validation error. | 32339 | 
Collection Management 2022 R1 (6.00.00 / 6.0.0.0)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 19.
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| General Application | New mail templates have been added to the setup file.  New merge fields have been introduced.  | 13511 | 
| General Application | Merge fields are now possible for the subject field on mail notifications. | 30356 | 
| General Application | Posting documents can now be inserted directly into a predefined Collection Journal. | 30458 | 
| General Application | The following Job Queries have been introduced for all Collection systems. - Exporting collections to the system provider. - Updating status from the system provider.  | 15667 | 
| General Application | Getting started Wizards have been introduced for the following Collection Systems. - Mastercard Betalingsservice - Mastercard Leverandørservice - Mastercard SEPA Direct Debit - Danske Bank Collection Service - Danske Bank SEPA Direct Debit - Handelsbanken SEPA Direct Debit - Nordea SEPA Direct Debit. Getting started Wizards have been optimized for the following Collection Systems. - MobilePay - Bambora  | 15876 29172 29175 29182 29179  | 
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | MobilePay / Bambora - Altering a Customer number unintended changes the agreement transfer status to "To be transferred". | 28815 | 
| Collection Systems | Using Payment Management and Collection Management in the same database can result in an error when posting using a filter on the field "Status". | 31391 | 
Collection Management 2021 R2 (5.03.00 / 5.3.0.0)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 19.
Changes to the Nets Betalingsservice
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Payment Slips through Nets can trigger a scheme validation error due to missing Record Type 062 in the Collection file. | 30999 | 
Collection Management 2021 R2 (5.02.00 / 5.2.0.0)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 19.
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| General Application | Installing Collection Management can cause an error for companies where it hasn't been activated. The error can occur when opening the pages Continia solutions administration, Assisted setup, and manual setup. | 29978 | 
| General Application | Using Continia Online to send and receive files from a System provider, communication time mustn't exceed 100 seconds. To accommodate this time limit a max number of lines provided for each file has been introduced on the Collection system. | 30319 | 
Changes to the Nets Betalingsservice
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Rejected Collections/Payments will unintended be applied with the amount value from the preceding line. | 
Changes to the Nets Leverandørservice
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Rejected Collections and Payments will unintended be applied with the amount value from the preceding line. | 30337 | 
Changes to the Danske Bank - Collection Service
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Each time the certificate is used, a set of XML tags are added to the stored Certificate. | 30445 | 
Collection Management 2021 R2 (5.01.00 / 5.1.0.0)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 19.
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| General Application | Imported e-mail templates for BC19 have been applied with new reports for Invoice and Credit Memo creation. | 28269 | 
| General Application | Opening the Collection Journal or altering the posting status on the Collection Setup page, can result in an error due to a missing key. | 28304 | 
Changes to the Nets Leverandørservice
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Nets Leverandørservice - Paymentfiles from Nets can now contain more than one line with the sum of payments. | 27786 | 
Collection Management 2021 R2 (5.00.00 / 5.0.0.0)
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 18.
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Attach a batch of documents from a Zip file to the Collection lines. | 15970 | 
| General Application | Import of the setup information for Collection Management has been made into a wizard, giving the option to choose what setup information to import. | 24505 | 
| General Application | If a customer opens the Collection Journal, a check / and modify on the page Gen. Jnl. template is performed that can cause an error due to missing rights. | 24551 | 
| General Application | An event log to debug changes made on the Collection setup-, Collection System-, Collection Method-, Collection Journal Setup- and Collections Import Journal Page has been added. | 25200 | 
| General Application | When an agreement is created, the Application Method on the Customer Card will automatically be set to Manual. | 13496 | 
Changes to the Nets BetalingsService
Functionality and improvements
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | The handling of expired mandates has been improved and also with updated messages for Vendor. | 13517 | 
Changes to the Danske Bank Collection Service
Functionality and improvements
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | The handling of expired mandates has been improved and also with updated messages for Vendor. | 13517 | 
| Collection Systems | Posted Servicedocuments are now supported through the Collection System DBCS. | 13537 | 
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Importing a Payment file with multiple entries, only generate one payment line in the Collection Import Journal. The Error only occurs for BC 15 version and newer. | 26215 | 
| General Application | Fixed an issue, where the report for invoices was used instead of the dedicated report for credit notes when sending email notifications. | 25762 | 
| Platform and Technology | Bambora - The subscription number stated on the posted credit notes doesn't get applied to the Customer ledger entries. | 15949 | 
| Platform and Technology | Improvement has been made for Leverandørservice and Betalingsservice for rejected Collections/Payments, when importing files to the Collection Import Journal. | 13531 | 
| Collection Systems | From a Service invoice, Service order, and Reminder the field subscription didn't return the right value when lookup was used. | 16647 | 
| Collection Systems | The field Subscription number has been made available for "Service Credit memos". | 16651 | 
| Collection Systems | Creating a new Bambora subscription agreement doesn't get applied with the renew email template stated on the Collection method. | 24710 | 
| Collection Systems | Fixes an issue where no mail is required, but the validation in the Collection Journal fails due to missing mail address. | 24891 | 
| Platform and Technology | If only Collection Management is installed, permission sets for Continia activation (CORE) are not created. If the users aren't applied with the SUPER permission set, the users will encounter a message to activate the solution when trying to use Collection Management. | 25419 | 
| Platform and Technology | The creation of a Collection Journals Batch can result in an error from one of the fact boxes, due to a missing Collection Entry. | 25746 | 
| Collection Systems | If a Payment Method isn't created with the correct code "MobilePay" or "Bambora" Exporting subscriptions from the Agreement Export Journal will not function. | 25980 | 
Version 4.03.00 / 4.3.0.0
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 18.
Changes to the Basic module
| Function Area | Description | ID | 
|---|---|---|
| General Application | Installing Collection Management and Payment Management on Business Central 2019 Wave 2 (BC15) and newer versions will result in a validation error from Collection Management when opening a purchase invoice. | 20967 | 
Changes to the Bambora module
Functionality and improvements
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Return of Payments through Bambora can result in errors due to missing XML tags in the response from Bambora. | 26963 | 
| Collection Systems | Request for the creation of agreements results in an error in the reply from Bambora. | 26961 | 
Version 4.02.00 / 4.2.0.0
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 17.
Changes to the Basic module
Functionality and improvements
| Function Area | Description | ID | 
|---|---|---|
| General Application | The day after "Kristi Himmelfart" is missing for the Bank Holiday list. This is now added to the setup fil. | 25767 | 
Version 4.01.00 / 4.1.0.0
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 17.
Changes to the Bambora module
Functionality and improvements
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Making Collections in foreign currencies resulted in errors due to the currency codes were taken from the G/L Setup instead of the Collection Journal. | 24199 | 
Version 4.00 / 4.0.0.0
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 17.
Changes to the Basic module
Functionality and improvements
| Function Area | Description | ID | 
|---|---|---|
| Collection System | An event hook has been added to control the choice of pdf templates that are being added to mails. | 23305 | 
| General Application | General improvements to user interface. | 21398, 22751, 20964, 23391, 19867  | 
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| General Application | Fixed an issue using the build-in function Insert Conv. LCY Rndg. Lines that could result in an error when inserting new lines. | 23683 | 
Changes to the Nets BetalingsService module
Functionality and improvements
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Improved handling of reimbursed Collections/Payments. | 22606 | 
| Collection System | Improved address setup on printed Payment Slips send abroad | 13551 | 
Version 3.05 / 3.5.0.0
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 17.
Changes to the Basic module
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection System | Fixed an issue with usage registration when using Nets Leverandørservice. | 22864 | 
| Collection System | Collection Journal: Reconcile and statistics only works when balance entries are created for each line. An dialog has been added for the ones, where it don't work. | 13558 | 
Version 3.04 / 3.4.0.0
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 17.
Changes to the Basic module
Functionality and improvements
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Support changes to the XSD schema for Nets Betalingsservice.  (Comes into effect 01.03.2021)  | 22363 | 
| Collection Systems | Bambora has announced changes to its format to accommodate the PSD2 requirements.  (Comes into effect 01.01.2021)  | 22409 | 
| Platform and Technology | Objects for BC14 CU19 has been added to the Collection Management package. | 19887 | 
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| General Application | If a collection journal is set up to create balance entries per journal or per customer, the posting could fail due to an incorrect balance amount.  The was seen if there were lines with different posting dates. This could occurred if there were lines with different posting dates.  | 22315 | 
| Collection Systems | When posting a document, the function that can create a Bambora fee line to the posted document failed. | 22503 | 
Version 3.03 / 3.3.0.0
The changes described here, applies for Microsoft Dynamics NAV 2013 through to Microsoft Dynamics 365 Business Central Version 17.
Changes to the Basic module
Functionality and improvements
| Function Area | Description | ID | 
|---|---|---|
| General Application | On the Collection Journal, the function Insert Conv. LCY Rndg. Linies didn´t work .   The function can now be added to the posting function when marking the field Insert Conv. LCY Rndg. Lines on the Collection Journal Setup page.  | 20317 | 
| Collection Systems | On the Collection System Page a alternative Data provider CVR-number can now be applied in the field **Data Provider VAT registration No. **Adding a value will suppress the VAT-number registered on the Company information page.  | 20653 | 
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| General Application | On the Collection Setup page marking the field Updating Payment Method Code on the Customer-card did not function properly. | 16714 | 
| General Application | Opening the Collection Setup page was slow and could result in an error. The is caused by the external system the provides the IP address of the Service Tier. A new provider has been applied to solve the issue. The provider can now be updated from the Setup file.  | 21596 | 
| Collection Systems | When creating new Certificates from the Collection System page an error would occur if an empty XML was returned. | 21660 | 
Changes to the MobilePay module
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | For MobilePay Subscription One-off the field "Email Notification Definition" on the agreement card was not editable. | 17910 | 
Changes to the Handelsbank module
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | If an error is received from Handelsbanken, when trying to establish communication, NAV/BC is rolled back. This results in the file being loaded again even though the error has been corrected. | 21497 | 
Changes to the Bambora module
Bug fixes
| Function Area | Description | ID | 
|---|---|---|
| Collection Systems | Importing an agreement from Bambora could result in an error if an agreement already exists in the BC/NAV database. | 21947 | 
Version 3.02
De ændringer der er beskrevet her, gælder fra Microsoft Dynamics NAV 2013 til og med Microsoft Dynamics 365 Business Central version 17.
Ændringer i Basis modulet
| Issue nr. | Fejl/Funktionalitet | Type | Løsning | 
|---|---|---|---|
| 16714 | Location: Collection Setup  Function: Update Customer Payment Method Updating Payment Method Code on the Customer-card did not function properly.  | Bug | Rettet | 
| 20752 | Hvis Collection Management er installeret i databasen, men ikke anvendes i alle regnskaber, opstår der fejl, når du bogfører dokumenter i regnskaber, som ikke anvender Collection Management. | Bug | Rettet | 
| 20950 | I NAV 9-11 kan der være visse events, som ikke blev startet. | Bug | Rettet | 
Ændringer i Handelsbank modulet
| Issue nr. | Fejl/Funktionalitet | Type | Løsning | 
|---|---|---|---|
| 20431 | Understøttelse af Handelsbankens nye krav til kommunikation. Handelsbanken har lavet ændringer, der øger sikkerheden, når data udveksles.  | Feature | Understøttet | 
Ændringer i MobilePay modulet
| Issue nr. | Fejl/Funktionalitet | Type | Løsning | 
|---|---|---|---|
| 20576 | MobilePay har udvidet datoen for, hvor langt det er muligt at fremdatere MobilePay Subscription opkrævninger. Ændres fra 32 dage til 126 dage. | Feature | Understøttet | 
| 20576 | MobilePay har ændret deres beløbsgrænse, så jeres kunder fremover kan betale op til 60.000 kr. på en måned med MobilePay Subscriptions i stedet for 15.000 kr. per dag. Derfor giver Collection Management mulighed for at sende opkrævninger via MobilePay på op til 60.000 kr. | Feature | Understøttet | 
| 20576 | MobilePay har fjernet grænsen for maksimalt at kunne sende 5.000 opkrævninger pr. dag. | Feature | Understøttet | 
| 20301 | Hvis en MobilePay linje står i fejl, var det ikke muligt at anvende funktionen Skift tilbage fra MobilePay. | Bug | Rettet | 
Version 3.01
De ændringer der er beskrevet her, gælder fra Microsoft Dynamics NAV 2013 til og med Microsoft Dynamics 365 Business Central version 17.
Ændringer i Basis modulet
| Issue nr. | Fejl/Funktionalitet | Type | Løsning | 
|---|---|---|---|
| Understøttelse af Business Central 365 Release Wave 2 (BC17) | Feature | ||
| 20300 | Ved aktivering af funktionen Skift tilbage - fra MobilePay sker der intet | Fejlrettelse | Rettet | 
| 20579 | Opgradering 1.30 (CM1.30 UPD1B.FOB )til NAV 2017 henviste til et forkert felt. | Fejlrettelse | Rettet | 
Version 3.00
De ændringer der er beskrevet her, gælder fra Microsoft Dynamics NAV 2013 til og med Microsoft Dynamics 365 Business Central version 16.
Ændringer i Basis modulet
| Issue nr. | Fejl/Funktionalitet | Type | Løsning | 
|---|---|---|---|
| 13579 | Der er nu lavet understøttelse af Business Central Onpremises og Cloud. | Feature | |
| 13451 | Opsætningsfilen for Collection Management hentes nu fra vores Continia-Online | Feature | |
| Kommunikation til de eksterne opkrævningscentraler forgår nu som standard fra Continia-Online. Dette kan afviges ved opsætning. | |||
| 16496 | Vi har forbedret performance på følgende funktioner Opkrævningskladde - Lav forslag - Forbedret med op til 15% Opkrævningskladde - Godkend og udlæs - Forbedret med op til 40% Opkrævningskladde - Bogføring - Forbedret med op til 5%  | Feature | |
| Installation på Multi-tenancy miljøer er nu fuld ud understøttet. | Feature | ||
| 13580 | Ved opsætningen af opkrævningscenter kan det være nødvendigt at vide Ip-adressen for servicen der kører NAV/BC installationen, dette kan give problemer ved anvendelse af Cloud løsninger. | Feature | Ip-adressen for den maskine som Service-tieret anvendes vises nu på "Opkrævningsopsætnings" siden. | 
| 13554 | Funktionen Efterudlign 0-beløb fra opkrævningskladden fik ikke sat et billagsnummer. | Fejlrettelse | Rettet, så der nu automatisk vil blive sat et bilagsnummer. | 
Version 2.04.
De ændringer der er beskrevet her, gælder fra Microsoft Dynamics NAV 2013 til og med Microsoft Dynamics 365 Business Central version 14.
Ændringer i Collection Management Basis modulet
| Issue nr. | Fejl/Funktionalitet | Type | Løsning | 
|---|---|---|---|
| 2708 | Det er nu muligt ved hjælp af opgavekøer at automatiseret bogføringsprocessen af udvalgte opkrævningskladder. | Feature | |
| 2715 | Det er nu muligt at få opdateret debitors betalingsformskode, når opkrævninger skiftes til MobilePay, og hvor opkrævningerne bliver gennemført | Feature | |
| 2778 | Bogføring af Salgsordre fejler på validering af feltet EAN nummer. | Bug | Valideringen er ændret. | 
| 2504 | Ved udlæsning af IBAN numre fra Bankkto, i forbindelse med SEPA Direct Debit, fejler filerne da formaterne ikke understøtter mellemrum i IBAN numre. | Feature | Mellemrum fjernes nu fra IBAN nummer feltet, der sendes til opkrævningssystemerne. | 
| 2178 | email advisering har fået tilføjet kvikfelterne  "Udligningsbilagstype" og "Udligningsbilagsnr."  | Feature | |
| 2570 | Ved indlæsning af status filer, kan opkrævningsposten få ændret status efter at den har nået sin slut status. | Featur | Opkrævningsposten ændres nu ikke efter at den har nået sin slutstatus "Posteret" | 
Ændringer i Collection Management Nets Betalingsservice modulet
| Issue nr. | Fejl/Funktionalitet | Type | Løsning | 
|---|---|---|---|
| 2549 | Ved import af aftalefiler fra Nets, er det nu muligt at tildele aftalerne til debitorer, hvor der ikke er nogen sammenhæng mellem aftalenumrene og debitornumrene fra aftalekortet. | Feature |