Punjab National Bank Revises Monitoring of Staff Accounts: 5 High-Risk Transactions to Be Monitored Through OSS Alerts
| ➡️ Click here to Join Whatsapp News Group - Get instant updates of all Banking News |
Punjab National Bank (PNB) has revised the process of monitoring of abnormal transactions in staff accounts through Staff-Related OSS (eTHIC) scenarios.
As per the revised instructions, monitoring of abnormal transactions in staff accounts through R-Audit Reports has been discontinued with effect from 1 November 2026. Going forward, such transactions will be monitored through five staff-related OSS scenarios, all of which have been classified as High Risk.
The Bank has also revised the authority responsible for reviewing and closing these alerts. In addition, documentary evidence supporting customers’ requests will be mandatory for certain OSS scenarios, and alerts can be closed only after proper verification of the supporting documents.
Monitoring Through R-Audit Reports Discontinued
PNB has decided to discontinue the monitoring of abnormal transactions in staff accounts through R-Audit Reports and continue monitoring through OSS scenarios.
All Zonal Audit Offices (ZAOs) have been advised to complete the exercise of monitoring abnormal transactions in staff accounts through R-Audit Reports for the period up to September 2026.
They must also submit confirmation to the Transaction Monitoring Division by 10 December 2026.
Five Staff-Related OSS Scenarios Classified as High Risk
PNB has identified five staff-related OSS scenarios for monitoring abnormal transactions in staff accounts. All five scenarios have been classified as High Risk.
The details are as follows:
| Sr. No. | Scenario Name | Risk Category |
|---|---|---|
| 1 | Monitoring of cash transactions (aggregate credit in a day) of more than ₹25,000 in staff accounts. Monitoring will be based on Customer ID, covering all accounts linked to the Customer ID. | High |
| 2 | Debit from customer’s loan account/accounts and credit to staff account/accounts. | High |
| 3 | Monitoring of cash transactions (aggregate credit in a month) of ₹1,00,000 and above in staff accounts. Monitoring will be based on Customer ID, covering all linked accounts. | High |
| 4 | Monitoring of transactions from staff accounts to customer loan accounts. | High |
| 5 | Monitoring of credit transactions (aggregate credit other than cash in a month) of more than ₹5,00,000 in staff accounts. Monitoring will be based on Customer ID, covering all linked accounts. | High |
These scenarios will help the Bank identify unusual cash deposits, transfers between staff and customer loan accounts, and other significant credit transactions involving staff accounts.
Revised Authority for Review and Closure of Staff-Related OSS Alerts
PNB has also revised the authority responsible for reviewing and closing alerts generated under the five staff-related OSS scenarios.
Previously, the closure authority was assigned to officials in Scale IV and above at ZOs, ZAOs, Head Office Divisions and other administrative offices.
Under the revised arrangement, the closure authority will be determined according to the office where the concerned staff member is posted or where the alert is triggered.
The revised responsibilities are as follows:
| Sr. No. | Office Where Staff Is Posted / Alert Is Triggered | Authority for Closure |
|---|---|---|
| 1 | GBBs | HRD Official of Scale IV and above at ZOs |
| 2 | LCB/ELCB/VLCB | HRD Official of Scale IV and above at ZOs |
| 3 | ZOs | HRD/Establishment Official of Scale IV and above at ZAOs |
| 4 | ZAOs | HRD/Establishment Official of Scale IV and above at ZAOs |
| 5 | HO Divisions | HRD/Establishment Official of Scale IV and above at HO Divisions |
Mandatory Uploading of Documentary Proof in OSS (eTHIC) Module
PNB has made uploading documentary evidence mandatory for certain OSS scenarios.
The decision follows recent incidents of employee-induced fraud. In its meeting held on 31 October 2026, the Bank’s Top Management directed that documentary evidence supporting the customer’s request must invariably be obtained and uploaded into the system.
As per the revised instructions, OSS alerts must be closed only after the competent closure authority has thoroughly verified the supporting documents.
Therefore, while closing such alerts, the concerned officials must ensure that all relevant documents are uploaded in the OSS (eTHIC) module.
List of OSS Scenarios Requiring Mandatory Documentary Proof
PNB has identified the following six OSS scenarios in which uploading documentary evidence is compulsory.
| Sr. No. | Scenario Name | Risk Category |
|---|---|---|
| 1 | Monitoring of transactions in inoperative accounts made operative. | High |
| 2 | Monitoring of mobile alerts that have been disabled. | Medium |
| 3 | Movement of deposit accounts of Government Organisations/Government Code. | Medium |
| 4 | Debit Remote SOL Transfer transactions in deposit accounts. | High |
| 5 | Debit Inter-SOL Transfer transactions in deposit accounts. | Medium |
| 6 | Debit from customer’s loan account/accounts and credit to staff account/accounts. | High |
For all the above scenarios, the concerned officials must obtain documentary evidence supporting the customer’s request and upload it into the system.
The competent closure authority must verify the documents before closing the alert. Simply reviewing the transaction will not be sufficient for closure.
Please login to comment