pega advanced e&i rulebooki-rulebook... · pega-uitheme — ui theme rules. pega advanced...

Pega Advanced E&I Rulebook

IMPLEMENTATION GUIDE 7.31

© 2018 Pegasystems Inc., Cambridge, MA

All rights reserved.

Trademarks

For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks or service marks are property of their respective holders.

For information about the third-party software that is delivered with the product, refer to the third-party license file on your installation media that is specific to your release.

Notices

This publication describes and/or represents products and services of Pegasystems Inc. It may contain trade secrets and proprietary information that are protected by various federal, state, and international laws, and distributed under licenses restricting their use, copying, modification, distribution, or transmittal in any form without prior written authorization of Pegasystems Inc.

This publication is current as of the date of publication only. Changes to the publication may be made from time to time at the discretion of Pegasystems Inc. This publication remains the property of Pegasystems Inc. and must be returned to it upon request. This publication does not imply any commitment to offer or deliver the products or services described herein.

This publication may include references to Pegasystems Inc. product features that have not been licensed by you or your company. If you have questions about whether a particular capability is included in your installation, please consult your Pegasystems Inc. services consultant.

Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain inaccuracies or typographical errors, as well as technical inaccuracies. Pegasystems Inc. shall not be liable for technical or editorial errors or omissions contained herein. Pegasystems Inc. may make improvements and/or changes to the publication at any time without notice.

Any references in this publication to non-Pegasystems websites are provided for convenience only and do not serve as an endorsement of these websites. The materials at these websites are not part of the material for Pegasystems products, and use of those websites is at your own risk.

Information concerning non-Pegasystems products was obtained from the suppliers of those products, their publications, or other publicly available sources. Address questions about non-Pegasystems products to the suppliers of those products.

This publication may contain examples used in daily business operations that include the names of people, companies, products, and other third-party publications. Such examples are fictitious and any similarity to the names or other data used by an actual business enterprise or individual is coincidental.

This information is the property of:

Pegasystems Inc. One Rogers Street Cambridge, MA 02142-1209 USA Phone: (617) 374-9600 Fax: (617) 374-9620 www.pega.com

Pega Advanced E&I Rulebook

Document: Implementation Guide

Software Version: 7.31

Updated: February 2018

CONTENTS

About .......................................................................................................................... 1

Intended audience ........................................................................................... 1

Guide organization .......................................................................................... 1

Application overview ................................................................................................ 2

What is already set up .............................................................................................. 3

Ruleset hierarchy ............................................................................................. 3

Correspondence templates ............................................................................ 5

Template naming convention ................................................................... 5

Parsing and processing inbound and outbound messages ........................ 6

Processing flows and messages ............................................................... 6

Starter messages and flows ...................................................................... 7

Follow-up messages and flows ................................................................. 7

Processing and parsing activities ............................................................. 7

Parsing and processing parameters ........................................................ 8

Interactive outbound correspondence generation ................................ 8

Extended message automation................................................................ 9

ProcessMessageAttachment activities ................................................... 10

Extending the application ...................................................................................... 12

Working with correspondence templates ................................................... 12

Making templates available to users ..................................................... 12

Configuring ticklers and verification ...................................................... 13

Using SWIFTNet correspondence templates ......................................... 13

SWIFTNet message types and templates .............................................. 17

Property formatting for message types ................................................ 17

Customizing SWIFTNet correspondence ............................................... 17

Customizing parsing and processing ........................................................... 22

Updating the parse message process.................................................... 23

Parsing the message ............................................................................... 23

Setting up Interfaces for inbound and outbound messages ..................... 24

Appendix A: Template mapping............................................................................. 28

RTMP RequestToModify payment ................................................................ 28

RTCP RequestToCancelPayment .................................................................. 30

CNRC Claims Non-Receipt ............................................................................. 32

UTAP UnableToApply .................................................................................... 32

APIN AdditionalPaymentInformation .......................................................... 34

ROIN ResolutionOfInvestigation ................................................................... 48

NOCA NotificationOfCaseAssignment ......................................................... 54

RCAS RejectCaseAssignment ........................................................................ 60

DARQ DebitAuthorisationRequest ............................................................... 61

CSRP CaseStatusReport ................................................................................ 62

Pega Advanced E&I Rulebook Implementation Guide 1

TITLE of INTERNAL DOCUMENT – Arial Bold 12 pt

This document describes the key features and functions of the Pega Advanced E&I (Exceptions and Investigations) Rulebook application and how to extend it for initial production use.

Intended audience This guide is intended for the following individuals:

• Business Managers — Responsible for evaluating the Application solution and possess a general, non-technical understanding of its features and capabilities.

• Project Managers / Business Analysts — Responsible for implementing an Application solution that can be applied to specific business requirements, and ensures compliance and continuous improvement across organizations.

• System Architects / Application Developers — Responsible for building, maintaining, modifying, and extending the Application.

• System and Database Administrators — Responsible for the installation, security, and ongoing operational functions of the Application such as access, tuning, and troubleshooting. These users are presumed to be experienced with system operations.

Guide organization This guide contains the following sections:

Application overview Provides an overview of the application. What is already set up Describes defaults and samples that are set

up and ready for your use and provide the basis for extending the application.

Extending the application Describes how to extend the application including:

• Setting up correspondence • Suggestions for customizing processing • How to update message parsing

Integrating with external systems to either send or receive data.

Appendix A:Template mapping Details the correspondence template mapping between the XML message field tags and application properties.

About


TITLE of INTERNAL DOCUMENT – Arial Bold 12

The Pega Advanced E&I Rulebook provides SWIFTNet compliant XML message support, prepackaged straight-through processing (STP) capabilities, a predefined data model, and human-workflow support for initiating and responding to payment investigations.

In many payment operations, two to five percent of all payment transactions on any particular day result in an inquiry. Management of exceptions and investigations remains one of the most labor-intensive activities for a financial institution, largely because of widespread use of free-format messages and a lack of industry rules.

In response to increasing regulatory and competitive pressure, SWIFT implemented new Exceptions and Investigations messages to support the following four payment-related investigation activities:

• Request to Cancel Payment -This request is raised by the party that initiated the payment. It can eventually entail a Request For Debit Authorization and its confirmation, but excludes the return of funds.

• Request to Modify Payment - This request is raised by the party that initiated the payment. It can eventually entail an Additional Payment Information message that may be sent by the account servicing institution to the creditor or beneficiary.

• Unable to Apply - This activity is initiated by a party instructed to make a payment or by the beneficiary of the payment.

• Claim Non-Receipt - This activity is initiated by the party who is expecting a payment. If the payment does not arrive, this party contacts its debtor. The debtor then creates a case and assigns it (by sending it) to the party that it had earlier instructed to make the payment. The activity also covers missing cover situations.

The application complements an existing investigation system. It also automates these messages and the associated business processes for all SWIFTNET initiated investigations in a way that allows your organization to transition investigations to new XML solutions incrementally over a period of time.

The SWIFT publication Message Reference Guide for Exceptions and Investigations 1.2 details the workflow requirements for the use of these application messages.

Application overview



This chapter describes defaults and samples that are set up and ready for your use in the application. It is expected that you will use these as a basis for extending the application. Topics include:

• RuleSet Hierarchy

• Correspondence Templates

• Parsing and Processing Inbound and Outbound Messages

Because the application is installed with and resides on top of Smart Investigate for Payments, you also can use components and processes from Smart Investigate to extend the application. See the Smart Investigate for Payments Implementation Guide for information on the following relevant topics:

• System Administrator Account

• Work Object Naming Convention

• Default Work Groups, Workbaskets, and Worklists

• Default Operators and Access Groups

• Predefined Organizations, Divisions, and Units

• Predefined Access Roles and Privileges

• Predefined Work Parties

• Smart Investigate Correspondence Templates

• Smart Investigate Accounting Correspondence Templates

• Sample Database Model

• Sample Data for Testing Purposes

Ruleset hierarchy Rulesets are arranged hierarchically with the more general rules at the bottom and the more specific rules at the top. The four RuleSets at the bottom are standard in all applications and control the underlying Pega 7 operations. The RuleSets at the top control the application functions. The RuleSet order is critical to rule resolution. To find the appropriate rule, Pega 7 begins with the top RuleSet in this list. If the rule is not found, Pega 7 moves to the next RuleSet. In this manner, custom, site-specific rules have precedence over application-specific rules.

What is already set up



Application RuleSets are:

• PegaSI_Sample — A working example of the rules used to execute Smart Investigate for Payments.

• SwiftNetEIAppGuide — Rules that help to quickly set up & configure/extend the E&I application

• SwiftNetEI — SWIFTNet Exceptions and Investigations rules.

• PegaSIAppGuides — Rules that help to quickly set up & configure/extend the SI Payments application

• PegaSINostro — Smart Investigate rules for Nostro account reconciliation.

• PegaSIPymt — Smart Investigate rules for payment investigations.

• PegaSI — Smart Investigate rules.

RuleSets that are shared across application layers and contain workflow components are:

• PegaAppResearch-CommBank — PegaRESEARCH Manager components specific to commercial banking.

• PegaAppResearch — PegaRESEARCH Manager components that are not application specific.

• PegaCommBank — Commercial banking rules.

• PegaSIInt— Smart Investigate integration assets.

• PegaAppCorr — Application correspondence rules.

• PegaAppFin — Common financial application rules.

• PegaApp — Common application rules.

• Pega-UITheme — UI theme rules.



• UI-Kit-7 — The UI Kit provides application architects and user interface (UI) designers with a sample end-user UI that reflects the latest design trends and Pega 7 Platform UI capabilities.

Correspondence templates The application is configured with SWIFT XML correspondence templates that are called in the background, and correspondence processing in intent-led flows that allow operators to request and update correspondence.

Template naming convention Template names consist of four or five alphabetic abbreviations separated by an underscore character (_) that represent the following indicators.

• The XML message name

• The party to whom message is sent

• The Assigner of the message

• The Assignee of the message

• An applicable code or variation

For example, a template named DARQ_CP_Us_CP indicates a Debit Authorization Request DARQ message sent to the Credit Party CP, with Us as the Assigner, and the Credit Party CP is the Assignee.

A template named NOCA_IP_Us_CP_DTAU is a NotificationOfCaseAssignment NOCA message to the Inquiry Party IP, with Us as the Assigner, the Credit Party CP as the Assignee, and the code DTAU in the <Justfn> (Case forwarding notification code) field.

The following table lists the message abbreviations for the first part of the template name.

XML Message name Abbreviation Request To Cancel Payment RTCP Request to Modify Payment RTMP Unable to Apply UTAP Claim Non Receipt CNRC Resolution Of Investigation ROIN Notification Of Case Assignment NOCA Request For Duplicate RFDP Duplicate DUPL Reject Case Assignment RCAS Cancel Case Assignment CCAS Case Status Report Request CSRR Case Status Report CSRP



XML Message name Abbreviation Debit Authorization Request DARQ Debit Authorization Response DARS Additional Payment Information APIN Proprietary Format Investigation PFIN

Parsing and processing inbound and outbound messages The parsing and processing of inbound and outbound SWIFTNet messages is modeled after, and utilizes where possible, the generic flows, activities, and processing paths already configured and available to you in the Smart Investigate (SI) SWIFT processing layer of the application.

The key differences between SWIFT and SWIFTNet processing are:

• Data Mapping — Different formats and syntax are used in SWIFT and SWIFTNet messages.

• Data Parsing — Parsed data from SWIFT messages resides on the embedded ParsedResults clipboard page, whereas parsed data from SWIFTNet messages resides on the embedded SwiftNet clipboard page.

• Properties — SWIFT properties correspond to the block elements in the message while the SWIFTNet properties correspond to the XML element tags used in the related messages.

For example, :21: is a block element in SWIFT where < Doc:Id> is the XML tag in SWIFTNet.

The topics in this section describe the workflows and messages, activities, and properties configured in the application for use in processing and parsing SWIFTNet messages.

Processing flows and messages To help you develop your unique business processes, the application includes examples of processing flows that can be used in message processing.

The following table lists and describes those flows.

Flow Description WorkCaseSearchAndAttach Checks for the existence of a previously opened

exception object based on information in the inbound SWIFTNet message. It uses the activity PegaSI- MsgCase-SwiftNet.WorkSearchDoSearch.

CreateWorkCase Looks for a single unlinked transaction in PegaRESEARCH Manager and if possible opens a case. It uses the activity PegSI-MsgCase- SwiftNet.PaymentSearch.



Flow Description ReviewMessage Allows the owner of the work object to review

the message and determine what action needs to take place. This is a generic flow. It uses the generic activity PegaSI-MsgCase-SwiftNet-ProcessingMessageAttachments.

Starter messages and flows The application processes the following four message types using the WorkCaseSearchAndAttach and CreateWorkCase flows:

• ClaimNonReceipt (camt.027.001.02)

• RequestToCancelPayment (camt.008.002.02)

• RequestToModifyPayment (camt.007.002.02)

• UnableToApply (camt.026.001.02)

Follow-up messages and flows All other SWIFTNet message types are treated as follow-up messages. These messages are used to:

• Send correspondence between banks to keep the banks informed

• Continue an investigation

• Conclude an investigation

These messages use the PegaSI-MsgCase-SwiftNet.WorkSearchDoSearch activity, which looks at the SWIFTNet properties Case ID and Case Creator.

Note: When a work case is not located, the message is processed using the PegaSI-MsgCase- StepByStep flow. This processing is rare because you typically do not receive a follow-up message without first sending a starter message. When a starter message is sent about a work case, the application passes the existing Case ID and Case Creator (if already sent based on an inbound SN message received), or creates a new one based on your SWIFT ID and the pyID property of the work object.

If a follow-up message does not find an existing work case to link to, it calls the CreateWorkCase flow but does not search because it does not usually have any transaction information.

Processing and parsing activities The following table lists and describes the activities used to parse and process SWIFTNet messages.



Activity Description PegaSI-MsgCase-.LookupMessageClass Determines if this is a SWIFTNet message and if

so parses the Message Identifier Code (for example, camt.026.001.01) and changes the generic message object to the correct SWIFTNet object class.

PegaCommBank-SwiftNet-.ParseMessage Creates the embedded SWIFTNet page using a SWIFTNet Class- specific Model record. Subsequent pages are created when the Rule-Parse-XML records are called via the Apply-Parse-XML methods in steps 4 and 5 of the activity. Depending on the XML elements in the message header, either step 4 or step 5 is executed and calls the starting top-level Rule-Parse-XML record, either SwiftNetExchangeRequest or SwiftNetHandleRequest.

PegaSI-MsgCase- SwiftNet.WorkSearchDoSearch

Looks for previously opened exception objects and, if found, attaches the message to the object. If no object is found, it moves the message to an assignment for manual processing.

PegaSI-MsgCase-SwiftNet.PaymentSearch Copies the inbound SWIFTNet properties and places them into temporary work object properties so they can be called by a common PegaRESEARCH Manager activity.

PegaSI-MsgCase-

SwiftNet.ProcessMessageAttachment

Performs additional message attach processing and is a placeholder if an override is needed.

Parsing and processing parameters The following table lists and describes the parameters used in the parsing and processing of the messages.

Parameter Description TicketToSet Automatically advances an existing flow on a

work object. FlowToStart Starts a new workflow on the work object.

Interactive outbound correspondence generation The outbound SWIFTNet message generation is modeled after standard SWIFT correspondence. The application supports the generation of SWIFTNet messages interactively through the



CreateCorrespondence flow action in step-by-step processing and also automatically in an intent-led flow. See the Smart Investigate for Payments Deployment Guide for more information about these processes.

Extended message automation In this version of the application, the message processing has been further automated to include out-of-the-box automated flows that you can use to extend for automated processing of messages.

How the automated process is configured:

• The ProcessMessageAttachment activity sets a value for Param.FlowToStart that is used later to determine which flow to call for auto processing.

• The ProcessMessageAttachment activity also sets a value of true or false to Param.ReviewMessage.

• Values of true or null create an assignment to review the incoming message. This example shows the activity for CaseStatusReportRequest.

• The value of the Param.ReviewMessage is evaluated in the AttachMessage activity.

If the message has a MessageClass set to SWIFTNet, then the MessageProcessAuto flow is called.

MessageProcessAuto routes the message to the SICaseEntry workbasket and sets an SLA on the assignment.

• The flow then runs a utility that calls the ProcessMessageAuto activity.



Note: All of the flows called in steps 1 through 12 of the activity are out-of-the-box automated flows. To extend this activity, copy it to your RuleSet and then make your changes. You will also need to update the ProcessMessageAttachment activities and the Flow-New rules. In addition to this activity see the list of ProcessMessageAttachment activities to extend and the list of Flow-New Rules to extend later both of which are described later in this chapter. The ProcessMessageAttachment activities and the Flow-New rules work with the ProcessMessageAuto activity to fully extend the functionality.

ProcessMessageAttachment activities Versions of the ProcessMessageAttachment activity have been created for all E&I messages. These are placeholder activities that you also can use to extend the application.

The following report lists the activities you can copy to your RuleSet and change to meet your processing requirements.



This chapter describes how to extend the Pega Advanced E&I Rulebook application. Topics include:

• Working with correspondence templates

• Customizing parsing and processing

• Updating the parse message process

• Integrating with external systems to send or receive data

For information about the extension and personalization of the following generic investigation processing topics, see the Smart Investigate for Payments Implementation Guide:

• Personalizing Smart Investigate

• Setting Up Accounting Functions

• Setting Up Your Organization

• Integrating Smart Investigate

Working with correspondence templates The application comes with predefined correspondence templates. Because the correspondence is HTML based, it provides the opportunity to create a professional look and feel for letters, email, and faxes that are sent to customers and banks.

Email is generated through capabilities built into Pega 7. The routing, printing, and faxing of correspondence are handled by an interface to the PegaDISTRIBUTION Manager™. However, it is not necessary to have PegaDISTRIBUTION Manager installed when updating and testing changes to the templates. Correspondence is generated, attached to the case, and reviewed online in its printed form. Correspondence is not printed until the interface is active.

Configuration Tip: When you copy and customize the templates in your RuleSet, maintain the same correspondence rule name. This avoids unnecessary updates to workflow elements that call specific templates. Add templates only when no alternative is available.

The rule types used by the application correspondence are:

• Rule-PegaApp-Corr — For master and context-specific text templates; these rules inherit from Rule-Obj-Corr-.

• Rule-PegaCommBank-Corr — For master and context-specific text templates; these rules inherit from PegaApp-Corr-. The application templates inherit directly from this class set.

Making templates available to users The class in which the template is defined determines where it appears to users.

Extending the application



For example: the template Regardingcustpayment is defined in PegaSIPymt-Work. It appears in the Select Correspondence list for any interaction that inherits from PegaSIPymt-Work. The template Requestforcharges is defined in PegaSIPymt-Work-CorrBkChg.It appears only for Correspondent Bank Charges interactions (or any interaction that inherits from PegaSIPymt- Work-CorrBkChg).

When creating or copying a correspondence template, specify key elements to complete the record: Work Class, Template Name, Type, and Language. Language is a free-text field so you can define templates for any language you need.

Configuring ticklers and verification Correspondence forms have a Control tab that you use for configuring ticklers and tickler verification. You can configure the interval after which each tickler is sent, whether verification is required, the threshold necessary to trigger it, and the escalation activity to run if there is no response. Verification may be necessary for the original correspondence whether or not it has ticklers. You can also use this form to configure workbasket routing.

Note: Do not use ticklers for correspondence that may be edited in Microsoft Word.

Using SWIFTNet correspondence templates The application comes with preconfigured SWIFTNet message templates that cover many business scenarios. It is assumed that you are familiar with SWIFT terminology and messages. For additional SWIFT information, refer to www.swift.com.

Before configuring a new message template, review existing messages to determine if a message already exists that meets your requirements, or if a similar message exists that can be copied.

For each message type, there are correspondence templates that are intended for use in step- by-step processing or automated flows.

SWIFTNet Message templates are instances of Rule-PegaCommBank-Corr-Swift. SWIFT templates must be defined with the same keys as other correspondence you create.

The following message types are supported by the application:

• AdditionalPaymentInformation (028)

• CancelCaseAssignment (032)

• CaseStatusReport (039)

• CaseStatusReportRequest (038)

• ClaimNonReceipt (027)

• DebitAuthorisationRequest (037)

http://www.swift.com/



• DebitAuthorisationResponse (036)

• DuplicateInstruction (034)

• NotificationOfCaseAssignment (030)

• ProprietaryFormatInvestigation (035)

• RejectCaseAssignment (031)

• RequestForDuplicateInstruction (033)

• RequestToCancelPayment (008)

• RequestToModifyPayment (007)

• ResolutionOfInvestigation (029)

• UnableToApply (026)

XML message Message type Template name RequestToModifyPayment camt.007.002.02 RequestToModifyPayment

RTMP_RB_Us_RB

RTMP_CP_Us_CP

RTMP_IP_Us_IP RequestToCancelPayment camt.008.002.02 RequestToCancelPayment

RTCP_RB_Us_RB

RTCP_RB_Us_RB_UPAY

RTCP_RB_Us_RB_AGNT UnableToApply camt.026.001.02 UnableToApply

UTAP_SB_Us_SB ClaimsNonReceipt camt.027.001.02 ClaimsNonReceipt

CNRC_CP_Us_CP

CNRC_RB_Us_RB



AdditionalPaymentInformation camt.028.001.02 AdditionalPaymentInformation

APIN_CP_Us_CP

APIN_CP_Us_CP_IncBkPd

APIN_CP_Us_CP_IncDbtr

APIN_CP_Us_CP_IncCdtr

APIN_CP_Us_CP_IncInfo

APIN_IP_Us_IP

ResolutionOfInvestigation camt.029.001.02 ResolutionOfInvestigation

ROIN_IP_Us_IP_CNCL

ROIN_IP_Us_IP_IncBkPd

ROIN_IP_Us_IP_INFO

ROIN_IP_Us_IP_MODI

ROIN_IP_Us_IP_CWFW

ROIN_IP_Us_IP_RejIncDbtr

ROIN_IP_Us_IP_RejIncCdtr

ROIN_IP_Us_IP_RejIncDate

ROIN_IP_Us_IP_IncAmt

ROIN_IP_Us_IP_RejIncChgs

ROIN_IP_Us_IP_IncInfo

ROIN_IP_Us_IP_RejAmBene

ROIN_IP_Us_IP_Reject

ROIN_IP_Us_IP_MWFW

ROIN_RB_Us_RB_CWFW



ROIN_CP_Us_CP_CWFW

ROIN_IP_Us_RB_CWFW

ROIN_IP_Us_CP_CWFW

ROIN_IP_Us_IP_Last

NotificationOfCaseAssignment camt.030.001.02 NotificationOfCaseAssignment

NOCA_IP_Us_RB_FTHI

NOCA_IP_Us_CP_DTAU

NOCA_IP

NOCA_IP_Us_RB_CANC

NOCA_IP_Us_RB_MODI

NOCA_IP_Us_RB_CNCL

NOCA_IP_Us_CP_MODI

NOCA_IP_IP_Us_FIAG

NOCA_IP_Us_SB_FTHI

NOCA_IP_Us_DP_FTHI

NOCA_IP_Us_CP_SAIN RejectCaseAssignment camt.031.001.02 RejectCaseAssignment

RCAS_IP_Us_IP_NFND

RCAS_IP_Us_IP_NAUT

RCAS_IP_Us_IP_UKNW CancelCaseAssignment camt.032.001.01 CancelCaseAssignment RequestForDuplicate camt.033.001.02 RequestForDuplicate Duplicate camt.034.001.02 Duplicate Proprietary Format Investigation

ProprietaryFormatInvestigation

DebitAuthorisationResponse camt.036.001.01 DebitAuthorisationResponse



DebitAuthorisationRequest camt.037.001.02 DebitAuthorisationRequest

DARQ_CP_Us_CP_UPAY CaseStatusReportRequest camt.038.001.01 CaseStatusReportRequest CaseStatusReport camt.039.001.02 CaseStatusReport

CSRP_IP_UKNW

CSRP_IP_CLSD

CSRP_IP_INVE

CSRP_IP_ASGN RequestToModifyPayment camt.007.002.02 RequestToModifyPayment

RTMP_RB_Us_RB

RTMP_CP_Us_CP

RTMP_IP_Us_IP

SWIFTNet message types and templates This table lists the XML messages and corresponding message types supported in the application, and it shows the associated SWIFTNet XML correspondence templates configured to map to work object properties for that message type.

For a list of the message properties for the message types that are mapped to application properties in each of the E&I specific templates, see Appendix A.

Property formatting for message types The application defines a number of properties to support the fields for SWIFTNet message types. The fields that make up a SWIFTNet message are defined at the Rule-PegaCommBank- Corr-Swift level; they take the structure and contents described in the SWIFT guidelines.

Customizing SWIFTNet correspondence You can customize SWIFTNet correspondence to meet your needs by following these four steps:

Step 1: Decide which Work and SWIFTNet classes apply SWIFTNet Message templates are applicable to Work- classes and a SWIFTNet- message class (PegaCommBank-SwiftNet-). When adding a new template, you must decide which class the new template applies to.



For example:

• If a template is used only when processing a specific work type within payments, such as Beneficiary Claims Non-Receipt, then the message template should be made applicable to the PegaSIPymt-Work-BCNR message class.

• If all work streams within Payments require use of the message template, then add it to PegaSIPymt-Work-.

• If multiple business streams need to use a template, then add it to PegaSI-Work-.

The SWIFTNet class a message belongs to determines how the SWIFTNet message is constructed and validated at runtime. In the following figure, the Class Explorer displays the SWIFTNet class tree which stores properties, construction activities, and validation rules.



In general, all properties used in the generation of SWIFTNet messages are stored at the PegaCommBank-SwiftNet- or Embed-PegaCommBank-SwiftNet- levels, so all lower inheriting classes use them.

Validation and construction activities are particular to smaller groups of message types and stored at the PegaSI-MsgCase-SwiftNet (common) levels. If a SWIFTNet message type needs a unique set of validation and construction rules, then define these rules specifically at that message level.

For example:

• If the message being configured is a Beneficiary Claims Non-Receipt, it may call the activity DefaultDataToWorkCaseSpecific in the PegaSI-MsgCase-SwiftNet- ClaimNonReceipt class.

• However, other SWIFTNet message types may instead call the generic activity DefaultDataToWorkCaseSpecific in the PegaSI-MsgCase-SwiftNet class.

Step 2: Assess SWIFTNet standards Any message transmitted across the SWIFTNet network must conform to the guidelines defined by the SWIFTNet standards.

When making your assessment, consider the following:

• How is the message going to be used?

• Does the intended type of message suit the purpose?

• What fields are required?

• Which fields and which combinations of fields are required by SWIFT?

• What field formats are needed?

• What data format is each field expecting?

Step 3: Add a SWIFTNet template Follow the instructions below to add a template.

1. Open the Manage Rules bar: on the Class Explorer tab, select Rule > PegaCommBank > Corr > Swift. A list of instances appears.

2. Click New to display a new template form.

3. Enter the following information:

In the Applies To field, enter the class to which this template applies.

In the Corr Name field, enter the name of the template. (As a standard, the name should reflect the purpose of the template.)

In the Corr Type field, enter SWIFTNET as the Message type.



In the Language field, enter the required language (for example, English, French, or Italian). This appears as the default in the Short Description field.

4. Click Create.

5. Complete the fields on the Structure and Control tabs described in the following table.

Field Description Structure tab

Class Enter the class of the message from which field properties and validation should inherit. For each basic SWIFTNet message (such as AdditionalPaymentInformation and UnableToApply) there is a single class that defines the properties, HTML displays, and XML output. This class should be used when creating a template based on those existing messages.

Model Enter a Model rule (of type Rule-Obj-Model) if the property values are to contain default information. The model specified is normally Default.

Message Edit HTML Enter a Rule-Obj-HTML rule that contains one or more further Rule-Obj-HTML rules that specify how the HTML should appear to users.

Property Enter the SWIFT property to be displayed. Tickler Specify if this property is to be included in All

messages, Tickler 1, or Tickler 2. Type Specify the input type of the property: Display

only, Input Box, or Text Area. Stream Enter the name of a Rule-Obj-HTML rule (such

as case references, party information, or standard wording) that should appear within the field value.

CRLF? Select this check box if a carriage return line feed is required after this line.

Control tab

Days Until First Tickler Specify the default number of business days, after the dispatch of the original message, until a tickler should be sent.

Days Until Second Tickler Specify the default number of business days, after the dispatch of first tickler, until a second tickler should be sent.

Ticklers Require Verification Check this box if ticklers require verification before dispatch.



Field Description First Verification Workbasket Rule Specify a decision tree (of type Rule-Declare-

DecisionTree) that evaluates if verification is required and, if true, returns the name of the first verification queue.

Second Verification Workbasket Rule Specify a decision tree that evaluates if verification is required and, if true, returns the name of the second verification queue.

Threshold Property Specify an amount property in the work object to which the message relates. (This can also be referenced in the decision tree.)

Escalation Activity Specify the name of an activity to be executed should the generated message not be verified.

Days Until Escalation Specify the number of days between message generation and when the escalation activity should be run.

Is Financial Document? Check this box if the message relates to an accounting step.

After Create Select whether this message should be dispatched after generation (Send) or sent to a verification queue (as calculated in the decision tree) (Verify).

6. Click Save.

Step 4: Review property and message validation Validation for the format of some SWIFTNet properties is stored in a Property rule, or the Property rule can reference a Validate rule.

Validation for entire SWIFTNet messages are instances of Rule-Obj-Validate called ValidateMessage, applicable to class PegaCommBank-Swift-SWIFTNET-xxx (where xxx is the type of message).

Customizing parsing and processing Review the Parsing and Processing Inbound and Outbound Messages topic, earlier in this guide, before extending the intent-led business processes.

Consider the following configuration options when you want to extend the process:

• To start the Review Message flow on a work object, set the parameter ReviewMessage to true or false in the ProcessMessageAttachment activity.



• To set a ticket to automatically advance an existing flow on a work object, use the parameter TicketToSet.

• To launch a new workflow on the work object, use the parameter FlowToStart.

• To automatically process a message that is attached to an exception object, either start a new flow or set a ticket. The application starts a flow called MessageProcessAuto that gets passed the name of the ticket at the start of the flow. The flow then automatically goes to an assignment that is picked up by an agent for processing. If messages attached to exception objects are not being processed automatically on your system, make sure your SLA agent is running and using an access group with the correct privileges. You can also use this methodology to generate automated correspondence.

You also may want to extend the Application processing in the following areas:

• Automated rejection of follow-up messages that do not match an existing exception work object with a Reject Assignment SWIFTNet message.

Tip: Make a new exception work object for this purpose and use that to attach the message and send the response. Sending SWIFTNet correspondence on a message object is not a best practice.

• Automated Debit Authorization Request and Response tickets that will advance your customized work object flows.

Updating the parse message process During inbound SWIFTNet message processing, the entire message body—which in this case contains the bank’s message switch header information and the XML containing the actual SWIFTNet message—opens a generic message object. Each new message work object created from a SWIFTNet message has a class that corresponds to the type of inbound message sent, such as MyCoSI-Work-MsgCase-SwiftNet-RequestToCancelPayment.

SWIFTNet messages are XML messages and are parsed using the Rule-XML-Parse records. This application does not perform free-format text parsing on the SWIFTNet messages.

Parsing the message Parsing messages is performed in three steps.

1. Message Switch Parsing — The application strips off the bank’s message switch information. You should modify the switch information for each bank based on the format and content of the information from the bank’s own switch.

2. Change the class of the generic message object — In the application, the activity PegaSI- MsgCase-.LookupMessageClass has been modified to add checks for SWIFTNet messages. If the XML of a SWIFTNet message is found, the application changes the generic message object to the correct SWIFTNet message object class.



3. Parsing the XML of the SWIFTNet message — SWIFTNet messages use Rule-Parse-XML records to parse the records. Parsing starts in the activity PegaCommBank-SwiftNet-ParseMessage. Many of the detailed parse rules are stored in the Embed-PegaCommBank- SwiftNet- class and subclasses.

Configuration Tip: Rules are named based on the SWIFTNet XML layout and are easy to find using a rule search. For example, to see the parsing of the underlying transaction, you could do either of the following: search for “undrlyg” and find the Rule-Parse-XML record called Embed-PegaCommBank- SwiftNet-PaymentInstructionExtract.SwiftNet.Undrlyg, or search for “assgnmt” and find Embed- PegaCommBank-SwiftNet-CaseAssignment.SwiftNet.assgnmt. Alternatively, you can view the list of all Rule-ParseXML records instances using the Class Explorer.

Setting up Interfaces for inbound and outbound messages The application supports the ability to send and receive all sixteen SWIFTNet messages.

Follow the five steps below to set up the SWIFTNet interface for outbound messages. For additional interface configuration information, see:

• The Pega Developer Network (PDN) article How to integrate PRPC with external systems using SOAP.

• The “Integrating With External Systems” topic in the Smart Investigate for Payments Implementation Guide.

Note: If your system is already set up to send and receive SWIFT messages, you do not need to complete these procedures.

1. Update the CLASSPATH.

Add MQ Series Java components to the CLASSPATH environment variable of the Java Container application hosting the Process Commander application. Two components must be referenced in the CLASSPATH variable:

− com.ibm.mq.jar

− connector.jar

2. Determine the MQ Server details.

The fields listed below are required to configure the interface rules. The values must match your system values. Queue names can be anything you want to use for identification.

− IP Address

− Host name

− Port

− Channel name



− Queue details

− Inbound: PRPC.SI.LT.INB1

− Outbound: PRPC.SI.LT.OUTB1

3. Configure the following records:

For inbound messages, configure an instance of Data-Admin-Connect-MQServer.

For outbound messages, configure a Connect MQ rule.



4. Configure a Connect MQListener instance for inbound messages. The Server Name is part of the record key for this record, and its value must match the name of the MQServer record you created in the last step.



5. Configure a Rule-Service-MQ record by completing the Primary Page and Service Activity sections. This service then runs an activity, begins processing inbound messages, and executes when the Listener record pulls in data.

This appendix shows the following information for each of the application’s SWIFTNet XML message template fields:

• XML Field Tag - The XML tag listed in the message.

• XML Tag Description - The description of the XML tag.

• SI Field Name - The SI property from which the default value is derived for that tag. This information is displayed in one or more tables for each of the following message types.

− RTMP RequestToModifyPayment

− RTCP RequestToCancelPayment

− CNRC Claims Non Receipt

− UTAP UnableToApply

− APIN AdditionalPaymentInformation

− ROIN ResolutionOfInvestigation

− NOCA NotificationOfCaseAssignment

− RCAS RejectCaseAssignment

− DARQ DebitAuthorisationRequest

− CSRP CaseStatusReport

RTMP RequestToModify payment RTMP_RB_Us_RB: RequestToModifyPayment camt.007.002.02 XML Field Tag XML Tag Description SI Field Name <Assgnmt> Assignment +<Id> Id Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee BIC of Receiving Bank +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/ Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Message Name ID Trantype/Insttype +<OrgnlInstrId> Original Instruction ID Transaction Reference Choice amongst +<InstdAmt> Instructed Amount Credit Amount +<IntrBkSttlmAmt> Interbank Settlement Amount Credit Amount Choice amongst

Appendix A: Template mapping



XML Field Tag XML Tag Description SI Field Name +<ReqdExctnDt> Requested Execution Date Tran Date +<IntrBkSttlmDt> Interbank Settlement Date Tran Date <Mod> Modification

RTMP_CP_Us_CP: RequestToModifyPayment camt.007.002.02 XML Field Tag XML Tag Description SI Field Name <Assgnmt> Assignment +<Id> Id Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee BIC of Credit Party +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/ Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Message Name ID Trantype/Insttype +<OrgnlInstrId> Original Instruction ID Transaction Reference Choice amongst +<InstdAmt> Instructed Amount Credit Amount +<IntrBkSttlmAmt> Interbank Settlement Amount Credit Amount Choice amongst +<ReqdExctnDt> Requested Execution Date Tran Date

RTMP_CP_Us_CP: Requ estToModifyPayment camt.007.002.02 XML Field Tag XML Tag Description SI Field Name +<IntrBkSttlmDt> Interbank Settlement Date Tran Date <Mod> Modification

RTMP_IP_Us_IP: RequestToModifyPayment camt.007.002.02 XML Field Tag XML Tag Description SI Field Name <Assgnmt> Assignment +<Id> Id Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee BIC of Inquiry Party +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/ Case ID Case/Id +<Cretr> Case Creator Case/Cretr



XML Field Tag XML Tag Description SI Field Name +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Message Name ID Trantype/Insttype +<OrgnlInstrId> Original Instruction ID Transaction Reference Choice amongst +<InstdAmt> Instructed Amount Credit Amount +<IntrBkSttlmAmt> Interbank Settlement Amount Credit Amount Choice amongst +<ReqdExctnDt> Requested Execution Date Tran Date +<IntrBkSttlmDt> Interbank Settlement Date Tran Date <Mod> Modification (allow all fields of <Mod> block

to be available for data entry)

RTCP RequestToCancelPayment RTCP_RB_Us_RB: RequestToCancelPayment MX camt.008.002.02 XML Field Tag XML Tag Description SI Field Tag <Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee BIC of Receiving Bank +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Pmt Message Name ID Trantype/Insttype +<OrgnlInstrId> Original Instruction ID Transaction Reference Choice amongst +<InstdAmt> Instructed Amount Credit Amount +<IntrBkSttlmAmt> Settlement Amount Credit Amount Choice amongst +<ReqdExctnDt> Required Execution Date Tran Date +<IntrBkSttlmDt> Settlement Date Tran Date <Justfn> Justification +<CxlRsn> Cancellation Reason Code Justfn/CxlRsn +<AmtToDbt> Amount to Debit Credit Amount +<ValDtToDbt> Value Date Credit Value Date



RTCP_RB_Us_RB_UPAY: RequestToCancelPayment camt.008.002.02 XML Field Tag XML Tag Description SI Field Name <Assgnmt> Assignment +<Id> Id Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee BIC of Receiving Bank +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/ Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Message Name ID Trantype/Insttype +<OrgnlInstrId> Original Instruction ID Transaction Reference Choice amongst +<InstdAmt> Instructed Amount Credit Amount +<IntrBkSttlmAmt> Interbank Settlement Amount Credit Amount

RTCP_RB_Us_RB_UPAY: RequestToCancelPayment camt.008.002.02 XML Field Tag XML Tag Description SI Field Name Choice amongst +<ReqdExctnDt> Requested Execution Date Tran Date +<IntrBkSttlmDt> Interbank Settlement Date Tran Date <Justfn> Justification +<CxlRsn> Cancellation Reason UPAY +<AmtToDbt> Amount to Debit Credit amount +<ValDtToDbt> Value Date to Debit Credit value date

RTCP_RB_Us_RB_AGNT: RequestToCancelPayment camt.008.002.02 XML Field Tag XML Tag Description SI Field Name <Assgnmt> Assignment +<Id> Id Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee BIC of Receiving Bank +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/ Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Message Name ID Trantype/Insttype +<OrgnlInstrId> Original Instruction ID Transaction Reference



XML Field Tag XML Tag Description SI Field Name Choice amongst +<InstdAmt> Instructed Amount Credit Amount +<IntrBkSttlmAmt> Interbank Settlement Amount Credit Amount Choice amongst +<ReqdExctnDt> Requested Execution Date Tran Date +<IntrBkSttlmDt> Interbank Settlement Date Tran Date <Justfn> Justification +<CxlRsn> Cancellation Reason AGNT +<AmtToDbt> Amount to Debit Credit amount +<ValDtToDbt> Value Date to Debit Credit value date

CNRC Claims Non-Receipt CNRC_RB_Us_RB: Claims Non Receipt camt.027.001.02 XML Field Tag XML Tag Description SI Field Name <Assgnmt> Assignment +<Id> Id Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Receiving Bank BIC +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/ Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Message Name

TranType/ Insttype

+<OrgnlInstrId> Original Instruction Identification Transaction Reference Choice amongst +<InstdAmt> Instructed Amount InquiryAmount +<IntrBkSttlmAmt> Interbank Settlement Amount InquiryAmount Choice amongst +<ReqdExctnDt> Requested Execution Date Transaction Date +<IntrBkSttlmDt> Interbank Settlement Date Transaction Date

UTAP UnableToApply UTAP_SB_Us_SB: UnableToApply camt.026.001.02 XML Field Tag XML Tag Description SI Field Name <Assgnmt> Assignment +<Id> Id Our Exception Case Id



XML Field Tag XML Tag Description SI Field Name +<Assgnr> Assigner Our BIC +<Assgne> Assignee Sending Bank BIC +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/ Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Message Name

TranType/ Insttype

+<OrgnlInstrId> Original Instruction Identification Transaction Reference Choice amongst +<InstdAmt> Instructed Amount InquiryAmount +<IntrBkSttlmAmt> Interbank Settlement Amount InquiryAmount Choice amongst +<ReqdExctnDt> Requested Execution Date Transaction Date +<IntrBkSttlmDt> Interbank Settlement Date Transaction Date <Justfn> Justification Choice amongst +<AnyInf> AnyInformation Justfn/AnyInf +<MssngOrIncrrctInf> MissingOrIncorrectInfo ++<MssngInf> MissingInformation Justfn/MssngOrIncrrctInf/MssngI

++<IncrrctInf> IncorrectInformation Justfn/MssngOrIncrrctInf/

UTAP_DP_Us_DP: UnableToApply camt.026.001.02 XML Field Tag XML Tag Description SI Field Name <Assgnmt> Assignment +<Id> Id Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Debit Party BIC +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/ Case ID Case/Id +<Cretr> Case Creator Case/Cretr

+<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn

<Undrlyg> Underlying

+<OrgnlMsgNmId> Original Message Name

TranType/ Insttype



UTAP_DP_Us_DP: UnableToApply camt.026.001.02 XML Field Tag XML Tag Description SI Field Name +<OrgnlInstrId> Original Instruction Identification Transaction Reference Choice amongst +<InstdAmt> Instructed Amount InquiryAmount +<IntrBkSttlmAmt> Interbank Settlement Amount InquiryAmount Choice amongst +<ReqdExctnDt> Requested Execution Date Transaction Date +<IntrBkSttlmDt> Interbank Settlement Date Transaction Date <Justfn> Justification Choice amongst +<AnyInf> AnyInformation Justfn/AnyInf +<MssngOrIncrrctInf> MissingOrIncorrectInfo ++<MssngInf> MissingInformation Justfn/MssngOrIncrrctInf/MssngI

++<IncrrctInf> IncorrectInformation Justfn/MssngOrIncrrctInf/

APIN AdditionalPaymentInformation APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name <Assgnmt> Assignment +<Id> Id Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee BIC of Credit Party +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/ Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Message Name ID Trantype/Insttype +<OrgnlInstrId> Original Instruction ID Transaction Reference Choice amongst +<InstdAmt> Instructed Amount Credit Amount +<IntrBkSttlmAmt> Interbank Settlement Amount Credit Amount Choice amongst +<ReqdExctnDt> Requested Execution Date Tran Date +<IntrBkSttlmDt> Interbank Settlement Date Tran Date <Inf> Information



APIN_CP_Us_CP_IncBkPd: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name <Assgnmt> Assignment +<Id> Id Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee BIC of Credit Party +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/ Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Message Name ID Trantype/Insttype +<OrgnlInstrId> Original Instruction ID Transaction Reference Choice amongst +<InstdAmt> Instructed Amount Credit Amount +<IntrBkSttlmAmt> Interbank Settlement Amount Credit Amount Choice amongst +<ReqdExctnDt> Requested Execution Date Tran Date +<IntrBkSttlmDt> Interbank Settlement Date Tran Date

APIN_CP_Us_CP_IncBkPd: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name <Inf> Information +<LastSttlmAgt> Intermediary Settlement Agent ++<FinInstnId> Financial Institution Id +++<BIC> BIC Mod/LastSttlmAgt/ FinInstnId/

+++<ClrSysMmbId> Clearing System Member ID Choice Amongst ++++<USCHU> CHIPS Universal ID Mod/LastSttlmAgt/ FinInstnId/

ClrSysMmbId/ USCHU ++++<NZNCC> New Zealand NCC Id Mod/LastSttlmAgt/ FinInstnId/

ClrSysMmbId/ NZNCC ++++<IENSC> Irish NSC Id Mod/LastSttlmAgt/ FinInstnId/

ClrSysMmbId/ IENSC ++++<GBSC> UK Domestic Sort Code Mod/LastSttlmAgt/ FinInstnId/

ClrSysMmbId/ GBSC ++++<USCH> CHIPS Participant Id Mod/LastSttlmAgt/ FinInstnId/

ClrSysMmbId/ USCH ++++<CJBC> Swiss BC Id Mod/LastSttlmAgt/ FinInstnId/

ClrSysMmbId/ CJBC ++++<USFW> Fedwire Routing Number Id Mod/LastSttlmAgt/ FinInstnId/

ClrSysMmbId/ USFW



XML Field Tag XML Tag Description SI Field Name ++++<PTNCC> Portuguese NCC Id Mod/LastSttlmAgt/ FinInstnId/

ClrSysMmbId/ PTNCC ++++<RUCB> Russian Central Bank Id Mod/LastSttlmAgt/ FinInstnId/

ClrSysMmbId/ RUCB ++++<ITNCC> Italian Domestic Id Code Mod/LastSttlmAgt/ FinInstnId/

ClrSysMmbId/ ITNCC ++++<ATBLZ> Austrian Bankleitzahl Id Mod/LastSttlmAgt/ FinInstnId/

ClrSysMmbId/ ATBLZ ++++<CACPA> Canadian Payments Association

Routing Number Id Mod/LastSttlmAgt/ FinInstnId/ ClrSysMmbId/ CACPA

++++<CHSIC> Swiss SIC Id Mod/LastSttlmAgt/ FinInstnId/ ClrSysMmbId/ CHSIC

++++<DEBLZ> German Bankleitzahl Id Mod/LastSttlmAgt/ FinInstnId/ ClrSysMmbId/ DEBLZ

++++<ESNCC> Spanish Domestic Interbanking Id Mod/LastSttlmAgt/ FinInstnId/ ClrSysMmbId/ ESNCC

++++<ZANCC> South African NCC Id Mod/LastSttlmAgt/FinInstnId/ ClrSysMmbId/ ZANCC

++++<HKNCC> Hong Kong Bank Code Mod/LastSttlmAgt/FinInstnId/ ClrSysMmbId/ HKNCC

++++<AUBSBx> Australian Extensive Branch Network Id

Mod/LastSttlmAgt/FinInstnId/ ClrSysMmbId/ AUBSBx

++++<AUBSBs> Australian Small Network Id Mod/LastSttlmAgt/FinInstnId/

APIN_CP_Us_CP_IncBkPd: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name ClrSysMmbId/ AUBSBs +++<Nm> Name Mod/ LastSttlmAgt/

+++<PstlAdr> Postal Address Mod/ LastSttlmAgt/ ++++<AdrTp> Address Type Mod/ LastSttlmAgt/

FinInstnId/PstlAdr / AdrTp ++++<AdrLine> Address Line Mod/ LastSttlmAgt/

FinInstnId/PstlAdr / AdrLine ++++<StrNm> Street Name Mod/ LastSttlmAgt/

FinInstnId/PstlAdr / StrNm ++++<BldgNb> Building Number Mod/ LastSttlmAgt/

FinInstnId/PstlAdr / BldgNb ++++<PstCd> Post Code Mod/ LastSttlmAgt/

FinInstnId/PstlAdr / PstCd ++++<TwnNm> Town Name Mod/ LastSttlmAgt/

FinInstnId/PstlAdr / TwnNm



XML Field Tag XML Tag Description SI Field Name ++++<CtrySubDvsn> Country SubDivision Mod/ LastSttlmAgt/

FinInstnId/PstlAdr / CtrySubDvsn ++++<Ctry> Country Mod/ LastSttlmAgt/

FinInstnId/PstlAdr

+++<PrtyId> Proprietary Id ++++<Id> Id Mod/ LastSttlmAgt/

++++<Issr> Issuer Mod/ LastSttlmAgt/

++<BrnchId> Branch Id +++<Id> Id Mod/ LastSttlmAgt/ BrnchId/Id +++<Nm> Name Mod/ LastSttlmAgt/ BrnchId/Nm +++<PstlAdr> Postal Address ++++<AdrTp> Address Type Mod/ LastSttlmAgt/

BrnchId/PstlAdr/ AdrTp ++++<AdrLine> Address Line Mod/ LastSttlmAgt/

BrnchId/PstlAdr/ AdrLine ++++<StrNm> Street Name Mod/ LastSttlmAgt/

BrnchId/PstlAdr/ StrNm ++++<BldgNb> Building Number Mod/ LastSttlmAgt/

BrnchId/PstlAdr/ BldgNb ++++<PstCd> Post Code Mod/ LastSttlmAgt/

BrnchId/PstlAdr/P stCd ++++<TwnNm> Town Name Mod/ LastSttlmAgt/

BrnchId/PstlAdr/ TwnNm ++++<CtrySubDvsn> Country SubDivision Mod/ LastSttlmAgt/

BrnchId/PstlAdr/ CtrySubDvsn ++++<Ctry> Country Mod/ LastSttlmAgt/

+<IntrmySttlmAgt> Intermediary Settlement Agent

APIN_CP_Us_CP_IncBkPd: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name ++<FinInstnId> Financial Institution Id +++<BIC> BIC Mod/IntrmySttlmAgt/ FinInstnId/

+++<ClrSysMmbId> Clearing System Member ID Choice Amongst ++++<USCHU> CHIPS Universal ID Mod/IntrmySttlmAgt/ FinInstnId/

++++<NZNCC> New Zealand NCC Id Mod/IntrmySttlmAgt/ FinInstnId/

++++<IENSC> Irish NSC Id Mod/IntrmySttlmAgt/ FinInstnId/



XML Field Tag XML Tag Description SI Field Name ++++<GBSC> UK Domestic Sort Code Mod/IntrmySttlmAgt/ FinInstnId/

++++<USCH> CHIPS Participant Id Mod/IntrmySttlmAgt/ FinInstnId/

++++<CJBC> Swiss BC Id Mod/IntrmySttlmAgt/ FinInstnId/

++++<USFW> Fedwire Routing Number Id Mod/IntrmySttlmAgt/ FinInstnId/

++++<PTNCC> Portuguese NCC Id Mod/IntrmySttlmAgt/ FinInstnId/

++++<RUCB> Russian Central Bank Id Mod/IntrmySttlmAgt/ FinInstnId/

++++<ITNCC> Italian Domestic Id Code Mod/IntrmySttlmAgt/ FinInstnId/

++++<ATBLZ> Austrain Bankleitzahl Id Mod/IntrmySttlmAgt/ FinInstnId/

++++<CACPA> Canadian Payments Association

Mod/IntrmySttlmAgt/ FinInstnId/

++++<CHSIC> Swiss SIC Id Mod/IntrmySttlmAgt/ FinInstnId/

++++<DEBLZ> German Bankleitzahl Id Mod/IntrmySttlmAgt/ FinInstnId/

++++<ESNCC> Spanish Domestic Interbanking Id Mod/IntrmySttlmAgt/ FinInstnId/

++++<ZANCC> South African NCC Id Mod/IntrmySttlmAgt/FinInstnId/

++++<HKNCC> Hong Kong Bank Code Mod/IntrmySttlmAgt/FinInstnId/

++++<AUBSBx> Australian Extensive Branch Network Id

Mod/IntrmySttlmAgt/FinInstnId/

++++<AUBSBs> Australian Small Network Id Mod/IntrmySttlmAgt/FinInstnId/

+++<Nm> Name Mod/ IntrmySttlmAgt/

APIN_CP_Us_CP_IncBkPd: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name +++<PstlAdr> Postal Address Mod/ IntrmySttlmAgt/

++++<AdrTp> Address Type Mod/ IntrmySttlmAgt/ FinInstnId/PstlAdr

++++<AdrLine> Address Line Mod/ IntrmySttlmAgt/

FinInstnId/PstlAdr



XML Field Tag XML Tag Description SI Field Name ++++<StrNm> Street Name Mod/ IntrmySttlmAgt/

FinInstnId/PstlAdr

++++<BldgNb> Building Number Mod/ IntrmySttlmAgt/

FinInstnId/PstlAdr

++++<PstCd> Post Code Mod/ IntrmySttlmAgt/

FinInstnId/PstlAdr

++++<TwnNm> Town Name Mod/ IntrmySttlmAgt/

FinInstnId/PstlAdr

++++<CtrySubDvsn> Country SubDivision Mod/ IntrmySttlmAgt/

FinInstnId/PstlAdr

++++<Ctry> Country Mod/ IntrmySttlmAgt/

FinInstnId/PstlAdr

+++<PrtyId> Proprietary Id ++++<Id> Id Mod/ IntrmySttlmAgt/

++++<Issr> Issuer Mod/ IntrmySttlmAgt/

++<BrnchId> Branch Id +++<Id> Id Mod/ IntrmySttlmAgt/ BrnchId/Id +++<Nm> Name Mod/ IntrmySttlmAgt/

+++<PstlAdr> Postal Address ++++<AdrTp> Address Type Mod/ IntrmySttlmAgt/

BrnchId/PstlAdr/ AdrTp ++++<AdrLine> Address Line Mod/ IntrmySttlmAgt/

BrnchId/PstlAdr/ AdrLine ++++<StrNm> Street Name Mod/ IntrmySttlmAgt/

BrnchId/PstlAdr/ StrNm ++++<BldgNb> Building Number Mod/ IntrmySttlmAgt/

BrnchId/PstlAdr/ BldgNb ++++<PstCd> Post Code Mod/ IntrmySttlmAgt/

BrnchId/PstlAdr/P stCd ++++<TwnNm> Town Name Mod/ IntrmySttlmAgt/

BrnchId/PstlAdr/ TwnNm ++++<CtrySubDvsn> Country SubDivision Mod/ IntrmySttlmAgt/

BrnchId/PstlAdr/ CtrySubDvsn ++++<Ctry> Country Mod/ IntrmySttlmAgt/

BrnchId/PstlAdr/Ctry

APIN_CP_Us_CP_IncDbtr: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name <Assgnmt> Assignment +<Id> Id Our Exception Case Id



XML Field Tag XML Tag Description SI Field Name +<Assgnr> Assigner Our BIC +<Assgne> Assignee BIC of Credit Party +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/ Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Message Name ID Trantype/Insttype +<OrgnlInstrId> Original Instruction ID Transaction Reference Choice amongst +<InstdAmt> Instructed Amount Credit Amount +<IntrBkSttlmAmt> Interbank Settlement Amount Credit Amount Choice amongst +<ReqdExctnDt> Requested Execution Date Tran Date +<IntrBkSttlmDt> Interbank Settlement Date Tran Date <Inf> Information +<Dbtr> Debtor Mod/ Dbtr ++<Nm> Name Mod/Dbtr Nm ++<PstlAdr> Postal Address +++<AdrTp> Address Type Mod/ Dbtr/ PstlAdr/AdrTp +++<AdrLine> Address Line Mod/ Dbtr/ PstlAdr/ AdrLine +++<StrNm> Street Name Mod/ Dbtr/ PstlAdr/ StrNm +++<BldgNb> Building Number Mod/ Dbtr/ PstlAdr/ BldgNb +++<PstCd> Post Code Mod/ Dbtr/ PstlAdr/ PstCd +++<TwnNm> Town Name Mod/ Dbtr/ PstlAdr/ TwnNm +++<CtrySubDvsn> Country SubDivision Mod/ Dbtr/ PstlAdr/CtrySubDvsn +++<Ctry> Country Mod/ Dbtr/ PstlAdr/ Ctry ++<Id> Id Choice amongst +++<OrgId> Organisation Id ++++<BEI> BEI Mod/ Dbtr/Id/ OrgId/ BEI ++++<EANGLN> EANGLN Mod/ Dbtr/Id/ OrgId/ EANGLN ++++<USCHU> CHIPS Universal Id Mod/ Dbtr/Id/ OrgId/ USCHU ++++<DUNS> DUNS Mod/ Dbtr/Id/ OrgId/ DUNS ++++<BkPtyId> Bank Party Id Mod/ Dbtr/Id/ OrgId/ BkPtyId ++++<TaxIdNb> Tax Id Number Mod/ Dbtr/Id/ OrgId/ TaxIdNb ++++<PrtryId> Proprietary Id +++++<Id> Id Mod/ Dbtr/Id/ OrgId/ PrtryId/Id +++++<Issr> Issuer Mod/ Dbtr/Id/ OrgId/PrtryId/Issr



APIN_CP_Us_CP_IncDbtr: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name +++<PrvtId> Private Id Choice Amongst ++++<DrvrsLicNb> Drivers License Number Mod/ Dbtr/ PrvtId/ DrvrsLicNb ++++<SclSctyNb> Social Security Number Mod/ Dbtr/ PrvtId/ SclSctyNb ++++<AlnRegnNb> Alien Registration Number Mod/ Dbtr/ PrvtId/ AlnRegnNb ++++<PsptNb> Passport Number Mod/ Dbtr/ PrvtId/ PsptNb ++++<TaxIdNb> Tax Id Number Mod/ Dbtr/ PrvtId/ TaxIdNb ++++<IdntyCardNb> Identity Card Number Mod/ Dbtr/ PrvtId/ IdntyCardNb ++++<MplyrIdNb> Employer Id Number Mod/ Dbtr/ PrvtId/ MplyrIdNb ++++<OthrId> Other Id +++++<Id> Id Mod/ Dbtr/ PrvtId/ OthrId/Id +++++<IdTp> Id Number Mod/ Dbtr/ PrvtId/ OthrId/IdTyp ++++<Issr> Issuer Mod/ Dbtr/ PrvtId/ Issr +<DbtrAcct> Debtor Account ++<Id> Id Choice Amongst +++<IBAN> IBAN Mod/ DbtrAcct/ Id/ IBAN +++<BBAN> BBAN Mod/ DbtrAcct/ Id/ BBAN +++<UPIC> UPIC Mod/ DbtrAcct/ Id/ UPIC +++<DmstAcct> Domestic Account ++++<Id> Id Mod/ DbtrAcct/ Id/ DmstAcct/Id ++<Tp> Type Mod/ DbtrAcct/ Tp ++<Ccy> Currency Mod/ DbtrAcct/ Ccy ++<Nm> Name Mod/ DbtrAcct/ Nm

APIN_CP_Us_CP_IncCdtr: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name <Assgnmt> Assignment +<Id> Id Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee BIC of Credit Party +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/ Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Message Name ID Trantype/Insttype +<OrgnlInstrId> Original Instruction ID Transaction Reference Choice amongst +<InstdAmt> Instructed Amount Credit Amount



APIN_CP_Us_CP_IncCdtr: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name +<IntrBkSttlmAmt> Interbank Settlement Amount Credit Amount Choice amongst +<ReqdExctnDt> Requested Execution Date Tran Date +<IntrBkSttlmDt> Interbank Settlement Date Tran Date <Inf> Information +<Cdtr> Creditor Inf/ Cdtr ++<Nm> Name Inf/Cdtr Nm ++<PstlAdr> Postal Address +++<AdrTp> Address Type Mod/ Cdtr/ PstlAdr/ AdrTp ++<AdrLine> Address Line Mod/ Cdtr/ PstlAdr/ AdrLine +++<StrNm> Street Name Mod/ Cdtr/ PstlAdr/ StrNm +++<BldgNb> Building Number Mod/ Cdtr/ PstlAdr/ BldgNb +++<PstCd> Post Code Mod/ Cdtr/ PstlAdr/ PstCd +++<TwnNm> Town Name Mod/ Cdtr/ PstlAdr/ TwnNm +++<CtrySubDvsn> Country SubDivision Mod/ Cdtr/ PstlAdr/CtrySubDvsn +++<Ctry> Country Mod/ Cdtr/ PstlAdr/Ctry ++<Id> Choice amongst +++<OrgId> ++++<BEI> BEI Mod/ Cdtr/Id/ OrgId/ BEI ++++<EANGLN> EANGLN Mod/ Cdtr/Id/ OrgId/ EANGLN ++++<USCHU> CHIPS Universal Id Mod/ Cdtr/Id/ OrgId/ USCHU ++++<DUNS> DUNS Mod/ Cdtr/Id/ OrgId/ DUNS ++++<BkPtyId> Bank Party Id Mod/ Cdtr/Id/ OrgId/ BkPtyId ++++<TaxIdNb> Tax Id Number Mod/ Cdtr/Id/ OrgId/ TaxIdNb ++++<PrtryId> Proprietary Id +++++<Id> Id Mod/ Cdtr/Id/ OrgId/ PrtryId/Id +++++<Issr> Issuer Mod/ Cdtr/Id/ OrgId/PrtryId/Issr +++<PrvtId> Private Id Choice Amongst ++++<DrvrsLicNb> Drivers License Number Mod/ Cdtr/ PrvtId/DrvrsLicNb ++++<SclSctyNb> Social Security Number Mod/ Cdtr/ PrvtId/ SclSctyNb ++++<AlnRegnNb> Alien Registration Number Mod/ Cdtr/ PrvtId/ AlnRegnNb ++++<PsptNb> Passport Number Mod/ Cdtr/ PrvtId/ PsptNb ++++<TaxIdNb> Tax Id Number Mod/ Cdtr/ PrvtId/ TaxIdNb ++++<IdntyCardNb> Identity Card Number Mod/ Cdtr/ PrvtId/ IdntyCardNb ++++<MplyrIdNb> Employer Id Number Mod/ Cdtr/ PrvtId/MplyrIdNb ++++<OthrId> Other Id +++++<Id> Id Mod/ Cdtr/ PrvtId/ OthrId/Id +++++<IdTp> Id Number Mod/ Cdtr/ PrvtId/ OthrId/IdTyp



XML Field Tag XML Tag Description SI Field Name ++++<Issr> Issuer Mod/ Cdtr/ PrvtId/Issr +<CdtrAcct> Debtor Account

APIN_CP_Us_CP_IncCdtr: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name ++<Id> Id Choice Amongst +++<IBAN> IBAN Mod/ CdtrAcct/ Id/IBAN +++<BBAN> BBAN Mod/ CdtrAcct/ Id/BBAN +++<UPIC> UPIC Mod/ CdtrAcct/ Id/UPIC +++<DmstAcct> Domestic Account ++++<Id> Id Mod/ CdtrAcct/Id/ DmstAcct/Id ++<Tp> Type Mod/ CdtrAcct/ Tp ++<Ccy> Currency Mod/ CdtrAcct/ Ccy ++<Nm> Name Mod/ CdtrAcct/ Nm

APIN_CP_Us_CP_IncInfo: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name <Assgnmt> Assignment +<Id> Id Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee BIC of Credit Party +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/ Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Message Name ID Trantype/Insttype +<OrgnlInstrId> Original Instruction ID Transaction Reference Choice amongst +<InstdAmt> Instructed Amount Credit Amount +<IntrBkSttlmAmt> Interbank Settlement Amount Credit Amount Choice amongst +<ReqdExctnDt> Requested Execution Date Tran Date +<IntrBkSttlmDt> Interbank Settlement Date Tran Date <Inf> Information +<RmtChc> Remittance Choice Choice amongst ++<Ustrd> Unstructured Mod/RmtInf/Ustrd ++<Strd> Structured



XML Field Tag XML Tag Description SI Field Name +++<RfrdDocTp> Referred Document Type Mod/RmtInf/Strd/ RfrdDocTp +++<RfrdDocRltdDt> Referred Document Related Date Mod/RmtInf/Strd/ RfrdDocRltdDt +++<RfrdDocAmt Referred Document Amount Mod/RmtInf/Strd/ RfrdDocAmt Choice amongst ++++<DuePyblAmt> Due Payable Amount Mod/RmtInf/Strd/

APIN_CP_Us_CP_IncInfo: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name RfrdDocAmt/DuePyblAmt ++++<DscntApldAmt> Discount Applied Amount Mod/RmtInf/Strd/

++++<RmtdAmt> Remitted Amount Mod/RmtInf/Strd/ ++++<CdtNoteAmt> Credit Note Amount Mod/RmtInf/Strd/

++++<TaxAmt> Tax Amount Mod/RmtInf/Strd/ +++<DocRefNb> Document Reference Number Mod/RmtInf/Strd/DocRefNb

+++<CdtrRef> Creditor Reference Mod/RmtInf/Strd/CdtrRef +++<Invcr> Invoicer ++++<Nm> Name Mod/RmtInf /Strd/Invcr/Nm ++++<PstlAdr> Postal Address +++++<AdrTp> Address Type Mod/RmtInf /

+++++<AdrLine> Address Line Mod/RmtInf / +++++<StrNm> Street Name Mod/RmtInf /

+++++<BldgNb> Building Number Mod/RmtInf / +++++<PstCd> Post Code Mod/RmtInf /

+++++<TwnNm> Town Name Mod/RmtInf / +++++<CtrySubDvsn> Country SubDivision Mod/RmtInf +++++<Ctry> Country Mod/RmtInf / Strd/Invcr/

++++<Id> Id Choice amongst +++++<OrgId> Organization Id ++++++<BEI> BEI Mod/RmtInf /

++++++<EANGLN> EANGLN Mod/RmtInf /

++++++<USCHU> CHIPS Universal Id Mod/RmtInf /

++++++<DUNS> DUNS Mod/RmtInf ++++++<BkPtyId> Bank Party Id Mod/RmtInf /

Strd/Invcr/Id/OrgId/BkPtyId ++++++<TaxIdNb> Tax Id Number Mod/RmtInf/ Strd/Invcr/Id/

OrgId/TaxIdNb ++++++<PrtryId> Proprietary Id



XML Field Tag XML Tag Description SI Field Name +++++++<Id> Id Mod/RmtInf/ Strd/Invcr/Id/

+++++++<Issr> Issuer Mod/RmtInf/ Strd/Invcr/Id/

+++++<PrvtId> Private Id Choice Amongst ++++++<DrvrsLicNb> Drivers License Number Mod/RmtInf/ Strd/Invcr/Id/

PrvtId/DrvrsLicNb

APIN_CP_Us_CP_IncInfo: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name ++++++<SclSctyNb> Social Security Number Mod/RmtInf/ Strd/Invcr/Id/

PrvtId/SclSctyNb ++++++<AlnRegnNb> Alien Registration Number Mod/RmtInf/ Strd/Invcr/Id/

PrvtId/AlnRegnNb ++++++<PsptNb> Passport Number Mod/RmtInf/ Strd/Invcr/Id/

++++++<TaxIdNb> Tax Id Number Mod/RmtInf/ Strd/Invcr/Id/

++++++<IdntyCardNb> Identity Card Number Mod/RmtInf/ Strd/Invcr/Id/

++++++<MplyrIdNb> Employer Id Number Mod/RmtInf/ Strd/Invcr/Id/

++++++<OthrId> Other Id +++++++<Id> Id Mod/RmtInf Strd//Invcr/Id/

+++++++<IdTp> Id Number Mod/RmtInf/ Strd/Invcr/Id/

++++++<Issr> Issuer Mod/RmtInf/ Strd/Invcr/Id/ +++<Invcee> Invoicee

++++<Nm> Name Mod/RmtInf / Strd/Invcee/Nm ++++<PstlAdr> Postal Address +++++<AdrTp> Address Type Mod/RmtInf /

++++<AdrLine> Address Line Mod/RmtInf /

+++++<StrNm> Street Name Mod/RmtInf +++++<BldgNb> Building Number Mod/RmtInf /

+++++<PstCd> Post Code Mod/RmtInf / +++++<TwnNm> Town Name Mod/RmtInf /

Strd/Invcee/PstlAdr/TwnNm +++++<CtrySubDvsn> Country SubDivision Mod/RmtInf /

Strd/Invcee/PstlAdr/CtrySubDvsn



XML Field Tag XML Tag Description SI Field Name +++++<Ctry> Country Mod/RmtInf /

++++<Id> Id Choice amongst +++++<OrgId> Organization Id ++++++<BEI> BEI Mod/RmtInf /

++++++<EANGLN> EANGLN Mod/RmtInf /

++++++<USCHU> CHIPS Universal Id Mod/RmtInf /

++++++<DUNS> DUNS Mod/RmtInf /

++++++<BkPtyId> Bank Party Id Mod/RmtInf /

APIN_CP_Us_CP_IncInfo: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name Strd/Invcee/Id/OrgId/BkPtyId

++++++<TaxIdNb> Tax Id Number Mod/RmtInf/ Strd/Invcee/Id/OrgId/TaxIdNb

++++++<PrtryId> Proprietary Id +++++++<Id> Id Mod/RmtInf/

Strd/Invcee/Id/OrgId/PrtyId/Id +++++++<Issr> Issuer Mod/RmtInf/

Strd/Invcee/Id/OrgId/PrtyId/Issr +++++<PrvtId> Private Id Choice Amongst ++++++<DrvrsLicNb> Drivers License Number Mod/RmtInf/

Strd/Invcee/Id/PrvtId/DrvrsLicNb ++++++<SclSctyNb> Social Security Number Mod/RmtInf/

Strd/Invcee/Id/PrvtId/SclSctyNb ++++++<AlnRegnNb> Alien Registration Number Mod/RmtInf/ Strd/Invcee/Id/

++++++<PsptNb> Passport Number Mod/RmtInf/ Strd/Invcee/Id/

++++++<TaxIdNb> Tax Id Number Mod/RmtInf/ Strd/Invcee/Id/

++++++<IdntyCardNb> Identity Card Number Mod/RmtInf/ Strd/Invcee/Id/

PrvtId/IdntyCardNb



XML Field Tag XML Tag Description SI Field Name ++++++<MplyrIdNb> Employer Id Number Mod/RmtInf/ Strd/Invcee/Id/

PrvtId/MplyrIdNb

++++++<OthrId> Other Id +++++++<Id> Id Mod/RmtInf/ Strd/Invcee/Id/

+++++++<IdTp> Id Number Mod/RmtInf/ Strd/Invcee/Id/

++++++<Issr> Issuer Mod/RmtInf/ Strd/Invcee/Id/ +<SndrToRcvrInf> Sender To Receiver Information Mod/SndrToRcvInf

APIN_IP_Us_IP: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name <Assgnmt> Assignment +<Id> Id Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee BIC of Inquiry Party +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/ Case ID Case/Id +<Cretr> Case Creator Case/Cretr

APIN_IP_Us_IP: AdditionalPaymentInformation camt.028.001.02 XML Field Tag XML Tag Description SI Field Name +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Message Name ID Trantype/Insttype +<OrgnlInstrId> Original Instruction ID Transaction Reference Choice amongst +<InstdAmt> Instructed Amount Credit Amount +<IntrBkSttlmAmt> Interbank Settlement Amount Credit Amount Choice amongst +<ReqdExctnDt> Requested Execution Date Tran Date +<IntrBkSttlmDt> Interbank Settlement Date Tran Date <Inf> Information (allow all fields of <Inf> block to

be



ROIN ResolutionOfInvestigation ROIN_IP_Us_IP_CNCL: ResolutionOfInvestigation camt.029 XML Field Tag Field name SI Field Name <Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Inquirer BIC +<CreDtTm> Create Date/Time Create time of message <RslvdCase> Resolved Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<Conf> InvestigationExecution

CNCL

+<RtrInf> Return Information ++<RtrdIntrBkSttlmAmt> Returned Interbank Settlement

Amount (Required field, must be entered by

++<IntrBkSttlmDt> Interbank Settlement Date (Required field, must be entered

by

++<ClrChanl> Clearing Channel

ROIN_IP_Us_IP_IncBkPd: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name <Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id

ROIN_IP_Us_IP_IncBkPd : ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name +<Assgnr> Assigner Our BIC +<Assgne> Assignee Inquirer BIC +<CreDtTm> Create Date/Time Create time of message <RslvdCase> Resolved Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<RjctdMod> Rejected Modification UM09 or UM10



ROIN_IP_Us_IP_INFO: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Inquirer BIC +<CreDtTm> Create Date/Time Create time of message <RslvdCase> Resolved Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<Conf> Confirmation INFO

ROIN_IP_Us_IP_MODI: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Inquirer BIC +<CreDtTm> Create Date/Time Create time of message <RslvdCase> Resolved Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<Conf> Confirmation MODI

ROIN_IP_Us_IP_RejIncDbtr: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Inquirer BIC +<CreDtTm> Create Date/Time Create time of message <RslvdCase> Resolved Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<RjctdMod> Rejected Modification UM07 or UM08



ROIN_IP_Us_IP_RejIncCdtr: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name


ROIN_IP_Us_IP_RejIncDate: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name


ROIN_IP_Us_IP_IncAmt: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Inquirer BIC +<CreDtTm> Create Date/Time Create time of message <RslvdCase> Resolved Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<RjctdMod> Rejected Modification UM06



ROIN_IP_Us_IP_RejIncChgs: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name


ROIN_IP_Us_IP_IncInfo: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Inquirer BIC +<CreDtTm> Create Date/Time Create time of message <RslvdCase> Resolved Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<RjctdMod> Rejected Modification UM01, UM02, UM03, UM11, UM15,

UM18, or UM19

ROIN_IP_Us_IP_RejAmBene: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name




ROIN_IP_Us_IP_Reject: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Inquirer BIC +<CreDtTm> Create Date/Time Create time of message <RslvdCase> Resolved Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<RjctdMod> Rejected Modification

ROIN_IP_Us_IP_MWFW: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Inquiry Party BIC +<CreDtTm> Create Date/Time Create time of message <RslvdCase> Resolved Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<Conf> Confirmation MWFW

ROIN_RB_Us_RB_CWFW: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Receiving Bank BIC +<CreDtTm> Create Date/Time Create time of message <RslvdCase> Resolved Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status



XML Field Tag XML Tag Description SI Field Name +<Conf> Confirmation CWFW

ROIN_CP_Us_CP_CWFW: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Credit Party BIC +<CreDtTm> Create Date/Time Create time of message <RslvdCase> Resolved Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator No <Sts> Status +<Conf> Confirmation MCWFW

ROIN_IP_Us_RB_CWFW: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Receiving Bank BIC +<CreDtTm> Create Date/Time Create time of message <RslvdCase> Resolved Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<Conf> Confirmation CWFW

ROIN_IP_Us_CP_CWFW: ResolutionOfInvestigation camt.029.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Credit Party BIC +<CreDtTm> Create Date/Time Create time of message <RslvdCase> Resolved Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr



XML Field Tag XML Tag Description SI Field Name +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<Conf> Confirmation CWFW

ROIN_IP_Us_IP_Last: ResolutionOfInvestigation camt.029 XML Field Tag Field name SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Inquirer BIC +<CreDtTm> Create Date/Time Create time of message <RslvdCase> Resolved Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<RjctdCxl> Rejected Cancellation ++<RsnCd> Reason Code Last Reason Code, drop down

options: CUST, AGNT, LEGL ++<Reason> Reason (text)

NOCA NotificationOfCaseAssignment NOCA_IP_Us_RB_FTHI: NotificationOfCaseAssignment MX camt.030.001.02 XML Field Tag XML Tag Description SI Field Name

<Hdr> Header +<Id> ID of Report Our Exception Case Id +<Fr> From Our BIC +<To> To Inquirer BIC +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Receiving Bank +<CreDtTm> Create Date/Time System Date/Time <Ntfctn> Notification +<Justfn> Case Forward Notification Code FTHI



NOCA_IP_Us_CP_DTAU: NotificationOfCaseAssignment MX camt.030.001.02 XML Field Tag XML Tag Description SI Field Name

<Hdr> Header +<Id> ID of Report Our Exception Case Id +<Fr> From Our BIC +<To> To Inquirer BIC +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee BIC of Credit Party +<CreDtTm> Create Date/Time System Date/Time <Ntfctn> Notification +<Justfn> Case Forward Notification Code DTAU

NOCA_IP: NotificationOfCaseAssignment MX camt.030 XML Field Tag XML Tag Description SI Field Name

<Hdr> Header +<Id> ID of Report Our Exception Case Id +<Fr> From Our BIC +<To> To Inquirer BIC +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Assgnmt> Assignment +<Id> Assignment ID LastAssgnmt/Id +<Assgnr> Assigner LastAssgnmt/Assgnr +<Assgne> Assignee LastAssgnmt/Assgne +<CreDtTm> Create Date/Time LastAssgnmt/CredtTm <Ntfctn> Notification +<Justfn> Case Forward Notification Code Ntfctn/Justfn from received msg

NOCA_IP_Us_RB_CANC: NotificationOfCaseAssignment MX camt.030.001.02 XML Field Tag XML Tag Description SI Field Name

<Hdr> Header +<Id> ID of Report Our Exception Case Id



XML Field Tag XML Tag Description SI Field Name +<Fr> From Our BIC

NOCA_IP_Us_RB_CA NC:

MX camt.030.001.02 XML Field Tag XML Tag Description SI Field Name

+<To> To Inquirer BIC +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Receiving Bank +<CreDtTm> Create Date/Time System Date/Time <Ntfctn> Notification +<Justfn> Case Forward Notification Code CANC

NOCA_IP_Us_RB_MODI: NotificationOfCaseAssignment MX camt.030.001.02 XML Field Tag XML Tag Description SI Field Name

<Hdr> Header +<Id> ID of Report Our Exception Case Id +<Fr> From Our BIC +<To> To Inquirer BIC +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Receiving Bank +<CreDtTm> Create Date/Time System Date/Time <Ntfctn> Notification +<Justfn> Case Forward Notification Code MODI

NOCA_IP_Us_RB_CNCL: NotificationOfCaseAssignment MX camt.030.001.02 XML Field Tag XML Tag Description SI Field Name

<Hdr> Header



XML Field Tag XML Tag Description SI Field Name +<Id> ID of Report Our Exception Case Id +<Fr> From Our BIC +<To> To Inquirer BIC +<CreDtTm> Create Date/Time System Date/Time <Case> Case

NOCA_IP_Us_RB_CNCL: NotificationOfCaseAssignment MX camt.030.001.02 XML Field Tag XML Tag Description SI Field Name

+<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Receiving Bank +<CreDtTm> Create Date/Time System Date/Time <Ntfctn> Notification +<Justfn> Case Forward Notification Code CNCL

NOCA_IP_Us_CP_MODI: NotificationOfCaseAssignment MX camt.030.001.02 XML Field Tag XML Tag Description SI Field Name

<Hdr> Header +<Id> ID of Report Our Exception Case Id +<Fr> From Our BIC +<To> To Inquirer BIC +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Credit Party +<CreDtTm> Create Date/Time System Date/Time

<Ntfctn> Notification

+<Justfn> Case Forward Notification Code MODI



NOCA_IP_IP_Us_FIAG: NotificationOfCaseAssignment MX camt.030.001.02 XML Field Tag XML Tag Description SI Field Name

<Hdr> Header +<Id> ID of Report Our Exception Case Id +<Fr> From Our BIC +<To> To Inquirer BIC +<CreDtTm> Create Date/Time System Date/Time <Case> Case

NOCA_IP_IP_Us_FIAG: NotificationOfCaseAssignment MX camt.030.001.02 XML Field Tag XML Tag Description SI Field Name

+<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Inquirer BIC +<Assgne> Assignee Our BIC +<CreDtTm> Create Date/Time System Date/Time <Ntfctn> Notification +<Justfn> Case Forward Notification Code FIAG

NOCA_IP_Us_SB_FTHI: NotificationOfCaseAssignment MX camt.030.001.02 XML Field Tag XML Tag Description SI Field Name

<Hdr> Header +<Id> ID of Report Our Exception Case Id +<Fr> From Our BIC +<To> To Inquirer Party BIC +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Sending Bank +<CreDtTm> Create Date/Time System Date/Time <Ntfctn> Notification +<Justfn> Case Forward Notification Code FTHI



NOCA_IP_Us_DP_FTHI: NotificationOfCaseAssignment MX camt.030.001.02 XML Field Tag XML Tag Description SI Field Name

<Hdr> Header +<Id> ID of Report Our Exception Case Id +<Fr> From Our BIC +<To> To Inquirer BIC +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn

NOCA_IP_Us_DP_FTHI: NotificationOfCaseAssignment M X camt.030.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Debit Party +<CreDtTm> Create Date/Time System Date/Time <Ntfctn> Notification +<Justfn> Case Forward Notification Code FTHI

NOCA_IP_Us_CP_SAIN: NotificationOfCaseAssignment MX camt.030.001.02 XML Field Tag XML Tag Description SI Field Name

<Hdr> Header +<Id> ID of Report Our Exception Case Id +<Fr> From Our BIC +<To> To Inquirer BIC +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Credit Party +<CreDtTm> Create Date/Time System Date/Time <Ntfctn> Notification +<Justfn> Case Forward Notification Code SAIN



RCAS RejectCaseAssignment RCAS_IP_Us_IP_NFND: RejectCaseAssignment camt.031.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Inquirer BIC +<CreDtTm> Create Date/Time System Date/Time <Case> +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn

RCAS_IP_Us_IP_NFND: RejectCaseAssignment camt.031.001.02 XML Field Tag XML Tag Description SI Field Name

<Justfn> +<RjctnRsn> Case Assignment Rejection Code NFND

RCAS_IP_Us_IP_NAUT: RejectCaseAssignment camt.031.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Inquirer BIC +<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Justfn> Justification +<RjctnRsn> Case Assignment Rejection Code NAUT

RCAS_IP_Us_IP_UKNW: RejectCaseAssignment camt.031.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Inquirer BIC +<CreDtTm> Create Date/Time System Date/Time <Case> +<Id> Creator’s Case ID Case/Id



XML Field Tag XML Tag Description SI Field Name +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Justfn> +<RjctnRsn> Case Assignment Rejection Code UKNW

DARQ DebitAuthorisationRequest DARQ_CP_Us_CP_UPAY: DebitAuthorisationRequest camt.037.001.02 XML Field Tag XML Tag Description SI Field Name

<Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee BIC/BEI of Credit Party

DARQ_CP_Us_CP_UPAY: DebitAuthorisationRequest cam t.037.001.02 XML Field Tag XML Tag Description SI Field Name

+<CreDtTm> Create Date/Time System Date/Time <Case> Case +<Id> Creator’s/Assigner’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr <ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Pmt Message Name ID Trantype/Insttype +<OrgnlInstrId> Original Instruction ID Transaction Reference Choice amongst +<InstdAmt> Instructed Amount Credit Amount +<IntrBkSttlmAmt> Settlement Amount Credit Amount Choice amongst +<ReqdExctnDt> Required Execution Date Tran Date +<IntrBkSttlmDt> Settlement Date Tran Date <Dtl> Detail +<CxlRsn> Cancellation Reason UPAY +<AmtToDbt> Amount to Debit Credit Amount +<ValDtToDbt> Value Date to Debit Credit Value Date



CSRP CaseStatusReport CSRP_ IP_UKNW: CaseStatusReport camt.039.001.02 XML Field Tag XML Tag Description SI Field Name

<Hdr> Header +<Id> ID of Report Our Case ID +<Fr> From Our BIC Address +<To> To BIC of Inquiry Party +<CreDtTm> Create Date/Time System Create Date/Time <Case> Case +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<DtTm> DateTime +<CaseSts> Case Status UKNW

CSRP_IP_CLSD: CaseStatusReport camt.039.001.02 XML Field Tag XML Tag Description SI Field Name

<Hdr> Header +<Id> ID of Report Our Exception Case Id +<Fr> From Our BIC

CSRP_IP_CLSD: CaseStat usReport camt.039.001.02 XML Field Tag XML Tag Description SI Field Name

+<To> To BIC of Inquiry Party +<CreDtTm> Create Date/Time System Create Date/Time <Case> Case +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<DtTm> DateTime +<CaseSts> Case Status CLSD

CSRP_IP_INVE: CaseStatusReport camt.039.001.02 XML Field Tag XML Tag Description SI Field Name

<Hdr> Header +<Id> ID of Report Our Exception Case Id +<Fr> From Our BIC +<To> To BIC of Inquiry Party +<CreDtTm> Create Date/Time System Create Date/Time



XML Field Tag XML Tag Description SI Field Name <Case> Case +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<DtTm> DateTime +<CaseSts> Case Status INVE

CSRP_IP_ASGN: CaseStatusReport camt.039.001.02 XML Field Tag XML Tag Description SI Field Name

<Hdr> Header +<Id> ID of Report Our Exception Case Id +<Fr> From Our BIC +<To> To BIC of Inquiry Party +<CreDtTm> Create Date/Time System Create Date/Time <Case> Case +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<DtTm> DateTime +<CaseSts> Case Status ASGN +<Rsn> Reason <NewAssgnmt> New Assignment

CSRP_IP_ASGN: CaseStatusReport camt.039.001.02

XML Field Tag XML Tag Description SI Field Name

+<Id> Id Last Assignment Id +<Assigner> Assigner Last Assigner +<Assignee> Assignee Last Assignee +<CredtTm> Create Date/Time Last Assignment Date/Time

pega advanced e&i rulebooki-rulebook... · pega-uitheme — ui theme rules. pega advanced...

Documents