Centralized Banking Systems

Centralization can refer to shared customer information, common services, or centrally managed operating rules. Pooya’s account-management documentation describes a Customer Information File, or CIF, used across branches, headquarters, and electronic banking. It also describes common interfaces and centrally maintained definitions. This provides a concrete Iranian example of intended information sharing, rather than proof that every bank uses the same architecture. s1

The important distinction is between a common customer record and a particular service channel. A branch and an electronic channel can draw on shared information while presenting different interfaces. The supplier’s description supports that design principle; it does not establish transaction speed, availability, or consistency under failure. s1

Pooya’s international-banking product offers a useful qualification. It describes a centralized database and integrated foreign-currency subsystems serving branches and specialist offices. Its documented scope includes foreign-currency accounts, trade-related operations, guarantees, and treasury. This demonstrates that centralization can occur within a specialized operational domain. s2

The same documentation describes links between foreign-currency operations, local-currency customer accounts, and the general ledger, including end-of-day accounting summaries. That description should not be generalized to every Iranian bank or read as proof of fully real-time integration. It also advertises messaging interfaces; software support alone does not establish a bank’s access to an international network or correspondent relationship. s2

Centralization within a specialized banking domain

This simplified interpretation of Pooya's product description separates service access from account and accounting interfaces. It is not a verified architecture diagram for a named bank.

Centralization makes dependencies important to understand. The Basel Committee’s resilience guidance calls for identifying the people, technology, information, facilities, and relationships supporting critical operations. Applied here as an analytical framework, that means asking which services depend on a shared component and how they continue through disruption. The guidance does not certify an Iranian implementation. s3