pega advanced e&i rulebook application

111
Pega Advanced E&I Rulebook Application WORKFLOW DEFINITION AND SPECIFICATION 7.31

Upload: others

Post on 20-Nov-2021

18 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application

WORKFLOW DEFINITION AND SPECIFICATION 7.31

Page 2: Pega Advanced E&I Rulebook Application

© 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 Application

Document: Workflow Definition and Specification

Software Version: 7.31

Updated: February 2018

Page 3: Pega Advanced E&I Rulebook Application

CONTENTS

Executive Summary ....................................................................................... 4

Business Context ............................................................................................. 5

Stepping to the Future… ................................................................................. 5

Functional Requirements - Overview .......................................................... 6

Unique Case Id ................................................................................................. 6

Case Creator..................................................................................................... 6

No-By-Pass Rule ............................................................................................... 6

SWIFTNet Directory Implementation ............................................................. 6

MT/MX Coexistence ......................................................................................... 7

Last Assignment Details .................................................................................. 7

Template Naming Convention........................................................................ 9

Unique Case Creator/Case Id ......................................................................... 9

Functional Requirements by Work Type ................................................... 11

RequestToCancelPayment Message, MX camt.008 .................................... 11

RTMP to APIN Comparison ............................................................................ 31

UnableToApply, MX camt.026....................................................................... 69

ClaimsNonReceipt, MX camt.027 ................................................................. 81

Debit Authorization Response, MX.camt.036 .............................................. 92

Debit Authorization Request, MX.camt.037 ................................................ 94

ResolutionOfInvestigation, MX.camt.029 .................................................... 96

NotificationOfCaseAssignment, MX.camt.030 .......................................... 100

AdditionalPaymentInformation, MX.camt.028 .......................................... 102

RejectCaseAssignment, MX.camt.031 ........................................................ 103

CancelCaseAssignment, MX.camt.032 ....................................................... 104

RequestForDuplicate, MX.camt.033 ........................................................... 105

Duplicate, MX.camt.034 .............................................................................. 107

CaseStatusReportRequest, MX.camt.038 .................................................. 108

CaseStatusReport, MX.camt.039 ................................................................ 111

Page 4: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 4

In an average Payments Operations department, two to five percent of all payments made on any given day result in an inquiry. The 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 has implemented new Exceptions and Investigations messages to support 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 it 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 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 includes missing cover situations.

The activities listed above are supported by the following Case Management messages:

• Resolution Of Investigation

• Notification Of Case Assignment

• Request For Duplicate

• Duplicate

• Reject Investigation

• Cancel Case Assignment

• Case Status Report Request

• Case Status Report

• Debit Authorization Request

• Debit Authorization Response

Executive Summary

Page 5: Pega Advanced E&I Rulebook Application

5 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

TITLE of INTERNAL DOCUMENT – Arial Bold 12

• Additional Payment Information

• Proprietary Format Investigation

SWIFT’s “Message Reference Guide for Exceptions and Investigations 1.2” details workflow requirements for the use of the above messages, which are included in Pega’s Advanced E&I Rulebook Application.

Business Context Pega® has committed to creating a new application–Pega Advanced E&I Rulebook –to enable our customers to use these enhanced workflow rules to improve the efficiency of their operations.

Pega achieved Technical validation on July 23, 2009 for our original SWIFTNet Exceptions and Investigations application. This has been referred to as "certification on the message level." With this validation, the application includes:

• Ability to receive and attach these 16 new XML messages.

• Ability to map fields from these messages to a work object.

• Display of messages in the work object with field tags.

• Creation of all new messages in outgoing correspondence, including all field validation and message validation rules.

• Mapping of work object properties to new messages.

Stepping to the Future… Pega’s approach begins with a defined implementation in the Pega Advanced E&I Rulebook application. Based on their existing implementation, our customers can implement all or some components of the application to rapidly achieve business value.

The Build For Change™ philosophy embraced by Pega in this project is based on a commitment to continuous improvement and self-sufficiency. This project represents an initial step towards evolutionary efficiency and service gains. Business benefits beyond this project will be designed and achieved through follow-on implementations.

Page 6: Pega Advanced E&I Rulebook Application

6 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

TITLE of INTERNAL DOCUMENT – Arial Bold 12

Several new concepts have been introduced to achieve the operational efficiencies intended with the Pega Advanced E&I Rulebook application.

Unique Case Id Additional processing has been added to map the data from the fields <Case> <Id> and <Case><Cretr> of an incoming investigation activity (Request to Cancel Payment, Request to Modify Payment, Unable to Apply, or Claims Non-Receipt), and to include those fields on all messages generated for that case. Pega had previously included functionality to create a unique case id that includes bank identifying information.

From the left side of the work portal, you can also search using the Unique Case ID.

Case Creator The original case creator of an incoming investigations message is a new field that must be saved to the exceptions case, along with that creator’s ID. In some cases, the original assigner will be the case creator, but not always.

No-By-Pass Rule The No-By-Pass Rule states that no party in the payment transaction chain can be skipped when sending E&I messages. The “next party in chain” or “previous party in chain” is determined by evaluating the payment direction, debit account type, and credit account type fields in the payment transaction record associated with a particular case. Because each bank’s payment system and underlying data model are unique, each bank will need to determine their place in the payment chain using different logic.

SWIFTNet Directory Implementation The SWIFTNet Services directory, found on the SWIFT.com website, includes the BICs of all banks who have registered for E&I, and who have indicated they are “operational,” meaning ready to send and receive XML messages.

This file will be used to update the PCB_ACCOUNTS table, specifically the “E&I Enabled” flag and the DistinguishedName field. Customers will need to create a batch job to update their customer records from this file.

During correspondence processing, the system will read the “E&I Enabled” flag to determine if the recipient can receive E&I messages. If the flag is set to “N,” the system will convert the indicated message to the appropriate MT message for operator review/update.

Functional Requirements - Overview

Page 7: Pega Advanced E&I Rulebook Application

7 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

TITLE of INTERNAL DOCUMENT – Arial Bold 12

If the flag is set to “Y,” the system will prepare the XML message with the contents of the DistinguishedName field copied to the XML header.

MT/MX Coexistence The Pega Advanced E&I Rulebook application will use the following table to determine which FIN template to present to the operator if the recipient is not E&I enabled. The operator will also be able to select a Local Action to go to Step-by-Step processing if the recipient’s correspondence preference is not SWIFT.

MX Message Name MT Equivalence RequestToCancelPaymentV02 MTn92 RequestToModifyPaymentV02 MTn95 UnableToApplyV02 MTn95 ClaimNonReceiptV02 MTn95 CancelCaseAssignment MTn95 CaseStatusReportRequest MTn95 DebitAuthorisationRequestV02 MTn95 RequestForDuplicateV02 MTn95 AdditionalPaymentInformationV02 MTn96 CaseStatusReportV02 MTn96 DebitAuthorisationResponse MTn96 NotificationOfCaseAssignmentV02 MTn96 RejectCaseAssignmentV02 MTn96 ResolutionOfInvestigationV02 MTn96 DuplicateV02 ProprietaryFormatInvestigation

Last Assignment Details Because the E&I rules require communicating current or most recent assignment information at various points in the life of a case, the system adds four properties at case creation. These properties will be populated as follows, based on how the case was originated:

Properties Received Via = SWIFTNet

Manually Opened Opened via other message

LastAssgnmtId Assgnmt/Id Our Case ID Our Case ID LastAssignr Assgnmt/Assgnr Our BIC Our BIC LastAssigne Assgnmt/Assgne Our BIC Our BIC LastAssgnmtCreDtTm Assgnmt/CreDtTm System Date/Time System Date/Time

Page 8: Pega Advanced E&I Rulebook Application

8 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

TITLE of INTERNAL DOCUMENT – Arial Bold 12

Whenever any of these SWIFTNet messages shown below are sent, the system will update the Last Assignment Id, Last Assigner, Last Assignee, and Last Assignment Date/Time properties based on those fields in the message.

• Request To Modify Payment

• Request To Cancel Payment

• Unable To Apply

• Claims Non Receipt

• Resolution Of Investigation

• Request For Duplicate

• Duplicate

• Reject Investigation

• Cancel Case Assignment

• Debit Authorization Request

• Debit Authorization Response

• Additional Payment Information

Whenever any of the following messages are received and attached as a single match to an existing case, the system will update the Last Assignment Id, Last Assigner, Last Assignee and Last Assignment Date/Time properties based on those fields in the message.

• Resolution Of Investigation

• Notification of Case Assignment

• Request For Duplicate

• Duplicate

• Reject Investigation

• Cancel Case Assignment

• Debit Authorization Request

• Debit Authorization Response

• Additional Payment Information

Page 9: Pega Advanced E&I Rulebook Application

9 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

TITLE of INTERNAL DOCUMENT – Arial Bold 12

Template Naming Convention Template names consist of four or five parts as follows:

• XML message name abbreviation (see table below)

• Abbreviation for party to whom message is sent

• Assigner of the message

• Assignee of the message

• Code or variation, if applicable.

MX 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 Debit Authorization Request DARQ Debit Authorization Response DARS Additional Payment Information APIN Proprietary Format Investigation PFIN

For example, DARQ_CP_Us_CP means the Debit Authorization Request message sent to the Credit Party, where Us is the Assigner and the Credit Party is the Assignee.

NOCA_IP_Us_CP_DAUT is a NotificationOfCaseAssignment message to the Inquiry Party, with Us as the Assigner, the Credit Party as the Assignee, and the code DAUT in the <Justfn> (Case forwarding notification code) field.

Unique Case Creator/Case Id For all incoming XML messages, the system will check if there are any exception cases in the system with the same Case Creator/Case Id combination.

Page 10: Pega Advanced E&I Rulebook Application

10 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

TITLE of INTERNAL DOCUMENT – Arial Bold 12

If the system finds an exception case with the same Case Creator/Case Id combination, attach the message to the existing case.

If the system does not find a matching case, and if the XML message is camt.007, camt.008, camt.026, or camt.027, the system will create a new exception case. The flow continues based on the actual message received. Note that searching the TRN database to determine whether the underlying payment transaction is in the payment database occurs with the duplicate search functionality in that specific work type.

If the system does not find an existing case, and if the XML message is not camt.007, camt.008, camt.026, or camt.027, the system will open a new miscellaneous exception case, and send a RejectCaseAssignment message (camt.031) to the Requestor/Inquiry Party of the message.

Page 11: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 11 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

Work types describe the high level business flows for the specific Investigation Activities. Processing flows for the Case Management messages that will make up this application are also included here.

RequestToCancelPayment Message, MX camt.008 1. System receives XML message RequestToCancelPayment, MX camt.008.

2. System creates M- case with the following mapping from message. All fields should be mapped into comparably named fields in the work area of the M- case, so that the operator reviewing the message can review with tag/data pairs rather than raw message. (SI:Common:CreateMsgCase)

RequestToCancelPayment MX camt.008.002.02 MX field tag MX Field name Msg Case Property

Name Exc

Case Map to Exc Case

Work Info Section

<Assgnmt> Assignment +<Id> Identification Assgnmt/Id ** +<Assgnr> Assigner Assgnmt/Assgnr ** +<Assgne> Assignee Assignmt/Assgne ** +<CreDtTm> Create Date/Time Assignmt/CreDtTm ** <Case> Case ** +<Id> Creator’s/ Case ID Case/Id ** +<Cretr> Case Creator Case/Cretr ** +<ReopCaseIndct n> Case Reopen Indicator Case/ReopCaseIndctn **

<Undrlyg> Underlying

+<OrgnlMsgNmId

>

Original Message Name ID

Undrlyg/OrgnlMsgNm Id *This will default from the payment txn, not the message

+<OrgnlInstrId> Original Instruction ID Undrlyg/OrgnlInstrId Transaction Reference

Choice amongst +<InstdAmt> Instructed Amount Undrlyg/CcyAmt/Ccy and

Undrlyg/InstdAmt/ Value InquiryAmount

+<IntrBkSttlmAm t> Interbank Settlement Amount

Undrlyg/CcyAmt/Ccy and Undrlyg/IntrBk SttlmAmt/ Value

InquiryAmount

Choice amongst

Functional Requirements by Work Type

Page 12: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 12 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

+<ReqdExctnDt> Requested Execution Date

Underlyg/Reqd ExctnDt Transaction Date

+<IntrBkSttlmDt

Interbank Settlement Date

Undrlyg/IntrBk SttlmtDt Transaction Date

<Justfn> Justification

+<CxlRsn> Cancellation Reason Justfn/CxlRsn **

+<AmtToDbt> Amount to Debit Justfn/AmtToDbt **

+<ValDtToDbt> Value Date To Debit Justrn/ValDtToDbt **

(Header) characters 5 and

Branch

(Header) Requestor Inquirer BIC

(Header) Date Inquiry Date

Default SWIFT Net for Received Via field

Note: **Use same property names for Exception case as Message case.

3. System searches case database to determine if case already exists, using existing case search criteria:

a. If multiple matching cases found, route to exception workbasket for operator intervention; (SI:Common:MultipleCasesFound)

b. If one matching case found, attach M- case to existing exception case and close M- case (Resolved-Attached); (SI:Common:AttachMessage)

c. If no matching case found, jump to Step 4.

4. System creates an exception case. (SI:Common:DetermineRTMPWorkType)

a. If more than one block of the Modification Block contains data, and any of those blocks are

<ReqdExctnDt>, <ValDt>, <IntrBkSttldAmt>, <Dbtr>, <DbtrAcct>, <IntrmySttlmAgt>,<LastSttlmAgt>, <BnfcryInstnAcct>, <Cdtr>, <CdtrAcct>, or <DtlsOfChrgs>, open Incorrect Payment case type.

b. If more than one block of the Modification Block contains data, and none of those blocks are

Page 13: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 13 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

<ReqdExctnDt>, <ValDt>, <IntrBkSttldAmt>, <Dbtr>, <DbtrAcct>, <IntrmySttlmAgt>,<LastSttlmAgt>, <BnfcryInstnAcct>, <Cdtr>, <CdtrAcct>, or <DtlsOfChrgs>, open Incorrect Information case type.

c. If only one block of the Modification Block contains data, and that block is either <RltdRef>,<BkOprCd>, <InstrCd>, <PmtSchme>, <RmtInf>, <Purp>, <InstrForFnlAgt>, or <SndrToRcvrInf>, open Incorrect Information case type.

d. If the only element in the Modification Block that contains data is <IntrBkSttldAmt>, open Incorrect Amount case type.

e. If the only element in the Modification Block that contains data is <ReqdExctnDt> or <ValDt>, open Incorrect Date case type.

f. If the only element in the Modification Block that contains data is <Dbtr> or <DbtrAcct>, open Incorrect Debit Account case type.

g. If the only element in the Modification Block that contains data is <IntrmySttlmAgt> or <LastSttlmAgt>, open Incorrect Bank Paid case type.

h. If the only element in the Modification Block that contains data is <BnfcryInstnAcct>, open Amend Bene case type.

i. If the only element in the Modification Block that contains data is <Cdtr> or <CdtrAcct>, open Incorrect Credit Account case type.

j. If the only element in the Modification Block that contains data is <DtlsOfChrgs>, open Incorrect Charges case type.

5. System auto populates exception case with details from RTMP message (see table above)

6. System checks transaction database using case details

a. If multiple matching payment transactions are found, route to exceptions workbasket for operator intervention; (SI:Common:TransferToWorkBasket) if operator can resolve the multiple transactions and attach and update one transaction to the case, return to the flow at Step 7; (SI:Common:EnrichCasewithTxn)

b. If no matching payment transaction is found, route to exceptions workbasket. (SI:Common:TransferToWorkBasket) Exceptions operator manually checks search portal. Operator clicks “research complete”:

i. If no matching transaction is found manually, System creates RejectCaseAssignment Message, RCAS_IP_Us_IP_NFND to Inquirer and closes the case (Resolved-Rejected) (SI:Common:TxnSearchNoMatch)

Page 14: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 14 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

RCAS_IP_Us_IP_NFND: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case <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 <Justfn> +<RjctnRsn> Case Assignment Rejection

Code NFND

ii. If a matching transaction is found manually, attach and update the case, return to the flow in Step 7. (SI:Common:EnrichCasewithTxn)

c. If a matching payment transaction is found, auto-populate transaction details, attach transaction to case. (SI:Common:EnrichCasewithTxn)

7. Case has matched and updated payment transaction:

a. If Received Via field is equal to SWIFTNet, and if SwiftNetCaseAssignmentAssgne is not our BIC, then case may have been received in error. System sends RejectCaseAssignment

message, RCAS_IP_Us_IP_NAUT to Inquirer in background as follows: (SI:Common:RejectCaseAssignmentNAUT); resolve case with status Resolved-Rejected.

RCAS_IP_Us_IP_NAUT: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case <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

Page 15: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 15 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

b. If Received Via field is equal to SWIFTNet and if the Inquiry Party is not either the debit party or the Sending Bank, the sender of RTCP may have violated no-by-pass rule. System sends RejectCaseAssignment camt.031 message, RCAS_IP_Us_IP_NAUT, to Inquirer in background as follows: (SI:Common:RejectCaseAssignmentNAUT); resolve case with status Resolved-Rejected.

RCAS_IP_Us_IP_NAUT: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case <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 <Justfn> +<RjctnRsn> Case Assignment Rejection

Code NAUT

8. If exception case does not contain data for these three properties, add this data in the background. Fields should not be modifiable by an operator. (SI:Common:AddCaseCreatorFields)

a. Case/Id: case id

b. Case/Cretr: our BIC Id

c. Case/ReopCaseIndcn: False

d. If Received Via field is not SWIFTNet, present operator with flow action “Enter additional case details”; include a Step-By-Step local action on this assignment. (SI:Common:RTMPAddCaseDetails)

e. If case type equals Incorrect Date, present operator with option, “enter date that needs to be modified”

i. Requested Execution Date (<ReqdExctnDt>)

ii. Value Date (<ValDt>)

f. If case type equals Incorrect Debit Account, present operator with option, “enter debtor or debit account information that needs to be corrected.” Show all subfields of <Dbtr> and <DbtrAcct> as per XML message.

Page 16: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 16 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

i. Debtor details (<Dbtr>)

ii. Debit Account details <DbtrAcct>

g. If case type equals Incorrect Bank Paid, present operator with option, “enter information for bank that needs to be corrected.” Show all subfields of <IntrmySttlmAgt> and <LastSttlmAgt> as per XML message.

i. Intermediary Settlement Agent <IntrmySttlmAgt>

ii. Last Settlement Agent <LastSttlmAgt>

h. If case type equals Amend Bene case type, peresnt operator with option, “enter corrected Beneficiary information.”

i. Beneficiary Institution Account <BenfcryInstnAcct>

i. If case type equals Incorrect Credit Account, present operator with option, “enter creditor or credit account information that needs to be corrected.” Show all subfields of <Cdtr> and

<CdtrAcct> as per XML message.

i. Creditor details (<Cdtr>)

ii. Credit Account details <CdtrAcct>

j. If case type equals Incorrect Charges, present operator with option, “enter correct charges information (<DtlsOfChrgs>.” Operator should select from a drop down list as follows:

i. BEN, BorneByCreditor, All charges are to be borne by the creditor

ii. OUR, BorneByDebtor, All charges are to be borne by the debtor

iii. SHA, Shared, Charges on the sender’s side are to be borne by the debtor; charges on the receiver’s side are to be borne by the creditor.

k. If case type equals Incorrect Amount, present operator with option, “enter correct amount:”

i. Interbank Settled Amount <IntrBkSttldAmt>

ii. Default Credit Amount Currency as a non-editable field

iii. Amount entered must be less than Credit Amount from payment transaction. If the entered amount is equal to or greater than Credit Amount, error message should be “amount entered must be less than payment amount.”

l. If case type equals Incorrect Information, present operator with option, “enter information that needs to be corrected.” Show all subfields as per XML message.

i. Related Reference <RltdRef>

ii. Bank Operation Code <BkOprCd>; Drop down options: 1. SPAY, SWIFTPay, processed according to SWIFTPay Service Level

Page 17: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 17 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

2. SSTD, Standard, processed according to Standard Service Level. iii. Instruction Code <InstrCd> Drop down options:

1. PBEN, PayTheBeneficiary, Creditor to be paid only after verification of identity.

2. TFRO, TimeFrom, Payment instruction will be valid from the date and time stipulated.

3. TTIL, TimeTill, Payment instruction is valid until the date and time stipulated; otherwise it will be rejected.

iv. Payment Scheme, <PmtSchme> v. Remittance Information <RmtInf> vi. Purpose Code (Proprietary, <Prtry>, or drop down Code <Cd>)

1. ADVA, AdvancePayment, Transaction is an advance payment. 2. AGRT, AgriculturalTransfer, Transaction is related to the agricultural

domain. 3. ALMY, AlimonyPayment, Transaction is the payment of alimony. 4. BECH, ChildBenefit, Transaction is related to a payment made to assist

parent/guardian to maintain child. 5. BENE, UnemploymentDisabilityBenefit, Transaction is related to a

payment to a person who is unemployed/disabled. 6. BONU, BonusPayment, Transaction is related to payment of a bonus. 7. CASH, CashManagementTransfer, Transaction is a general cash

management instruction. 8. CBFF, CapitalBuilding, Transaction is related to capital building fringe

fortune, i.e. capital building for retirement. 9. CHAR, CharityPayment, Transaction is a payment for charity reasons.

10. CMDT, CommodityTransfer, Transaction is payment of commodities. 11. COLL, CollectionPayment, Transaction is a collection of funds initiated

via a credit transfer or direct debit. 12. COMC, CommercialPayment, Transaction is related to a payment of

commercial credit or debit. 13. COMM, Commission, Transaction is payment of commission. 14. COMT, ConsumerThirdPartyConsolidatedPayment, Transaction is a

payment used by a third party who can collect funds to pay on behalf of consumers

15. COST, Costs, Transaction is related to payment of costs. 16. CPYR, Copyright, Transaction is payment of copyright. 17. DBTC, DebitCollectionPayment, Collection of funds initiated via a debit

transfer. 18. DIVI, Dividend, Transaction is payment of dividends. 19. FREX, ForeignExchange, Transaction is related to a foreign exchange

operation. 20. GDDS, PurchaseSaleOfGoods, Transaction is related to purchase and

sale of goods. 21. GOVT, GovernmentPayment, Transaction is a payment to or from a

government department. 22. HEDG, Hedging, Transaction is related to a hedging operation. 23. IHRP, InstallmentHirePurchaseAgreement, Transaction is payment for

an installment/hire-purchase agreement. 24. INSU, InsurancePremium, Transaction is payment of an insurance

premium. 25. INTC, IntraCompanyPayment, Transaction is an intra-company

payment.

Page 18: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 18 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

26. INTE, Interest, Transaction is payment of interest. 27. LICF, LicenseFee, Transaction is payment of a license fee. 28. LOAN, Loan, Transaction is related to transfer of loan to borrower. 29. LOAR, LoanRepayment, Transaction is related to repayment of loan to

lender. 30. NETT, Netting, Transaction is related to a netting operation. 31. PAYR, Payroll, Transaction is related to the payment of payroll. 32. PENS, PensionPayment, Transaction is the payment of pension.

vii. Instruction For Final Agent, <InstrForFnlAgt>, Proprietary, <Prtry>, or drop down Code <Cd>)

1. CHQB, PayCreditorBy Cheque, Creditor must be paid by cheque. 2. HOLD, HoldCashForCreditor, Hold for Creditor, who will call, pay on

identification 3. PHOB, PhoneBeneficiary, Advise/contact creditor/claimant by phone 4. TELB, Telecom, Advise/contact creditor/claimant by most efficient

means of telecommunication. viii. Sender To Receiver Information, <SndrToRcvInf>

m. If case type equals Incorrect Payment, present operator with option, “enter information that needs to be corrected.” Show all Modification blocks and subfields as per RequestToModifyPayment XML message.

i. Related Reference <RltdRef> ii. Bank Operation Code<BkOprCd>

See h ii above for drop down options

iii. Instruction Code <InstrCd> See h iii above for drop down options

iv. Requested Execution Date <ReqdExctnDt> v. Value Date <ValDt> vi. Interbank Settled Amount <IntrBkSttldAmt>

Default Credit Amount Currency as a non-editable field

Amount entered must be less than Credit Amount from payment transaction. If the entered amount is equal to or greater than Credit Amount, error message should be “amount entered must be less than payment amount.”

vii. Debtor <Dbtr> viii. Debtor Account <DbtrAcct> ix. Intermediary Settlement Agent <IntrmySttlmAgt> x. Last Settlement Agent <LastSttlmAgt> xi. Payment Scheme <PmtSchme> xii. Beneficiary Institution Account <BnfcryInstnAcct> xiii. Creditor <Cdtr> xiv. Creditor Account <CdtrAcct> xv. Remittance Information <RmtInf> xvi. Purpose <Purp>

See h vi above for drop down options

xvii. Instructions For Final Agent <InstrForFnlAgt>

Page 19: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 19 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

See h vii above for drop down

xviii. Details of Charges <DtlsOfChrgs> xix. Sender To Receiver Information <SndrToRcvrInf>

9. If case type is Incorrect Bank Paid, present operator with these options in a drop down list:

a. Forward RequestToModifyPayment message (SI:Common:ForwardRTMP)

i. System sends RTMP template to Receiving Bank of Txn in background

1. Use mapping for Assgnmt, Case and Undrlyg block as in RTMP_RB_Us_RB below

2. Map any fields in <Mod><IntrmySttlmAgt> or <Mod><LastSttlmAgt> blocks from exception case to template

ii. System sends NOCA to Inquirer in background

1. Use mapping in NOCA_IP_Us_RB_MODI below

2. Field <Ntfctn><Justfn> is MODI.

iii. System places case in Pending status.

b. Send AdditionalPaymentInformation message to the Credit Party (SI:Common:SendAPINToCP)

i. System sends API message to Credit Party of Txn

1. Use mapping for Assgnmt, Case and Undrlyg block as in APIN_CP_Us_CP_IncBkPd below

2. Copy all fields in Mod block to corresponding fields in Inf block

ii. Send NOCA to Inquirer in background

1. Use mapping in NOCA_IP_IP_Us_FIAG below (when using FIAG, you do not reassign the case)

2. <Assgnmt><Assgne> is our BIC

3. Use code FIAG in field <Ntfctn><Justfn>

iii. System sends ResolutionOfInvestigation message to Inquirer in background

1. Use mapping in ROIN_IP_Us_IP_INFO

2. <Sts><Conf> code is INFO

iv. System changes status to Resolved v.

c. Cannot complete Modification request

Page 20: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 20 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

i. System sends ROIN_IP_Us_IP_RejIncBkPd

ii. Operator is prompted to enter Rejected Modification code (<RjctdMod>)

1. UM09, Unable to Modify Receiver Correspondent

2. UM10 Unable to Modify Third Reimbursement Institution

iii. Resolve case with status Resolved-Rejected.

d. Process case Step-By-Step. (SI:Common:ProcessStepByStep)

e. Add assignment to case to process receipt of case management messages. “Process new case management message.”

10. If case type is Incorrect Debit, present operator with these options in a drop down list:

a. Forward RequestToModifyPayment (SI:Common:ForwardRTMP)

i. System sends RTMP to Receiving Bank of Txn in background

1. Use mapping in RTMP_RB_Us_RB

2. Copy all fields in Modification Block from exception case to template

ii. System sends NOCA to Inquirer in background

1. Use mapping in NOCA_IP_Us_RB_MODI

2. Use code MODI in field <Ntfctn><Justfn>

iii. System places case in Pending status

b. Send AdditionalPaymentInformation message to the Credit Party (SI:Common:SendAPIToCP)

i. System sends API message to Credit Party of Txn

1. Use mapping for Assgnmt, Case and Undrlyg block as in APIN_CP_Us_CP_IncDbtr below

2. Copy all fields in Mod block to corresponding fields in Inf block

ii. Send NOCA to Inquirer in background

1. Use mapping in NOCA_IP_IP_Us_FIAG below (when using FIAG, you do not reassign the case)

2. <Assgnmt><Assgne> is our BIC

3. Use code FIAG in field <Ntfctn><Justfn>

Page 21: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 21 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

iii. System sends ResolutionOfInvestigation message to Inquirer in background

1. Use mapping in ROI_IP_Us_IP_INFO

2. <Sts><Conf> code is INFO

iv. System changes status to Resolved

c. Generate accounting to correct debit party on our books (SI:Common:CorrectDebitParty)

i. System routes to accounting workbasket

ii. When accounting is complete, Operator must generate RTMP_RB_Us_RB and NOCA_IP_Us_RB_MODI.

d. Cannot complete Modification request

i. System sends ROIN_IP_Us_IP_RejIncDbtr ii. Operator is prompted to enter Rejected Modification code (<RjctdMod>)

A. UM07, Unable to Modify Debtor B. UM08, Unable to Modify Debtor Account

iii. Resolve case with status Resolved-Rejected. e. Process case Step-By-Step. (SI:Common:ProcessStepByStep)

f. Add assignment to case to process receipt of case management messages. “Process new case management message.”

11. If case type is Incorrect Credit, present operator with these options in a drop down list:

a. Forward Request to Modify message (SI:Common: ForwardRTMP)

i. System sends RTMP to Receiving Bank of Txn in background

1. Use mapping for Assgnmt, Case and Undrlyg block as in RTMP_RB_Us_RB below

2. Copy all fields in Modification Block from exception case to template

ii. System sends NOCA to Inquirer in background

1. Use mapping in NOCA_IP_Us_RB_MODI

2. <Assgnmt><Assgne> is BIC of Receiving Bank

3. Use code MODI in field <Ntfctn><Justfn>

iii. System places case in Pending status

b. Request Debit Authorization (SI:Common:RequestDebAuth)

Page 22: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 22 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

i. .System sends DebitAuthorisationRequest to Credit Party

1. Use mapping in DARQ_CP_Us_CP_UPAY

2. Use code UPAY but allow editable field with other options allowed via operator entry:

AGNT, IncorrectAgent, Agent in the payment workflow is incorrect. CURR, IncorrectCurrency, Currency of the payment is incorrect.

CUST, RequestedByCustomer, Cancellation requested by the Debtor.

DUPL, DuplicatePayment, Payment is a duplicate of another payment

UPAY, UnduePayment, Payment is not justified.

ii. Send NOCA to Inquirer in background

1. Use mapping in NOCA_IP_Us_CP_DTAU below

2. <Assgnmt><Assgne> is BIC of Credit Party

3. Use code DTAU in field <Ntfctn><Justfn>

iii. System places case in Pending status

c. Send AdditionalPaymentInformation message to the Credit Party (SI:Common:SendAPINoCP)

i. System sends API message to Credit Party of Txn

1. Use mapping for Assgnmt, Case and Undrlyg block as in APIN_CP_Us_CP_IncCdtr below

2. Copy all fields in Mod block to corresponding fields in Inf block

ii. Send NOCA to Inquirer in background

1. Use mapping in NOCA_IP_IP_Us_FIAG below (when using FIAG, you do not reassign the case)

2. <Assgnmt><Assgne> is our BIC

3. Use code FIAG in field <Ntfctn><Justfn>

iii. System sends ResolutionOfInvestigation message to Inquirer in background

1. Use mapping in ROI_IP_Us_IP_INFO

2. <Sts><Conf> code is INFO

Page 23: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 23 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

iv. System changes status to Resolved

d. Cannot complete Modification request

i. System sends ROIN_IP_Us_IP_RejIncCdtr

1. Operator is prompted to enter Rejected Modification code (<RjctdMod>)

2. UM13, Unable to Modify Creditor

3. UM14, Unable to Modify Creditor Account

ii. Resolve case with status Resolved-Rejected.

e. Process case Step-By-Step (SI:Common:ProcessStepByStep)

f. Add assignment to case to process receipt of case management messages. “Process new case management message.”

12. If case type is Incorrect Date, present operator with these options in a drop down list:

a. Forward RequestToModifyPayment message (SI:Common: ForwardRTMP)

i. System sends RTMP template in background to Receiving Bank

1. Use mapping for Assgnmt, Case and Undrlyg block as in RTMP_RB_Us_RB below

2. Map any fields in <Mod> block from exception case to template

ii. System sends NOCA to Inquirer in background

1. Use mapping in NOCA_IP_Us_RB_MODI below

2. Field <Ntfctn><Justfn> is MODI

iii. System places case in Pending status

b. Request payment cancellation (SI:Common:SendRTCPToRBUPAY)

i. Send Resolution of Investigation to Inquiry Party, indicating Cancellation will follow, ROIN_IP_Us_IP_CWFW.

ii. Send RTCP to Receiving Bank of Txn

1. Use mapping as in RTCP_RB_Us_RB_UPAY

2. Use code UPAY, Undue Payment, in the <Justfn><CxlRsn> field.

iii. System sends NOCA to Inquirer in background

Page 24: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 24 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

1. Use mapping in NOCA_IP_Us_RB_CNCL below

2. Use code CNCL in field <Ntfctn><Justfn>

iv. System places case in Pending status

c. Request Debit Authorization (SI:Common:RequestDebAuth)

i. Send Resolution of Investigation to Inquiry Party, indicating Cancellation will follow, ROIN_IP_Us_IP_CWFW.

ii. System sends DebitAuthorisationRequest to Credit Party

1. Use mapping in DARQ_CP_Us_CP_UPAY

2. Use code UPAY but allow editable field with other options allowed via operator entry:

AGNT, IncorrectAgent, Agent in the payment workflow is incorrect.

CURR, IncorrectCurrency, Currency of the payment is incorrect.

CUST, RequestedByCustomer, Cancellation requested by the Debtor.

DUPL, DuplicatePayment, Payment is a duplicate of another payment

UPAY, UnduePayment, Payment is not justified.

iii. Send NOCA to Inquirer in background

1. Use mapping in NOCA_IP_Us_CP_DTAU below

2. <Assgnmt><Assgne> is BIC of Credit Party

3. Use code DTAU in field <Ntfctn><Justfn>

iv. System places case in Pending status

d. Cannot complete Modification request

i. System sends ROIN_IP_Us_IP_RejIncDate

ii. Operator is prompted to enter Rejected Modification code (<RjctdMod>)

1. UM04, Unable to Modify Requested Execution Date

2. UM05, Unable to Modify Value Date

iii. Resolve case with status Resolved-Rejected.

e. Process case Step-By-Step (SI:Common:ProcessStepByStep)

Page 25: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 25 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

f. Add assignment to case to process receipt of case management messages. “Process new case management message.”

13. If case type is Incorrect Amount, check if Modification request is higher than original amount (SI:IncorrectAmount:ROIReject)

a. If <Mod><IntrBkSttldAmt> is greater than <Undrlyng><IntrBkSttldAmt> then send negative ResolutionOfInvestigation to Inquiry Party

i. Use mapping as in ROIN_IP_Us_IP_IncAmt

ii. UM06 in field <Sts>< RjctdMod>

iii. Resolve case with status Resolved-Rejected.

b. If <Mod><IntrBkSttldAmt> is not greater than <Undrlyng><IntrBkSttldAmt>, present operator with these options in a drop down list:

c. Forward RequestToModifyPayment (SI:Common: ForwardRTMP)

i. System sends RequestToModifyPayment to Receiving Bank in background

1. Use mapping as in RTMP_RB_Us_RB

2. Copy all fields in Modification Block from exception case to template

ii. System sends NOCA to Inquirer in background

1. Use mapping in NOCA_IP_Us_RB_MODI

2. Use code MODI in field <Ntfctn><Justfn>

iii. System places case in Pending status

d. Request payment cancellation (SI:Common:SendRTCPToRBUPAY)

i. Send Resolution of Investigation to Inquiry Party, indicating Cancellation will follow, ROIN_IP_Us_IP_CWFW.

ii. System sends RequestToCancelPayment to Receiving Bank party of Txn

1. Use mapping as in RTCP_RB_Us_RB_UPAY below

2. <Amt> of cancellation request is <Undrlyng><IntrBkSttldAmt> less <Mod><IntrBkSttldAmt>

3. Use code UPAY, Undue Payment, in the <Justfn><CxlRsn> field

iii. Send NOCA to Inquirer in background

Page 26: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 26 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

1. Use mapping in NOCA_IP_Us_RB_CNCL

2. Use code CNCL in field <Ntfctn><Justfn>

iv. System places case in Pending status

e. Request Debit Authorization (SI:IncorrectAmount:RequestDebAuth)

i. Send Resolution of Investigation to Inquiry Party, indicating Cancellation will follow, ROIN_IP_Us_IP_CWFW.

ii. System sends DebitAuthorisationRequest to Credit Party

1. Use mapping in DARQ_CP_Us_CP_UPAY

2. <AmtToDbt> of debit authorization request is <Undrlyng><IntrBkSttldAmt> less <Mod><IntrBkSttldAmt>

3. Use code UPAY in <CxlRsn> field but allow editable field with other options allowed via operator entry:

AGNT, IncorrectAgent, Agent in the payment workflow is incorrect. CURR, IncorrectCurrency, Currency of the payment is incorrect.

CUST, RequestedByCustomer, Cancellation requested by the Debtor.

DUPL, DuplicatePayment, Payment is a duplicate of another payment

UPAY, UnduePayment, Payment is not justified.

iii. Send NOCA to Inquirer in background

1. Use mapping in NOCA_IP_Us_CP_DTAU below

2. <Assgnmt><Assgne> is BIC of Credit Party

3. code DTAU in field <Ntfctn><Justfn>

iv. System places case in Pending status

f. Process case Step-By-Step (SI:Common:ProcessStepByStep)

g. Add assignment to case to process receipt of case management messages. “Process new case management message.”

14. If case type is Incorrect Charges, present operator with these options in a drop down list

a. Forward RequestToModifyPayment message (SI:Common: ForwardRTMP)

i. System sends RTMP template in background to Receiving Bank

Page 27: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 27 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

1. Use mapping for Assgnmt, Case and Undrlyg block as in RTMP_RB_Us_RB below

2. Map any fields in <Mod> block from exception case to template

ii. System sends NOCA to Inquirer in background

1. Use mapping in NOCA_IP_Us_RB_MODI below

2. <Assgnmt><Assgne> is BIC of Receiving Bank or if no Receiving Bank, Credit Party

3. Field <Ntfctn><Justfn> is MODI

iii. System places case in Pending status

b. Make correcting accounting entries (SI:IncorrectCharges:CorrectChargeEntries)

i. System sends NOCA to Inquirer in background

1. Use mapping in NOCA_IP_IP_Us_FIAG below (when using FIAG, you do not reassign the case)

2. <Assgnmt><Assgne> is our BIC

3. Use code FIAG in field <Ntfctn><Justfn>

4. System routes item to accounting workbasket; Operator must send ROIN_IP_Us_IP_MODI when completed

c. Cannot complete Modification request

i. System sends ROIN_IP_Us_IP_RejIncChgs

ii. Default UM17, Unable to Modify Details of Charges in Rejected Modification code (<RjctdMod>)

iii. Resolve case with status Resolved-Rejected.

d. Process case Step-By-Step (SI:Common:ProcessStepByStep)

e. Add assignment to case to process receipt of case management messages. “Process new case management message.”

15. If case type is Incorrect Information, present operator with these options in a drop down list: (**see table RTMP to APIN Comparison below)

a. Forward RequestToModifyPayment (SI:IncorrectInformation:ForwardRTMP

Page 28: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 28 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

i. System sends RequestToModifyPayment to Receiving Bank party of Txn, or if no Receiving Bank, to Credit Party of Txn

1. Use mapping as in RTMP_RB_Us_RB or RTMP_CP_Us_CP

2. Copy all fields in Modification Block from exception case to template

ii. Send NOCA to Inquirer in background

1. Use mapping in NOCA_IP_Us_RB_MODI or NOCA_IP_Us_CP_MODI

2. Use code MODI in field <Ntfctn><Justfn>

iii. System places case in Pending status

b. Send AdditionalPaymentInformation message; conditionalize this option so that it appears only if the <Mod> blocks to be modified are only Remittance Info, <RmtInf> and/or Sender To Receiver Info, <SndrToRcvrInf>. (SI:IncorrectInformation:SendAddPmtInfo)

i. If the <Mod> blocks containing data are other than <SndrToRcvrInfo> or <RmtInf>, present operator with an error message saying “Selection not allowed, please select another option.”

ii. System sends AdditionalPaymentInformation message to Credit Party

1. Use mapping as in APIN_CP_Us_CP_IncInfo below

2. Copy all fields in Mod block to corresponding fields in Inf block

iii. Send NOCA to Inquirer in background

1. Use mapping in NOCA_IP_IP_Us_FIAG below (when using FIAG, you do not reassign the case)

2. <Assgnmt><Assgne> is our BIC

3. Use code FIAG in field <Ntfctn><Justfn >

iv. Send ResolutionOfInvestigation message to Inquirer in background

1. Use mapping in ROIN_IP_Us_IP_INFO

2. <Sts><Conf> code is INFO

3. System changes status to Resolved

c. Cannot complete Modification request

i. System sends ROIN_IP_Us_IP_RejIncInfo

Page 29: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 29 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

ii. Operator is prompted to enter Rejected Modification code (<RjctdMod>)

1. UM01, Unable to Modify Related Reference

2. UM02, Unable to Modify Bank Operation Code

3. UM03, Unable to Modify Instruction Code

4. UM11, Unable to Modify Payment Scheme

5. UM15, Unable to Modify Remittance Information

6. UM18, Unable to Modify Sender to Receiver Information

7. UM19, Unable to Modify Instruction for Final Agent

iii. Resolve case with status Resolved-Rejected.

d. Process case Step-By-Step (SI:Common:ProcessStepByStep)

e. Add assignment to case to process receipt of case management messages. “Process new case management message.”

16. If case type is Amend Bene, present operator with these options in a drop down list:

a. Forward Request to Modify message (SI:Common: ForwardRTMP)

i. System sends RTMP to Receiving Bank of Txn in background

1. Use mapping for Assgnmt, Case and Undrlyg block as in RTMP_RB_Us_RB below

2. Copy all fields in Modification Block from exception case to template

ii. System sends NOCA to Inquirer in background

1. Use mapping in NOCA_IP_Us_RB_MODI

2. <Assgnmt><Assgne> is BIC of Receiving Bank

3. Use code MODI in field <Ntfctn><Justfn>

iii. System places case in Pending status

b. Request payment cancellation (SI:Common:SendRTCPToRBAGNT)

i. Send Resolution of Investigation to Inquiry Party, indicating Cancellation will follow, ROIN_IP_Us_IP_CWFW.

ii. Send RTCP to Receiving Bank of Txn

Page 30: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 30 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

1. Use mapping as in RTCP_RB_Us_RB_AGNT

2. Use code AGNT, Incorrect Agent, in the <Justfn><CxlRsn> field.

iii. Send NOCA to Inquirer in background

1. Use mapping in NOCA_IP_Us_RB_CNCL below

2. Use code CNCL in field <Ntfctn><Justfn>

iv. System places case in Pending status

c. Request Debit Authorization (SI:Common:RequestDebAuth)

i. Send Resolution of Investigation to Inquiry Party, indicating Cancellation will follow, ROIN_IP_Us_IP_CWFW.

ii. System sends DebitAuthorisationRequest to Credit Party

1. Use mapping in DARQ_CP_Us_CP_UPAY

2. Use code UPAY but allow editable field with other options allowed via operator entry:

AGNT, IncorrectAgent, Agent in the payment workflow is incorrect. CURR, IncorrectCurrency, Currency of the payment is incorrect.

CUST, RequestedByCustomer, Cancellation requested by the Debtor.

DUPL, DuplicatePayment, Payment is a duplicate of another payment

UPAY, UnduePayment, Payment is not justified.

iii. Send NOCA to Inquirer in background

1. Use mapping in NOCA_IP_Us_CP_DTAU below

2. <Assgnmt><Assgne> is BIC of Credit Party

3. Use code DTAU in field <Ntfctn><Justfn>

iv. System places case in Pending status

d. Cannot complete Modification request

i. System sends ROIN_IP_Us_IP_RejAmBene

ii. Default UM12, Unable To Modify Account of Beneficiary Institution Rejected Modification code (<RjctdMod>)

iii. Resolve case with status Resolved-Rejected.

Page 31: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 31 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

e. Process case Step-By-Step (SI:Common:ProcessStepByStep)

f. Add assignment to case to process receipt of case management messages. “Process new case management message.”

17. If case type is Incorrect Payment, process case Step-By-Step. (SI:Common:ProcessStepByStep)

a. Add assignment to case to process receipt of case management messages. “Process new case management message.”

RTMP to APIN Comparison

Ind x

Message Item RequestToMod y Payment XML Tag

Additional Payment Info XML Tag

Case Type

4.1 RelatedReference <RltdRef> Incorrect Information

4.2 BankOperation Code <BkOprCd> Incorrect Information

4.3 InstructionCode <InstrCd> Incorrect Information

4.4 Requested ExecutionDate

<ReqdExctnDt> Incorrect Date

4.5 ValueDate <ValDt> Incorrect Date 4.6 InterbankSettledAmount <IntrBkSttldAmt

> Incorrect Amount

4.7 Debtor <Dbtr> <Dbtr> Incorrect Debit Account

4.8 DebtorAccount <DbtrAcct> <DbtrAcct> Incorrect Debit Account

FirstAgent (Field 52) <FrstAgt> Amount <Amt> NostroVostroAccount <NstrVstrAcct> FirstSettlementAgent Fld

53 <

FrstSttlmAgt>

4.9 Intermediary SettlementAgent

<IntrmySttlmAgt >

<IntrmySttlm Agt>

Incorrect Bank Paid

<Intrmy> 4.10 LastSettlement Agent <LastSttlmAgt> <LastSttlmAgt

> Incorrect Bank Paid

4.11 PaymentScheme <PmtSchme> Incorrect Information

4.14 BeneficiaryInstitutionAcc ount

<BnfcryInstnAcct >

Amend Bene

4.15 Creditor <Cdtr> <Cdtr> Incorrect Credit Account

4.16 CreditorAccount <CdtrAcct> <CdtrAcct> Incorrect Credit Account

Page 32: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 32 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

Ind x

Message Item RequestToMod y Payment XML Tag

Additional Payment Info XML Tag

Case Type

4.17 Remittance Information <RmtInf> <RmtChc> Incorrect Information

4.32 Purpose <Purp> Incorrect Information

4.35 InstructionFor FinalAgent <InstrForFnlAgt >

Incorrect Information

4.38 DetailsOfCharges <DtlsOfChrgs> Incorrect Charges 4.39 SenderToReceiver

Information <SndrToRcvrInf >

<SndrToRcvrIn f>

Incorrect Information

RTMP_RB_Us_RB: RequestToModifyPayment camt.007.002.02 MX field tag MX 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 +<ReqdExctnDt> Requested Execution Date Tran Date +<IntrBkSttlmDt> Interbank Settlement

Date Tran Date

<Mod> Modification

NOCA_IP_Us_RB_MODI: NotificationOfCaseAssignment MX camt.030.001.02

MX field tag MX 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

Page 33: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 33 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

NOCA_IP_Us_RB_MODI: NotificationOfCa camt.030.001.02

seAssignment MX

MX field tag MX Tag Description SI Field Name +<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

RTCP_RB_Us_RB_UPAY: RequestToCancelPayment camt.008.002.02

MX field tag MX 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 +<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

NOCA_IP_Us_RB_CNCL: NotificationOfCaseAssignment MX camt.030.001.02 MX field tag MX 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

Page 34: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 34 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

NOCA_IP_Us_RB_CNCL: NotificationOfCaseAssignment MX camt.030.001.02 MX field tag MX 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

ROIN_IP_Us_IP_IncBkPd: ResolutionOfInvestigation camt.029.001.02 MX field tag MX 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 UM09 or UM10

RTMP_CP_Us_CP: RequestToModifyPayment camt.007.002.02 MX field tag MX 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

Page 35: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 35 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

RTMP_CP_U s_CP: RequestToModifyPayment camt.007.002.02 MX field tag MX Tag Description SI Field Name +<IntrBkSttlmDt> Interbank Settlement

Date Tran Date

<Mod> Modification

RTCP_RB_Us_RB_AGNT: RequestToCancelPayment camt.008.002.02 MX field tag MX 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 +<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

NOCA_IP_Us_CP_MODI: NotificationOfCaseAssignment MX camt.030.001.02 MX field tag MX 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

Page 36: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 36 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

NOCA_IP_Us_CP_MODI: NotificationOfCaseAssignment MX camt.030.001.02 MX field tag MX Tag Description SI Field Name +<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 MX field tag MX 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 Inquirer BIC +<Assgne> Assignee Our BIC +<CreDtTm> Create Date/Time System Date/Time <Ntfctn> Notification +<Justfn> Case Forward Notification Code FIAG

NOCA_IP_Us_CP_DTAU: NotificationOfCaseAssignment MX camt.030.001.02 MX field tag MX 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

DARQ_CP_Us_CP_UPAY: DebitAuthorisationRequest camt.037.001.02 MX field tag MX Tag Description SI Field Name <Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id

Page 37: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 37 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

DARQ_CP_Us_CP _UPAY: DebitAuthorisationRequest camt.037.001.02 MX field tag MX Tag Description SI Field Name +<Assgnr> Assigner Our BIC +<Assgne> Assignee BIC/BEI of Credit Party +<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

ROIN_IP_Us_IP_INFO: ResolutionOfInvestigation camt.029.001.02 MX field tag MX 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 MX field tag MX 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

ROIN_IP_Us_I P_MODI: ResolutionOfInv estigation camt.029.001.02

Page 38: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 38 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

MX field tag MX Tag Description SI Field Name +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<Conf> Confirmation MODI

ROIN_IP_Us_IP_CWFW: ResolutionOfInvestigation camt.029.001.02 MX field tag MX 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 CWFW

ROIN_IP_Us_IP_RejIncDbtr: ResolutionOfInvestigation camt.029.001.02 MX field tag MX 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 MX field tag MX 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

Page 39: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 39 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

ROIN_IP_Us_IP_ RejIncCdtr: ResolutionOf Investigation camt.029.001.02 MX field tag MX Tag Description SI Field Name +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<RjctdMod> Rejected Modification UM13 or UM14

ROIN_IP_Us_IP_RejIncDate: ResolutionOfInvestigation camt.029.001.02 MX field tag MX 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 UM04 or UM05

ROIN_IP_Us_IP_IncAmt: ResolutionOfInvestigation camt.029.001.02 MX field tag MX 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 MX field tag MX 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

Page 40: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 40 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

ROIN_IP_Us_IP_R ejIncChgs: ResolutionOfInvestigation camt.029.001.02 MX field tag MX Tag Description SI Field Name <Sts> Status +<RjctdMod> Rejected Modification UM17

ROIN_IP_Us_IP_IncInfo: ResolutionOfInvestigation camt.029.001.02 MX field tag MX 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 MX field tag MX 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 UM12

ROIN_IP_Us_IP_Reject: ResolutionOfInvestigation camt.029.001.02 MX field tag MX 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

Page 41: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 41 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

ROIN_IP_Us_IP_Reject: ResolutionOfIn vestigation camt.029.001.02 MX field tag MX Tag Description SI Field Name <Sts> Status +<RjctdMod> Rejected Modification

APIN_CP_Us_CP_IncBkPd: AdditionalPaymentInformation camt.028.001.02

MX field tag MX 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 +<LastSttlmAgt> Intermediary Settlement

Agent

++<FinInstnId> Financial Institution Id +++<BIC> BIC Mod/LastSttlmAgt/ FinInstnId/

BIC +++<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

Page 42: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 42 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

APIN_CP_Us_CP_IncBkPd: AdditionalPaymentInformation camt.028.001.02

MX field tag MX Tag Description SI Field Name ++++<USFW> Fedwire Routing Number

Id Mod/LastSttlmAgt/ FinInstnId/ ClrSysMmbId/ USFW

++++<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> Austrain 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/ ClrSysMmbId/ AUBSBs

+++<Nm> Name Mod/ LastSttlmAgt/ FinInstnId/Name

+++<PstlAdr> Postal Address Mod/ LastSttlmAgt/ FinInstnId/PstlAdr

++++<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

++++<CtrySubDvs n>

Country SubDivision Mod/ LastSttlmAgt/ FinInstnId/PstlAdr / CtrySubDvsn

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

+++<PrtyId> Proprietary Id

Page 43: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 43 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

APIN_CP_Us_CP_IncBkPd: AdditionalPaymentInformation camt.028.001.02

MX field tag MX Tag Description SI Field Name ++++<Id> Id Mod/ LastSttlmAgt/

FinInstnId/PrtyId/Id ++++<Issr> Issuer Mod/ LastSttlmAgt/

FinInstnId/PrtyId/Issr ++<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 ++++<CtrySubDvs n>

Country SubDivision Mod/ LastSttlmAgt/ BrnchId/PstlAdr/ CtrySubDvsn

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

+<IntrmySttlmAgt> Intermediary Settlement Agent

++<FinInstnId> Financial Institution Id +++<BIC> BIC Mod/IntrmySttlmAgt/

FinInstnId/ BIC +++<ClrSysMmbId >

Clearing System Member ID

Choice Amongst ++++<USCHU> CHIPS Universal ID Mod/IntrmySttlmAgt/

FinInstnId/ ClrSysMmbId/ USCHU

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

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

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

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

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

Page 44: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 44 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

APIN_CP_Us_CP_IncBkPd: AdditionalPaymentInformation camt.028.001.02

MX field tag MX Tag Description SI Field Name FinInstnId/ ClrSysMmbId/

CJBC ++++<USFW> Fedwire Routing Number

Id Mod/IntrmySttlmAgt/ FinInstnId/ ClrSysMmbId/ USFW

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

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

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

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

++++<CACPA> Canadian Payments Association Routing Number Id

Mod/IntrmySttlmAgt/ FinInstnId/ ClrSysMmbId/ CACPA

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

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

++++<ESNCC> Spanish Domestic Interbanking Id

Mod/IntrmySttlmAgt/ FinInstnId/ ClrSysMmbId/ ESNCC

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

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

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

Mod/IntrmySttlmAgt/FinInstnId / ClrSysMmbId/ AUBSBx

++++<AUBSBs> Australian Small Network Id

Mod/IntrmySttlmAgt/FinInstnId / ClrSysMmbId/ AUBSBs

+++<Nm> Name Mod/ IntrmySttlmAgt/ FinInstnId/Name

+++<PstlAdr> Postal Address Mod/ IntrmySttlmAgt/ FinInstnId/PstlAdr

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

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

++++<StrNm> Street Name Mod/ IntrmySttlmAgt/ FinInstnId/PstlAdr / StrNm

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

Page 45: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 45 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

APIN_CP_Us_CP_IncBkPd: AdditionalPaymentInformation camt.028.001.02

MX field tag MX Tag Description SI Field Name ++++<PstCd> Post Code Mod/ IntrmySttlmAgt/

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

FinInstnId/PstlAdr / TwnNm ++++<CtrySubDvs n>

Country SubDivision Mod/ IntrmySttlmAgt/ FinInstnId/PstlAdr / CtrySubDvsn

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

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

FinInstnId/PrtyId/Id ++++<Issr> Issuer Mod/ IntrmySttlmAgt/

FinInstnId/PrtyId/Issr ++<BrnchId> Branch Id +++<Id> Id Mod/ IntrmySttlmAgt/

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

BrnchId/Nm +++<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 ++++<CtrySubDvs n>

Country SubDivision Mod/ IntrmySttlmAgt/ BrnchId/PstlAdr/ CtrySubDvsn

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

APIN_CP_Us_CP_IncDbtr: AdditionalPaymentInformation camt.028.001.02

MX field tag MX 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

Page 46: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 46 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

APIN_CP_Us_CP_IncDbtr: AdditionalPaymentInformation camt.028.001.02

MX field tag MX Tag Description SI Field Name +<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 +++<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

Page 47: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 47 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

APIN_CP_Us_CP_IncDbtr: AdditionalPaymentInformation camt.028.001.02

MX field tag MX Tag Description SI Field Name ++++<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

MX field tag MX 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 +<Cdtr> Creditor Inf/ Cdtr

Page 48: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 48 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

APIN_CP_Us_CP_IncCdtr: AdditionalPaymentInformation camt.028.001.02

MX field tag MX Tag Description SI Field Name ++<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 ++++<Issr> Issuer Mod/ Cdtr/ PrvtId/Issr +<CdtrAcct> Debtor Account ++<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

Page 49: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 49 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

APIN_CP_Us_CP_IncCdtr: AdditionalPaymentInformation camt.028.001.02

MX field tag MX Tag Description SI Field Name ++<Ccy> Currency Mod/ CdtrAcct/ Ccy ++<Nm> Name Mod/ CdtrAcct/ Nm

APIN_CP_Us_CP_IncInfo: AdditionalPaymentInformation camt.028.001.02

MX field tag MX 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 +++<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/ RfrdDocAmt/DuePyblAmt

++++<DscntApldA mt>

Discount Applied Amount Mod/RmtInf/Strd/ RfrdDocAmt/DscntAPldAmt

++++<RmtdAmt> Remitted Amount Mod/RmtInf/Strd/ RfrdDocAmt/RmtdAmt

++++<CdtNoteAmt >

Credit Note Amount Mod/RmtInf/Strd/ RfrdDocAmt/CdtNoteAmt

++++<TaxAmt> Tax Amount Mod/RmtInf/Strd/

Page 50: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 50 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

APIN_CP_Us_CP_IncInfo: AdditionalPaymentInformation camt.028.001.02

MX field tag MX Tag Description SI Field Name RfrdDocAmt/TaxAmt +++<DocRefNb> Document Reference

Number Mod/RmtInf/Strd/DocRefNb

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

/Invcr/PstlAdr/AdrTp +++++<AdrLine> Address Line Mod/RmtInf

/Invcr/PstlAdr/AdrLine +++++<StrNm> Street Name Mod/RmtInf

/Invcr/PstlAdr/StrNm +++++<BldgNb> Building Number Mod/RmtInf

/Invcr/PstlAdr/BldgNb +++++<PstCd> Post Code Mod/RmtInf

/Invcr/PstlAdr/PstCd +++++<TwnNm> Town Name Mod/RmtInf

/Invcr/PstlAdr/TwnNm +++++<CtrySubDv sn>

Country SubDivision Mod/RmtInf /Invcr/PstlAdr/CtrySubDvsn

+++++<Ctry> Country Mod/RmtInf /Invcr/ PstlAdr/Ctry

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

/Invcr/Id/OrgId/BEI ++++++<EANGLN >

EANGLN Mod/RmtInf /Invcr/Id/OrgId/EANGLN

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

++++++<DUNS> DUNS Mod/RmtInf /Invcr/Id/OrgId/DUNS

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

++++++<TaxIdNb >

Tax Id Number Mod/RmtInf/Invcr/Id/ OrgId/TaxIdNb

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

OrgId/PrtyId/Id +++++++<Issr> Issuer Mod/RmtInf/Invcr/Id/

OrgId/PrtyId/Issr +++++<PrvtId> Private Id

Choice Amongst ++++++<DrvrsLicN b>

Drivers License Number Mod/RmtInf/Invcr/Id/ PrvtId/DrvrsLicNb

++++++<SclSctyN Social Security Number Mod/RmtInf/Invcr/Id/

Page 51: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 51 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

APIN_CP_Us_CP_IncInfo: AdditionalPaymentInformation camt.028.001.02

MX field tag MX Tag Description SI Field Name b> PrvtId/SclSctyNb ++++++<AlnRegnN b>

Alien Registration Number Mod/RmtInf/Invcr/Id/ PrvtId/AlnRegnNb

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

++++++<TaxIdNb >

Tax Id Number Mod/RmtInf/Invcr/Id/ PrvtId/TaxidNb

++++++<IdntyCar dNb>

Identity Card Number Mod/RmtInf/Invcr/Id/ PrvtId/IdntyCardNb

++++++<MplyrIdN b>

Employer Id Number Mod/RmtInf/Invcr/Id/ PrvtId/MplyrIdNb

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

PrvtId/OthrId/Id +++++++<IdTp> Id Number Mod/RmtInf/Invcr/Id/

PrvtId/OthrId/IdTp ++++++<Issr> Issuer Mod/RmtInf/Invcr/Id/

PrvtId/Issr +++<Invcee> Invoicee ++++<Nm> Name Mod/RmtInf /Invcee/Nm ++++<PstlAdr> Postal Address +++++<AdrTp> Address Type Mod/RmtInf

/Invcee/PstlAdr/AdrTp ++++<AdrLine> Address Line Mod/RmtInf

/Invcee/PstlAdr/AdrLine +++++<StrNm> Street Name Mod/RmtInf

/Invcee/PstlAdr/StrNm +++++<BldgNb> Building Number Mod/RmtInf

/Invcee/PstlAdr/BldgNb +++++<PstCd> Post Code Mod/RmtInf

/Invcee/PstlAdr/PstCd +++++<TwnNm> Town Name Mod/RmtInf

/Invcee/PstlAdr/TwnNm +++++<CtrySubDv sn>

Country SubDivision Mod/RmtInf /Invcee/PstlAdr/CtrySubDvsn

+++++<Ctry> Country Mod/RmtInf /Invcee/PstlAdr/Ctry

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

/Invcee/Id/OrgId/BEI ++++++<EANGLN >

EANGLN Mod/RmtInf /Invcee/Id/OrgId/EANGLN

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

++++++<DUNS> DUNS Mod/RmtInf /Invcee/Id/OrgId/DUNS

Page 52: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 52 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

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

APIN_CP_Us_CP_IncInfo: AdditionalPaymentInformation camt.028.001.02

MX field tag MX Tag Description SI Field Name /Invcee/Id/OrgId/BkPtyId ++++++<TaxIdNb >

Tax Id Number Mod/RmtInf/Invcee/Id/ OrgId/TaxIdNb

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

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

OrgId/PrtyId/Issr +++++<PrvtId> Private Id

Choice Amongst ++++++<DrvrsLicN b>

Drivers License Number Mod/RmtInf/Invcee/Id/ PrvtId/DrvrsLicNb

++++++<SclSctyN b>

Social Security Number Mod/RmtInf/Invcee/Id/ PrvtId/SclSctyNb

++++++<AlnRegnN b>

Alien Registration Number Mod/RmtInf/Invcee/Id/ PrvtId/AlnRegnNb

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

++++++<TaxIdNb >

Tax Id Number Mod/RmtInf/Invcee/Id/ PrvtId/TaxidNb

++++++<IdntyCar dNb>

Identity Card Number Mod/RmtInf/Invcee/Id/ PrvtId/IdntyCardNb

++++++<MplyrIdN b>

Employer Id Number Mod/RmtInf/Invcee/Id/ PrvtId/MplyrIdNb

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

PrvtId/OthrId/Id +++++++<IdTp> Id Number Mod/RmtInf/Invcee/Id/

PrvtId/OthrId/IdTp ++++++<Issr> Issuer Mod/RmtInf/Invcee/Id/

PrvtId/Issr +<SndrToRcvrInf> Sender To Receiver

Information Mod/SndrToRcvInf

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX 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

Page 53: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 53 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

+<OrgnlMsgNmId> Original Message Name Trantype/Insttype

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name

ID +<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/RmtChc/Ustrd ++<Strd> Structured +++<RfrdDocTp> Referred Document Type Mod/RmtChc/Strd/ RfrdDocTp +++<RfrdDocRltdDt >

Referred Document Related Date

Mod/RmtChc/Strd/ RfrdDocRltdDt

+++<RfrdDocAmt Referred Document Amount

Mod/RmtChc/Strd/ RfrdDocAmt

Choice amongst ++++<DuePyblAmt> Due Payable Amount Mod/RmtChc/Strd/

RfrdDocAmt/DuePyblAmt ++++<DscntApldAm t>

Discount Applied Amount Mod/RmtChc/Strd/ RfrdDocAmt/DscntAPldAmt

++++<RmtdAmt> Remitted Amount Mod/RmtChc/Strd/ RfrdDocAmt/RmtdAmt

++++<CdtNoteAmt> Credit Note Amount Mod/RmtChc/Strd/ RfrdDocAmt/CdtNoteAmt

++++<TaxAmt> Tax Amount Mod/RmtChc/Strd/ RfrdDocAmt/TaxAmt

+++<DocRefNb> Document Reference Number

Mod/RmtChc/Strd/DocRefNb

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

/Invcr/PstlAdr/AdrTp +++++<AdrLine> Address Line Mod/RmtChc

/Invcr/PstlAdr/AdrLine +++++<StrNm> Street Name Mod/RmtChc

/Invcr/PstlAdr/StrNm +++++<BldgNb> Building Number Mod/RmtChc

/Invcr/PstlAdr/BldgNb +++++<PstCd> Post Code Mod/RmtChc

/Invcr/PstlAdr/PstCd

Page 54: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 54 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

+++++<TwnNm> Town Name Mod/RmtChc /Invcr/PstlAdr/TwnNm

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name +++++<CtrySubDvs n>

Country SubDivision Mod/RmtChc /Invcr/PstlAdr/CtrySubDvsn

+++++<Ctry> Country Mod/RmtChc /Invcr/ PstlAdr/Ctry

++++<Id> Id Choice amongst

+++++<OrgId> Organization Id ++++++<BEI> BEI Mod/RmtChc

/Invcr/Id/OrgId/BEI ++++++<EANGLN> EANGLN Mod/RmtChc

/Invcr/Id/OrgId/EANGLN ++++++<USCHU> CHIPS Universal Id Mod/RmtChc

/Invcr/Id/OrgId/USCHU ++++++<DUNS> DUNS Mod/RmtChc

/Invcr/Id/OrgId/DUNS ++++++<BkPtyId> Bank Party Id Mod/RmtChc

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

OrgId/TaxIdNb ++++++<PrtryId> Proprietary Id +++++++<Id> Id Mod/RmtChc/Invcr/Id/

OrgId/PrtyId/Id +++++++<Issr> Issuer Mod/RmtChc/Invcr/Id/

OrgId/PrtyId/Issr +++++<PrvtId> Private Id

Choice Amongst ++++++<DrvrsLicN b>

Drivers License Number Mod/RmtChc/Invcr/Id/ PrvtId/DrvrsLicNb

++++++<SclSctyNb >

Social Security Number Mod/RmtChc/Invcr/Id/ PrvtId/SclSctyNb

++++++<AlnRegnN b>

Alien Registration Number Mod/RmtChc/Invcr/Id/ PrvtId/AlnRegnNb

++++++<PsptNb> Passport Number Mod/RmtChc/Invcr/Id/ PrvtId/PsptNb

++++++<TaxIdNb> Tax Id Number Mod/RmtChc/Invcr/Id/ PrvtId/TaxidNb

++++++<IdntyCard Nb>

Identity Card Number Mod/RmtChc/Invcr/Id/ PrvtId/IdntyCardNb

++++++<MplyrIdNb >

Employer Id Number Mod/RmtChc/Invcr/Id/ PrvtId/MplyrIdNb

++++++<OthrId> Other Id +++++++<Id> Id Mod/RmtChc/Invcr/Id/

PrvtId/OthrId/Id +++++++<IdTp> Id Number Mod/RmtChc/Invcr/Id/

PrvtId/OthrId/IdTp ++++++<Issr> Issuer Mod/RmtChc/Invcr/Id/

PrvtId/Issr

Page 55: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 55 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

+++<Invcee> Invoicee ++++<Nm> Name Mod/RmtChc /Invcee/Nm

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name ++++<PstlAdr> Postal Address +++++<AdrTp> Address Type Mod/RmtChc

/Invcee/PstlAdr/AdrTp ++++<AdrLine> Address Line Mod/RmtChc

/Invcee/PstlAdr/AdrLine +++++<StrNm> Street Name Mod/RmtChc

/Invcee/PstlAdr/StrNm +++++<BldgNb> Building Number Mod/RmtChc

/Invcee/PstlAdr/BldgNb +++++<PstCd> Post Code Mod/RmtChc

/Invcee/PstlAdr/PstCd +++++<TwnNm> Town Name Mod/RmtChc

/Invcee/PstlAdr/TwnNm +++++<CtrySubDvs n>

Country SubDivision Mod/RmtChc /Invcee/PstlAdr/CtrySubDvsn

+++++<Ctry> Country Mod/RmtChc /Invcee/PstlAdr/Ctry

++++<Id> Id Choice amongst

+++++<OrgId> Organization Id ++++++<BEI> BEI Mod/RmtChc

/Invcee/Id/OrgId/BEI ++++++<EANGLN> EANGLN Mod/RmtChc

/Invcee/Id/OrgId/EANGLN ++++++<USCHU> CHIPS Universal Id Mod/RmtChc

/Invcee/Id/OrgId/USCHU ++++++<DUNS> DUNS Mod/RmtChc

/Invcee/Id/OrgId/DUNS ++++++<BkPtyId> Bank Party Id Mod/RmtChc

/Invcee/Id/OrgId/BkPtyId ++++++<TaxIdNb> Tax Id Number Mod/RmtChc/Invcee/Id/

OrgId/TaxIdNb ++++++<PrtryId> Proprietary Id +++++++<Id> Id Mod/RmtChc/Invcee/Id/

OrgId/PrtyId/Id +++++++<Issr> Issuer Mod/RmtChc/Invcee/Id/

OrgId/PrtyId/Issr +++++<PrvtId> Private Id

Choice Amongst ++++++<DrvrsLicN b>

Drivers License Number Mod/RmtChc/Invcee/Id/ PrvtId/DrvrsLicNb

++++++<SclSctyNb >

Social Security Number Mod/RmtChc/Invcee/Id/ PrvtId/SclSctyNb

++++++<AlnRegnN b>

Alien Registration Number Mod/RmtChc/Invcee/Id/ PrvtId/AlnRegnNb

++++++<PsptNb> Passport Number Mod/RmtChc/Invcee/Id/ PrvtId/PsptNb

Page 56: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 56 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

++++++<TaxIdNb> Tax Id Number Mod/RmtChc/Invcee/Id/ PrvtId/TaxidNb

++++++<IdntyCard Identity Card Number Mod/RmtChc/Invcee/Id/

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name Nb> PrvtId/IdntyCardNb ++++++<MplyrIdNb >

Employer Id Number Mod/RmtChc/Invcee/Id/ PrvtId/MplyrIdNb

++++++<OthrId> Other Id +++++++<Id> Id Mod/RmtChc/Invcee/Id/

PrvtId/OthrId/Id +++++++<IdTp> Id Number Mod/RmtChc/Invcee/Id/

PrvtId/OthrId/IdTp ++++++<Issr> Issuer Mod/RmtChc/Invcee/Id/

PrvtId/Issr +<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 +++<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

Page 57: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 57 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

++++<MplyrIdNb> Employer Id Number Mod/ Dbtr/ PrvtId/ MplyrIdNb ++++<OthrId> Other Id +++++<Id> Id Mod/ Dbtr/ PrvtId/ OthrId/Id +++++<IdTp> Id Number Mod/ Dbtr/ PrvtId/

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name

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 +<FrstAgt> First Agent ++<FinInstnId> Financial Institution Id +++<BIC> BIC Mod/FrstAgt/ FinInstnId/ BIC +++<ClrSysMmbId> Clearing System Member

ID

Choice Amongst ++++<USCHU> CHIPS Universal ID Mod/FrstAgt/ FinInstnId/

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

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

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

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

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

ClrSysMmbId/ CJBC ++++<USFW> Fedwire Routing Number

Id Mod/FrstAgt/ FinInstnId/ ClrSysMmbId/ USFW

++++<PTNCC> Portuguese NCC Id Mod/FrstAgt/ FinInstnId/ ClrSysMmbId/ PTNCC

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

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

++++<ATBLZ> Austrain Bankleitzahl Id Mod/FrstAgt/ FinInstnId/ ClrSysMmbId/ ATBLZ

Page 58: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 58 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

++++<CACPA> Canadian Payments Association Routing Number Id

Mod/FrstAgt/ FinInstnId/ ClrSysMmbId/ CACPA

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

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

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name ++++<ESNCC> Spanish Domestic

Interbanking Id Mod/FrstAgt/ FinInstnId/ ClrSysMmbId/ ESNCC

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

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

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

Mod/FrstAgt/ FinInstnId/ ClrSysMmbId/ AUBSBx

++++<AUBSBs> Australian Small Network Id

Mod/FrstAgt/FinInstnId/ ClrSysMmbId/ AUBSBs

+++<Nm> Name Mod/ FrstAgt/ FinInstnId/Name +++<PstlAdr> Postal Address Mod/ FrstAgt/

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

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

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

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

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

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

FinInstnId/PstlAdr / TwnNm ++++<CtrySubDvsn >

Country SubDivision Mod/ FrstAgt/ FinInstnId/PstlAdr / CtrySubDvsn

++++<Ctry> Country Mod/ FrstAgt/ FinInstnId/PstlAdr / Ctry

+++<PrtyId> Party Id ++++<Id> Id Mod/ FrstAgt/

FinInstnId/PrtyId/Id ++++<Issr> Issuer Mod/ FrstAgt/

FinInstnId/PrtyId/Issr ++<BrnchId> Branch Id +++<Id> Id Mod/ FrstAgt/ BrnchId/Id +++<Nm> Name Mod/ FrstAgt/ BrnchId/Nm +++<PstlAdr> Postal Address ++++<AdrTp> Address Type Mod/ FrstAgt/ BrnchId/PstlAdr/

AdrTp

Page 59: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 59 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

++++<AdrLine> Address Line Mod/ FrstAgt/ BrnchId/PstlAdr/ AdrLine

++++<StrNm> Street Name Mod/ FrstAgt/ BrnchId/PstlAdr/ StrNm

++++<BldgNb> Building Number Mod/ FrstAgt/ BrnchId/PstlAdr/ BldgNb

++++<PstCd> Post Code Mod/ FrstAgt/ BrnchId/PstlAdr/ PstCd

++++<TwnNm> Town Name Mod/ FrstAgt/ BrnchId/PstlAdr/

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name

TwnNm ++++<CtrySubDvsn >

Country SubDivision Mod/ FrstAgt/ BrnchId/PstlAdr/ CtrySubDvsn

++++<Ctry> Country Mod/ FrstAgt/ BrnchId/PstlAdr/Ctry

+<Amt> Amount Choice Amongst ++<InstdAmt> Instructed Amount Mod/Amt/InstdAmt ++<EqvtAmt> Equivalent Amount +++<Amt> Amount Mod/Amt/EqvtAmt/Amt +++<CcyOfTrf> Currency Of Transfer Mod/Amt/EqvtAmt/CcyOfTrf +<NstrVstrAcct> Nostro Vostro Account ++<Id> Id

Choice Amongst +++<IBAN> IBAN Mod/NstrVstrAcct/ Id/ IBAN +++<BBAN> BBAN Mod/NstrVstrAcct/ Id/ BBAN +++<UPIC> UPIC Mod/NstrVstrAcct/ Id/ UPIC +++<DmstAcct> Domestic Account ++++<Id> Id Mod/NstrVstrAcct/ Id/

DmstAcct/Id ++<Tp> Type Mod/NstrVstrAcct/ Tp ++<Ccy> Currency Mod/NstrVstrAcct/ Ccy ++<Nm> Name Mod/NstrVstrAcct/ Nm +<Intrmy> Intermediary ++<Id> Identification +++<BICOrBEI> BIC or BEI Mod/Intrmy/Id/BICOrBEI +++<PrtryId> Proprietary Id ++++<Id> Identification Mod/Intrmy/Id/PrtryId/Id ++++<SchmeNm> Scheme Name Mod/Intrmy/Id/PrtryId/SchmeN

m ++++<Issr> Issuer Mod/Intrmy/Id/PrtryId/Issr +++<NmAndAdr> Name and Address ++++<Nm> Name Mod/Intrmy/Id/NmAndAdr/Nm ++++<Adr> Address +++++<Ustrd> Unstructured Mod/Intrmy/Id/NmAndAdr/Adr/

Unstrd +++++<Strd > Structured ++++++<BldgNm> Building Name Mod/Intrmy/Id/NmAndAdr/Adr/

Unstrd/BldgNm

Page 60: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 60 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

++++++<StrtNm> Street Name Mod/Intrmy/Id/NmAndAdr/Adr/ Unstrd/StrtNm

++++++<StrtBldgId >

Street Building Id Mod/Intrmy/Id/NmAndAdr/Adr/ Unstrd/StrtBldgId

++++++<Flr> Floor Mod/Intrmy/Id/NmAndAdr/Adr/ Unstrd/Flr

++++++<TwnNm> Town Name Mod/Intrmy/Id/NmAndAdr/Adr/ Unstrd/TwnNm

++++++<DstrctNm >

District Name Mod/Intrmy/Id/NmAndAdr/Adr/ Unstrd/DstrctNm

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name ++++++<RgnId> Region Id Mod/Intrmy/Id/NmAndAdr/Adr/

Unstrd/RgnId ++++++<Stat> State Mod/Intrmy/Id/NmAndAdr/Adr/

Unstrd/Stat ++++++<CtyId> Country Id Mod/Intrmy/Id/NmAndAdr/Adr/

Unstrd/CtyId ++++++<Cty> Country Mod/Intrmy/Id/NmAndAdr/Adr/

Unstrd/Cty ++++++<PstCdId> Post Code Id Mod/Intrmy/Id/NmAndAdr/Adr/

Unstrd/PstCdId ++++++<POB> Post Office Box Mod/Intrmy/Id/NmAndAdr/Adr/

Unstrd/POB ++<Acct> Account +++<Id> Id ++++<Prtry> Proprietary +++++<Id> Id Mod/Intrmy/Acct/Id/Prtry/Id +++<AcctSvcr> Account Servicer ++++<BICOrBEI> BIC or BEI Mod/Intrmy/Acct/AcctSvcr/BIC

OrBEI ++++<PrtryId> Proprietary Id +++++<Id> Id Mod/Intrmy/Acct/AcctSvcr/Prty

Id/Id +++++<SchmeNm> Scheme Name Mod/Intrmy/Acct/AcctSvcr/Prty

Id/SchmeNm +++++<Issr> Issuer Mod/Intrmy/Acct/AcctSvcr/Prty

Id/Issr ++++<NmAndAdr> Name and Address +++++<Nm> Name Mod/Intrmy/Acct/AcctSvcr/Nm

AndAdr/Nm +++++<Adr> Address ++++++<Ustrd> Unstructured Mod/Intrmy/Acct/AcctSvcr/Nm

AndAdr/Adr/Ustrd ++++++<Strd > Structured +++++++<BldgNm >

Building Name Mod/Intrmy/Acct/AcctSvcr/Nm AndAdr/Adr/Strd/BldgNm

+++++++<StrtNm> Street Name Mod/Intrmy/Acct/AcctSvcr/Nm AndAdr/Adr/Strd/StrNm

Page 61: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 61 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

+++++++<StrtBldgI d>

Street Building Id Mod/Intrmy/Acct/AcctSvcr/Nm AndAdr/Adr/Strd/StrtBldgId

+++++++<Flr> Floor Mod/Intrmy/Acct/AcctSvcr/Nm AndAdr/Adr/Strd/Flr

+++++++<TwnNm> Town Name Mod/Intrmy/Acct/AcctSvcr/Nm AndAdr/Adr/Strd/TwnNm

+++++++<DstrctN m>

District Name Mod/Intrmy/Acct/AcctSvcr/Nm AndAdr/Adr/Strd/DstrctNm

+++++++<RgnId> Region Id Mod/Intrmy/Acct/AcctSvcr/Nm AndAdr/Adr/Strd/RgnId

+++++++<Stat> State Mod/Intrmy/Acct/AcctSvcr/Nm AndAdr/Adr/Strd/Stat

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name +++++++<CtyId> Country Id Mod/Intrmy/Acct/AcctSvcr/Nm

AndAdr/Adr/Strd/CtyId +++++++<Cty> Country Mod/Intrmy/Acct/AcctSvcr/Nm

AndAdr/Adr/Strd/Cty +++++++<PstCdId >

Post Code Id Mod/Intrmy/Acct/AcctSvcr/Nm AndAdr/Adr/Strd/PstCdId

+++++++<POB> Post Office Box Mod/Intrmy/Acct/AcctSvcr/Nm AndAdr/Adr/Strd/POB

++<Role> Role Mod/Intrmy/Role +<FrstSttlmAgt> First Settlement Agent ++<FinInstnId> Financial Institution Id +++<BIC> BIC Mod/ FrstSttlmAgt/ FinInstnId/

BIC +++<ClrSysMmbId> Clearing System Member

ID

Choice Amongst ++++<USCHU> CHIPS Universal ID Mod/ FrstSttlmAgt/ FinInstnId/

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

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

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

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

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

ClrSysMmbId/ CJBC ++++<USFW> Fedwire Routing Number

Id Mod/ FrstSttlmAgt/ FinInstnId/ ClrSysMmbId/ USFW

++++<PTNCC> Portuguese NCC Id Mod/ FrstSttlmAgt/ FinInstnId/ ClrSysMmbId/ PTNCC

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

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

Page 62: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 62 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

++++<ATBLZ> Austrain Bankleitzahl Id Mod/ FrstSttlmAgt/ FinInstnId/ ClrSysMmbId/ ATBLZ

++++<CACPA> Canadian Payments Association Routing Number Id

Mod/ FrstSttlmAgt/ FinInstnId/ ClrSysMmbId/ CACPA

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

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

++++<ESNCC> Spanish Domestic Interbanking Id

Mod/ FrstSttlmAgt/ FinInstnId/ ClrSysMmbId/ ESNCC

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

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

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name

ClrSysMmbId/ HKNCC ++++<AUBSBx> Australian Extensive

Branch Network Id Mod/ FrstSttlmAgt/FinInstnId/ ClrSysMmbId/ AUBSBx

++++<AUBSBs> Australian Small Network Id

Mod/ FrstSttlmAgt/FinInstnId/ ClrSysMmbId/ AUBSBs

+++<Nm> Name Mod/ FrstSttlmAgt/ FinInstnId/Name

+++<PstlAdr> Postal Address Mod/ FrstSttlmAgt/ FinInstnId/PstlAdr

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

++++<AdrLine> Address Line Mod/ FrstSttlmAgt/ FinInstnId/PstlAdr / AdrLine

++++<StrNm> Street Name Mod/ FrstSttlmAgt/ FinInstnId/PstlAdr / StrNm

++++<BldgNb> Building Number Mod/ FrstSttlmAgt/ FinInstnId/PstlAdr / BldgNb

++++<PstCd> Post Code Mod/ FrstSttlmAgt/ FinInstnId/PstlAdr / PstCd

++++<TwnNm> Town Name Mod/ FrstSttlmAgt/ FinInstnId/PstlAdr / TwnNm

++++<CtrySubDvsn >

Country SubDivision Mod/ FrstSttlmAgt/ FinInstnId/PstlAdr / CtrySubDvsn

++++<Ctry> Country Mod/ FrstSttlmAgt/ FinInstnId/PstlAdr /Ctry

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

FinInstnId/PrtyId/Id ++++<Issr> Issuer Mod/ FrstSttlmAgt/

FinInstnId/PrtyId/Issr ++<BrnchId> Branch Id +++<Id> Id Mod/ FrstSttlmAgt/ BrnchId/Id

Page 63: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 63 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

+++<Nm> Name Mod/ FrstSttlmAgt/ BrnchId/Nm

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

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

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

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

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

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

BrnchId/PstlAdr/ TwnNm ++++<CtrySubDvsn >

Country SubDivision Mod/ FrstSttlmAgt/ BrnchId/PstlAdr/ CtrySubDvsn

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name ++++<Ctry> Country Mod/ FrstSttlmAgt/

BrnchId/PstlAdr/Ctry +<LastSttlmAgt> Intermediary Settlement

Agent

++<FinInstnId> Financial Institution Id +++<BIC> BIC Mod/LastSttlmAgt/ FinInstnId/

BIC +++<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

++++<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

Page 64: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 64 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

++++<ATBLZ> Austrain 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/ ClrSysMmbId/ AUBSBs

+++<Nm> Name Mod/ LastSttlmAgt/

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name

FinInstnId/Name +++<PstlAdr> Postal Address Mod/ LastSttlmAgt/

FinInstnId/PstlAdr ++++<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 ++++<CtrySubDvsn >

Country SubDivision Mod/ LastSttlmAgt/ FinInstnId/PstlAdr / CtrySubDvsn

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

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

FinInstnId/PrtyId/Id ++++<Issr> Issuer Mod/ LastSttlmAgt/

FinInstnId/PrtyId/Issr ++<BrnchId> Branch Id +++<Id> Id Mod/ LastSttlmAgt/ BrnchId/Id

Page 65: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 65 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

+++<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/ BrnchId/PstlAdr/Ctry

+<IntrmySttlmAgt> Intermediary Settlement Agent

++<FinInstnId> Financial Institution Id +++<BIC> BIC Mod/IntrmySttlmAgt/

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name

FinInstnId/ BIC +++<ClrSysMmbId> Clearing System Member

ID

Choice Amongst ++++<USCHU> CHIPS Universal ID Mod/IntrmySttlmAgt/

FinInstnId/ ClrSysMmbId/ USCHU

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

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

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

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

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

++++<USFW> Fedwire Routing Number Id

Mod/IntrmySttlmAgt/ FinInstnId/ ClrSysMmbId/ USFW

Page 66: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 66 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

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

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

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

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

++++<CACPA> Canadian Payments Association Routing Number Id

Mod/IntrmySttlmAgt/ FinInstnId/ ClrSysMmbId/ CACPA

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

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

++++<ESNCC> Spanish Domestic Interbanking Id

Mod/IntrmySttlmAgt/ FinInstnId/ ClrSysMmbId/ ESNCC

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

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name

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

/ ClrSysMmbId/ HKNCC ++++<AUBSBx> Australian Extensive

Branch Network Id Mod/IntrmySttlmAgt/FinInstnId / ClrSysMmbId/ AUBSBx

++++<AUBSBs> Australian Small Network Id

Mod/IntrmySttlmAgt/FinInstnId / ClrSysMmbId/ AUBSBs

+++<Nm> Name Mod/ IntrmySttlmAgt/ FinInstnId/Name

+++<PstlAdr> Postal Address Mod/ IntrmySttlmAgt/ FinInstnId/PstlAdr

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

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

++++<StrNm> Street Name Mod/ IntrmySttlmAgt/ FinInstnId/PstlAdr / StrNm

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

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

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

Page 67: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 67 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

++++<CtrySubDvsn >

Country SubDivision Mod/ IntrmySttlmAgt/ FinInstnId/PstlAdr / CtrySubDvsn

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

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

FinInstnId/PrtyId/Id ++++<Issr> Issuer Mod/ IntrmySttlmAgt/

FinInstnId/PrtyId/Issr ++<BrnchId> Branch Id +++<Id> Id Mod/ IntrmySttlmAgt/

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

BrnchId/Nm +++<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/

Page 68: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 68 Pega Advanced E&I Rulebook Application Workflow Definition and Specification

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name

BrnchId/PstlAdr/ TwnNm ++++<CtrySubDvsn >

Country SubDivision Mod/ IntrmySttlmAgt/ BrnchId/PstlAdr/ CtrySubDvsn

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

+<Cdtr> Creditor Mod/ Cdtr ++<Nm> Name Mod/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 ++++<Issr> Issuer Mod/ Cdtr/ PrvtId/Issr +<CdtrAcct> Debtor Account ++<Id> Id

Choice Amongst +++<IBAN> IBAN Mod/ CdtrAcct/ Id/IBAN

Page 69: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 69

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX Tag Description SI Field Name +++<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 +<SndrToRcvrInf> Sender To Receiver

Information Mod/SndrToRcvInf

UnableToApply, MX camt.026 1. System receives XML message UnableToApply message, MX camt.026

2. System creates M- case with the following mapping from message. All fields should be mapped into comparably named fields in the work area of the M- case, so operator reviewing message can review with tag/data pairs rather than raw message. (SI:Common:CreateMsgCase)

UnableToApply camt.026.001.02 MX field tag MX Field name Msg Case

Property Name Exc Case

Map to Exc Case Work Info Section

<Assgnmt> Assignment +<Id> Id Assgnmt/Id ** +<Assgnr> Assigner Assgnmt/Assgnr ** +<Assgne> Assignee Assignmt/Assgne ** +<CreDtTm> Create Date/Time Assignmt/CreDtTm ** <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 Identification

Undrlyg/OrgnlMsgNm Id

TranType/ Insttype

+<OrgnlInstrId> Original Instruction Identification

Undrlyg/OrgnlInstrId Transaction Reference

Choice amongst +<InstdAmt> Instructed

Amount Undrlyg/CcyAmt/Ccy and Undrlyg/InstdAmt/ Value

InquiryAmount

Page 70: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 70

+<IntrBkSttlmAmt >

Interbank Settlement Amount

Undrlyg/CcyAmt/Ccy and Undrlyg/IntrBk SttlmAmt/ Value

InquiryAmount

UnableToApply camt.026.001.02 MX field tag MX Field name Msg Case

Property Name Exc Case

Map to Exc Case Work Info Section

Choice amongst +<ReqdExctnDt> Requested

Execution Date Underlyg/Reqd ExctnDt

Transaction Date

+<IntrBkSttlmDt> Interbank Settlement Date

Underlyg/IntrBkSttlm Dt

Transaction Date

<Justfn> Justification Choice amongst +<AnyInf> AnyInformation Justfn/AnyInf ** +<MssngOrIncrrctI nf>

MissingIncorrect Info

++<MssngInf> MissingInformatio n

Justfn/MssngOrIncrrc tInf/MssngInf

**

++<IncrrctInf> IncorrectInformati on

Justfn/MssngOrIncrrc tInf/ IncrrctInf

**

(Header) characters 5 and 6 of Requestor

Branch

(Header) Requestor

Inquirer BIC

(Header) Date Inquiry Date Default SWIFT

Net for Received Via field

3. System searches case database to determine if case already exists, using existing case search criteria:

a. If multiple matching cases found, route to exception workbasket for operator intervention; (SI:Common:MultipleCasesFound)

b. If one matching case found, attach M- case to existing exception case and close M- case (Resolved-Attached); (SI:Common:AttachMessage)

c. If no matching case found, jump to Step 4.

Note: **Use same property names for Exception case as Message case.

Page 71: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 71

4. If any of <Justfn><MssngOrIncrrctInf><MssngInf> is MS03 or MS04, or if any of

<Justfn><MssngOrIncrrctInf>< IncrrctInf> is IN07, IN08, or MM21, system creates an Unable to Apply Debit exception case; otherwise, system creates UnableToApply Credit exception case.

5. System auto populates exception case with details from UTAP message (see table above) (SI:Common:UTPCreatePoplulateCase)

6. System checks transaction database using case details

a. If multiple matching payment transactions are found, route to exceptions workbasket for operator intervention (SI:Common:TransferToWorkBasket); if operator can resolve the multiple transactions and attach and update one transaction to the case, return to the flow at Step 9 (SI:Common:EnrichCasewithTxn);

b. If no matching payment transaction is found, route to exceptions workbasket. (SI:Common:TransferToWorkBasket) Exceptions operator manually checks search portal. Operator clicks “research complete”:

i. If no matching transaction is found manually, System creates RejectCaseAssignment Message, RCAS_IP_Us_IP_NFND to Inquirer and closes the case (Resolved-Rejected) (SI:Common:TxnSearchNoMatch)

RCAS_IP_Us_IP_NFND: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case <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 <Justfn> +<RjctnRsn> Case Assignment Rejection

Code NFND

ii. If a matching transaction is found manually, attach and update the case, return to the flow in Step 7. (SI:Common:EnrichCasewithTxn)

c. If a matching payment transaction is found, auto-populate transaction details, attach transaction to case. (SI:Common:EnrichCasewithTxn)

7. Case has matched and updated payment transaction:

Note: processing for two work types, Unable to Apply Credit and Unable to Apply Debit, is the same from here forward.

Page 72: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 72

a. If Received Via field is equal to SWIFTNet, and if SwiftNetCaseAssignmentAssgne is not our BIC, then case may have been received in error. System sends RejectCaseAssignment camt.031 message, RCAS_IP_Us_IP_NAUT to Inquirer in background as follows: (SI:Common:RejectCaseAssignmentNAUT); resolve case with status Resolved-Rejected.

RCAS_IP_Us_IP_NAUT: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case <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 NAUT

RCAS_IP_Us_IP_NAUT: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case

Code

b. If Received Via field is equal to SWIFTNet, and if the Inquiry Party is neither the credit party nor the Receiving Bank, the sender of the UTAP message may have violated no-by-pass rule. System sends RejectCaseAssignment camt.031 message, RCAS_IP_Us_IP_NAUT, to Inquirer in background as follows: (SI:Common:RejectCaseAssignmentNAUT); resolve case with status Resolved-Rejected.

RCAS_IP_Us_IP_NAUT: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case <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 <Justfn> +<RjctnRsn> Case Assignment Rejection

Code NAUT

Page 73: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 73

8. If exception case does not contain data for these three properties, add this data in the background. Fields should not be modifiable by an operator. (SI:Common:AddUniqueCaseFields)

− Case/Id: case id

− Case/Cretr: our BIC Id

− Case/ReopCaseIndcn: (blank)

9. If Received via field is not SWIFTNet, present operator with flow action, “Select Unable to Apply justification.” Operator may select option a, or option d, or up to 10 selections from option b and 10 from option c. (SI:Common:UTAAddJustification)

a. Any

b. Missing Information (select up to 10 codes from drop down list, using add a line icon)

− MS01, MissingRemittanceInformation, RemittanceInformation is missing.

− MS02, MissingSenderToReceiverInformation, SenderToReceiverInformation is missing.

− MS03, MissingDebtor, Debtor is missing.

− MS04, MissingDebtorAccount, DebtorAccount is missing.

− MS05, MissingFirstAgent, FirstAgent is missing.

− MS06, MissingAmount, Amount is missing.

− MS07, MissingNostroVostroAccount, Nostro_VostroAccount is missing.

− MS08, MissingIntermediary, Intermediary is missing.

− MS09, MissingReimbursementAgent1, ReimbursementAgent (53) is missing.

− MS10, MissingReimbursementAgent2, ReimbursementAgent (54) is missing.

− MS11, MissingReimbursementAgent, ReimbursementAgent (55) is missing.

− MS12, MissingCreditor, Creditor is missing.

− MS13, MissingCreditorAccount, CreditorAccount is missing.

− MS14, MissingInstruction, Indicates the payment instruction (MT103) is missing.

c. Incorrect Information (select up to 10 codes from drop down list, using add a line icon)

− IN01, IncorrectRelatedReference, Related Reference is incorrect.

− IN02, IncorrectBankOperationCode, BankOperationCode is incorrect.

− IN03, IncorrectInstructionCode, InstructionCode is incorrect.

− IN04, IncorrectRequestedExecutionDate, RequestedExecutionDate is incorrect.

− IN05, IncorrectValueDate, ValueDate is incorrect.

Page 74: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 74

− IN06, IncorrectInterbankSettledAmount, InterbankSettledAmount is incorrect.

− IN07, IncorrectDebtor, Debtor is incorrect.

− IN08, IncorrectDebtorAccount, DebtorAccount is incorrect.

− IN09, IncorrectReceiverCorrespondent, ReceiverCorrespondent is incorrect.

− IN10, IncorrectThirdReimbursementInstitution, ThirdReimbursementInstitution is incorrect.

− IN11, IncorrectPaymentScheme, PaymentScheme is incorrect.

− IN12, IncorrectAccountOfBeneficiaryInstitution, AccountOfBeneficiaryInstitution is incorrect.

− IN13, IncorrectCreditor, Creditor is incorrect.

− IN14, IncorrectCreditorAccount, CreditorAccount is incorrect.

− IN15, IncorrectRemittanceInformation, RemittanceInformation is incorrect.

− IN16, IncorrectPaymentPurpose, PaymentPurpose is incorrect.

− IN17, IncorrectDetailsOfCharges, DetailsOfCharges is incorrect.

− IN18, IncorrectSenderToReceiverInformation, SenderToReceiverInformation is incorrect.

− IN19, IncorrectInstructionForFinalAgent, InstructionForFinalAgent is incorrect.

− MM20, MismatchCreditorNameAccount, Name and Account of Creditor mismatched.

− MM21, MismatchDebtorNameAccount, Name and Account of Debtor mismatched.

− MM22, MismatchFinalAgentNameAccount, Name and Account of FinalAgent mismatched.

− MM23, InsufficientDebtorDetails, Insufficient or incoherent details about the debtor with respect to regulatory requirements.

− MM24, InsufficientCreditorDetails, Insufficient or incoherent details about the creditor with respect to regulatory requirements.

d. Process case Step-by-Step

10. Operator is presented with five options:

a. Modify the payment (SI:Common:UTAModPayment)

− Systems sends Resolution message to the Inquiry Party, ROIN_IP_Us_IP_MWFW;

− Update <ReopCaseIndctn> flag to true;

− Present operator with RTMP template to Inquiry Party, RTMP_IP_Us_IP;

− System places case in Pending-Cust status;

Page 75: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 75

b. Send Additional Payment Information message to resolve case (SI:Common:UTAAddPmt)

− Present operator with APIN to Inquiry Party, APIN_IP_Us_IP. Operator needs to enter data necessary to resolve case.

− System sends Resolution message to Inquiry party, ROIN_IP_Us_IP_INFO.

− Resolve case.

c. Forward the UnableToApply message (SI:Common:UTAForwardUTAP)

− If there is a Sending Bank in the payment transaction, system sends UTAP to Sending Bank, UTAP_SB_Us_SB; send NOCA to IP,

− NOCA_IP_Us_SB_FTHI

− If there is no Sending Bank in the payment transaction, system sends UTAP to Debit Party, UTAP_DP_Us_DP; send NOCA to IP,

− NOCA_IP_Us_DP_FTHI

− System places case in Pending-Cust status

d. Payment was executed incorrectly, cancel payment (SI:Common:UTACancelPmt)

− If there is a Receiving Bank in the payment transaction, send Resolution message to Receiving Bank, ROIN_RB_Us_RB_CWFW; send RTCP to RB, RTCP_RB_Us_RB_UPAY; system updates status to Pending-Cust;

− If there is no Receiving Bank, send Resolution message to Credit Party, ROIN_CP_Us_CP_CWFW; send DARQ to Credit Party,

− DARQ_CP_Us_CP; note that <ReopCaseIndctn> flag is set to Yes

e. Process case Step-by-Step (SI:Common:StepByStep)

11. Add assignment to case to process receipt of case management messages. “Process new case management message.”

ROIN_IP_Us_IP_MWFW: ResolutionOfInvestigation camt.029.001.02

MX field tag MX 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

Page 76: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 76

ROIN_IP_Us_IP_MWFW: ResolutionOfInvestigation camt.029.001.02

MX field tag MX Tag Description SI Field Name +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Sts> Status +<Conf> Confirmation MWFW

RTMP_IP_Us_IP: RequestToModifyPayment camt.007.002.02 MX field tag MX 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 +<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)

APIN_IP_Us_IP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX 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 +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Undrlyg> Underlying +<OrgnlMsgNmId> Original Message Name

ID Trantype/Insttype

+<OrgnlInstrId> Original Instruction ID Transaction Reference

Page 77: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 77

APIN_IP_Us_IP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX 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

<Inf> Information (allow all fields of <Inf> block to be available for data entry)

ROIN_IP_Us_IP_INFO: ResolutionOfInvestigation camt.029.001.02 MX field tag MX 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 INFO

UTAP_SB_Us_SB: UnableToApply camt.026.001.02 MX field tag MX Field name Msg Case Property Name <Assgnmt> Assignment +<Id> Id Our Exception Case Id +<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

Identification 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

Page 78: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 78

UTAP_SB_Us_SB: UnableToApply ca mt.026.001.02 MX field tag MX Field name Msg Case Property Name +<IntrBkSttlmDt> Interbank Settlement Date Transaction Date <Justfn> Justification Choice amongst +<AnyInf> AnyInformation Justfn/AnyInf +<MssngOrIncrrctIn f>

MissingOrIncorrectInfo

++<MssngInf> MissingInformation Justfn/MssngOrIncrrctInf/Ms sngInf

++<IncrrctInf> IncorrectInformation Justfn/MssngOrIncrrctInf/ IncrrctInf

NOCA_IP_Us_SB_FTHI: NotificationOfCaseAssignment MX camt.030.001.02 MX field tag MX 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

UTAP_DP_Us_DP: UnableToApply camt.026.001.02 MX field tag MX Field name Msg Case Property 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

Identification TranType/ Insttype

+<OrgnlInstrId> Original Instruction Identification

Transaction Reference

Page 79: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 79

Choice amongst

UTAP_DP_Us_DP: UnableToApply ca mt.026.001.02 MX field tag MX Field name Msg Case Property Name +<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 +<MssngOrIncrrctIn f>

MissingOrIncorrectInfo

++<MssngInf> MissingInformation Justfn/MssngOrIncrrctInf/Ms sngInf

++<IncrrctInf> IncorrectInformation Justfn/MssngOrIncrrctInf/ IncrrctInf

NOCA_IP_Us_DP_FTHI: NotificationOfCaseAssignment MX camt.030.001.02 MX field tag MX 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 Debit Party +<CreDtTm> Create Date/Time System Date/Time <Ntfctn> Notification +<Justfn> Case Forward Notification Code FTHI

ROIN_RB_Us_RB_CWFW: ResolutionOfInvestigation camt.029.001.02 MX field tag MX 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

Page 80: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 80

ROIN_RB_Us_RB_CWFW: ResolutionOfInvestigation camt.029.001.02 MX field tag MX Tag Description SI Field Name +<Conf> Confirmation CWFW

RTCP_RB_Us_RB_UPAY: RequestToCancelPayment camt.008.002.02

MX field tag MX 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 +<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

ROIN_CP_Us_CP_CWFW: ResolutionOfInvestigation camt.029.001.02 MX field tag MX 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

DARQ_CP_Us_CP_UPAY: DebitAuthorisationRequest camt.037.001.02 MX field tag MX Tag Description SI Field Name

Page 81: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 81

<Assgnmt> Assignment <Id> Assignment ID Our Exception Case Id <Assgnr> Assigner Our BIC <Assgne> Assignee BIC/BEI of Credit Party <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

ClaimsNonReceipt, MX camt.027 1. System receives XML message ClaimsNonReceipt message, MX camt.027

2. System creates M- case with the following mapping from message. All fields should be mapped into comparably named fields in the work area of the M- case, so operator reviewing message can review with tag/data pairs rather than raw message. (SI:Common:CreateMsgCase)

Claims Non Receipt camt.027.001.02 MX field tag MX Field name Msg Case Property

Name Exc Cas e

Map to Exc Case Work Info Section

<Assgnmt> Assignment +<Id> Id Assgnmt/Id ** +<Assgnr> Assigner Assgnmt/Assgnr ** +<Assgne> Assignee Assignmt/Assgne ** +<CreDtTm> Create Date/Time Assignmt/CreDtTm ** <Case> Case +<Id> Creator’s/ Case ID Case/Id ** +<Cretr> Case Creator Case/Cretr ** +<ReopCaseIndc Case Reopen Case/ReopCaseIndctn **

Page 82: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 82

Claims Non Rec eipt camt.027.001.02 MX field tag MX Field name Msg Case Property

Name Exc Cas e

Map to Exc Case Work Info Section

tn> Indicator <Undrlyg> Underlying +<OrgnlMsgNmI d>

Original Message Name Identification

Undrlyg/OrgnlMsgNm Id

TranType/ Insttype

+<OrgnlInstrId> Original Instruction Identification

Undrlyg/OrgnlInstrId Transaction Reference

Choice amongst +<InstdAmt> Instructed Amount Undrlyg/CcyAmt/Ccy

and Undrlyg/InstdAmt/ Value

InquiryAmount

+<IntrBkSttlmA mt>

Interbank Settlement Amount

Undrlyg/CcyAmt/Ccy and Undrlyg/IntrBk SttlmAmt/ Value

InquiryAmount

Choice amongst +<ReqdExctnDt >

Requested Execution Date

Underlyg/Reqd ExctnDt

Transaction Date

+<IntrBkSttlmDt >

Interbank Settlement Date

Underlyg/IntrBkSttlm Dt

Transaction Date

<MssngCover> Missing Cover +<MssngCoverIn dctn>

Missing Cover Indication

MssngCover/MssngCo ver Indctn

**

(Header) characters 5 and 6 of Requestor

Branch

(Header) Requestor

Inquirer BIC

(Header) Date Inquiry Date Default SWIFT

Net for Received Via field

3. System searches case database to determine if case already exists, using existing case search criteria:

a. If multiple matching cases found, route to exception workbasket for operator intervention; (SI:Common:MultipleCasesFound)

b. If one matching case found, attach M- case to existing exception case and close M- case (Resolved-Attached); (SI:Common:AttachMessage)

Note: **Use same property names for Exception case as Message case

Page 83: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 83

c. If no matching case found, jump to Step 4. 4. System creates a Beneficiary Claims Non-Receipt exception case.

5. System auto populates exception case with details from CNRC message (see table above) (SI:BCNR:CreatePopulateCase)

6. System checks transaction database using case details

a. If multiple matching payment transactions are found, route to exceptions workbasket for operator intervention (SI:Common:TransferToWorkBasket); if operator can resolve the multiple transactions and attach and update one transaction to the case, return to the flow at Step 9 (SI:Common:EnrichCasewithTxn);

b. If no matching payment transaction is found, route to exceptions workbasket. (SI:Common:TransferToWorkBasket) Exceptions operator manually checks search portal. Operator clicks “research complete”:

i. 8If no matching transaction is found manually, System creates RejectCaseAssignment Message, RCAS_IP_Us_IP_NFND to Inquirer and closes the case (Resolved-Rejected) (SI:Common:TxnSearchNoMatch)

RCAS_IP_Us_IP_NFND: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case <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 <Justfn> +<RjctnRsn> Case Assignment Rejection

Code NFND

ii. If a matching transaction is found manually, attach and update the case, return to the flow in Step 9. (SI:Common:EnrichCasewithTxn)

c. If a matching payment transaction is found, auto-populate transaction details, attach transaction to case. (SI:Common:EnrichCasewithTxn)

7. Case has matched and updated payment transaction:

a. If Received Via field is equal to SWIFTNet, and if SwiftNetCaseAssignmentAssgne is not our BIC, then case may have been received in error. System sends RejectCaseAssignment camt.031 message, RCAS_IP_Us_IP_NAUT to Inquirer in background as follows: (SI:Common:RejectCaseAssignmentNAUT); resolve case with status of Resolve-Rejected.

Page 84: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 84

RCAS_IP_Us_IP_NAUT: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case <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

RCAS_IP_Us_IP_NAUT: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Justfn> Justification +<RjctnRsn> Case Assignment Rejection

Code NAUT

b. If Received Via field is equal to SWIFTNet, and if the <MssngCoverIndctn> flag is No or blank, and the Inquiry Party is neither the debit party nor the Sending Bank, or if the

<MssngCoverIndctn> flag is Yes, and the Inquiry Party is not the Receiving Bank, then the sender of the CNRC message may have violated the no-by-pass rule.

System sends RejectCaseAssignment camt.031 message, RCAS_IP_Us_IP_NAUT, to Inquirer in background (SI:BCNR:RejectCaseAssignmentNAUT)

System resolves case with Resolve-Rejected.

c. If Received Via is equal to SWIFTNet, and neither a nor b are true, go to step 10.

RCAS_IP_Us_IP_NAUT: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case <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 <Justfn> +<RjctnRsn> Case Assignment Rejection

Code NAUT

Page 85: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 85

8. If exception case does not contain data for these three properties, add this data in the background. Fields should not be modifiable by an operator. (SI:Common:AddUniqueCaseFields)

− Case/Id: case id

− Case/Cretr: our BIC Id

− Case/ReopCaseIndcn: False

9. If Received via field is not SWIFTNet, present operator with an assignment, “Is this case a missing cover?” Populate Yes or No answer to <MssngCoverIndctn> field.

10. If <MssngCoverIndctn> is true, present operator with an assignment, “Process case Step-By- Step.” (SI:BCNR:MssngCover)

11. If <MssngCoverIndctn> flag is false or blank, Operator needs to determine if the payment was made correctly. Present operator with an assignment, “Was payment made correctly according to original instructions?” with the following two Flow Actions: (SI:BCNR:WasPmtCorrect)

a. Payment was made correctly

b. Payment was made incorrectly

c. Local Action: Process Case step by step

12. If operator selects “Payment was made correctly” (SI:BCNR:PmtCorrect)

a. If there is a Receiving Bank Party in the transaction,

i. System sends CNRC to the Receiving Bank, CNRC_RB_Us_RB

ii. System sends NotificationOfCaseAssignment to Inquirer party,

NOCA_IP_Us_RB_FTHI

iii. System places case in Pending-Cust status. Flow continues based on receipt of ResolutionOfInvestigation message.

CNRC_RB_Us_RB: Claims Non Receipt camt.027.001.02 MX field tag MX Field name Msg Case Property 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

Page 86: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 86

<Undrlyg> Underlying +<OrgnlMsgNmId> Original Message Name

Identification 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

NOCA_IP_Us_RB_FTHI: NotificationOfCaseAssignment MX camt.030.001.02 MX field tag MX 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_RB_F THI: NotificationOfCaseAssign ment MX camt.030.001.02 MX field tag MX Tag Description SI Field Name <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

b. If there is no Receiving Bank party in the transaction,

i. Present Operator with Additional Payment Information message template, camt.028, to Credit Party, ADPI_CP_Us_CP, with the expectation that the additional information will resolve the case. (Only part of template is shown; operator will need to add any information available to ADPI message.)

ii. System sends NotificationofCaseAssignment, NOCA_IP_Us_CP_SAIN (Sent Additional Information.)

iii. System sends ROIN_IP_Us_IP_INFO, and changes status to Resolved- Complete.

Page 87: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 87

APIN_CP_Us_CP: AdditionalPaymentInformation camt.028.001.02 MX field tag MX 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

NOCA_IP_Us_CP_SAIN: NotificationOfCaseAssignment MX camt.030.001.02

MX field tag MX Tag Description SI Field Name <Hdr> Header +<Id> ID of Report Our Exception Case Id

Page 88: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 88

NOCA_IP_Us_CP_SAIN: NotificationOfCaseAssignment MX camt.030.001.02

MX field tag MX Tag Description SI Field Name +<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 +<ReopCaseIndct n>

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

ROIN_IP_Us_IP_INFO: ResolutionOfInvestigation camt.029 .001.02 MX field tag MX 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

13. If operator selects “payment was made incorrectly” (SI:BCNR:PmtIncorrect)

a. If there is a Receiving Bank Party in the transaction

i. System sends ResolutionOfInvestigation message, camt.029, to Inquiry Party, ROIN_IP_Us_RB_CWFW.

ii. System changes <ReopCaseIndctn> flag to true.

iii. System sends RequestToCancelPayment message, camt.008 to Receiving Bank, RTCP_RB_Us_RB_UPAY, with same case creator and case creator ID.

iv. System sends NotificationOfCaseAssignment to Inquiry Party, NOCA_IP_Us_RB_CANC.

Page 89: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 89

v. System changes status to Pending-Cust, and flow continues upon receipt of Resolution message from Receiving Bank.

ROIN_IP_Us_RB_CWFW: ResolutionOfInvestigation camt.029.001.02 MX field tag MX Tag Description SI Field Name <Assgnmt> Assignment

ROIN_IP_Us_RB_ CWFW: ResolutionOfInvestigation camt.029.001.02 MX field tag MX Tag Description SI Field Name +<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

RTCP_RB_Us_RB_UPAY: RequestToCancelPayment camt.008.002.02

MX field tag MX 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 +<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

Page 90: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 90

NOCA_IP_Us_RB_CNCL: NotificationOfCaseAssignment MX camt.030.001.02 MX field tag MX Tag Description SI Field Name <Hdr> Header +<Id> ID of Report Our Exception Case Id +<Fr> From Our BIC +<To> To Inquirer BIC

NOCA_IP_Us_RB_CN CL: NotificationOfCaseAssignm ent MX camt.030.001.02 MX field tag MX Tag Description SI Field Name +<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 CNCL

b. If there is no Receiving Bank Party in the transaction,

i. System sends ResolutionOfInvestigation messages, camt.029, to Inquiry Party, ROIN_IP_Us_CP_CWFW.

ii. System changes <ReopCaseIndctn> flag to true.

iii. System sends DebitAuthorizationRequest camt.037, DARQ_CP_Us_CP_UPAY, to Credit Party

iv. System sends NotificationOfCaseAssignment, NOCA_IP_Us_CP_DTAU, with code DTAU (Request Debit Authority) to Inquirer. (SI:Common:DARwithNOCA).

v. Flow continues upon receipt of Debit Authorisation Response message.

14. Add assignment to case to process receipt of case management messages. “Process new case management message.”

ROIN_IP_Us_CP_CWFW: ResolutionOfInvestigation camt.029.001.02 MX field tag MX 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

Page 91: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 91

<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

DARQ_CP_Us_CP_UPAY: DebitAuthorisationRequest camt.037.001.02 MX field tag MX 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 camt.037.001.02 MX field tag MX 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

NOCA_IP_Us_CP_DTAU: NotificationOfCaseAssignment MX camt.030.001.02

MX field tag MX 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

Page 92: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 92

+<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

Debit Authorization Response, MX.camt.036 1. System receives camt.036.001 DebitAuthorisationResponse message.

2. System creates M- case with the following mapping from message. All fields should be mapped into comparably named fields in the work area of the M- case. (SI:Common:CreateMsgCase)

Debit Authorisation Response, camt.036.001.01 MX field tag MX Field name Msg Case

Property Name Map to Misc Exc Case

<Assgnmt> Assignment +<Id> Identification Assgnmt/Id +<Assgnr> Assigner Assgnmt/Assgnr +<Assgne> Assignee Assignmt/Assgne +<CreDtTm> Create Date/Time Assignmt/CreDtTm <Case> Case +<Id> Creator’s/ Case ID Case/Id *** +<Cretr> Case Creator Case/Cretr *** +<ReopCaseIndctn> Case Reopen

Indicator Case/ReopCaseIndc tn

***

<Conf> Confirmation +<DbtAuthstn> Debit Authorisation Conf/DbtAuthstn +<AmtToDbt> Amount To Debit Conf/AmtToDbt +<ValDtToDbt> Value date To

Debit Conf/ValDtToDbt

+<Rsn> Reason Conf/Rsn

3. System searches case database to determine if case already exists, using existing case search criteria

a. If multiple matching cases found, route to exception workbasket for operator intervention; (SI:Common:MultipleCasesFound)

b. If no matching case found, system creates Miscellaneous exception case with the mapping indicated above (SI:Common:MsgNoMatch)

i. Send Reject Case Assignment message to Inquiry Party, RCAS_IP_Us_IP_UKNW

Note: *** Map fields to Miscellaneous case only

Page 93: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 93

ii. Close the case with status Resolved-Rejected (SI:Common:RejectCaseAssignmentUKNW))

RCAS_IP_Us_IP_UKNW: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case <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

RCAS_IP_Us_I P_UKNW: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Justfn> +<RjctnRsn> Case Assignment Rejection

Code UKNW

c. If one matching case found, attach M- case to existing exception case and close M- case (Resolved-Attached); (SI:Common:AttachMessage)

4. If <DbtAuthstn> is “TRUE” then case goes to accounting workbasket

a. After accounting is complete, present operator with Resolution of Investigation message to Inquirer party, ROIN_IP_Us_IP_CNCL. (SI:Common:AcctgROIN)

ROIN_IP_Us_IP_CNCL: ResolutionOfInvestigation camt.029 MX 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

ConfirmationCode CNCL

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

Settlement Amount (Required field, must be entered by operator)

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

++<ClrChanl> Clearing Channel

b. Close case with Resolved-Complete status. 5. If <DbtAuthstn> is “FALSE,” present operator with Resolution of Investigation message to

Page 94: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 94

Inquirer party, ROIN_IP_Us_IP_Last. (SI:Common:ROINLast);

a. Operator needs to select Cancellation Rejection Reason from drop down list.

ROIN_IP_Us_IP_Last: ResolutionOfInvestigation camt.029 MX 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

ROIN_IP_Us_IP_Last: ResolutionOfInvestigation camt.029 MX field tag Field name SI Field Name +<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)

b. Close case with Resolved-Rejected status.

Debit Authorization Request, MX.camt.037 1. System receives camt.037.001 DebitAuthorisationRequest message.

2. System creates M- case with the following mapping from message. All fields should be mapped into comparably named fields in the work area of the M- case. (SI:Common:CreateMsgCase)

Debit Authorisation Request, camt.037.001.02 MX field tag MX Field name Msg Case Property

Name Map to Misc Exc Case

<Assgnmt> Assignment +<Id> Identification Assgnmt/Id +<Assgnr> Assigner Assgnmt/Assgnr +<Assgne> Assignee Assignmt/Assgne +<CreDtTm> Create Date/Time Assignmt/CreDtTm <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 Identification Undrlyg/OrgnlMsgNm Id

Page 95: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 95

+<OrgnlInstrId> Original Instruction Identification

Undrlyg/OrgnlInstrId

Choice amongst +<InstdAmt> Instructed Amount Undrlyg/CcyAmt/Ccy

and Undrlyg/InstdAmt/ Value

+<IntrBkSttlmAmt> Interbank Settlement Amount

Undrlyg/CcyAmt/Ccy and Undrlyg/IntrBk SttlmAmt/ Value

Choice amongst +<ReqdExctnDt> Requested Execution

Date Underlyg/Reqd ExctnDt

+<IntrBkSttlmDt> Interbank Settlement Date

Underlyg/IntrBkSttlmD t

Debit A uthorisation Request, camt.037.001.02 MX field tag MX Field name Msg Case Property

Name Map to Misc Exc Case

<Dtl> Detail +<CxlRsn> CancellationReason Dtl/CxlRsn +<AmtToDbt> Amount To Debit Dtl/AmtToDbt +<ValDtToDbt> Value Date To Debit Dtl/ValDtToDbt

3. System searches case database to determine if case already exists, using existing case search criteria

a. If multiple matching cases found, route to exception workbasket for operator intervention; (SI:Common:MultipleCasesFound)

b. If no matching case found, system creates Miscellaneous exception case, mapping those items marked with an asterisk (***) to identically named fields in the exception case (SI:Common:MsgNoMatch);

i. Send Reject Case Assignment message to Inquiry Party, RCAS_IP_Us_IP_UKNW

ii. Close the case with status Resolved-Rejected (SI:Common:RejectCaseAssignmentUKNW)).

RCAS_IP_Us_IP_UKNW: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case <Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC +<Assgne> Assignee Inquirer BIC +<CreDtTm> Create Date/Time System Date/Time

Note: ***Map fields to Miscellaneous case only.

Page 96: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 96

<Case> +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn <Justfn> +<RjctnRsn> Case Assignment Rejection

Code UKNW

c. If one matching case is found, attach message to existing case, route case to exceptions workbasket for Step by Step processing.(SI:Common:AuxMsgStbySt)

ResolutionOfInvestigation, MX.camt.029 1. System receives camt.029.001 ResolutionOfInvestigation message.

2. System creates M- case with the following mapping from message. All fields should be mapped into comparably named fields in the work area of the M- case. (SI:Common:CreateMsgCase)

ResolutionOfInvestigation camt.029.001 MX field tag MX Field name Msg Case Property

Name Map to Misc Exc Case

<Assgnmt> Assignment +<Id> Assignment ID Assgnmt/Id +<Assgnr> Assigner Assgnmt/Assgnr +<Assgne> Assignee Assgnmt/Assgne +<CreDtTm> Create Date/Time Assgnmt/CredtTm <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 Choice Amongst +<Conf> Investigation Execution

Confirmation Code Sts/Conf

+<AssgnmtCxlConf >

Assignment Cancellation Confirmation

Sts/AssgnmtCxlConf

+<RjctdMod> Rejected Modification Sts/RjctdMod +<RjctdCxl> Rejected Cancellation ++<RsnCd> Reason Code Sts/RjctdCxl/RsnCd ++<Rsn> Reason Sts/RjctdCxl/Rsn +<DplctOf> Duplicate Of ++<Id> Identification Sts/DplctOf/Id ++<Cretr> Creator Sts/DplctOf/Cretr ++<ReopCaseIndct n>

Reopen Case Indicator Sts/DplctOf/ReopCaseInd ctn

+<RtrInf> Return Information

Page 97: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 97

++<RtrdIntrBkSttl mAmt>

Returned Interbank Settlement Amount

Sts/RtrInf/RtrdIntrBkSttl mAmt

++<IntrBkSttlmDt >

Interbank Settlement Date

Sts/RtrInf/IntrBkSttlmDt

++<ClrChanl> Clearing Channel Sts/RtrInf/ClrChanl +<CrrctnTx> Corrected Transaction ++<IntstrId> Instruction Id Sts/CrrctnTx/InstrId Choice Amongst ++<InstdAmt> Instructed Amount Sts/CrrctnTx/InstdAmt ++<IntrBkSttlmAm t>

Interbank Settlement Amount

Sts/CrrctnTx/IntrBkSttlm Amt

Choice Amongst

ResolutionOfInvestigatio n camt.029.001 MX field tag MX Field name Msg Case Property

Name Map to Misc Exc Case

++<ReqdExctnDt> Requested Execution Date

Sts/CrrctnTx/ReqdExctn Dt

++<IntrBkSttlmDt >

Interbank Settlement Date

Sts/CrrctnTx/IntrBkSttlm Dt

(Header) characters 5 and 6 of Requestor

(Header) Requestor (Header) Date

3. System searches case database to determine if case already exists, using existing case search criteria

a. If multiple matching cases found, route to exception workbasket for operator intervention; (SI:Common:MultipleCasesFound)

b. If no matching case found, system creates Miscellaneous exception case, mapping those items marked with an asterisk (**) to identically named fields in the exception case (SI:Common:MsgNoMatch);

i. Send Reject Case Assignment message to Inquiry Party, RCAS_IP_Us_IP_UKNW

ii. Close the case with status Resolved-Rejected (SI:Common:RejectCaseAssignmentUKNW).

Note: ***Map fields to Miscellaneous case only

Page 98: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 98

RCAS_IP_Us_IP_UKNW: RejectCaseAssignment camt.031

MX field tag MX Field name Map from Exception Case

<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 <Justfn> +<RjctnRsn> Case Assignment Rejection

Code UKNW

c. If one matching case is found, attach message to existing case. (SI:Common:AttachMsg) 4. If Assignment/Assignee field is not our BIC, we may have received ROIN in error. Place case in

status Pending-Review and route to exception workbasket for Step by Step processing. (SI:Common:AuxMsgstBySt)

5. If case type is Cancellation Request, and <Sts><Conf> is CNCL, route case to accounting workbasket to complete accounting. When accounting in complete, present operator with ROIN_IP_Us_IP_CNCL to Inquiry Party. Operator will add corrected transaction information. Close case with Resolved-Complete. (SI:Cancel:AcctgROINCNCL)

6. If case type is Cancellation Request, and <Sts><Conf> is not CNCL, route to exception workbasket for Step by Step processing. (SI:Cancel:AuxMsgstBySt)

7. If <Sts><Conf> is MWFW, CWFW, or UWFW, and Case Creator is not our BIC, present operator with ROIN_IP_Us_IP_Last to Inquiry Party, and operator selects appropriate resolution status (SI:Common:ROINLast.) Note that template pulls <Sts><Conf> from received ROIN message

8. If case type is Incorrect Payment, route item to accounting workbasket to complete accounting entry; When accounting in complete, present operator with ROIN_IP_Us_IP_Last to Inquiry Party. Operator will add corrected transaction information. Close case with Resolved-Complete. (SI:Cancel:AcctgROINLast)

9. If case type is Incorrect Amount, and the <Sts><Conf> is MODI, route item to accounting workbasket to complete accounting entry; When accounting in complete, present operator with ROIN_IP_Us_IP_Last to Inquiry Party. Operator will add corrected transaction information. Close case with Resolved-Complete. (SI:Cancel:AcctgROINLast)

10. <Sts><Conf> is MODI or INFO, present operator with ROIN_IP_Us_IP_Last to Inquiry Party, and operator selects appropriate resolution status (SI:Common:ROINLast.) Note that template pulls <Sts><Conf> from received ROIN message

11. For all other case types, if <Sts><Conf> is ICOV, IPAY, or MCOV, route item to accounting

Page 99: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 99

workbasket to complete accounting entry; When accounting in complete, present operator with ROIN_IP_Us_IP_Last to Inquiry Party. Operator will add corrected transaction information. Close case with Resolved-Complete. (SI:Cancel:AcctgROINLast)

12. If <RjctdMod> contains data, route item to exception workbasket for Step by Step processing. (SI:Common:AuxMsgStBySt)

13. If <DplctOf> contains data, route item to exception workbasket for Step by Step processing. (SI:Common:AuxMsgStBySt)

Page 100: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 100

NotificationOfCaseAssignment, MX.camt.030 1. System receives camt.030.001 NotificationOfCaseAssignment message.

2. System creates M- case with the following mapping from message. All fields should be mapped into comparably named fields in the work area of the M- case. (SI:Common:CreateMsgCase)

NotificationOfCaseAssignment camt.030.001.02 MX field tag MX Field name Msg Case Property

Name Map to Misc Exc Case

<Hdr> Header +<Id> ID of Report Hdr/Id +<Fr> From Hdr/Fr +<To> To Hdr/To +<CreDtTm> Create Date/Time Hdr/CreDtTm <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 Assgnmt/Id +<Assgnr> Assigner Assgnmt/Assgnr +<Assgne> Assignee Assgnmt/Assgne +<CreDtTm> Create Date/Time Assgnmt/CredtTm <Ntfctn> Notification +<Justfn> Case Forward

Notification Code Ntfctn/Justfn

3. System searches case database to determine if case already exists, using existing case search criteria

a. If multiple matching cases found, route to exception workbasket for operator intervention; (SI:Common:MultipleCasesFound)

b. If no matching case found, system creates Miscellaneous exception case, mapping those items marked with an asterisk (***) to identically named fields in the exception case (SI:Common:MsgNoMatch);

i. System sends Reject Case Assignment message to Inquiry Party, RCAS_IP_Us_IP_UKNW

ii. Close the case with status Resolved-Rejected (SI:Common:RejectCaseAssignmentUKNW).

Note: ***Map fields to Miscellaneous case only

Page 101: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 101

RCAS_IP_Us_IP_UKNW: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case <Assgnmt> Assignment +<Id> Assignment ID Our Exception Case Id +<Assgnr> Assigner Our BIC

RCAS_IP_Us_IP_UKNW: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case +<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 <Justfn> +<RjctnRsn> Case Assignment Rejection

Code UKNW

c. If one matching case is found, attach message to existing case. (SI:Common:AttachMsg) 4. If Received via field of exception case is equal to SWIFTNet, system sends NOCA to Inquiry

Party in background, NOCA_IP. Note that the Assignment and Notification block data from the message must be copied to the outbound message. Because subsequent Notification messages could be received, these fields will not be copied into the UI of the case. (SI:Common:FrowardNOCAIP)

NOCA_IP : NotificationOfCaseAssignment MX camt.030 MX field tag MX 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

5. If Received via field of exception case is not equal to SWIFTNet, present operator with MT 196. Operator decides whether to send MT notification Include option for operator to cancel MT message. (SI:Common:MT196orCancel)

Page 102: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 102

AdditionalPaymentInformation, MX.camt.028 1. System receives camt.028.001 AdditionalPaymentInformation message.

2. System creates M- case with the following mapping from message. All fields should be mapped into comparably named fields in the work area of the M- case. (SI:Common:CreateMsgCase). (Full message is not shown here; see template in RequestToModifyPayment section)

AdditionalPaymentInformation camt.028.001.02 MX field tag MX Field name Msg Case Property

Name Map to Misc Exc Case

<Assgnmt> Assignment +<Id> Id Assgnmt/Id +<Assgnr> Assigner Assgnmt/Assgnr +<Assgne> Assignee Assgnmt/Assgne +<CreDtTm> Create Date/Time Assgnmt/CredtTm <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

3. System searches case database to determine if case already exists, using existing case search criteria

a. If multiple matching cases found, route to exception workbasket for operator intervention; (SI:Common:MultipleCasesFound)

b. If no matching case found, system creates Miscellaneous exception case, mapping those items marked with an asterisk (**) to identically named fields in the exception case (SI:Common:MsgNoMatch);

i. System sends Reject Case Assignment message to Inquiry Party, RCAS_IP_Us_IP_UKNW.

Note: ***Map fields to Miscellaneous case only

Page 103: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 103

ii. Close the case with status Resolved-Rejected (SI:Common:RejectCaseAssignmentUKNW).

RCAS_IP_Us_IP_UKNW: RejectCaseAssignment camt.031

MX field tag MX Field name Map from Exception Case <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 <Justfn> +<RjctnRsn> Case Assignment Rejection

Code UKNW

c. If one matching case is found, attach message to existing case, route case to exceptions workbasket for Step by Step processing. (SI:Common: AuxMsgStbySt)

RejectCaseAssignment, MX.camt.031 1. System receives camt.031.001 RejectCaseAssignment message.

2. System creates M- case with the following mapping from message. All fields should be mapped into comparably named fields in the work area of the M- case. (SI:Common:CreateMsgCase).

RejectCaseAssignment, camt.031.001.02 MX field tag MX Field name Msg Case Property

Name Map to Misc Exc Case

<Assgnmt> Assignment +<Id> Assignment ID Assgnmt/Id +<Assgnr> Assigner Assgnmt/Assgnr +<Assgne> Assignee Assgnmt/Assgne +<CreDtTm> Create Date/Time Assgnmt/CredtTm <Case> +<Id> Creator’s Case ID Case/Id *** +<Cretr> Case Creator Case/Cretr *** +<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn *** <Justfn> +<RjctnRsn> Case Assignment

Rejection Code Justfn/RjctnRsn

Note: ***Map fields to Miscellaneous case only

Page 104: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 104

a. System searches case database to determine if case already exists, using existing case search criteria.

b. If multiple matching cases found, route to exception workbasket for operator intervention; (SI:Common:MultipleCasesFound)

c. If no matching case found, system creates Miscellaneous exception case, mapping those items marked with an asterisk (**) to identically named fields in the exception case (SI:Common:MsgNoMatch);

i. System sends Reject Case Assignment message to Inquiry Party, RCAS_IP_Us_IP_UKNW.

ii. Close the case with status Resolved-Rejected (SI:Common:RejectCaseAssignmentUKNW).

RCAS_IP_Us_IP_UKNW: RejectCaseAssignment camt.031.001.02

MX field tag MX Field name Map from Exception Case <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 <Justfn> +<RjctnRsn> Case Assignment Rejection

Code UKNW

d. If one matching cases is found, attach message to existing case, route case to exceptions workbasket for Step by Step processing. (SI:Common: AuxMsgStbySt)

CancelCaseAssignment, MX.camt.032 1. System receives camt.032.001 CancelCaseAssignment message.

2. System creates M- case with the following mapping from message. All fields should be mapped into comparably named fields in the work area of the M- case. (SI:Common:CreateMsgCase).

CancelCaseAssignment, camt.032.001.01 MX field tag MX Field name Msg Case Property

Name Map to Misc Exc Case

<Assgnmt> Assignment +<Id> Assignment ID Assgnmt/Id +<Assgnr> Assigner Assgnmt/Assgnr +<Assgne> Assignee Assgnmt/Assgne +<CreDtTm> Create Date/Time Assgnmt/CredtTm <Case> +<Id> Creator’s Case ID Case/Id *** +<Cretr> Case Creator Case/Cretr ***

Page 105: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 105

+<ReopCaseIndctn> Case Reopen Indicator Case/ReopCaseIndctn ***

3. System searches case database to determine if case already exists, using existing case search criteria

a. If multiple matching cases found, route to exception workbasket for operator intervention; (SI:Common:MultipleCasesFound)

b. If no matching case found, system creates Miscellaneous exception case, mapping those items marked with an asterisk (**) to identically named fields in the exception case (SI:Common:MsgNoMatch);

i. System sends Reject Case Assignment message to Inquiry Party, RCAS_IP_Us_IP_UKNW.

ii. Close the case with status Resolved-Rejected (SI:Common:RejectCaseAssignmentUKNW).

RCAS_IP_Us_IP_UKNW: RejectCaseAssignment camt.031.001.02

MX field tag MX Field name Map from Exception Case <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 <Justfn> +<RjctnRsn> Case Assignment Rejection

Code UKNW

c. If one matching case is found, attach message to existing case, route case to exceptions

workbasket for Step by Step processing. (SI:Common: AuxMsgStbySt)

RequestForDuplicate, MX.camt.033 1. System receives camt.033.001 RequestForDuplicate message.

2. System creates M- case with the following mapping from message. All fields should be mapped into comparably named fields in the work area of the M- case. (SI:Common:CreateMsgCase).

RequestForDuplicate, camt.033.001.02 MX field tag MX Field name Msg Case Property

Name Map to Misc Exc Case

<Assgnmt> Assignment +<Id> Assignment ID Assgnmt/Id

Note: ***Map fields to Miscellaneous case only

Page 106: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 106

+<Assgnr> Assigner Assgnmt/Assgnr +<Assgne> Assignee Assgnmt/Assgne +<CreDtTm> Create Date/Time Assgnmt/CredtTm <Case> +<Id> Creator’s Case ID Case/Id ** +<Cretr> Case Creator Case/Cretr ** +<ReopCaseIndctn> Case Reopen

Indicator Case/ReopCaseIndctn **

3. System searches case database to determine if case already exists, using existing case search criteria

a. If multiple matching cases found, route to exception workbasket for operator intervention; (SI:Common:MultipleCasesFound)

b. If no matching case found, system creates Miscellaneous exception case, mapping those items marked with an asterisk (**) to identically named fields in the exception case (SI:Common:MsgNoMatch);

i. System sends Reject Case Assignment message to Inquiry Party, RCAS_IP_Us_IP_UKNW.

ii. Close the case with status Resolved-Rejected (SI:Common:RejectCaseAssignmentUKNW).

RCAS_IP_Us_IP_UKNW: RejectCaseAssignment camt.031.001.02

MX field tag MX Field name Map from Exception Case <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 <Justfn>

RCAS_IP_Us_IP_UKNW: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case +<RjctnRsn> Case Assignment Rejection

Code UKNW

d. If one matching case is found, attach message to existing case, route case to exceptions workbasket for Step by Step processing. (SI:Common:AuxMsgStbySt)

Note: ***Map fields to Miscellaneous case only.

Page 107: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 107

Duplicate, MX.camt.034 1. System receives camt.033.001 Duplicate message.

2. System creates M- case with the following mapping from message. All fields should be mapped into comparably named fields in the work area of the M- case. (SI:Common:CreateMsgCase).

Duplicate, camt.034.001.02 MX field tag MX Field name Msg Case Property

Name Map to Misc Exc Case

<Assgnmt> Assignment +<Id> Assignment ID Assgnmt/Id +<Assgnr> Assigner Assgnmt/Assgnr +<Assgne> Assignee Assgnmt/Assgne +<CreDtTm> Create Date/Time Assgnmt/CredtTm <Case> Case +<Id> Creator’s Case ID Case/Id *** +<Cretr> Case Creator Case/Cretr *** +<ReopCaseIndctn> Case Reopen

Indicator Case/ReopCaseIndctn ***

<DplctData> Duplicate Data +<Tp> Type +<Cntn> Content

3. System searches case database to determine if case already exists, using existing case search criteria

a. If multiple matching cases found, route to exception workbasket for operator intervention; (SI:Common:MultipleCasesFound)

b. If no matching case found, system creates Miscellaneous exception case, mapping those items marked with an asterisk (**) to identically named fields in the exception case (SI:Common:MsgNoMatch);

i. System sends Reject Case Assignment message to Inquiry Party, RCAS_IP_Us_IP_UKNW.

ii. Close the case with status Resolved-Rejected (SI:Common:RejectCaseAssignmentUKNW).

Note: ***Map fields to Miscellaneous case only

Page 108: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 108

RCAS_IP_Us_IP_UKNW: RejectCaseAssignment camt.031.001.02 MX field tag MX Field name Map from Exception Case <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 <Justfn> +<RjctnRsn> Case Assignment Rejection

Code UKNW

c. If one matching case is found, attach message to existing case, route case to exceptions workbasket for Step by Step processing. (SI:Common: AuxMsgStbySt)

CaseStatusReportRequest, MX.camt.038 1. System receives camt.038.001 CaseStatusReportRequest message.

2. System creates M- case with the following mapping from message. All fields should be mapped into comparably named fields in the work area of the M- case. (SI:Common:CreateMsgCase)

CaseStatusReportRequest camt.038.001.01 MX field tag MX Field name Msg Case Property

Name Map to Misc Exc Case

<Hdr> Header +<Id> ID of Report Hdr/Id +<Fr> From Hdr/Fr +<To> To Hdr/To +<CreDtTm> Create Date/Time Hdr/CreDtTm <Case> Case +<Id> Creator’s Case ID Case/Id *** +<Cretr> Case Creator Case/Cretr *** +<ReopCaseIndctn >

Case Reopen Indicator Case/ReopCaseIndctn ***

3. System searches case database to determine if case already exists, using existing case search criteria

a. If multiple matching cases found, route to exception workbasket for operator intervention;

Note: ***Map fields to Miscellaneous case only

Page 109: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 109

(SI:Common:MultipleCasesFound) b. If no matching case is found, system creates Miscellaneous exception case, mapping those

items marked with an asterisk (**) to identically named fields in the exception case; map the Hdr/Fr field to the Inquiry Party (SI:Common:MsgNoMatch);

i. System sends CaseStatusReport message to Inquiry Party of incoming message, CSRP_ IP_UKNW

ii. Resolve case with Resolved-NoAction (SI:Miscellaneous:CSRRUKNW)

CSRP_ IP_UKNW: CaseStatusReport camt.039.001.02 MX field tag MX Field name Map from Exception Case <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

c. If one matching case is found, attach message to existing case. 4. If BIC of Inquiry Party of exception case is not equal to BIC in Hdr/Fr field of Case Status

Request, route case to exception workbasket for Step-by-Step processing.

5. If case is resolved, (status of case begins with “Resolved”) send CaseStatusReport to Inquiry Party, CSRP_IP_CLSD (SI:Common:CSRQCLSD)

CSRP_IP_CLSD: CaseStatusReport camt.039.001.02 MX field tag MX Field name Map from Exception Case <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 CLSD

6. If case is not resolved, and Last Assignee field equals our BIC, system generates CaseStatusReport message, camt.039.001 to Inquiry Party, CSRP_IP_INVE (SI:Common:CSRPINVE)

Page 110: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 110

CSRP_IP_INVE: CaseStatusReport camt.039.001.02 MX field tag MX Field name Map from Exception Case

CSRP_IP_INVE: CaseStatusReport camt.039.001.02 MX field tag MX Field name Map from Exception Case <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 INVE

7. If case is not resolved and Last Assignee field is not equal to our BIC, system generates CaseStatusReport message, camt.039.001 to IP, CSRP_IP_ASGN. (SI:Common:CSRPASGN)

CSRP_IP_ASGN: CaseStatusReport camt.039.001.02 MX field tag MX Field name Map from Exception Case <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 +<Id> Id Last Assignment Id +<Assigner> Assigner Last Assigner +<Assignee> Assignee Last Assignee +<CredtTm> Create Date/Time Last Assignment Date/Time

Page 111: Pega Advanced E&I Rulebook Application

Pega Advanced E&I Rulebook Application Workflow Definition and Specification 111

CaseStatusReport, MX.camt.039 1. System receives camt.039.001 CaseStatusReport message.

2. System creates M- case with the following mapping from message. All fields should be mapped into comparably named fields in the work area of the M- case. (SI:Common:CreateMsgCase)

CaseStatusReport camt.039.001.02 MX field tag MX Field name Msg Case Property

Name Map to Misc Exc Case

<Hdr> Header +<Id> ID of Report Hdr/Id +<Fr> From Hdr/Fr +<To> To Hdr/To +<CreDtTm> Create Date/Time Hdr/CreDtTm <Case> Case +<Id> Creator’s Case ID Case/Id +<Cretr> Case Creator Case/Cretr +<ReopCaseIndctn >

Case Reopen Indicator Case/ReopCaseIndctn

3. If no matching case is found, resolve M case.

4. If one matching case is found, attach M-case, route case to exception workbasket for Operator review. (SI:Common:AuxMsgStBySt)