This DOKA-NG release Version 2.5.09 contains following main R&D enhancements and many other functional features and technical enhancements,

• SWIFT 2026 changes for SWIFT interbank and Swift Score.
• Migration: Number of Amendments in Legacy Systems now included in migration files.
• Settlement advices now contain additional information about preliminary exchange rates and total interest.
• General Ledger extract: output file enhanced.
• Bug corrections for CBPR+, Loans, Accruals, Reports and others.

Improvements:

• [Improvement] - SR2026: DBxSWH - Mapping for trailer data of incoming MT Swift
• [Improvement] - SR2026: Swift incoming (DBxSWH) - Mapping for trailer data of incoming Swifts
• [Improvement] - SR2026: SWIFT ADR- Adjust party field mappings for incoming SWIFT Interbank messages
• [Improvement] - SR2026: SWIFT ADR - Field 59A replacement with 59C where 59a is present
• [Improvement] - SR2026: SWIFT address changes using subsequences in MT7xx messages, Replacement of Tag 50B Non Bank Issuer by individual tags 50E, 50I, 50M, 50U, 50W
• [Improvement] - SR2026: IMPBID /CHKBID import type LEI as well
• [Improvement] - SR2026: IMPBID /CHKBID import type BLZ as well
• [Improvement] - SR2026: Changes in Database fields for Tags 44A, 44B, 44E, 44F in LI, LE, LT, SC/ SD, SG and PA
• [Improvement] - SR2026: Incoterm code additional values and Incoterm Place to allow 2 x 70z characters
• [Improvement] - SR2026: Look and Feel of Shipment fields and Incoterms in the panels
• [Improvement] - SR2026: Check if Shipment field 44A, 44B, 44E, 44F changes are required for CP and TR
• [Improvement] - SR2026: Update HS Code Database fields for as Tag45H in LI, LE, LT, GI opening and amendment Swift & Score messages
• [Improvement] - SR2026: Update Incoming Swift & Score mapping for HS Code as field changed as Tag45H instead of 44K
• [Improvement] - SR2026: GI- Update Pretty Print label to “Beneficiary Identification” for tag 59A (MT 760, 765, 767 & 785)
• [Improvement] - Transfer: BTTSND Document Instructions panel is missing
• [Improvement] - SR2026:GI- MT760 Field 23 Allowed Only When 22A = ACNF or ADVI
• [Improvement] - SR2026: SWIFT ADR- Adjust mappings for incoming SCORE messages (Party changes)
• [Improvement] - SR2026: Swift Score Outgoing - 29B changed to 29Z & character set updated to z (4*35z) for 29Z and 29D
• [Improvement] - SR2026: Swift Score Incoming - 29A changed to 29Z & character set updated to z (4*35z)
• [Improvement] - SR2026: Swift Score Outgoing - Address structure changes for 748<750>
• [Improvement] - SR2026: Swift Score Outgoing - Tag 21T (Customer Business Reference ) Mandatory for 737, 758, 781
• [Improvement] - SR2026: Swift Score Outgoing - Tag 23x code FACT- SwiftNet
• [Improvement] - SR2026 Incoming & Outgoing: Change Tag 73A to 71D for MT765 (SWIFT and SCORE)
• [Improvement] - SR2026: Swift Score Outgoing - Field 78B changes
• [Improvement] - SR2026: HS Code field to be created in Seq C panels of Guarantee transactions
• [Improvement] - SR2026: SWIFT Structured Addresses for DTA - Add new tag structure for outgoing DTA messages
• [Improvement] - SR2026: SWIFT and SCORE: Check for amended addresses in outgoing messages
• [Improvement] - CBPR+: Optionally add value date field for MX messages
• [Improvement] - Migration: Migration of No of Amendments In Legacy Systems
• [Improvement] - Settlement: Issue on Currency exchange rate Display in Advice of Acceptance Letter
• [Improvement] - General Ledger (DBIGLC): Include Client Number and Nostro Correspondent Client ID in DOKA GLE extract
• [Improvement - Bookings: Differences in Loan booking between LI and BC
• [Improvement] - Add Windows User to the Session Record

Bug Fixes : 

• [Bug Fix] - Import Collection: BCTPAY creates a DPU, but no DPU is necessary for free of payment
• [Bug Fix] - System Manager: Wrong Status of MQITSK in SYSMGR
• [Bug Fix] - System Settings: Issue with "Production" flag
• [Bug Fix] - Document Editor: Export data of document editor
• [Bug Fix] - Trade AI: Type setting for JSON, XML Files in the Trade AI interface should be amended
• [Bug Fix] - Participation - Expiry date of the LC/Guarantee Field (EXPDATLC) not showing the changed value
• [Bug Fix] - Target 2: Business Application Header version to be updated for Target2 messages
• [Bug Fix] - RPO / RIVO: Automated attachments
• [Bug Fix] - CBPR+: Pacs.009 - Allowed character length against the field - Instruction for Creditor Agent and Instruction for Instructed Agent
• [Bug Fix] - DBxATC: Copy From Transaction for Documents to copy actual description
• [Bug Fix] - Loans: TRCX related observations
• [Bug Fix] - Workflow Manager: MQITSK crashes with dump because of duplicate keys when reading CAMT.054 message
• [Bug Fix] - Export Finance: Dump while saving ECTEDT Transaction
• [Bug Fix] - Loans: Unable to proceed with Amendment for loan (TRTAME)
• [Bug Fix] - Accrual: Interest Accrual not Recalculated After Cancellation of Partial Payment - Instalment scenario
• [Bug Fix] - Office: Showing all Usergroups of all available entities
• [Bug Fix] - Export LC: Unable to generate Free format message via channel DTE
• [Bug Fix] - Loans: Interest Advice and TRCX Commission Not Generated for Extended Period on Capitalized Amount During Loan Amendment (TRTAME)
• [Bug Fix] - DNGAPI - Add infotext should update existing OIT
• [Bug Fix] - SWIFT Score: Duplicate Tags in MT 798 messages
• [Bug Fix] - Advance under Export Docs: Application dump in BETPAY transaction when 'create advance' is selected)
• [Bug Fix] - SR2026: Update position for HS Code tag (Tag45H) in LI, LE, LT opening and amendment Swift & Score messages
• [Bug Fix] - SR2026 Outgoing - Update position for Incoterms tag (Tag44I) in LI, LE, LT opening and amendment Swift & Score messages
• [Bug Fix] - Reports : DST Collection Interest Rate display in CSV
• [Bug Fix] - Settlement: In Financing fee long text field to show Total Interest rate i/o showing only margin
• [Bug Fix] - SR2026: Incoming LI/LE/LT messages not mapping Shipment Details & Incoterms Place related tag details
• [Bug Fix] - SR2026: Incoming LI/LE/LT messages not Applicant & Beneficiary party details
• [Bug Fix] - SR2026: Incoming score messages are not mapping Incoterms, Shipment fields
• [Bug Fix] - SR2026: Score Mappings to be created for 78K Instructions to the Paying/Accepting/Negotiating
• [Bug Fix] - SR2026: Swift Score Outgoing - 29B changed to 29Z & character set updated to z (4*35z) for 29Z and 29D
• [Bug Fix] - SR2026: Adjust Mappings for Incoming LI/LE/LT messages not Applicant & Beneficiary party details
• [Bug Fix] - Check and hide INSTXT in GC transactions for Score
• [Bug Fix] - SR2026: Adjust Mapping method Fill Addressblock from structured for Address Block fields
• [Bug Fix] - SR2026: Incoterms Place - field is displayed with scroll bar
• [Bug Fix] - SR2026: Adjust Mappings for Incoming LI/LE/LT messages for tag 51 party details
• [Bug Fix] - SR2026: Update DBISYS -Swift activation date to 14.11.2026
• [Bug Fix] - SR2026: Edited Party information in AddressBlock does not show in the Message Output
• [Bug Fix] - SR2026 - Swift ON - LETNOT - tag 41D is not mapped ok
• [Bug Fix] - SR2026 - Switch ON - Incoming MT720 - Parties mapping issues
• [Bug Fix] - SR2026: Party without Street information reflected without Mandatory Street tag (missing 59S) in MT700
• [Bug Fix] - SR2026 - Swift ON - Incoming MT760 ADVI - Governing Law and Place of jurisdiction are disabled
• [Bug Fix] - SR2026 : GITPOP - Applicant party details are not reflecting properly when mapped from Incoming 784
• [Bug Fix] - SR2026 - Swift ON- incoming MT765- tag 33A is displayed wrongly in unmapped section
• [Bug Fix] - SR2026 - Swift ON - Incoming MT760 ADVI - cannot produce outgoing MT760