Skip to content
Banking & Finance

User, Data and Integration Governance: The Backbone of Modern Banking Architecture

Three governance disciplines determine whether modern banking architecture is merely connected or genuinely secure, accountable and dependable.

Perspectives · Banking · Architecture · Governance

A bank completes a major core banking transformation. The new Core Banking System (CBS) is operational, digital channels are connected, applications are integrated and management dashboards are available.

A few weeks later, an employee who has moved departments still retains access to an old application. Two dashboards report different customer numbers. A failed payment cannot be traced because the channel, middleware and core banking systems maintain different transaction references.

None of these problems necessarily indicates a failure of the new CBS. They reveal something more fundamental: modern banking architecture requires governance that extends beyond individual platforms.

Three disciplines are central to this challenge—User Governance, Data Governance and Integration Governance. They may be implemented through different technologies and managed by different teams, but they must operate together whenever a person or system performs a banking activity.

1. Why governance must begin with the architecture

Consider a banking landscape containing core banking, CRM, loan origination, digital channels, payment applications, fraud monitoring and regulatory reporting. Every application may have its own security model, information structures, interfaces and operating procedures.

Modernisation can improve these components individually without correcting inconsistencies between them. A new API gateway does not automatically resolve weak authorisation within an application. A central identity platform does not correct excessive permissions. An ODS does not make inconsistent source information authoritative.

The bank needs to establish who is authorised to act, which system owns each business decision, how information moves, what happens when an interaction fails and who remains accountable for investigating its outcome. Those questions should shape the architecture before technology implementation begins.

2. User Governance: Who can act, and under whose authority?

A branch employee moves from customer servicing to credit operations. The new role is assigned, but access to the old application remains active. The bank has centralised authentication without governing the complete access lifecycle.

Central identity is a starting point, not the destination

User Governance covers onboarding, authentication, authorisation, role changes, privileged access, access certification and deprovisioning. Single Sign-On (SSO) simplifies authentication across participating applications. Multi-Factor Authentication (MFA) strengthens identity verification. Identity governance manages entitlements and approvals. Privileged Access Management (PAM) controls elevated access.

The application performing a sensitive business action must still determine whether the actor is authorised for that action. A relationship manager permitted to view a customer record is not automatically permitted to approve a loan, modify a beneficiary or release a payment.

Do not overlook non-human identities

Banks also operate service accounts, batch users, API clients, database identities and integration credentials. Assign them accountable owners, limited privileges, managed credentials, rotation procedures and auditable activity. An old integration credential active after a migration can be as dangerous as an orphaned employee account.

The outcome: The bank can establish who or what performed an action, under which authority, and how the access was approved and maintained.

3. Data Governance: Which information can the bank trust?

A customer changes a mobile number through digital banking. Core banking reflects the change, but CRM continues to show the old number. A reporting platform receives both records and treats them as different customer profiles. The systems may all be technically operational; the information is still inconsistent.

Separate data movement from data authority

For important banking entities—customer, account, loan, transaction and product—the bank should identify the authoritative source and the owner of critical attributes. Other systems may hold replicas or derived views, but they should not silently become competing sources of truth.

A common data model aligns definitions across applications, but it cannot replace explicit business meaning. A loan marked approved in origination may not yet be disbursed in core banking. Treating those states as equivalent creates reporting errors.

Where the Operational Data Store fits

An Operational Data Store (ODS) is a query-only replicated data store populated through replication engines or controlled ETL pipelines. It supports dashboards, curated reporting data and downstream reads while reducing load on source transactional systems. It does not execute a payment, update core banking, retry a failed posting or reverse a transaction.

Consumers must know the freshness, lineage and quality of the replicated view. An instruction missing from a lagging replica is not evidence that the authoritative core posting failed.

Make reconciliation accountable

Replication success is not the same as data reconciliation. Banks need controls comparing critical records, financial totals, statuses and other business attributes across source and target. Exceptions require owners, ageing thresholds and documented closure.

The outcome: The bank knows which information is authoritative, how derived information was produced and whether it is fit for the intended decision.

4. Integration Governance: How do systems communicate safely?

A digital channel sends a fund transfer through an API gateway and middleware to core banking. The core posts the debit, but the response times out before reaching the channel. The channel retries. Without agreed transaction identity, retry eligibility and duplicate prevention, one failed response can create a second financial instruction.

A platform is not the same as governance

API gateways provide exposure controls and routing. Enterprise Service Buses mediate between heterogeneous applications. Brokers support asynchronous messages, and managed file transfer platforms handle controlled batch exchange. None of these tools alone defines end-to-end business accountability.

Each material integration should have a documented purpose, owner, contract, security model, business identifier, service expectations and recovery procedure. Response states must distinguish receipt, acceptance, processing and completion. A middleware timeout does not prove that a posting failed.

Preserve business meaning

Integration contracts should define authorised operations, required information, error meanings, version compatibility and the authority for financial outcomes—not just request schemas. Avoid placing product-specific business decisions in shared middleware without explicit ownership.

Design for uncertain outcomes and recovery

Preserve stable identifiers, implement appropriate duplicate controls, define bounded retries and verify uncertain outcomes against authoritative systems. Maintain correlation across hops and control the lifecycle of certificates, secrets and interfaces in production and disaster recovery.

A forgotten old endpoint or active credential after migration is an uncontrolled execution path, not merely technical debt.

The outcome: The bank understands its interfaces and dependencies, and can establish what happened when something goes wrong.

5. One journey, three governance responsibilities

Consider a relationship manager initiating a customer loan disbursement. User Governance confirms identity, permissions and approval authority. Data Governance establishes the authoritative loan details, amount, beneficiary and state. Integration Governance controls how the approved instruction reaches the posting service and how the outcome is traced.

PillarCritical questionEvidence
UserWas the actor authorised to initiate or approve?Identity, entitlement and approval records
DataWere the loan and beneficiary details authoritative and current?Source records, validation and lineage
IntegrationWas the approved instruction executed as permitted?Transaction references, states and reconciliation

If the response disappears, the outcome must be checked with the authoritative posting service. The ODS may support later reporting and reconciliation, but it cannot perform financial correction. The value of governance becomes clearest when the happy path fails.

6. Who owns the decisions?

Technology teams implement controls, and a system integrator can coordinate dependencies and delivery. The bank retains accountability for business decisions, information authority and risk acceptance under its approved governance.

Business owners define the permitted activity and correct outcome. Identity and security teams manage authentication and access controls. Data owners establish definitions, quality and authorised use. Application and integration owners maintain contracts, dependencies and recovery. Enterprise Architecture connects these decisions through consistent standards and design reviews.

Risk, compliance and internal audit provide challenge and assurance within their mandates. They do not replace the business or technology owners accountable for operating controls. The goal is not another approval layer for every change; it is visible, supported ownership for material decisions.

7. How should a bank begin?

Begin with a handful of critical journeys: customer onboarding, account servicing, loan disbursement or fund transfer. Map identities, authoritative records, applications, interfaces and final business outcomes. Identify the decision owner and evidence at each boundary.

The exercise may reveal dormant users, conflicting data ownership, undocumented recovery procedures, stale reporting views or payment retry paths lacking duplicate controls. Prioritise these by customer impact, financial risk and operational importance.

Implement shared standards in controlled waves and make verification part of application onboarding, release management and periodic assurance—not a one-time transformation activity.

8. Measure governance through banking outcomes

For user governance, examine orphaned accounts, privileged-access certification and access-revocation times. For data, measure reconciliation exceptions, quality gaps and stale feeds. For integration, track undocumented interfaces, unresolved transaction outcomes and recovery performance.

Connect these indicators to customer and business impact. A low API error rate can coexist with pending payments; high SSO coverage does not demonstrate correct entitlements. Governance evidence should establish whether the complete journey remains dependable.

The perspective: Governance is the architecture behind the architecture

Banks will continue to modernise core platforms, adopt cloud services and expand their API ecosystems. Technology will evolve; accountability will remain.

User Governance establishes who can act. Data Governance establishes which information can be trusted. Integration Governance establishes how systems interact and how their outcomes can be traced. These are responsibilities that converge in nearly every banking journey.

A modern banking architecture is defined not only by how successfully its systems connect, but by how reliably the bank governs what happens across those connections.

Continue with Learning

The Governance Triangle: Who Owns the Banking Outcome? A loan disbursement reaches core banking through middleware, but its response disappears. Explore the identity, data and integration controls needed to establish the outcome and determine who may act. Mid level · 10 minutes · Scenario-based mission.

Learn the topic

Put this perspective into practice.

Explore the concepts, make a decision and test what changes when the situation changes.

Leave a Reply

Your email address will not be published. Required fields are marked *

An invitation to contribute

Everyone has a perspective worth hearing.

A lesson from your profession. An experience that changed your mind. A question you think deserves a better conversation.

Share your perspective