[OR] [DBP] [E3] [CBS] [1] [ITo] Establish Impact Tolerances

CBS-1 Deposit & Account Services

Introduction

For CBS-1 Deposit and Account Services, impact tolerance should define the maximum level of disruption DBP can withstand before the disruption causes intolerable harm to customers, the bank, or the wider financial system.

BCM Institute describes impact tolerance as the maximum tolerable level of disruption to a critical business service, and recommends setting tolerances across impact types such as downtime, data loss, customer impact, and regulatory impact.
This is especially relevant for DBP because its deposit services are delivered through branch-based deposit products, ATM services, and online banking channels, including DBP EC Banking and the DBP Digital Banking Portal.

BSP Circular No. 1203 requires BSFIs to identify critical operations, set a tolerance for disruption for each identified critical operation, consider, at a minimum, a time-based metric, and also consider other metrics such as the number of customers affected and the volume and value of transactions affected. The Circular further says those tolerances should be tested against severe but plausible scenarios and reviewed by the board.

Purpose of the Chapter

This chapter provides a proposed management baseline for setting impact tolerances for each Sub-CBS under CBS-1 Deposit and Account Services. It is intended to support DBP’s operational resilience planning, board review, scenario testing, and remediation prioritisation. The tolerances below are therefore illustrative and should be validated by DBP management, risk owners, operations, technology, compliance, and business continuity teams against actual architecture, process controls, recovery capability, transaction volumes, and customer/regulatory obligations.

Table P4: Establish Impact Tolerance for CBS-1

Sub-CBS Code	Sub-CBS	Maximum Tolerable Downtime (MTD)	Maximum Tolerable Data Loss (MTDL)	Customer Impact	Regulatory Impact	Impact Type	Current Resilience Status	Action Required
1.1	Customer Onboarding and Account Application	1 business day	Up to 4 hours of recoverable application data	Moderate: delayed onboarding, branch queues, abandoned applications	Moderate: service delays, potential consumer fairness issues if prolonged	Service delay / reputational/operational	Proposed baseline – validate	Enable manual fallback forms, queue prioritisation, and digital-to-branch fallback
1.2	Customer Identification and Verification (KYC/CDD)	4 hours	Zero for approved KYC records; up to 1 hour for unverified intake data	High: inability to open accounts lawfully	High: AML/CFT and customer due diligence breach risk	Compliance / legal/operational	Proposed baseline – validate	Strengthen document imaging, sanctions/watchlist redundancy, and maker-checker fallback
1.3	Account Approval and Opening	4 hours	Near-zero; no loss of approved account master data	High: customers unable to activate new accounts	High: account-opening control failures and audit issues	Operational / customer/compliance	Proposed baseline – validate	Implement controlled manual approval workflow and core-banking recovery priority
1.4	Initial Funding and Deposit Booking	2 hours	Near-zero; no unreconciled loss of booking records	High: funding not reflected, customer distrust	High: ledger integrity and possible financial misstatement	Financial / customer / operational	Proposed baseline – validate	Prioritise real-time posting recovery and suspense/reconciliation controls
1.5	Product Terms Setup and Account Parameter Maintenance	1 business day	Up to 1 hour, provided approved changes are reproducible	Low to Moderate: delayed product changes, fee/interest setup delays	Moderate: pricing, disclosure, and control exceptions if errors occur	Configuration/control/compliance	Proposed baseline – validate	Enforce change freeze during incidents and maintain approved parameter backups
1.6	Deposit Transactions Processing	2 hours	Near-zero; no loss of posted deposit transactions	Very High: customers unable to deposit/credit funds correctly	Very High: transaction integrity, settlement, and conduct risk	Financial / customer / systemic	Proposed baseline – validate	Tier-1 recovery priority, active-active/rapid restore, batch replay, real-time monitoring
1.7	Withdrawal and Funds Access Processing	1 hour	Near-zero	Very High: customers cannot access their own funds	Very High: consumer harm and heightened supervisory concern	Customer harm/liquidity access / reputational	Proposed baseline – validate	Prioritise branch, ATM, and alternate channel continuity; define cash contingency procedures
1.8	Account Servicing and Customer Maintenance	4 hours	Up to 1 hour for pending updates; zero for approved customer master changes	High: inability to update details, limits, mandates, and contact data	Moderate to High: Inaccurate records may affect compliance and service delivery	Customer/data integrity/compliance	Proposed baseline – validate	Provide controlled manual servicing and post-incident update verification
1.9	Interest, Fees, and Charges Processing	End of business day	Zero for final accrual/posting files; up to 1 hour for interim processing data	Moderate: inaccurate balances, fee complaints	High: customer restitution, disclosure, and conduct risk	Financial / conduct / reputational	Proposed baseline – validate	Prepare recalculation routines, billing override controls, and restitution workflow
1.10	Statement, Passbook, and Balance Reporting	1 business day	Up to 4 hours, provided the source ledger is intact	Moderate: reduced visibility, complaints, branch congestion	Moderate: reporting and disclosure delays	Information/customer / reputational	Proposed baseline – validate	Enable deferred generation, cached balances with controls, and customer advisories
1.11	Digital Account Access and Channel Integration	2 hours	Zero for authentication, transaction, and access control logs; up to 15 minutes for session data	Very High: customers unable to access accounts online	High: digital service disruption and customer protection concerns	Channel availability / cyber / customer	Proposed baseline – validate	Harden IAM, API gateway, internet banking DR, and failover communications
1.12	ATM and Card-Based Access Management	2 hours	Near-zero for card/account linkage and transaction logs	Very High: cash access and balance services impaired	High: consumer impact and network/service obligations	Cash access/channel/customer	Proposed baseline – validate	Prioritise switch/network resilience, ATM fallback limits, and card hotlist synchronisation
1.13	Account Reconciliation and Exception Handling	End of the next business day	Zero for final recon files; up to 2 hours for working files	Indirect but High if not resolved: balance disputes, delayed corrections	High: unresolved breaks may trigger reporting/control issues	Financial control / operational / compliance	Proposed baseline – validate	Increase automated recon coverage and aged-break escalation thresholds
1.14	Dormancy, Holds, Restrictions, and Account Control Administration	4 hours	Zero for restriction flags and legal holds	High: wrongful blocking or release of funds	Very High: legal, fraud, AML, and consumer protection exposure	Control integrity / legal / fraud	Proposed baseline – validate	Protect restriction tables, dual authorisation, and post-recovery control validation
1.15	Fraud Monitoring and Transaction Surveillance for Deposit Accounts	30 minutes	Zero for alerts, case notes, and watchlist updates	Very High if suspicious activity is not detected promptly	Very High: AML/fraud monitoring failure	Fraud / cyber / compliance	Proposed baseline – validate	Ensure 24/7 monitoring, alternate alert routing, and resilient case-management tools
1.16	Complaints, Disputes, and Service Recovery	1 business day	Up to 4 hours for case intake; zero for final complaint records and resolutions	Moderate to High: dissatisfaction, reputational damage	High: consumer protection and complaint-handling obligations	Customer/conduct / reputational	Proposed baseline – validate	Maintain incident complaint queue, priority triage, and root-cause/service recovery playbook
1.17	Regulatory Reporting and Compliance Monitoring	By regulatory deadline; internal outage tolerance 4 hours	Zero for submitted regulatory records; up to 1 hour for working data	Low direct customer impact, but significant indirect impact if compliance fails	Very High: breach of BSP and statutory obligations	Compliance/reporting / legal	Proposed baseline – validate	Maintain regulatory reporting calendar, backup templates, and compliance escalation triggers
1.18	Incident Response, Business Continuity, and Recovery	15 minutes to mobilise; 1 hour to activate the relevant response structure	Zero for incident logs, contact lists, and decision records	Very High if recovery is delayed across all sub-services	Very High: inability to manage disruption within tolerance	Enterprise resilience/governance / operational	Proposed baseline – validate	Maintain tested crisis playbooks, call trees, command structure, and recovery dashboards

Regulatory Requirements and Philippine Banking Examples

BSP Circular No. 1203 says identified critical operations should drive later steps, including setting tolerance for disruption and mapping interconnections and interdependencies. It also says the tolerance should include at least a time-based metric and may include other quantitative or qualitative metrics, such as affected customers and transaction values.

The Circular further requires those tolerances to be tested under severe but plausible scenarios. BSP gives examples of scenarios banks are strongly encouraged to consider, including a major earthquake such as the “Big One,” a severe typhoon, failure of a critical third-party service provider, disturbances in payment and settlement systems, and simultaneous or coordinated cyberattacks/ransomware affecting multiple banks.

For DBP, practical examples would include:

an internet banking outage affecting DBP EC Banking or the DBP Digital Banking Portal;
ATM network disruption is affecting withdrawals and balance inquiries.
failure of a third-party telecom or payment/network provider affecting digital and ATM access;
cyber disruption that affects deposit transaction processing or fraud surveillance;
a branch and back-office disruption that delays onboarding, account servicing, reconciliation, and complaint handling. These examples align with DBP’s actual service channels and BSP’s requirement to set tolerances around the delivery of critical operations, not just system recovery times.

The key objective in establishing impact tolerance for CBS-1 Deposit and Account Services is not to promise zero disruption, but to define the point beyond which disruption becomes unacceptable for DBP’s customers, regulatory obligations, financial integrity, and institutional credibility. Consistent with BSP Circular No. 1203, DBP should ensure that these tolerances are board-reviewed, mapped to critical operations, linked to dependencies and vulnerabilities, and tested using severe but plausible scenarios.

Accordingly, the table above should be treated as a structured starting point for DBP’s operational resilience programme. The next step is to validate each tolerance against actual process capability, channel architecture, staffing, third-party dependency, data recovery capability, and business continuity arrangements, then use scenario testing results to refine tolerances and prioritise remediation. That approach is consistent with BCM Institute’s guidance to identify impact types, set tolerance levels, document them, and review them regularly as the operating environment evolves.

DBP Title Banner

eBook 3: Starting Your OR Implementation
CBS-1 Deposit & Account Services
CBS-1 DP	CBS-1 MD	CBS-1 MPR	CBS-1 ITo	CBS-1 SuPS	CBS-1 ST

Gain Competency: For organisations looking to accelerate their journey, BCM Institute’s training and certification programs, including the OR-5000 Operational Resilience Expert Implementer course, provide in-depth insights and practical toolkits for effectively embedding this model.

More Information About OR-5000 [OR-5] or OR-300 [OR-3]

To learn more about the course and schedule, click the buttons below for the OR-300 Operational Resilience Implementer course and the OR-5000 Operational Resilience Expert Implementer course.



	If you have any questions, click to contact us.

Strengthening Resilience in Public Banking: The DBP Operational Resilience Journey

[OR] [DBP] [E3] [CBS] [1] [ITo] Establish Impact Tolerances

Operational Resilience Certified Planner-Specialist-Expert

CBS-1 Deposit & Account Services

Introduction

Purpose of the Chapter

Table P4: Establish Impact Tolerance for CBS-1

Regulatory Requirements and Philippine Banking Examples

More Information About OR-5000 [OR-5] or OR-300 [OR-3]

Comments:

Strengthening Resilience in Public Banking: The DBP Operational Resilience Journey

[OR] [DBP] [E3] [CBS] [1] [ITo] Establish Impact Tolerances

hbspt.cta._relativeUrls=true;hbspt.cta.load(3893111, '0430108a-ef49-43aa-ac7d-ee6bb474eba8', {"useNewLoader":"true","region":"na1"});

Operational Resilience Certified Planner-Specialist-Expert

hbspt.cta._relativeUrls=true;hbspt.cta.load(3893111, '39340e49-edb0-4bef-baa2-32294d677282', {"useNewLoader":"true","region":"na1"});

hbspt.cta._relativeUrls=true;hbspt.cta.load(3893111, '0430108a-ef49-43aa-ac7d-ee6bb474eba8', {"useNewLoader":"true","region":"na1"}); CBS-1 Deposit & Account Services

Introduction

Purpose of the Chapter

Table P4: Establish Impact Tolerance for CBS-1

Regulatory Requirements and Philippine Banking Examples

hbspt.cta._relativeUrls=true;hbspt.cta.load(3893111, '5e80e50f-5e3e-44ea-8c43-16bf42d4f3b5', {"useNewLoader":"true","region":"na1"});

More Information About OR-5000 [OR-5] or OR-300 [OR-3]

Comments:

CBS-1 Deposit & Account Services