Update: 4 September 2026

• V1, which includes the SWIFT changes, remains available on the INT environment.
• The UAT deployment date will be derived from that Q1 date and will therefore be communicated later.

INT environment deployment

Date:  July 13th, 2pm  (Geneva time)
Expected downtime: 2 hours

• UI: konsole-int.eu.komgo-sit.net/GTSAPortalWUI
• REST: konsole-rest-int.eu.komgo-sit.net

UAT environment deployment

Date: End of March 2027

Expected downtime: 2 hours

• UI: wui-uat.egtsa.com/GTSAPortalWUI
• REST: rest-uat.egtsa.com

PRODUCTION environment deployment

Date:  12 June 2027

Expected downtime: 2 hours

• UI: https://wui.egtsa.com/GTSAPortalWUI
• REST: https://rest.egtsa.com/GTSAPortalREST/

Release Content

New Features

Swift 2026 / ICC Major Upgrade

Structured Fields for Counterparty Addresses 

• In line with SWIFT 2026, counterparty addresses (Applicant, Beneficiary, Obligor, Drawer, Drawee, Non-bank Issuer) are now captured as structured data across Letters of Credit, Standby Letters of Credit, Guarantees, Documentary Collections, Letter of Indemnity, Release of Goods, Financing / Loan requests and Free-Text Instructions. Three fields complement the existing name and address: Town/City and Country (mandatory) and Post Code (optional). To ease the transition, Konsole pre-populates these fields for existing counterparties where possible, and users remain fully able to review and correct the proposed values. The structured fields are also available in the Address Book.

•  
• Bulk Import - Template has been extended with the new structured address columns (Applicant and Beneficiary City, Post Code and Country) so that these values are populated automatically during import.
   
• Transaction migration - Existing instruments are migrated to the new structured address format, with persisted company addresses enriched with Country Code, Town and Postal Code.

Existing fields updates

Several existing fields have been reformatted to meet the new SWIFT 2026 character set and length rules, with parsing and validation updated accordingly in the UI and on inbound/outbound SWIFT messages:

• Drafts at… (42C) on Letters of Credit - extended character set.

•  
• Shipment & transport locations (44A / 44B / 44E / 44F) on LCs, SBLCs and Guarantees - Place of Taking in Charge/Dispatch, Place of Final Destination, Port of Loading/Airport of Departure and Port of Discharge/Airport of Destination now support two lines

•  
• Instructions to the Paying/Accepting/Negotiating Bank (78) on LCs - increased capacity and extended character set

• Place of Jurisdiction (44P) - For SBLs and BG, the governing-law information has been restructured: "Governing Law/Jurisdiction (44J)" is renamed Governing Law, and the former narrative sub-field becomes an independent Place of Jurisdiction (44P) field. A validation rule ensures Place of Jurisdiction can only be filled when Governing Law is also filled
  
   
• Charges (71D) for SBLCs and BGs - The Charges field is upgraded to the new SWIFT 2026 structured coded format. Users enter charges as coded lines (fee type, currency, amount and free-text narrative); Konsole then dynamically parses each line and displays it in read-only structured blocks, with guidance messages when the coding rules are not respected. Supported fee types: Agent's Commission, Our Commission, Our Correspondent's Commission, Commercial Discount, Insurance Premium, Our Postage, Stamp Duty, Teletransmission Charges, and Wharfing & Warehouse. Correctly mapped on both incoming (bank-to-corporate) and outgoing (corporate-to-bank) directions
   

What happens to existing messages and transactions at the time of Go-Live ?

Existing transactions sent / received

• Transactions active at go-live continue — but messages are exchanged using the new structure (no fallback possible to “old” format)
• Komgo will convert messages onto the new format at first interaction with the transaction: the next message a user receives or replies to will be pre-populated with the new address format.
• A warning is displayed to ensure all users are aware of the change. This option will be possible as far as “old format” messages exist.
• Human validation is required before proceeding to the sending of your instructions.
• All historical messages remain available in their original format for audit purposes.
• No retroactive modification of archived data.

Action Required for Draft & Pending Signature Message

• All unsent Messages will be deprecated at the time of Go-Live.
• Deprecated draft will be available for cloning but won’t be available for sending.
• Messages pending Signature (sign-off) before the time of the release won’t be available.

New fields added for better Corporate/Bank Communication 

LCIM, LCEX, SBIM, SBEX, BGIS, BGRE

•  HS Code (45H) - A new optional field to tag the HS code(s) of the covered goods, available on Import/Export Letters of Credit, Standby Letters of Credit and Bank Guarantees. Multiple codes can be entered, separated by a comma. It allows banks, customs authorities and compliance teams to identify the nature of the goods without parsing the free-text goods description. On LCs it is available at Opening, Amendment and Internal Modification; on SBLCs and Guarantees it is available at Opening and Internal Modification
  
   

LCIM, LCEX

• Incoterms (44I) - Two dedicated fields for Import and Export Letters of Credit: a structured Incoterms code (three-letter ICC code selected from a dropdown, e.g. CFR - Cost and Freight) and an Incoterms Narrative. Previously embedded in free-text (45A/45B, 77C), Incoterms are now captured as structured data. When the code "OTH" is selected, the narrative becomes mandatory. Displayed in the Narrative tab, below the Goods Description (45A)
  
   
• Additional Information at Utilisation - The Additional Information field, previously available only at Opening, is now also available at the Utilization step (Corporate-to-Bank direction) on Import Letters of Credit. Corporates can provide additional context directly when presenting documents, keeping all relevant information within the same structured message

• Utilization Balance mandatory at payment - To support accurate tracking of partial versus full payment under a document presentation, the Utilization Balance field is now mandatory in the Bank-to-Corporate direction at the Paid and Settled statuses, for both Import Letters of Credit and Export Letters of Credit. The balance must be expressed in the same currency as the Utilization Amount and cannot be negative. This allows all parties and integrated systems, to know immediately whether a presentation is fully paid (balance = 0) or partially paid (balance > 0). The field remains optional in the Corporate-to-Bank direction and at other statuses

SBIM, SBEX, BGIS, BGRE -

• Renamed field: Undertaking Structure - Standby Letters of Credit & Bank Guarantees
  • On Standby Letters of Credit and Bank Guarantees (SBIM, SBEX, BGIS, BGRE), the former "Counter Guarantee" (Yes/No) field has been replaced by a clearer "Undertaking Structure" field offering two values: Direct (default) and Indirect
    • Direct: direct issuance, with no local issuing bank involved
    • Indirect: a counter-guarantee structure involving a local issuing bank (the former "Counter Guarantee = Yes" case), which displays the related local guarantee fields
  • This makes the choice self-explanatory for corporate users, reduces mis-selections at opening, and aligns the naming convention with GTK. 
  • The Purpose of Message (22A) values offered adapt automatically to the selected Undertaking Structure. 

• Requested Date of Issue (31C) - For local (indirect) guarantees (BGIS/BGRE, SBIM/SBEX), a distinct "Requested Date of Issue" is now available alongside the actual "Date of Issue". It is displayed when the Undertaking Structure is set to Indirect, at Opening and Internal Modification, and is shown in the Consolidated View. The existing field is renamed "Date of Issue (30)" for clarity

•  

• Settlement Account (53C) - A new optional Settlement Account field for Standby Letters of Credit and Bank Guarantees, available at Opening and Internal Modification, displayed in the Bank tab under the Issuer section, and mapped to the relevant settlement and claim flows

   

• Total Amount Claimed (33a) - Now fully supported on Standby Letter of Credit and Bank Guarantee drawing/claim flows, with both SWIFT options: date + currency + amount, or currency + amount only. The date is optional; when provided, currency and amount become mandatory

• Reduction Release Date field is now available on the Reduction Agreement Received message (Bank-to-Corporate) for Export Standby Letters of Credit and Bank Guarantees Received (SBEX, BGRE). This field already existed on the Reduction Payment / Paid message; it is now also captured when the bank confirms the reduction agreement, ensuring the release date is recorded consistently throughout the reduction flow