
On Tuesday, October 6, a transfer from a savings account to checking comes back rejected. The app still shows a $6,000 balance, but the available figure next to it reads $3,000. A letter mailed later that week explains the rest. A debt buyer holding an old credit card balance won a court judgment and served a garnishment order on the bank on Friday, October 2, and the bank froze part of the account.
The $3,000 left available is not a courtesy. Two Social Security direct deposits of $1,500, one on Wednesday, August 12 and one on Wednesday, September 9, landed in that account during the two months before the bank reviewed it. A federal rule told the bank to leave that much alone, and the account holder did nothing to set it in motion.
So can a creditor garnish a savings account that holds Social Security? A creditor with a court order can reach the account, yes. What it cannot reach under 31 CFR Part 212 is the “protected amount”: the lesser of the federal benefits direct deposited during a two-month lookback window or the balance on the day the bank reviews the account. The bank calculates that figure itself, within two business days, and leaves it available. Money above the line can be frozen under state law, and some debts, including back taxes and child support, follow different rules.
Who can send a garnishment order
The scope in section 212.2 covers benefit payments from four agencies: SSA, VA, the Railroad Retirement Board and the Office of Personnel Management. The rule binds every financial institution, which section 212.3 defines as “a bank, savings association, credit union, or other entity chartered under Federal or State law to engage in the business of banking.” An online high-yield savings account and a credit union share account sit under the same rule.
The same section defines a garnishment order as “a writ, order, notice, summons, judgment, levy or similar written instruction issued by a court, a State or State agency, a municipality or municipal corporation, or a State child support enforcement agency.” A private creditor with a judgment gets its order through a court, so the ordinary debt collection case sits squarely inside that list. The procedures start when a bank is served with an order.
Before anything else, section 212.4(a) has the bank check, “no later than two business days following receipt of the order,” whether “the United States or a State child support enforcement agency has attached or included a Notice of Right to Garnish Federal Benefits.” If that notice is attached, the bank “shall follow its otherwise customary procedures for handling the order” and skips the protections. A credit card judgment carries no such notice, which is why the account in the opening kept $3,000.
The two-business-day account review
Section 212.5(a) sets the clock. The bank “shall perform an account review … No later than two business days following receipt of (A) the order, and (B) sufficient information from the creditor that initiated the order to determine whether the debtor is an account holder, if such information is not already included in the order.”
The review is “the process of examining deposits in an account to determine if a benefit agency has deposited a benefit payment into the account during the lookback period.” If no benefit payment arrived in the window, the bank handles the order under its normal state-law procedures. If one did, section 212.6 takes over.
Section 212.5(d) keeps the review mechanical. The bank performs it “without consideration for any other attributes of the account or the garnishment order,” including:
- “The presence of other funds, from whatever source, that may be commingled in the account with funds from a benefit payment”
- “The existence of a co-owner on the account”
- “Instructions to the contrary in the order”
- “The nature of the debt or obligation underlying the order”
Commingling matters most for a savings account. Interest, a tax refund and transfers from a paycheck do not dilute the protection. And under 212.5(e) the review comes “prior to taking any other actions related to the garnishment order that may affect funds in the account.”
Where the two-month lookback starts and ends
“Lookback period means the two month period that begins on the date preceding the date of account review and ends on the corresponding date of the month two months earlier, or on the last date of the month two months earlier if the corresponding date does not exist.”
The window counts backward. Applied to the opening scenario:
| Step | Date |
|---|---|
| Order received | Friday, October 2, 2026 |
| Account review, second business day after receipt | Tuesday, October 6, 2026 |
| Lookback begins, the date preceding review | Monday, October 5, 2026 |
| Lookback ends, the corresponding date two months earlier | Wednesday, August 5, 2026 |
| Benefit deposits inside the window | August 12 and September 9, $1,500 each |
The next deposit, on October 14, arrives after the review and plays no part. Two payments totaling $3,000 go into the calculation.
Appendix C to Part 212 works through the edge cases. An account reviewed on Thursday, September 1 has a lookback running from August 31 back to June 30, “since June 31 does not exist to correspond with August 31.” In one protected-amount example, a benefit payment posted on the review date itself is left out of the sum. In another, the window catches three monthly payments, on December 1, November 1 and October 1, because both ends land on payment dates. The count is not always two.
The protected amount in three balances
“Protected amount means the lesser of the sum of all benefit payments posted to an account between the close of business on the beginning date of the lookback period and the open of business on the ending date of the lookback period, or the balance in an account when the account review is performed.”
Two numbers, and the smaller one wins. Hold the benefit total at $3,000 and change only the balance:
| Balance at review | Benefits in lookback | Protected amount | Left for state-law freeze | Notice under 212.7 |
|---|---|---|---|---|
| $6,000 | $3,000 | $3,000 | $3,000 | Required |
| $3,000 | $3,000 | $3,000 | $0 | Not required |
| $1,000 | $3,000 | $1,000 | $0 | Not required |
The first row is the opening scenario: $3,000 protected, and state law governs the other $3,000. In the second row the balance equals the benefit total, so the whole account is protected. The third row is where “lesser of” cuts the other way, though it costs nothing that day, because the protection cannot exceed what is in the account. Appendix C’s first example uses the same pattern, a $1,000 balance against $2,500 in benefit deposits, and sets the protected amount at $1,000.
The notice column comes from section 212.7(a). A notice is required only when benefits arrived in the lookback, a protected amount was set, and “There are funds in the account in excess of the protected amount.” No excess, no letter.
The part that asks nothing of the account holder is section 212.6(a). The bank “shall immediately calculate and establish the protected amount,” must give “full and customary access to the protected amount, which the financial institution shall not freeze in response to the garnishment order,” and “An account holder shall have no requirement to assert any right of garnishment exemption prior to accessing the protected amount in the account.” Paragraph (c) adds that the amount “shall be conclusively considered to be exempt from garnishment under law.”
State law can set a higher figure. Section 212.9(b) says a state requirement to protect benefits “at a higher protected amount than is required under this part is not inconsistent with this part if the financial institution can comply with both this part and the State law requirement.” The federal number works as a floor.
What stays frozen, and the fee limit
For “any funds in an account in excess of the protected amount,” 212.6(d) sends the bank back to “its otherwise customary procedures for handling garnishment orders, including the freezing of funds.” What happens to that money next depends on the state’s garnishment process.
Long-term savers get caught here. Picture a retiree who has let Social Security build up in one savings account for years and now holds $20,000, all of it originally benefit money. The review still counts only the two-month window. At $1,500 a month, $3,000 is protected automatically and $17,000 can be frozen until an exemption is claimed. Section 212.8(a) preserves the right “to assert against a creditor a further exemption from garnishment for funds in excess of the protected amount,” and the notice must explain how, “by completing exemption claim forms, contacting the court of jurisdiction, or contacting the creditor, as customarily applicable for a given jurisdiction.” Older benefit money can still be claimed. It just is not automatic.
Money deposited after the review is treated differently. Under 212.6(g), the bank “shall not continually garnish amounts deposited or credited to the account following the date of account review, and shall take no action to freeze any funds subsequently deposited or credited, unless the institution is served with a new or different garnishment order.” The October 14 deposit in the example is outside the October 2 order.
On fees, 212.6(h) is direct: “The financial institution may not charge or collect a garnishment fee against a protected amount.” It leaves one opening. The bank “may charge or collect a garnishment fee up to five business days after the account review if funds other than a benefit payment are deposited to the account within this period, provided that the fee may not exceed the amount of the non-benefit deposited funds.” Move $200 from checking into the garnished account on Thursday, October 8, and a fee of up to $200 can come out of that deposit.
One safe-harbor line deserves a warning. Section 212.10(d)(3) protects a bank for honoring “an account holder’s express written instruction,” dated and given after the order was served, “to use an otherwise protected amount to satisfy the order.” A signed instruction can hand protected money to the creditor. Nothing requires signing one.
Benefits the automatic rule does not see
Section 212.3 defines a benefit payment by its electronic coding: a federal benefit “paid by direct deposit” carrying specific codes in the “Batch Header Record of the direct deposit entry.” That definition has two consequences for savers.
Paper checks do not register. A benefit check deposited at a branch or by phone camera is not a direct deposit, so the automatic review cannot see it. Any exemption for that money has to be claimed, the same way as the older funds described above.
Transfers between accounts are not traced. Section 212.5(f) says the bank “shall not trace the movement of funds between accounts by attempting to associate funds from a benefit payment deposited into one account with amounts subsequently transferred to another account.” If Social Security lands in checking and $3,000 moves to a high-yield savings account, the savings account’s review shows no benefit deposit, and that order is handled under customary procedures. Checking gets its own review, capped by its own balance.
The CFPB’s page on federal benefits and debt collectors, last updated January 29, 2024, lists a wider set of protected federal payments, including Supplemental Security Income, servicemember pay, federal student aid and FEMA assistance, and sums up the account rule this way: “Two months’ worth of benefits are protected and remain in your account for you to use.”
Debts that can still reach Social Security
Part 212 settles the question for an ordinary creditor with a court order. It does not make benefits untouchable. The same CFPB page says Social Security and SSDI “can sometimes be garnished to pay money you owe to the government, such as back taxes or federal student loans, and money you owe for child or spousal support.” SSI stands apart: the page says it is protected from garnishment “even to pay a government debt or child or spousal support.”
| Source of the order | Automatic two-month protection |
|---|---|
| Court judgment for a private creditor, such as credit card or medical debt | Yes, when benefits were direct deposited in the lookback |
| United States, with a Notice of Right to Garnish Federal Benefits attached | No, customary procedures apply |
| State child support enforcement agency, with that notice attached | No, customary procedures apply |
| IRS bank levy | A separate federal process, covered next |
The IRS bank levy and its 21-day wait
The IRS page on bank levies states: “When the levy is on a bank account, the Internal Revenue Code (IRC) provides a 21-day waiting period for complying with the levy. The waiting period is intended to allow you time to contact the IRS and arrange to pay the tax or notify the IRS of errors in the levy.”
The timing is tied to delivery: “In the case of a bank levy, funds in the account are frozen as of the date and time the levy is received.” And: “Normally, the levy does not affect funds you add to your bank account after the date of the levy.”
A levy reaches the bank on a Monday while the balance is $6,000. That $6,000 is frozen at the moment of receipt, and compliance waits 21 days. A $1,500 deposit the following Wednesday is normally outside the levy. The 21 days are the window to contact the IRS, arrange payment or point out an error.
If an erroneous levy triggers a bank fee, the same page points to Form 8546, Claim for Reimbursement of Bank Charges, with conditions: “The IRS must have caused the error,” the taxpayer must not have contributed “to continuing or compounding the error,” and before the levy the taxpayer must have “responded timely to contacts and given information requested.” The page does not address benefit deposits, and since the CFPB lists back taxes among debts that can reach Social Security, the two-month cushion should not be assumed for a tax debt.
When your own bank is the creditor
Some savers hold a credit card at the same bank. Can the bank sweep savings to cover a missed payment? For card debt, Regulation Z section 1026.12(d)(1) says no: “A card issuer may not take any action, either before or after termination of credit card privileges, to offset a cardholder’s indebtedness arising from a consumer credit transaction under the relevant credit card plan against funds of the cardholder held on deposit with the card issuer.”
With $4,000 in savings and a card $2,500 past due at the same bank, the bank cannot move $2,500 out of savings to pay the card, and closing the card does not change that.
Paragraph (d)(2) preserves the issuer’s right, when “the same procedure is constitutionally available to creditors generally,” to “Obtain or enforce a consensual security interest in the funds; attach or otherwise levy upon the funds; or obtain or enforce a court order relating to the funds.” The bank can sue like anyone else, and a court-issued garnishment order is exactly what Part 212 covers. Paragraph (d)(3) allows a plan “authorized in writing by the cardholder” under which the issuer “may periodically deduct all or part of the cardholder’s credit card debt from a deposit account held with the card issuer.” That is autopay, and it rests on written consent.
The protection is narrow. Its words reach debt “under the relevant credit card plan.” An auto loan or personal installment loan at the same bank is not described by that sentence, and 1026.12(d) does not speak to it. For those debts, the deposit agreement is the document to read, and setoff is the word to search for.
After the freeze: a checklist
- Read the 212.7 notice. It must go out “within 3 business days from the date of account review” and state the date the order was served, the protected amount, any amount frozen, any garnishment fee and the creditor’s name. A review on Tuesday, October 6 means a notice sent by Friday, October 9.
- Use the protected amount normally. The Appendix A model notice says: “There is nothing else that you need to do to make sure that the ‘protected amount’ is safe.”
- Do not sign away protected money. A dated written instruction to apply it to the order is one the bank may honor.
- Claim the rest in writing. The CFPB’s advice is to “notify the court, the bank, and the person or business that is garnishing your account immediately in writing, and seek help from a lawyer.” Statements showing each direct deposit are the evidence.
- Keep benefit deposits where they land. Transfers are not traced, so benefits moved elsewhere lose the automatic calculation. Separating money by purpose is the same logic behind where to keep an emergency fund.
- Ask why no protected amount was set. Either no benefit deposit appeared in the lookback, or a Notice of Right to Garnish Federal Benefits came with the order. The answer decides which rules apply.
- Time the next few deposits. For an IRS levy, use the 21 days before compliance. After a garnishment review, non-benefit money moved into the account within five business days can still absorb a fee.
The rule protects the latest two months of benefits automatically and everything older only on request. For a saver whose account is mostly years of accumulated Social Security, that gap decides how much of the balance stays usable while the dispute runs.
Run your own numbers instead: your balance, the APY on offer, and the period you plan to hold.
Compound interest calculator
Runs in your browser. Nothing you type is sent anywhere or saved.
| Year | You put in | Interest earned | Balance |
|---|
Interest compounds monthly from the APY you enter. Because APY already reflects compounding, this converts it to the equivalent monthly rate rather than dividing by twelve — dividing by twelve and then compounding would overstate the result. Figures are before tax; deposit interest is generally taxable as ordinary income.