What's new in Packs V11.0.2.0

This is what's new in this version of packs:

What's new in Pack for Financial Payment v11.0.2.0

SWIFT component:

  • Support is provided for 2025 SRG Standards
  • Corresponding updates are as follows:
    • SWIFT type trees
    • LMF maps and trees
    • Java Validation Component and support for ISO 20022 Contingency Measures (ICM) additional network rules for SWIFT MT Category 1 and 2 payment instruction messages
    • Introduced a configurable property in jvalccyy.prop to enable or disable ICM rules validation:

      icm.validation.enabled=false

    • MX schemas, type trees, and validation framework
  • For TX version 11.0.2, and later
    • IFD deployment script will need saved .msl to TX_INSTALL_DIR/system folder
    • Prop file will no longer have sub-directories references under TX install directory
    • As a pre-requisite, users will need to edit the property file to replace generic PACK_INSTALL_DIR with the actual location where the ZIP distro was unzipped
    • Utility jvcsetup.sh in swiftJVCconfigIBM.tar.gz is for Docker, and Podman based installations
  • For Design Server installation:
    • Copy the jvalccyy.jar and jvcwrap.jar into the directory set in the config.yaml server.persistence.libs, by default, this is set to /opt/txlibs. Then restart the tx-server, for example ./ITX, stop and then start ./ITX
  • Configuring JVC on Design Server:
    • After importing the swiftMTCompliance.zip project, the jvalccyy.prop file must be copied into the workdir directory under directory set in the config.yaml server.persistence.files, default settings is /opt/txfiles/workdir
    • On the project, update the map rule on the validate_message map, on output card #1 item JvalPropPath. Change the map rule from =NONE to the location of the jvalccyy.prop
    • For example:
      • On UNIX: ="DS_DATA_DIR/workdir"
      • On WINDOWS: ="DS_DATA_DIR\\workdir"

      Where DS_DATA_DIR refers to the Design Server data directory, set in the config.yaml server.persistence.files previously TX_FILE_DIR

  • Post EAP updates:
    • Updated swift_iso15022_2025.mtt to change Tag 94a in MT524 Sequence B and MT543 Sequence C from mandatory to optional.
    • Updated MT566.xml to modify Tag 97D in Sequence D2, allowing the Identification of Blockchain or Wallet field a maximum length of 140 characters.
    • Updated MT300.xml to change Tag 22U format to 12x.
    • Updated swift_iso7775_2025.mtt
      • MT097 updated to remove Tags 433 and 434.
      • MT030 removed from Live System Messages list.
      • MT199 and MT299 updated to remove CASE structure.
    • Updated descriptions for error codes C44 and C47 to reference Sequence B.
    • Updated and clarified network rules for error codes E62 and C71 on MT567.
    • Field 70 ICM rules enforced for: MT103 COR/STP, MT202 COV, and MT205 COV.
    • Field 72 ICM rules enforced for: MT200, MT202 COR/COV, and MT205 COR/COV.
    • Field 72 NOT STP ICM rules enforced for: MT103, MT202 COV, and MT205 COV.

NACHA component:

Support 2025 NACHA Operating Rules related to Company Entry Description were previously implemented in ACH 2024 type trees, no ACH 2025 type trees for this release.

FIX component:

Support FIX 5.0 SP2 Extension Pack (FIX Latest) up to EP299.

SEPA component:

  • Support 2025 EPC SCT/SDD rulebooks, including both structured and hybrid formatted addresses
  • Enhanced SEPA compliance map configuration to support UNIFI validation and to allow unstructured address formats
  • Update SEPA EPC example with sample SDD Core and B2B test files, along with improved documentation for setup and configuration
  • Original Message name identification for matching will be restricted to message variants and versions supported by this Pack

Miscellaneous:

  • For ITX 11.0.2, build JVC jars using IBM Semeru JAVA 17
  • ZIP distros are digitally signed

Deprecated components:

  • SWIFT MT-MX translation example maps
  • SWIFT Sterling B2B Integration examples
  • SEPA EPC rules related to ‘matching’ elements with original messages

What's new in Pack for Financial Payment Plus v11.0.2.0

CBPR+ Translation:
  • Updated translation frameworks to support CBPR+ Translation guide version 1.7.2.
  • Additional CBPR+ Translation scenarios:
    • MT103 REJT <=> pacs.002.001.10
    • MT202 COR/COV REJT <=> pacs.002.001.10
    • MT205 COR/COV REJT<=> pacs.002.001.10
CBPR+ Validation:
  • Support version SR2025 schemas based on MyStandards Readiness CBPR+ Readiness portal published March 21, 2025.
  • New 2025 CBPR+ messages:
    • admi.024.001.01​
    • camt.025.001.08
  • Support for Hybrid Postal Addresses.
CHAPS ENH Validation​:
  • Support version 1.4.0 based on SWIFT MyStandards Readiness CHAPS portal published April 03, 2025.
EBA E1S1 Validation:
  • Support version UG2025 based on SWIFT MyStandards Readiness E1S1 portal published June 27, 2025.
T2 CLM Validation​:
  • New version UDFS T2 R2025.JUN schemas based on SWIFT MyStandards Readiness TARGET2 CLM portal published June 17, 2025.
  • Support for Business File Header.
T2 RTGS Validation:
  • New version UDFS T2 R2025.JUN schemas based on SWIFT MyStandards Readiness TARGET2 RTGS portal published June 17, 2025.
  • Support for Business File Header.
T2 CoCo Validation:​
  • New version UDFS T2 R2025.JUN schemas based on SWIFT MyStandards Readiness TARGET2 CoCo portal published June 13, 2025.
  • Support for Business File Header .
T2S Validation:
  • New version UDFS T2S R2025.JUN schemas based on SWIFT MyStandards Readiness TARGET2 T2S portal version published June 15, 2025.
  • Support for generic enveloping on BAH and instance Document.

SWIFT GPI/SWIFT Go​ Validation:

  • Support the following versions:
    • pacs.008.001.08 SWIFT Go – published February 03, 2025
  • Support for Hybrid Postal Addresses.
SWIFT UC​ Validation:
  • Update with version SR2024 schemas based on SWIFT MyStandards Readiness Universal Confirmation portal version published on January 30, 2024.
  • Support the following versions:
    • trck.001.001.03 published 30 January 2024
SIC RTGS​ Validation:
  • Support for generic enveloping on BAH and instance Document based on SWISS Interbank Clearing (SIC) Platform Release v4.12 (RTGS services, SIC and euroSIC) and 5.2 (SIC IP service).
NBP SORBNET3 Validation:
  • New validation frameworks (schema only) based on SWIFT MyStandards Readiness Narodowy Bank Polski (NBP) / Central Bank of Poland portal version published on August 02, 2024July 17, 2025.
NBOR ReGIS Validation:
  • Update validation frameworks (schema only) to support version 1.3 based on SWIFT MyStandards Readiness National Bank of Romania (NBOR) ReGIS portal version published on August 25, 2025.
NBOR SaFIR Validation:
  • New validation frameworks (schema only) based on SWIFT MyStandards Readiness National Bank of Romania (NBOR) SaFIR portal version published on June 30, 2023.
SWIFT Exception and Investigation CASE Validation:
  • New validation frameworks (schema only) based on SWIFT MyStandards Readiness CASE portal version published on May 05, 2025.
SWIFT SCORE+ Validation:
  • New validation frameworks (schema only) based on SWIFT MyStandards Readiness SCORE+ portal version published on February 13, 2025.

Deprecated components:

  • CHAPS L4L validation

What's new in the Pack for SAP Applications v11.0.2.0

Support for the latest versions of IBM Sterling Transformation Extender:

The Pack for SAP Applications v11.0.2.0 includes installation packages for all currently supported releases of TX at the time of the release, which includes ITX versions 10.1.0, 10.1.1, 10.1.2, 11.0.0, 11.0.1 and 11.0.2.

SAP BAPI Adapter:

The SAP BAPI Adapter has been added to enable invoking SAP BAPI functions from ITX maps and flows. This adapter is available in Design Server and returns data in JSON format.

SAP R/3 ALE adapter:

The SAP R/3 ALE adapter has been added to enable sending and receiving IDocs from SAP R/3 system from ITX maps and flows.

This adapter is available in Design Server and returns data in XML format.

The previously available adapters are now labeled “SAP R/3 ALE Classic” and “SAP R/3 BAPI Classic” in Design Server.

What's new in Pack for Healthcare v11.0.2.0

HIPAA
  • HIPAA 8060 preview - The 8060 preview is based on a combination of X12 8060 structure, the HIPAA 8040 implementation guidelines (TR3s), and existing HIPAA 5010 rules provided with the Health Care pack.
    The preview is not based on the HIPAA 8060 TR3s. Location of the preview is instream with the existing HIPAA 5010 support and includes four HIPAA transactions:
    • X322 - Health Care Claim Payment/Advice (835) Type 1 – Type 7
    • X323 - Health Care Claim: Professional (837) Type 1 – Type 7
    • X324 - Health Care Claim: Institutional (837) Type 1 - Type 2 Incomplete with limited testing.
    • X325 - Health Care Claim: Dental (837) Type 1 – Type 7
  • The hcsvu exit library shipped with the release MUST be used with the HIPAA compliance check maps. Code changes were required with the 8060 preview.
  • Enhancement - New Type 7 Rules with rule type R33 to enable extended validations for the HIPAA 837 (professional, dental), 270, and 271 diagnosis code pointers located in the SV1, SV3, EQ, and EB segments. Diagnosis code pointers should reference diagnosis codes in the HI segment and should not be duplicated
  • Enhancement - New 005010X279A1 Type 4 rules 60892 and 60893 (BHT03 required for real time processing). These rules are shipped with default on/off indicator set to off. These rules can be used with external process flows that can identify batch versus real time processing.
  • External Code List updates.
  • Enhancement - ICD10 code sets (T5_896 and T5_897) to provide historical codes. These code lists were updated to contain codes from 2018-2025.
  • Announcing plans to deprecate ICD9 type trees/schemas in a future release.
NCPDP
  • The Annual Code lists updates.
  • Enhancement Request - NCPDP PACDR needs to preserve the occurrence of repetitive fields in the input to enable mapping the same occurrence in the output.
  • Enhancement Request – NCPDP D0 Supply sample data for all messages. Maps used to generate generic sample data have been included and contain all valid segments and fields for each message with hard coded values. The maps may be modified as needed to change values and add repeats. The files can be validated using the NCPCP validation utility.

What's new in the Pack for Supply Chain EDI v11.0.2.0

X12 and X12U component:
  • Contains the X12 Standard currency updates with version 8060.
EDIFACT component:
  • Contains the EDIFACT Standard currency updates with D24A version.