New Features

Digital Delivery is now available for Unregistered Beneficiaries - Beneficiary Access, Sharing and Recovery (Digital SBIM, Digital BGIS)

Digital Delivery allows Konsole to automatically transmit a guarantee or a stand-by letter of credit to a beneficiary upon validation by the issuing bank — without any additional manual step from the applicant or the bank. Initially made available to on-platform beneficiaries, it has been extended to off-platform beneficiaries in this releae.

Beneficiary can access and perform selected post-issuance actions. A beneficiary who is not registered on Konsole receives the instrument by email and authenticates through a secure token carried by a second, separate email. Once authenticated, the beneficiary can consult the instrument, download its documents and act on the undertaking after issuance, rather than being limited to a read-only certificate.

Sharing from any endpoint. A share mechanism has been introduced. Beneficiary, Issuer and Applicant can each share an instrument from their own endpoint in read-only mode. Shared instruments are grouped for the recipient under a dedicated Shared with me view. Sharing creates no user account, no permission and no profile on the endpoint - the recipient continues to authenticate through the one-time code mechanism.

Recovery and change of designated user. The designated beneficiary contact can be changed after issuance. When the contact changes, the previous recipient is notified by email so that the loss of access is explained rather than discovered.

Document classification at issuance. Banks can now classify each document attached to a digital issuance as shared with the Applicant only, or with both the Applicant and the Beneficiary. Classification is available from the user interface and from the API. The default is Applicant and Beneficiary. Documents restricted to the Applicant are withheld from the beneficiary view of the instrument.

Fees are no longer visible to the beneficiary. Fee content is never copied into the SBEX/BGRE message received by the beneficiary, at any step of the flow, and the Fees tab is no longer displayed on digital-delivery beneficiary exports. The Charges tab remains visible, as settlement charges are legitimately the beneficiary's concern. The bank and applicant side is unchanged, and other type of deliveries are unaffected.

Document upload. Attaching a supporting document is mandatory at issuance only, and no longer at subsequent steps of a digital instrument's lifecycle.

Automated Renewal of Standby Letters of Credit and Bank Guarantees (SBIM, BGIS, BGRE, SBEX)

Evergreen instruments carrying an automatic extension period are now renewed automatically, removing the manual Renewal message previously required on each renewal date. Only instruments that actually carry an automatic extension period are considered for renewal; instruments without one are left untouched.

Automatic renewal is enabled by default. Banks whose back office already generates its own Renewal messages can opt out at endpoint level, from the Export menu of the Admin interface:

• Opt in — Konsole generates the Renewal message automatically
• Opt out — the bank's back office remains responsible for sending it

Opting out prevents duplicate renewals where a bank's own system already handles the extension. The setting applies to all evergreen instruments on the endpoint, including those issued with digital delivery.

User Interface translated in German (User Settings)

The Konsole user interface is now available in German, based on each User's Settings. Field labels, tooltips, date formats and authentication screens are covered.

New Report available: Task List with Unanswered messages (Analytics)

A new report has been added to the set of pre-defined Analytics, giving corporates and banks visibility on outstanding items and supporting follow-up on response times.

Improvements

Goods module

• Goods x Trakk for Release Request - Release confirmation email

Email Directory Lists can now include signing roles as recipients, alongside the fixed To, CC and BCC addresses. A new Signing role recipients panel is available in the Admin interface, on each Email Directory List linked to a Goods template.

The selector lists only the signing roles that are actually used in the endpoint's Signing Role Combinations applicable to Goods messages, so the configuration stays aligned with the approval chain already in place.

When the release confirmation email is sent, the users who effectively signed under the selected role are added in copy. Recipients therefore follow the actual approval chain of each release, instead of a static address list that has to be maintained whenever the team changes.

Blind copy is fully honoured: an address configured in BCC only appears in the Bcc header and is not visible to the other recipients, and an address present in both CC and BCC is included once, in CC.

Managing role recipients requires the same permission as managing To, CC and BCC addresses.

[OUTLOOK ONLINE OFR SCREENSHOT ANONYMIZE]

• Clause Library extended to Special Instructions field

The Clauses Library is now available on the Special Instructions field of the Goods module Narrative tab, alongside the narrative fields already covered.

A search icon on the field opens the library and gives access to pre-configured text blocks. Selecting an entry populates the field automatically, and the inserted text can then be edited freely without affecting the stored clause.

This is particularly useful for recurring content that has to appear on the release PDF and cannot be captured by the standard address fields — a full entity name and postal address, for example, previously retyped on every release with the associated risk of error and inconsistency.

Creating, updating and deleting clauses follows the existing library permission model and remains reserved to users holding the Manage Clauses Library role.

UX Improvements for faster message creation and better data quality 

• Single-bank corporates. When a corporate is connected to a single bank, the bank endpoint is pre-selected on any new instrument and the selection step is skipped. The selector behaves as before for corporates connected to more than one bank, and reappears as soon as a second bank is connected.
• Bank selection from the SWIFT directory. The directory picker has been redesigned. Results now display the bank identifier and name on the first line and the bank address on the second, presented consistently whether or not a search has been performed.

• NEW STEP action. The NEW STEP action is no longer offered on a message whose status is not final, preventing a follow-up step from being started on an incomplete exchange.

Not Final Status	Final Status

Bulk Import

• The column (GTR) Automatic Extension Period Days has been added to the BGRE/SBEX bulk import template, bringing it in line with the BGIS/SBIM template. The column is mandatory when Automatic Extension Period is set to DAYS. The three extension modes remain mutually exclusive: DAYS requires the Days column, OTHR requires the Details column, ONEY requires neither.

Credit Line add-on: custom FX Rate based on File Upload

 These features are optional. Please reach out to your dedicated Account Executive to learn more about Credit Line Monitoring powered by Komgo.

• Corporates with appropriate permission (Manage Credut Line) can now decide which exchange rate applies to their credit line, instead of relying on the default market source. Rates are imported from a CSV file listing, for each line, the valuation date, the target currency and the rate. Once imported, they are used to convert message amounts against the credit line.

• A dedicated Exchange Rate entry in the Admin menu gives access to the import and to the history of previous imports, showing the file name, the date and the user who performed it. Two permissions govern access, one to consult the imported rates, one to manage them - so that the ability to change a rate can be restricted to the appropriate users.

• Sending a message in a currency for which no rate has been loaded is blocked, with an explicit message indicating that the conversion cannot be performed.

(screenshot for Admin)

Bug Fixes

The following issues reported by clients have been resolved:

• SWIFT directory - missing banks. Banks whose name exceeds 35 characters are now imported into the directory, with the overflow stored in the address field. 
• Admin Audit Log - missing user identity. User-category audit entries again record and display the username on user creation and update. 
• Sending multiple drafts. Selecting a subset of drafts in the Draft repository now sends exactly the messages that were ticked.
• Forwarding a message by email. Forwarding no longer fails when the forward email subject has not been configured; the subject is now a mandatory configuration field.
• Guarantee Word preview. The Word preview no longer fails on guarantees containing an applicant address field.
• Goods release - Warehouse validation. Switching the release reason away from Release to Discharge Vessel no longer raises a blocking validation error on Warehouse fields that are not displayed.
• Bulk import of import Letters of Credit. Bulk creation of LCIM instruments addressed to a connected corporate endpoint now completes as expected.
• Automatic pre-fill of field Obligor in Bank to Corporate direction (BGIS, SBIM). On the Bank-to-Corporate direction, the Obligor and Instructing Party field is auto-filled based the endpoint information, aligning the behavior with the Corporate-to-Bank direction.
• Signing rules with amount. Messages that carry no amount are no longer blocked by signing rules configured with an amount threshold. This covers subtypes with no amount field (Non-Extension on SBIM, SBEX, BGIS and BGRE; Closing and Direct Payment on DCIM and DCEX; Release at Submitted on DGIS). Several subtypes carrying a mandatory amount that were not evaluated against the correct field are now mapped correctly.
• Endpoint State. The behaviour of endpoint states has been aligned. A locked endpoint can no longer send messages but continues to receive them. Cancelled and disabled endpoints can neither send nor receive.

Deprecations and Behavior Changes

• Signing rules with an amount threshold. Until 13.2, a message carrying no amount could not be signed by a user whose only applicable signing rules were amount-restricted. From 13.2, such messages are excluded from the amount check and can be signed. Administrators who relied on the previous behaviour to block these subtypes must now configure an explicit rule. Please review your signing rule configuration before upgrading.
• Locked endpoints. A locked endpoint can no longer send messages. Integrations that submit messages on behalf of a locked endpoint will receive an error where the send previously succeeded.
• Digital Delivery - document classification. A document attached to a digital issuance and classified as Applicant is only valid on a message that generates a beneficiary export. Sends that do not satisfy this condition are rejected with the new error code GTSA_ERROR_0108, on both the user interface and the SDK path.