Detailed changelog for Continia Banking 2025 R2
This article lists all new updates, features, service packs, and hotfixes for Continia Banking 2025 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 2025 R2 supports the following version of Microsoft Dynamics 365 Business Central: Business Central 2025 R2 (v27).
Continia Banking 2025 R2, Service Pack 7, hotfix 1
Release date online: May 18, 2026
Release date, on-premises: pending
Continia Banking version: 27.7.1
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | Improved AccessPay status import to avoid duplicate processing. | 78011 |
| General Application | Prevented re-running DNB setup for already configured accounts. | 78041 |
| General Application | Added full Yapily response to the File Archive for easier troubleshooting. | 78093 |
| General Application | Fixed lingering verification entries after reverting field changes. | 78116 |
| General Application | Automatically sets AccessPay transaction ID format during setup. | 78148 |
| General Application | Restored missing communication setup rows when resetting defaults. | 78206 |
| General Application | Fixed DNB authentication validation not using correct implementation. | 78207 |
| PSP | Fixed PSP search rules using Additional Description. | 78128 |
| PSP | Fixed upgrade failure caused by unsupported CSV amount formats. | 78193 |
| Payment Export | Fixed posting error for summarized payments with partial applications. | 77744 |
| Payment Export | Fixed posting error with summarized payments and credit memos. | 78190 |
| Payment Import | Fixed matching issues caused by automatic uppercasing of payment IDs. | 76740 |
| Payment Import | Fixed import failure when values contained the % character. | 76903 |
| Payment Import | Fixed inconsistent rule clearing when changing account fields. | 77455 |
| Payment Import | Fixed import failure caused by missing value dates in Yapily data. | 78200 |
Continia Banking 2025 R2, Service Pack 7
Release date online: May 8, 2026
Release date, on-premises: pending
Continia Banking version: 27.7.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 2025 R2, Service Pack 6, hotfix 3
Release date online: April 21, 2026
Release date, on-premises: April 22, 2026
Continia Banking version: 27.6.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 2025 R2, Service Pack 6, hotfix 2
Release date online: April 10, 2026
Release date, on-premises: April 22, 2026
Continia Banking version: 27.6.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 | Removed a redundant RefreshConnection call during Rabobank import to reduce overhead and avoid unnecessary database commits. | 76544 |
| 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 2025 R2, Service Pack 6, hotfix 1
Release date online: April 10, 2026
Release date, on-premises: April 22, 2026
Continia Banking version: 27.6.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, causing incorrect line breaks and leading spaces. | 76375 |
Continia Banking 2025 R2, Service Pack 6
Release date online: March 16, 2026
Release date, on-premises: pending
Continia Banking version: 27.6.0
New functionality
| Functional Area | Description | ID |
|---|---|---|
| General Application | Refactored HandleRequestEntryResponseArray to use foreach for JSON array iteration in all bank import codeunits. Removed unused loop counters and simplified redundant blocks. No behavioral change; improves code readability and consistency. | 59064 |
| General Application | Fixed Camt 054 import blocking when Status Request Header contained In Progress entries. Improved stale entry detection with type-specific thresholds (1 hour for authentication, 3 hours for imports/status). Stale entries are now marked as Failed, preventing indefinite polling. | 71818 |
| General Application | Added action to apply partial payments in payment import. See The Payment Application Review page. | 74791 |
| General Application | Separated PSD2 and EBICS URL routing logic in BANKSapi integration. Added FileType parameter to ICommunicationTypeSpecificUrlValue interface. EBICS-specific routing now handled by dedicated codeunit. No end-user impact; internal refactoring for clarity. | 74974 |
| General Application | Improved BANKSapi Account Statement import to handle JSON array responses. Each entry in Base64-encoded JSON arrays is now decoded and imported individually, ensuring complete data capture. See Onboarding through BANKSapi. | 74975 |
| General Application | Removed unused local TryGetStatusDefinition procedure from Payment Status Management. Code cleanup with no behavioral impact. | 74976 |
| General Application | Restructured KYB step in Bank Account Setup wizard for Yapily connections. Operating Address is now primary and required; Registered Address is optional. Simplifies setup for most businesses. See Onboarding through Yapily. | 74983 |
| General Application | Added EDIFACT file type (ordinal 30) to File Type enum. Enables processing of EDIFACT-formatted files in Continia Online request headers, alongside CAMT053, MT940, PAIN001, etc. | 74985 |
| General Application | Added validation for GZip decompression during bank communication imports. Responses not in Completed state are routed to error handling, preventing decompression errors for pending/failed async status responses. | 75008 |
| General Application | Added Generate Support Case Info action to Troubleshooting page. Guides users to select a scenario, collect diagnostic data, and export as ZIP. Supports Conversion Failure and Bank Agreement Not Activated scenarios. | 75192 |
| General Application | Fixed orphaned records in Multi Bank Account Assisted Setup wizard. Database records are now created only after successful bank onboarding, ensuring clean state if setup fails or is aborted. | 75213 |
| General Application | Fixed RecordMandateUsage procedure to clear Mandate Id filter before early exit. Ensures caller receives unfiltered payment entry record set, regardless of mandate usage. | 75368 |
| General Application | Added Bank Account Communication Setup data to support case export. Includes system type, transaction type, transfer, enabled status, default, and file type. Exported as JSON for further analysis. | 75409 |
| General Application | Removed duplicate OAuth refresh token call in Bizcuit bank data import. Token is now refreshed once per import, improving reliability and reducing unnecessary API requests. | 75503 |
| General Application | Changed GZip decompression handling for Danske Bank to use EOS (End of Stream) read instead of ReadText. Ensures full content of EDIFACT-formatted files is read correctly after decompression. | 75515 |
| General Application | Fixed orphaned file export queue entries when canceling Support Case Summary dialog. Queue is now cleared on cancel, preventing stale temporary export entries. | 75550 |
| General Application | Fixed conflict detection for Account Statement transaction type in Bank Account Setup wizard. Conflicts are now only checked if the bank system supports account statements, preventing false warnings. | 75713 |
| General Application | Fixed orphaned Request ID Entry records in Yapily payment export. Records are now marked as Failed and deleted if authorization is canceled, ensuring immediate cleanup. | 75826 |
| General Application | Improved AccessPay export response handling. Raw responses that cannot be decoded as JSON arrays are now archived as Payment Error for diagnostics, and processing stops early. Ensures traceability for failed or unexpected responses. | 75885 |
| General Application | Updated AccessPay Assist Setup wizard instructions. Clarifies that AccessPay onboarding may take up to 2 days before the bank is ready in Business Central. See Onboarding through AccessPay. | 75916 |
| General Application | Fix Nordea import to use per-entry metadata for uncollected request entries. | 75018 |
| General Application | Simplified Yapily setup for HSBC and Allied Irish Bank by removing Connect Profile ID requirement. Uses generic Yapily setup codeunit; bank-specific codeunits obsoleted. | 75978 |
| General Application | Improved AccessPay transaction import handling. Now uses API-based import dictionary, allowing multiple payment register entries to map to the same bank account. Previously, only the first entry per account was captured. | 75981 |
| General Application | Reorganized Troubleshooting page actions into logical groups: Logs, Files, Support, Setup & Maintenance, and Advanced. Promoted actions grouped for better discoverability. | 75986 |
| General Application | Added Manual Payment field to Bank System Payment Method table. Conflict detection now excludes manual payment methods, preventing false-positive alerts during bank system setup. | 76013 |
| General Application | Automated reconciliation matching in AccessPay setup wizard. Configures CTS-CB Date Amount Matching and Tolerance Days for selected bank accounts, eliminating manual post-setup steps. | 76142 |
| General Application | Added bulk actions to Bank Acc. Com. Setup page: All Manual, All Direct, and Set Default Communication. Enables switching transfer types for all records at once, reducing manual effort. | 76252 |
| General Application | Added exclusivity rule for Account Statement communication records. Enabling a new record automatically disables others for the same bank account, preventing ambiguous configurations. | 76253 |
| General Application | Added OnDelete trigger to Bank System table to clean up Bank System Active Map entries when a bank system is deleted. Prevents orphaned records and incorrect visibility of setup actions. | 76254 |
| General Application | Added 23 test procedures for bulk communication setup operations. Covers EnableByTransferType, SetDefaultCommunication, exclusivity, and multi-system prompts. Improves regression safety. | 76255 |
| General Application | Improved error handling for authentication cleanup. DeleteAuthenticationEntry now returns success status, and Remove Connection action shows descriptive errors if bank system is not found. | 76256 |
| General Application | Added ARUCS file type to File Type enum. Enables selection of ARUCS format for bank integrations, supporting ARUCS-formatted files without custom workarounds. | 76270 |
| General Application | Fixed bank system code resolution for payment status import. Now sources code directly from Payment Register record, ensuring correct bank system is used for accounts with multiple configurations. | 76362 |
| General Application | Introduced an enumeration that defines Account, BulkPayment, and SinglePayment token types for Yapily authorization. This improves token management and ensures the correct Yapily API endpoints are used during payment batch authorization. | 73934 |
| General Application | Introduced an interface that supports bank‑specific rules for grouping payments into batches prior to export. The interface standardizes batch creation and user‑interaction requirements across different bank strategy implementations. | 73936 |
| General Application | Defined an interface for communication types that require user interaction (SCA) during the export flow. Supports two‑phase Yapily‑style authorization by separating PreparePayment and SubmitPayment logic. | 73938 |
| General Application | Introduced a table for storing authorization data returned from PreparePayment, such as token type, expiry, and batch state. The table is read during SubmitPayment to continue the Yapily authorization process. | 73935 |
| General Application | Implements the Yapily SubmitPayment method that validates token freshness, retrieves the stored payload, exchanges the consent for an access token, and submits the payment. Updates journal line status based on the Yapily response and marks the batch as submitted. | 73942 |
| General Application | Updates the export orchestrator to detect whether a communication provider supports interactive export and route the flow accordingly. Interactive providers use the PreparePayment path, while non‑interactive providers continue with the standard SendPayment flow. | 73945 |
| General Application | Extends the BankExportFactory to return the correct batch‑strategy implementation based on the communication type configuration. Resolves the Yapily strategy when applicable, and falls back to the default strategy otherwise. | 73943 |
| General Application | Creates a page that lists payment batches pending authorization, allowing users to authorize or cancel each batch. Displays batch details, expiry status, and refreshes automatically while tracking prepared batches. | 73944 |
| General Application | Implements callback handling that processes Yapily authorization responses, retrieves the matching batch, and triggers SubmitPayment. Validates token expiry, submits the payment, updates the batch status, and reports success or failure. | 73946 |
| General Application | Implements the Yapily PreparePayment method that converts journal lines to Yapily format, calls the PreparePayment API, and stores authorization data for the SCA flow. Returns the authorization URL and records token details with a five‑minute expiry. | 73941 |
| General Application | Creates a scheduled job that removes expired Payment Batch Auth records still in Prepared status and resets their linked journal lines. Helps clean up abandoned authorization sessions caused by browser closures or crashes. | 73948 |
| General Application | Adds integration tests for the complete Yapily Prepare‑Authorize‑Submit flow using test doubles for the Yapily API. Verifies journal status transitions, abandoned‑flow cleanup, expired‑token handling, and correct orchestration of interactive and non‑interactive exports. | 73951 |
| General Application | Implements cleanup logic on page close to reset journal line statuses and remove any Prepared Payment Batch Auth records left unsubmitted. Ensures abandoned authorization batches are cleared and the system returns to a consistent state. | 73947 |
| General Application | Adds support in the file conversion service to transform in‑house JSON into Yapily’s payment format for export flows. Includes a new Yapily file type and system‑type mapping used before PreparePayment sends data to the Yapily API. | 73952 |
| General Application | Adds unit tests to validate enums, interfaces, and default implementations introduced in the Yapily foundation layer. Ensures field behavior, strategy defaults, and interface contracts compile and function as expected. | 73949 |
| General Application | Implemented Yapily‑specific batching rules that group payments by currency, limit bulk batches to five payments, and isolate amounts above a configured threshold. This strategy is selected for Yapily communication types and requires user interaction. | 73939 |
| General Application | Provided a default batch‑strategy implementation that returns all input lines as a single batch for banks without special requirements. Used when no bank‑specific strategy is configured and no user interaction is required. | 73937 |
| Payment Export | Introduced functionality for Payment Information Setup. See Working with the Payment Information Setup. | 70866 |
| Payment Export (Yapily) | Improved error logging for the Yapily Prepare and Export flow. Errors are now clearly displayed, and a missing interface implementation was added to the communication type enum. | 75435 |
| Payment Import | Added object ID range to Banking Import application for future development. Internal change; no impact on existing functionality. | 76156 |
| Payment Import | Added integration event OnAfterMatchingBankAccReconciliation to codeunit 71554177 (CTS‑PI Match Reconciliation). | 75050 |
| Payment Import | Improved handling of expired payment discounts in payment import. | 67765 |
| Payment Import | Enhancements to discount handling when using payment discounts and discount tolerance. See The Payment Application Review page. | 57675 |
| Payment Import | Added specification for payment discount handling. See The Payment Application Review page. | 72371 |
| Payment Import | Validation now warns you when the No. field on the Bank Account Card contains restricted characters that may affect banking functions in the Payment Reconciliation Journal. | 74312 |
| Payment Import | Added integration event OnAfterProcessDDReturnEntry to codeunit 71554339 (CTS‑PI Process DD Return). | 75036 |
Bug fixes
| Functional Area | Description | ID |
|---|---|---|
| General Application | Corrected Yapily payment export issues with incorrect JSON keys and hardcoded File Type parameter. JSON keys are now accurate, and the File Type parameter is dynamic. | 75812 |
| General Application | Fixed payment status import failures due to missing bank system tracking. The bank system code is now stored on the Payment Register and used to resolve the correct communication type during status imports. | 75813 |
| General Application | Resolved Yapily payment export failures caused by JSON mutation, improper error handling, and incorrect token extraction. JSON is no longer mutated before status updates, and errors now trigger proper rollback. | 75811 |
| Payment Export | Updated the action caption from Payment Info. Setup to Payment Information Setup for clarity and consistency across customer, vendor, and employee ards/Lists. | 75972 |
| Payment Export | Fixed issue where the Exported to Payment File flag was not reverted on canceled interactive exports, causing entries to remain marked as exported. Rollback logic now resets the flag and payment status. | 76118 |
| Payment Import | Fixed issue where refreshed authentication tokens were not committed before API calls, risking token loss if the API failed. The RefreshConnection method now returns a Boolean to ensure tokens are committed before proceeding. | 74714 |
Continia Banking 2025 R2, Service Pack 5, hotfix 4
Release date online: March 16, 2026
Release date, on-premises: March 17, 2026
Continia Banking version: 27.5.4
Bug fixes
| Functional Area | Description | ID |
|---|---|---|
| General Application | Scanning for unverified bank accounts is now significantly faster, especially in environments with many vendors, customers, or employees. | 75520 |
Continia Banking 2025 R2, Service Pack 5, hotfix 3
Release date online: March 13, 2026
Release date, on-premises: pending
Continia Banking version: 27.5.3
Bug fixes
| Functional Area | Description | ID |
|---|---|---|
| Payment Export | Fixed an issue where the Pay-to Vendor Bank Account Code was not updated when changing the vendor on a purchase invoice. The field kept the previous vendor’s bank account. The same issue occurred on sales invoices, where changing the Bill-to Customer No. did not refresh the customer bank account. This happened on the Purchase Invoice page when changing the Pay-to Vendor No., and on the Sales Invoice page when changing the Bill-to Customer No. With Purchase Invoice Validation enabled, an error could appear during posting: Pay-to Vendor Bank Account No. does not exist. The bank account fields are now correctly updated when the vendor or customer is changed. On sales invoices, changing the Bill-to Customer No. now also validates the Bal. Account No., and removes any existing external codes from the document. | 75357 |
| Payment Export | Fixed an issue in the export upgrade where creditor bank accounts could be duplicated because record ID‑based deduplication was not working correctly. | 75511 |
Continia Banking 2025 R2, Service Pack 5, hotfix 2
Release date online: March 11, 2026
Release date, on-premises: pending
Continia Banking version: 27.5.2
Bug fixes
| Functional Area | Description | ID |
|---|---|---|
| Payment Export | Fixed an issue where the CtgyPurpCode field was incorrectly used for both transaction and payment initiation at the same time. | 72055 |
| Payment Export | Fixed a potential error message when manually creating payment journal lines: Bank Account does not exist. This issue is specific to the Danish localization when a card type with a payment method code (e.g., Payment Method Code 71) is used. | 74625 |
| General Application | Fixed an issue where templates lost their connection to previously selected fields after updating from version 27.4 to 27.5. | 75048 |
| Payment Export | Fixed incorrect summarization of payments for multiple external codes. If different external codes were related to separate entries, payments were not summarized correctly. Instead of grouping them, single lines were created. | 75147 |
| General Application | Fixed an issue where the update from version 27.5.0.357745 to 27.5.1.362786 failed for Continia Banking (DK). | 75202 |
| Payment Export | Fixed validation engine inconsistency for field validation in the direct debit journal when using the manual payment method. | 75206 |
Continia Banking 2025 R2, Service Pack 5, hotfix 1
Release date online: March 3, 2026
Release date, on-premises: March 6
Continia Banking version: 27.5.1
Bug fixes
| Functional Area | Description | ID |
|---|---|---|
| General Application | The SEB bank assisted setup previously rejected registration numbers that were not exactly 10 characters, blocking some customers from completing the Bank Account Setup wizard. This fixed-length validation has been removed. The VAT No. field now accepts numeric values of any length. See Onboarding SEB. | 75019 |
| Payment Export | Updated the payment journal to correctly support changing the balancing account. | 74437 |
| Payment Import | Fixed an issue where the system used the Work Date to filter bank transactions during bank statement import when the statement date was blank on the Bank Account Reconciliation or Payment Reconciliation Journal. | 73775 |
| Payment Import | Fixed an issue where empty bank transactions were imported into Bank Account Reconciliation when only balance information was included in the header. Empty transactions are no longer imported. | 73970 |
| Payment Import | Fixed an issue where bank statement transactions were not imported and the error Nothing to import appeared even when transactions were available. This occurred when the bank transaction date was missing. The system now uses the statement To Date if the transaction date is blank. | 74718 |
| Payment Import | Fixed an issue where invoking the import payments action on an empty Payment Reconciliation Journal page caused the error The Bank Acc. Reconciliation does not exist. The action now works as expected. | 75021 |
| Payment Import | Fixed an issue where enabling the Import with Job Queue field on the Reconciliation Import Setup page caused the error Could not update the page. | 75039 |
Continia Banking 2025 R2, Service Pack 5
Release date online: February 25, 2026
Release date, on-premises: February 27, 2026
Continia Banking version: 27.5.0
| Functional Area | Description | ID |
|---|---|---|
| CSV Import | Improved amount formatting. See Setting up CSV ports using the wizard. | 73517 |
| CSV Import | You can now edit an existing CSV Port in the CSV Port Wizard. | 73525 |
| CSV Import | You can now import file formats other than UTF-8. See Setting up CSV ports using the wizard. | 73526 |
| General Application | Added new fields to support Yapily Payment Export. | 73852 |
| General Application | Implemented the SendDirectDebit procedure in the Danske Bank export module. You can now send PAIN.008 direct debit files through Continia Online using the same workflow as payment exports, including authentication, file compression, status tracking, and token refresh handling. | 74394 |
| Payment Export | Introduced a global character mapping table in Banking to handle special characters. The action is available for Bank Systems and Bank System payment methods. Standard ISO-related entries are created during setup. SEPA-allowed characters are included by default. Added validation for character mapping. See Special character mapping. | 70604 |
| Payment Export | The Exported to File field is now updated by Banking Export. When a file is created or reaches a higher status, the field is set on related entries and journals. If a line is voided, the field is cleared. | 73794 |
| Payment Export | Improved bank account verification performance. | 74128 |
| Payment Export | Made the Remittance Advice Mail area public so partners can extend the tables. Added new publishers to populate the information. | 74305 |
| Payment Export | Added a new publisher to populate Suggestion Line information. | 74447 |
| Payment Import | The OCR reference in the ClrSysRef tag is now imported, enabling proper reconciliation of OCR payments for Handelsbanken (SE) statements. | 72123 |
| Payment Import | Added an action on the Bank Account Reconciliation and Payment Reconciliation Journal pages to force removal of a match on a bank account ledger entry. The action is available under Show more actions. Select Actions > Matching > Other > Force Remove Match. | 72465 |
| Payment Import | Optimized procedures to improve overall performance and responsiveness during bank account reconciliation. | 72954 |
| Payment Import | Added integration events that allow partners to restrict the visible ledger entries on the Ledger Entries page for manual application. | 73363 |
| Payment Import | Removed the time portion from the Bank Transaction Date field on the Bank Transaction Card page. | 73776 |
| Payment Import | Enabled public access to the search rule table and its procedures. | 73862 |
| Payment Import | It is now possible to assign a split rule by Return Reason Code. See Applying split rules automatically. | 74266 |
| Payment Import | Added shortcuts to Apply Entries on the Bank Account Reconciliation and Payment Reconciliation Journal pages. Added shortcuts on the Apply Ledger Entries page for apply and unapply actions. | 74379 |
| Payment Import | Enabled external access for enum Transaction Type (ID 71553615). | 74413 |
| Payment Import | Made table CTS-PI Bank Recon. Line Detail externally accessible. | 74799 |
| Payment Import | Added a publisher in codeunit 71554259 CTS-PI ReconManual Jnl Line. | 74800 |
Bug fixes
| Functional Area | Description | ID |
|---|---|---|
| General Application | Corrected the Handelsbanken onboarding email sent during SFTP certificate setup. Removed unsupported CAMT.052.001.02 from the file format list and added a link to the Continia documentation for Handelsbanken file specifications. | 74810 |
| Payment Export | Fixed an issue where remittance sending during posting could not run in the same session, causing consistency errors in the standard sending process. | 73473 |
| Payment Export | Fixed an issue where summarization was incorrect when multiple payment dates used the same external code. | 74183 |
| Payment Export | Improved performance when deleting direct debit journal lines. | 74699 |
| Payment Import | Fixed an error when importing bank account statements: "Cannot rename Bank Account Reconciliation." | 73783 |
| Payment Import | Fixed an issue that occurred when importing statement files during bank reconciliation. | 73970 |
| Payment Import | Fixed an issue where Import Setup Data crashed if no table was specified in the table filter. | 74392 |
| Payment Import | Fixed an error when importing bank account statements with Bizcuit: "The changes to the Bank Account record cannot be saved because some information on the page is not up to date. Close the page, reopen it, and try again." | 74632 |
Continia Banking 2025 R2, Service Pack 4
Release date online: February 6, 2026
Release date, on-premises: February 12, 2026
Continia Banking version: 27.4.0
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| General Application | Renamed Continia Banking (GB) to Continia Banking (UK) with new app ID. | 66682 |
| Payment Export | Added several new publishers that allow partners to create data within the payment suggestion header and line structure. | 73304 |
| Payment Export | Fixed an issue where remaining and discount amounts were displayed incorrectly on the manual application page due to the payment discount tolerance warning. | 70501 |
| Payment Export | Added the Print Payment List action to the Payment Suggestions page. The action is hidden by default but can be enabled by customers. Changed the access level of the Payment Suggestion table to Public to align with the header and line tables. | 73306 |
| Payment Export | Marked additional variables as protected variables to allow partners to switch values in the Remittance Advice Report. | 73305 |
| Payment Export | Added new publishers that allow partners to extend the data available in remittance templates. | 72802 |
| Payment Export | A new external publisher has been added for partners to modify the fixed text See Remittance Advice. The publisher is called before inserting the remittance entry. Codeunit: CTS-PE Rem. Calc. Mgt. Pub. Publisher: OnAfterCalculateRemittanceTextForAdviceOnBeforeInsert | 73238 |
| Payment Export | Added public publishers to exchange name and address information during file creation: OnBeforeGetVendorInformationAsDebtor, OnBeforeGetVendorInformationAsCreditor, OnBeforeGetCustomerInformationAsDebtor, OnBeforeGetCustomerInformationAsCreditor, OnBeforeGetEmployeeInformationAsDebtor, OnBeforeGetEmployeeInformationAsCreditor. Added publishers for recipient bank accounts: OnBeforeSearchForRecipientBankAccount, OnAfterSearchForRecipientBankAccount. Added publisher to clean up data during posting: OnAfterUpdatePaymentSuggestionInformationOnBeforeNextLine. | 73301 |
| Payment Import | Leading and trailing spaces are now automatically removed from regular expressions used in payment reference rules. | 72054 |
| Payment Import | Added new extension points and external access to support processing of direct debit returns and reconciliation status handling. | 72800 |
| Payment Import | Added an option to transfer an overpayment difference to the payment instead of creating a new entry. | 68803 |
| Payment Import | Added support for using Banking Import transformation rules together with payment reference rules. This enables matching when references require content to be added or removed before matching. See Creating transformation rules. | 71518 |
| Payment Import | Made the CTS-PI IHandle Split By Type interface and related split rule tables accessible to allow partners to implement custom split amount calculations. | 72883 |
| Payment Import | Improved import app performance by optimizing Match Related Party procedures to reduce database calls. No changes were made to business logic. | 72955 |
| Payment Import | Added support for creating Z4 reporting entries for incoming payments from abroad. Reporting entries are generated on posting when the related party’s country differs from the company’s country and the reporting setup is configured. You can define a default Regulatory Reporting Code in Banking Import Setup. | 73021 |
| Payment Import | Added external access to the Bank Transaction Header, Line, Detail, and Charges tables. | 73300 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | Fixed an issue where validation triggered incorrectly due to Business Central region settings, regardless of the delimiter. | 71988 |
| General Application | Fixed an issue where a vendor bank account could be verified by the user who created it. | 72996 |
| General Application | Fixed issue where sharing bank authentication credentials across companies for Rabobank failed. The assisted bank account setup wizard now properly handles the sharing prompt, and the Client IP is copied when sharing manually via Related Companies. | 72082 |
| General Application | Issue where payment lines remained in Processing status when using Bizcuit connection has been resolved. | 73040 |
| General Application | Corrected Rabobank and Bizcuit authentication token refresh to prevent failures after 24 hours. Tokens are now refreshed at the appropriate intervals, maintaining continuous connectivity. | 72330 |
| General Application | The last statement date and time from Rabobank camt.053 responses is now saved correctly to the bank account’s CTS-CB Acc Stmt Last Update field. | 72464 |
| Payment Export | Field Remittance Advice After Entr. updated to allow remittance advice for a single entry. Enter 1 for 1 entry, 2 for 2 entries, etc. | 72989 |
| Payment Export | Removed restrictions preventing creation of new direct debit templates due to legacy checks in recurring payments functionality. | 73229 |
| Payment Export | Corrected permissions issue on vendor ledger entries that caused errors when posting receipts of goods. | 73279 |
| Payment Export | Corrected the filter in the rebuilding remittance advice function to include only the actual journal. | 73767 |
| Payment Export | Corrected an error that occurred when only one line in the payment journal was related to association or linking payments. | 73366 |
| Payment Export | Corrected a parameter issue in the MLPD calculation for Association payments that caused incorrect discount results. | 73369 |
| Payment Export | Fixed error in Customer/Vendor linking (Continia Finance) when running GetDimensionSetID. | 73452 |
| Payment Export | Fixed error when using advanced suggestion to create a manual payment for a vendor with an account number entered. | 73800 |
| Payment Export | Fixed issue where remittance sending could not be completed in the same session, preventing inconsistencies. | 73473 |
| Payment Export | Corrected issue where Z4 codes in banking export setup were not used for reporting entry creation. | 73861 |
| Payment Export | Refactored status update logic to correctly handle EndToEndId references with missing transaction status. Batch-level statuses are now correctly applied. | 73528 |
| Payment Export | Fixed SEPA Mandate sending to only process the selected mandate instead of all mandates in the background. | 73551 |
| Payment Export | Added summarized sender reference field for summarized payments. A second field was added to handle non-summarized payments. | 73584 |
| Payment Export | Corrected error when using Bill-to Another Customer sales orders with different bank account codes. | 73591 |
| Payment Export | Fixed an issue where blocked customers were incorrectly excluded from direct debit suggestions. | 73593 |
| Payment Export | Corrected bug where vendor balance account setup was not prioritized correctly over default account. | 73684 |
| Payment Export | Fixed incorrect status reset for payment suggestion entries after deleting journal lines. | 73719 |
| Payment Import | Fixed an issue where matching did not run automatically during Import and Apply Bank Transaction. Users no longer need to click Apply Automatically to complete matching. | 71380 |
| Payment Import | Fixed an issue where multiple proposals were created for already applied bank ledger entries when using Match on Posting Date and Amount with Apply to Oldest reconciliation. Now, previously applied entries are disregarded to prevent duplicate proposals. | 73765 |
Continia Banking 2025 R2, Service Pack 3
Release date online: January 15, 2026
Release date, on-premises: January 16, 2026
Continia Banking version: 27.3.0
New or changed functionality
| Functional area | Release notes | ID |
|---|---|---|
| CSV Import | Introduces a guided setup wizard (CSV Port Setup) that helps users easily configure CSV and Excel file import formats for PSP and payment reconciliation workflows. | 67781 |
| General Application | Verifies local fields in SE. | 70612 |
| General Application | Created a unified Job Queue Setup page. | 72919 |
| General Application | Removes the backoff policy from GetResponseFromOldAsyncStatusEntries to speed up processing of pending async requests during bank authentication and statement imports. | 71217 |
| Payment Export | Updates to batch posting functionality. | 70442 |
| Payment Export | Prevents single errors during double application checks when using imports. | 72487 |
| Payment Import | Adds support to enable or disable matching by posting date and amount on the bank account. | 72572 |
| Payment Import | Checks page trigger performance for the import application. | 72956 |
| Payment Method | Adds the ability to copy payment methods and introduces a new payment method code: "Collection" / "Abbucher". | 63694 70611 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Payment Import | Fixed the default KID Payment Reference Validation Pattern, correcting it from 11 digits to 10. | 70922 |
| Payment Import | Fixed an error "Applied Amount must be equal to 0" when using the Suggest Lines action in Bank Account Reconciliation. | 71978 |
| Payment Export | Corrected FIK OCR behavior with Applies-to ID (payments created from the vendor ledger entries list). | 72056 |
| Payment Export | Fixed Remaining Amount calculation in Advanced Mode for "include all entries". | 72243 |
| Payment Export | Fixed potential bank account verification error that caused a client crash ("Index out of bounds"). | 72247 |
| General Application | Customer Bank Account IBANs with blanks are now recognized. | 72325 |
| General Application | SequenceType is correctly added to inhouse entries if set to Inactive. | 72329 |
| Payment Export | Excluding credit memos when summarizing payments now works correctly. | 72467 |
| Payment Export | Notification field showing the paid amount is now available in the suggestion setup. | 72473 |
| Payment Export | Fixed zero invoice error. | 72525 |
| Payment Export | Banking Export Setup no longer incorrectly references the Security Module as Approval. | 72553 |
| Payment Export | Creditor Scheme Type now correctly handles missing values. | 72616 |
| General Application | Fixed issue preventing users from changing the Azure Blob Storage container after initial setup. Added a "Clear Storage Account Setup" action to reset storage configuration. | 72633 |
| Payment Export | Employee Remittance Advice issue resolved. | 72845 |
| Payment Import | Corrected sum posting feature in the payment reconciliation journal. | 72864 |
| Payment Export | Fixed application of entries from the Payment Journal. Summarized lines are now correctly applied, preventing unintended open entries. | 72898 |
| Payment Export | Fixed validation error for external payment codes. | 72904 |
| Payment Export | Fixed "Out of memory" error when finding a valid date for processing payments, e.g., when registering a Purchase Document. | 72906 |
| Payment Export | Cleared uncleared fields in the Payment Suggestion Template. | 72914 |
| Payment Export | Fixed issue resending Remittance Advice in the Remittance Advice Outbox. | 72936 |
| Payment Export | Sales Invoice Mandate-ID field now fills automatically. | 72951 |
| Payment Export | Mandate-ID in general journal lines now fills automatically. | 72952 |
| Payment Export | Removed check for non-existing direct debit mandates when voiding a direct debit journal line without an assigned mandate. | 72977 |
| Payment Export | Z4-Reporting: Direct Debit reporting entries no longer default to "No Reporting needed" during export. | 73025 |
| Payment Export | Split payments from allocation now use unique End-to-End IDs, resolving multiple related issues. | 73076 |
| Payment Export | Recalculates Amount to Pay if Discount amount or percentage is manually reduced. | 73093 |
Continia Banking 2025 R2, Service Pack 2
Release date online: December 15, 2025
Continia Banking version: 27.2.0
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| General Application | Added instructions for debtor and creditor at the group level. | 71328 |
| General Application | Added additional options for the creation of End-to-End ID and Payment Information ID, with multiple length variants (18, 15, and 16 characters). | 71248 71954 |
| General Application | Enabled GZip compression for Danske Bank communication. Compression improves performance and reduces bandwidth usage for payment operations. It applies automatically to all requests and responses, including payment exports, bank statement imports, and payment status inquiries. No configuration is required. | 72426 |
| Payment Export | Made the payment template extensible for partners. | 72048 |
| Payment Export | Added publisher and change options for customizing remittance information. | 68797 |
| Payment Export | You can now email mandates directly to customers. The required entry is created automatically during upgrade or activation to maintain correct report layouts. For more information, see Working with SEPA mandate reports and email delivery | 44522 |
| Payment Export | Excluded unverified bank accounts from payment suggestions. | 71514 |
| Payment Export | Remittance Advice: Added more information in the dataset and made layout changes. | 68114 |
| Payment Export | Enhanced the web client experience by implementing a workaround for a known Microsoft platform issue where a background dialog could be rendered behind the active page during suggestion processing, making the client appear unresponsive. | 71340 |
| Payment Import | Added a sum posting feature that consolidates multiple applications for the same account into one ledger entry on a single statement line. For more information, see Posting multiple applications as one sum entry | 68929 |
| Payment Import | Added support for the Bank Accounts account type in search rules. | 70022 |
| Payment Import | Added the Balance (LCY) field to the Match Details FactBoxes on the Payment Reconciliation Journal page and the Payment Application Review page. The field shows the total balance of open ledger entries. | 70590 |
| Payment Import | Added a new cue to role centers to show customer ledger entries put on hold after handling a direct debit return in reconciliation. | 70004 |
| Payment Import | Added support for using the first reconciliation line detail text in posting description templates. Added a new default template called DETAILTEXT. | 71819 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | Fixed error in TietoEvry import where asynchronously fetched files could get incorrect file types. | 71716 |
| General Application | Fixed error in Bizcuit import that caused an infinite loop. | 71670 |
| General Application | Updated DE Demo App to use the correct VAT Posting Group in split rules. Changed from NO VAT to OHNE MWST. | 71376 |
| General Application | Assisted setup for Payment Receivables now preserves the current payment method in the Payment Method (New) field when modifying a record, instead of deleting it. Additionally, synchronization of the Summarizing Payments field has been fixed. | 71388 |
| Payment Export | Fixed an issue where Find Discount could collect ledger entries without discount amounts based on discount due date instead of due date. This occurred only when multiple ledger entries were included in the suggestion filter. Ledger entries without discounts are now evaluated solely by due date. | 72419 |
| Payment Export | Fixed an issue where OCR file import in the cash receipt journal stopped processing the entire file if a single line caused an error (e.g. double payment). This behavior occurred when Continia Banking was active, preventing valid lines after the error from being imported. The import now continues processing remaining lines even if one line fails. | 72244 |
| Payment Export | Fixed issue where Z4 file creation used incorrect filtering. The filter now correctly applies Exported = false instead of Exported = true. | 71739 |
| Payment Export | Fixed an issue where entering a value in “New payment after number of Entries” in Banking Export Setup or on a customer/vendor card incorrectly created two payments instead of one. Now, payments correctly reflect the specified number of entries. | 72110 |
| Payment Export | Updated sender reference handling: if no template is defined, the system now uses the account’s alternative information first; if empty, it falls back to the account name. | 71873 |
| Payment Export | Fixed issues with credit memo handling when summarizing payments. Now correctly applies Ignore Credit Memo Date and supports summarizing credit memos with earlier due dates than invoice dates. | 68171 |
| Payment Export | Fixed issue where summarizing payments caused missing External Code information in Regulatory Reporting. | 71751 |
| Payment Export | Fixed filtering of external codes for NO and SE: the system now considers the sender country code, as regulatory reporting codes are linked to the sender, not the recipient. | 71046 |
| Payment Export | Fixed issue where deleting a suggested line also deleted the single payment bank account. | 71920 |
| Payment Export | Fixed an issue where mandates with status Closed could still be reused, potentially causing duplicate payment files and bank rejections. Now, closed mandates are properly blocked from further use. | 72049 |
| Payment Export | Fixed issue where Handelsbanken payment file exports could contain invalid characters in filenames due to incorrect character sanitization. | 72609 |
| Payment Export | Fixed default sender reference template behavior. Now checks alternative account information before using the account name. | 71873 |
| Payment Export | Fixed entry selection in suggestions when using the Always Apply Discount option. Selection now correctly ignores discount and due dates when this option is enabled. | 71370 |
| Payment Export | Fixed potential error in bank account verification that could cause a client crash with Index out of bounds. | 72247 |
| Payment Export | Previously, if an order had already been posted, changes to default dimensions were not reflected in the payment journal suggestions. This has been fixed: now, updates to default dimensions are applied correctly, even for posted order lines. | 72414 |
| Payment Export | Dimensions are now preserved when using a line for batch posting. | 72255 |
| Payment Export | Fixed assignment of mandate sequence type. | 72523 |
| Payment Export | In advanced mode, if a payment proposal was summarized but contained only a single payment line, the line was created correctly as a single line. However, during editing, it was incorrectly treated as a summarized line. This has been fixed so that single-line proposals are now correctly handled as single lines during editing as well. | 72205 |
| Payment Export | Previously, voiding payments in advanced mode did not correctly reset the end-to-end ID. This has been fixed so that the end-to-end ID is now properly reset in advanced mode. | 72197 |
| Payment Export | Changing dimensions in advanced mode now correctly updates the global dimensions. | 72210 |
| Payment Import | Fixed the default value of the Document Type field in search rules assigned to an account type other than G/L account or bank account. | 72377 |
| Payment Import | Added reconciliation lines with Difference status to journal line creation in Bank Account Reconciliation. | 71802 |
| Payment Import | Corrected the value of the Accept Pmt. Discount Tolerance field in the Payment Application Proposal after an entry is unapplied. | 70630 |
| Payment Import | Fixed the auto-application process when both payment tolerances and custom tolerances apply. | 68771 |
| Payment Import | Fixed issue where matching did not run automatically during Import and Apply Bank Transaction. Matching now runs without requiring manual action. | 71380 |
| Payment Import | Fixed issue where changing the statement amount on a Bank Account Reconciliation line did not update when matched to a Bank Account Ledger Entry. | 71052 |
| Payment Import | Fixed issue where the Show All button was not visible in certain situations on the Bank Account Reconciliation page. | 72267 |
| Payment Import | Fixed the default KID Payment Reference Validation Pattern. It now correctly validates 10-digit numbers instead of 11. | 70922 |
| Payment Import | Fixed error in Bank Account Reconciliation when Sum Posting per Day was enabled for the Payment Reconciliation Journal. | 71212 |
| Payment Import | Fixed error where currency code was not correctly assigned when creating journal lines in Bank Account Reconciliation. Also fixed posting errors when applying FCY entries with the same bank account. | 71874 |
Continia Banking 2025 R2, Service Pack 1, hotfix 2
Release date online: November 24, 2025
Continia Banking version: 27.1.2
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Payment Export | Due to incorrect filtering, the Z4 file creation did not work correctly. A filter for Exported = true was used instead of Exported = false. This has been corrected. | 71739 |
| Payment Export | When summarizing was used in the Payment Suggestion, the transfer of Regulatory Reporting codes did not work correctly. The created payment journal line was missing the External Code information. This has been corrected. | 71751 |
| Payment Export | If no sender reference template is defined for the suggestion, a default is used by the system, which uses the account name. The default behavior was adjusted: the system now checks the alternative information on the account. If the alternative name is available, it is used; otherwise, the normal account name is used. | 71873 |
| Payment Export | When creating payment journal lines from a suggestion using single payment bank accounts, deleting the suggested line also deleted the single payment bank account itself. This behavior was incorrect and has been fixed. | 71920 |
| Payment Import | An error occurred in Bank Account Reconciliation when the Sum Posting per Day setting was enabled for the Payment Reconciliation Journal. | 71212 |
| Payment Export | Fixed an issue where remittance advice documents in the outbox lost content when they were recreated after an update. | 71423 |
| General Application | Updated the DE Demo App to use the correct VAT Posting Group in split rules. Changed from NO VAT to OHNE MWST. | 71376 |
| General Application | Improved Assisted Setup for Payment Receivables to store the current payment method values in the payment method (new) field and not delete them after modification. Also fixed synchronization of the Summarizing Payments field. | 71388 |
Continia Banking 2025 R2, Service Pack 1, hotfix 1
Release date online: November 16, 2025
Continia Banking version: 27.1.1
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | Bizcuit: fixed an error in Bizcuit import that caused an infinite loop. | 71670 |
| General Application | Tietoevry: fixed an error in Tietoevry import where asynchronously fetched files could receive an incorrect file type. | 71716 |
| Payment Export | Fixed an issue where entry selection didn’t work correctly when using the Always Apply Discount option. | 71370 |
Continia Banking 2025 R2, Service Pack 1
Release date online: November 11, 2025
Continia Banking version: 27.1.0
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Payment Import | The Import and Apply Payments action in the Payment Reconciliation Journal is now shown by default on the page. | 68213 |
| Payment Import | Added support for matching G/L open entries by balance. | 69013 |
| Payment Import | The Document Type field is now hidden on the Payment Reference Rule Test page when document type matching is not enabled for the rule. | 70007 |
| Payment Export | The Finance module Multi-level Payment Discount is now prepared for integration with Banking. Discounts are checked in payment suggestions if the Finance module is activated. A Finance update is also required. | 65586 |
| Payment Import | Improved performance for manual application using the Apply Entries action on the Bank Acc. Reconciliation or Payment Reconciliation pages. Also improved performance for manual application using the Ledger Entries action on the Payment Application Review page. | 70824 |
| Payment Import | Added an action to the error message displayed when importing account statements, allowing users to clear the statement date. | 67819 |
| Payment Import | Reintroduced the standard Business Central codeunit Match Bank Rec. Lines and added new events for matching and removing matches from bank account ledger entries. | 67844 |
| Payment Import | Created a test to ensure payment entry fields are aligned with archive and ledger. | 70584 |
| Payment Import | Extended validation for payment date. | 71290 |
| General Application | AccessPay is now available in Feature Management. | 71326 |
| Payment Import | Added a check during file import that displays an error message if multiple bank accounts exist with the same combination of Bank Branch No., Bank Account No., and currency, or IBAN and currency. | 68405 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Payment Export | Fixed an issue where invoices with 100% VAT showed an amount of 0. The validation engine was blocking posting due to an incorrect amount check. | 69946 |
| Payment Export | The End-to-End ID is now included in the payment suggestion header (summarized payments) and lines (non-summarized payments). Visibility depends on the summarization setting. The field can also be used for Sender Reference templates if needed. | 70468 |
| Payment Export | Fixed an issue where the Remittance Advice printout was incorrect when the finance module association was used. Linked or associated accounts were not printed. | 70768 |
| Payment Export | Partial payments with discounts are now disallowed, as they could not be posted correctly. This feature will be reintroduced later in a different way. | 70851 |
| Payment Export | Changed the behavior of the posting job queue for exported payment journal lines. It is now created but not automatically activated after setup. | 70982 |
| Payment Export | Fixed an issue where standard linking between accounts was not working correctly. The linked account was always skipped if it had a higher balance. This condition now applies only when the linking payment is used in the suggestion. | 70989 |
| Payment Export | Fixed external code validation. When entering a code used for multiple countries, the selection page now allows users to confirm with OK. | 71043 |
| Payment Export | Fixed an issue where deleting an added value in the sender reference pattern incorrectly inserted “2%” into the pattern. The pattern now updates correctly when values are removed. | 70488 |
| Payment Export | The Payment Suggestion Templates tile is now always visible in the Role Center. | 71228 |
| Payment Export | Corrected validation error details for related fields. | 70253 |
| General Application | Rabobank: Only one bank account is authorized, but all were shown as ready. | 71040 |
| General Application | Fixed an error handling response from Continia Online when updating status. | 70952 |
| General Application | Bizcuit: Fixed an error when importing account statements from ABN AMRO. | 70997 |
| General Application | Bizcuit: Fixed an issue where payments remained in the Sent to bank status after approval. | 70999 |
| Payment Export | Fixed an issue where payment suggestions created payment lines in the default journal instead of the current journal. | 71039 |
| General Application | Added support for extended clearing of information related to direct communication with Rabobank, Bizcuit, and similar integrations. | 71061 |
Continia Banking 2025 R2, hotfix 4
Release date online: October 27, 2025
Continia Banking version: 27.0.4
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | Resolved activation failure caused by CB 25 upgrade applying a filter to a field with ObsoleteState = Removed. | 70888 |
| General Application | Fixed issue where Update JobQueue 71553647 failed with an empty ETag error when encountering bank accounts not connected to Continia Banking (i.e., missing Bankcode Mapping). This error prevented updates to other valid bank systems from completing successfully. | 70826 |
Continia Banking 2025 R2, hotfix 3
Release date online: October 24, 2025
Continia Banking version: 27.0.3
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| CSV Import | Added support for specific CSV formats with double delimiters when a space exists in a CSV value. | 70709 |
| Payment Export | Fixed an issue where balance ledger entries incorrectly received the End-to-End ID instead of the Payment Information ID during batch posting; now, balancing lines include only the Payment Information ID, as they aggregate multiple lines. | 70316 |
| Payment Export | Fixed an issue that prevented users from selecting external codes. | 70627 |
| Payment Export | When a journal contained multiple payment methods, batch posting was applied to all lines even if setup existed for only one method. This is fixed: only payment methods with batch posting configured are now included. | 70697 |
| Payment Import | Blocked bank accounts are now disregarded during file import. | 70312 |
| Payment Export | Fixed an issue where the Recipient Reference was overwritten on the payment journal line after selecting Apply Entries. The Recipient Reference now rebuilds correctly based on the template setup instead of using a fixed value. | 70377 |
| Payment Export | Fixed an issue where the Standard Batch Approval Send/Cancel actions weren’t shown in Banking Journals. They now appear if no Security module approval workflows are enabled. | 70633 |
| Payment Import | Fixed an issue where modifying the applied amount in the application proposal caused the system to delete the transferred difference line without restoring the original transaction amount on the parent line. | 67818 |
Continia Banking 2025 R2, hotfix 2
Release date online: October 8, 2025
Continia Banking version: 27.0.2
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | Resolved error occurring when exporting payments via Danske Bank direct communication. | 70384 |
Continia Banking 2025 R2, hotfix 1
Release date, online: October 7, 2025
Continia Banking version: 27.0.1
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Payment and Cash Receipts | Fixed an error where mandate usage was not registered correctly. | 70113 |
Continia Banking 2025 R2
Pre-release date, online: September 23, 2025
Release date online: October 1, 2025
Continia Banking version: 27.0.0
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| General Application | Enhanced the HTTP client interface with new utilities, updated related integrations, and improved logging for greater consistency and functionality. | 69164 |
| General Application | Added the possibility to add implementation for storage of Authentication Items used in direct integrations to banks. | 68936 |
| General Application | Updated Continia Hub – Learn Links. | 69853 |
| General Application | Added versioning to Feature Management. | 69481 |
| General Application | The following changes have been applied to the Continia Banking permission sets:
The renamed permission sets will be updated automatically during the upgrade. For more information about permission sets, see Continia Banking permissions. | 68673 |
| General Application | Added context-sensitive help links to several pages in Continia Banking. | 70003 |
| Payment Export | Postings can now be created in one sum using Posting Option BatchPosting via Payment Info ID. | 62770 |
| Payment Export | This version introduces explicit control over how payment discounts are detected and applied, including optional tolerance and date-based logic. Discounts are considered only when the Find Payment Discounts feature is enabled. When active, the application method can always apply the entry’s discount even if expired, or respect the tolerance date in calculations. An optional posting date can override the evaluation date, while leaving it empty preserves the previous logic. | 62364 |
| Payment Export | Added batch posting functionality to Payment Export. Includes new validations, setup options, posting number series notifications, and import setup validation for transaction reversals. | 66651 |
| Payment Export | Added a Pattern column to the Banking Templates list showing readable field references instead of placeholder tokens (for example, displays <"Customer"."Name"> instead of <%1>). The original Text Pattern column is hidden. | 69606 |
| Payment Export | Added option to fill End-to-End ID in detailed entries. | 68209 |
| Payment Export | Added Export Setup Check. | 66652 |
| Payment Export | Added Import Setup Check. | 66653 |
| Payment Export | Added option to fill End-to-End ID in VAT entries. | 68210 |
| Payment Export | Added Payment Posting Setup fields. | 66654 |
| Payment Export | Added Payment Distribution functionality. See Splitting payment suggestions across multiple bank accounts | 67025 |
| Payment Import | Added option to reopen a specific entry in Return Direct Debit. | 68211 |
| Payment Import | Added ability to view which Payment Reference Rule was used to create a Payment Application Proposal. | 68538 |
Bug fixes
| Functional area | Release notes | ID |
|---|---|---|
| General Application | Fixed missing permissions and resolved permission set code analysis warnings. | 69478 |
| General Application | CSC Telemetry now shows a deprecation warning. | 69479 |
| General Application | Fixed an issue where running Upgrade twice could result in templates being deleted. | 69899 69769 |
| Payment Export | Fixed multiple issues when manually editing Direct Debit journals after using Suggest Direct Debits in standard mode. Issues included incorrect mandate selection and errors when changing fields such as Recipient Bank Account, Direct Debit Mandate ID, Payment Method Code, and Balancing Account. | 69409 |
| Payment Export | Fixed an issue where payments were summarized even when an error occurred. | 68891 |
| Payment Export | Removed payment batch approval type. | 64335 |
| Payment Export | Purchase header not updated correctly when vendor has multiple bank accounts and different currencies. | 68853 |
| Payment Export | Fixed Payment Validation Error – navigation to Error fails. | 69477 |
| Payment Export | Fixed an issue in the Payment Journal where customers had to click Update Status multiple times to update all lines when statuses were split across multiple files. | 70241 |
| Payment Import | Deleting a child line clears Imported to Company in the related bank transaction line. This has now been fixed. | 69828 |
| Payment Import | Corrected Direct Debit Return Processing Type – Reverse. The reversed bank account ledger entry was set to an amount with wrong sign. | 69499 |
| Payment Import | Fixed an error when changing the type for return direct debit processing. | 70006 |
| Payment Import | Fixed an issue where the bank account reconciliation import job queue was not processing files automatically. | 70034 |