# Regulation CC Funds Availability and the AI Deposit-Servicing Agent: Next-Day, Second-Day, Case-by-Case Holds, and the Notice the Rule Insists On

*July 10, 2026 · 15 min read · Ramkumar Venkataraman*

> Regulation CC at 12 CFR 229 is the rule every branch teller learns and every AI deposit-servicing agent has to learn too, because the customer calling about a check that has not cleared is asking a question the rule already answered. The next-day and second-day defaults, the four exception-hold categories, the case-by-case rule for larger deposits, and the disclosure timing all sit inside the agent's first conversation with the customer. The architecture we run so the agent's answer is the right one on the day the customer asks, and the bank's file supports it later.

## The Question the Bank Answers Wrong Most Often

The most common inbound call a retail deposit-servicing team receives is some version of "why is my check on hold." The customer deposited a check yesterday, expected the funds today, and does not have them. The teller or CSR reads the hold reason from a screen, the customer disputes it, the CSR escalates, and the conversation ends with a partial answer that neither the customer nor the bank's file will thank later. The rule the customer's deposit is being held under is [Regulation CC at 12 CFR 229](https://www.ecfr.gov/current/title-12/chapter-II/subchapter-A/part-229), the implementing regulation for the [Expedited Funds Availability Act of 1987](https://www.federalreserve.gov/paymentsystems/regcc-about.htm) and one of the most operationally consequential rules in retail deposit servicing. The rule was written for a paper-check world with a partial nod to electronic clearing, has been amended twice (most recently the 2018 [electronic-check amendments](https://www.federalreserve.gov/newsevents/pressreleases/bcreg20180627a.htm) that extended the rule to electronic items), and remains the substantive standard the bank's hold decisions are read against.

We build the AI agent that handles retail-deposit inbound calls and chat for banks and credit unions. Reg CC comes up on a meaningful share of those conversations, and the architecture below is the one we run so the agent's explanation is accurate, so the exception-hold decision the bank made is defensible in the file, and so the customer's problem is either solved on the first call or routed to the person who can solve it with the right information already assembled.

## The Availability Schedule the Rule Actually Sets

The default availability rules at [1026.229.10 through 229.12](https://www.consumerfinance.gov/rules-policy/regulations/1005/) sit on top of two categories: next-day availability for specific low-risk items and second-business-day availability for most other local checks. Cash deposits at the teller line are available on the day of deposit for cash withdrawal and on the next business day for other purposes under 229.10(a). Electronic payments credited to the account are available on the day the bank receives the funds under 229.10(b). Wire transfers are same-day. Direct deposits are same-day.

The next-day availability rules at [229.10(c)](https://www.ecfr.gov/current/title-12/chapter-II/subchapter-A/part-229/subpart-B/section-229.10) cover Treasury checks, U.S. Postal Service money orders, Federal Reserve Bank and Federal Home Loan Bank checks, state and local government checks (if the depositor is a customer of the bank and the check is deposited in person to a bank employee), cashier's checks and certified checks (same in-person condition applies), and the first $275 of any other check under the "$275 rule" at [229.10(c)(1)(vii)](https://www.ecfr.gov/current/title-12/chapter-II/subchapter-A/part-229/subpart-B/section-229.10). The $275 figure has been in place since the 2020 amendments moved it up from $225, and further inflation adjustments are pending under the Dodd-Frank inflation-adjustment mechanism.

The second-business-day availability rule at [229.12](https://www.ecfr.gov/current/title-12/chapter-II/subchapter-A/part-229/subpart-B/section-229.12) is the general rule for local checks (which is now effectively all checks, since the elimination of the non-local check distinction in 2010). A $5,000 personal check deposited into a checking account on Monday is generally available on Wednesday for withdrawal, with $275 available on Tuesday under the next-day carve-out.

The agent has to compute the specific availability for a specific deposit type against these rules and give the customer the accurate answer the first time. "Two business days" is not a sufficient answer when the customer's account is showing a five-day hold; the discrepancy is either an exception hold the customer needs to understand, or an error the bank needs to correct.

## The Four Exception Hold Categories the Rule Permits

The bank can extend the default availability under [229.13](https://www.ecfr.gov/current/title-12/chapter-II/subchapter-A/part-229/subpart-B/section-229.13) for specific enumerated reasons, and the extension has to be disclosed to the customer at the time the hold is placed. The categories are narrower than the branch's default vocabulary of "we always hold checks" would suggest.

The first category is the large-deposit hold at 229.13(b): a check that, together with other same-day deposits, exceeds $6,725 (the current figure, adjusted from $5,525 in the 2020 amendments). The bank can hold the amount above $6,725 for a reasonable period of time, generally understood as up to five additional business days beyond the default. The customer's first $6,725 is available under the default rule; only the excess is held.

The second is the new-account hold at 229.13(a) for accounts open less than 30 calendar days. The bank can extend availability on cash and check deposits during the first 30 days to up to nine business days for the amount above $6,725 and to next-day for the first $6,725 of specific low-risk items (Treasury checks, wire transfers, on-us checks). The new-account rule ties together several restrictions that catch customers off-guard when they open an account and expect the funds they deposit to be available on the schedule the marketing material implied.

The third is the redeposited-check hold at 229.13(c), applicable when a check has been returned unpaid and is being redeposited. The bank can hold the redeposit for a reasonable period of time on the theory that the underlying instrument has already failed once and the risk of the redeposit failing again is elevated.

The fourth is the repeated-overdraft hold at 229.13(d), applicable when the depositor's account has been overdrawn on six or more banking days in the prior six months or on two or more banking days in the prior six months where the overdraft was $6,725 or more. The bank can extend availability on the depositor's check deposits during a period when the overdraft pattern is present.

The fifth category (five, not four, if the counting is being honest about the rule's structure) is the reasonable-cause-to-doubt-collectibility hold at 229.13(e), which the rule allows when the bank has "reasonable cause to believe the check is uncollectible." The reasonable-cause standard is the subjective one in the rule; it requires facts specific to the check or the depositor and cannot be based on race, national origin, or the class of the depositor. The [Consumer Financial Protection Bureau's supervisory findings](https://www.consumerfinance.gov/data-research/research-reports/supervisory-highlights-issue-30-summer-2023/) have repeatedly cited banks for reasonable-cause holds imposed on checks that did not have specific facts supporting the doubt, and the bank's file has to show the specific facts if the hold is later reviewed.

The agent's classification of the specific hold reason against the rule's five categories is the first analytical step in the conversation. The customer whose hold was placed under 229.13(e) needs to hear a different explanation than the customer whose hold was placed under 229.13(b), because the underlying reasoning and the reasonable-period-of-time analysis are different.

## The Notice the Rule Requires and the Timing the Bank Often Misses

The exception-hold notice at [229.13(g)](https://www.ecfr.gov/current/title-12/chapter-II/subchapter-A/part-229/subpart-B/section-229.13) has to be given to the customer at the time of the deposit if the person depositing the item is present, and it has to be mailed no later than the business day after the deposit if the depositor is not present. The notice has to state the specific reason for the hold, the amount of the deposit being held, the day the funds will be available, and the account number.

The rule at [229.13(g)(1)(ii)](https://www.ecfr.gov/current/title-12/chapter-II/subchapter-A/part-229/subpart-B/section-229.13) permits the notice to be delayed past the deposit day for a case-by-case reasonable-cause hold under 229.13(e), where the bank did not know at the deposit moment that the hold would be imposed but decided later based on facts learned about the check. The delayed notice is still a per-hold notice, and it has to be sent no later than the business day following the day the bank made the decision to hold. The genuinely "one-time" or blanket exception notice at 229.13(g)(2) is a separate provision and is available only for nonconsumer accounts, and only for the large-deposit and redeposited-check categories at 229.13(b) and (c); it is not available for consumer accounts and it is not available for reasonable-cause holds under 229.13(e). A consumer reasonable-cause hold requires a per-hold notice with the specific reason, amount, and availability date on every hold the bank imposes.

The timing on the notice is what banks most commonly get wrong. A branch teller who did not deliver the notice at deposit and a back-office team that mails the notice three days later has produced a compliant hold under 229.13 with a non-compliant notice under 229.13(g). The bank's exception-hold exposure is not just the substantive question of whether the hold was permitted; it is the procedural question of whether the notice was delivered on time.

The agent's contribution to the notice mechanics is to confirm at the customer's inbound call that the notice was delivered on the schedule the rule requires, and to identify the timing gap if the notice was not delivered as required. The customer whose call is the first they have heard about the hold is a customer whose notice may not have been delivered, and the file has to reflect the gap. The agent's identification of the gap routes the case for the bank's compliance team to review the notice's timing and, if the timing failed, to remediate.

## The Case-by-Case Reasonable-Cause Hold and the Fact File

The reasonable-cause hold at 229.13(e) is the category the bank uses most often on larger checks and the category that produces the most customer disputes. The rule requires the bank to have reasonable cause to believe the check is uncollectible, and the reasonable-cause standard has to be supported by specific facts. The [CFPB and FDIC supervisory highlights](https://www.fdic.gov/regulations/examinations/supervisory/insights/) have documented findings against banks that imposed reasonable-cause holds based on the check amount alone, the depositor's demographic characteristics, or the check-issuer's location, without specific facts supporting the doubt.

The specific facts the rule accepts include the check being drawn on an account with a history of returned items, the check being significantly larger than the depositor's typical activity, the check bearing signs of alteration or lacking normal endorsements, the drawer being on a watchlist for check fraud, or the specific check-issuing bank having a known operational disruption. The facts have to be documented in the file at the time of the hold, and the file has to support the reasonable-cause conclusion the bank drew from the facts.

The agent's inbound call about a reasonable-cause hold reads the file's factual support and explains it to the customer to the extent the explanation is consistent with the bank's fraud-monitoring posture (the bank cannot always disclose the specific fraud indicator the hold was based on, but it can characterize the type of doubt). The customer whose reasonable-cause hold is based on a specific fact the bank can share gets an explanation. The customer whose reasonable-cause hold is not supported by a specific fact in the file gets a case routed to the bank's compliance team for review, and the file's deficiency is caught pre-exam rather than at exam.

## The Payment Order Interaction and Kited Check Recovery

A check hold's release is not the end of the bank's exposure. The rule at [229.30](https://www.ecfr.gov/current/title-12/chapter-II/subchapter-A/part-229/subpart-C/section-229.30) allocates the bank's warranties on returned checks, and the [UCC Article 4](https://www.law.cornell.edu/ucc/4) provisions on final settlement govern the bank's ability to recover from an account that has withdrawn against a check that later returns unpaid. A customer who withdraws the full amount of a deposited check on day three under the default rule, whose check returns unpaid on day six, is a customer whose account is now in a negative position and whose recovery is a matter of the account balance the bank can chase and the customer's willingness to make the account whole.

The agent's coordination between the funds-availability rule and the returned-check process is that the customer whose check has been returned unpaid receives a clear communication about the return, the resulting overdraft, and the collection process the bank is running. The [UCC 4-215](https://www.law.cornell.edu/ucc/4/4-215) treatment of final settlement and the bank's charge-back rights under 4-214 are the operational basis for the collection, and the customer's understanding of what happened between the deposit and the return is often the difference between a customer who cooperates with the recovery and a customer who disputes it.

The agent's file for the deposit-and-return sequence records the deposit, the availability under the rule, the withdrawal, the return of the check, the notification to the customer, and the recovery activity. The bank's exposure to a returned check is meaningfully reduced by the file's completeness, because the eventual collection or write-off decision is based on the file's specifics.

## The Overdraft-Fee Interaction and What the Customer Actually Owes

The customer who withdrew against a check that later returned is a customer whose account is now overdrawn, and the bank's overdraft-fee schedule applies to the resulting negative balance. The [CFPB's various rulemakings on overdraft fees](https://www.consumerfinance.gov/rules-policy/regulations/1005/17/) and the [Federal Reserve's Regulation E overdraft opt-in rules at 12 CFR 1005.17](https://www.consumerfinance.gov/rules-policy/regulations/1005/17/) apply to the treatment of the negative balance and to the specific fees the bank can charge. The overdraft opt-in rules apply to one-time debit card transactions and ATM withdrawals; the check-deposit-and-withdrawal pattern is not the same as the opt-in-covered transaction, but the fee schedule the bank applies to the resulting overdraft is subject to the bank's disclosure and consistency requirements.

The [2024 CFPB rules on overdraft fees for very large banks](https://www.consumerfinance.gov/rules-policy/final-rules/overdraft-lending-very-large-financial-institutions/) that were substantially undone by the Congressional Review Act in 2025 have left the specific fee structure and disclosure regime for larger institutions somewhat unsettled, but the substantive requirement that overdraft fees be disclosed under [Reg DD](https://www.consumerfinance.gov/rules-policy/regulations/1030/) and be consistent with the account terms remains. The agent's explanation of the overdraft fee to the customer references the specific fee schedule, the specific transactions that produced the negative balance, and the specific options the customer has for curing the balance.

The failure mode we see is the customer whose account has been assessed multiple overdraft fees from a single returned check, whose call to the bank does not produce an accurate accounting of the fees, and whose eventual complaint to the CFPB includes the fee-cascade issue in addition to the underlying hold-and-return issue. The agent's ability to walk the customer through the specific fee calculation and to identify any fee that was assessed in error is a customer-service and a compliance-risk mitigation simultaneously.

## The Case-by-Case Rule for Deposits Above the Threshold

Section 229.13(b)'s large-deposit hold applies to the excess above $6,725, and the operational question banks have to answer is how they decide whether to hold the excess. The case-by-case approach at 229.13(h) permits the bank to apply the exception on a case-by-case basis rather than as a blanket policy on all large deposits. The case-by-case approach requires the bank to document its decision in the file and, per the [Federal Reserve Board's official commentary](https://www.federalreserve.gov/paymentsystems/regcc-about.htm), to have a bank policy that guides when the exception is invoked.

The customer whose $9,500 payroll check from a Fortune 500 employer is held under 229.13(b) is likely to dispute the hold, because the underlying check risk is low. The bank that has a policy of applying 229.13(b) to every deposit above $6,725 is a bank whose policy may be more restrictive than necessary and whose case-by-case decisions on the excess should reflect that the underlying risk on many of the checks is minimal.

The agent's inbound call reviews the specific check details (drawer, drawer bank, deposit history) and either explains the specific facts supporting the hold or identifies the case as one where the case-by-case decision should be reconsidered. The bank's escalation team gets the case with the facts already reviewed and can either confirm the hold with better documentation or release the hold with the customer's day changed for the better.

## The New-Account Rule and the First-30-Day Conversation

New-account holds are the second most common source of customer disputes on Reg CC, and they are also the disputes that the bank's marketing team gets pulled into most often. A customer who opened an account based on a "same-day availability" ad and whose first deposit is being held for nine business days is a customer whose experience contradicts the marketing promise, and the bank's Reg CC posture and its UDAAP posture on the marketing claim are both implicated.

The agent's opening conversation with a new-account customer explains the specific availability rules for the account's first 30 days and the specific carve-outs (Treasury checks and on-us checks with next-day availability on the first $6,725) that apply during the initial period. The customer who understands the rule at the account-opening moment is a customer whose first deposit does not produce a surprise, and the bank's marketing on same-day-availability claims is checked against the rule's actual mechanics.

We have run analyses for retail banks where the new-account complaint rate on Reg CC drops meaningfully when the agent proactively discusses the rule at account opening rather than reactively when the customer's first check is held. The customer-experience improvement and the compliance-risk reduction are the same operational improvement.

## The State-Law Overlay and the Where-It-Applies Question

Regulation CC's federal floor is the base availability rule; state laws that provide more favorable availability to the customer supersede the federal rule under the [227.20 preemption principle](https://www.federalreserve.gov/paymentsystems/regcc-about.htm). New York's Article 3-A and California's Financial Code Section 866 have historically provided more favorable availability for specific check types, and several states have provisions that require faster availability than the federal default for state-issued checks.

The agent's intake for a customer's deposit is aware of the state where the account is domiciled and applies the more-favorable-of-federal-or-state rule to the customer's availability. The customer in a state whose law provides next-day availability on a check type that federal law provides second-day availability on gets the next-day treatment, and the bank's file records the specific state-law basis for the treatment.

The state-law overlay is the aspect of the funds-availability program that changes most slowly, but it is also the aspect where the bank's automated systems are least likely to be up to date. The agent's ability to check the state-law rule for the specific customer's state is a specific operational advantage the branch teller may not have.

## The Electronic Deposit and Mobile Capture Coverage

The 2018 amendments extended Regulation CC to electronic checks and electronically-created items, which now dominate the deposit-volume mix through mobile-deposit-capture channels. The rule's availability schedule applies to electronic items with the same next-day and second-business-day defaults, with the specific mobile-deposit-capture cut-off times at [229.19(a)(5)](https://www.ecfr.gov/current/title-12/chapter-II/subchapter-A/part-229/subpart-B/section-229.19) determining the "business day of deposit" for schedule purposes.

The cut-off time is the operational lever. A bank whose mobile-deposit cut-off is 6 pm treats a deposit at 6:15 pm as being on the next business day for availability purposes, and the customer whose deposit at 6:15 pm on Thursday expected Monday availability is going to receive Tuesday availability. The cut-off time has to be disclosed at [229.19(a)(5)(ii)](https://www.ecfr.gov/current/title-12/chapter-II/subchapter-A/part-229/subpart-B/section-229.19), and the bank whose disclosure does not clearly identify the cut-off time or whose mobile app allows deposits past the cut-off without warning is a bank whose customer disputes will focus on the disclosure gap.

The agent's mobile-deposit conversation confirms the cut-off time for the customer's specific deposit and explains the resulting availability. The customer's understanding of the cut-off is what produces the deposit-timing behavior the bank prefers, and the agent's proactive explanation is what produces the understanding.

## The Audit File Per Held Check

The audit file per held check that the examiner will ask for includes the deposit's timestamp, the check's specific classification against the availability rule, the hold reason if a hold was placed, the specific exception category if the hold was under 229.13, the factual support if the hold was under 229.13(e), the notice's delivery timestamp and method, the customer's inquiries if any and the responses provided, and the release of the hold when it occurred with the specific date.

The file's completeness supports the bank's exam posture on Reg CC compliance and supports the bank's UDAAP posture on the specific customer's experience. The file's incompleteness is the single largest risk to the exception-hold decisions the bank makes, because the reasonable-cause hold whose fact file cannot be reconstructed is a hold the examiner will read as not reasonably supported.

The agent's contribution to the file is that every customer inquiry produces a record with the customer's specific question, the agent's specific answer, and any escalation the agent triggered. The file assembles across the customer's inquiries and across the bank's operational decisions on the deposit, and the file is available for review by the examiner or by the customer's inquiry under Reg CC's disclosure requirements at [229.15](https://www.ecfr.gov/current/title-12/chapter-II/subchapter-A/part-229/subpart-B/section-229.15).

## The Failure Mode We Engineer Against

The pattern that produces the worst Reg CC outcomes is the bank whose deposit-servicing system was configured to a blanket hold policy years ago, whose customer-facing explanations are cut-and-paste text that does not identify the specific hold reason, and whose customer complaints escalate to the CFPB or the state banking agency without the bank's compliance team having visibility into the pattern. The individual holds are technically compliant against 229.13; the aggregate pattern is the operational posture the examiner and the CFPB will read as UDAAP-adjacent.

The architecture we run against this is that every hold produces a customer-facing communication with the specific hold reason, the specific rule reference, and the specific availability date, and every customer inquiry is classified for the operational-quality dashboard the bank's deposit-servicing team reviews. A pattern of customer disputes on a specific hold category (large-deposit holds on customers with strong deposit histories, reasonable-cause holds without file support, new-account holds that produced a marketing complaint) is a pattern the team can address before the pattern becomes an examination finding.

The customer inquiries in this model are a source of operational-quality data that improves the bank's Reg CC posture for all customers, not just for the customers who called. The bank whose inquiry volume feeds the quality process is the bank whose exam posture on Reg CC and whose UDAAP posture on deposit servicing is stronger over time.

## The Honest Read

Regulation CC is the rule every teller learns and every AI agent has to learn too, because the rule's specifics are what the customer's frustration is being measured against. The rule's mechanics are dense, the exception-hold decisions require documented factual support, and the notice timing is a compliance requirement banks fail routinely. The AI agent's role in the deposit-servicing operation is to be the layer that explains the specific hold accurately, catches the bank's own compliance gaps on the notice and the fact file, and produces the operational-quality signal that improves the bank's Reg CC posture over time.

We build the agent for that role at retail banks and credit unions. The rule is old, the operational reality has shifted to electronic and mobile channels, and the customer's expectation has moved faster than the rule's amendments. The gap between the rule's mechanics and the customer's expectation is the space the agent works in, and the agent's job is to make the answer accurate for the customer and defensible for the bank in the same conversation.

We have written separately on the [Regulation E error-resolution rules for electronic transfers](/blog/regulation-e-error-resolution-ai-agents-dispute-intake), on the [UCC Article 4A wire-verification architecture](/blog/ucc-article-4a-wire-fraud-ai-verification-commercially-reasonable), and on the [Reg X escrow-analysis rules for mortgage servicing](/blog/reg-x-1024-17-escrow-analysis-ai-mortgage-servicing) that share the same operational discipline the Reg CC program requires. The deposit-servicing agent that runs across all of these with the same architecture is the agent whose contribution to the bank's operational posture compounds across the customer's relationship with the institution.

---

_Source: [https://seiright.com/blog/regulation-cc-funds-availability-ai-deposit-servicing-agent](https://seiright.com/blog/regulation-cc-funds-availability-ai-deposit-servicing-agent) · Sei AI_