1.2 Release Enhancements

Regulatory Enhancements

  • Hybrid Address Support for Parties as per ISO 20022 Guidelines

    System is enhanced to support hybrid (semi-structured) postal address option for all the parties in settlement instruction maintenance and in settlement subsystem of contracts. Town Name and Country are mandatory in the maintenance. The payment message generation request to OBPM carries the structured address field values maintained for the parties.

  • ISO 20022 MX Message Support for Foreign Exchange Trade

    System supports below listed foreign exchange trade messages in ISO20022 MX format( equivalent to MT300 - Foreign Exchange Confirmation): Foreign Exchange Trade Instruction (fxtr.014.001) - Sent by a participant to a central system to notify the creation of the foreign exchange trade agreed by both trading parties.

    Foreign Exchange Trade Instruction Amendment (fxtr.015.001) -Sent by a participant to a central system to notify the amendment of the foreign exchange trade previously confirmed by the sender.

    Foreign Exchange Trade Instruction Cancellation (fxtr.016.001) - Sent by a participant to a central system to notify the cancellation of the foreign exchange trade previously confirmed by the sender.

  • SWIFT 2025 changes

    System is enhanced to support SWIFT 2025 Regulatory changes: A new parameter for SWIFT 2025 is introduced to control enabling/disabling the usage of SWIFT 2025 changes.

    The field name for mandatory tag 30V under Mandatory Sequence B-Transaction Details, will now be renamed to Settlement date from earlier named Value Date . This will impact MT 300 and MT 304.

    In MT305( Foreign Currency Option Confirmation) mandatory field 31a will support a new Option W in addition to existing Option G which will specify the date, time, and location at which the option expires.

  • SWIFT 2026 changes

    System is enhanced to support SWIFT 2026 changes . Category 3 MT messages are enhanced to add a new subfield for country in the J tag which will be picked from the postal address maintained for the party.

Product Enhancements

  • Inflation Linked Bonds

    Oracle Banking Treasury Management (OBTR) is enhanced to support inflation-linked bonds for capital protection. These enhancements enable users to book, manage, and calculate instruments where principal and coupon payments are linked to inflation indices. Key features include:

    • Booking and Management of Inflation-Linked Bonds – Users can create and manage bonds with principal adjustments based on inflation indices, and coupon calculations are applied on inflation-adjusted principal.
    • Instrument Product Definition Screen (TIDINPRD) – Allows creation of instrument products for inflation-linked bonds, with proper segregation by preference classification (Bonds, Equity, etc.).
    • Instrument Master Screen (TIDINSDF) – Enables the definition of individual inflation-linked bond instruments.
    • Instrument Corporate Action Screen (TIDICADF) – Supports modification of revision schedules, coupon schedules, and redemption schedules.
    • Credit Rating Maintenance Screen (TRDCRERT) – Facilitates defining credit rating agencies and assigning ratings for instruments and issuers.
    • Redemption Blotter Screen (TIDRDBTR) – Allows manual redemption of bonds with a detailed split of positions across portfolios being redeemed.
    • Corporate Action Blotter(TIDCPBTR) - Streamline and enhance the processing of manual coupon events
    These enhancements strengthen OBTR’s capabilities in managing inflation-linked instruments, providing users with complete flexibility, accuracy, and transparency in capital-protected investment products.
  • Securities Conversion (Stock Splits and Mergers)
    The Securities Conversion functionality now supports corporate actions where an investor’s holdings in one security are transformed into another based on predefined terms and regulatory guidelines. The supported conversion types include stock splits and mergers. Key enhancements include:
    • New Maintenance Screen (TIDCNVMT) – Enables setup and ongoing maintenance of securities conversion rules and parameters.
    • New Deal Input Screen (TIDCNVTR) – Allows recording and management of conversion-related corporate actions, including splits and mergers.
    • Instrument Conversion Monitor (TIDCNVBT) – A new screen to track conversion status, including converted nominal amounts and custodian-wise conversions.
    • Linked Entities Subsystem – Added to the Securities Definition (SEDTRONL) screen, providing improved mapping and management of related entities.
    • Enhanced Securities Bank Parameters Maintenance (SEDXBNPM) – Existing maintenance screen under Deal Products now includes new fields to capture conversion products for the following deal
      • Bank Buy / Customer Sell
      • Customer Buy / Bank Sell
      • Customer Buy / Customer Sell
    These enhancements provide greater visibility, control, and accuracy in tracking instrument conversions and managing linked securities across deals.
  • Treasury Settlement-Netting
    Managing the settlement of cashflows throughout the lifecycle of booked deals is a critical operation in treasury management. In large treasuries, a dedicated team typically oversees settlement for all deals across various treasury modules and product types. To enhance operational efficiency, the new Treasury Settlement module has been introduced in Oracle Banking Treasury Management, supporting:
    • Net Settlement Across Deals – Enables netting of cashflows with the same counterparty and currency, even across multiple deals, modules, deal types, portfolios, and component types.
    • Centralized Settlement Management – Provides a unified platform for treasury teams to manage settlements consistently and accurately across the organization.
    This module streamlines settlement operations, reduces manual effort, and improves cashflow management across complex treasury environments. The Treasury Settlement module in Oracle Banking Treasury Management provides users with the ability to configure and manage settlements efficiently across deals and portfolios. Key setup functionalities include:
    • Treasury Settlement Parameters (NTDSNPRM) – Maintain settlement preferences at the Head Office or branch level.
    • Treasury Settlement Product (NTDSNPRD) – Define accounting roles and events for settlement processing.
    • Settlement Netting Scheme (NTDSNSHM) – Configure preferences for net settlement with a counterparty and currency.
    • Settlement Netting Agreement (NTDSNAGM) – Establish agreements for net settlement with a counterparty, ensuring standardized processing.
    The Treasury Settlement module enables users to efficiently perform, monitor, and analyze settlement operations across multiple treasury products:
    • Settlement Operations: Treasury Settlement Blotter (NTDSNBTR) – Initiate individual or net settlements.
    • Treasury Settlement Monitor (NTDSNMTR) – Monitor the status of settlements across external systems.
  • Settlement Analytics

    Treasury Settlement Dashboard (NTDSNDBD) – View summary statistics and track performance of initiated settlements.. Supported Modules: Cashflows from Money Market, Securities, Repo, Derivatives, Securities and Over-the-Counter Option modules can be processed through this module.

  • OBRH Integration

    OBTR is enhanced to support the integration with External Products like OBPM, ELCM and FCUBS through OBRH Existing External Service Maintenance screens for OBPM, ELCM and FCUBS are enhanced by adding Header Profile and Communication type fields.

  • Foreign Exchange Rate Fetch and Deal Booking
    Existing Treasury Customer Currency Spread Maintenance (CYDTRCSP) is enhanced with below additional fields to improve flexibility and mapping to external rate providers.
    • Rate Type: Added to map the external rate provider.
    • Amount Slab: Added for Buy/Sell spread tiering by amount.
    Below listed services are introduced in the system
    • Fetch exchange rate from the external rate source for the Foreign Exchange contract.
    • Book the Foreign Exchange deal based on the fetched rate.
    • Query the booked FX deal
    • Summary query for the booked deals
    System is integrated with OBDX for the above functionalities

Common Core Enhancements

  • Oracle Banking Microservice Architecture (OBMA) and Oracle Development Tool (ODT) Core Merger
    The OBMA Core and ODT Core have been unified into a single common core system to be shared by both OBMA and ODT products.
    • Functions that existed in both cores have been removed from the ODT common core if they were already available in the OBMA common core.
    • The OBMA common core screens will now be used to maintain all common core data.
    • The ODT common core will reference OBMA common core data through Oracle database views.
    • Replication of the following entities from Oracle FLEXCUBE Universal Banking to the ODT common core has been discontinued:
      • External Customer
      • External Customer Account
      • External Chart of Accounts
      • External Consumer Loan Account
      • External Transaction Code
  • Security Management System (SMS) Unification
    This enhancement unifies SMS user/role management across OBMA and ODT.
    • This is achieved through the System for Cross-domain Identity Management (SCIM), which facilitates seamless synchronization of user data (profiles, roles, attributes, permissions) across systems and domains.
    • SCIM offers standardized APIs for operations like Create, Read, Update, and Delete. It ensures that common SMS attributes in OBMA are exposed to ODT without data inconsistencies.
  • Synchronous EOD between ODT and OBMA Framework
    The system now supports synchronous EOD between OBMA products and ODT products to ensure consistency and accurate status updates across frameworks.
    • New Parameter: OBMA_EOD_ENABLE – Determines whether EOD processing is triggered from ODT or OBMA. When enabled, EOD-related datastore updates for status and branch date from ODT are skipped to maintain synchronization.
    • The system now allow users, EOD to be triggered centrally from OBMA for both OBMA and ODT products:
      • Centralized EOD Trigger: Users initiate EOD from OBMA.
      • Automated ODT EOD Invocation: OBMA triggers the ODT EOD by calling the REST service of End Of Cycle Operations (AEDSTART / BrnEODStartService) for each EOD stage.
    • OBMA will wait/hold the EOD stage until ODT EOD stage is completed. Completion of ODT EOD stage, it will be identified by OBMA by querying the REST service of EOC Monitor(AEDBRMTR) (BrnEODMonitorService) screen.
    This enhancement ensures synchronized, streamlined, and automated EOD processing across the OBMA and ODT frameworks, reducing manual intervention and improving operational efficiency.
  • OBMA common core customer availability in OBTR

    The customers maintained in OBMA common core will be available in OBTR for usage even when the customers are not maintained in Treasury customer maintenance screen . A new template screen is introduced based on the customer category to default the Treasury related details for the replicated customers .