“Ledger” is one of those words that means different things in different teams. Finance may mean the general ledger. Banking may mean the account posting engine. Product teams may mean a balance table. This article clears it up. It explains what a ledger system is, what a core banking ledger is, and how sub-ledgers fit in. It is not about blockchain.

Why the same word causes so much confusion

A ledger is a record of value changes. That sounds simple. But in real systems there are many ledgers. They serve different users. They also sit in different places.

If you mix them up, you get problems. You may reconcile the wrong totals. You may build reports from the wrong source. You may also break accounting rules.

Quick definitions (plain language)

Here are the terms you will hear most often.

  • Ledger system: software that stores entries, computes balances, and gives an audit trail.
  • General ledger (GL): the official accounting book for financial statements. It sits in an accounting or ERP system.
  • Sub-ledger: a detailed book that feeds the GL. Examples include loans, cards, or accounts payable.
  • Core banking ledger: the bank’s system of record for customer accounts (deposits and often loans). It posts transactions and updates balances.
  • Customer ledger vs company ledger: customer ledger tracks customer balances. Company ledger tracks the bank’s own assets, liabilities, income, and expenses.

A good way to remember it: the core banking ledger answers “What is this customer’s balance right now?” The GL answers “What do we report in our financial statements?”

What a ledger system actually does

A ledger system is not a single feature. It is a set of capabilities.

  • Stores entries with timestamps, amounts, and references.
  • Posts entries to accounts.
  • Calculates balances (available, current, ledger, accrued).
  • Prevents or flags bad postings with rules and controls.
  • Keeps an audit trail so you can explain every balance.
  • Supports reversals and adjustments without losing history.

Many products have a “ledger.” But not all are suitable for banking or accounting. The difference is usually in controls, traceability, and reconciliation support.

Accounting GL vs banking ledger: the core differences

Both are ledgers. But they are built for different jobs.

1) Purpose

General ledger exists for financial reporting. It supports month-end close. It supports audit. It supports tax and regulatory reporting.

Core banking ledger exists for running accounts. It supports real-time posting. It supports channels like mobile and branch. It supports product rules like interest and fees.

2) Level of detail

A GL is summarized. It groups activity into chart-of-accounts buckets. A core banking ledger is granular. It tracks each customer account, and often each posting line.

3) Timing

Core banking is often near real time. The GL is often batch-based. Some firms push closer to real time. But the close process still drives the GL rhythm.

4) Data model

GL systems are built around a chart of accounts, journals, periods, and posting rules.

Core banking systems are built around products, accounts, posting events, holds, and balance types.

5) “Truth” and governance

The GL is the source of truth for financial statements. The core banking ledger is the source of truth for customer balances. Both can be “true” at the same time. They answer different questions.

Where each ledger lives in a modern financial stack

In most banks and fintechs, ledgers are spread across systems. This is normal.

  • Core banking platform: holds the customer accounts and posting engine (the core banking ledger).
  • Sub-ledger platforms: cards, loans, treasury, payables, receivables, chargebacks.
  • Accounting/ERP: holds the GL and financial reporting structure.
  • Payments processors: maintain settlement and clearing views. These are ledger-like, but not your GL.
  • Data warehouse / lake: used for analytics and monitoring. It should not be used to “fix” ledger truth.

If you are designing a new product, this question helps: “Which ledger must be correct at transaction time?” That usually points to the core banking ledger (or a product sub-ledger) rather than the GL.

Sub-ledgers: what they are, and why they exist

A sub-ledger is a detail book. It tracks activity at a level the GL does not want to store. It also supports business rules that the GL is not designed to handle.

Common sub-ledgers include:

  • Loans sub-ledger: amortisation, accruals, repayment allocations.
  • Cards sub-ledger: authorisations, presentments, chargebacks.
  • Payments sub-ledger: holds, pending states, settlement batches.
  • Fees and commissions sub-ledger: fee events by product and channel.

Sub-ledgers typically feed the GL. They do it through posting files, APIs, or integration middleware. The GL then records the summarized accounting entries.

Core banking ledger: what it is (and what it is not)

A core banking ledger is the heart of account processing. It posts debits and credits to customer accounts. It applies product logic. It stores balances that channels use.

It is not the same as:

  • A reporting database: reporting copies can lag and can be incomplete.
  • A data warehouse: warehouses are for analytics, not posting.
  • The GL: the GL is for financial statements, not customer balance queries.

If you are building with partners, you may encounter “ledger” inside a platform model. For context on how fintechs assemble these building blocks, see this guide to core banking ledger components in BaaS stacks.

A simple comparison table

Topic Ledger system (general concept) Core banking ledger Accounting GL
Main user Ops, finance, product, risk Banking ops, channels, product Finance, audit, regulators
Main question “What changed, and why?” “What is the customer balance?” “What do we report?”
Posting speed Varies Often real time Often batch + period close
Typical granularity Varies Account and transaction line Chart of accounts summary
Controls Depends on design Strong controls needed Strong controls required

How money movement shows up across ledgers

Consider a card purchase. Your app may show a balance change fast. But settlement happens later. That means different ledgers can show different states at the same time.

  • Authorisation: a hold may reduce available balance in the core banking ledger.
  • Clearing: a presentment may move from pending to posted.
  • Settlement: the bank settles with networks and partners, often in batches.
  • Accounting: the GL records revenue, interchange, and liabilities at the right time.

If you want a clear view of these stages, this explainer on ledger posting during money movement is a helpful companion.

Reconciliation: the glue between ledgers

When you have more than one ledger, you must reconcile. Reconciliation proves that totals match, even if detail differs.

Common reconciliation pairs include:

  • Core banking ledger totals vs GL control accounts.
  • Payments sub-ledger vs processor settlement reports.
  • Cards sub-ledger vs scheme files and chargeback data.
  • Loan sub-ledger accruals vs GL interest income.

Reconciliation is also a control for fraud and errors. It benefits from strong monitoring and clear audit trails. Controls like these are part of broader operational defence, similar to the practices in ledger system controls for preventing fintech crime.

Common misconceptions (and the correct view)

“The ledger is just a database table.”

A table can store entries. But a ledger system also needs rules, traceability, and safe correction paths. Without that, it is easy to create silent balance drift.

“If we have a core banking ledger, we don’t need a GL.”

You still need the GL for financial statements and period close. The core banking ledger is not designed to be your full accounting engine.

“Sub-ledger and GL are the same thing.”

A sub-ledger is detailed and operational. The GL is summarized and report-driven. Sub-ledgers feed the GL.

“Ledger means blockchain.”

Not here. Banks used ledgers long before blockchain. In this article, ledger means internal financial recordkeeping.

How to decide which “ledger” you need

If you are choosing or designing a ledger system, start with these questions.

  • Who needs the balance? Customer channels, finance, or both?
  • How fast must it update? Real time, near real time, or daily?
  • What states must it support? Pending, held, posted, reversed, disputed.
  • What controls are required? Dual control, approvals, limits, and audit logs.
  • How will you reconcile? Define control totals and ownership early.
  • What is the accounting policy? Revenue timing and accrual rules drive postings.

For accounting treatment and disclosure expectations, it helps to align with established standards such as IFRS financial reporting standards. For bank supervision context, guidance and principles from bodies like the Basel Committee on Banking Supervision are also useful references.

Practical example: a simple deposit account posting

Let’s say a customer receives salary.

  • Core banking ledger: posts credit to the customer account. Balance updates for the app.
  • Payments/clearing view: confirms inbound transfer status and settlement.
  • GL: records the liability increase in deposits. It may also record fees.

Each record is linked. But each serves a different purpose. That is why “which ledger is right” depends on the question you ask.

Key takeaways

  • A ledger system is software for entries, balances, and audit trails.
  • The core banking ledger is the system of record for customer accounts and posting.
  • The GL is the system of record for financial reporting.
  • Sub-ledgers hold operational detail and feed the GL.
  • Reconciliation is mandatory when multiple ledgers exist.

FAQs

Is a core banking ledger double-entry?

Often, yes. Many core systems use double-entry concepts internally. But implementations vary. What matters most is consistency, traceability, and the ability to reconcile to the GL.

Can a fintech run without a core banking ledger?

If you hold customer funds or issue accounts, you need a reliable account ledger somewhere. It may be provided by a BaaS partner. But the ledger function still exists.

Where does the “ledger balance” vs “available balance” come from?

These are balance types in the core banking ledger (or a payments sub-ledger). Holds and pending items usually affect available balance first.

Does the GL need transaction-level detail?

Usually not. The GL needs enough detail to support reporting and audit. Transaction-level detail is normally kept in sub-ledgers and operational systems.

What is the fastest way to reduce ledger confusion in an organisation?

Name each ledger by function and owner. For example: “Customer Account Ledger (Core)” and “Financial GL (ERP).” Then document which reports must use which source.