RULEBOOK PH-ISO20022 STANDARDS ON PAYMENT MESSAGES · 1 1. Introduction This rulebook called the Philippine Rulebook on Payments and Settlements was crafted and finalized through

RULEBOOK

PH-ISO20022 STANDARDS ON

PAYMENT MESSAGES

Table of Contents 1. Introduction .............................................................................................................................................. 1

1.1 Terms and Definitions ........................................................................................................................ 1

1.2 Abbreviations and Acronyms ............................................................................................................. 1

1.3 Document Scope and Objectives ....................................................................................................... 1

1.4 References ......................................................................................................................................... 2

2. Scope and Functionality ........................................................................................................................... 3

2.1 Background ........................................................................................................................................ 3

2.2 Scope ................................................................................................................................................. 3

2.3 Groups of Message Definitions and Functionality ............................................................................. 3

2.3.1 Groups of Message Definitions ............................................................................................... 3

2.3.1.1 Payment Clearing and Settlement ............................................................................ 3

2.3.1.2 Bank To Customer Cash Management ...................................................................... 4

2.3.1.3 Transaction Management ......................................................................................... 5

2.3.1.4 Limit Management .................................................................................................... 5

2.3.1.5 System Status Management ..................................................................................... 6

2.3.1.6 Reservation Management ........................................................................................ 7

2.3.1.7 Liquidity Management .............................................................................................. 7

2.3.1.8 Exceptions and Investigations Initiation ................................................................... 7

2.3.1.9 Exceptions and Investigations Case Management .................................................... 7

2.3.1.10 Cash Management Proprietary Message ................................................................ 8

2.3.1.11 Business Application Header .................................................................................. 8

2.3.1.12 Administration ........................................................................................................ 8

2.3.2 Functionality ........................................................................................................................... 8

3. Business Roles and Participants ............................................................................................................... 8

3.1 Participants and Business Role Definitions ........................................................................................ 9

3.2 Business Roles and Participants Table ............................................................................................. 10

4. Business Process Descriptions ............................................................................................................... 10

4.1 Positive Message Flow of the FI To FI Customer Payment (pacs.008) ............................................. 10

4.2 Negative Message Flow of the FI To FI Customer Payment (pacs.008) ........................................... 12

4.3 Positive Message Flow of the Financial Institution Credit Transfer (pacs.009) ............................... 13

4.4 Negative Message Flow of the Financial Institution Credit Transfer (pacs.009) ............................. 15

4.5 Positive Message Flow of the Financial Institution Request of Cancellation (camt.008) ................ 16

4.6 Negative Message Flow of the Financial Institution Request of Cancellation (camt.008) ............... 16

4.7 Positive Message Flow of the Financial Institution Request of Modification of Payment Business

Priority (camt.007) ........................................................................................................................... 17

4.8 Negative Message Flow of the Financial Institution Request of Modification of Payment Business

Priority (camt.007) .......................................................................................................................... 18

4.9 Positive Message Flow of Stop and Recall Payment (camt.056) .................................................... 19

4.10 Negative Message Flow of Stop and Recall Payment (camt.056) ................................................... 20

4.11 Positive Message Flow of a Liquidity Credit Transfer (camt.050) ................................................... 21

4.12 Negative Message Flow of a Liquidity Credit Transfer (camt.050) .................................................. 21

4.13 Positive Message Flow of a Liquidity Debit Transfer (camt.051) .................................................... 22

4.14 Negative Message Flow of a Liquidity Debit Transfer (camt.051) ................................................... 23

4.15 Positive Message Flow of a Direct Debit Transfer (pacs.010) ......................................................... 24

4.16 Negative Message Flow of a Direct Debit Transfer (pacs.010) ........................................................ 25

4.17 Positive Message Flow of a Third-Party Financial Institution Credit Transfer (pacs.009) ............... 26

4.18 Negative Message Flow of a Third-Party Financial Institution Credit Transfer (pacs.009) .............. 26

4.19 Positive Message Flow of a Third-Party Batch Gross/Net Credit Transfer (pacs.009) .................... 27

4.20 Negative Message Flow of a Third-Party Batch Gross/Net Credit Transfer (pacs.009) ................... 28

5. Business Examples ................................................................................................................................... 28

5.1 Request to get an account balance report ...................................................................................... 28

5.2 Request to get an interim transaction report .................................................................................. 32

5.3 Request for a payment status .......................................................................................................... 38

5.4 Payment cancellation request ......................................................................................................... 45

5.5 Payment priority change request .................................................................................................... 50

5.6 FI To FI Customer Credit Transfer .................................................................................................. 54

5.7 Customer Status Report .................................................................................................................. 58

5.8 Financial Institution Credit Transfer ................................................................................................ 61

5.9 Stop and Recall Request .................................................................................................................. 65

5.10 Liquidity Credit Transfer ................................................................................................................ 67

5.11 Liquidity Debit Transfer ................................................................................................................. 69

5.12 Financial Institution Direct Debit Transfer ..................................................................................... 71

5.13 Third Party Financial Credit Transfer ............................................................................................. 74

5.14 Third Party Batch Net/Gross Credit Transfer ................................................................................. 77

5.15 Statement Message ....................................................................................................................... 89

5.16 PhilPaSSplus Business Day Information ........................................................................................... 96

5.17 Message Reject .............................................................................................................................. 97

6. Annexes .................................................................................................................................................. 98

6.1 Annex A – Local Instruments ............................................................................................................. 98

6.2 Annex B – Payment Return Reason Code (pacs.004) and Customer Payment Status

Reject Reason Code (pacs.002) ......................................................................................................... 98

6.3 Annex C – Cancellation and Request for Return Reason Code (camt.008 and camt.056) .............. 102

6.4 Annex D – Payment return request decline codes (camt.029) ....................................................... 103

6.5 Annex E – Rejected Reason Code (admi.002, camt.025, pacs.002) ................................................ 103

6.6 Annex F – Transaction Purpose Code .............................................................................................. 117

1

1. Introduction

This rulebook called the Philippine Rulebook on Payments and Settlements was crafted and finalized through the joint efforts of the ISO 20022 Task Force consisting of members from the Bangko Sentral ng Pilipinas (BSP), the banking sector and the 3rd Party Service Providers of the existing Real Time Gross Settlement System (RTGS) of the BSP called Philippine Payment and Settlement System (PhilPaSS) which will eventually be called PhilPaSSplus.

1.1 Terms and Definitions

Term Definition

Business Role Specific sets of application, rules, permissions that each member of a business role is authorized to use

Participant Is a person or entity that is involved in the business transaction Business Process Is a collection of wide range of activities or tasks performed by

participants to produce a specific business service or a business project

Business Transaction Refers to the exchange of transacted values amongst parties who are part of the business project

Message Definition Provides the underlying description of each message under the ISO 20022

1.2 Abbreviation and Acronyms

Abbreviation Definition MDR Message Definition Report MCR Maintenance Change Request SEG Standards Evaluation Group FI Financial Institution XML eXtensible Mark-up Language IBAN International Bank Account Number BIC Business Identifier Code ACH Automated Clearing House DD Direct Debit RTGS Real Time Gross Settlement MRI Mandated Related Information Etc. Etcetera

1.3 Document Scope and Objectives

The document scope refers to a formal list of payment messages and its usage according to the business scenarios with detailed message flows for the Payments Clearing and Settlement.

It describes the business transactions and message sets of the following:

2

• Message Payments Flow according to Business Scenarios • Business Roles in the Business Process

The objectives of this document are as follows:

• to provide detailed information about the payment messages which are part of the business process.

• to describe the Business Processes and the related Business Activities including the associated Business Roles of the participants.

• to document the underlying business transactions with business examples.

1.4 References This section lists documents referred to in the Rulebook.

Document Version Date Author

ISO 20022 Business Justification #6 – (single) credit transfers

2006 09-09-2005 SWIFT

ISO 20022 Business Justification #5 – Direct Debits

2006 08-09-2006 SWIFT

ISO 20022 Business Justification #8 – (bulk) credit transfers

2006 08-09-2006 SWIFT

ISO 20022 Business Justification #85 – Financial Institution Direct Debit

2014 31-07-2014 SWIFT

ISO 20022 Business Justification #110 – Payment Status Request

2016 11-07-2016 SWIFT

BSP Circular 980 Adoption of National Retail Payment System (NRPS) Framework

2017 06-11-2017 BSP

ISO 20022 Maintenance Change Request (MCR #137) document (Payments Maintenance 2018/2019)

2018 26-09-2017 SWIFT

R.A. 11127 – The National Payment Systems Act – an act providing the regulation and supervision of payment systems

2018 30-10-2018 BSP

BSP Circular 1000 – Guidelines on the Settlement of Instant Retail Payments

2018 23-04-2018 BSP

BSP Memorandum M-2018-012 Guidelines on the National Retail Payment System (NRPS) Key Principles and Specific Rules Applicable thereto

2018 23-03-2018 BSP

Payments Clearing and Settlement November 2019 Standards MX Message Definition Report Part 1

February 2019 22-02-2019 SWIFT

3

Payments Clearing and Settlement November 2019 Standards MX Message Definition Report Part 2

February 2019 22-02-2019 SWIFT

BSP Circular 1033 – Amendments to Regulations on Electronic Banking Services and Other Electronic Operations

February 2019 22-01-2019 BSP

BSP Memorandum M-2019-002 Adoption of ISO 20022 on Retail Payment Systems and on Real-Time Gross Settlement System

2019 23-01-2019 BSP

BSP Circular Letter CL-2019-053 Mandatory Adoption of ISO 20022 as message standard for electronic retail and high value payments that settle in the next generation Philippine Payment and Settlement System (PhilPaSS)

2019 05-08-2019 BSP

2. Scope and Functionality

2.1 Background This rulebook is explicitly drafted to help the users in the implementation of the ISO 20022 for the Philippines Payments Domestic Landscape. It covers the different sets of PACS and CAMT messages that were discussed and mapped by the designated Task Force Members from the Bangko Sentral ng Pilipinas (BSP), Banking Sector, ACH Operators and other Stakeholders with the assistance and technical support of SWIFT Standards.

These messages will be used for the clearing and settlement of credit transfers, debit transfers, rejections, refunds between banks or through the ACH Operators or directly with BSP, the Real Time Gross Settlement System Operator.

2.2 Scope

This rulebook covers the set of messages used between financial institutions for the clearing and settlement of payment transactions and the related messages administration, business application header and cash management reporting.

2.3 Groups of Message Definitions and Functionality

2.3.1 Group of Message Definitions

2.3.1.1 Payment Clearing and Settlement

4

2.3.1 The FIToFICustomerCreditTransfer message (pacs.008) is used to move funds from a debtor account to a creditor.

2.3.1 The FinancialInstitutionCreditTransfer message (pacs.009) is used to move

funds from a debtor account to a creditor, where both debtor and creditor are financial institution.

2.3.1 The FiToFIPaymentStatusRequest message (pacs.028) is used to request a

FIToFIPaymentStatusReport message containing information on the status of a previously sent instruction.

2.3.1 The FIToFIPaymentStatusReport message (pacs.002) is used to inform on the

positive and negative status of an instruction (either single or file) and to report on a pending instruction.

2.3.1 The PaymentReturn message (pacs.004) is used to undo a payment

previously settled.

2.3.1 The FinancialInstitutionDirectDebit message (pacs.010) is used to collect funds from a debtor account for a creditor, where both debtor and creditor are financial institution. This message is also used by the ACH operators for their net settlement.

Message Description Message Identifier MT Equivalent

Customer Payment Message pacs.008 MT 103 FI to FI Payment Message pacs.009 MT 202 Payment Enquiry Request pacs.028 MT n95 Payment Enquiry Response pacs.002 MT n95/n96 Payment Return pacs.004 MT 103/202 FI to FI Direct Debit pacs.010 MT 204

2.3.1.2 Bank to Customer Cash Management

2.3.1 The AccountReportingRequest message (camt.060) is sent by the account

owner, either directly or through a forwarding agent, to one of its account servicing institutions. It is used to ask the account servicing institution to send a report on the account owner's account in a BankToCustomerAccountReport (camt.052).

2.3.1 The BankToCustomerAccountReport message (camt.052) is sent by the

account servicer to an account owner or to a party authorized by the account owner to receive the message. It can be used to inform the account owner, or authorized party, of the entries reported to the account, and/or to provide the owner with balance information on the account at a given point in time.

5

2.3.1 The BankToCustomerStatement message (camt.053) is sent by the account servicer to an account owner or to a party authorized by the account owner to receive the message. It is used to inform the account owner, or authorized party, of the entries booked to the account, and to provide the owner with balance information on the account at a given point in time.

2.3.1 The BankToCustomerDebitCreditNotification message (camt.054) is sent by

the account servicer to an account owner or to a party authorized by the account owner to receive the message. It can be used to inform the account owner, or authorized party, of single or multiple debit and/or credit entries reported to the account.


Account Reporting Request camt.060 MT 920 Balance Report / Interim Report camt.052 MT 941/942 Statement Message camt.053 MT 950 DR Advice / CR Advice camt.054 MT 900/910

2.3.1.3 Transaction Management

2.3.1 The ModifyTransaction message (camt.007) is sent by a member to the

transaction administrator. It is used to request one modification in one payment instruction held at the transaction administrator and sent by the member, debiting or crediting its account at the transaction administrator.

2.3.1 The CancelTransaction message (camt.008) is sent by a member to the

transaction administrator. It is used to request the cancellation of one payment instruction held at the transaction administrator and sent by the member.


Payment Priority Change camt.007 MT n95 Payment Cancellation camt.008 MT n92

2.3.1.4 Limit Management

2.3.1 The GetLimit message (camt.009) is used to request information on the

details of one or more limits set by the member (or on behalf of the member) and managed by the transaction administrator.

The ReturnLimit message (camt.010) is sent by the transaction administrator to a member of the system.

6

It is used to provide information on the details of one or more limits set by the member (or on behalf of the member) and managed by the transaction administrator.

The ReturnLimit message can be sent as a response to a related GetLimit message (pull mode) or initiated by the transaction administrator (push mode). The push of information can take place either at prearranged times or as a warning or alarm when a problem has occurred.

2.3.1 The ModifyLimit message (camt.011) is sent by a member to the transaction

administrator.

It is used to request modifications in the details of one particular, several or all limits set by the member and managed by the transaction administrator.

Each ModifyLimit message can alter only one type of limit (current or default).


Get Limit camt.009 MT 199 Return Limit camt.010 MT 199 Modify Limit camt.011 MT 199

2.3.1.5 System Status Management

2.3.1 The ReturnBusinessDayInformation message (camt.019) is sent by the

transaction administrator to a member of the system.

It is used to provide information on different types of administrative data linked to the system.

The ReturnBusinessDayInformation message can be sent as a response to a related GetBusinessDayInformation message (pull mode), or initiated by the transaction administrator (push mode). The push of information can take place either at prearranged times or as a warning or alarm when a problem has occurred.

2.3.1 The Receipt message (camt.025) is sent by the transaction administrator to a

member of the system. It is sent to acknowledge the receipt of one or multiple messages sent previously. The Receipt message is an application receipt acknowledgement and conveys information about the processing of the original message(s).

7


Return Business Day Information camt.019 MT 199 Receipt camt.025 MT n96

2.3.1.6 Reservation Management

2.3.1 The ModifyReservation message (camt.048) is used to request modifications

in the details of one particular reservation set by the member and managed by the transaction administrator


Modify Reservation camt.048

2.3.1.7 Liquidity Management

2.3.1 The LiquidityCreditTransfer message (camt.050) is sent by a member to the transaction administrator. It is used to request a transfer of funds between two accounts belonging to the same member or the same group of accounts, and being held at the transaction administrator.

2.3.1 The LiquidityDebitTransfer message (camt.051) is sent by a member to the

transaction administrator. It is used to request a transfer of funds between two accounts belonging to the same member or the same group of accounts, and being held at the transaction administrator.


Liquidity Credit Transfer camt.050 MT 200 Liquidity Debit Transfer camt.051 MT 200

2.3.1.8 Exceptions and Investigations Initiation

2.3.1 The FIToFIPaymentCancellationRequest message (camt.056) is used to

initiate or forward a case for a payment cancellation request workflow in the Payment Interbank business area.


FI To FI Payment Cancellation Request

camt.056 MT n92

2.3.1.9 Exceptions and Investigations Case Management

2.3.1 The ResolutionOfInvestigation message (camt.029) is used to provide an

answer to the inquiry (positive or negative) and enables the case assignee to close the case.

8

Message Description Message Identifier MT Equivalent Resolution of Investigation camt.029 MT n96

2.3.1.10 Cash Management Proprietary Message

2.3.1 The CashManagementProprietaryMessage (camt.998) is used by financial

institutions, with their own offices, or with other financial institutions with which they have established bilateral agreements. It is used as an envelope for a specified message included in it.


Proprietary Message camt.998 MT 199/999

2.3.1.11 Business Application Header

2.3.1 The BusinessApplicationHeader message (head.001) is composed of 12 building blocks. The business header contains information that is relevant to customer business applications that route and process messages.


Business Application Header head.001

2.3.1.12 Administration

2.3.1 The Message Reject message (admi.002) is sent by a central system to notify the rejection of a previously received message.


Message Reject admi.002 MT n96

2.3.2 Functionality See Message Definition Report Part 2 for the message scopes and formats

3 Business Roles and Participants

A Business Role is a group of persons or entities with different level of authorities having a common set of responsibilities to perform a given task which could either be manual or system enabled. Examples: Banks, Automated Clearing House, Bureau of the Treasury, etc.

A Participant is one who takes part in an activity. Example on a Payment Scenario: Debtor, Creditor, Intermediary Agent, etc.

Both Business Role and participants have positive relationships in performing different activities utilizing varied payment messages under the MX platform completing a particular transaction.

9

3.1 Participants and Business Role Definitions

Participants Description Debtor A person or entity that owes money

that is making payment to the final (ultimate) creditor. The debtor can also be the debit account holder.

Creditor The party receiving the payment which could also be the credit account holder.

Ultimate Debtor Ordering customer giving instructions to a debtor (remitter) who makes the payment to the final creditor.

Ultimate Creditor The last beneficiary to which the payment is due

Debtor Agent Bank that services the account of the debtor.

Creditor Agent Bank that services the account of the creditor.

Forwarding Agent Intermediary that receives payment instruction from the initiating party and forwards the same to another paying agent for execution.

Initiating Party Party that initiates and gives instructions to the agents. This could either be the debtor (for a credit transfer) or the creditor (for a direct debit) or a party initiating the payment in behalf of the debtor or creditor as the case maybe.

Account Owner Person or entity that legally owns the account

Account Servicer Party that administers the account of the account holder which includes amongst others the registration, accounting and reconciliation aspects.

Payment Clearing Agent (Instructing Agent)

ACH Operators that instructs the next institution to carry out the payment to the next party

10

Payment Settlement Agent (Instructed Agent)

Party that executes the payment instruction coming from the Payment Clearing Agent

Intermediary Agent Party between the debtor agent and the creditor agent, which could be several as specified in the instructions to execute the payment.

3.2 Business Roles and Participants Table

Participants Banks Payment Clearing Agent Party Debtor X Creditor X Ultimate Debtor X Ultimate Creditor X Debtor Agent X X Creditor Agent X X Forwarding Agent X X Initiating Party X X Account Owner X X Account Servicer X X Payment Clearing Agent X X Payment Settlement Agent X X Intermediary Agent X X

4 Business Process Description 4.1 Positive Message Flow of the FI To FI Customer Payment (pacs.008)

11

Business Scenario 1. Customer 1 with account in Domestic Bank 1 as payment to Customer 2 with account in Domestic Bank 2.

Actors Name Debtor Customer 1 Instructing Agent / Debtor Agent Domestic Bank 1 Clearing System RTGS Instructed Agent / Creditor Agent Domestic Bank 2 Creditor Customer 2

Business Scenario 2. Customer 1 of Remitter 1 with account in Domestic Bank 1 as payment to Customer 2 with account in Domestic Bank 2.

Actors Name Ultimate Debtor Customer 1 Debtor Remitter 1 Instructing Agent / Debtor Agent Domestic Bank 1 Clearing System RTGS Instructed Agent / Creditor Agent Domestic Bank 2 Creditor Customer 2

Business Scenario 3. A Foreign Customer 1 with account in Foreign Bank 1 instructed correspondent Domestic Bank 1 to credit account of customer 2 in Domestic Bank 2.

Actors Name Debtor Foreign Customer 1 Debtor Agent Foreign Bank 1 Instructing Agent/ Intermediary Agent Domestic Bank 1 Clearing System RTGS Instructed Agent / Creditor Agent Domestic Bank 2 Creditor Customer 2

Process Steps

1. The ordering customer (Debtor) applies for a payment transfer with his Domestic Bank 1

(Instructing Agent and/or Debtor Agent). It is assumed that the debtor client has complied all the requirement of his Domestic Bank 1 on payment transfers and has provided the payment details.

2. The Domestic Bank 1 prepares a customer payment transfer request (pacs.008) to Domestic Bank 2 to credit the account of the beneficiary customer (Creditor). The Domestic Bank 1 then transmits the instruction to BSP (PhilPaSSplus).

3. BSP (PhilPaSSplus) checks the credit transfer instruction and executes the clearing and settlement. A payment status report is released to Domestic Bank 1 if the customer payment transaction is queued (PDNG). If the customer payment transaction is settled (ACSC), then a copy of the customer payment instruction (pacs.008) and a credit notification (camt.054) is released to the Domestic Bank 2 and a settled payment status report (pacs.002) and debit notification (camt.054) is released to the Domestic Bank 1.

4. Domestic Bank 1 receives a settled payment status report (pacs.002) and a debit notification (camt.054) from BSP (PhilPaSSplus).

5. Domestic Bank 2 (Instructed Agent and/or Creditor Agent) receives a copy of the customer payment instruction (pacs.008) and a credit notification (camt.054) from BSP (PhilPaSSplus).

12

6. Domestic Bank 2 then prepares a customer status report (pacs.002) containing the (ACCC) settled status information on the further credit to the beneficiary customer and transmit this report to BSP (PhilPaSSplus) within 2 hours.

7. Domestic Bank 2 then credits the account of the Creditor and notifies the Creditor about the credit.

4.2 Negative Message Flow of the FI To FI Customer Credit Transfer (pacs.008)

Process Steps

1. The ordering customer (Debtor) applies for a payment transfer with his Domestic Bank 1 (Instructing Agent and/or Debtor Agent). It is assumed that the debtor client has complied all the requirement of his Domestic Bank 1 on payment transfers and has provided the payment details.

2. The Domestic Bank 1 prepares a customer payment transfer request (pacs.008) to Domestic Bank 2 to credit the account of the beneficiary customer (Creditor). The Domestic Bank 1 then transmits the instruction to BSP (PhilPaSSplus).

3. BSP (PhilPaSSplus) checks the credit transfer instruction and executes the clearing and settlement.

4. Domestic Bank 1 receives a settled payment status report (pacs.002) and a debit notification (camt.054) from BSP (PhilPaSSplus)

5. Domestic Bank 2 (Instructed Agent and/or Creditor Agent) receives a copy of the customer payment instruction (pacs.008) and a credit notification (camt.054) from BSP (PhilPaSSplus).

Exception for Step 3 3.1 BSP (PhilPaSSplus) rejects the credit transfer and release the payment status report

(pacs.002) containing the rejected information or a negative notification (camt.025 or admi.002). Below are some conditions of a reject: a. Credit transfer has a value date not equal to the business day opened.

13

b. Instructing agent of the transaction has no access rights to settle the transfer of a transaction type in the current business day period.

c. The settlement time of transfer is not within the earliest settlement time and latest settlement time.

d. XML message does not conform to the pacs.008 schema.

The rejected reason error codes are referred in Annex E.

3.2 Domestic Bank 1 receives the payment rejected status report (pacs.002).

Exception for Step 5 5.1 Domestic Bank 2 (Instructed Agent and/or Creditor Agent) prepares a customer status report

(pacs.002) containing the (RJCT) rejected status information on the further credit to the beneficiary customer and transmits the report to BSP (PhilPaSSplus) within 2 hours. The rejected reason codes are referred in Annex B.

5.2 Domestic Bank 2 then prepares the payment return instruction and transmits the instruction to BSP (PhilPaSSplus). The payment return reason codes are referred in Annex B.

5.3 BSP (PhilPaSSplus) checks the credit transfer instruction and executes the clearing and settlement.

5.4 Domestic Bank 2 receives a debit notification (camt.054) from BSP (PhilPaSSplus) and notifies the beneficiary customer of the debit.

5.5 Domestic Bank 1 receives a copy of the payment return instruction (pacs.004) and a credit notification (camt.054) from BSP (PhilPaSSplus).

5.6 Domestic Bank 1 then credits the account of the Debtor and notifies the debtor about the credit.

4.3 Positive Message Flow of the Financial Institution Credit Transfer (pacs.009)

14

Business Scenario 1. Domestic Bank 1 as payment to Domestic Bank 2.

Actors Name Instructing Agent & Debtor Domestic Bank 1 Clearing System RTGS Instructed Agent & Creditor Domestic Bank 2

Business Scenario 2. Domestic Bank 3 has instructed to debit its account in Domestic Bank 1 as payment to Domestic Bank 2.

Actors Name Debtor Domestic Bank 3 Instructing Agent & Debtor Agent Domestic Bank 1 Clearing System RTGS Instructed Agent Domestic Bank 2 Creditor Domestic Bank 2

Business Scenario 3. Domestic Bank 3 has instructed to debit its account in Domestic Bank 1 and credit its account in Domestic Bank 2.

Actors Name Debtor Domestic Bank 3 Instructing Agent & Debtor Agent Domestic Bank 1 Clearing System RTGS Instructed Agent & Creditor Agent Domestic Bank 2 Creditor Domestic Bank 3

Business Scenario 4. BSP/BTr/PCHC as payment to Domestic Bank 2.

Actors Name Instructing Agent & Debtor BSP/BTr/PCHC Clearing System RTGS Instructed Agent & Creditor Domestic Bank 2

Process Steps

1. The Domestic Bank 1 prepares a financial institution payment transfer request (pacs.009) to

Domestic Bank 2. The Domestic Bank 1 then transmits the instruction to BSP (PhilPaSSplus). 2. BSP (PhilPaSSplus) checks the credit transfer instruction and executes the clearing and

settlement. A payment status report (pacs.002) is released to Domestic Bank 1 (sender) if the financial institution payment transaction is queued (PDNG). If the financial institution payment transaction is settled (ACSC), then a copy of the financial institution payment instruction (pacs.009) and a credit notification (camt.054) is release to the Domestic Bank 2 and a settled payment status report (pacs.002) and debit notification (camt.054) is released to the Domestic Bank 1.

3. Domestic Bank 1 receives a settled payment status report (pacs.002) and debit notification (camt.054) from BSP (PhilPaSSplus).

4. Domestic Bank 2 receives a copy of the financial instruction payment instruction (pacs.009) and a credit notification (camt.054) from BSP (PhilPaSSplus).

15

4.4 Negative Message Flow of the Financial Institution Credit Transfer (pacs.009)

Process Steps

1. The Domestic Bank 1 prepares a financial institution payment transfer request (pacs.009) to Domestic Bank 2 (Instructed Agent and/or Creditor Agent and/or Creditor). The Domestic Bank 1 then transmits the instruction to BSP (PhilPaSSplus).


Exception for Step 2 2.1 BSP (PhilPaSSplus) rejects the credit transfer and released the payment status report

(pacs.002) containing the rejected information or a negative notification (camt.025 or admi.002). Below are some conditions of a reject: a. Credit transfer has a value date not equal to the business day opened. b. Instructing agent of the transaction has no access rights to settle the transfer of a

transaction type in the current business day period. c. The settlement time of transfer is not within the earliest settlement time and latest

settlement time. d. XML message does not conform to the pacs.009 schema. The rejected reason error codes are referred in Annex E.

2.2 Domestic Bank 1 (Instructing Agent and/or Creditor Agent) receives the payment rejected status report (pacs.002).

16

4.5 Positive Message Flow of Financial Institution Request of Cancellation (camt.008)

Process Steps

1. The Domestic Bank 1 prepares a payment cancellation request (camt.008) of a queued

payment transaction. The Domestic Bank 1 then transmits the instruction to BSP (PhilPaSSplus). The cancellation reason codes are referred in Annex D.

2. BSP (PhilPaSSplus) checks and executes the cancellation of the instruction. 3. Domestic Bank 1 receives a positive notification (camt.025) containing an acknowledgement

of a successful processing of cancellation request and a payment status report (pacs.002) containing the cancelled information from BSP (PhilPaSSplus).

4.6 Negative Message Flow of Financial Institution Request of Cancellation (camt.008)

17

Process Steps

1. The Domestic Bank 1 prepares a financial institution payment cancellation request (camt.008) of a queued payment transaction. The Domestic Bank 1 then transmits the instruction to BSP (PhilPaSSplus).

2. BSP (PhilPaSSplus) checks and executes the cancellation of the instruction (camt.008).

Exception for Step 2 2.1 The Domestic Bank 1 receives a negative notification (camt.025 or admi.002) from BSP

(PhilPaSSplus). Below are some conditions of a reject: a. Referred payment has settled or cancelled in BSP (PhilPaSSplus). b. XML message does not conform to the camt.008 schema


4.7 Positive Message Flow of Financial Institution Request for Modification of Payment Business

Priority (camt.007)

Process Steps

1. The Domestic Bank 1 prepares a modification of payment business priority request (camt.007) of a queued payment transaction. The Domestic Bank 1 then transmits the instruction to BSP (PhilPaSSplus).

2. BSP (PhilPaSSplus) checks and executes the change in the business priority of the instruction. A payment status report (pacs.002) is released to Domestic Bank 1 if the financial institution payment transaction is queued (PDNG).

18

3. Domestic Bank 1 receives a positive notification containing acknowledgement of a successful processing of a payment priority change request, a settled payment status report (pacs.002) and a debit notification (camt.054) from BSP (PhilPaSSplus).

4. Domestic Bank 2 receives a copy of the credit transfer (pacs.008/pacs.009) and the credit notification (camt.054) from BSP (PhilPaSSplus).

4.8 Negative Message Flow of Financial Institution Request for Modification of Payment Business

Priority (camt.007)

Process Steps

1. The Domestic Bank 1 prepares a modification of payment business priority request

(camt.007) of a queued payment transaction. The Domestic Bank 1 then transmits the instruction to BSP (PhilPaSSplus).

2. BSP (PhilPaSSplus) checks and executes the change in the business priority of the instruction.

Exception for Step 2 2.1 The Domestic Bank 1 receives a negative notification (camt.025 or admi.002) from BSP

(PhilPaSSplus). Below are some conditions of a reject: a. Referred payment has settled or cancelled in BSP (PhilPaSSplus). b. XML message does not conform to the camt.007 schema


19

4.9 Positive Message Flow of Stop and Recall Payment (camt.056)

Process Steps

1. Ordering customer has instructed a refund payment to his Domestic Bank 1. 2. The Domestic Bank 1 prepares a recall of payment request (camt.056) to Domestic Bank 2.

The Domestic Bank 1 then transmits the instruction to BSP (PhilPaSSplus). The cancellation reason codes are referred in Annex D.

3. BSP (PhilPaSSplus) checks the recall of payment request (camt.056). If the referred payment in the camt.056 is settled (ACSC), then BSP (PhilPaSSplus) forwards a copy of the recall of payment request (camt.056) to Domestic Bank 2.

4. Domestic Bank 2 receives the recall of payment request (camt.056) of Domestic Bank 1. It is assumed that the refund payment request was granted.

5. Domestic Bank 2 then prepares the payment return instruction and transmits the instruction to BSP (PhilPaSSplus) valid within 5 days. The payment return reason codes are referred in Annex C.

6. BSP (PhilPaSSplus) checks the return transfer instruction and executes the clearing and settlement.

7. Domestic Bank 2 receives a settled payment status report (pacs.002) and a debit notification (camt.054) from BSP (PhilPaSSplus). Domestic Bank 2 notifies the beneficiary customer of the debit.

8. Domestic Bank 1 receives a copy of the payment return instruction (pacs.004) and a credit notification (camt.054) from BSP (PhilPaSSplus).

9. Domestic Bank 1 then credits the account of the Debtor and notifies the debtor about the credit.

20

4.10 Negative Message Flow of Stop and Recall Payment (camt.056)

Process Steps

1. Ordering customer has instructed a refund payment to his Domestic Bank 1. 2. The Domestic Bank 1 prepares a Recall of Payment Request (camt.056) to Domestic Bank 2.

The Domestic Bank 1 then transmits the instruction to BSP (PhilPaSSplus). 3. BSP (PhilPaSSplus) checks the recall of payment request (camt.056). 4. Domestic Bank 2 receives the recall of payment request (camt.056) of Domestic Bank 1.

Exception for Step 3 3.1 The Domestic Bank 1 receives a rejection status report (camt.029 or admi.002) from BSP

(PhilPaSSplus). Below are some conditions of a reject: a. Referred payment transfer was queued (PDNG) or cancelled (RJCT) in BSP (PhilPaSSplus). b. XML message does not conform to the camt.056 schema


Exception for Step 4 4.1 Domestic Bank 2 beneficiary customer has denied the refund request. 4.2 Domestic Bank 2 then prepares the resolution of investigation message (camt.029)

containing the reason for the rejection and transmits the instruction to BSP (PhilPaSSplus) valid within the next business day.

4.3 Domestic Bank 1 receives the resolution of investigation message (camt.029) and informs the ordering customer that request was denied. The payment return request decline codes are referred in Annex D.

21

4.11 Positive Message Flow of a Liquidity Credit Transfer (camt.050)

Process Steps

1. The Domestic Bank 1 prepares a Liquidity Credit Transfer (camt.050) to transfer funds from

account 1 to account 2. The Domestic Bank 1 then transmits the instruction to BSP (PhilPaSSplus).


3. Domestic Bank 1 receives a settled payment status report (pacs.002).

4.12 Negative Message Flow of a Liquidity Credit Transfer (camt.050)

22

Process Steps

1. The Domestic Bank 1 prepares a Liquidity Credit Transfer (camt.050) to transfer funds from account 1 to account 2. The Domestic Bank 1 then transmits the instruction to BSP (PhilPaSSplus).


Exception for Step 2 2.1 The Domestic Bank 1 receives a negative notification (camt.025 or admi.002) or a rejected

payment status report (pacs.002) from BSP (PhilPaSSplus). Below are some conditions of a reject: a. Domestic Bank 1 has no access rights to debit or credit own account. b. Domestic Bank 1 account has no sufficient balance to credit the ILF account. c. XML message does not conform to the camt.050 schema


4.13 Positive Message Flow of a Liquidity Debit Transfer (camt.051)

Process Steps

1. The Domestic Bank 1 prepares a Liquidity Debit Transfer (camt.051) to debit funds from

account 2 and transfer funds to account 1. The Domestic Bank 1 then transmits the instruction to BSP (PhilPaSSplus).


3. Domestic Bank 1 receives the account 2 debit advice (camt.054) and an account 1 credit advice (camt.054).

23

4.14 Negative Message Flow of a Liquidity Debit Transfer (camt.051)

Process Steps

1. The Domestic Bank 1 prepares a Liquidity Debit Transfer (camt.051) to debit funds from

account 2 and transfer funds to account 1. The Domestic Bank 1 then transmits the instruction to BSP (PhilPaSSplus).


Exception for Step 2 2.1 The Domestic Bank 1 receives a negative notification (camt.025 or admi.002) or a rejected

payment status report (pacs.002) from BSP (PhilPaSSplus). Below are some conditions of a reject: a. Domestic Bank 1 has no access rights to debit or credit own account. b. Domestic Bank 1 has no sufficient balance to credit the ILF account. c. XML message does not conform to the camt.051 schema


24

4.15 Positive Message Flow of a Financial Institution Direct Debit Transfer (pacs.010)

Process Steps

1. BSP/BTr/PCHC-CICS prepares a direct debit message (pacs.010) to debit Domestic Bank 2.

BSP/BTr/PCHC-CICS then transmits the instruction to BSP (PhilPaSSplus). 2. BSP (PhilPaSSplus) checks the credit transfer instruction and executes the clearing and

settlement. A payment status report (pacs.002) is released to BSP/BTr/PCHC-CICS if the payment transaction is queued (PDNG). If the payment transaction is settled (ACSC), then a copy of the direct debit instruction (pacs.010) and a debit notification (camt.054) is released to the Domestic Bank 2 and a settled payment status report (pacs.002) and a credit notification (camt.054) is released to the BSP/BTr/PCHC-CICS.

3. BSP/BTr/PCHC-CICS receives a settled payment status report (pacs.002) and a credit advice (camt.054) from BSP (PhilPaSSplus).

4. Domestic Bank 2 receives a copy of the direct debit instruction (pacs.010) and the credit advice (camt.054) from BSP (PhilPaSSplus).

25

4.16 Negative Message Flow of a Direct Debit Transfer (pacs.010)

Process Steps

1. BSP/BTr/PCHC-CICS prepares a direct debit message (pacs.010) to debit Domestic Bank 2. BSP/BTr/PCHC-CICS then transmits the instruction to BSP (PhilPaSSplus).


Exception for Step 2 2.1 BSP/BTr/PCHC-CICS receives a negative notification (admi.002 or camt.025) or a reject status

report (pacs.002) from BSP (PhilPaSSplus). Below are some conditions of a reject: a. Direct Debit transfer has a value date not equal to the business day opened. b. XML message does not conform to the pacs.010 schema.


26

4.17 Positive Message Flow of a Third-Party Financial Institution Credit Transfer (pacs.009)

Process Steps

1. BTr / BancNet-ATM/PDS prepares a credit transfer (pacs.009) to debit Domestic Bank 1 and credit Domestic Bank 2. BTr / BancNet-ATM/PDS then transmits the instruction to BSP (PhilPaSSplus).

2. BSP (PhilPaSSplus) checks the credit transfer instruction and executes the clearing and settlement. BTr / BancNet-ATM/PDS to receive a payment status report (pacs.002) if payment is rejected (RJCT), queued (PDNG) or settled (ACSC). If the payment transaction is settled, then a copy of the credit transfer instruction (pacs.009) and a credit notification (camt.054) is released to the Domestic Bank 2, a debit notification (camt.054) is released to the Domestic Bank 1 and a settled status report (pacs.002) to BTr / BancNet-ATM/PDS.

3. BTr/Bancnet receives the settled status report (pacs.002) from BSP (PhilPaSSplus) 4. Domestic Bank 1 receives a debit advice (camt.054) from BSP (PhilPaSSplus). 5. Domestic Bank 2 receives a copy of the credit transfer (pacs.009) and the credit advice from

BSP (PhilPaSSplus).

4.18 Negative Message Flow of a Third-Party Financial Institution Credit Transfer (pacs.009)

27

Process Steps

1. BTr /BancNet-ATM/PDS prepares a credit transfer (pacs.009) to debit Domestic Bank 1 and credit Domestic Bank 2. BTr/BancNet-ATM/PDS then transmits the instruction to BSP (PhilPaSSplus).


Exception for Step 2 2.1 BTr/BancNet-ATM/PDS receives a negative notification (admi.002 or camt.025) or a rejected

payment status report (pacs.002) from BSP (PhilPaSSplus). Below are some conditions of a reject: a. Direct Debit transfer has a value date not equal to the business day opened. b. XML message does not conform to the pacs.009 schema.


4.19 Positive Message Flow of a Batch Gross or Net Credit Transfer (pacs.009)

Process Steps

1. InstaPay/PESONet prepares batch (gross-InstaPay/net-PESONet) instruction (pacs.009) and

transmits the instruction to BSP (PhilPaSSplus). 2. BSP (PhilPaSSplus) checks the credit transfer instruction and executes the clearing and

settlement. InstaPay/PESONet to receive a payment status report (pacs.002) if payment is rejected (RJCT), queued (PDNG) or settled (ACSC).

3. InstaPay/PESONet receives the settled status report (pacs.002) from BSP (PhilPaSSplus). 4. Domestic Bank 1 receives a debit advice (camt.054) from BSP (PhilPaSSplus) if debited or a

credit advice (camt.054) if credited. 4.1 Domestic Bank receives a single credit transfer (pacs.009) if credited from BSP (PhilPaSSplus).

28

4.20 Negative Message Flow of a Batch Gross or Net Credit Transfer (pacs.009)

Process Steps

1. InstaPay/PESONet prepares batch (gross-InstaPay/net-PESONet) instruction (pacs.009) and

transmits the instruction to BSP (PhilPaSSplus). 2. BSP (PhilPaSSplus) checks the credit transfer instruction and executes the clearing and

settlement.

Exception for Step 2 2.1 InstaPay/PESONet receives a negative notification (admi.002 or camt.025) or a rejected

payment status report (pacs.002 or admi.002) from BSP (PhilPaSSplus). Below are some conditions of a reject: a. PhilPaSSplus is not started. b. PhilPaSSplus business day is not yet open. c. Direct Debit transfer has a value date not equal to the business day opened. d. XML message does not conform to the pacs.009 schema.


5 Business Examples 5.1 Request to get an account balance report

5.1.1 camt.060.001.01 Message Item Comment Required

Business Application Header V02 From Message Sender Y To Message Receiver Y Business Message Identifier Sender’s Unique Reference Y Message Definition Identifier MX Name Identification Y Creation Date Message Creation Date and Time Y Account Reporting Request V05 Message identification Sender’s Unique Reference Y Creation Date Time Message Creation Date and Time Y

29

Requested Message Name Identification MX Name Identification Y Account Account Number Y Account Owner Account BIC Y

Use Case BOPIPHMM send a request to get the account balance report of its reserved demand deposit account 10000050. <?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>REQBPIBAL0516001</BizMsgIdr> <MsgDefIdr>camt.060.001.05</MsgDefIdr> <CreDt>2020-05-16T10:13:51.0</CreDt> </AppHdr>  <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.060.001.05"> <AcctRptgReq> <GrpHdr> <MsgId>REQBPIBAL0516001</MsgId> <CreDtTm>2020-05-16T10:13:51.0</CreDtTm> </GrpHdr> <RptgReq> <ReqdMsgNmId>camt.052/BALR</ReqdMsgNmId> <Acct> <Id> <Othr> <Id>10000050</Id> </Othr> </Id> </Acct> <AcctOwnr> <Agt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId>

30

</ClrSysMmbId> </FinInstnId> </Agt> </AcctOwnr> </RptgReq> </AcctRptgReq> </Document>

5.1.2 camt.052.001.08 Response of a Balance report

Message Item Comment Required Business Application Header V02 From Message Sender To Message Receiver Business Message Identifier RTGS Unique Reference Message Definition Identifier MX Name Identification Creation Date Message Creation Date and Time Related Related Business Header of camt.060 BankToCustomerAccountReportV08 Group Header Message identification RTGS Unique Message Reference Creation Date Time Message Creation Date and Time Message Identification Camt.060 Original Business Query Message Name Identification Camt.060 Original Business Query Create Date Time Camt.060 Original Business Query Additional Information Requested camt.052 Report Identification RTGS Unique Report Reference Electronic Sequence Number Report Sequence Number Account Account number and owner Balance Balance information Transaction Summary Summary of debit and credit entries

BOPIPHMM with reserved demand deposit account 10000050 has a balance of Php 3,000,000.00. <?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId>

31

</FIId> </To> <BizMsgIdr>123456BR941</BizMsgIdr> <MsgDefIdr>camt.052.001.08</MsgDefIdr> <CreDt>2020-05-16T10:14:51.0</CreDt> <!—Related camt.060 Business Application Header --> <Rltd> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>REQBPIBAL0516001</BizMsgIdr> <MsgDefIdr>camt.060.001.05</MsgDefIdr> <CreDt>2020-05-16T10:13:51.0</CreDt> </Rltd> </AppHdr> <!—Balance Report --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.052.001.08"> <BkToCstmrAcctRpt> <GrpHdr> <MsgId>123456BR941</MsgId> <CreDtTm>2020-05-16T10:14:51.0</CreDtTm> <AddtlInf>BALR</AddtlInf> </GrpHdr> <Rpt> <Id>123456</Id> <Acct> <Id> <Othr> <Id>10000050</Id> </Othr> </Id> <Ownr> <!—BSP Requirement to include Name, Address and BIC of account owner --> <Nm>BANK OF THE PHIL ISLANDS</Nm> <PstlAdr> <AdrLine>MSE BLDG AYALA AVENUE MAKATI CITY</AdrLine> </PstlAdr> <Id> <OrgId> <Othr> <Id>BOPIPHMM</Id>

32

<SchmeNm> <Prtry>PCOD</Prtry> </SchmeNm> </Othr> </OrgId> </Id> </Ownr> </Acct> <!—Balance--> <Bal> <Tp> <CdOrPrtry> <Cd>PRCD</Cd> </CdOrPrtry> </Tp> <Amt Ccy="PHP">0.00</Amt> <CdtDbtInd>CRDT</CdtDbtInd> <Dt>2020-05-16</Dt> </Bal> <Bal> <Tp> <CdOrPrtry> <Cd>CLBD</Cd> </CdOrPrtry> </Tp> <Amt Ccy="PHP">3000000.00</Amt> <CdtDbtInd>CRDT</CdtDbtInd> <Dt>2020-05-16</Dt> </Bal> <!—Transaction Summary--> <TxsSummry> <TtlCdtNtries> <NbOfNtries>2</NbOfNtries> <Sum>3500000.00</Sum> </TtlCdtNtries> <TtlDbtNtries> <NbOfNtries>1</NbOfNtries> <Sum>500000.00</Sum> </TtlDbtNtries> </TxsSummry> </Rpt> </BkToCstmrAcctRpt> </Document> 5.2 Request to get an interim transaction report

5.2.1 camt.060.001.01 Use Case BOPIPHMM send a request to get the interim transaction report of its reserved demand deposit account 10000050. <?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr>

33

<FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>REQBPIBAL0516002</BizMsgIdr> <MsgDefIdr>camt.060.001.05</MsgDefIdr> <CreDt>2020-05-16T10:15:51.0</CreDt> </AppHdr>  <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.060.001.05"> <AcctRptgReq> <GrpHdr> <MsgId>REQBPIBAL0516002</MsgId> <CreDtTm>2020-05-16T10:15:51.0</CreDtTm> </GrpHdr> <RptgReq> <ReqdMsgNmId>camt.052/INTR</ReqdMsgNmId> <Acct> <Id> <Othr> <Id>10000050</Id> </Othr> </Id> </Acct> <AcctOwnr> <Agt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Agt> </AcctOwnr> </RptgReq> </AcctRptgReq> </Document>

5.2.2 camt.052.001.08 Response of an Interim Transaction Report

Message Item Comment Required Business Application Header V02

34

From Message Sender To Message Receiver Business Message Identifier RTGS Unique Reference Message Definition Identifier MX Name Identification Creation Date Message Creation Date and Time Related Related Business Header of camt.060 BankToCustomerAccountReportV08 Group Header Message identification RTGS Unique Message Reference Creation Date Time Message Creation Date and Time Message Identification Camt.060 Original Business Query Message Name Identification Camt.060 Original Business Query Create Date Time Camt.060 Original Business Query Additional Information Requested camt.052 Report Identification RTGS Unique Report Reference Electronic Sequence Number Report Sequence Number Account Account number and owner Entry Details of each transaction

BOPIPHMM with reserved demand deposit account 10000050 has the following transactions as of 10:15:52.

• Php 1,500,000.00 C BEGBAL • Php 500,000.00 D IBCFTR • Php 2,000,000.00 C GSOTC1

<?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>123456BR942</BizMsgIdr> <MsgDefIdr>camt.052.001.08</MsgDefIdr> <CreDt>2020-05-16T10:15:52.0</CreDt> <!—Related camt.060 Business Application Header --> <Rltd> <Fr>

35

<FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>REQBPIBAL0516002</BizMsgIdr> <MsgDefIdr>camt.060.001.05</MsgDefIdr> <CreDt>2020-05-16T10:15:51.0</CreDt> </Rltd> </AppHdr> <!—Interim Report --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.052.001.08"> <BkToCstmrAcctRpt> <GrpHdr> <MsgId>123456BR942</MsgId> <CreDtTm>2020-05-16T10:15:52.0</CreDtTm> <AddtlInf>BALR</AddtlInf> </GrpHdr> <Rpt> <Id>123456</Id> <Acct> <Id> <Othr> <Id>10000050</Id> </Othr> </Id> <Ownr> <Nm>BANK OF THE PHIL ISLANDS</Nm> <PstlAdr> <AdrLine>MSE BLDG AYALA AVENUE MAKATI CITY</AdrLine> </PstlAdr> <Id> <OrgId> <Othr> <Id>BOPIPHMM</Id> <SchmeNm> <Prtry>PCOD</Prtry> </SchmeNm> </Othr> </OrgId> </Id> </Ownr> </Acct>

36

<!—Entry 1 --> <Ntry> <NtryRef>1</NtryRef> <Amt Ccy="PHP">1500000.00</Amt> <CdtDbtInd>CRDT</CdtDbtInd> <Sts> <Cd>BOOK</Cd> </Sts> <BookgDt> <DtTm>2020-05-16T08:55:00.0</DtTm> </BookgDt> <ValDt> <Dt>2020-05-16</Dt> </ValDt> <BkTxCd> <Prtry> <Cd>pacs.009.001.09</Cd> </Prtry> </BkTxCd> <NtryDtls> <TxDtls> <Refs> <MsgId>BEGBAL051620111</MsgId> <EndToEndId>NOTPROVIDED</EndToEndId> <UETR>6d8bf870-f0e5-4d7d-9b55-0661bf9f66b3</UETR> <TxId>BEGBAL051620111</TxId> </Refs> <RltdAgts> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>ZZCFASRT</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> <InstdAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </InstdAgt> </RltdAgts> <LclInstrm> <Prtry>RTGS-IFCT</Prtry> </LclInstrm> <Purp> <Prtry>BEGBAL</Prtry> </Purp> </TxDtls> </NtryDtls> </Ntry> <!—Entry 2 --> <Ntry> <NtryRef>2</NtryRef> <Amt Ccy="PHP">500000.00</Amt> <CdtDbtInd>DBIT</CdtDbtInd>

37

<Sts> <Cd>BOOK</Cd> </Sts> <BookgDt> <DtTm>2020-05-16T09:05:00.0</DtTm> </BookgDt> <ValDt> <Dt>2020-05-16</Dt> </ValDt> <BkTxCd> <Prtry> <Cd>pacs.008.001.09</Cd> </Prtry> </BkTxCd> <NtryDtls> <TxDtls> <Refs> <MsgId>IBCP-BOPI051620-01</MsgId> <EndToEndId>NOTPROVIDED</EndToEndId> <UETR>ada45c79-0bd1-44da-b39b-4b1fe192a35c</UETR> <TxId>IBCP-BOPI051620-01</TxId> </Refs> <RltdAgts> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> <InstdAgt> <FinInstnId> <ClrSysMmbId> <MmbId>UCPBPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </InstdAgt> </RltdAgts> <LclInstrm> <Prtry>RTGS-SCCT</Prtry> </LclInstrm> <Purp> <Prtry>IBCFTR</Prtry> </Purp> </TxDtls> </NtryDtls> </Ntry> <!—Entry 3 --> <Ntry> <NtryRef>3</NtryRef> <Amt Ccy="PHP">2000000.00</Amt> <CdtDbtInd>CRDT</CdtDbtInd> <Sts> <Cd>BOOK</Cd> </Sts> <BookgDt> <DtTm>2020-05-16T09:31:10.0</DtTm>

38

</BookgDt> <ValDt> <Dt>2020-05-16</Dt> </ValDt> <BkTxCd> <Prtry> <Cd>pacs.009.001.09</Cd> </Prtry> </BkTxCd> <NtryDtls> <TxDtls> <Refs> <MsgId>GSOTC12005160001</MsgId> <EndToEndId>NOTPROVIDED</EndToEndId> <UETR>240b1cb8-cae3-4e34-b7f4-26f68147716a</UETR> <TxId>GSOTC12005160001</TxId> </Refs> <RltdAgts> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>EWBCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> <InstdAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </InstdAgt> </RltdAgts> <LclInstrm> <Prtry>RTGS-IFCT</Prtry> </LclInstrm> <Purp> <Prtry>GSOTC1</Prtry> </Purp> </TxDtls> </NtryDtls> </Ntry> </Rpt> </BkToCstmrAcctRpt> </Document> 5.3 Request for a payment status

5.3.1 pacs.028.001.04 Message Item Comment Required

Business Application Header V02 From Message Sender Y To Message Receiver Y Business Message Identifier Sender’s Unique Reference Y Message Definition Identifier MX Name Identification Y Creation Date Message Creation Date and Time Y FI To FI Payment Status Request V04

39

Group Header Y Message identification Sender’s Unique Reference Y Creation Date Time Message Creation Date and Time Y Transaction Information Y Original Message Identification Requested Payment Message Id Y Original Message Name Identification Requested MX Message Type Y Original Creation Date Time Requested Payment Creation Date

and Time Y

Instructing Agent Original Sender of the requested payment

Y

Interbank Settlement Date Original Value Date of the requested payment

Y

Use Case BOPIPHMM sends a request to get the payment status of transaction IBCP-BOPI051620-01 <?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>REQBPIPYST0516001</BizMsgIdr> <MsgDefIdr>pacs.002.001.11</MsgDefIdr> <CreDt>2020-05-16T09:05:00.0</CreDt> </AppHdr>  <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.028.001.04"> <FIToFIPmtStsReq> <GrpHdr> <MsgId>REQBPIPYST0516001</MsgId> <CreDtTm>2020-05-16T09:05:00.0</CreDtTm> </GrpHdr> <TxInf> <OrgnlGrpInf> <OrgnlMsgId>IBCP-BOPI051620-01</OrgnlMsgId> <OrgnlMsgNmId>pacs.008.001.09</OrgnlMsgNmId> <OrgnlCreDtTm>2020-05-16T09:04:45.0</OrgnlCreDtTm> </OrgnlGrpInf>

40

<InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> <OrgnlTxRef> <IntrBkSttlmDt>2020-05-16</IntrBkSttlmDt> </OrgnlTxRef> </TxInf> </FIToFIPmtStsReq> </Document>

5.3.2 pacs.002.001.011 Response of Payment Status Report

Message Item Comment Required Business Application Header V02 From Message Sender To Message Receiver Business Message Identifier Sender’s Unique Reference Message Definition Identifier MX Name Identification Creation Date Message Creation Date and Time Related Related pacs.028 Business

Application Header

FI To FI Payment Status Report V11 Group Header Message identification Sender’s Unique Reference Creation Date Time Message Creation Date and Time Original Group Information and Status Original Message Identification Payment Message Id Original Message Name Identification Payment MX Message Type Original Creation Date Time Payment Message Creation Date

and Time

Group Status Payment Status Status Reason Information Detailed information on the status

reason

Transaction Information and Status Transaction Status Status of the transaction Status Reason Information Detailed information on the status

reason

Acceptance Date and Time Payment receipt date and time Effective Interbank Settlement Date Payment settlement date and time Instructing Agent Original Sender of the payment Interbank Settlement Date Original Value Date of the payment

If requested payment is rejected. It was previously cancelled by BOPIPHMM

<?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId>

41

<ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>STAT/123456</BizMsgIdr> <MsgDefIdr>pacs.002.001.11</MsgDefIdr> <CreDt>2020-05-16T09:05:00.0</CreDt> <!—Related camt.028 Business Application Header --> <Rltd> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>REQBPIPYST0516001</BizMsgIdr> <MsgDefIdr>pacs.028.001.04</MsgDefIdr> <CreDt>2020-05-16T09:05:00.0</CreDt> </Rltd> </AppHdr> <!—FI To FI Payment Status Report --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.002.001.11"> <FIToFIPmtStsRpt> <GrpHdr> <MsgId>STAT/123456</MsgId> <CreDtTm>2020-05-16T09:05:00.0</CreDtTm> </GrpHdr> <OrgnlGrpInfAndSts> <OrgnlMsgId>IBCP-BOPI051620-01</OrgnlMsgId> <OrgnlMsgNmId>pacs.008.001.09</OrgnlMsgNmId> <OrgnlCreDtTm>2020-05-16T09:04:45.0</OrgnlCreDtTm> <GrpSts>RJCT</GrpSts> <StsRsnInf>

42

<Rsn> <Prtry>EP69</Prtry> </Rsn> <AddtlInf>Instruction Cancelled</AddtlInf> </StsRsnInf> </OrgnlGrpInfAndSts> <TxInfAndSts> <TxSts>RJCT</TxSts> <StsRsnInf> <Rsn> <Prtry>EP69</Prtry> </Rsn> <AddtlInf>Instruction Cancelled</AddtlInf> </StsRsnInf> <AccptncDtTm>2020-05-16T09:04:45.0</AccptncDtTm> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> <OrgnlTxRef> <IntrBkSttlmDt>2020-05-16</IntrBkSttlmDt> </OrgnlTxRef> </TxInfAndSts> </FIToFIPmtStsRpt> </Document> If requested payment is queued

<?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>STAT/123456</BizMsgIdr> <MsgDefIdr>pacs.002.001.11</MsgDefIdr> <CreDt>2020-05-16T09:05:00.0</CreDt> <!—Related camt.028 Business Application Header --> <Rltd>

43

<Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>REQBPIPYST0516001</BizMsgIdr> <MsgDefIdr>pacs.028.001.04</MsgDefIdr> <CreDt>2020-05-16T09:05:00.0</CreDt> </Rltd> </AppHdr> <!—FI To FI Payment Status Report --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.002.001.11"> <FIToFIPmtStsRpt> <GrpHdr> <MsgId>STAT/123456</MsgId> <CreDtTm>2020-05-16T09:05:00.0</CreDtTm> </GrpHdr> <OrgnlGrpInfAndSts> <OrgnlMsgId>IBCP-BOPI051620-01</OrgnlMsgId> <OrgnlMsgNmId>pacs.008.001.09</OrgnlMsgNmId> <OrgnlCreDtTm>2020-05-16T09:04:45.0</OrgnlCreDtTm> <GrpSts>PDNG</GrpSts> <StsRsnInf> <Rsn> <Prtry>EP183</Prtry> </Rsn> <AddtlInf>Lack of funds</AddtlInf> </StsRsnInf> </OrgnlGrpInfAndSts> <TxInfAndSts> <TxSts>PDNG</TxSts> <StsRsnInf> <Rsn> <Prtry>EP183</Prtry> </Rsn> <AddtlInf>Lack of funds</AddtlInf> </StsRsnInf> <AccptncDtTm>2020-05-16T09:04:45.0</AccptncDtTm> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId>

44

</FinInstnId> </InstgAgt> <OrgnlTxRef> <IntrBkSttlmDt>2020-05-16</IntrBkSttlmDt> </OrgnlTxRef> </TxInfAndSts> </FIToFIPmtStsRpt> </Document>

If requested payment is settled

<?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>STAT/123456</BizMsgIdr> <MsgDefIdr>pacs.002.001.11</MsgDefIdr> <CreDt>2020-05-16T09:05:00.0</CreDt> <!—Related camt.028 Business Application Header --> <Rltd> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>REQBPIPYST0516001</BizMsgIdr>

45

<MsgDefIdr>pacs.028.001.04</MsgDefIdr> <CreDt>2020-05-16T09:05:00.0</CreDt> </Rltd> </AppHdr> <!—FI To FI Payment Status Report --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.002.001.11"> <FIToFIPmtStsRpt> <GrpHdr> <MsgId>STAT/123456</MsgId> <CreDtTm>2020-05-16T09:05:00.0</CreDtTm> </GrpHdr> <OrgnlGrpInfAndSts> <OrgnlMsgId>IBCP-BOPI051620-01</OrgnlMsgId> <OrgnlMsgNmId>pacs.008.001.09</OrgnlMsgNmId> <OrgnlCreDtTm>2020-05-16T09:04:45.0</OrgnlCreDtTm> <GrpSts>ACSC</GrpSts> </OrgnlGrpInfAndSts> <TxInfAndSts> <TxSts>ACSC</TxSts> <AccptncDtTm>2020-05-16T09:04:45.0</AccptncDtTm> <FctvIntrBkSttlmDt> <DtTm>2020-05-16T09:05:00.0</DtTm> </FctvIntrBkSttlmDt> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> <OrgnlTxRef> <IntrBkSttlmDt>2020-05-16</IntrBkSttlmDt> </OrgnlTxRef> </TxInfAndSts> </FIToFIPmtStsRpt> </Document> 5.4 Payment Cancellation Request

5.4.1 camt.008.001.08 Message Item Comment Required

Business Application Header V02 From Message Sender Y To Message Receiver Y Business Message Identifier Sender’s Unique Reference Y Message Definition Identifier MX Name Identification Y Creation Date Message Creation Date and Time Y Cancel Transaction V8 Message identification Sender’s Unique Reference Y Creation Date Time Message Creation Date and Time Y Payment Identification Y Short Business Identification Payment identification Y Transaction Identification Payment Transaction Identification Y Interbank Settlement Date Payment Value Date Y Instructing Agent Payment Sender Y

46

Cancellation Reason Y Reason Reason code for the cancellation Y Additional Information Further details on the cancellation

Use Case BOPIPHMM send a request to cancel the payment IBCP-BOPI051620-01 amounting to Php 500,000.00. <?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>CNCL05162001</BizMsgIdr> <MsgDefIdr>camt.008.001.08</MsgDefIdr> <CreDt>2020-05-16T09:04:50.0</CreDt> </AppHdr> <!—Payment Cancellation Request --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.008.001.08"> <CclTx> <MsgHdr> <MsgId>CNCL05162001</MsgId> <CreDtTm>2020-05-16T09:04:50.0</CreDtTm> </MsgHdr> <PmtId> <ShrtBizId> <TxId>IBCP-BOPI051620-01</TxId> <IntrBkSttlmDt>2020-05-16</IntrBkSttlmDt> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> </ShrtBizId> </PmtId> <CxlRsn> <Rsn> <Prtry>DUPL</Prtry>

47

</Rsn> </CxlRsn> </CclTx> </Document>

5.4.2 camt.025.001.05 Payment Cancellation Response

Message Item Comment Required Business Application Header V02 From Message Sender To Message Receiver Business Message Identifier Sender’s Unique Reference Message Definition Identifier MX Name Identification Creation Date Message Creation Date and Time Related Related camt.008 Business

Application Header

Receipt V5 Message identification RTGS Unique Reference Creation Date Time Message Creation Date and Time Receipt Details Original Message Identification Message Identification Referred message id Message Name Identification Referred message MX Type Original Name Party that assigned the original

message id

Request Handling Status Code Status of the request

If cancellation is successful

<?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>R123456</BizMsgIdr> <MsgDefIdr>camt.025.001.05</MsgDefIdr> <CreDt>2020-05-16T09:04:50.0</CreDt>

48

<!—Related camt.008 Business Application Header --> <Rltd> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>CNCL05162001</BizMsgIdr> <MsgDefIdr>camt.008.001.08</MsgDefIdr> <CreDt>2020-05-16T09:04:50.0</CreDt> </Rltd> </AppHdr> <!—Receipt --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.025.001.05"> <Rct> <MsgHdr> <MsgId>R123456</MsgId> <CreDtTm>2020-05-16T09:04:50.0</CreDtTm> </MsgHdr> <RctDtls> <OrgnlMsgId> <MsgId>CNCL05162001</MsgId> <MsgNmId>camt.008.001.08</MsgNmId> <OrgtrNm>BOPIPHMM</OrgtrNm> </OrgnlMsgId> <ReqHdlg> <StsCd>OK</StsCd> </ReqHdlg> </RctDtls> </Rct> </Document>

If cancellation is rejected

<?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId>

49

</ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>R123456</BizMsgIdr> <MsgDefIdr>camt.025.001.05</MsgDefIdr> <CreDt>2020-05-16T09:04:50.0</CreDt> <!—Related camt.008 Business Application Header --> <Rltd> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>CNCL05162001</BizMsgIdr> <MsgDefIdr>camt.008.001.08</MsgDefIdr> <CreDt>2020-05-16T09:04:50.0</CreDt> </Rltd> </AppHdr> <!—Receipt --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.025.001.05"> <Rct> <MsgHdr> <MsgId>R123456</MsgId> <CreDtTm>2020-05-16T09:04:50.0</CreDtTm> </MsgHdr> <RctDtls> <OrgnlMsgId> <MsgId>CNCL05162001</MsgId> <MsgNmId>camt.008.001.08</MsgNmId> <OrgtrNm>BOPIPHMM</OrgtrNm> </OrgnlMsgId> <ReqHdlg> <StsCd>ERRC</StsCd>

50

<Desc>EP69 Instruction cancelled</Desc> </ReqHdlg> </RctDtls> </Rct> </Document>

5.5 Payment Priority Change Request 5.5.1 camt.007.001.08

Message Item Comment Required Business Application Header V02 From Message Sender Y To Message Receiver Y Business Message Identifier Sender’s Unique Reference Y Message Definition Identifier MX Name Identification Y Creation Date Message Creation Date and Time Y Modify Transaction V8 Message identification Sender’s Unique Reference Y Creation Date Time Message Creation Date and Time Y Payment Identification Y Short Business Identification Payment identification Y Transaction Identification Payment Transaction Identification Y Interbank Settlement Date Payment Value Date Y Instructing Agent Payment Sender Y New Payment Value Set Y Priority New Payment Priority Number Y

Use Case BOPIPHMM send a request to cancel the payment IBCP-BOPI051620-01 amounting to Php 500,000.00. <?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>CHGPRTRY05162001</BizMsgIdr> <MsgDefIdr>camt.008.001.08</MsgDefIdr>

51

<CreDt>2020-05-16T09:04:50.0</CreDt> </AppHdr> <!—Payment Priority Request --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.007.001.08"> <ModfyTx> <MsgHdr> <MsgId>CHGPRTRY05162001</MsgId> <CreDtTm>2020-05-16T09:04:50.0</CreDtTm> </MsgHdr> <PmtId> <ShrtBizId> <TxId>IBCP-BOPI051620-01</TxId> <IntrBkSttlmDt>2020-05-16</IntrBkSttlmDt> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> </ShrtBizId> </PmtId> <NewPmtValSet> <Prty> <Prtry>96</Prtry> </Prty> </NewPmtValSet> </ModfyTx> </Document>

5.5.2 camt.025.001.05 Payment Priority Change Response

If payment priority change is successful

<?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId>

52

</To> <BizMsgIdr>R123456</BizMsgIdr> <MsgDefIdr>camt.025.001.05</MsgDefIdr> <CreDt>2020-05-16T09:04:50.0</CreDt> <!—Related camt.007 Business Application Header --> <Rltd> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>CHGPRTRY05162001</BizMsgIdr> <MsgDefIdr>camt.007.001.08</MsgDefIdr> <CreDt>2020-05-16T09:04:50.0</CreDt> </Rltd> </AppHdr> <!—Receipt --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.025.001.05"> <Rct> <MsgHdr> <MsgId>R123456</MsgId> <CreDtTm>2020-05-16T09:04:50.0</CreDtTm> </MsgHdr> <RctDtls> <OrgnlMsgId> <MsgId>CHGPRTRY05162001</MsgId> <MsgNmId>camt.007.001.08</MsgNmId> <OrgtrNm>BOPIPHMM</OrgtrNm> </OrgnlMsgId> <ReqHdlg> <StsCd>OK</StsCd> </ReqHdlg> </RctDtls> </Rct> </Document>

If payment priority change is rejected

<?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr>

53

<FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>R123456</BizMsgIdr> <MsgDefIdr>camt.025.001.05</MsgDefIdr> <CreDt>2020-05-16T09:04:50.0</CreDt> <!—Related camt.007 Business Application Header --> <Rltd> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>CHGPRTRY05162001</BizMsgIdr> <MsgDefIdr>camt.007.001.08</MsgDefIdr> <CreDt>2020-05-16T09:04:50.0</CreDt> </Rltd> </AppHdr> <!—Receipt --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.025.001.05"> <Rct> <MsgHdr> <MsgId>R123456</MsgId> <CreDtTm>2020-05-16T09:04:50.0</CreDtTm> </MsgHdr> <RctDtls> <OrgnlMsgId> <MsgId>CHGPRTRY05162001</MsgId> <MsgNmId>camt.007.001.08</MsgNmId>

54

<OrgtrNm>BOPIPHMM</OrgtrNm> </OrgnlMsgId> <ReqHdlg> <StsCd>ERRC</StsCd>

<Desc>EP69 Instruction cancelled</Desc> </ReqHdlg> </RctDtls> </Rct> </Document> 5.6 FI To FI Customer Credit Transfer

5.6.1 pacs.008.001.09 Message Item Comment M/O

Business Application Header V02 From Message Sender Y To Message Receiver Y Business Message Identifier Sender’s Unique Reference Y Message Definition Identifier MX Name Identification Y Creation Date Message Creation Date and Time Y Priority Payment Priority Number Y FI To FI Customer Credit Transfer V9 Message identification Payment Reference Y Creation Date Time Message Creation Date and Time Y Batch Booking Fixed Value: false, individual

booking Y

Number of Transactions Fixed Value: 1, single customer credit transfer

Y

Settlement Information Y FI to FI Customer Credit Transfer V9 Payment Identification Y End To End Identification Field 70 in case narrative will refer

to SWIFT, can also be F20 of received MT101. Field 21 of MT101 mapped to Field 70 of MT103. E.g. value after the codeword /ROC/ to be populated here. If there is no reference, then the same transaction identification is provided.

Y

Transaction Identification Payment Reference Y UETR Universally Unique Identifier

RFC 4122 – UUID version 4 Y

Payment Type Identification Y Clearing Channel RTGS – clearing system channel

that process the payment instruction

Y

Local Instrument RTGS-SCCP – single customer credit payment

Y

Interbank Settlement Amount Payment Amount Y Interbank Settlement Date Payment Value Date Y Charge Bearer Party that bears the charge for the

processing of the payment Y

Instructing Agent Agent that is debited in the RTGS Y Instructed Agent Agent that is credited in the RTGS Y

55

Ultimate Debtor Party that originally orders the goods and services to the debtor.

Debtor Party whose account is debited with the payment

Y

Debtor Account Party account that is debited Y Debtor Agent Agent servicing an account for the

debtor and party who executes the debit of Debtor account.

Y

Creditor Agent Agent servicing an account for the debtor and party who executes the credit of Creditor account.

Y

Creditor Party whose account is credited with the payment

Y

Creditor Account Party account that is credited Y Ultimate Creditor Party which is the ultimate

beneficiary of the payment

Instruction for Creditor Agent Sender to receiver information Purpose Payment Transaction Code Y Regulatory Reporting Bank to indicate the ITRS code if

debtor is a non-resident of PH

Use Case BOPIPHMM Bank of the Philippine Island has received a payment instruction from its client ESM Garments with BPI account 122345678 to pay Rico J. Oriones a client of UCPBPHMM United Coconut Planters Bank with UCPB account 8967634.

<?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>IBCP-BOPI051620-01</BizMsgIdr> <MsgDefIdr>pacs.008.001.09</MsgDefIdr> <CreDt>2020-05-16T09:04:50.0</CreDt> <!—Payment Priority Request --> <Prty>98</Prty> </AppHdr> <!—FI To FI Customer Credit Transfer --> <?xml version="1.0" encoding="UTF-8"?>

56

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.008.001.09"> <FIToFICstmrCdtTrf> <GrpHdr> <MsgId>IBCP-BOPI051620-01</MsgId> <CreDtTm>2020-05-16T09:04:50.0</CreDtTm> <BtchBookg>false</BtchBookg> <NbOfTxs>1</NbOfTxs> <SttlmInf> <SttlmMtd>CLRG</SttlmMtd> <ClrSys> <Cd>BSP</Cd> </ClrSys> </SttlmInf> </GrpHdr> <CdtTrfTxInf> <PmtId> <EndToEndId>IBCP-BOPI051620-01</EndToEndId> <TxId>IBCP-BOPI051620-01</TxId> <UETR>ada45c79-0bd1-44da-b39b-4b1fe192a35c</UETR> </PmtId> <PmtTpInf> <ClrChanl>RTGS</ClrChanl> <LclInstrm> <Prtry>RTGS-SCCT</Prtry> </LclInstrm> </PmtTpInf> <IntrBkSttlmAmt Ccy="PHP">500000.00</IntrBkSttlmAmt> <ChrgBr>DEBT</ChrgBr> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> <Othr> <Id>10000050</Id> <SchmeNm> <Prtry>STAC</Prtry> </SchmeNm> </Othr> </FinInstnId> </InstgAgt> <InstdAgt> <FinInstnId> <ClrSysMmbId> <MmbId>UCPBPHMM</MmbId> </ClrSysMmbId> <Othr> <Id>10000470</Id> <SchmeNm> <Prtry>STAC</Prtry> </SchmeNm> </Othr> </FinInstnId> </InstdAgt> <Dbtr> <Nm>ESM Garments</Nm> <PstlAdr>

57

<AdrLine>Estrada St., Malate</AdrLine> <AdrLine>Manila</AdrLine> </PstlAdr> <Id> <OrgId> <Othr> <Id>1943-10-23</Id> <SchmeNm> <Prtry>DINC</Prtry> </SchmeNm> </Othr> </OrgId> </Id> </Dbtr> <DbtrAcct> <Id> <Othr> <Id>122345678</Id> </Othr> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </DbtrAgt> <CdtrAgt> <FinInstnId> <ClrSysMmbId> <MmbId>UCPBPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Rico J. Oriones</Nm> <PstlAdr> <AdrLine>Five E-Com center, Palm</AdrLine> <AdrLine>Coast Avenue Corner Harbor Drive,</AdrLine> <AdrLine>Pasay City</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>8967634</Id> </Othr> </Id> </CdtrAcct> <InstrForCdtrAgt> <InstrInf>Test Only</InstrInf> </InstrForCdtrAgt> <Purp> <Prtry>CORPYP</Prtry> </Purp> <RgltryRptg>

58

<Dtls> <Cd>1520000018</Cd> </Dtls> </RgltryRptg> </CdtTrfTxInf> </FIToFICstmrCdtTrf> </Document> 5.7 Customer Status Report

5.7.1 pacs.002.001.11 Message Item Comment Required

Business Application Header V02 From Message Sender Y To Message Receiver Y Business Message Identifier Sender’s Unique Reference Y Message Definition Identifier MX Name Identification Y Creation Date Message Creation Date and Time Y Business Process Date Required if transaction status

”ACCC”, and indicated the posting date and time of further credit to beneficiary account

Related Related pacs.028 Business Application Header

Y

FI To FI Payment Status Report V11 Group Header Y Message identification Sender’s Unique Reference Y Creation Date Time Message Creation Date and Time Y Transaction Information and Status Y Original Group Information Y Original Message Identification Referred Payment Message Id Y Original Message Name Identification Referred Payment MX Type Y Original Creation Date Time Referred Payment Message

Creation Date and Time Y

Transaction Status Status of the transaction Y Status Reason Information Required if Transaction is “RJCT”

detailed information on the rejected status reason

Instructing Agent Original Sender of the payment Y Interbank Settlement Date Original Value Date of the payment Y

If further credit to beneficiary customer is complete <?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>UCPBPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr>

59

<To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>CUSTUCPBSTAT050616001</BizMsgIdr> <MsgDefIdr>pacs.002.001.11</MsgDefIdr> <CreDt>2020-05-16T09:10:51.0</CreDt> <!—Posting date and time beneficiary account was credited --> <BizPrcgDt>2020-05-16T09:04:45.0</BizPrcgDt> <!—Related pacs.008 Business Application Header --> <Rltd> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>IBCP-BOPI051620-01</BizMsgIdr> <MsgDefIdr>pacs.008.001.09</MsgDefIdr> <CreDt>2020-05-16T09:04:45.0</CreDt> </Rltd> </AppHdr> <!—Customer Status Report --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.002.001.11"> <FIToFIPmtStsRpt> <GrpHdr> <MsgId>CUSTUCPBSTAT050616001</MsgId> <CreDtTm>2020-05-16T09:10:51.0</CreDtTm> </GrpHdr> <TxInfAndSts> <OrgnlGrpInf> <OrgnlMsgId>IBCP-BOPI051620-01</OrgnlMsgId> <OrgnlMsgNmId>pacs.008.001.09</OrgnlMsgNmId> <OrgnlCreDtTm>2020-05-16T09:04:45.0</OrgnlCreDtTm> </OrgnlGrpInf> <TxSts>ACCC</TxSts> <InstgAgt>

60

<FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> <OrgnlTxRef> <IntrBkSttlmDt>2020-05-16</IntrBkSttlmDt> </OrgnlTxRef> </TxInfAndSts> </FIToFIPmtStsRpt> </Document> If further credit to beneficiary customer is not complete due to account is invalid <?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>UCPBPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>CUSTUCPBSTAT050616001</BizMsgIdr> <MsgDefIdr>pacs.002.001.11</MsgDefIdr> <CreDt>2020-05-16T09:10:51.0</CreDt> <!—Related pacs.008 Business Application Header --> <Rltd> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId>

61

</FinInstnId> </FIId> </To> <BizMsgIdr>IBCP-BOPI051620-01</BizMsgIdr> <MsgDefIdr>pacs.008.001.09</MsgDefIdr> <CreDt>2020-05-16T09:04:45.0</CreDt> </Rltd> </AppHdr> <!—Customer Status Report --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.002.001.11"> <FIToFIPmtStsRpt> <GrpHdr> <MsgId>CUSTUCPBSTAT050616001</MsgId> <CreDtTm>2020-05-16T09:10:51.0</CreDtTm> </GrpHdr> <TxInfAndSts> <OrgnlGrpInf> <OrgnlMsgId>IBCP-BOPI051620-01</OrgnlMsgId> <OrgnlMsgNmId>pacs.008.001.09</OrgnlMsgNmId> <OrgnlCreDtTm>2020-05-16T09:04:45.0</OrgnlCreDtTm> </OrgnlGrpInf> <TxSts>RJCT</TxSts> <StsRsnInf>

<Rsn> <Prtry>AC01</Prtry> </Rsn> <AddtlInf>Account number is invalid or missing</AddtlInf>

</StsRsnInf> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> <OrgnlTxRef> <IntrBkSttlmDt>2020-05-16</IntrBkSttlmDt> </OrgnlTxRef> </TxInfAndSts> </FIToFIPmtStsRpt> </Document> 5.8 Financial Institution Credit Transfer


Business Application Header V02 From Message Sender Y To Message Receiver Y Business Message Identifier Sender’s Unique Reference Y Message Definition Identifier MX Name Identification Y Creation Date Message Creation Date and Time Y Priority Payment Priority Number Y

62

Financial Institution Credit Transfer V9 Message identification Payment Reference Y Creation Date Time Message Creation Date and Time Y Batch Booking Fixed Value: false, individual

booking Y


Y

Settlement Information Y Credit Transfer Transaction Information Y Payment Identification Y End To End Identification Related Reference, NOTPROVIDED

if no related reference Y





Y

Local Instrument RTGS-FICT – single financial institution credit transfer

Y

Interbank Settlement Amount Payment Amount Y Interbank Settlement Date Payment Value Date Y Instructing Agent Agent that is debited in the RTGS Y Instructed Agent Agent that is credited in the RTGS Y Debtor Financial Institution whose account

is debited with the payment Y

Debtor Account Financial Institution account that is debited

Debtor Agent Agent servicing an account for the debtor and party who executes the debit of Debtor account.

Debtor Agent Account Identification of account of debtor agent

Creditor Agent Agent servicing an account for the debtor and party who executes the credit of Creditor account.

Creditor Agent Account Identification of account of creditor agent

Creditor Financial Institution whose account is credited with the payment

Y

Creditor Account Party account that is credited Instruction for Creditor Agent Sender to receiver information Purpose Payment Transaction Code Y

Use Case EWBCPHMM East West Bank has received a payment instruction from its Rural Bank ABC with account 12345688 to transfer fund to Rural Bank ABC account 87654321 in HSBCPHMM Hongkong and Shanghai Bank.

<?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId>

63

<FinInstnId> <ClrSysMmbId> <MmbId>EWBCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>2020042900002</BizMsgIdr> <MsgDefIdr>pacs.009.001.09</MsgDefIdr> <CreDt>2020-05-16T09:13:51.0</CreDt> <!—Payment Priority Request --> <Prty>98</Prty> </AppHdr> <!—Financial Institution Credit Transfer --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.009.001.09"> <FICdtTrf> <GrpHdr> <MsgId>2020042900002</MsgId> <CreDtTm>2020-05-16T09:13:51.0</CreDtTm> <BtchBookg>false</BtchBookg> <NbOfTxs>1</NbOfTxs> <SttlmInf> <SttlmMtd>CLRG</SttlmMtd> <ClrSys> <Cd>BSP</Cd> </ClrSys> </SttlmInf> </GrpHdr> <CdtTrfTxInf> <PmtId> <EndToEndId>2020042900012</EndToEndId> <TxId>2020042900002</TxId> <UETR>956bff26-db55-4f2c-9662-0a37cad90fac</UETR> </PmtId> <PmtTpInf> <ClrChanl>RTGS</ClrChanl> <LclInstrm> <Prtry>RTGS-FICT</Prtry> </LclInstrm> </PmtTpInf> <IntrBkSttlmAmt Ccy="PHP">1000.00</IntrBkSttlmAmt> <IntrBkSttlmDt>2020-05-16</IntrBkSttlmDt> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>EWBCPHMM</MmbId> </ClrSysMmbId>

64

<Othr> <Id>10000135</Id> <SchmeNm> <Prtry>STAC</Prtry> </SchmeNm> </Othr> </FinInstnId> </InstgAgt> <InstdAgt> <FinInstnId> <ClrSysMmbId> <MmbId>HSBCPHMM</MmbId> </ClrSysMmbId> <Othr> <Id>10000210</Id> <SchmeNm> <Prtry>STAC</Prtry> </SchmeNm> </Othr> </FinInstnId> </InstdAgt> <Dbtr> <FinInstnId> <Nm>Rural Bank ABC</Nm> <PstlAdr> <BldgNm>Minerva Building</BldgNm> <Flr>Ground Floor</Flr> <TwnNm>Brgy. Putatan</TwnNm> <TwnLctnNm>National Highway</TwnLctnNm> <DstrctNm>Muntinlupa City</DstrctNm> <Ctry>PH</Ctry> </PstlAdr> </FinInstnId> </Dbtr> <DbtrAcct> <Id> <Othr> <Id>12345688</Id> </Othr> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId> <ClrSysMmbId> <MmbId>EWBCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </DbtrAgt> <CdtrAgt> <FinInstnId> <ClrSysMmbId> <MmbId>HSBCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </CdtrAgt> <Cdtr> <FinInstnId>

65

<Nm>Rural Bank ABC</Nm> <PstlAdr> <BldgNm>Minerva Building</BldgNm> <Flr>Ground Floor</Flr> <TwnNm>Brgy. Putatan</TwnNm> <DstrctNm>Muntinlupa City</DstrctNm> <Ctry>PH</Ctry> </PstlAdr> </FinInstnId> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>87654321</Id> </Othr> </Id> </CdtrAcct> <InstrForCdtrAgt> <InstrInf>Test only</InstrInf> </InstrForCdtrAgt> <Purp> <Prtry>IBFT00</Prtry> </Purp> </CdtTrfTxInf> </FICdtTrf> </Document> 5.9 Stop and Recall Request

5.9.1 camt.056.001.09 Message Item Comment M/O

Business Application Header V02 From Message Sender Y To Message Receiver Y Business Message Identifier Sender’s Unique Reference Y Message Definition Identifier MX Name Identification Y Creation Date Message Creation Date and Time Y Priority Payment Priority Number Y Stop and Recall Request Identification Sender’s Unique Reference Y Assigner Sender of the message Assignee Receiver of the message Creation Date Time Message Creation Date and Time Y Underlying Transaction Transaction Information Y Original Group Information Original Message Identification Referred payment message id Y Original Message Name Identification Referred payment mx type Y Original Creation Date Time Referred payment message

creation date and time Y

Original Interbank Settlement Date Referred Payment Value Date Y Assigner Referred Payment Original Sender Y Cancellation Reason Information Y Reason Reason for the cancellation request Y Additional Information Further details on the cancellation

request

66

Use Case BOPIPHMM Bank of the Philippine Island requested the stop payment for ST200429001 <?xml version="1.0" encoding="UTF-8"?>  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>ST200429001</BizMsgIdr> <MsgDefIdr>camt.056.001.09</MsgDefIdr> <CreDt>2020-05-16T09:13:51.0</CreDt> </AppHdr> <!—Stop and Recall Request --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.056.001.09"> <FIToFIPmtCxlReq> <Assgnmt> <Id>ST200429001</Id> <Assgnr> <Agt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Agt> </Assgnr> <Assgne> <Agt> <FinInstnId> <ClrSysMmbId> <MmbId>UCPBPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Agt> </Assgne> <CreDtTm>2020-05-16T09:13:51.0</CreDtTm>

67

</Assgnmt> <Undrlyg> <TxInf>

<OrgnlGrpInf> <OrgnlMsgId>2020042900001</OrgnlMsgId> <OrgnlMsgNmId>pacs.008.001.08</OrgnlMsgNmId> <OrgnlCreDtTm>2020-04-29T09:13:51.0</OrgnlCreDtTm> </OrgnlGrpInf> <OrgnlIntrBkSttlmDt>2020-04-29</OrgnlIntrBkSttlmDt> <CxlRsnInf> <Rsn> <Prtry>CUST</Prtry> </Rsn> <AddtlInf>Requested by Customer</AddtlInf> </CxlRsnInf> </TxInf> </Undrlyg> </FIToFIPmtCxlReq> </Document> 5.10 Liquidity Credit Transfer


Business Application Header V02 From Message Sender Y To Message Receiver Y Business Message Identifier Sender’s Unique Reference Y Message Definition Identifier MX Name Identification Y Creation Date Message Creation Date and Time Y Priority Payment Priority Number Y Liquidity Credit Transfer V05 Message Header Message Identification Sender’s Unique Reference Y Creation Date Time Message Creation Date and Time Y Liquidity Credit Transfer Liquidity Transfer Identification Y End to End Identification If there is no reference, then the

same transaction identification is provided.

Y

Transaction Identification Sender’s Unique Reference Y UETR Universally Unique Identifier


Creditor Participant that is credit in RTGS Y Creditor Account Participant account that is credited

in RTGS Y

Transferred Amount Amount to be transferred from one account to another

Y

Debtor Participant that is debited in RTGS Y Debtor Account Participant account that is debited

in RTGS Y

Settlement Date Transaction Value Date Y

Use Case MBTCPHMM Metrobank initiate SSA Top up

68

<?xml version="1.0" encoding="UTF-8"?> <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>LC200429001</BizMsgIdr> <MsgDefIdr>camt.050.001.05</MsgDefIdr> <CreDt>2020-04-29T09:13:51.0</CreDt> <Prty>98</Prty </AppHdr> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.050.001.05"> <LqdtyCdtTrf> <MsgHdr> <MsgId>LC200429001</MsgId> <CreDtTm>2020-04-29T09:13:51.0</CreDtTm> </MsgHdr> <LqdtyCdtTrf> <LqdtyTrfId> <EndToEndId>20200429001</EndToEndId> <TxId>20200429001</TxId> <UETR>955e569b-5769-4d11-a7a6-fb01a62cdaf0</UETR> </LqdtyTrfId> <Cdtr> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>13000260</Id> </Othr> </Id> </CdtrAcct> <TrfdAmt> <AmtWthCcy Ccy="PHP">300000.00</AmtWthCcy>

69

</TrfdAmt> <Dbtr> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Dbtr> <DbtrAcct> <Id> <Othr> <Id>10000260</Id> </Othr> </Id> </DbtrAcct> <SttlmDt>2020-04-29</SttlmDt> </LqdtyCdtTrf> </LqdtyCdtTrf> </Document> 5.11 Liquidity Debit Transfer


Business Application Header V02 From Message Sender Y To Message Receiver Y Business Message Identifier Sender’s Unique Reference Y Message Definition Identifier MX Name Identification Y Creation Date Message Creation Date and Time Y Priority Payment Priority Number Y Liquidity Debit Transfer V05 Message Header Message Identification Sender’s Unique Reference Y Creation Date Time Message Creation Date and Time Y Liquidity Debit Transfer Liquidity Transfer Identification Y End to End Identification If there is no reference, then the


Y



Creditor Participant that is credit in RTGS Y Creditor Account Participant account that is credited

in RTGS Y

Transferred Amount Amount to be transferred from one account to another

Y

Debtor Participant that is debited in RTGS Y Debtor Account Participant account that is debited

in RTGS Y

Settlement Date Transaction Value Date Y

70

Use Case MBTCPHMM make repayments to cover the drawdowns made from the ILF credit line.

<?xml version="1.0" encoding="UTF-8"?> <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>LC200429001</BizMsgIdr> <MsgDefIdr>camt.051.001.05</MsgDefIdr> <CreDt>2020-04-29T09:13:51.0</CreDt> <Prty>98</Prty </AppHdr> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.051.001.05"> <LqdtyCdtTrf> <MsgHdr> <MsgId>LC200429001</MsgId> <CreDtTm>2020-04-29T09:13:51.0</CreDtTm> </MsgHdr> <LqdtyCdtTrf> <LqdtyTrfId> <EndToEndId>20200429001</EndToEndId> <TxId>20200429001</TxId> <UETR>955e569b-5769-4d11-a7a6-fb01a62cdaf0</UETR> </LqdtyTrfId> <Cdtr> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>31000260</Id> </Othr> </Id>

71

</CdtrAcct> <TrfdAmt> <AmtWthCcy Ccy="PHP">300000.00</AmtWthCcy> </TrfdAmt> <Dbtr> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Dbtr> <DbtrAcct> <Id> <Othr> <Id>10000260</Id> </Othr> </Id> </DbtrAcct> <SttlmDt>2020-04-29</SttlmDt> </LqdtyCdtTrf> </LqdtyCdtTrf> </Document> 5.12 Direct Debit Transfer


Business Application Header V02 From Message Sender Y To Message Receiver Y Business Message Identifier Sender’s Unique Reference Y Message Definition Identifier MX Name Identification Y Creation Date Message Creation Date and Time Y Priority Payment Priority Number Y Direct Debit Transfer V4 Message identification Payment Reference Y Creation Date Time Message Creation Date and Time Y Number of Transactions Fixed Value: 1, single customer

credit transfer Y

Settlement Information Y Credit Transfer Transaction Y Credit Identification Sender’s Unique Reference Y Batch Booking Fixed Value: false, individual

booking Y



Y

Local Instrument RTGS-FICT – single financial institution credit transfer

Y

Interbank Settlement Date Payment Value Date Y Instructing Agent Participant that is debited in the

RTGS Y

72

Instructed Agent Participant that is credited in the RTGS

Y

Creditor Financial Institution whose account is credited with the payment

Y

Direct Debit Transaction Information Payment Identification End to End Identification If there is no reference, then the


Y



Interbank Settlement Amount Payment amount Debtor Financial Institution whose account

is debited with the payment Y

Purpose Payment Transaction Code Y Use Case CASGPHM1 CASG Unit transmit the scheduled collection of annual supervisory fees to BSP

<?xml version="1.0" encoding="UTF-8"?> <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>CASGPHM1</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>CSGASF20042900001</BizMsgIdr> <MsgDefIdr>pacs.010.001.08</MsgDefIdr> <CreDt>2020-04-29T10:13:51.0</CreDt> <!—Payment Priority Request --> <Prty>10</Prty> </AppHdr> <!—Direct Debit --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.010.001.04"> <FIDrctDbt> <GrpHdr> <MsgId>CSGASF20042900001</MsgId> <CreDtTm>2020-04-29T10:13:51.0</CreDtTm> <NbOfTxs>1</NbOfTxs> </GrpHdr> <CdtInstr>

73

<CdtId>CSGASF20042900001</CdtId> <BtchBookg>false</BtchBookg> <PmtTpInf> <ClrChanl>RTGS</ClrChanl> <LclInstrm> <Prtry>RTGS-SDDT</Prtry> </LclInstrm> </PmtTpInf> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>CASGPHM1</MmbId> </ClrSysMmbId> <Othr> <Id>30190401</Id> <SchmeNm> <Prtry>STAC</Prtry> </SchmeNm> </Othr> </FinInstnId> </InstgAgt> <InstdAgt> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </InstdAgt> <Cdtr> <FinInstnId> <ClrSysMmbId> <MmbId>CASGPHM1</MmbId> </ClrSysMmbId> <Othr> <Id>10000260</Id> <SchmeNm> <Prtry>STAC</Prtry> </SchmeNm> </Othr> </FinInstnId> </Cdtr> <DrctDbtTxInf> <PmtId> <EndToEndId>CSGASF20042900001</EndToEndId> <TxId>CSGASF20042900001</TxId> <UETR>ac6f3327-d766-44f4-9887-8d097902cb0d</UETR> </PmtId> <IntrBkSttlmAmt Ccy="PHP">5000.00</IntrBkSttlmAmt> <Dbtr> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Dbtr> <Purp> <Prtry>CSGASF</Prtry>

74

</Purp> </DrctDbtTxInf> </CdtInstr> </FIDrctDbt> </Document> 5.13 Third Party Financial Institution Credit Transfer


Business Application Header V02 From Message Sender Y To Message Receiver Y Business Message Identifier Sender’s Unique Reference Y Message Definition Identifier MX Name Identification Y Creation Date Message Creation Date and Time Y Priority Payment Priority Number Y Financial Institution Credit Transfer V9 Message identification Payment Reference Y Creation Date Time Message Creation Date and Time Y Batch Booking Fixed Value: false, individual

booking Y


Y

Settlement Information Y Credit Transfer Transaction Information Payment Identification Y End To End Identification Related Reference, NOTPROVIDED






Y

Local Instrument RTGS-IFCT – Third-Party Interbank credit transfer

Y

Interbank Settlement Amount Amount of money moved between Instructing Agent and Instructed Agent

Y

Interbank Settlement Date Payment Value Date Y Instructing Agent Participant sending the message Y Instructed Agent Participant receiving the message

RTGS System Y

Debtor Participant whose account is debited in RTGS

Y

Debtor Account Participant account that is debited in RTGS

Y

Creditor Participant whose account is credited in RTGS

Y

Creditor Account Participant account that is credited in RTGS

Y

Purpose Payment Transaction Code Y

75

Use Case BTr NRoSS transmits the secondary market trade of EWBCPHMM and HSBCPHMM <!—Business Application Header --> <?xml version="1.0" encoding="UTF-8"?> <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BNNNPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>IPAY202004290001</BizMsgIdr> <MsgDefIdr>pacs.009.001.08</MsgDefIdr> <CreDt>2020-04-29T09:00:51.0</CreDt> <!—Payment Priority Request --> <Prty>19</Prty> </AppHdr> <!—Third Party Financial Institution Credit Transfer --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.009.001.09"> <FICdtTrf> <GrpHdr> <MsgId>2020042900002</MsgId> <CreDtTm>2020-05-16T09:13:51.0</CreDtTm> <BtchBookg>false</BtchBookg> <NbOfTxs>1</NbOfTxs> <SttlmInf> <SttlmMtd>CLRG</SttlmMtd> <ClrSys> <Cd>BSP</Cd> </ClrSys> </SttlmInf> </GrpHdr> <CdtTrfTxInf> <PmtId> <EndToEndId>2020042900001</EndToEndId> <TxId>2020042900001</TxId> <UETR>856bff26-db55-4f2c-9662-0a37cad90fac</UETR> </PmtId> <PmtTpInf> <ClrChanl>RTGS</ClrChanl> <LclInstrm> <Prtry>RTGS-IFCT</Prtry>

76

</LclInstrm> </PmtTpInf> <IntrBkSttlmAmt Ccy="PHP">1000.00</IntrBkSttlmAmt> <IntrBkSttlmDt>2020-05-16</IntrBkSttlmDt> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BUTRPHM1</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> <InstdAgt> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </InstdAgt> <Dbtr> <FinInstnId> <ClrSysMmbId> <MmbId>EWBCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Dbtr> <DbtrAcct> <Id> <Othr> <Id>10000135</Id> </Othr> </Id> </DbtrAcct> <Cdtr> <FinInstnId> <ClrSysMmbId> <MmbId>HSBCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>10000210</Id> </Othr> </Id> </CdtrAcct> <Purp> <Prtry>GSOTC1</Prtry> </Purp> </CdtTrfTxInf> </FICdtTrf> </Document>

77

5.14 Financial Institution Batch Net/Gross Credit Transfer


Business Application Header V02 From Message Sender Y To Message Receiver Y Business Message Identifier Sender’s Unique Reference Y Message Definition Identifier MX Name Identification Y Creation Date Message Creation Date and Time Y Priority Payment Priority Number Y Financial Institution Credit Transfer V9 Message identification Payment Reference Y Creation Date Time Message Creation Date and Time Y Batch Booking Fixed Value: false, individual

booking Y


Y

Settlement Information Y Instructing Agent Sender of the message Y Instructed Agent Receiver of the message Y Credit Transfer Transaction Information Payment Identification Y End To End Identification Related Reference, NOTPROVIDED






Y

Local Instrument RTGS-NFCT – Batch Net financial institution credit transfer RTGS-GFCT – Batch Gross financial institution credit transfer

Y

Interbank Settlement Amount Payment Amount Y Interbank Settlement Date Payment Value Date Y Debtor Participant whose account is

debited in RTGS Use name and postal address if entry involves a sponsored client

Y

Debtor Account Participant account that is debited in RTGS Required if entry does not involve a sponsored client

Debtor Agent Servicing Agent of InstaPay Sponsored Client Not Required if entry does not involve a sponsored client

Debtor Agent Account Account that is debited in RTGS Not Required if entry does not involve a sponsored client

78

Creditor Agent Participant whose account is credited in RTGS Not Required if entry does not involve a sponsored client

Creditor Agent Account Participant account that is credited in RTGS Not Required if entry does not involve a sponsored client

Creditor Participant whose account is credited in RTGS Use name and postal address if entry involves a sponsored client

Y

Creditor Account Participant account that is credited in RTGS Required if entry does not involve a sponsored client

Y

Purpose Payment Transaction Code Y Use Case: BNNNPHM2 Bancnet transmit the InstaPay batch gross result

<!—Business Application Header --> <?xml version="1.0" encoding="UTF-8"?> <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>BNNNPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>IPAY202004290001</BizMsgIdr> <MsgDefIdr>pacs.009.001.08</MsgDefIdr> <CreDt>2020-04-29T09:00:51.0</CreDt> <!—Payment Priority Request --> <Prty>11</Prty> </AppHdr> <!—Batch Gross Credit Transfer --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.009.001.09"> <FICdtTrf> <GrpHdr> <MsgId>IPAY202004290001</MsgId> <CreDtTm>2020-04-29T09:00:51.0</CreDtTm>

79

<BtchBookg>false</BtchBookg> <NbOfTxs>7</NbOfTxs> <IntrBkSttlmDt>2020-04-29</IntrBkSttlmDt> <SttlmInf> <SttlmMtd>CLRG</SttlmMtd> <ClrSys> <Prtry>BSP</Prtry> </ClrSys> </SttlmInf> <PmtTpInf> <ClrChanl>RTGS</ClrChanl> <LclInstrm> <Prtry>RTGS-GFCT</Prtry> </LclInstrm> </PmtTpInf> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BNNNPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> <InstdAgt> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </InstdAgt> </GrpHdr> <CdtTrfTxInf> Transaction #1 <PmtId> <EndToEndId>IPAY20042900001</EndToEndId> <TxId>IPAY20042900001</TxId> <UETR>f5290d41-1ffe-4479-b9fb-cc2c51dfb391</UETR> </PmtId> <IntrBkSttlmAmt Ccy="PHP">235000.00</IntrBkSttlmAmt> <Dbtr> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Dbtr> <DbtrAcct> <Id> <Othr> <Id>13000260</Id> <SchmeNm> <Prtry>STAC</Prtry> </SchmeNm> </Othr> </Id> </DbtrAcct> <Cdtr> <FinInstnId> <ClrSysMmbId>

80

<MmbId>BNNNPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>30193000</Id> </Othr> </Id> </CdtrAcct> <Purp> <Prtry>IPAYCL</Prtry> </Purp> </CdtTrfTxInf> <CdtTrfTxInf> Transaction #2 <PmtId> <EndToEndId>IPAY20042900002</EndToEndId> <TxId>IPAY20042900002</TxId> <UETR>b57639bc-524c-4c61-9005-e3b76da29b3f</UETR> </PmtId> <IntrBkSttlmAmt Ccy="PHP">35000.00</IntrBkSttlmAmt> <Dbtr> <FinInstnId> <ClrSysMmbId> <MmbId>BNNNPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </Dbtr> <DbtrAcct> <Id> <Othr> <Id>30193000</Id> </Othr> </Id> </DbtrAcct> <CdtrAgt> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </CdtrAgt> <CdtrAgtAcct> <Id> <Othr> <Id>10000260</Id> </Othr> </Id> </CdtrAgtAcct> <Cdtr> <FinInstnId> <Nm>PAYMAYA</Nm> <PstlAdr> <AdrLine>MANILA, PH</AdrLine> </PstlAdr> </FinInstnId>

81

</Cdtr> <Purp> <Prtry>IPAYCL</Prtry> </Purp> </CdtTrfTxInf> <CdtTrfTxInf> Transation #3 <PmtId> <EndToEndId>IPAY20042900003</EndToEndId> <TxId>IPAY20042900003</TxId> <UETR>bb2a2aa3-ffd1-4234-9fa6-77179c8db014</UETR> </PmtId> <IntrBkSttlmAmt Ccy="PHP">50000.00</IntrBkSttlmAmt> <Dbtr> <FinInstnId> <ClrSysMmbId> <MmbId>BNNNPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </Dbtr> <DbtrAcct> <Id> <Othr> <Id>30193000</Id> </Othr> </Id> </DbtrAcct> <CdtrAgt> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </CdtrAgt> <CdtrAgtAcct> <Id> <Othr> <Id>10000260</Id> </Othr> </Id> </CdtrAgtAcct> <Cdtr> <FinInstnId> <Nm>OMNIPAY</Nm> <PstlAdr> <AdrLine>MANILA, PH</AdrLine> </PstlAdr> </FinInstnId> </Cdtr> <Purp> <Prtry>IPAYCL</Prtry> </Purp> </CdtTrfTxInf> <CdtTrfTxInf> Transaction #4 <PmtId> <EndToEndId>IPAY20042900004</EndToEndId> <TxId>IPAY20042900004</TxId> <UETR>58b783f1-047a-490c-a08d-239b072af533</UETR>

82

</PmtId> <IntrBkSttlmAmt Ccy="PHP">199000.00</IntrBkSttlmAmt> <Dbtr> <FinInstnId> <ClrSysMmbId> <MmbId>BNNNPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </Dbtr> <DbtrAcct> <Id> <Othr> <Id>30193000</Id> </Othr> </Id> </DbtrAcct> <Cdtr> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>10000050</Id> </Othr> </Id> </CdtrAcct> <Purp> <Prtry>IPAYCL</Prtry> </Purp> </CdtTrfTxInf> <CdtTrfTxInf> Transaction #5 <PmtId> <EndToEndId>IPAY20042900005</EndToEndId> <TxId>IPAY20042900005</TxId> <UETR>071e21be-12b0-4cb3-b912-9f3bb8841d2f</UETR> </PmtId> <IntrBkSttlmAmt Ccy="PHP">61500.00</IntrBkSttlmAmt> <Dbtr> <FinInstnId> <Nm>GXI</Nm> <PstlAdr> <AdrLine>MANILA, PH</AdrLine> </PstlAdr> </FinInstnId> </Dbtr> <DbtrAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </DbtrAgt> <DbtrAgtAcct>

83

<Id> <Othr> <Id>13000050</Id> </Othr> </Id> </DbtrAgtAcct> <Cdtr> <FinInstnId> <ClrSysMmbId> <MmbId>BNNNPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>30193000</Id> </Othr> </Id> </CdtrAcct> <Purp> <Prtry>IPAYCL</Prtry> </Purp> </CdtTrfTxInf> <CdtTrfTxInf> Transaction #6 <PmtId> <EndToEndId>IPAY20042900006</EndToEndId> <TxId>IPAY20042900006</TxId> <UETR>7be611e4-0d91-46b9-ba54-7e29e58ba912</UETR> </PmtId> <IntrBkSttlmAmt Ccy="PHP">25000.00</IntrBkSttlmAmt> <Dbtr> <FinInstnId> <ClrSysMmbId> <MmbId>BNNNPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </Dbtr> <DbtrAcct> <Id> <Othr> <Id>30193000</Id> </Othr> </Id> </DbtrAcct> <Cdtr> <FinInstnId> <ClrSysMmbId> <MmbId>RCBCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>10000420</Id> </Othr>

84

</Id> </CdtrAcct> <Purp> <Prtry>IPAYCL</Prtry> </Purp> </CdtTrfTxInf> <CdtTrfTxInf> Transaction #7 <PmtId> <EndToEndId>IPAY20042900007</EndToEndId> <TxId>IPAY20042900007</TxId> <UETR>f9dc91e8-5bb7-44dd-bcb1-eef441cbcfe9</UETR> </PmtId> <IntrBkSttlmAmt Ccy="PHP">12500.00</IntrBkSttlmAmt> <Dbtr> <FinInstnId> <Nm>RCBC 1ST</Nm> <PstlAdr> <AdrLine>MANILA, PH</AdrLine> </PstlAdr> </FinInstnId> </Dbtr> <DbtrAgt> <FinInstnId> <ClrSysMmbId> <MmbId>RCBCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </DbtrAgt> <DbtrAgtAcct> <Id> <Othr> <Id>13000420</Id> </Othr> </Id> </DbtrAgtAcct> <Cdtr> <FinInstnId> <ClrSysMmbId> <MmbId>BNNNPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>30193000</Id> </Othr> </Id> </CdtrAcct> <Purp> <Prtry>IPAYCL</Prtry> </Purp> </CdtTrfTxInf> </FICdtTrf> </Document>

85

Use Case: PESONet Batch Net PCHC transmit the PESONet batch net result <!—Business Application Header --> <?xml version="1.0" encoding="UTF-8"?> <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PCHCPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>PNET202004290001</BizMsgIdr> <MsgDefIdr>pacs.009.001.08</MsgDefIdr> <CreDt>2020-04-29T09:00:51.0</CreDt> <!—Payment Priority Request --> <Prty>11</Prty> </AppHdr> <!—Batch Net Credit Transfer--> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.009.001.09"> <FICdtTrf> <GrpHdr> <MsgId>PNET202004290001</MsgId> <CreDtTm>2020-04-29T09:00:51.0</CreDtTm> <BtchBookg>false</BtchBookg> <NbOfTxs>5</NbOfTxs> <IntrBkSttlmDt>2020-04-29</IntrBkSttlmDt> <SttlmInf> <SttlmMtd>CLRG</SttlmMtd> <ClrSys> <Prtry>BSP</Prtry> </ClrSys> </SttlmInf> <PmtTpInf> <ClrChanl>RTGS</ClrChanl> <LclInstrm> <Prtry>RTGS-NFCT</Prtry> </LclInstrm> </PmtTpInf> </GrpHdr> <CdtTrfTxInf>

86

<PmtId> <EndToEndId>PNET20042900001</EndToEndId> <TxId>PNET20042900001</TxId> <UETR>71c2e959-b086-4fcc-9480-76f4124ce205</UETR> </PmtId> <IntrBkSttlmAmt Ccy="PHP">1000000.00</IntrBkSttlmAmt> <Dbtr> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Dbtr> <DbtrAcct> <Id> <Othr> <Id>13000260</Id> </Othr> </Id> </DbtrAcct> <Cdtr> <FinInstnId> <ClrSysMmbId> <MmbId>PCHCPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>30194000</Id> </Othr> </Id> </CdtrAcct> <Purp> <Prtry>PNETCL</Prtry> </Purp> </CdtTrfTxInf> <CdtTrfTxInf> <PmtId> <EndToEndId>PNET20042900002</EndToEndId> <TxId>PNET20042900002</TxId> <UETR>e884e16b-9649-4c88-98db-4eebf9add6ab</UETR> </PmtId> <IntrBkSttlmAmt Ccy="PHP">1500000.00</IntrBkSttlmAmt> <Dbtr> <FinInstnId> <ClrSysMmbId> <MmbId>PCHCPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </Dbtr> <DbtrAcct> <Id> <Othr> <Id>30194000</Id> </Othr>

87

</Id> </DbtrAcct> <Cdtr> <FinInstnId> <ClrSysMmbId> <MmbId>BOPIPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>10000050</Id> </Othr> </Id> </CdtrAcct> <Purp> <Prtry>PNETCL</Prtry> </Purp> </CdtTrfTxInf> <CdtTrfTxInf> <PmtId> <EndToEndId>PNET20042900003</EndToEndId> <TxId>PNET20042900003</TxId> <UETR>d538382d-e33b-4401-8cf5-5de0c5d1e438</UETR> </PmtId> <IntrBkSttlmAmt Ccy="PHP">875000.00</IntrBkSttlmAmt> <Dbtr> <FinInstnId> <ClrSysMmbId> <MmbId>BNORPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Dbtr> <DbtrAcct> <Id> <Othr> <Id>13000035</Id> </Othr> </Id> </DbtrAcct> <Cdtr> <FinInstnId> <ClrSysMmbId> <MmbId>PCHCPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>30194000</Id> </Othr> </Id> </CdtrAcct> <Purp> <Prtry>PNETCL</Prtry>

88

</Purp> </CdtTrfTxInf> <CdtTrfTxInf> <PmtId> <EndToEndId>PNET20042900004</EndToEndId> <TxId>PNET20042900004</TxId> <UETR>58b783f1-047a-490c-a08d-239b072af533</UETR> </PmtId> <IntrBkSttlmAmt Ccy="PHP">750000.00</IntrBkSttlmAmt> <Dbtr> <FinInstnId> <ClrSysMmbId> <MmbId>PCHCPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </Dbtr> <DbtrAcct> <Id> <Othr> <Id>30194000</Id> </Othr> </Id> </DbtrAcct> <Cdtr> <FinInstnId> <ClrSysMmbId> <MmbId>PNBMPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>10000330</Id> </Othr> </Id> </CdtrAcct> <Purp> <Prtry>PNETCL</Prtry> </Purp> </CdtTrfTxInf> <CdtTrfTxInf> <PmtId> <EndToEndId>PNET20042900005</EndToEndId> <TxId>PNET20042900005</TxId> <UETR>071e21be-12b0-4cb3-b912-9f3bb8841d2f</UETR> </PmtId> <IntrBkSttlmAmt Ccy="PHP">375000.00</IntrBkSttlmAmt> <Dbtr> <FinInstnId> <ClrSysMmbId> <MmbId>UBPHPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </Dbtr> <DbtrAgtAcct> <Id>

89

<Othr> <Id>13000460</Id> </Othr> </Id> </DbtrAgtAcct> <Cdtr> <FinInstnId> <ClrSysMmbId> <MmbId>PCHCPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>30194000</Id> </Othr> </Id> </CdtrAcct> <Purp> <Prtry>PNETCL</Prtry> </Purp> </CdtTrfTxInf> </FICdtTrf> </Document> 5.15 Statement Message

BSP (PhilPaSSplus) End of Day Statement Report

<!—Business Application Header --> <?xml version="1.0" encoding="UTF-8"?> <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCHPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>123456/950</BizMsgIdr> <MsgDefIdr>camt.053.001.08</MsgDefIdr> <CreDt>2020-04-29T18:00:00.0</CreDt> </AppHdr> <!—Statement Message -->

90

<?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.053.001.08"> <BkToCstmrStmt> <GrpHdr> <MsgId>123456/950</MsgId> <CreDtTm>2020-04-29T18:00:00.0</CreDtTm> <AddtlInf>GBST</AddtlInf> </GrpHdr> <Stmt> <Id>123456/950</Id> <StmtPgntn> <PgNb>1</PgNb> <LastPgInd>true</LastPgInd> </StmtPgntn> <ElctrncSeqNb>105</ElctrncSeqNb> <CreDtTm>2020-04-29T18:00:00.0</CreDtTm> <Acct> <Id> <Othr> <Id>10000260</Id> <SchmeNm> <Prtry>STAC</Prtry> </SchmeNm> </Othr> </Id> <Ownr> <Nm>METROPOLITAN BANK AND TCO</Nm> <PstlAdr> <AdrLine>METROBANK PLAZA GIL PUYAT AVE MKTI</AdrLine> </PstlAdr> <Id> <OrgId> <Othr> <Id>MBTCPHMM</Id> <SchmeNm> <Prtry>PCOD</Prtry> </SchmeNm> </Othr> </OrgId> </Id> </Ownr> </Acct> <Bal> <Tp> <CdOrPrtry> <Cd>PRCD</Cd> </CdOrPrtry> </Tp> <Amt Ccy="PHP">0.00</Amt> <CdtDbtInd>CRDT</CdtDbtInd> <Dt> <Dt>2020-04-29</Dt> </Dt>

91

</Bal> <Bal> <Tp> <CdOrPrtry> <Cd>CLBD</Cd> </CdOrPrtry> </Tp> <Amt Ccy="PHP">0.00</Amt> <CdtDbtInd>CRDT</CdtDbtInd> <Dt> <Dt>2020-04-29</Dt> </Dt> </Bal> <Ntry> <NtryRef>1</NtryRef> <Amt Ccy="PHP">1000000.00</Amt> <CdtDbtInd>CRDT</CdtDbtInd> <Sts> <Cd>BOOK</Cd> </Sts> <BookgDt> <DtTm>2020-04-29T09:00:51.0</DtTm> </BookgDt> <ValDt> <Dt>2020-04-29</Dt> </ValDt> <BkTxCd> <Prtry> <Cd>pacs.009.001.09</Cd> </Prtry> </BkTxCd> <NtryDtls> <TxDtls> <Refs> <MsgId>BEGBAL000000001</MsgId> <EndToEndId>NOTPROVIDED</EndToEndId> <UETR>fb64753a-e52f-4683-9115-fd6752e3dac7</UETR> <TxId>BEGBAL000000001</TxId> </Refs> <RltdAgts> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>ZZCFASRT</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> <InstdAgt> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCPHMM</MmbId> </ClrSysMmbId> </FinInstnId>

92

</InstdAgt> </RltdAgts> <LclInstrm> <Prtry>RTGS-IFCT</Prtry> </LclInstrm> <Purp> <Prtry>BEGBAL</Prtry> </Purp> </TxDtls> </NtryDtls> </Ntry> <Ntry> <NtryRef>2</NtryRef> <Amt Ccy="PHP">35000.00</Amt> <CdtDbtInd>CRDT</CdtDbtInd> <Sts> <Cd>BOOK</Cd> </Sts> <BookgDt> <DtTm>2020-04-29T09:00:51.0</DtTm> </BookgDt> <ValDt> <Dt>2020-04-29</Dt> </ValDt> <BkTxCd> <Prtry> <Cd>pacs.009.001.09</Cd> </Prtry> </BkTxCd> <NtryDtls> <TxDtls> <Refs> <MsgId>IPAY202004290001</MsgId> <EndToEndId>IPAY20042900002</EndToEndId> <UETR>b57639bc-524c-4c61-9005-e3b76da29b3f</UETR> <TxId>IPAY20042900002</TxId> </Refs> <RltdAgts> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BNNNPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> <InstdAgt> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </InstdAgt> </RltdAgts>

93

<LclInstrm> <Prtry>RTGS-GFCT</Prtry> </LclInstrm> <Purp> <Prtry>IPAYCL</Prtry> </Purp> </TxDtls> </NtryDtls> </Ntry> <Ntry> <NtryRef>3</NtryRef> <Amt Ccy="PHP">50000.00</Amt> <CdtDbtInd>CRDT</CdtDbtInd> <Sts> <Cd>BOOK</Cd> </Sts> <BookgDt> <DtTm>2020-04-29T09:00:51.0</DtTm> </BookgDt> <ValDt> <Dt>2020-04-29</Dt> </ValDt> <BkTxCd> <Prtry> <Cd>pacs.009.001.09</Cd> </Prtry> </BkTxCd> <NtryDtls> <TxDtls> <Refs> <MsgId>IPAY202004290001</MsgId> <EndToEndId>IPAY20042900003</EndToEndId> <UETR>bb2a2aa3-ffd1-4234-9fa6-77179c8db014</UETR> <TxId>IPAY20042900003</TxId> </Refs> <RltdAgts> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>BNNNPHM2</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> <InstdAgt> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </InstdAgt> </RltdAgts> <LclInstrm> <Prtry>RTGS-GFCT</Prtry>

94

</LclInstrm> <Purp> <Prtry>IPAYCL</Prtry> </Purp> </TxDtls> </NtryDtls> </Ntry> <Ntry> <NtryRef>4</NtryRef> <Amt Ccy="PHP">5000.00</Amt> <CdtDbtInd>DBIT</CdtDbtInd> <Sts> <Cd>BOOK</Cd> </Sts> <BookgDt> <DtTm>2020-04-29T10:13:51.0</DtTm> </BookgDt> <ValDt> <Dt>2020-04-29</Dt> </ValDt> <BkTxCd> <Prtry> <Cd>pacs.009.001.09</Cd> </Prtry> </BkTxCd> <NtryDtls> <TxDtls> <Refs> <MsgId>CSGASF20042900001</MsgId> <EndToEndId>CSGASF20042900001</EndToEndId> <UETR>ac6f3327-d766-44f4-9887-8d097902cb0d</UETR> <TxId>CSGASF20042900001</TxId> </Refs> <RltdAgts> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>CASGPHM1</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> <InstdAgt> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </InstdAgt> </RltdAgts> <LclInstrm> <Prtry>RTGS-IFCT</Prtry> </LclInstrm> <Purp>

95

<Prtry>CSGASF</Prtry> </Purp> </TxDtls> </NtryDtls> </Ntry> <Ntry> <NtryRef>5</NtryRef> <Amt Ccy="PHP">1080000.00</Amt> <CdtDbtInd>DBIT</CdtDbtInd> <Sts> <Cd>BOOK</Cd> </Sts> <BookgDt> <DtTm>2020-04-29T10:13:51.0</DtTm> </BookgDt> <ValDt> <Dt>2020-04-29</Dt> </ValDt> <BkTxCd> <Prtry> <Cd>pacs.010.001.08</Cd> </Prtry> </BkTxCd> <NtryDtls> <TxDtls> <Refs> <MsgId>EOD202004290010</MsgId> <EndToEndId>CSGASF20042900001</EndToEndId> <UETR>305963b0-9969-4585-b72a-106e0fda9b45</UETR> <TxId>EOD202004290010</TxId> </Refs> <RltdAgts> <InstgAgt> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </InstgAgt> <InstdAgt> <FinInstnId> <ClrSysMmbId> <MmbId>ZZCFASRT</MmbId> </ClrSysMmbId> </FinInstnId> </InstdAgt> </RltdAgts> <LclInstrm> <Prtry>RTGS-SDDT</Prtry> </LclInstrm> <Purp> <Prtry>EODSWP</Prtry> </Purp>

96

</TxDtls> </NtryDtls> </Ntry> </Stmt> </BkToCstmrStmt> </Document> 5.16 PhilPaSSplus Business Day Information <?xml version="1.0" encoding="UTF-8"?> <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCHPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr>123456</BizMsgIdr> <MsgDefIdr>camt.019.001.07</MsgDefIdr> <CreDt>2020-05-20T09:00:00</CreDt> </AppHdr> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.019.001.07"> <RtrBizDayInf> <MsgHdr> <MsgId>123456</MsgId> <CreDtTm>2020-05-20T09:00:00</CreDtTm> </MsgHdr> <RptOrErr> <BizRpt> <SysId> <MktInfrstrctrId> <Prtry>BSP</Prtry> </MktInfrstrctrId> </SysId> <BizDayOrErr> <BizDayInf> <SysDt> <Dt>2020-05-16</Dt> </SysDt> <SysInfPerCcy><Evt> <Tp> <Prtry> <Id>Start of business day</Id>

97

</Prtry> </Tp> <SchdldTm>2020-05-16T08:00:00</SchdldTm> <StartTm>2020-05-16T08:01:00</StartTm> </Evt> </SysInfPerCcy> </BizDayInf> </BizDayOrErr> </BizRpt> </RptOrErr> </RtrBizDayInf> </Document> 5.17 Message Reject <!—Business Application Header --> <?xml version="1.0" encoding="UTF-8"?> <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.02"> <Fr> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>PHCBPHMA</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <ClrSysMmbId> <MmbId>MBTCHPHMM</MmbId> </ClrSysMmbId> </FinInstnId> </FIId> </To> <BizMsgIdr> A60000044551</BizMsgIdr> <MsgDefIdr>admi.002.001.01</MsgDefIdr> <CreDt>2020-05-16T09:05:00.0</CreDt> </AppHdr> <!—Message Reject --> <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:admi.002.001.01"> <admi.002.001.01> <RltdRef> <Ref>IBCP-BOPI051620-02</Ref> </RltdRef> <Rsn> <RjctgPtyRsn>EA1</RjctgPtyRsn> <RjctnDtTm>2020-05-16T09:04:45.0</RjctnDtTm> <RsnDesc>Text block has invalid format</RsnDesc> <AddtlData>Invalid MX input: [1,1366] cvc-complex-type.2.4.a: Invalid content was found starting with element 'NbOfTxs'. One of '{"urn:iso:std:iso:20022:tech:xsd:pacs.009.001.07":BtchBookg}' is expected </AddtlData> </Rsn>

98

</admi.002.001.01> </Document> 6. Annexes

6.1 Annex A – Local Instruments

Code

Name

Definition

RTGS-FICT pacs.009.001.09 FI to FI Financial Credit Transfer

RTGS-NFCT pacs.009.001.09_NET FI to FI Financial Credit Transfer Batch Net

RTGS-GFCT pacs.009.001.009_NET FI to FI Financial Credit Transfer Batch Gross

RTGS-SCCT pacs.008.001.09 Single FI to FI Customer Credit Transfer

RTGS-SDDT Pacs.010.001.04 Single FI to FI Direct Debit Transfer

RTGS-SPRT Pacs.004.001.10 Single Payment Return Transfer

RTGS-LQCT cam.050.001.05 Liquidity Credit Transfer

RTGS-LQDT camt.051.001.05 Liquidity Debit Transfer

RTGS-TDDT Pacs.010.001.03 Third Party Single FI to FI Direct Debit Transfer

RTGS-IFCT pacs.009.001.09 Third Party FI to FI Financial Credit Transfer Interbank

RTGS-TSCT Pacs.008.001.09 Third Party Single FI to FI Customer Credit Transfer

6.2 Annex B – Payment Return Reason Code (pacs.004) and Customer Payment Status Reject Reason Code

(pacs.002)

Code Name Definition

AC01 IncorrectAccountNumber Format of the account number specified is not correct

AC03 InvalidCreditorAccountNumber Wrong IBAN in SCT

AC04 ClosedAccountNumber Account number specified has been closed on the bank of account's books

AC06 BlockedAccount Account specified is blocked, prohibiting posting of transactions against it.

AC13 InvalidDebtorAccountType Debtor account type is missing or invalid

AC14 InvalidAgent An agent in the payment chain is invalid.

AC15 AccountDetailsChanged Account details have changed.

99

AC16 AccountInSequestration Account is in sequestration.

AC17 AccountInLiquidation Account is in liquidation.

AG01 TransactionForbidden Transaction forbidden on this type of account (formerly NoAgreement)

AG02 InvalidBankOperationCode Bank Operation code specified in the message is not valid for receiver

AM01 ZeroAmount Specified message amount is equal to zero

AM02 NotAllowedAmount Specific transaction/message amount is greater than allowed maximum

AM03 NotAllowedCurrency Specified message amount is an non processable currency outside of existing agreement

AM04 InsufficientFunds Amount of funds available to cover specified message amount is insufficient.

AM05 Duplication Duplication

AM06 TooLowAmount Specified transaction amount is less than agreed minimum.

AM07 BlockedAmount Amount of funds available to cover specified message amount is insufficient.

AM09 WrongAmount Amount received is not the amount agreed or expected

AM10 InvalidControlSum Sum of instructed amounts does not equal the control sum.

ARDT AlreadyReturnedTransaction Already returned original SCT

BE01 InconsistenWithEndCustomer Identification of end customer is not consistent with associated account number (formerly CreditorConsistency).

BE04 MissingCreditorAddress Specification of creditor's address, which is required for payment, is missing/not correct (formerly IncorrectCreditorAddress).

BE05 UnrecognisedInitiatingParty Party who initiated the message is not recognised by the end customer

BE06 UnknownEndCustomer End customer specified is not known at associated Sort/National Bank Code or does no longer exist in the books

BE07 MissingDebtorAddress Specification of debtor's address, which is required for payment, is missing/not correct.

BE08 BankError Returned as a result of a bank error.

CN01 AuthorisationCancelled Authorisation is cancelled.

CNOR Creditor bank is not registered Creditor bank is not registered under this BIC in the CSM

100

CURR IncorrectCurrency Currency of the payment is incorrect

CUST RequestedByCustomer Cancellation requested by the Debtor

DNOR Debtor bank is not registered Debtor bank is not registered under this BIC in the CSM

DS28 ReturnForTechnicalReason Return following technical problems resulting in erroneous transaction.

DT01 InvalidDate Invalid date (eg, wrong settlement date)

ED01 CorrespondentBankNotPossible Correspondent bank not possible.

ED03 BalanceInfoRequest Balance of payments complementary info is requested

ED05 SettlementFailed Settlement of the transaction has failed.

EMVL EMV Liability Shift The card payment is fraudulent and was not processed with EMV technology for an EMV card.

ERIN ERIOptionNotSupported The Extended Remittance Information (ERI) option is not supported.

FF05 InvalidLocalInstrumentCode Local Instrument code is missing or invalid

FOCR FollowingCancellationRequest Return following a cancellation request

FR01 Fraud Returned as a result of fraud.

FRTR FinalResponseMandateCancelled Final response/tracking is recalled as mandate is cancelled.

MD01 NoMandate No Mandate

MD02 MissingMandatoryInformationIn Mandate

Mandate related information data required by the scheme is missing.

MD06 RefundRequestByEndCustomer Return of funds requested by end customer

MD07 EndCustomerDeceased End customer is deceased.

MS02 NotSpecifiedReasonCustomer Generated

Reason has not been specified by end customer

MS03 NotSpecifiedReasonAgent Generated Reason has not been specified by agent.

NARR Narrative Reason is provided as narrative information in the additional reason information.

NOAS NoAnswerFromCustomer No response from Beneficiary

NOCM NotCompliant Customer account is not compliant with regulatory requirements, for example FICA (in South Africa) or any other regulatory requirements which render an account inactive for certain processing.

101

NOOR NoOriginalTransactionReceived Original SCT never received

PINL PIN Liability Shift The card payment is fraudulent (lost and stolen fraud) and was processed as EMV transaction without PIN verification.

RC01 BankIdentifierIncorrect Bank Identifier code specified in the message has an incorrect format (formerly IncorrectFormatForRoutingCode).

RC07 InvalidCreditorBICIdentifier Incorrrect BIC of the beneficiary Bank in the SCTR

RF01 NotUniqueTransactionReference Transaction reference is not unique within the message.

RR01 Missing Debtor Account or Identification

Specification of the debtor’s account or unique identification needed for reasons of regulatory requirements is insufficient or missing

RR02 Missing Debtor Name or Address Specification of the debtor’s name and/or address needed for regulatory requirements is insufficient or missing.

RR03 Missing Creditor Name or Address Specification of the creditor’s name and/or address needed for regulatory requirements is insufficient or missing.

RR04 Regulatory Reason Regulatory Reason

RUTA ReturnUponUnableToApply Return following investigation request and no remediation possible.

SL01 Specific Service offered by Debtor Agent

Due to specific service offered by the Debtor Agent

SL02 Specific Service offered by Creditor Agent

Due to specific service offered by the Creditor Agent

SL11 Creditor not on Whitelist of Debtor Whitelisting service offered by the Debtor Agent; Debtor has not included the Creditor on its “Whitelist” (yet). In the Whitelist the Debtor may list all allowed Creditors to debit Debtor bank account.

SL12 Creditor on Blacklist of Debtor Blacklisting service offered by the Debtor Agent; Debtor included the Creditor on his “Blacklist”. In the Blacklist the Debtor may list all Creditors not allowed to debit Debtor bank account.

SL13 Maximum number of Direct Debit Transactions exceeded

Due to Maximum allowed Direct Debit Transactions per period service offered by the Debtor Agent.

SL14 Maximum Direct Debit Transaction Amount exceeded

Due to Maximum allowed Direct Debit Transaction amount service offered by the Debtor Agent.

SP01 PaymentStopped Payment is stopped by account holder.

SP02 PreviouslyStopped Previously stopped by means of a stop payment advise.

102

SVNR ServiceNotRendered The card payment is returned since a cash amount rendered was not correct or goods or a service was not rendered to the customer, e.g. in an e-commerce situation.

TM01 CutOffTime Associated message was received after agreed processing cut-off time.

TRAC RemovedFromTracking Return following direct debit being removed from tracking process.

UPAY UnduePayment Payment is not justified.

6.3 Annex C – Cancellation and Request for Return Reason Code (camt.008 and camt.056)


AC03 InvalidCreditorAccountNumber Wrong account number in Credit Transfer.

AGNT IncorrectAgent Agent in the payment workflow is incorrect.

AM09 WrongAmount Amount is not the amount agreed or expected.

COVR CoverCancelledOrReturned Cover payments has either been returned or cancelled.

CURR IncorrectCurrency Currency of the payment is incorrect.

CUST RequestedByCustomer Cancellation requested by the Debtor.

CUTA CancelUponUnableToApply Cancellation requested because an investigation request has been received and no remediation is possible.

DS24 TimeOut Cancellation requested because the original payment order expired due to time-out.

DUPL DuplicatePayment Payment is a duplicate of another payment.

FRAD FraudulentOrigin Cancellation requested following a transaction that was originated fraudulently. The use of the FraudulentOrigin code should be governed by jurisdictions.

FRNA ForwardToNextAgent To complement a rejection response, suggesting the request for cancelation should be forwarded to the next agent in the payment transaction chain.

FRTR FinalResponse Direct Debit Tracking recalled as Mandate Cancelled

INDM IndemnityRequired To express the wish to establish a bilateral indemnity agreement.

SVNR ServiceNotRendered The payment is cancelled since a cash amount rendered was not correct or goods or a service was not rendered to the customer, e.g. in an e-commerce situation.

SYAD RequestToSettlementSystemAdministrator Cancellation requested by System Member to Settlement System Administrator to indicate that the cancellation request must not be forwarded further in the chain.

103

TECH TechnicalProblem Cancellation requested following technical problems resulting in an erroneous transaction.

UPAY UnduePayment Payment is not justified.

6.4 Annex D – Payment return request decline codes (camt.029)


AC04 ClosedAccountNumber Account number specified has been closed on the receiver’s books.

AGNT AgentDecision Reported when the cancellation cannot be accepted because of an agent refuses to cancel.

ARDT AlreadyReturned Cancellation not accepted as the transaction has already been returned.

ARPL AwaitingReply Reported when the cancellation request cannot be processed because no reply has been received yet from the receiver of the request message.

CUST CustomerDecision Reported when the cancellation cannot be accepted because of a customer decision (Creditor).

LEGL LegalDecision Reported when the cancellation cannot be accepted because of regulatory rules.

NARR Narrative Reason is provided as narrative information in the additional reason information.

NOAS NoAnswerFromCustomer No response from beneficiary (to the cancellation request).

NOOR NoOriginalTransactionReceived Original transaction (subject to cancellation) never received.

PTNA PassedtoTheNextAgent Reported when the cancellation request cannot be accepted because the payment instruction has been passed to the next agent.

6.5 Annex E – Rejected Reason Code (admi.002, camt.025, pacs.002)

Code Name Reason

EA1 Text block has invalid format On checking the format of the message sent to the system, the format was found inconsistent with specifications. The Info field of the error message contains an extensive description of the error.

EA107 Incoming message was not recognized or document has got wrong structure

Incoming message was not recognized or document has got wrong structure.

EA113 This document has been already authorized or rejected

An attempt to change status repeatedly, the document status is already authorized or rejected.

EA114 Check of amount according to SWIFT rules has passed unsuccessfully

Entered amount value is not correct.

EA133 Credit account owner cannot be equal to debit account owner

Credit account owner is equal to debit account owner.

104

EA134 Wrong data in AppHdr Invalid data was specified in AppHdr.

EA14 Invalid date format. Expected: YYYY-MM-DD.

The instruction sent to the system contains an invalid value date.

EA15 Account code is not found The instruction has an invalid account code.

EA155 Invalid data in trans type code Entered data in trans type code is invalid.

EA156 Message type mismatch in request Message type is not expected for related document type.

EA157 Zero value are not allowed in mandate limit

Zero value was entered in mandate limit.

EA158 Zero value are not allowed in mandate total limit

Zero value was entered in mandate total limit.

EA159 User can not authorize document The participant has no authority to confirm the document.

EA16 Message is corrupted The signature check routine rejects the signature as invalid.

EA160 Only one of "Fixed amount" or "Maximum amount" must be set

Both fields "Fixed amount" and "Maximum amount" was set.

EA161 Parameter "Count per period" cannot be equal to zero

Parameter "Count per period" value is not correct and cannot be zero.

EA17 Message could not be accepted due to business day schedule

The system cannot accept the incoming message due to the system's business day schedule.

EA176 NRT clearing confirmation must have NRT priority

Internal error.

EA177 Value date is behind of defined timeframe

Entered value date is not correct.

EA178 RTP was rejected by authorizer Request to Pay was rejected by counterparty.

EA18 Amount has invalid format The message has an invalid format of payment amount.

EA183 Participant does not support RTP Debtor or Creditor participant specified in pain.001 does not support RTP.

EA184 Confirmation is not required Authorization is not required for this document type.

EA23 Another period is still active On attempt to change the period of the business day, previous period is still active.

EA25 Invalid business day period There is a intention to activate a period that is not registered in the system, or period is not current (active), or period is not the following one in the business day schedule.

EA27 Cache should be updated Error in cached data.

EA30 BIC is unknown or invalid The message received by the system contains an unknown or invalid BIC in a field of the text block.

EA31 Wrong board operation System error.

EA32 Wrong data in field Incoming message contains wrong data in field.

EA33 Wrong user code User code in message is not registered.

105

EA34 Undefined error code System error.

EA35 Participant has more than one account An account cannot be identified by BIC.

EA36 Wrong certificate The 4th block of the SWIFT message or the whole message was signed by a wrong abonent.

EA37 Wrong message sender Message sender is incorrect or not registered in the system.

EA38 Wrong session id for user substitution Session Id value must be different from 0001 when connecting to the system as service bureau user.

EA39 Query is rejected by external system The external system (e.g. file adapter) rejected a query.

EA40 Wrong priority The wrong priority value was assigned to the transfer.

EA42 Related message was rejected or not found

Related message was rejected or not found.

EA43 Wrong password Wrong password is specified while attempting to change password.

EA44 Decryption error There is an attempt to change password, but the new password is wrong encrypted.

EA47 User is not connected The user's status is not active.

EA5 Message is duplicated The system receives a message having the same session number and serial number as an already existing message, though text block differs; or having the same text block, though session number and serial number differ.

EA51 Wrong document step Internal system error.

EA52 Query has been rejected A query or document was rejected.

EA6 Reference document is not found An instruction referenced by the message sent to the system has not been found.

EA60 Failed to activate period 1. There is an attempt to activate a period of the business day, but previous period is still active. 2. During execution of actions assigned to the period an error occured.

EA62 User can not use private network The participant has no authority to use private network.

EA64 Adapter can not be used as service bureau

Message is sent under user different from the one that logged on to the system. In users configuration user that prepared the message has connection group Private network, not service bureau, dissallowing successful processing of the message via service bureau.

EA65 Wrong service bureau Entered service bureau value is not correct.

EA7 Message has incompatible type with reference instruction

The message sent to the system references an instruction, which type is inconsistent with the types that may be referenced by the given variety of incoming message.

EA70 Wrong username or password Entered username or password value is not correct.

EA74 Participant can not authorize document The participant has no authority to authorize document.

EA89 Wrong currency Entered currency value is not correct.

106

EA9 Message subtype is unknown Unknown message subtype of 998 type.

EA93 The document is already processed Attempt to change document status repeatedly.

EA95 This operation is not allowed Participant has no authority to perform the operation.

EA97 Invalid system parameter Entered system parameter value is invalid.

EI1 Broadcast error Internal system error.

EL10 Wrong template string for account code Wrong template for calculation of accounts involved in any accounting entry.

EL100 More than one default subaccount exists More than one subaccount with attribute "default" exists.

EL105 Instruction rejected due to errors in batch

Internal system error.

EL11 Wrong template string for amount Wrong template for calculation of entry amounts.

EL11111 Fraud Detection: Error Fraud activity was noticed.

EL12 Wrong template string for currency code Wrong template for calculation of currencies involved in any accounting entry.

EL13 Package has another route step On invocation of the transaction generation function, the referenced status code of instruction package is inconsistent with the actual package status code.

EL148 Payment amount is greater than maximum allowed

The entered payment amount value was greater than maximum allowed.

EL149 Payment amount is less than minimum allowed

The entered payment amount value was less than minimum allowed.

EL15 Invalid type for outgoing message On invocation of the outgoing message generation function, an unknown outgoing message type is requested.

EL155 Wrong rejection motive Entered rejection motive value is not correct.

EL17 Invalid Error code Error code is not registered in the system errors.

EL18 Too many rows in error description Error description contains too many rows.

EL19 Total sum not equal to the sum for debited accounts

In an instruction received by the system, internal instruction amounts fail to add up to its gross total.

EL190 IBAN has invalid length Entered IBAN value has invalid length.

EL191 IBAN has invalid country code IBAN checksum can consist only from digits.

EL192 IBAN only digits are allowed in checksum IBAN checksum can consist only from digits.

EL193 IBAN has invalid symbol Entered IBAN value has invalid symbol.

EL194 IBAN has invalid checksum Entered IBAN value is in exclusion list.

EL195 IBAN has invalid country code (IBAN+ validation)

Entered IBAN value has invalid country code.

107

EL196 IBAN has invalid total length (IBAN+ validation)

Entered IBAN value has invalid total length.

EL197 IBAN is in exclusion list (IBAN+ validation) Entered IBAN value is in exclusion list.

EL200 NRT - Invalid action Internal system error.

EL201 Document was rejected by counterparty Document was rejected by counterparty.

EL202 Document was rejected by timeout Document was rejected by Central System due to timeout.

EL21 Invalid data in source message Internal system error.

EL210 Business signature is invalid The signature check routine rejects the signature as invalid.

EL22 Error in entry template The accounting entry template is wrong.

EL24 Invalid reference to incoming message Internal system error.

EL25 Invalid field in incoming message One of the fields in the incoming message is invalid.

EL26 Invalid value of message user priority The incoming message contains an invalid value in the user priority field.

EL27 Invalid data in incoming message The incoming message contains invalid data.

EL271 Referenced payment initiation request was not found

Request to Pay referenced in payment was not found in the system.

EL272 Referenced pain.001 rejected by timeout Referenced Request to pay was already rejected by timeout.

EL273 Referenced payment request is cancelled Referenced Request to pay in payment was already cancelled.

EL274 Referenced payment request has invalid type

Payment and Request to pay are related to different services (DNS/NRT).

EL275 Referenced payment request is already used

Referenced Request to pay was already used.

EL276 Referenced payment request has invalid status

Referenced Request to pay already has linked payment.

EL277 Referenced pain.001 does not match with payment data

Payment data in Request to pay differs from data in payment.

EL28 Account is not open The incoming message uses an account not yet opened.

EL280 Return is not allowed for this instrument code

Payment return is not allowed for this instrument code.

EL281 Return period expired Payment return was rejected because exceeded maximum return period allowed.

EL282 Payment was refused Payment was refused by counterparty.

EL283 Payment was cancelled Payment was cancelled by sender.

EL284 Instruction is already authorized An attempt to change status repeatedly, the instruction status is already authorized.

EL285 Wrong MCC Entered MCC value is not correct.

108

EL29 Invalid Account close date The incoming message uses an already closed account.

EL3 Invalid type of message Invalid type of message.

EL35 Payment is wrong formatted The format of the payment in the message is wrong.

EL39 Payment is not found Wrong payment reference.

EL4 Accounts have different currencies Debit and credit accounts referenced by the payment instruction are expressed in different currencies.

EL40 Instruction not found Wrong instruction reference.

EL41 Instruction already rejected An attempt to reject an already rejected instruction.

EL42 Number of instructions is wrong The number of the instructions specified for the batch is not equal to the number of instructions in the batch.

EL45 Instruction amount is greater than maximum allowed

The incoming message contains instruction which amount is greater than the maximum value allowed for the participant.

EL46 Instruction amount is less than minimum allowed

The incoming message contains an instruction which amount is less than the minimum value allowed for the participant.

EL47 Batch amount is greater than maximum allowed

The incoming message contains payment which amount is greater than the maximum value allowed for the participant.

EL48 Batch amount is less than minimum allowed

The incoming message contains payment which amount is less than the minimum value allowed for the participant.

EL5 Wrong number of instructions in package Wrong number of instructions is in the package.

EL51 Account is invalid The message sent to the system contains an invalid account.

EL52 BIC is invalid The message sent to the system contains an invalid BIC.

EL53 Account should be specified Account should be specified for the participant having more than one account in a bank.

EL54 Transaction reference is duplicated The instruction sent to the system contains duplicated transaction reference.

EL56 All instructions are rejected All instructions inside batch were rejected.

EL6 Some instructions already belong to other packages

On attempt to assemble an instruction package, one or more instructions are found to belong to other packages.

EL64 Invalid MIR for OUTPUT Message Entered MIR for output message value is invalid.

EL65 Invalid field option for BIC Entered field option for BIC is invalid.

EL66 Participant cannot send query on document

The participant has no authority to send query on document.

EL69 Instruction cancelled Instruction status has changed.

EL70 Instruction Rejected The instruction status was changed to "Rejected".

109

EL81 Wrong operation code Entered operation code value is not correct.

EL83 Account is locked for clearing Selected account was locked for reconciliation.

EL9 Instructions have different value dates On attempt to assemble an instruction package, the package instructions are found to have different value dates.

EL99 Clearing transaction was not settled Clearing (netto) transaction was not settled in external system or response was not received.

EP101 Unknown message type The message received belongs to no known message type.

EP103 Too few parameters Too few parameters are used while invoking system functions.

EP106 Invalid value An invalid parameter value is used while invoking system functions.

EP107 Invalid direction An invalid direction value is used while invoking system functions.

EP108 Invalid user identifier Am invalid user identifier is used while invoking system functions.

EP109 Invalid participant identifier An invalid identifier of participant is used while invoking system functions.

EP110 Invalid message identifier An invalid message identifier is used while invoking system functions.

EP111 Invalid transaction identifier An invalid transaction identifier is used while invoking system functions.

EP112 Invalid package identifier An invalid package identifier is used while invoking system functions.

EP113 Invalid account An invalid account identifier is used while invoking system functions.

EP114 Invalid currency code An invalid currency code is used while invoking system functions.

EP115 Invalid status of participant An invalid status of participant is used while invoking system functions.

EP116 Invalid operation An invalid operation code is used while invoking system functions.

EP117 Invalid type of limit An invalid limit type is used while invoking system functions.

EP118 Invalid type of overdraft An invalid overdraft type is used while invoking system functions.

EP119 Invalid expression Internal system error.

EP120 Invalid business day An invalid business day date is used while invoking system functions.

EP121 Invalid transaction status Invalid transaction status is used while invoking system functions.

EP122 Invalid value date An invalid value date is used while invoking system.

EP123 Invalid step An invalid value of instruction execution step is used while invoking system functions.

EP124 Invalid date An invalid date is used while invoking system functions.

110

EP125 Instruction is not included in the package Internal system error.

EP126 Business day already opened A request is made to open the business day while it has already opened. The business day may only be opened once; if attempts are made to open it again, the system would return the above error.

EP127 User is suspended The user sending the query to the system is suspended from the system.

EP128 User in default The user sending the query to the system is in default.

EP129 Participant is suspended The participant sending the message to the system is in suspended status.

EP130 Participant is inactive The participant sending the message to the system is in inactive status.

EP131 Could not change user status (less) The value of user status field cannot be changed downwards. It means the current value in the status field is lower than the user's requested value.

EP132 Could not change user status (more) The value of user status field cannot be changed upwards. It means the current value in the status field is higher than the user's requested value.

EP133 Could not change participant status (less) The value of participant status field cannot be changed downwards. It means the current value in the status field is lower than the user's requested value.

EP134 Could not change participant status (more)

The value of participant status field cannot be changed upwards. It means the current value in the status field is higher than the user's requested value.

EP135 Debit already locked An attempt to lock debit in an account already locked.

EP136 Credit already locked An attempt to lock credit in an account already locked.

EP137 Debit already unlocked An attempt to unlock debit in an account that is not locked.

EP138 Credit already unlocked An attempt to unlock credit in an account that is not locked.

EP139 Account limit already exists An attempt to set up limit facility for an account already having such limit facility.

EP140 Account limit does not exist An attempt to delete the limit of an account that has no limit facility.

EP141 Could not change account limit (less) The limit of any account cannot be changed downwards. It means the current limit is lower than the user's requested value.

EP142 Could not change account limit (more) The limit of any account cannot be changed upwards. It means the current limit is higher than the user's requested value.

EP143 Overdraft limit is not set for account An attempt to set an overly high limit for an account.

EP144 Account overdraft already exists An attempt to set up an overdraft facility for an account already having such overdraft facility.

EP145 Account overdraft does not exist An attempt to delete the overdraft limit of an account that has no overdraft facility.

EP146 Could not change overdraft (less) The overdraft limit of any account cannot be changed downwards. It means the current overdraft limit is lower than the user's requested value.

111

EP147 Could not change overdraft (more) The overdraft limit of any account cannot be changed upwards. It means the current overdraft limit is higher than the user's requested value.

EP148 New overdraft value is less than used Overdraft/debit cap cannot be set less than amount already used from it.

EP149 Could not change overdraft limit (less) The overdraft limit of any account cannot be changed downwards. It means the current overdraft limit is lower than the user's requested value.

EP150 Could not change overdraft limit (more) The overdraft limit of any account cannot be changed upwards. It means the current overdraft limit is higher than the user's requested value.

EP151 Overdraft limit too big An attempt to set an overly high overdraft limit for an account.

EP152 Could not change participant overdraft limit (less)

The overdraft limit of the settlement system participant cannot be changed downwards. It means the current overdraft limit is lower than the user's requested value.

EP153 Could not change participant overdraft limit (more)

The overdraft limit of the settlement system participant cannot be changed upwards. It means the current overdraft limit is higher than the user's requested value.

EP154 Participant overdraft limit too big An attempt to set an overly high overdraft limit for a settlement system participant.

EP158 Account is locked for debit An attempt to execute a transaction involving a debit-locked account.

EP159 Account is locked for credit An attempt to execute a transaction involving a credit-locked account.

EP163 Soft check failed The account is found to contain insufficient funds with due regard to any queuing instructions that would credit the account if processed successfully.

EP164 Too many instructions in the package An attempt to reject an instruction from a package containing some more instructions; as a result, the transaction fails.

EP165 Operation could not be completed. Payment has been settled.

Operation cannot be processed due to payment to status "rejected".

EP166 Operation could not be completed. Payment has been rejected.

Operation cannot be processed due to payment status "rejected".

EP168 Package is not splitable Attempt to split package. Operation is forbidden as package is not splitable.

EP169 Invalid status Entered status value is invalid.

EP170 Invalid query id An invalid query ID is used while invoking the system functions.

EP171 Wrong query status An invalid query status is used while invoking the system functions.

EP172 Participant is not suspended An attempt to unsuspend a settlement system participant who has not been suspended.

EP173 Participant is not defaulted An attempt to change the status of a settlement system participant to 'not default' while its original status is other than 'default'.

EP174 Invalid password On logging on to the system, the user has entered a wrong username/password combination.

EP175 Duplicated confirmation An attempt to confirm already confirmed instruction.

112

EP176 Reject confirmation An attempt for confirmation is rejected.

EP177 Instruction is not rejected An instruction that must have been rejected has not been rejected for some reason.

EP178 Enforced cancellation Internal system alert.

EP179 Return for original payment is already registered

On changing the balance at the start of a business day, some flows attributed to such day are found in the account.

EP180 Invalid previous business day closing balance

On changing the balance, the balance so computed fails to match the previous business day's ending balance.

EP181 Invalid date of previous business day On performing some action, the date of previous business day is found invalid.

EP182 Invalid amount On changing any value, a non-numerical value is specified instead of a number.

EP183 Lack of funds The transfer was sent to the system, but was queued due to lack of funds on account.

EP186 Board already created An attempt to create a message board with a duplicated name.

EP187 Board not found An attempt to refer to the message board, which was not created.

EP189 User has already open session The user tries to open one more session or tries to open a session immediately after the previous session was failed.

EP190 Invalid account activity Invalid account activity was detected.

EP191 Invalid priority Wrong priority or unavailable for the given current user.

EP192 User cannot connect User is locked because he or she has not changed his/her password on account of its expiration.

EP193 Password is duplicated There is an attempt to change the password, but the user has specified the existing password or one of the previous passwords as new one.

EP197 Participant does not have settlement account

Participant dos not have settlement account.

EP2 Payment was rejected An attempt to do something with already rejected payment.

EP203 Participant has more than one settlement account

Participant has more than one settlement account.

EP204 Participant does not have CLIA account Participant does not have settlement account.

EP205 Settlement account does not exist Settlement account does not exist.

EP206 Message is corrupted Message cannot be processed.

EP208 Integrity error. Accounts and Participants mismatch or accounts currency mismatch

Accounts and Participants mismatch or accounts currency mismatch.

EP21 Active operday not found Active operday not found.

EP211 Password is not allowed to be changed at this time

Password is not allowed to be changed at this time.

113

EP212 Password is too short Password does not match password policy.

EP213 Password is not strong enough Password does not match password policy.

EP215 Password contains disallowed characters Password does not match password policy.

EP216 Password starts from disallowed character

Password does not match password policy.

EP218 User has been locked due to long idle period

User has been locked due to long idle period according to security policy.

EP225 NRT rejected by restart/recovery NRT payment was rejected after system restart.

EP235 Number of instructions in batch has exceeded the maximum allowed for this instrument type

Number of instructions in batch has exceeded the maximum allowed for this instrument type.

EP252 Query rejected by timeout Query rejected by timeout.

EP258 Requested period range is too big Requested time interval in query exceeded maximum allowed by configuration in the system.

EP330 Invalid workplace Entered workplace is invalid for user.

EP331 System parameter is absent or incorrectly defined

Internal error or wrong value was specified in system parameter.

EP332 The exchange rate for this pair of currencies has invalid number of decimals

The exchange rate for entered pair of currencies has invalid number of decimals.

EP333 Calculated amount is too big and violates swift rules

Calculated amount is too big and violates swift rules.

EP334 Unable to change the priority with Queue allowed to Non-queue and vice-versa

The participant is not authorized to change the priority with Queue allowed to Non-queue and vice-versa.

EP356 Invalid participant code Entered participant code value is invalid.

EP357 Invalid currency code Entered currency code value is invalid.

EP401 Positive AML check Positive AML check.

EP402 Wrong participant tax number Entered participant tax number value is not correct.

EP403 Wrong participant alternative code Entered participant alternative code value is not correct.

EP404 Wrong participant settlement account Entered participant settlement account value is not correct.

EP405 Wrong participant settlement agent Entered participant settlement agent value is not correct.

EP406 Instructing Agent is invalid Entered instructing agent value is invalid.

EP407 Debtor name is empty Mandatory field is empty.

EP408 Creditor name is empty Mandatory field is empty.

EP409 Position must be 0 Intention to lock/unlock an account having non-zero position.

114

EP69 Instruction cancelled Instruction cancelled.

ER1 Access rights are not assigned This error is returned each time when an attempt is made to perform any action without proper access rights.

ER10 Participant cannot lock account The participant has no authority to lock the account.

ER11 Participant cannot unlock account The participant has no authority to unlock the account.

ER12 Wrong priority value The participant has no authority to change payment documents' priority.

ER13 Participant cannot cancel instruction The participant has no authority to cancel a payment instruction.

ER15 Participant cannot set overdraft limit for account

The participant has no authority to set an overdraft limit for the account.

ER18 Participant cannot set limit for account The participant has no authority to set an account limit.

ER2 Access rights are not assigned(set ROLE ONLY)

The user has no authority to access the system.

ER20 Participant {0} cannot debit account of {1}

The participant has no authority to debit the account.

ER21 Participant cannot credit account The participant has no authority to credit the account.

ER22 Participant cannot change priority of instruction with this type

The participant has no authority to change priority of the given document type.

ER23 Participant cannot lock participant The participant has no authority to lock another participant.

ER24 Participant cannot lock user The participant has no authority to lock a given user.

ER28 Participant cannot get account report on specified account

The participant has no authority to obtain reports on a specified account.

ER29 Participant cannot change business day period

The participant has no authority to change business day period.

ER30 User cannot send message The user has no authority to send any message on business days of certain type.

ER31 User cannot substitute other user The user has no authority to send any message on other user's behalf.

ER32 User can not change Business Day Period The user has no access right to change the current Business Day Period.

ER33 User cannot resolve gridlock The user is not authorized to resolve gridlock.

ER34 User cannot perform archiving User has no authority to perform archiving.

ER35 User cannot approve right changes The user is not authorized to approve right changes.

ER36 User can not create Request to Change Access Rights

The user has no access right to create request to change access rights.

ER40 Cannot send message at that business day period

An attempt to send a message at such period of a business day when messages of that type may not be sent.

ER41 Settlement is not allowed for the participant in this period

Settlement is not allowed for authorization by the participant in this period.

115

ER50 Account cannot accept document with priority specified at this business day period

There was an attempt to send a document, which priority is wrong or not specified at this business day period for the given user.

ER60 Participant cannot get report on specified participant

The participant has no access right to get Participant Report on specified participant.

ER61 Participant cannot settle payments by type

The participant has no authority to settle payments by type.

ER62 Participant cannot settle payments by priorities

The participant has no authority to settle payments by priorities.

ER63 Participant cannot accept payments by type

The participant has no access right to accept payment messages of the defined type.

ER68 No rights to authorize payment The participant has no authority to authorize payment.

ER7 Participant cannot send message in current period

The participant is not authorized to send the given message on a given type of business day.

ER70 Participant has no rights to send payment with this priority

The participant has no rights to send payment with this priority.

ER75 Participant cannot receive specified document

The participant has no authority to receive specified document.

ER76 Accept Payment by Instrument code Participant has no rights to send document with specified instrument code.

ER78 Set Debit Cap limit for accounts Debit cap limit is not set.

SA1 Service is not available This error message appears in case the RTS/X server is not accessible.

SA10 Message Id not found in QUERIES Internal system error.

SA11 Message type is unknown Internal system error.

SA12 Error during Close Message Internal system error.

SA13 Transaction has invalid status Internal system error.

SA14 Transaction is not found Internal system error.

SA15 Message signature check failed Signature of incoming message is invalid.

SA16 Text block signature check failed Text block signature check shows that the signature is incorrect.

SA17 Message is rejected by external system Message is rejected by client software.

SA2 Status not equal X Internal system error.

SA27 No data found in cache Internal system error.

SA3 Instruction with Route Step eq P and PackId not found


SA4 Instruction with Status eq R and TransId not found


SA41 Wrong data in reply System error.

116

SA5 Unknown Status Internal system error.

SA55 Wrong or undefined account with type code


SA56 Wrong or undefined user with type code Internal system error.

SA57 Period action finished unsuccessfully Internal system error.

SA6 Instruction with Status eq E and TransId not found


SA69 Token cancelled Internal system error.

SA7 Instruction with Status eq F and TransId not found


SA73 Direct participant is undefined Entered direct participant value cannot be found in system's directory.

SA8 Check Replies status is unknown Internal system error.

SA9 Unknown Route Step Internal system error.

SC301 Cannot start Session Internal system error.

SC302 Cannot get number of devices Internal system error.

SC303 Cannot check device Internal system error.

SC304 Cannot open device Internal system error.

SC305 Cannot get abonent ID Internal system error.

SC306 Path to sign not exists Sign path setting is not set.

SC307 Error in access to array Internal system error.

SC308 Error in unaccess array Internal system error.

SC309 Cannot allocate memory Internal system error.

SC310 Cannot sign Internal system error.

SC311 Path with signature not exists Path with signature setting is not set.

SC312 Signature check fail Internal system error.

SI1 Broadcast critical error Internal system error.

SL1 Invalid sequence number A message the system has received from its user contains a sequence number that differs from the expected value.

SL2 Invalid duplication flag An incoming message contains a duplication flag, while its service fields coincide with a message already stored in the database. Though such messages have identical fields,

117

such as session number and serial number, their text block content differs.

SL20 Message was not accepted Due to errors message cannot be sent. Check the logs.

SP100 Incoming message contains invalid character(s)

The incoming message contains unallowable character(s).

SP102 Field not found Internal system error.

SP104 Inconsistent data Internal system error.

SS1 Operation cannot be completed. Database error


WL11111 Fraud Detection: Warning Fraud activity was noticed.

6.6 Annex F – Transaction Purpose Code

Transaction Codes

Description ISO20022 Sender Priority No. (Range)

1 AUTDLP Peso Automatic Debit Loan Payment pacs.009 BSP GL 10 2 BEGBAL Account Beginning Balance pacs.009 BSP GL 1 3 BIR101 BIR Tax Collections pacs.009 BANK 16-98 4 BIR108 BIR Creditable Withholding Tax pacs.009 BANK 16-98 5 BIR109 BIR Own Tax Liabilities pacs.009 BANK 16-98 6 BLSPAY Bills payment to non-government pacs.008 BANK 11-15 7 BNTATM ATM Settlement pacs.009 BANCNET-

ATM 11

8 BOC072 PAS Advance Import Duties pacs.009 BANK 16-98 9 BOC073 PAS Final Payment - Import Duties pacs.009 BANK 16-98

10 BOC074 PAS Import Processing Fees pacs.009 BANK 16-98 11 BOC075 Non PAS Advance Import Duties pacs.009 BANK 16-98 12 BOC076 Non PAS Final Payment - Import

Duties pacs.009 BANK 16-98

13 BOC077 Non PAS Import Processing Fees pacs.009 BANK 16-98 14 BOC078 Export Documentary Stamp Fees pacs.009 BANK 16-98 15 CASHDP Cash Deposit pacs.009 BSP ICMS-

CD 98

16 CASHRC Cash Receipts pacs.009 BSP ICMS-CD

98

17 CORPYB Corporate payment to business pacs.008 BANK 16-98 18 CORPYG Corporate payment to government pacs.008 BANK 16-98 19 CORPYP Corporate payment to person pacs.008 BANK 16-98 20 CSGASF BSP Supervisory Collection of Annual

Fees pacs.010 BSP ASOFS-

FSS 10

21 CSGPEN BSP Supervisory Collection of Penalties

pacs.010 BSP ASOFS-FSS

10

22 CURRET Currency Retirement pacs.009 BSP ICMS-CD

98

23 EMLAVL Peso Emergency Loan Availment pacs.009 BSP CFAS 10 24 FEENND Service Fee for New Note Deposit pacs.010 BSP ICMS-

CD 98

118

25 FEEWID Service Fee for Cash Withdrawal pacs.010 BSP ICMS-CD

98

26 FTAMLC Fund Transfer to AMLC Account pacs.009 BANK 16-98 27 FTDAVL FTD Availment pacs.009 BANK 16-98 28 FTDMAT FTD Maturity pacs.009 BSP DOS 10 29 FTDPEN FTD Penalty pacs.009 BSP DOS 10 30 FTDPRE FTD Pre-termination Availment pacs.009 BSP DOS 10 31 FXDEPO FX Deposit pacs.009 BSP ICMS-

CD 98

32 G4PBSP Government Securities BSP Purchase Treasury Bills

pacs.009 BSP DOS 10

33 G4PTRS Government Securities Trust Purchase Treasury Bills

pacs.009 BSP DOS 10

34 G4SBSP Government Securities BSP Sale Treasury Bills

pacs.010 BSP DOS 10

35 G4STRS Government Securities Trust Sale Treasury Bills

pacs.010 BSP DOS 10

36 G6PBSP Government Securities BSP Purchase Treasury Bonds

pacs.009 BSP DOS 10

37 G6PTRS Government Securities Trust Purchase Treasury Bonds

pacs.009 BSP DOS 10

38 G6SBSP Government Securities BSP Sale Treasury Bonds

pacs.010 BSP DOS 10

39 G6STRS Government Securities Trust Sale Treasury Bonds

pacs.010 BSP DOS 10

40 GMACLR Settlement of GMA Check Clearing Results

pacs.009 PCHC-CICS 11

41 GOVD2B Government Disbursement to business

pacs.008 BTR 10

42 GOVD2G Government Disbursement to other government agencies

pacs.008 BTR 10

43 GOVD2P Government Disbursement to person pacs.008 BTR 10 44 GSOTCI GS OTC Issuance, Bloomberg Trading pacs.009 BTR-NROSS 19 45 GSPAUC GS Primary Auction Issuance, Re-

opening pacs.010 BTR-NROSS 10

46 GSPTAP GS Primary Treasury Bills Roll-over pacs.009 BTR-NROSS 10 47 GSREDC GS Redemption, Coupon pacs.009 BTR-NROSS 10 48 BSPOTC BSP Securities Secondary Market

Trade pacs.009 BTR-NROSS 10

49 BSPERD BSP Securities Early Redemption pacs.009 BTR-NROSS 10 50 BSPMAT BSP Securities Maturity pacs.009 BTR-NROSS 10 51 BSPCPN BSP Securities Coupon Payment pacs.009 BTR-NROSS 10 52 BSPAUC BSP Securities Auction pacs.010 BTR-NROSS 10 53 IBCFTR Interbank Customer Fund Transfer -

Remittance pacs.008 BANK 16-98

54 IBCPAY Interbank Customer Payment pacs.008 BANK 16-98 55 IBCPYM Interbank Customer Payment to

Merchants pacs.008 BANK 16-98

56 IBFT00 Interbank Fund Transfer pacs.009 BANK 16-98 57 IBFTRM Interbank Fund Transfer - Remittance pacs.009 BANK 16-98 58 IBLPAY Interbank Loan Payment pacs.009 BANK 16-98 59 ILFAVL ILF Availment camt.050 BANK 5-11 60 ILFREP ILF Repayment camt.051 BSP MOS-ILF 5-11 61 ILFEXT Extended ILF pacs.009 BSP MOS-ILF 5-11

119

62 ILFXRP Extended ILF Repayment pacs.010 BSP MOS-ILF 5-11 63 ILFINT Extended ILF Interest pacs.010 BSP MOS-ILF 5-11 64 ILFORP ILF Outright Purchase pacs.009 BSP MOS-ILF 5-11 65 IPAYCL Settlement of InstaPay Clearing

Result pacs.009 BANCNET-

INSTAPAY 11

66 IPAYDF InstaPay SSA Defund pacs.009 BANCNET-INSTAPAY

11

67 MANDLP Peso Authority to Debit Loan Payment

pacs.009 BSP CFAS 10

68 MNYCTR Money Counter pacs.009 BSP ICMS-CD

98

69 MUTCLM Mutilated Claim pacs.009 BSP ICMS-CD

98

70 NCOBIR BIR Collection by National Collecting Officer

pacs.009 BANK 16-98

71 NCOBOC BOC Collection by National Collecting Officer

pacs.009 BANK 16-98

72 NONTAX Non-Tax Collection pacs.009 BANK 16-98 73 OCLAVL Peso Overdraft Credit Line Availment pacs.009 BSP GL 10 74 ODFAV1 ODF Availment pacs.010 BSP MOS-

ODF 10

75 ODFMT1 ODF Maturity pacs.009 BSP MOS-ODF

10

76 ODFPN1 ODF Penalty pacs.009 BSP MOS-ODF

10

77 OLFAV1 OLF Availment pacs.009 BSP MOS-OLF

10

78 OLFMT1 OLF Maturity pacs.010 BSP MOS-OLF

10

79 OLFPN1 OLF Penalty pacs.010 BSP MOS-OLF

10

80 OWNACC Own Account Transfer camt.050 BANK 16-98 81 PAYGOV Other payments to government pacs.008 BANK 16-98 82 PAYRLL Salary payment pacs.008 BANK 16-98 83 PEANTY Annuity pacs.009 BANK 16-98 84 PEBIPR Bank-Issued PERA Products pacs.009 BANK 16-98 85 PECASA Cash Custodian Fund pacs.009 BANK 16-98 86 PEDVP3 Settlement of GS Tertiary Market

Trades pacs.009 PDS-EDVP 21

87 PEGOVS Government Securities pacs.009 BANK 16-98 88 PEINPP Insurance Pension Product pacs.009 BANK 16-98 89 PEMUTF Mutual Fund pacs.009 BANK 16-98 90 PEPREP Pre-need Pension Plan pacs.009 BANK 16-98 91 PESTCK Stock or Other Security Listed and

Traded in Local Exchange pacs.009 BANK 16-98

92 PESODF PESONet SSA Defund pacs.009 PCHC-PESONET

93 PEUITF Unit Investement Trust Fund pacs.009 BANK 16-98 94 PEXTRB Exchange-Traded Bond pacs.009 BANK 16-98 95 PNETCL Settlement of PesoNet Clearing

Results pacs.009 PCHC-

PESONET 11

96 PSEEQT PSE transactions involving equities pacs.009 BANK 16-98 97 PSEETF PSE transactions involving exchange

traded fund pacs.009 BANK 16-98

120

98 PVPRMB Settlement of FX Trades involving Remninbi (RMB)

pacs.009 PDS-PVP 21

99 PVPUSD Settlement of FX Trades involving US Dollar (USD)

pacs.009 PDS-PVP 21

100 REDAVL Peso Rediscounting Loan Availment pacs.009 BSP GL 10 101 RETCHK Returned Checks pacs.009 BSP ICMS-

CD 98

102 ROSBIL NRoSS Monthly Fees pacs.010 BTR-NROSS 10 103 RRPAV1 RRP Availment pacs.010 BSP MOS-

RRP 10

104 RRPMT1 RRP Maturity pacs.009 BSP MOS-RRP

10

105 RRPPN1 RRP Penalty pacs.009 BSP MOS-RRP

10

106 RRPTRM RRP Term pacs.009 BSP MOS-RRP

10

107 SSATOP SSA Top-Up camt.050 BANK 16-98 108 TDFAV1 7-Day TDF Availment pacs.010 BSP MOS-

TDF 10

109 TDFAV2 28-Day TDF Availment pacs.010 BSP MOS-TDF

10

110 TDFAV3 14-Day TDF Availment pacs.010 BSP MOS-TDF

10

111 TDFMT1 7-Day TDF Maturity pacs.009 BSP MOS-TDF

10


10


10

114 TDFPN1 7-Day TDF Penalty pacs.009 BSP MOS-TDF

10


10


10

117 TDFPR2 28-Day TDF Pre-termination Availment

pacs.009 BSP MOS-TDF

10

118 TDFPR3 14-Day TDF Pre-termination Availment

pacs.009 BSP MOS-TDF

10

119 WIDBAC Cash Withdrawal BSP Bacolod pacs.010 BSP ICMS-RO

98

120 WIDBAG Cash Withdrawal BSP Baguio pacs.010 BSP ICMS-RO

98

121 WIDBAT Cash Withdrawal BSP Batac pacs.010 BSP ICMS-RO

98

122 WIDBUT Cash Withdrawal BSP Butuan pacs.010 BSP ICMS-RO

98

123 WIDCAG Cash Withdrawal BSP Cabanatuan pacs.010 BSP ICMS-RO

98

124 WIDCDO Cash Withdrawal BSP CDO pacs.010 BSP ICMS-RO

98

125 WIDCEB Cash Withdrawal BSP Cebu pacs.010 BSP ICMS-RO

98

126 WIDCOT Cash Withdrawal BSP Cotabato pacs.010 BSP ICMS-RO

98

121

END OF DOCUMENT

127 WIDDAG Cash Withdrawal BSP Dagupan pacs.010 BSP ICMS-RO

98

128 WIDDAV Cash Withdrawal BSP Davao pacs.010 BSP ICMS-RO

98

129 WIDDUM Cash Withdrawal BSP Dumaguete pacs.010 BSP ICMS-RO

98

130 WIDFER Cash Withdrawal BSP San Fernando pacs.010 BSP ICMS-RO

98

131 WIDGEN Cash Withdrawal BSP General Santos pacs.010 BSP ICMS-RO

98

132 WIDILO Cash Withdrawal BSP Iloilo pacs.010 BSP ICMS-RO

98

133 WIDLAU Cash Withdrawal BSP La Union pacs.010 BSP ICMS-RO

98

134 WIDLEG Cash Withdrawal BSP Legaspi pacs.010 BSP ICMS-RO

98

135 WIDLUC Cash Withdrawal BSP Lucena pacs.010 BSP ICMS-RO

98

136 WIDMLA Cash Withdrawal BSP Manila pacs.009 BSP ICMS-RO

98

137 WIDNAG Cash Withdrawal BSP Naga pacs.010 BSP ICMS-RO

98

138 WIDOZA Cash Withdrawal BSP Ozamis pacs.010 BSP ICMS-RO

98

139 WIDROX Cash Withdrawal BSP Roxas pacs.010 BSP ICMS-RO

98

140 WIDTAC Cash Withdrawal BSP Tacloban pacs.010 BSP ICMS-RO

98

141 WIDTUG Cash Withdrawal BSP Tuguegarao pacs.010 BSP ICMS-RO

98

142 WIDZAM Cash Withdrawal BSP Zamboanga pacs.010 BSP ICMS-RO

98

Documents

RULEBOOK PH-ISO20022 STANDARDS ON PAYMENT MESSAGES · 1 1. Introduction This rulebook called the Philippine Rulebook on Payments and Settlements was crafted and finalized through