PESONet MC 20-039

December 21, 2020


TO : All PESONet Participating Banks/Institutions


RE : IMPLEMENTATION OF THE ENHANCED INTERFACE FILE (EIF) FORMAT FOR PESONet


1. We wish to issue our final reminder that effective February 01, 2021, PESONet will only accept transactions that follow one standard ISO20022 format whether sent via the Enhanced Interface File (EIF) upload, via API or via the web-based front-end application provided by PCHC.


2. It may be recalled that we have issued a similar reminder on October 29, 2020 after members of the PESONet ACH Steering Committee agreed to grant a non-extendable cutover date for the adoption of one standard format in PESONet.


3. The implementation on the said date would mean that conventional file formats used in the PESONet Front-End Application will no longer be accepted for processing, to wit:


a. EPCS Outward File Format

b. PhilPass Remit Outward File Format

c. PESONet Status Update File (non-EIF)


4. Additionally, PCHC shall no longer generate the inward counterparts of the above-mentioned files, to wit:

a. EPCS Inward File Format

b. PESONet Status Interface File (non-EIF)

c. PESONet Status Update File (non-EIF)


5. PESONet participants are enjoined to ensure that a minimum, have implemented the PESONet Enhanced Interface File Format on the said date.


6. Participants that are PESONet Web Service API are also reminded that inherent in an API, is a shared responsibility. Therefore, participants should implement the PESONet Enhanced Interface File format as part of their exception handling and to adopt as an integral component of a BCP scenario. Everyone is expected to handle exception situations such as but not limited to:


a. Exception Handling in the Event of Time-out - as the PESONet Web Service API is delivered over the internet,

communication issues do occur, and participants are expected to handle such exceptions accordingly.


b. Exception Handling in the Event of Non-Acceptance - in the event of issues with acceptance of transactions,

participants are expected to be able to transmit and receive PESONet transactions, as appropriate using the

PESONet Enhanced Interface File via PESONet Front-End Application,


c. Exception Handling in the Event of Non-Availability - participants are expected to be able to continue to process

both their inward and outward transactions via the PESONet Front-End Application using the PESONet Enhanced

Interface File in the event, that for any reason, that the PESONet Web Service API is unavailable.


7. Participants implementing the PESONet Web Service API are also reminded that participants bear the ultimate responsibility for transactions they transmit to PCHC for processing which means that participants must ensure that they perform the necessary validation and integrity checks on transactions prior to sending.


8. Likewise for participants that have already implemented the PESONet Web Service API but are not yet using the PESONet Enhanced Interface File, we strongly encourage to do the same henceforth to prevent any operational issues.


9. We trust for your full cooperation.


PESONet MC.20-039
.Implementation of the
Download IMPLEMENTATION OF THE • 545KB