Skip to content
Banking & Finance

BIAN Architecture: A Common Language for a Global Banking Landscape

BIAN provides a shared language for banking services and their interactions. Explore its role in global standardisation, its relationship with ISO 20022, and the implementation decisions banks still need to own.

Perspectives · Inside the Banking Backbone

Two banks can offer the same product and describe the technology behind it in very different ways.

In one bank, the customer relationship management platform owns customer servicing. In another, that responsibility is spread across the core banking platform, a workflow engine and several channel applications. Both may expose an API called “customer update”, while disagreeing about what the operation changes, who owns the information and when the change becomes effective.

The connection can work technically while the business meaning remains uncertain.

This is where the Banking Industry Architecture Network, or BIAN, becomes relevant. Its contribution to global banking standards begins with a shared understanding of banking functions and service boundaries. The practical opportunity is to make technology decisions more comparable across institutions, vendors and transformation programmes.

What BIAN brings to banking architecture

BIAN is an independent, not-for-profit standards association bringing together banks, technology providers and other industry participants. Its stated mission centres on a common framework for banking interoperability. Its standards are developed through member-led working groups. [1]

For an architecture team, this offers an external reference against which to examine the bank’s own landscape. Instead of starting every programme with a different collection of application names, teams can discuss the banking responsibilities those applications perform.

That distinction matters. An application is a particular implementation, bought or built at a point in time. A banking responsibility may survive several generations of products, platforms and organisational structures.

BIAN helps create continuity in that discussion. The bank must still decide how to implement the responsibilities, assign ownership and meet its obligations.

Understanding the main building blocks

BIAN organises its Service Domains into a reference framework called the Service Landscape. Each Service Domain has a specific business function or purpose. Its portal also supports business scenarios that bring relevant domains together into workflows. [2]

Building block What it contributes How a bank can use it
Service Landscape A reference map organising Service Domains. Compare application coverage, overlaps and gaps.
Service Domain A defined banking responsibility with a specific purpose. Discuss ownership and boundaries independently of product names.
Service operations and semantic APIs Descriptions of interactions associated with a Service Domain. Provide a reference for service contracts and API mapping.
Business scenarios A way to describe collaboration across relevant domains. Explore how a customer or operational journey crosses responsibilities.

BIAN’s official public repository provides API specifications representing Service Domains, including OpenAPI and AsyncAPI artefacts in its current release. These make the reference material accessible to implementation teams. [3]

The value is in connecting the map, the responsibilities and the interactions. A diagram alone cannot establish whether a delivered service behaves as its consumers expect.

Its role in defining global banking standards

A global banking ecosystem needs participants to understand one another despite differences in technology and operating models. BIAN contributes an industry-developed architectural vocabulary and reference structure to that effort. [1]

Our view is that this can improve three recurring conversations.

Inside a bank: business and technology teams gain a common reference for discussing responsibilities that cut across departments.

Between a bank and its vendors: competing proposals can be compared against the same banking functions, rather than against each vendor’s product taxonomy.

Across an ecosystem: partners can start service-design discussions with a shared reference and then make their implementation differences explicit.

These benefits depend on adoption and disciplined interpretation. Calling an interface “BIAN-aligned” does not establish that two institutions can exchange requests without further work.

For a transformation programme, a useful ambition is therefore less ambiguity in the contract. The bank should be able to show precisely which reference definitions it follows, where it extends them and how those choices are tested.

BIAN and ISO 20022 address complementary concerns

ISO 20022 is a multipart international standard providing a common platform for developing financial messages. Its methodology and repository support consistent financial information definitions. [4]

BIAN brings a service-architecture perspective. Its relationship with ISO 20022 is increasingly explicit: BIAN’s March 2026 announcement of Service Landscape 14.0 highlighted stronger alignment with ISO 20022 and interoperability across APIs, messaging and modular systems. [5]

Reference or requirement Primary concern in this discussion Question for the bank
BIAN Banking service responsibilities and semantic interactions. Which responsibility does this service perform?
ISO 20022 Financial message modelling and shared information definitions. What does the exchanged financial information mean?
The bank’s implementation contract Actual behaviour, supported fields, errors, timing and compatibility. What will this deployed service do?
Applicable regulatory and scheme requirements The bank’s obligations for the relevant jurisdiction and service. What must this journey satisfy?

The bank should maintain traceability between these layers. Architectural alignment is one design input; evidence that a particular implementation meets an obligation remains a separate assessment.

A practical example: one account-opening journey, several owners

Consider a hypothetical bank modernising account opening while retaining its existing core platform.

The onboarding application captures the request. CRM holds relationship information. Verification services perform checks. The core banking system establishes the account. A communication service sends updates. An operational data store receives replicated data for query-only reads.

This example describes an illustrative allocation of responsibilities, not an official BIAN scenario or a prescribed domain mapping.

The architecture team can use the BIAN reference to examine each responsibility and compare it with the current application landscape. The essential next step is to resolve questions such as:

  • Which system is authoritative for each customer attribute?
  • Which service can request account creation, and which system actually commits it?
  • What does an acknowledgement mean: received, validated or completed?
  • How will a repeated request be recognised after a timeout?
  • Which event tells the communication service that an account genuinely exists?

Suppose the core commits an account but the response is lost. A retry must not silently create a second account. The implementation needs an agreed request identity, duplicate-handling behaviour and a way to recover the outcome.

Meanwhile, the ODS can support reads from replicated information, subject to its freshness. It performs no account-opening transaction. The architecture must preserve that boundary even if the onboarding journey reads from both the source and the replicated store.

The shared reference helps structure the discussion. The bank’s contracts and tests turn the resulting decisions into dependable behaviour.

A Service Domain is a design reference for deployment decisions

When applying a logical reference model, teams should make deployment choices explicitly. Automatically creating a separate deployable service for every mapped responsibility can introduce additional network calls, operational dependencies and support overhead.

For this article, our recommendation is to assess transaction boundaries, consistency requirements, release independence, workload and team ownership before deciding how to package the implementation.

A bank may initially expose well-defined responsibilities through adapters around an existing platform. Another may implement selected responsibilities in independently deployed services. The acceptance question should be whether the design preserves the agreed boundaries and delivers the required behaviour.

This also protects incremental modernisation. A programme can improve its contracts and ownership model before attempting a wider platform replacement.

Where BIAN can strengthen a transformation programme

For a core replacement, a shared reference can help separate banking requirements from features tied to the incumbent product. That makes it easier to ask which behaviours must be preserved and which historical arrangements can change.

For a merger, it can provide a comparison structure across two differently named landscapes. A shared domain label should start the investigation; the banks still need to compare product rules, data quality and operational practices.

For vendor selection, it can sharpen demonstrations. Ask a supplier to walk through the required responsibilities, supported interactions and exceptions, then demonstrate the resulting journey.

For integration governance, it can support a consistent catalogue. The useful catalogue entry should connect business purpose to owner, deployed endpoint, version and operational evidence.

These are proposed applications of the reference model. Their value should be measured against the bank’s actual delivery problems rather than assumed from adoption alone.

Manage the trade-offs of standardisation

A reference model can reduce repeated interpretation, but adopting it also takes effort. Teams must learn its terminology, map existing services and maintain the relationship as both the reference and the bank evolve.

There are two practical risks to manage.

First, a team may reproduce the vocabulary while leaving responsibility unclear. An API can gain a new name while still exposing the same ambiguous operation underneath.

Second, local extensions may accumulate without governance. Over time, two services carrying the same alignment label can develop different meanings. The remedy is an explicit record of extensions, their rationale and their compatibility implications.

Version management matters too. BIAN’s Service Landscape page records changes in 14.0, including renamed, removed and added Service Domains and rationalised operations. A bank should record the release it has mapped against and assess changes deliberately. [6]

A newer reference release should trigger an impact assessment, rather than an automatic production contract change.

Start with one journey and prove the outcome

A practical adoption approach is to select a journey with known ownership or integration friction, then:

  1. Establish a baseline. Record current handoffs, duplicated logic, contract gaps and recurring incidents.
  2. Map responsibilities. Select relevant BIAN reference material and document the release and any interpretation decisions.
  3. Define ownership and contracts. Agree authoritative data, commands, read models, errors and completion states.
  4. Implement and test. Include timeout, replay, partial failure and recovery scenarios alongside the successful path.
  5. Review the evidence. Assess whether delivery, reuse and incident resolution improved before extending the approach.

Security and resilience belong in that implementation assessment. Authentication, authorisation, encryption, auditability, recovery and performance must be specified for the actual journey. A semantic mapping cannot establish that those controls operate effectively.

Our perspective

BIAN’s contribution to global banking standards is a common architectural language that can travel across institutions and technology generations.

Its strongest use is as a disciplined reference for decisions. It helps teams ask clearer questions about responsibility and interaction, while leaving room for banks to differentiate through products, service and execution.

The meaningful result is a landscape in which ownership is easier to explain, contracts are easier to compare and change is easier to assess. A bank should judge its adoption by those outcomes.

Key takeaway

BIAN helps standardise how the banking industry describes services and their interactions. Combined with information standards such as ISO 20022 and rigorous implementation contracts, it can support more coherent modernisation. The bank remains responsible for turning that common language into secure, resilient and operationally clear services.

Continue the BIAN in Practice series

This foundation article is Part 1 of the series. Part 2: From Service Landscape to Clear Ownership applies the reference to a fictional lending journey, responsibility mapping and recovery ownership.

Sources & further reading

  1. BIAN — About Us. Mission, collaborative structure and member-led standards work.
  2. BIAN — Portal. Service Domains, the Service Landscape and business-scenario tooling.
  3. BIAN official public repository. Published semantic API artefacts and release-specific specifications.
  4. ISO 20022 — Official website. The financial messaging standard and its modelling approach.
  5. BIAN — Service Landscape 14.0 announcement, 13 March 2026. Recent direction and stronger ISO 20022 alignment.
  6. BIAN — Service Landscape. Release history and changes to the reference structure.

Sources checked on 18 October 2026. Scenarios, adoption recommendations and trade-off analysis are original editorial interpretation. Illustrative responsibility descriptions are not presented as official BIAN domain mappings.

Learn the topic

Put this perspective into practice.

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

Topics: , , , ,

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