Quick answer: a bank does not decide whether money is “available” by looking only at the posted ledger balance. The account engine can also consider authorisation holds, pending credits and debits, deposited-item availability, card reversals, overdraft limits or linked protection, account restrictions and transaction-specific rules. The result is a real-time state variable: how much of the account can this customer use for this transaction at this moment? That state can differ from the amount shown on the last statement and can change between card authorisation and final settlement.

The ledger answers, “What has posted?” Available balance answers, “What can be spent now under the bank’s current rules and known commitments?”

Jurisdiction boundary: the mathematical architecture is general. Consumer overdraft law is jurisdiction-specific. Where this article discusses Regulation E, CFPB guidance or US opt-in requirements, those are United States examples—not universal banking rules.

Why this belongs in mathematics

Available-balance calculation is a state-machine and accounting problem. The system receives asynchronous events—deposits, card authorisations, reversals, ACH items, cheques, fees and settlement messages—and must transform them into a consistent current state without double-counting provisional events or losing final ones. Overdraft decisioning then adds policy constraints: whether a transaction may be authorised, whether temporary credit is available, and whether any fee may lawfully or contractually be charged.

This sits next to How Banks Reconcile Transactions. Reconciliation repairs agreement after events have moved; available-balance logic decides what the account should permit before all those events have become final.

1. Ledger balance and available balance are different objects

Suppose an account has S$1,000 of posted ledger balance. The customer has also used a debit card for a S$300 hotel deposit that has been authorised but not yet settled. A simple available-balance engine might therefore begin with:

Available balance = posted ledger balance − active debit holds + recognised available credits ± other permitted adjustments.

In the simple example, ignoring other adjustments, available balance becomes S$700 even though the posted balance remains S$1,000.

The distinction is essential because authorisation holds represent spending commitments that have not yet become final ledger entries.

2. Authorisation creates provisional state

A card transaction can pass through several states:

request → authorised hold → clearing → final posting

or:

request → authorised hold → reversal/expiry → hold released.

The hold protects against spending the same economic capacity twice. But it is provisional. Hotels, fuel stations and other merchants can authorise estimated amounts that later settle differently. The account engine must therefore match the clearing event to the earlier hold and release any remaining reservation correctly.

That lifecycle connects to How Card Authorisation Algorithms Decide Approve or Decline.

3. A real-time balance engine is an event processor

Let A_t be available balance after event t. A simplified recurrence is:

A_t+1 = A_t + available credits − new holds − posted debits + released holds ± policy adjustments.

But the event types are not interchangeable. A deposited cheque may increase ledger balance while some or all funds remain unavailable. A card reversal releases a reservation but is not new income. A final clearing entry should replace, not duplicate, the corresponding hold.

The state machine therefore needs event identity and lineage, not merely signed amounts.

4. Holds create the “same money twice” problem

Suppose a S$100 purchase is authorised and creates a S$100 hold. Later the S$100 clearing transaction posts. If the system subtracts the posted transaction but forgets to release the hold, the account is reduced by S$200 economically. If it releases the hold before recording the final transaction, the customer may temporarily appear to have S$100 more available than intended.

A strong engine therefore uses matching keys, transaction references, merchant data, amount tolerances and timing windows to connect provisional and final states.

5. Pending credits are not always immediately spendable

The opposite error is equally important. A credit can be visible but not yet fully available. Deposited items can be subject to availability schedules, fraud review, legal holds or return risk. A bank therefore needs separate fields for:

posted amount;
available amount;
hold amount;
hold expiry/release condition;
finality state;
source transaction and legal availability rule.

This is why a customer-facing “balance” should be labelled clearly. A single number cannot simultaneously mean posted balance, cleared funds, available balance and future projected balance.

6. Overdraft decisioning adds a credit boundary

When a debit request exceeds positive available funds, the bank still has several possible policies. It may decline the item, return it, transfer funds from a linked account, draw an agreed overdraft line, or pay into an overdraft under a discretionary service where permitted.

A simplified decision rule is:

Approve if transaction amount ≤ available balance + usable overdraft capacity

subject to account status, transaction type, consumer elections, credit rules, fraud controls and jurisdiction-specific law.

An overdraft limit is therefore not “extra balance.” It is conditional short-term credit or discretionary coverage with different legal and economic treatment.

7. US Regulation E creates a specific opt-in boundary

In the United States, Regulation E contains special rules for overdraft fees on ATM and one-time debit-card transactions. For covered overdraft services, a financial institution generally may not charge the consumer an overdraft fee for paying those transactions unless the consumer has affirmatively opted in after receiving the required notice and confirmation.

See current Regulation E §1005.17 and CFPB Circular 2024-05 on evidence of overdraft opt-in.

The rule does not force a bank to approve an overdraft simply because the consumer opted in. It governs the fee/consent framework for specified transactions. Checks, ACH and recurring transactions have different treatment under that particular opt-in provision.

8. Authorise-positive, settle-negative: timing can change the state

Consider an account with S$100 available when a S$75 debit-card transaction is authorised. Before that transaction settles, another transaction posts and lowers the available funds. The original card transaction later arrives for settlement when the account would go negative.

This pattern is often described as authorise positive, settle negative (APSN). The arithmetic is simple; the fee/legal treatment is not. The CFPB’s 2022 Circular identified unanticipated overdraft-fee practices involving transactions authorised on a positive balance but settling on a negative balance as potentially unfair under federal consumer-financial law. Current Regulation E commentary also contains transaction-specific requirements affecting fee assessment.

See CFPB Circular 2022-06. The educational lesson is broader than US law: a bank should preserve the account state at authorisation and settlement rather than reconstructing the earlier decision from today’s balance.

9. Posting order changes path-dependent outcomes

Suppose an account has S$100 and three debits arrive for S$70, S$40 and S$20. If all are posted from smallest to largest, the path is different from largest to smallest. Depending on the account terms, fee rules and local law, the number and timing of items that encounter insufficient funds can change.

The deeper mathematical point is that posting is not necessarily commutative when policy consequences depend on crossing zero:

apply(A) then apply(B) can create a different fee/state path from apply(B) then apply(A).

A bank therefore needs transparent ordering rules and should test whether a posting sequence creates unintended consumer or operational outcomes. No single posting-order rule is universal across jurisdictions and products.

10. A worked state example

Assume:

posted ledger balance = S$500;
active card hold = S$120;
available deposited funds not yet posted = S$50;
usable agreed overdraft line = S$200.

Ignoring other rules:

cash available before overdraft = 500 − 120 + 50 = S$430.

maximum decision capacity including the line = 430 + 200 = S$630.

A S$450 transaction would exceed positive funds by S$20 but remain inside the illustrative overdraft line. A S$650 transaction would exceed total illustrated decision capacity. Whether either transaction is actually approved still depends on transaction type, account restrictions, credit and consumer rules.

11. Overdraft limits should be modelled separately from ordinary funds

If a customer repeatedly uses a S$500 overdraft line, the system should not report that account as having S$500 of cash. It has zero or negative own funds plus conditional credit capacity.

Useful state fields include:

own available funds;
linked-transfer capacity;
formal credit-line capacity;
discretionary overdraft capacity;
fees/interest accrued;
account restrictions;
time since negative balance began.

This keeps liquidity and credit concepts separate in the account representation.

12. False insufficiency is a control failure

A bank can wrongly decline a legitimate payment if a stale hold remains, an incoming credit is not recognised when it should be, a duplicate pending transaction is counted twice, or a reversal message fails to release capacity.

This is the deposit-account equivalent of a false decline in card authorisation. It is not harmless merely because the bank avoided credit risk. The customer can suffer missed-payment consequences while the bank’s internal state was wrong.

13. Creative-work lens: a theatre ticket reservation

A seat can be reserved without yet being sold. During the reservation, the theatre should not sell the same seat to somebody else. If the reservation expires, the seat must return to inventory. A debit-card hold behaves similarly: it reserves spending capacity before final posting.

The analogy helps with provisional state. It breaks if pushed too far: money is fungible, account law matters, and multiple payment rails can interact. The ledger remains the source of truth.

14. The available-balance algorithmic pipeline

Load posted ledger state.
Load active debit holds and pending debits.
Identify available versus unavailable credits.
Match reversals and clearing events to provisional holds.
Apply account restrictions and legal availability rules.
Calculate own-funds available balance.
Calculate linked or credit-based overdraft capacity separately.
Classify incoming transaction type.
Apply fraud, account and consumer-election controls.
Approve, decline, return or route according to governed policy.
Create new provisional state where necessary.
Apply final posting in the governed sequence.
Assess any fee only under applicable contract and law.
Reconcile the account after settlement and reversal events.

15. Failure modes

Ledger=available assumption. Pending obligations are ignored.
Stale hold. Capacity remains reserved after the transaction was reversed or expired.
Double subtraction. A hold and its final clearing item both reduce available balance.
Pending-credit optimism. Funds are made spendable before applicable availability conditions are satisfied.
State-history loss. The bank cannot reconstruct the balance at authorisation time.
Posting-order opacity. Non-commutative ordering creates consequences nobody can explain.
Overdraft-capacity confusion. Credit is displayed or modelled as owned cash.
Fee-before-rule logic. Operational fee code runs without checking transaction type, consent and applicable law.

16. Diagnostics and falsifiers

Can the bank reproduce the available balance shown at any historical transaction time?
How many holds remain after their matching reversal or clearing event?
How often are legitimate transactions declined because of stale provisional state?
Does the same set of items produce different overdraft outcomes under different posting order?
Are own funds and overdraft credit displayed separately?
For covered US transactions, is evidence of affirmative opt-in available before a fee is charged?
Which transaction type generates the most balance disputes?
Can an independent ledger replay reproduce every fee and decline?

Suppose someone claims, “The account was negative at settlement, so the overdraft decision was obviously correct.” A falsifier is a historical state showing that the bank authorised the transaction when sufficient funds were available and later balance changes, stale holds or posting logic caused the negative settlement state. Settlement balance alone does not reconstruct the decision path.

17. Verification and update triggers

replay raw events through an independent balance calculator;
test hold/clearing/reversal lifecycle edge cases;
test duplicate and out-of-order messages;
review posting logic after core-banking changes;
verify consumer elections and fee evidence where law requires it;
track balance disputes and false insufficiency;
update rules when payment rails introduce new provisional states;
retain historical product and legal-rule versions so prior decisions remain reconstructable.

Research anchors

The deeper lesson

Available balance is the mathematics of provisional truth. The posted ledger tells us what has become final. Holds represent obligations that may become final. Availability rules decide which credits may be used. Overdraft logic adds conditional credit and consumer rules. A strong system therefore does not ask only “What is the balance?” It asks “Which events are final, which are provisional, what capacity is genuinely usable now, and can we reconstruct why the system believed that at the moment it made the decision?”

Educational note: This article explains deposit-account mathematics and public US regulatory examples. It is not legal advice, account-specific overdraft advice or a substitute for the terms governing any bank account.

Small Group Tutorials

How Banks Calculate Available Balance and Overdraft Decisions: Holds, Posting Order, Overdraft Limits, Fees and Real-Time Ledger State