Unit 08 · Chapter 2 · 10 min read

Treasury, liquidity, and settlement operations

Keep usable funds aligned with the obligations that come due.

Friday’s balance looks healthy. Saturday’s instant payouts continue. Monday’s incoming settlement has not arrived. A business can run out of usable money between two perfectly reasonable daily reports.

Build a time and currency cash ladder

A cash ladder shows opening usable funds, expected inflows, committed outflows, and buffers by time and currency. Distinguish funds available now from funds expected later. A balance restricted for one purpose may not fund another obligation.

Use intraday detail where the product requires it. Instant services and cross-border partners can create obligations outside ordinary office hours. Record assumptions about holidays, settlement timing, and partner availability. The ladder should show which shortfalls are certain under current commitments and which arise only in a stress scenario.

A cash ladder places expected inflows and outflows into time buckets by currency and usable location. A total across all bank balances can hide the fact that funds are in the wrong currency, held at an unavailable institution, or arriving after a payment cutoff. Treasury needs the amount it can actually use for the obligation at the required time.

Separate forecasts from confirmed balances and identify the confidence of expected receipts. A merchant payout funded by an incoming settlement depends on both events occurring in the expected sequence. If the receipt is delayed, the platform may need another approved funding source or a controlled change to the payout. The customer-facing status should reflect that operational reality.

Build a time and currency cash ladder Build a time and currency cash ladder — the flow Follow the sequence. Compare obligations with available resources. Open Identify usable funds by currency Schedule Place inflows and outflows in time Gap Compare obligations with available resources — Follow the sequence. Compare obligations with available resources. Chapter sources · Open image

Build a time and currency cash ladder Build a time and currency cash ladder — the distinction These concepts answer different questions. Read each definition in the context of the section. Ledger cash Recorded asset balance Usable liquidity Funds accessible for this obligation now — These concepts answer different questions. Read each definition in the context of the section. Chapter sources · Open image

Build a time and currency cash ladder Weekend ladder Fictional teaching record. Does not automatically cover the weekend. Weekend ladder Illustrative data; not a real customer record or a prescribed policy. Usable Friday 90000 USD Available opening funds Weekend payouts 110000 USD Expected committed outflow Monday inflow 60000 USD Does not automatically cover the weekend An aggregate balance can hide an immediate gap — Fictional teaching record. Does not automatically cover the weekend. Chapter sources · Open image

Build a time and currency cash ladder Build a time and currency cash ladder — control and failure modes An aggregate balance can hide an immediate gap. The branches show why alternative designs fail. Control design Model time currency and restrictions. An aggregate balance can hide an immediate gap. Failure mode 1 Count Monday funds as Saturday cash. Timing still matters. avoid Failure mode 2 Mix currencies without conversion assumptions. Amounts are not directly additive. avoid Failure mode 3 Use restricted customer funds as general liquidity. Permitted use must be established. avoid — An aggregate balance can hide an immediate gap. The branches show why alternative designs fail. Chapter sources · Open image

Reconcile settlement at the item level

Settlement operations compare processor reports, bank statements, internal journals, and customer obligations. Use stable references and explicit handling for fees, returns, timing, and currency differences.

A matched batch total is useful but insufficient for consequential discrepancies. Investigate unmatched items and age them with an owner. Avoid suspense accounts that become permanent storage for unexplained money. A suspense balance should have supporting items and a resolution path. Regular item-level reconciliation makes a sudden partner problem easier to distinguish from an old internal defect.

Reconcile settlement at the item level Reconcile settlement at the item level — the flow Follow the sequence. Clear supported breaks with an owner. Match Connect independent settlement records Classify Explain fees timing and exceptions Resolve Clear supported breaks with an owner — Follow the sequence. Clear supported breaks with an owner. Chapter sources · Open image

Reconcile settlement at the item level Reconcile settlement at the item level — the distinction These concepts answer different questions. Read each definition in the context of the section. Suspense account Temporary location for unresolved items Resolved balance Every amount has an explained economic owner — These concepts answer different questions. Read each definition in the context of the section. Chapter sources · Open image

Reconcile settlement at the item level Suspense review Fictional teaching record. Needs investigation. Suspense review Illustrative data; not a real customer record or a prescribed policy. Balance 18000 USD Unresolved total Supported items 15000 USD Identified references Unexplained 3000 USD Needs investigation A total alone cannot explain ownership — Fictional teaching record. Needs investigation. Chapter sources · Open image

Reconcile settlement at the item level Reconcile settlement at the item level — control and failure modes A total alone cannot explain ownership. The branches show why alternative designs fail. Control design Reconcile suspense to individual supporting items. A total alone cannot explain ownership. Failure mode 1 Leave aged breaks indefinitely. Uncertainty can accumulate. avoid Failure mode 2 Force-match to clear the dashboard. That hides the difference. avoid Failure mode 3 Treat every break as a partner error. Internal mapping may be responsible. avoid — A total alone cannot explain ownership. The branches show why alternative designs fail. Chapter sources · Open image

Stress partner and funding concentration

A single bank, processor, or funding source can support several products. Its failure can create correlated liquidity and operational problems. Map dependencies beneath the visible product lines.

Stress delayed settlement, account restrictions, reduced credit availability, and higher refunds. Separate contractual access to a facility from the ability to draw it under stress. Test contact and approval procedures. A funding plan that requires an unavailable executive at midnight is not fully executable. The response should preserve legal restrictions and customer obligations.

Stress partner and funding concentration Stress partner and funding concentration — the flow Follow the sequence. Test approved funding and operating options. Dependency Identify shared funding and settlement providers Shock Model delayed or unavailable access Response Test approved funding and operating options — Follow the sequence. Test approved funding and operating options. Chapter sources · Open image

Stress partner and funding concentration Stress partner and funding concentration — the distinction These concepts answer different questions. Read each definition in the context of the section. Committed facility Contractual funding arrangement Drawable funds Amount actually accessible under current conditions — These concepts answer different questions. Read each definition in the context of the section. Chapter sources · Open image

Stress partner and funding concentration Partner stress Fictional teaching record. Readiness gap. Partner stress Illustrative data; not a real customer record or a prescribed policy. Products three Different customer experiences Settlement bank one Shared dependency Contingency draw conditions untested Readiness gap A contract alone does not prove immediate liquidity — Fictional teaching record. Readiness gap. Chapter sources · Open image

Stress partner and funding concentration Stress partner and funding concentration — control and failure modes A contract alone does not prove immediate liquidity. The branches show why alternative designs fail. Control design Test actual access under the stress conditions. A contract alone does not prove immediate liquidity. Failure mode 1 Assume product diversity means funding diversity. The same partner may support all products. avoid Failure mode 2 Ignore refund surges. They can coincide with delayed inflows. avoid Failure mode 3 Rely on an untested midnight approval. Operational access can fail. avoid — A contract alone does not prove immediate liquidity. The branches show why alternative designs fail. Chapter sources · Open image

Separate reserves capital and liquidity

A reserve can cover specified exposure under its terms. Capital absorbs losses at the firm level under the relevant accounting and regulatory framework. Liquidity meets obligations when due. These concepts interact but are not interchangeable.

A firm may have enough capital and insufficient same-day cash. A merchant reserve may be liquid but unavailable for the platform’s unrelated operating expense. Use distinct measures and avoid counting the same resource as protection for several simultaneous obligations. The decision should show what each resource can legally and operationally do.

Capital, reserves, and liquidity serve different purposes. Capital can absorb losses without necessarily being held as immediately usable cash. A merchant reserve can support a defined claim while remaining subject to eligibility and access conditions. Liquidity concerns the ability to meet cash obligations when due. A sound report keeps these measures distinct and then explains how they interact in a stress event. Calling all three a buffer hides which problem each resource can actually solve.

Separate reserves capital and liquidity Separate reserves capital and liquidity — the flow Follow the sequence. Assess timely payment ability. Reserve Identify purpose-specific cover Capital Assess loss-absorption resources Liquidity Assess timely payment ability — Follow the sequence. Assess timely payment ability. Chapter sources · Open image

Separate reserves capital and liquidity Separate reserves capital and liquidity — the distinction These concepts answer different questions. Read each definition in the context of the section. Loss absorption Capacity to bear an economic loss Payment ability Access to funds when an obligation is due — These concepts answer different questions. Read each definition in the context of the section. Chapter sources · Open image

Separate reserves capital and liquidity Resource classification Fictional teaching record. Subject to actual restrictions. Resource classification Illustrative data; not a real customer record or a prescribed policy. Merchant reserve restricted purpose Not general operating cash Equity loss absorption May not be held as cash Bank balance available cash Subject to actual restrictions One balance cannot perform every role automatically — Fictional teaching record. Subject to actual restrictions. Chapter sources · Open image

Separate reserves capital and liquidity Separate reserves capital and liquidity — control and failure modes One balance cannot perform every role automatically. The branches show why alternative designs fail. Control design Keep resource purpose and availability distinct. One balance cannot perform every role automatically. Failure mode 1 Use capital ratio as a cash forecast. Solvency and timing differ. avoid Failure mode 2 Spend restricted reserves on unrelated costs. Permitted use matters. avoid Failure mode 3 Allocate the same cover to multiple stress losses. That double counts protection. avoid — One balance cannot perform every role automatically. The branches show why alternative designs fail. Chapter sources · Open image

Communicate funds status accurately

Customers need to distinguish pending, available, reserved, paid out, returned, and restricted funds. The displayed state should come from the authoritative ledger and policy, with clear explanations of relevant conditions.

Do not show a projected settlement as spendable merely to make the interface feel instant. If the product advances funds before settlement, record that as a separate exposure and promise. During an incident, keep status messages aligned with known facts and update them as evidence changes. Clear funds language reduces support load and prevents customers from planning around money they cannot use.

Communicate funds status accurately Communicate funds status accurately — the flow Follow the sequence. Explain the state and next event. Ledger Establish the authoritative financial state Policy Determine current availability Display Explain the state and next event — Follow the sequence. Explain the state and next event. Chapter sources · Open image

Communicate funds status accurately Communicate funds status accurately — the distinction These concepts answer different questions. Read each definition in the context of the section. Pending funds Expected but not yet available Available funds Usable under the product’s current conditions — These concepts answer different questions. Read each definition in the context of the section. Chapter sources · Open image

Communicate funds status accurately Balance screen record Fictional teaching record. Simple eligible difference. Balance screen record Illustrative data; not a real customer record or a prescribed policy. Settled balance 500 USD Ledger amount Reserved 100 USD Restricted for an obligation Available 400 USD Simple eligible difference Visual speed must not invent usable money — Fictional teaching record. Simple eligible difference. Chapter sources · Open image

Communicate funds status accurately Communicate funds status accurately — control and failure modes Visual speed must not invent usable money. The branches show why alternative designs fail. Control design Derive availability from ledger and policy. Visual speed must not invent usable money. Failure mode 1 Label every incoming payment available. Settlement and restrictions can differ. avoid Failure mode 2 Hide reserve effects. Customers cannot explain their balance. avoid Failure mode 3 Call an advance settled cash. The funding exposure is different. avoid — Visual speed must not invent usable money. The branches show why alternative designs fail. Chapter sources · Open image

Chapter connections

This chapter builds on Case operations and human decisions. Continue with Operational resilience and failure design to follow the next part of the system. Use the glossary for terminology and risk mathematics for formulas and worked calculations.

Sources

Reviewed 2026-09-17