Detailed changelog for Continia Banking 2026 R2
This article lists all new updates, features, service packs, and hotfixes for Continia Banking 2026 R2.
Tip
As a Continia partner, we can notify you of new Continia Banking versions and service packs whenever we release them. To sign up for this service, go to this page in the Continia PartnerZone (only available to partners).
Important
Continia Banking 2026 R2 supports the following version of Microsoft Dynamics 365 Business Central: Business Central 2026 R2 (v29).
Continia Banking 2026 R2
Pre-release date online: September 21, 2026
Release date, online: October 1, 2026
Release date, on-premises: Pending
Continia Banking version: 29.0.0
New functionality
| Functional area | Description | ID |
|---|---|---|
| General Application | You can now set up the same currency exchange rate provider across multiple companies from a single assisted setup process. | 83387 |
| General Application | Partner extensions can now access regulatory reporting entries and reporting types through a public API. | 82769 |
| General Application | Transaction imports from NatWest now only include booked transactions when the TransactionMutability attribute is empty. See Reconciling statements imported through Yapily. | 83024 |
| General Application | Restored compatibility for partner extensions that use the bank authentication interface. | 83113 |
| General Application | Field provenance tracking for values copied between records is now available for more tables and is no longer limited to payment entries. | 80693 |
| General Application | Text template rendering has been optimized to improve performance by reducing repeated reads of source records during text generation. | 81475 |
| General Application | Authentication sharing between companies now correctly transfers bank information, bank system mappings, active bank systems, and communication settings. The process also provides clearer error reporting when a share cannot be completed. | 82008 |
| General Application | Telemetry is now logged for each successful payment export, including information about the company, bank, bank system, and number of payment entries exported. This helps improve diagnostics and troubleshooting. | 82481 |
| General Application | You can now enter a dedicated BACS Service User Number in a new BACS ID field on supported bank cards, without using the Agreement No. field. | 77843 |
| General Application | Partner extensions can now access external codes stored by Continia Banking for accounts, payments, templates, and related records. | 83368 |
| General Application | You can now set up Business Central currency exchange rate services from a catalog of verified providers through a guided setup experience. | 83383 |
| General Application | Continia Banking now provides a catalog of verified currency exchange rate providers that is maintained through Continia Online. | 83384 |
| General Application | You can now configure automatic currency exchange rate updates through an assisted setup that recommends providers, previews rates, and schedules updates. | 83385 |
| General Application | Continia Banking now notifies you when exchange rate services require attention and provides actions to help resolve detected issues. | 83386 |
| Payment Export | You can now generate the ZABIL C1 XML report for the AWV monthly payment report to Deutsche Bundesbank. This report supports the new file-naming requirements while the Z4 export remains available for other reporting entities. For more information, see Introducing AWV reporting. | 80015 |
| Payment Export | A new Refresh Account Information setting in Payment Journal Setup lets you choose whether payment suggestion lines use account information from the ledger entry or refresh it from the current vendor, customer, or employee card. | 76702 |
| Payment Export | Payment suggestions opened from the Payment Journal now follow the same editing restrictions as the standard Payment Suggestion card. Suggestions that have already been sent or posted can no longer be edited. | 81314 |
| Payment Export | You can now export complete regulatory reporting details for payments, helping ensure payments that require regulatory reporting are processed successfully by receiving banks. | 68468 |
| Payment Export | You can now configure automatic creation of fee lines from fee details imported from bank status files, including support for currency and dimension handling. | 68645 |
| Payment Export | Other Continia apps can now add additional remittance information lines to payments before export through the Continia Connector App. | 79614 |
| Payment Export | VAT registration numbers and social security numbers can now be used as verified account identifiers for vendors, customers, and employees. Payments using updated values are held until verification is completed. | 81946 |
| Payment Export | You can now create a new banking template by copying an existing one. The new template retains the original configuration while leaving the source template unchanged. | 82503 |
| Payment Export | The field selection experience for banking templates now shows the most commonly used fields by default, with options to switch between common and all available fields. | 82506 |
| Payment Export | Find Entries now shows related Continia Banking payments and provides direct access to payment details. | 82693 |
| Payment Export | Payment suggestions now include the posting date during account validation, improving compatibility with partner solutions that require posting date validation. | 82764 |
| Payment Export | You can now manage payment suggestion templates on a dedicated card page with organized sections and a simplified list view. | 82810 |
| Payment Export | Remittance advices now follow rejected payments. Unsent advices are removed, and previously sent advices are marked as rejected. | 82819 |
| Payment Export | The Update Payment Allocation report now includes a caption, making it easier to identify in report lists. | 83125 |
| Payment Export | Word report layouts now include report captions and company information fields, making customization easier. | 83168 |
| Payment Export | You can now configure separate email scenarios for vendor and customer remittance advices, allowing different email accounts to be used. | 83213 |
| Payment Export | Remittance texts can now be merged without creating duplicate comma separators. | 83304 |
| Payment Import | You can now add filters on the Apply Entries page to make it easier to find and work with relevant entries. | 80943 |
| Payment Import | You can now import CSV bank account statements directly by using a new statement import action and CSV target type. See Setting up bank accounts for CSV ports | 70532 |
| Payment Import | You can now automatically create LCY rounding correction lines for foreign-currency bank reconciliations when split rules are applied. This helps ensure journal lines remain balanced in LCY. | 79813 |
| Payment Import | You can now view and edit dimensions, including the full dimension set, directly in the Create Manual Journal Line dialog. | 82424 |
| Payment Import | You can now view and edit dimensions directly in the Apply to Account dialog. Dimensions are automatically updated when the account changes. | 82425 |
| PSP | The Set As Imported action is now available directly on the PSP Header list page. | 80044 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | Fixed an issue where Update Status in the Payment Journal failed for Rabobank direct-connected accounts when a payment register did not yet have a Payment Batch ID. Status requests are now skipped until the ID is available. | 82782 |
| General Application | When the Vendor Invoice No. field was validated on a purchase header before it had been inserted, an error occurred. This has been fixed. | 79099 |
| General Application | Fixed an issue where authentication sharing showed bank accounts from the current company instead of the selected target company in the Share Authentication wizard. | 82007 |
| General Application | Fixed an issue where deleting a bank did not remove all related entries from Active Bank Systems, leaving obsolete records behind. | 82016 |
| General Application | Fixed an issue where account statements retrieved through BANKSapi direct communication could not be requested again if a day was skipped during import. Missing statements can now be retrieved when they become available. | 81087 |
| General Application | Fixed an issue where merged lines were not marked as Imported to Company in certain scenarios, causing them to be re-imported. | 82080 |
| General Application | Fixed an issue where BANKSapi connections became unusable when stored credentials lost their password. You can now reconnect the bank account by running the assisted setup again. | 82605 |
| Payment Export | Fixed an issue where temporary fields on the Field Selection page did not display the Temp prefix when selecting fields for customer payment reference templates. Without the prefix, it was not possible to distinguish temporary fields from standard fields. | 82760 |
| Payment Export | Fixed an issue where posting association payments could fail when a customer or vendor association contained an overpaid member. Failed previews no longer block subsequent posting attempts. | 82767 |
| Payment Export | Fixed an issue where displaying masked Bank Account No. and IBAN fields in a bank account selection list caused an error in Business Central 29. | 82776 |
| Payment Export | Fixed an issue where the End-to-End ID was overwritten when payment suggestion lines were moved between payment distribution headers. Each header now retains its own End-to-End ID. | 81618 |
| Payment Export | Fixed validation of preferred bank accounts in Payment Information Setup. The same checks used on vendor and customer cards are now applied consistently. | 81943 |
| Payment Export | Fixed an issue where payment statuses reported by Konfipay were not always reflected in the Payment Journal. The Payment Journal now shows the correct status. | 82369 |
| Payment Export | Fixed an issue where long remittance information lines could truncate document numbers during export. Additional document numbers now move to a new line when needed. | 82626 |
| Payment Export | Fixed an issue where a shared creditor reference was lost when one payment covered multiple invoices. The payment-level reference is now included correctly. | 82629 |
| Payment Export | Fixed an issue where remittance information from other invoices could appear on payment lines. Each payment line now shows only its own remittance information. | 82927 |
| Payment Export | Fixed an issue where payment suggestions failed for bank accounts without a Bank Code and displayed an unclear error message. The process now skips those accounts and continues suggesting other payments. | 83075 |
| Payment Export | Fixed an issue where a failed purchase or sales document posting could display an unrelated posted document. The prompt no longer appears after a failed posting. | 83082 |
| Payment Export | Fixed an issue where inactive SEPA direct debit mandates were blocked even when sales document validation was disabled. Mandates are now checked only when validation is enabled. | 83443 |
| Payment Export | Fixed an issue where object ID ranges overlapped between the base application and approval apps. Each app now uses a unique ID range. | 83763 |
| Payment Import | Fixed an issue where posting payment reconciliation lines failed after manual application of ledger entries on the Apply Ledger Entries page. | 81974 |
| Payment Import | Fixed an issue where the Posting Date filter on Bank Account Ledger Entries was not applied in Bank Account Reconciliation. The filter now works correctly. | 80625 |
| Payment Import | Fixed an issue where restricted characters in bank account numbers were displayed incorrectly in warning messages. Characters are now shown correctly. | 81685 |
| Payment Import | Fixed an issue where adding a search rule from text longer than 100 characters caused an error. The text is now truncated automatically to fit the Search Text field. | 81899 |
| Payment Import | Fixed an issue where bank date and time values containing milliseconds could be interpreted using the environment's time zone. Dates are now read exactly as provided. | 82460 |