Messaging engine

Using Smart Investigate for Payments (SIP), many banks created extensive libraries of custom SWIFT MT templates for investigation and messaging scenarios. However, these templates are not directly portable to Pega Smart Investigate Agentic Automation because of differences in user interface structure and view rendering. Although MT messaging remains supported, the global transition away from MT formats makes this an appropriate time to review templates.

The following steps can help you to assess your existing MT templates:

• Assess which MT templates are still required.
• Use the template wizard in Pega Smart Investigate Agentic Automation to rebuild only necessary templates.
• Avoid rebuilding complex free-format messages. Adopt structured or templated formats instead.

The template wizard simplifies template creation, supports faster configuration, and reduces maintenance. Use this opportunity to transition to ISO 20022 (MX) standards or adopt out-of-the-box templates that enforce consistency and reduce manual effort.

Banks previously used many email templates for routine communications. These templates require review and reconfiguration because of changes in the template engine, data referencing, and user interface model. While you can reuse content, its structure and layout must align with the new approach.

The email template wizard in SIAA provides dynamic fields, conditional formatting, standardized styling, and reusable content blocks. This simplifies the template building process, ensures consistency, and reduces manual edits.

Follow these steps:

• Streamline and consolidate templates.
• Remove outdated formats.
• Improve clarity, branding, and tone.
• Align templates with standards.

Use this phase as a strategic refresh to enhance efficiency and enable scalable communication.

Banks can reuse existing MT parsing configurations. The SIP parsing component remains part of the product stack, although the version may differ. Exporting and importing parsing rules into SIAA is supported.

Parsing extracts details that include:

• Header block information (BICs, references)
• Transaction-specific data
• Investigation intent (cancellation, inquiry, creditor claims non-receipt)

Parsing uses priority rules to interpret strings when multiple matches occur. For example, prioritize “cancel” over “creditor claims non-receipt.”

Follow these steps:

• Migrate all parsing rules and intent priority logic.
• Validate imports for version compatibility.
• Test parsing outcomes for accuracy.

Proper handling ensures continuity in data extraction and intent recognition without reauthoring parsing logic.

ISO 20022 (MX) message formats provide richer data structures and improved standardization compared to MT formats. In SIP, MX support was limited or required customization. SIAA provides native MX support with configurable views that allow efficient interaction with complex message structures. The system parses, displays, and generates MX messages according to ISO 20022 standards.

Follow these steps:

1. Identify MX message types your institution needs to support.
2. Determine which business processes involve MX messages.
3. Map relationships between MT and MX formats for dual-format periods.
4. Configure MX views:
   • Enable relevant MX message types in system configuration.
   • Customize display formats to highlight key information.
   • Set up field mappings between MX elements and case properties.

SIP and SIAA support SWIFT schemes out of the box for FIN and FINPlus, including MT, CBPR+ MT and MX formats. Many domestic and regional Real-Time Payment (RTP) and Real-Time Gross Settlement (RTGS) schemes have moved to ISO 20022. These schemes require dedicated ISO 20022 investigation formats that Pega does not support out of the box.

If you updated SIP to support Payment Market Infrastructures (PMI) schemes, you can export and import configurations because both solutions share the messaging engine.

Follow these steps:

• Export and import SIP PMI rules (classes, properties, validation rules).
• Create new Constellation views for manual interaction because SIP sections are not compatible.
• Display only the necessary PMI message elements that are key to user interactions. Do not include all fields.
• Prepopulate data by mapping values from the transaction module or case data to PMI message elements.