Daylight Overdrafts: Intraday Liquidity

By Ryan O'Connell, CFA, FRM Published November 11, 2026

A bank can finish the day with money in its Federal Reserve account and still need credit to make payments earlier that day. Daylight overdrafts arise when the account goes negative during the business day. The underlying problem is payment timing: an outgoing obligation may come due before an expected incoming payment arrives.

This U.S.-focused guide follows a hypothetical Reserve Bank account through one day, measures its largest funding gap, and separates that calculation from the Federal Reserve’s rules for caps, collateral and fees. It then considers payment queues, CHIPS liquidity saving and delayed-receipt stress. The policy discussion reflects official materials accessed November 11, 2026; individual institutions’ eligibility and approved arrangements differ.

What Are Daylight Overdrafts?

A daylight overdraft is a negative balance in an institution’s Federal Reserve account during the business day. It represents intraday credit from a Reserve Bank. The Federal Reserve’s Payment System Risk policy governs that credit, including how account activity is measured and how the Reserve Banks control their exposure.^[1]

The account balance here belongs to a bank that holds its own Reserve Bank account. It is separate from the deposit balances the bank owes its customers. A customer’s large deposit does not establish that the bank has sufficient immediately usable reserves for every outgoing payment. For those balance-sheet relationships, see bank balance sheet management.

Banks can also obtain payment services through correspondents. Their commercial account and credit terms require a separate analysis; the article on correspondent banking and nostro/vostro accounts follows those relationships and their accounting. This article concentrates on the timing of the direct account holder’s Reserve Bank balance.

A Payment Ledger: Positive at Close, Negative Intraday

Suppose Cedar Bank, a fictional institution, starts the example at 08:00 Eastern Time with $20 million in its Reserve Bank account. Its outgoing payments are $35 million at 09:00, $25 million at 11:00 and $15 million at 15:00. Incoming payments are $10 million at 10:00, $40 million at 13:00 and $20 million at 16:00.

Assume no other transactions, interest, fees or changes in funding. Every listed outgoing payment executes with sufficient authorized daylight credit available when needed. Each event posts at the stated time; balances stay unchanged between events. The hourly presentation is a hypothetical teaching schedule, rather than the Federal Reserve’s full posting timetable.

The first outgoing payment takes the balance to $20 million − $35 million = −$15 million. At 11:00, the balance becomes −$5 million − $25 million = −$30 million, its lowest point. The final reconciliation is $20 million + $70 million − $75 million = $15 million.

Cedar therefore has a $30 million peak daylight overdraft despite ending positive. The ending balance answers whether the illustrated payments leave money in the account at close. It does not describe the largest intraday credit exposure.

Peak Overdraft vs. Maximum Net Payment Outflow

There are two related funding measurements. By 11:00, Cedar has sent $35 million + $25 million = $60 million and received $10 million. Its largest cumulative net payment outflow is therefore $60 million − $10 million = $50 million. The opening $20 million covers part of that need, leaving the $30 million account overdraft.

The Basel intraday-monitoring framework measures maximum daily liquidity usage from cumulative net payment flows, which show the change from the opening balance. That is different from simply reading the largest negative account balance. Central-bank intraday credit is not counted again as a payment receipt in that measure.^[5] In this fixed example, starting with $50 million would avoid an overdraft; starting with $20 million requires a $30 million bridge.

Federal Reserve Net Debit Caps

Correct arithmetic does not authorize credit. Part II of the Federal Reserve’s current published PSR policy, effective July 20, 2023, sets the framework for intraday credit in Reserve Bank accounts. A net debit cap limits an institution’s uncollateralized daylight overdraft capacity. It is calculated using the institution’s cap category and the policy’s capital measure.^[2]

A positive net debit cap requires regular access to the discount window and satisfaction of the applicable creditworthiness criteria. A Reserve Bank retains discretion over granting a cap or extending intraday credit. Charter-specific restrictions and the treatment of foreign banking organizations also matter; the table does not establish any particular bank’s approval.^[2]

Capital helps determine permitted exposure, but capital is not the same as cash available to settle a payment. The broader Basel capital requirements guide explains bank capital separately from this intraday-credit framework.

Collateral, Lendable Value and Maximum Capacity

Pledging collateral does not itself increase the net debit cap. It can cover a daylight overdraft for pricing purposes. Separately, an eligible institution may receive Reserve Bank approval for additional collateralized capacity, producing a maximum daylight overdraft capacity, or max cap.^[2]

The relevant collateral amount is its available lendable value after the Reserve Bank’s valuation and margins, allowing for existing encumbrances. Collateral already supporting an outstanding loan cannot also provide the same available coverage for daylight overdraft pricing. An owned security, an accepted pledge and a positive cash balance are different things.^[3]

Collateral eligibility and margins generally follow discount-window arrangements, subject to the policy’s provisions and Reserve Bank acceptance. The current official valuation page was updated September 8, 2026; actual values depend on the assets and applicable treatment.^[4] A single assumed haircut would be a poor substitute for verifying usable collateral before a payment deadline.

How Daylight Overdraft Fees Are Calculated

For institutions eligible for the ordinary PSR pricing treatment, the policy provides a zero fee on collateralized daylight overdrafts and a 50-basis-point annual rate on the uncollateralized portion. Fifty basis points means 0.50% per year, not a 0.50% charge on each payment or each day’s peak overdraft. Eligible charges are reduced by a $150 waiver per two-week reserve maintenance period.^[2]

The calculation uses end-of-minute uncovered overdrafts, averaged over a 24-hour business day of 1,440 minutes, and a 360-day year. The policy specifies that the effective daily rate is truncated to 0.0000138. Positive account balances do not offset negative observations in the average; they contribute zero. Fully collateralized negative balances also contribute zero.^[2][3] The word “daylight” is a policy label, not an instruction to average only during literal daylight hours.

At a given minute, the uncovered amount is the excess, if any, of the overdraft magnitude over available collateral coverage. The fee therefore depends on size, duration and collateral. Knowing the peak negative balance alone is insufficient to calculate it.

With sufficient qualifying collateral covering those same overdrafts throughout, the daylight-overdraft fee would be zero under ordinary eligible pricing. That does not eliminate the cost of obtaining, holding or mobilizing collateral, or other payment and funding expenses.

Institutions without regular discount-window access are subject to different restrictions and penalty treatment; the ordinary zero/50-basis-point pricing and waiver cannot simply be assumed. The official policy and its companion guidance control those cases.^[2][3]

Payment Queues and Liquidity-Saving Mechanisms

Managing a Bank’s Outgoing Queue

A bank’s payment-management process can distinguish obligations that must settle at a particular time from payments with more scheduling flexibility. Releasing a flexible payment after an expected receipt can reduce the funding bridge. Holding a critical payment too long can breach a deadline and deprive another institution of expected incoming liquidity.

That creates a tradeoff: using less of one’s own intraday liquidity can impose a delay elsewhere in the network. If many banks wait for incoming funds before sending, payment circulation can slow. The Basel monitoring framework therefore considers timing and payment throughput alongside funding amounts.^[5] A queue policy needs deadlines, priorities and escalation rules; reducing the measured overdraft is only one objective.

How Offsetting Can Reduce the Funding Needed

A liquidity-saving mechanism can examine multiple waiting instructions for offsets before releasing and settling them under the system’s rules. In an abstract hypothetical example, Bank A owes Bank B $100 million while B owes A $95 million. The gross instructions total $195 million, but if the rules permit simultaneous offsetting, $95 million can offset in each direction and the net funding movement is $100 million − $95 million = $5 million from A to B.

This arithmetic illustrates the benefit of matching obligations. It does not describe actual CHIPS funding requirements or reproduce its algorithm. Required prefunding, participant positions, payment priorities and the available set of instructions constrain what a real mechanism can release.

CHIPS, operated by The Clearing House, combines a queue and liquidity-saving algorithm with prefunding held at the Federal Reserve Bank of New York. It can release payments individually or with offsetting obligations. This reduces the funding needed to support payment activity; it does not mean CHIPS supplies a participant with Federal Reserve daylight credit.^[6]

CHIPS participant positions and releases are governed by its rules. A stored instruction differs from a released, settled payment, and payment release must satisfy the applicable position constraints. Funding the system and obtaining credit in a bank’s own Reserve Bank account are separate arrangements.^[7] For the broader payment-infrastructure landscape, see digital payment systems.

Stress Example: The Receipt Arrives Late

Return to Cedar Bank’s original ledger, with its $20 million opening balance and the same payment amounts. Change only one event: the $40 million incoming payment expected at 13:00 arrives at 16:00. Every outgoing payment still executes at its original time; assume Cedar has sufficient authorized credit to do so. At 16:00, the delayed $40 million and the original $20 million receipt arrive with no intervening debit.

The chart compares six hourly snapshots around the delay. Negative bars represent account overdrafts; zero is the boundary between a positive balance and intraday credit.

The late receipt deepens Cedar’s peak overdraft from $30 million to $45 million. At 15:00, the stressed balance is $20 million + $10 million − $35 million − $25 million − $15 million = −$45 million. Yet both paths reach $15 million at 16:00 and finish there. Identical daily totals can conceal different intraday capacity needs.

If sufficient credit were unavailable, Cedar could instead face a delayed or rejected outgoing payment; the chart assumes execution to expose the funding requirement. It does not predict how a Reserve Bank would handle a particular capacity breach.

If the Receipt Does Not Arrive Before Close

Now suppose that $40 million receipt is missing through the example’s close, with every other original event unchanged. The closing calculation becomes $20 million + $10 million + $20 million − $75 million = −$25 million. This introduces a closing funding problem as well as the intraday trough.

A negative Reserve Bank balance at the close of the business day is an overnight overdraft. The Federal Reserve expects institutions to avoid it and provides for penalty treatment and counseling. It is not an automatically approved discount-window loan or a routine rollover of daylight credit.^[1][2]

Stress can also reduce available resources: incoming payments may slow, credit lines may be withdrawn, or collateral value and eligibility may deteriorate. The Basel scenarios explicitly consider such changes.^[5] Their interaction connects intraday funding with broader liquidity risk management.

Intraday Liquidity vs. Overnight Funding and Solvency

These questions concern different constraints. Passing one test does not answer the others.

Likewise, the LCR and NSFR liquidity ratios address broader liquidity and funding horizons. A favorable ratio does not reconcile an 11:00 payment deadline with a 13:00 receipt. Intraday monitoring requires the timing information shown in the ledger, alongside the relevant usable resources and constraints.

How to Evaluate Intraday Liquidity

A useful treasury assessment connects payment operations with funding decisions:

1. Map the account and settlement events. Identify the legal entity, currency, system and actual posting or settlement timestamps. Separate confirmed receipts from forecasts.
2. Calculate both the account trough and cumulative net outflow. Reconcile opening funds, incoming payments, outgoing payments and closing funds. Use sufficiently granular data to capture the true peak.
3. Verify usable resources. Establish the actual reserve balance, approved credit capacity and accepted collateral available when required. Avoid counting collateral-backed capacity twice.
4. Protect deadlines. Identify time-specific obligations, queue priorities and the effect of delays on recipients. Escalate exceptions while there is still time to act.
5. Test contingencies. Delay a large receipt, remove a funding source and reduce collateral availability. Determine who can arrange replacement liquidity and how it can reach the necessary account.

Operational resilience belongs in that assessment: usable collateral and approved capacity may not help if instructions cannot be processed in time. The operational risk management guide covers the wider role of process, system and control failures. The Federal Reserve System article provides institutional background on the Reserve Banks.

Common Daylight Overdraft Mistakes

• Using the closing balance as the day’s liquidity test. Cedar ends positive while needing substantial credit earlier.
• Confusing net payment outflow with the account overdraft. Opening funds cover part of the cumulative outflow; the two peak measures need not match.
• Treating every account holder as eligible for ordinary credit. Access, creditworthiness, charter-specific rules and Reserve Bank discretion matter.
• Calling collateral cash. Check acceptance, lendable value, encumbrances and actual availability rather than adding a security’s face value to the account balance.
• Assuming a pledge automatically raises the cap. Fee coverage, the net debit cap and approved collateralized capacity have distinct roles.
• Charging the annual fee against the peak. Ordinary pricing uses the average uncovered end-of-minute exposure and the specified day-count conventions.
• Applying the $150 waiver every day. It is an eligible maintenance-period waiver.
• Equating liquidity saving with new credit. Offsetting payments changes the funding needed; it does not itself create a Reserve Bank lending commitment.

Limitations of a Simplified Intraday Model

Actual accounts contain many more events, governed by payment-specific posting rules. Hourly snapshots can miss a deeper gap between observations. The worked table captures its own peak only because all events are specified and nothing else occurs. Actual fees also need minute-level collateral coverage, not a single end-of-day collateral total.

Liquidity may sit in another currency, legal entity or system and take time to move. Credit can be conditional, collateral can lose value and forecasts can fail. A single normal day cannot determine a suitable buffer, a stress probability or a regulatory requirement. The Basel monitoring framework is an international supervisory reference; applicable U.S. requirements and institution-specific Reserve Bank arrangements must be checked separately.

Sources and Policy Notes

Official materials accessed November 11, 2026. All bank names, account balances, fee examples and offsetting amounts in the worked scenarios are hypothetical. The policy version dates below distinguish current published guidance from the research date.

1. Federal Reserve Board: Payment System Risk, current policy landing page, last updated July 21, 2023; Parts II and III overview and minute-by-minute monitoring.
2. Federal Reserve Policy on Payment System Risk, effective July 20, 2023; Part II.A-G on measurement, collateral, pricing, caps and monitoring, and Part III on overnight overdrafts.
3. Federal Reserve System: Overview of the PSR Policy on Intraday Credit, companion to the July 2023 policy; capacity, collateral availability, 24-hour measurement and maintenance-period fees. The article’s hypothetical fee calculation uses the published truncated daily rate, also specified in policy footnote 58.
4. Federal Reserve Discount Window: Collateral Valuation, updated September 8, 2026; assigned collateral values, valuation and margins. Actual Reserve Bank requirements control an individual arrangement.
5. Basel Committee: SRP50, Liquidity monitoring metrics, consolidated framework version effective December 15, 2019; paragraphs 50.47-50.51, 50.64-50.71 and 50.82-50.87. Used as an international monitoring reference, rather than a universal U.S. reporting rule.
6. The Clearing House: CHIPS Public Disclosure, October 2026; system design and operation, prefunding, liquidity-saving release and Standards VIII-IX.
7. The Clearing House: CHIPS Rules and Administrative Procedures, June 4, 2026; Rules 2, 12 and 13 on stored instructions, positions, release and settlement.