Detailed changelog for Continia Banking 2026 R1
This article lists all new updates, features, service packs, and hotfixes for Continia Banking 2026 R1.
Tipp
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).
Wichtig
Continia Banking 2026 R1 supports the following version of Microsoft Dynamics 365 Business Central: Business Central 2026 R1 (v28).
Continia Banking 2026 R1, Service Pack 1
Pre-release date online: May 8, 2026
Release date online: May 8, 2026
Release date, on-premises: pending
Continia Banking version: 28.1.0
New functionality
| Functional Area | Description | ID |
|---|---|---|
| CSV Import | A new column mapping system replaces hardcoded dimension positions in the CSV Port. It introduces flexible CSV‑to‑field mapping, including support for document type values flowing to Gen. Journal Lines. See Setting up CSV Ports. | 73527 |
| CSV Import | A new Setup CSV Port action has been added to the CSV Port page, providing a guided setup experience from the port page. | 76754 |
| General Application | Bank account verification now also covers vendor, customer, and Payment Information Setup records, including sensitive fields like Creditor No.. Verified values are reused across related records and auto‑approved. Unverified fields now block approval and export on key documents, including journals, invoices, sales documents, and payment suggestions. The Role Center and record pages highlight items that require attention. | 65542 |
| General Application | You can now automatically match bank account ledger entries from CAMT.053 files with related CAMT.054 entries created during posting. Enable Sum Posting per Posting Date on the Banking Import Setup page when posting CAMT.054. The feature is available on the Continia Feature Management page. For Swiss localizations, default CAMT Reference templates are assigned automatically during activation. | 60832 |
| General Application | Document type determination during application in the Bank Account Reconciliation and Payment Reconciliation Journal has been improved. The system now evaluates account type, amount sign, and original document type together. This ensures correct document types and prevents posting errors caused by mismatches, including for entries migrated from OPplus or Dynamo. | 69819 |
| General Application | The Bank Account Setup wizard for Yapily, Bizcuit, and Rabobank now removes authentication entries created during incomplete setups while preserving existing entries. The Rabobank wizard also correctly marks the setup as finished when it closes automatically after validating credentials. | 76841 |
| General Application | A confirmation dialog is now shown when you share authentication between related banks. Confirming copies authentication details to the target bank and updates its active bank system and linked accounts accordingly. | 77022 |
| General Application | Instructional text in the Bank Account Setup assisted guide has been clarified. The finish step no longer references a disabled Next button, and the Back button is consistently disabled. | 77198 |
| General Application | A new Search in File Archive action has been added to the File Archive List page. The report scans the content of every archived file matching the specified date range and transaction type, and opens the File Archive List filtered to files whose content contains the search text. See Troubleshooting source files. | 77415 |
| General Application | The AUDDIS payment status handling pipeline has been improved. SEPA Direct Debit lifecycle messages (AUDDIS Arrival, Input, Withdrawal, Input Test, File Acceptance, File Rejection, and Submission Component History) can now be matched and updated through a dedicated bank-specific handler before falling through to the generic CAMT status processor. | 77413 |
| Payment Export | A new Payment Information Setup capability has been introduced, allowing payment information to be managed and reused across customer, vendor, and employee records. | 70866 |
| Payment Export | A new Complete Suggestion From Template action has been added to the Payment Suggestions page. The action opens a template selection dialog and applies the filters and settings from the selected payment suggestion template, including Use Bank Account and Use Payment Method. The Excl. Account without Due Bal. field is automatically disabled when association is activated. The suggestion reports for vendor, customer, and employee payments preserve the template reference. | 73274 |
| Payment Export | Association and linking payments now respect the summarization configuration. Posting lines are grouped per account and applied using a shared Applies-to ID, rather than being posted as separate entries. | 73368 |
| Payment Export | All Message Type values from Finnish vendor ledger entries are now correctly transferred through payment suggestion, payment journal, and payment entry. New Message Type (FI) and Invoice Message fields have been added to the Payment Entry, Payment Entry Archive, Payment Ledger Entry, and Payment Suggestion Line tables. The previous Invoice Message (FI) field has been obsoleted, and its data is migrated automatically during upgrade. | 76144 |
| Payment Export | The full range of Danish NemKonto payment methods (NKC, NKV, NKVP, NKVS, NKS) is now supported for vendors, customers, and employees. New identification fields have been added: Social Security No. on Customer and Vendor, SE No. and P No. on Customer, Vendor, and Employee, and VAT Registration No. on Employee. The values are mapped to the corresponding Payment Entry creditor fields and included in the inhouse file structure during payment file creation. | 77258 |
| Payment Export | Country/region matching during payment entry creation now uses the ISO Code field on the Countries/Regions page instead of the Code field. Environments with custom country codes no longer receive false IBAN validation errors. The ISO Code field must be populated for the countries used in payment processing; in standard environments, ISO codes are present by default. | 77559 |
| Payment Export | The payment suggestion now allows a discount amount higher than the originally posted Remaining Pmt. Disc. Possible on a ledger entry. The same mechanism used for reduced discount amounts applies: the field is temporarily updated to the new value, and the original is preserved so it can be restored when needed. | 77416 |
| Payment Export | Three new publisher codeunits have been added to enable partner extensibility for payment validation and export blocking: CTS-PE Pmt. Sugg. Head Pub. (event OnAfterCheckPaymentSuggestionHead), CTS-PE Gen. Jnl. Line Pub., and CTS-PE Check Jnl. Line Bef. Exp. Pub. Partners can subscribe to these events to enforce custom validation rules and block payment exports without modifying the base application. See Extending Banking Export. | 77106 |
| Payment Export | The internal extensibility surface for alternate payment entry data has been replaced by a single public publisher on CTS-CB Pmt. Entry Mgt. Publ., backed by four scope-specific temporary buffer tables: CTS-CB Alt. Pmt. Account, CTS-CB Alt. Pmt. Creditor, CTS-CB Alt. Pmt. Creditor Bank, and CTS-CB Alt. Pmt. Debtor. A parallel buffer, CTS-CB Alt. Rem. Info. Line, supports partner-supplied remittance long-advice lines. Bank-account fields are now partner-settable. The previous surfaces CTS-CB External Payment Entry (table 71553695) and CTS-CB Pmt. Entry Mgt. Ext. Publ. (codeunit 72282348) are obsolete pending and continue to fire in parallel during the deprecation window. Existing subscribers must migrate before version 29.0. | 77420 |
| Payment Export | The CTSPEIsBankingJournal variable on the Payment Journal page extension has been moved to the protected variable area, allowing partner extensions to read it. | 77388 |
| Payment Export | Improved payment allocation calculations by using actual invoice VAT, added preview, editing, and recalculation features. | 70509 |
| Payment Export | Added support for editing, adding, and recalculating payment allocations after posting. | 70595 |
| Payment Export | Extended payment allocation functionality with preview, VAT-only option, and post-posting edits. | 70597 |
| Payment Export | Added BASt allocation type and enhanced allocation flexibility, preview, and extensibility. | 70598 |
| Payment Export | Added bulk recalculation of allocations and improved preview and editing options. | 70599 |
| Payment Export | Added allocation preview on invoices and improved post-posting flexibility. | 70600 |
| Payment Export | Added option to disable payment allocation calculation per invoice. | 70601 |
| Payment Export | Added extensibility for allocation lines and improved preview and recalculation features. | 73259 |
| Payment Export | Added template-level configuration for bank account and payment method usage. | 73364 |
| Payment Export | Fixed payment status import performance issues by reducing SQL calls and optimizing matching logic. | 74621 |
| Payment Export | Introduced a core data model for storing payment remittance details for future functionality. | 75832 |
| Payment Export | Added new validation interfaces and operators to support related record validation and remittance scenarios. | 75833 |
| Payment Export | Added interfaces and loaders to support extensible remittance data handling. | 75834 |
| Payment Export | Introduced data loaders and interfaces to standardize remittance information mapping and extensibility. | 75835 |
| Payment Import | A new Allow Multiple Applications option on payment reference rules lets matching create proposals for all matching entries instead of stopping at the first match. | 75641 |
| Payment Import | Added per-bank-account control over document number assignment. | 76495 |
| Payment Import | Improved document number handling and visibility across reconciliation pages. | 76496 |
| Payment Import | Two new fields, Document No. Matching and External Document No. Matching, have been added to the Banking Import Setup page in the General section. Both are enabled by default and are visible when Show more is enabled. The fields are initialized automatically for existing setups during upgrade. | 76266 |
| Payment Import | A new Pmt. Recon. Doc. No. Assignment setting has been added to the Bank Account Card page, allowing the document number assignment for Payment Reconciliation Journal lines to be configured per bank account. The available strategies are Default, Legal Sequence, Electronic Sequence, and Line-based Numbering. The chosen strategy is carried through to posted general ledger, bank ledger, VAT, and sub-ledger entries. Bank Account Reconciliation is not affected. The feature is managed through Continia Feature Management under code 69080 and must be enabled before the new fields become visible. | 76494 |
| Payment Import | The File Type field has been added to the bank transaction pages. | 77207 |
| Payment Import | The visibility of the Split Lines field is now controlled by the split rules setting on the Banking Import Setup page. When split rules are disabled, the field is hidden from the Bank Acc. Reconciliation, Bank Acc. Reconciliation Lines, and Payment Reconciliation Journal pages. | 74059 |
| Payment Import | When importing a CAMT file, the value date is now used as the statement date if the booking date is empty. | 77553 |
| Payment Import | When a bank statement line has multiple payment application proposals applied with different accounts, Line applies different accounts is now shown on the Bank Account Reconciliation and Payment Reconciliation Journal pages, aligning the behavior with other reconciliation views. | 76574 |
| Payment Import | A new Create Suggestion action has been added to the Vendor Ledger Entries page, providing a payment suggestion workflow through Continia Banking directly from ledger entries. Vendor ledger entries marked as On Hold are now excluded when payment journal lines are created. | 76604 |
| Payment Import | A new publisher event OnAfterFilterCustLedgerEntryAllowedToCreateDDReturnEntry has been added to codeunit 71554338 (CTS-PI Match Direct Debit). | 76930 |
| PSP | Adds a custom PSP external reference type, allowing rules based on any table and field. During reconciliation, these rules automatically resolve and populate the correct customer number on journal lines. | 76751 |
| PSP | A new option has been added to the Amount Format Rules in the CSV Port, allowing the type values that should always be imported to be selected, rather than only the values to skip. A new Type Value Selection page supports the configuration. When a positive selection is used, additional values that appear in newer CSV files are automatically excluded. | 76783 |
| PSP | The extended search functionality has been improved. A new Force Document Type option has been added to the PSP Agreement Reconciliation Setup page, providing more control over matching. Posting date matching now works more reliably with configured date tolerances, and amount matching falls back to LCY values when the original amounts do not match. | 77491 |
Bug fixes
| Functional Area | Description | ID |
|---|---|---|
| General Application | A permission error occurred when opening the Continia Payment page with entries, due to missing read access to a Document Capture table. The required permission is now included when accessed through approval management. | 73419 |
| General Application | A field type mismatch error occurred when Save as Template was used on customer, vendor, or employee cards, preventing templates from being saved. Templates can now be created from entity cards and correctly include all Continia Banking fields such as Bal. Account No., Payment Method Code, Cost Type, and external codes. | 72623 |
| General Application | Opening journals or setup pages could trigger unexpected approval permission errors. The ShowError parameter on the approval access check was incorrectly set to true, causing the check to throw an error instead of returning the result. The parameter has been corrected, and the return value from the module license check is now stored correctly. | 76520 |
| General Application | Opening the Bank Account Setup page failed because the access check for the Direct Communication module did not return its result correctly. The return value is now saved, and error handling on the approval access check has been improved. | 76508 |
| General Application | A permission error was shown when the Manual Setup action was invoked from a setup page by a user without permissions for Continia Banking. | 75640 |
| General Application | The PSP Agreement Setup page displayed notification banners for assisted setup and videos that were not related to PSP payment processing. The unrelated notifications have been removed. The assisted setup and video links remain available on other, more relevant pages. | 75697 |
| General Application | Notification banners and unrelated video links displayed on the PSP Agreement Setup page have been removed. | 75697 |
| General Application | Continia Banking PSP search rules and templates were missing in the demo app. Agreements such as the Klarna Agreement appeared empty, and all PSP templates were missing across payment service providers. The demo app referenced obsoleted PSP tables. It has been updated to use the current PSP tables, so PSP search rules and templates are now created correctly during demo data setup. | 76433 |
| General Application | A race condition could cause payment exports to fail when a background session hadn’t yet committed a Request ID Entry. A retry mechanism now polls for the record with limited attempts and exits gracefully if it’s still unavailable. Applies to all supported bank integrations. | 76963 |
| General Application | When an authentication was shared from one bank to a sibling bank in the same company, the operation silently did nothing. No confirmation was shown, the target bank's authentication fields were not copied, and the Active Bank System list and Bank Acc. Com. Setup on linked bank accounts were not configured. A confirmation dialog now appears, and on confirmation the target bank is populated correctly, the shared bank system is mirrored, and every linked bank account is configured for the shared bank system. | 77022 |
| General Application | Opening the Bank System Setup wizard could fail with a hard error when a bank account referenced an asynchronous status entry that no longer existed on Continia Online. When this occurred, the following error occurred: * Status entry id 'StatusEntryIdNotFound and skipped on subsequent polls. A telemetry event (0020, functional area Authentication) is emitted with EntryID, BankCode, and BankSystemCode dimensions. | 77407 |
| General Application | Closing a bank communication sub‑wizard (BANKSapi EBICS, BANKSapi, or Rabobank) with the close button previously discarded the setup. Both Finish and close now save the configuration. | 76678 |
| General Application | Setting default communication for a bank account could fail with a The page has been updated error when the bank system had account statement communication configured. The account statement uniqueness enforcement is now deferred to run after the cursor loop completes, avoiding the version conflict while preserving the business rule. | 76934 |
| General Application | The Bank Card page did not display bank-specific communication agreement groups (such as Signer ID/User No., Company ID, Certificate Holder, and Agreement No.) when a bank was configured with only manual communication. The visibility logic now includes bothdirect and manual communication types, so the agreement field groups are correctly shown. | 76781 |
| General Application | Structured remittance information was not generated during payment file creation because the MoreThanOneEntryFound parameter was always evaluated as false in the calling procedure. The var keyword has been added to the parameter on GetCustomerLedgerEntry and GetVendorLedgerEntry, so the value is now passed back to the caller. Structured remittance advice is now correctly included in the payment file when multiple ledger entries are found. | 77467 |
| Payment Export | Regulatory reporting codes were included in payment export files even when the Regulatory Reporting field was set to Inactive in the payment validation. This could cause payment files to be rejected. For example, in domestic SE-to-SE BG payments, the code was still included despite the inactive setting. The regulatory reporting code is now correctly excluded from the payment file when regulatory reporting is Inactive. | 76354 |
| Payment Export | Payments were created even when the vendor balance was 0 on the due date. A new Exclude Vendors without Due Balance option has been added to the Suggest Vendor Payments request page and to Payment Suggestion Templates. When enabled, vendors with a zero or positive overall balance are skipped. The default is off. | 74187 |
| Payment Export | The Direct Debit Mandate ID was automatically filled on sales invoices without setting the corresponding customer bank account. This has been corrected. | 74479 |
| Payment Export | Remittance advice text generated from a Remittance Information Pattern could exceed the payment method’s maximum line length, and line breaks could introduce leading spaces. Lines are now truncated and marked with ..., and leading spaces after line breaks are removed. | 76375 |
| Payment Export | The Update Posting Date function removed payment discount amounts from payment suggestion lines even when the new posting date still fell within the discount period. It is now possible to use a fixed Posting Date together with the Find Payment Discounts option, and the discount values are correctly recalculated and prefilled based on the specified posting date. | 76512 |
| Payment Export | Opening a payment reference template that contained a Modulus 7-3-1 Control No. placeholder crashed the CTS-CB Banking Template page. When this occurred, the following error occurred: * The value "." can't be evaluated into type Integer A non-numeric input guard has been added to the Modulus 7-3-1 calculation, so placeholder characters are now handled gracefully. The Banking Template page opens and displays correctly, and affected records can be deleted. | 76949 |
| Payment Export | When payment files were exported, the Name 2 field from the vendor or customer was not included in the generated banking export files. The Creditor Name 2 and Debtor Name 2 fields are now included in the inhouse file generation. | 77102 |
| Payment Export | Vendor ledger entries marked as On Hold were incorrectly included in the payment journal when the Create Payment action was used on the Vendor Ledger Entries page. The general journal creation handling now respects the On Hold status, and a new Create Suggestion action provides a Continia Banking-specific payment suggestion workflow directly from the ledger entries. | 76604 |
| Payment Export | When importing PSP payment files into the Cash Receipt Journal, lines with the same description but opposite signs were incorrectly grouped together. When the amounts summed to 0, the grouped line could not be used to automatically settle the corresponding sales invoice and credit invoice separately. The grouping logic now keeps positive and negative amount lines separate when their sum would equal 0. | 77496 |
| Payment Export | The Payment Allocation setup entry was displayed at the top level of the Manual Setup page instead of under Banking Export Setup. The entry has been moved to the correct location. | 75636 |
| Payment Export | Approval functionality failed due to a reference to an obsoleted Document Capture table that is no longer available. The record reference has been updated to point to the correct table, and permission checks in the Approval Management codeunit and the Applied Entries Part page have been enhanced. | 77842 |
| Payment Export | Improved validation rules by adding scope to prevent ambiguity between payment entry and remittance fields. | 76960 |
| Payment Export | Yapily payment exports for UK/GB bank accounts returned without an IBAN were not matched, so accounts silently missed their Yapily Account ID and subsequent statement retrieval failed. UK/GB bank accounts are now matched on Bank Branch No. and Bank Account No. (sort code and account number) when no IBAN is present. | 77117 |
| Payment Export | Improved captions and tooltips for payment suggestion filtering options. | 77173 |
| Payment Export | Added template-based completion for payment suggestions and resolved conflicting settings. | 77327 |
| Payment Export | Replaced legacy extensibility with structured buffer-based approach. | 77421 |
| Payment Import | The Substring transformation type could be selected on a transformation rule linked to a payment reference rule, even though the same functionality is available directly on the rule. A validation now prevents this selection and raises a field validation error if the Substring type is selected in this context. | 76027 |
| Payment Import | Fixed localization handling for Change Statement ID action. | 76573 |
| Payment Import | The Copy VAT Setup to Jnl. Line setting on the Payment Reconciliation Journal was not respected during posting. The setting is now applied correctly. | 76398 |
| Payment Import | Processing direct debit returns failed when a partner Banking extension was installed alongside the Continia Banking module. The customer ledger entry lookup now filters on the correct entry number, and the event binding of the CTS-PI DD Return Unapply Sub codeunit has been corrected so that it subscribes at the appropriate time. | 76400 |
| Payment Import | When unapplying invoice and payment entries through Process Pending Direct Debit Returns in the Payment Reconciliation Journal or Bank Account Reconciliation, the required VAT adjustment reversal entries were not created. VAT entries and general ledger entries are now generated consistently, regardless of whether the unapply is performed manually or through direct debit return processing. | 77392 |
| Payment Import | The Balance Last Statement field on the bank account reconciliation was incorrectly updated when bank account statements were imported. The field could be overridden with 0 when the imported file contained no balance data, and it was also modified when multiple statements were imported into the same reconciliation. The import process now preserves the Balance Last Statement value: balance fields are no longer overwritten when the file contains no balance data, and subsequent imports into the same reconciliation no longer modify the value. | 74378 |
| Payment Import | When importing bank statement files without balance information (for example, CAMT.053 files without balance nodes), the Balance Last Statement field on the Bank Acc. Reconciliation was incorrectly overridden with 0. The import logic now preserves existing balance values from the bank account when the file does not contain balance data. The fix applies to manual import, multiple statement import with aggregated periods, and automated import using job queues. | 75105 |
| Payment Import | The statement date was not shown when bank account statements were imported without balance data. The import logic now correctly preserves existing balance field values when the imported file does not contain balance data. | 77177 |
| Payment Import | Date and time values from imported bank files were stored with incorrect dates. ISO 8601 datetime strings without timezone indicators (for example, 2026-03-06T23:59:00) from CAMT.053 or CAMT.054 files were shifted by the session timezone offset, resulting in wrong booking dates. Datetime values from imported bank files are now parsed without applying the session timezone offset. | 76365 |
| Payment Import | Bank transactions imported from Yapily could appear as duplicates on the Bank Account Reconciliation page, because Yapily's API returns a rolling window of transactions that overlaps with previously imported data. The duplicate detection logic has been corrected: already-imported transactions are now identified and skipped, since the transaction hash used for duplicate detection is now available at the time the check is performed. | 76817 |
| Payment Import | The label for the transactionHash value in the allow to import check on Yapily has been corrected. | 76734 |
| Payment Import | Payment status import could match a disabled Bank Account Communication Setup when looking up the setup from the Payment Register, preventing the correct fallback lookup from being used. The GetBankAccountCommSetupFromRegister procedure now filters on Enabled = true, so only active communication setups are considered. | 76744 |
| Platform and Technology | A demo app setup limitation created only one authentication entry for multiple bank systems. The setup now iterates over all active bank systems and uses the provided bank system code directly. | 76361 |
| Platform and Technology | Continia Banking Demo app (28.0.2) issues with data, setup, and authentication have been fixed, with updated BC 28 compatibility and translations. | 77059 |
Continia Banking 2026 R1, hotfix 3
Pre-release date online: April 21, 2026
Release date online: April 21, 2026
Release date, on-premises: pending
Continia Banking version: 28.0.3
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | Fixed an issue where the PSP Agreement Setup page showed assisted setup and video notification banners that were not related to PSP payment processing. The unrelated notifications have been removed, while the assisted setup and video links remain available on more relevant pages. | 75697 |
| General Application | Fixed an issue where payment status import could match a disabled bank account communication setup, preventing the correct fallback lookup. This occurred when multiple communication setups existed for the same bank account and bank system code and one or more were disabled. Only active communication setups are now considered, ensuring the fallback lookup works as expected. | 76744 |
| General Application | Fixed an issue where the Bank Card page did not show bank-specific communication agreement groups for banks using manual communication, such as Nordea. The visibility logic only checked direct communication types, which hid required fields. The logic now supports both direct and manual communication types, so the required agreement fields are displayed correctly. | 76781 |
| General Application | Fixed an issue where setting default communication for a bank account could fail with a The page has been updated error when account statement communication was configured on the bank system. The account statement uniqueness check now runs after the cursor loop completes, avoiding the version conflict while preserving the business rule. | 76934 |
| General Application | Fixed a race condition where payment exports could fail when reading a request ID entry record that had not yet been committed by a background session. This could affect payment export, authentication confirmation, and status update flows across all supported bank integrations. | 76963 |
| General Application | Fixed an issue where sharing an authentication to a sibling bank in the same company did not trigger any action. No confirmation was shown, authentication fields were not copied, and related bank configurations were not applied. A confirmation dialog is now displayed, and upon confirmation the authentication details, active bank systems, and linked bank account setups are correctly copied to the target bank. | 77022 |
| Payment Import | Fixed an issue where date and time values from imported bank files were stored with incorrect dates. ISO 8601 datetime values without time zone indicators from CAMT.053 or CAMT.054 files were incorrectly adjusted by the session time zone offset, resulting in wrong booking dates. Datetime values are now parsed exactly as provided in the file, without applying a time zone offset. | 76365 |
| Payment Import | Fixed an issue where bank transactions imported from Yapily could appear as duplicates on the Bank Account Reconciliation page. Because the Yapily API returns overlapping transaction data, previously imported transactions could be re-imported. Duplicate detection has been corrected so existing transactions are identified and skipped during import. | 76817 |
| Payment Export | Added a new option, Exclude Vendors With no Amount due, on the Suggest Vendor Payments request page. When enabled, vendors whose overall balance shows they do not owe you money are skipped during payment suggestion. This prevents unnecessary payment lines from being created for vendors with a zero or positive balance. The option is also available in Payment Suggestion Templates. The default is off, so existing behavior is unchanged unless the option is enabled. | 74187 |
Continia Banking 2026 R1, hotfix 2
Pre-release date online: April 10, 2026
Release date online: April 10, 2026
Release date, on-premises: April 15, 2026
Continia Banking version: 28.0.2
Bug fixes
| Functional Area | Description | ID |
|---|---|---|
| General Application | Fixed a permission error on the Continia Payment page caused by missing read access to a Document Capture table when records were present. The required permission is now included. | 73419 |
| General Application | Fixed an issue where closing a bank communication sub-wizard with the close (X) button did not save the setup. Configuration is now saved correctly. | 76678 |
| Payment Export | Fixed an issue where regulatory reporting codes were included in payment exports even when Regulatory Reporting was set to Inactive. | 76354 |
| Payment Import | Fixed an issue where the system prevented the Substring transformation type from being selected when a payment reference rule already provides substring functionality. | 76027 |
Continia Banking 2026 R1, hotfix 1
Pre-release date online: April 7, 2026
Release date online: April 7, 2026
Release date, on-premises: April 15, 2026
Continia Banking version: 28.0.1
Bug fixes
| Functional Area | Description | ID |
|---|---|---|
| General Application | Fixed an issue where creating a template from a customer, vendor, or employee card failed due to a field type mismatch, preventing templates from being saved correctly. | 72623 |
| General Application | Fixed an issue where opening journals or setup pages showed unexpected approval permission errors due to incorrect approval access checks. | 76520 |
| General Application | Fixed an issue where opening the Bank Account Setup page failed because the access check for the Direct Communication module did not return its result correctly. | 76508 |
| Payment Import | Fixed an issue where the Copy VAT Setup to Jnl. Line setting on the Payment Reconciliation Journal was not respected during posting. | 76398 |
| Payment Import | Fixed an issue where processing direct debit returns failed when a partner banking extension was installed, due to an incorrect customer ledger entry lookup. | 76400 |
| Payment Export | Fixed an issue where remittance advice text generated from a pattern could exceed the configured line length, by inserting line breaks. The new line could cause leading spaces, which we now remove. | 76375 |
Continia Banking 2026 R1
Pre-release date online: March 20, 2026
Release date online: April 1, 2026
Release date, on-premises: April 15, 2026
Continia Banking version: 28.0.0
New functionality
| Functional area | Description | ID |
|---|---|---|
| General Application | Updated dependencies across all Continia Banking apps to support Business Central 28 and ensure compatibility. | 57076 |
| General Application | Updated translatable strings and captions across multiple modules to improve translation quality across supported languages. | 58769 |
| General Application | Updated translation files across all modules and supported languages to improve consistency and correctness. | 62163 |
| Payment Export | Introduced Payment Information Setup to define payment settings per account and payment method, reducing manual adjustments. | 70864 |
| Payment Export | Added a dedicated Payment Information Setup page with integration across customer, vendor, and employee records. | 70865 |
| Payment Export | Enabled flexible configuration of payment settings per account and payment method combinations. | 70866 |
| Payment Export | Added a total payment amount field to payment and direct debit journals for improved visibility. | 71796 |
| Payment Export | Added a total payment amount field to provide a correct overview of payment amounts without exporting data. | 72979 |
| Payment Export | Enabled distribution of payments across multiple payment suggestions to a selected bank account. | 73273 |
| Payment Export | Added default sender reference templates in Banking Export Setup. | 73512 |
| Payment Export | Improved configuration of payment exports with support for alternative payment address scenarios. | 74911 |
| Payment Import | Improved handling of expired payment discounts during payment import. | 67765 |
| Payment Import | Added support for ignoring account type in search rules during reconciliation matching. | 70470 |
| Payment Import | Added validation on bank account numbers to prevent unsupported special characters. | 74312 |
| Payment Import | Added an integration event after processing direct debit return entries. | 75036 |
| Payment Import | Added an integration event after matching bank account reconciliation. | 75050 |
| Payment Import | Improved manual import behavior when the job queue is on hold by prompting for user confirmation. | 75159 |
| Payment Import | Added external access to posted direct debit return entries and return reason code tables. | 75765 |
| Payment Import | Improved remittance information handling by introducing lifecycle tracking with a phase field. | 75853 |
| Payment Import | Refactored remittance calculation into smaller components to improve maintainability and extensibility. | 75855 |
| Payment Import | Improved remittance templates by separating single-instance and line-break functionality. | 75857 |
| Payment Import | Improved remittance compression to respect line breaks during text merging. | 75858 |
| Payment Import | Ensured automatic upgrade of template data to support new remittance template behavior. | 75859 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | Fixed an issue where importing bank systems overwrote user-defined batch settings. | 74349 |
| General Application | Fixed an issue where permission checks did not work correctly for approval admin permissions. | 73601 |
| General Application | Fixed an issue where SEB registration numbers were incorrectly limited to 10 characters in setup. | 75019 |
| General Application | Fixed an issue where Bizcuit imports could enter an infinite loop during pagination. | 76166 |
| Payment Export | Fixed an issue where payment distribution could fail with a JIT load error when moving lines. | 70422 |
| Payment Export | Fixed an issue where CtgyPurpCode was incorrectly used for multiple transaction types. | 72055 |
| Payment Export | Fixed an issue where remittance text could be truncated instead of continuing on a new line. | 75288 |
| Payment Export | Fixed an issue where changing vendor or customer did not update associated bank accounts. | 75357 |
| Payment Export | Fixed an issue where exported payment journal lines could still be modified. | 75549 |
| Payment Export | Fixed an issue where empty bank account codes caused journal line deletion failures. | 75568 |
| Payment Export | Fixed an issue where Direct Debit validation used incorrect validation rules. | 75717 |
| Payment Export | Fixed an issue where unapplied entries were not removed from exported payment tracking. | 75888 |
| Payment Export | Fixed an issue where only direct debit journals were visible in security setup. | 75891 |
| Payment Export | Fixed an issue where payment discounts were not correctly updated in summarized suggestions. | 75902 |
| Payment Export | Fixed issues in remittance rebuild functionality affecting multiple journal lines and cancellation behavior. | 75906 |
| Payment Export | Fixed an issue where remittance templates were ignored during rebuild when payment information setup existed. | 75907 |
| Payment Export | Fixed an issue where discount values were not correctly calculated during remittance rebuild. | 76168 |
| Payment Import | Fixed an issue where WorkDate was incorrectly used when importing bank statements. | 73775 |
| Payment Import | Fixed an issue where empty bank transactions were imported unnecessarily. | 73970 |
| Payment Import | Fixed an issue where transaction date handling caused import failures. | 74718 |
| Payment Import | Fixed an issue where payment import actions failed on empty reconciliation pages. | 75021 |
| Payment Import | Fixed an issue where job queue import setup caused page update errors. | 75039 |