We are pleased to introduce the Summer 2026 release of Bank Standards App (BSA), bringing significant enhancements to configuration, payment routing, validation, SEPA processing, payment-file generation and CAMT.053 bank-statement imports.
This release focuses on making BSA easier to configure and manage while improving the reliability and transparency of payment processing. Importantly, backward-compatible defaults have been preserved, allowing existing customers to review and adopt the new functionality in a controlled way.
What’s New in Bank Standards App: Summer 2026 Release
A New Bank Standards App Configurator
One of the key enhancements in this release is the introduction of the BSA Configurator.
The new Lightning-based configuration experience provides administrators with a more structured and intuitive way to manage Bank Standards App settings. Configuration options are organised into dedicated sections covering bank payment files, country and address handling, file storage, bank-statement matching and advanced settings.
Field-level explanations provide guidance on defaults, fallbacks, effects and examples, while previews help administrators understand how payment references, direct-debit references and payment-file data will be generated.
New configuration records are also initialised with the defaults defined in the application’s metadata, providing a clearer starting point for setup.
Smarter Payment Routing
The Summer 2026 release introduces an optional Standards Based payment routing mode alongside the existing Legacy behaviour.
The default remains Legacy, ensuring that existing installations continue to operate as before. Customers can switch to Standards Based routing after reviewing their bank formats and configuration.
In Standards Based mode, routing is determined using the payment currency and beneficiary bank details. For example, an EUR payment to a valid IBAN at a bank within the SEPA area is routed as a SEPA payment, while non-EUR payments or payments to banks outside the SEPA area are routed as non-SEPA.
This approach reduces reliance on Account postal information when determining the appropriate payment route.
Stronger and More Flexible Validation
Payment-file validation has been enhanced with new configurable validation modes.
The default remains Legacy to avoid unexpectedly blocking existing customers. Additional validation modes can identify route-specific issues as warnings or prevent file generation where structural errors must be corrected.
Validation now includes more comprehensive checks for payment details, including payer and beneficiary information, account identifiers, BIC and clearing-system details, IBAN formats and route-specific requirements.
Support has also been enhanced for specific payment types, including SEPA, Swedish BankGiro and Swiss QR/SCOR references.
Where an issue is identified, validation messages provide clearer and more actionable information by identifying the affected payment and the relevant object and field requiring attention.
Improved SEPA Address Handling
A valid SEPA payment should not fail simply because address information is missing when the selected payment route does not require it.
Previously, valid EUR payments between SEPA IBAN accounts could be treated as incomplete when certain Account address fields were not populated. The Summer 2026 release addresses this by using the effective beneficiary bank details when determining the SEPA route.
Standard SEPA payment files no longer require or generate debtor or creditor postal-address elements where they are not required. As a result, missing Account or Owner Company address information will no longer prevent a valid SEPA payment from being processed.
Full structured addresses remain required for payment routes where they are required by the relevant bank-file format.
Improved Country and Bank-Detail Configuration
The release introduces enhanced country-code configuration using restricted ISO alpha-2 picklists for Account postal and beneficiary bank country information.
This provides a more consistent approach to country handling and avoids unreliable language-dependent conversions from country names.
The release also improves the documented precedence of bank details used during payment-file generation, including configured Payable Invoice overrides, selected Vendor Bank Accounts and existing Account bank fields.
Additional configuration options provide greater control over payment references and structured creditor references where supported by the selected payment format.
Clearer Payment-File Generation Feedback
Payment-file generation has also been improved to provide better visibility when something goes wrong.
Pre-generation validation feedback is now available on the Payments page, while generation and merge-stage failures are surfaced to users rather than failing silently.
The release also introduces safer handling of partial failures. If a generation batch reports errors, a partial payment file will no longer be merged, helping to prevent incomplete or unreliable output.
More Robust CAMT.053 Bank-Statement Imports
The Summer 2026 release also improves the handling of CAMT.053 bank statements where an IBAN is not available.
Where possible, the system will now use an alternative account number when constructing the bank-statement reference. This prevents incomplete references that could previously begin with a null value.
If neither an IBAN nor an alternative account number is available, the import is stopped and a clear error message is displayed.
This provides a more reliable and predictable import process while ensuring that incomplete bank-account information is identified clearly.
Continued Focus on Stability and Evolution
Some legacy and obsolete configuration options have been marked as deprecated in this release. These settings remain in the metadata where necessary for package compatibility but are hidden from the new BSA Configurator.
The release is also supported by updated documentation and expanded regression coverage across payment flows, including SEPA and non-SEPA routing, bank-detail overrides, BankGiro, Swiss payment references and payment-file generation behaviour.
Moving Forward
The Summer 2026 release of Bank Standards App represents an important step forward in improving configuration, payment routing, validation and bank-statement processing.
For existing customers, the preservation of backward-compatible defaults provides the opportunity to explore and adopt the new capabilities at an appropriate pace.
At ArtixNova, our focus remains on supporting, maintaining and evolving the solutions that our Certinia customers rely on.
Continuity. Security. Evolution.