The Sub-Ledger Behind a European Bank

Building the financial layer behind a modern banking platform

Industry

Banking & Financial Services

Service

Design + Development

Tools Used

Web + Backend Infrastructure

Completion Timeline

Not specified

Building the financial layer behind a modern banking platform

Overview

The platform provides the financial infrastructure required to support banking operations across accounts, transactions and financial activity.

At the centre of the platform is a dedicated sub-ledger that maintains structured financial records behind the operational banking workflows.

The goal was to create a reliable financial foundation where transactions, account activity and financial records remain connected throughout the banking lifecycle.

The Challenge

Modern banking workflows generate a constant stream of financial activity.

Payments, transfers, account movements and adjustments all need to be processed while maintaining an accurate record of their financial impact.

The challenge was creating a financial layer that could keep these records consistent and traceable without tightly coupling financial record keeping to individual banking workflows.

A Dedicated Financial Layer

The platform is structured around a dedicated sub-ledger responsible for recording financial activity.

Transaction Processing

Banking operations are validated and processed before their financial impact is recorded.

Sub-Ledger

The sub-ledger maintains structured financial entries and transaction records.

Account Activity

Financial activity is connected back to the accounts affected by each transaction.

Financial State

Recorded activity provides the foundation for maintaining account balances and financial records.

Together, these components create a clearer separation between what the banking platform does and what happens financially as a result.

From Transaction to Financial Record

The platform supports the complete lifecycle of a financial transaction:

Initiate → Validate → Process → Record → Update → Reconcile

Each stage builds on the previous one, creating a structured financial trail for every transaction.

This approach makes it easier to understand how an operation was processed, what financial impact it created and how that impact relates to the account.

The Sub-Ledger

The sub-ledger acts as the financial record behind the banking platform.

It captures the information required to understand financial activity across the system.

Financial Entries

Records the financial impact created by a transaction.

Transaction State

Maintains the state and progression of financial activity.

Account Activity

Connects transactions with the accounts they affect.

Financial Records

Provides the underlying records required to understand the resulting financial position.

Account & Transaction Management

The financial layer is designed to keep account activity and transaction records connected.

Each transaction contributes to the broader financial state of the account, creating a consistent record of activity rather than treating balances as isolated values.

This provides a clearer foundation for transaction history, account management and downstream financial processes.

Reconciliation

Financial systems need more than successful transaction processing.

They also need a reliable way to verify that recorded activity reflects the expected financial state.

The structured records maintained within the sub-ledger provide a foundation for reconciliation and financial verification.

Built for Banking Workflows

The financial layer provides a foundation that can support different banking operations without requiring each workflow to maintain its own financial record system.

This separation allows operational services to evolve while keeping financial records structured and consistent.

It also creates a foundation for extending the platform with additional banking capabilities.

Financial Architecture

The platform separates operational banking activity from the financial records created by those operations.

Banking Operations

Accounts, payments and banking workflows.

Transaction Processing

Validation and execution of financial activity.

Sub-Ledger

Financial entries, transaction state and account activity.

Financial Records

Balances and resulting financial state.

Reconciliation

Verification of financial activity.

This architecture creates a dedicated financial foundation beneath the banking experience.

Engineering the Foundation

The work focused on the product and engineering layers behind the banking platform.

The objective was not simply to build another banking interface, but to establish the financial infrastructure required to support reliable transaction processing and account activity.

The architecture was designed around four principles:

Consistency

Financial records need to remain aligned with banking activity.

Traceability

Every financial operation should leave a structured record.

Separation

Operational workflows and financial record keeping should remain distinct.

Extensibility

The financial layer should provide a foundation for future banking workflows.

The Outcome

The result is a structured financial layer that provides the foundation for banking transactions and account activity.

Traceable financial activity

Transactions leave structured financial records.

Connected account state

Financial activity remains connected to the accounts it affects.

Reconciliation foundation

Financial records provide a basis for verification.

Extensible architecture

Banking workflows can build on a dedicated financial layer.

Clearer financial infrastructure

The platform separates operational banking activity from the financial records created by it.

Gunpowder’s Role

Gunpowder worked across product strategy, design and engineering to build the systems behind the banking experience.

The focus was on creating a financial foundation that could support the complexity of modern banking operations while remaining structured enough to evolve with the platform.