SOP on IPPB Data Fetch Issues and Resolution

1 Purpose

To provide guidance on the issues related to non-fetching of IPPB transaction data and the actions required to ensure successful fetching of IPPB transaction data.

2 Scope

This SOP applies to all Branch Offices (BOs), BPMs, Substitute BPMs.

3 Background and Introduction

As part of the revised IPPB data-fetch mechanism implemented from May 2026, transaction data is fetched incrementally from the last successful fetch date and time up to the current fetch date and time.

Under this logic, successful fetching of IPPB transaction data is dependent upon successful balance validation at the BO level. Any mismatch in the BO balance arising due to mismatch adjustment entries, wallet adjustments, or non-transfer of cash during BPM leave arrangements may result in failure of the data-fetch process. Consequently, IPPB transaction data that is not fetched on a particular day may not be fetched in the subsequent data-fetch cycles.

4 Problem Description

The following issues are being reported from the field:

1. BOs are raising tickets regarding non-fetching of IPPB transaction data in the application.
2. Once transaction data is not fetched on a particular day, it is generally not fetched in the subsequent data-fetch cycles as well.

5 Causes of Non-Fetching

5.1 Mismatch Entries and Wallet Adjustments

In cases where mismatch entries were made and wallet adjustments are performed for any non-fetch of IPPB data automatically due to any reason, the IPPB data will not be fetched in the subsequent data-fetch cycle due to mismatch in BO balance.

5.2 BPM Leave Arrangements

During BPM leave arrangements, if cash transfer to substitute is not performed in the system, the IPPB data will not be fetched in the subsequent data-fetch cycle due to mismatch in BO balance for the present BPM account.

---

Extracted Content – Page 5

6 Preventive Measures

The following instructions shall be followed under the new logic:

1. Cash transfers during leave arrangements must be performed to ensure matching of cash balance with cash balance report, wallet, and physical cash.
2. No mismatch adjustment entries or wallet adjustments should be carried out for IPPB transaction non-fetching on any day.

7 Resolution Procedure

In cases where mismatch entries or wallet adjustments have already been carried out:

1. Corresponding contra entries should be passed to reverse such adjustments.
2. Once the balance is restored correctly, balance validation during the data-fetch process will succeed.
3. Pending IPPB transaction data can then be fetched successfully.

After restoration of the correct balance through reversal of mismatch entries or wallet adjustments, balance validation during the data-fetch process will succeed and pending IPPB transaction data can be fetched successfully. 

Circulation of SOP on IPPB Data Fetch Issues and Resolution

Please find the attached SOP on the IPPB data fetch issues encountered by the field units, along with the corresponding resolution steps.

It is requested that the SOP may kindly be circulated to all field units for their guidance and reference, so that such issues can be addressed efficiently and resolved in a timely manner.

CEPT