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, Service Pack 1
Release date, online: November 1, 2026
Release date, on-premises: pending
Continia Banking version: 29.1.0
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| General Application | Translatable source strings have been updated across Authentication, Bank Account, Bank System Setup, Payment Status, PSP, and CSV Import, including captions, tooltips, and labels on the affected pages, tables, and codeunits. Users working in non-English languages will see improved and up-to-date translations, with no changes to existing functionality. | 58769 |
| General Application | For a valid Norwegian IBAN, the IBAN lookup now fills in the Bank Account No. field with the full 11-digit account number from the IBAN instead of a shortened number. Bank accounts that already hold a shortened number are not corrected automatically, but a new lookup offers the full number. | 84629 |
| General Application | Service ID filtering on the Bank Files page and in automatic downloads now also includes Danske Bank files returned without a service ID by matching their parent file reference to a configured service ID. Previously, these files were excluded once service IDs were set up. Service IDs on the Service IDs page can now contain only letters and digits. | 84873 |
| General Application | You can now use the assist edit button on the Archive File Path field to browse for a folder, the same way as the File Path field. | 85106 |
| Payment Export | A new Translated Fixed Text method in a Banking Template's field selection lets you maintain a fixed text per language, so each vendor, customer, or employee receives it in their own language. | 84342 |
| Payment Import | A new Apply After Payment Date setting in Banking Import Setup lets Banking Import match a payment to an open customer or vendor invoice, or an open G/L entry, dated after the payment. This covers cases such as a webshop, where the customer pays before the invoice is posted. See Applying payments to entries dated after the payment in Continia Banking. | 78834 |
| Payment Import | Added information on the Merge Lines page that enables the user to see the text the bank statement line was matched to the search rule on and also the text the merge of the line was based on. | 80839 |
| Payment Import | Added support for importing a FIK file (PBS Sector) file into the Payment Reconciliation Journal. The feature has to be enabled in Continia Feature Mangement. See Importing FIK payments into the payment reconciliation journal. | 80851 |
| Payment Import | You can now enable the preview feature Post Sum per Payment Batch in the Continia Feature Management page to post one bank account entry per payment batch and posting date when you post the Payment Reconciliation Journal. This option is available in Banking Import Setup and the posting options dialog, adds the Payment Batch No. column, and can’t be used together with Post Sum per Posting Date. | 84904 |
| Payment Import | Partner extensions can now set the processing type per Direct Debit Return Entry and add custom fields when it is created or posted. This also enables processing returns for customer payments that are still open or only partially applied, not only fully applied ones. | 85849 |
| PSP | PSP external references that belong to a custom reference rule are now updated by a new job queue. Custom references are generated automatically, not only during setup. | 84339 |
| PSP | PSP matching now supports customer ledger entries with a blank document type in addition to Invoice and Credit Memo. Blank document types can now be matched as expected. | 84522 |
Bug fixes
| Functional Area | Description | ID |
|---|---|---|
| General Application | On the CTS-CB Authentication Entries page, audit fields such as Bank Code, Bank System Code, and Last Updated could be edited even though insertion and deletion were already blocked. This has been fixed, and the page is now read-only. | 84961 |
| General Application | We now remove the Payment Journal Setup when the batch or its journal template is deleted. Previously the setup stayed behind, so a new batch with the same name silently picked up the old approval, field restriction, summarizing and automatic sending settings. | 85188 |
| General Application | When the daily Refresh Token job ran for a Direct bank system without a stored credential, the following error occurred for Rabobank and Bizcuit: - The date is not valid. This has been fixed, and the job now skips bank systems without a stored credential instead of failing or sending invalid authentication data to Continia Online. | 85220 |
| General Application | When CAMT.054 transactions were imported for a bank account that uses BANKSapi EBICS, for example with Import New Payments in the Payment Reconciliation Journal, one of the following errors occurred: - Bank Access Guid is required. - You cannot import transactions from today. This has been fixed. The first camt.054 import now asks you for a start date. | 85296 |
| General Application | When the Azure Blob Storage guide was run again for a bank account, PSP agreement, or CSV port, existing folders kept using the previous storage account, so import or export could use the wrong container or fail. This has been fixed, and folders now follow the newly selected account. | 86207 |
| General Application | When the Azure Blob Storage guide was run for a bank account without folder setup while two or more other bank accounts of the same bank had one, only the last of those accounts was offered for copying its folders. This has been fixed, and each of those accounts is now offered. | 86244 |
| Payment Export | In Payment Journals > Summarizing Payment Setup, the tooltip for Exclude Entry Types had the meanings of All and No swapped and used Vendor instead of Recipient. This has now been fixed, and the German tooltip translation for No is handled through Crowdin. | 68604 |
| Payment Export | When approvers had Email Notification set to Never, a failed notification could leave the payment journal stuck in Pending Approval status after approval was completed. This has been fixed, and the status now updates correctly. | 82045 |
| Payment Export | When Amount (LCY) was changed on a line in the Payment Journal or Direct Debit Journal, or validated on purchase and sales documents, validation gave stale, wrong, or missing results. This has been fixed; Amount (LCY) is now revalidated and calculated correctly, including rounding for foreign currency. | 84461 |
| Payment Export | When payment allocations were used on a purchase or sales document, each allocation and the main payment were validated using the full document amount instead of each allocation's own amount. This has been fixed, so amount-based validation rules now apply correctly on documents with allocations. | 84484 |
| Payment Export | Direct debit mandates that have not been used for 36 months are now only blocked automatically by journal lines created by Continia Banking, such as Banking journals and payment suggestions. Journal lines from elsewhere, such as Business Central's own Direct Debit Collections, no longer block them, so customers who do not use Continia Banking for direct debits keep their mandates open. | 84934 |
| Payment Export | We no longer ask whether to send remittance advice mails automatically when exporting payments where none of them will send a remittance advice by email, for example when the vendor is set to Bank Only. The question is now only shown when at least one payment will actually send an email. | 84940 |
| Payment Export | When you clicked Mandate ID must be specified on the Payment Suggestion Card, it could fail with the following error occurred: The Gen. Journal Line does not exist. Identification fields and values: Journal Template Name='',Journal Batch Name='',Line No.='0'. This has now been fixed by validating that the related record exists before drill-down, and the error source for Mandate ID now points to the suggestion head’s SEPA Mandate ID so the drill-down opens the Payment Suggestion Card. | 85149 |
| Payment Export | When a vendor, customer, employee, or bank account with verified details was deleted or renamed, its verification history was lost and the account could need to be verified again. This has been fixed, and verification history is now kept and automatically restored when the account is re-created or renamed. | 85327 |
| Payment Export | When pending changes to a vendor bank account's secure fields were rejected, the fields were cleared or reset to an outdated value instead of the latest verified value. This has been fixed, and rejecting pending changes now restores the current verified values. | 85417 |
| Payment Import | In the Payment Reconciliation Journal, lines found by a search rule with both a merge rule and an account stayed in status Search Rule Matched and never became Completed, and Apply to Account wasn't available for that status. These lines now become Completed on the search rule's account, like lines from any other search rule. | 82833 |
| Payment Import | When a bank system's setup was updated, the Default Statement Description Template and Default Payment Description Template fields on the bank account card were automatically filled in, even after a user had cleared them. This has been fixed, and bank system updates no longer change these fields. | 83039 |
| Payment Import | Fixed a bug where overdue entries setting on the Customer Statement Report caused records not to be created for use in the reconciliation. | 84502 |
| Payment Import | When you used Create Manual Journal Lines in Bank Acc. Reconciliation with multiple statement lines selected, the dialog was shown once for each line. The dialog is now shown only once, and the information from the first dialog is used for the remaining lines. | 85415 |
| Payment Import | When Match GLOE was enabled, filling the ledger entry buffer for automatic matching read G/L Entry once for every open G/L entry, which made matching slow on reconciliations with many open entries. This has been fixed by reading the payment IDs in batches instead. | 85831 |
| Payment Import | On the Bank Acc. Reconciliation page, when a split rule split a bank statement line into multiple journal lines and an incoming document was attached to one of them, the following error occurred: Posted must be equal to 'No' in Incoming Document: Entry No.=<Entry No.>. Current value is 'Yes'. This has now been fixed, and you can post the journal lines with the incoming document attached to the posted entries. | 85876 |
Continia Banking 2026 R2, hotfix 1
Release date, online: October 14, 2026
Release date, on-premises: pending
Continia Banking version: 29.0.1
Bug fixes
| Functional Area | Description | ID |
|---|---|---|
| CSV Import | When importing a CSV file with Import Target set to Account Statement, Fee Alternative Descriptions were not applied. This issue has been fixed. | 84472 |
| CSV Import | Special characters in imported CSV Port configurations could be displayed incorrectly because of an encoding issue. Imported files are now read using the correct character encoding. | 84481 |
| General Application | When an authentication was shared to another company or bank, target company bank accounts remained Not Ready until Bank Account Setup was run again. Accounts now correctly become Ready, and the sharing process has been improved for account mapping and reporting. | 82318 |
| Payment Export | When remittance lines added after payment creation exceeded bank limits, the default remittance advice text was used instead of the configured template. The remittance advice template from Banking Export Setup is now used. | 83928 |
| Payment Export | When Summarize per Account and Find Payment Discounts were enabled, entries with payment discount dates on bank closing days were not summarized together. These entries are now combined into a single payment. | 84038 |
| Payment Export | Regulatory reporting codes from purchase and sales orders were not retained after posting, causing payment validation failures in some cases. The codes are now preserved on posted entries. | 84351 |
| Payment Export | Suggested vendor payments were not reduced by open payment allocations marked On Hold. Payments are now reduced by all open allocations regardless of their hold status. | 84456 |
| Payment Export | In advanced payment suggestions not summarized per account, opposing entries such as credit memos could be marked as paid together with payment entries. Opposing entries can no longer be marked as paid in these scenarios. | 84470 |
| Payment Export | Validation in advanced payment journal setup could incorrectly report that Bank Code was missing. Payment entries now correctly use the bank account's bank code. | 84742 |
| Payment Export | Using Apply Entries or changing Applies-to Doc. No. could still recalculate amounts on payment journal lines already sent to the bank or under approval. Amounts on these lines can no longer be changed through application updates. | 84847 |
| Payment Export | RemoveApprovalRestriction relied on user permissions and exact text matching to identify workflows. It now uses Business Central workflow lookup to identify and remove matching Continia approval restrictions. | 84952 |
| PSP | Performance issues when generating external payment references caused most reported banking errors. Processing of external payment reference records has been optimized for significantly better performance. | 84486 |
| PSP | Changing the PSP Code on a PSP Agreement did not update related search rules and reconciliation settings. These settings are now updated automatically when the PSP Code changes. | 84501 |
Continia Banking 2026 R2
Pre-release date online: September 21, 2026
Release date, online: October 1, 2026
Release date, on-premises: October 8, 2026
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. See Using field templates in Continia Banking. | 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. See Using field templates in Continia Banking. | 82506 |
| Payment Export | Find Entries now shows related Continia Banking payments and provides direct access to payment details. For more information, see Showing Continia Banking payments in Find Entries. | 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 |