When a garnishment order arrives against a customer who receives Social Security, veterans, railroad retirement or federal civil service benefits, the bank has one calculation to get right before anything else happens: the protected amount under 31 CFR Part 212. Get it right and the customer keeps access to exempt funds in the bank account while the creditor gets what state law allows. Get it wrong in one direction and you have frozen money a federal rule says is conclusively exempt. Get it wrong in the other and you have released funds the order reached.
The rule itself is short. The trouble is in the dates. This post works through the calculation the way a processor actually does it, with examples built on the rule's own illustrations in Appendix C to Part 212. If you need the wider workflow around the calculation (intake, holds, answers, remittance), see our overview of bank account garnishment procedures.
First, the inputs. The calculation only applies when the order does not carry a Notice of Right to Garnish Federal Benefits from the United States or a state child support enforcement agency (212.4). It only counts benefit payments as the rule defines them: payments from SSA, VA, RRB or OPM, made by direct deposit, with "XX" in positions 54 and 55 of the Company Entry Description field and originator status code "2" in the ACH batch header (212.3). A Social Security check deposited at the teller line does not count. A private pension direct deposit does not count. A benefit payment to a co-owner does count.
The rule defines the lookback period as 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 that month if the corresponding date does not exist (212.3).
Three things follow from that definition:
Here are the rule's own date examples, which every processor should be able to reproduce:
|
Order received |
Account review |
Period begins |
Period ends |
|
Wed., March 17 |
Wed., March 17 |
Tue., March 16 |
Sat., January 16 |
|
Wed., November 17 |
Thu., November 18 |
Wed., November 17 |
Fri., September 17 |
|
Tue., August 30 |
Thu., September 1 |
Wed., August 31 |
Wed., June 30 (no June 31) |
|
Fri., December 10 |
Tue., December 14 |
Mon., December 13 |
Wed., October 13 |
The third row is the one people miss. August 31 has no counterpart in June, so the period ends on June 30, the last date of that month. The same logic means a review on May 1 has a period beginning April 30 and ending on the last day of February, whether that is the 28th or the 29th.
Weekends and holidays do not move the dates. The period runs on calendar dates even when the end date falls on a Saturday, as in the first row.
Once you have the period, list every qualifying benefit payment that posted inside it. The rule speaks of payments posted between the beginning and ending dates of the lookback period; the Appendix C examples confirm that payments on the end date count and payments on the review date do not.
When building the list:
The protected amount is the lesser of (a) the sum of benefit payments in the lookback period or (b) the balance in the account when the review is performed (212.3).
Example A. A creditor's garnishment order for $6,000 is served on April 15. The bank performs the account review the same day.
Because a benefit payment posted in the lookback, the balance was above zero, a protected amount was established and there were funds above it, the bank must send the Part 212 notice within 3 business days of the review (212.7).
Notice what happened to the April 15 deposit. It is real Social Security money, but it falls outside the automatic calculation and sits in the $1,420 the bank may freeze. That matches Appendix C, Example 4. The customer's route to recover it is a state exemption claim against the creditor, which is exactly why the notice must explain the right to assert further exemptions.
Variation. Same facts, but the balance at review is $2,900. The protected amount is $2,900, the lesser figure. Nothing is frozen, and because there are no funds above the protected amount, no Part 212 notice is required. Appendix C, Example 1 reaches the same result on its own figures: a $1,000 balance against $2,500 of benefit payments, protected amount $1,000, no notice.
Example B. An order for $3,000 is received Monday, June 8. The bank completes the review on Wednesday, June 10, within two business days.
Sum of benefit payments in the lookback: $1,500 + $900 + $1,500 + $900 = $4,800.
Balance at review: $3,350.
Protected amount: lesser of $4,800 and $3,350 = $3,350. The entire balance is protected. Nothing is frozen and no notice is required.
Three lessons from this example:
A related point on intraday activity: the balance that matters is the balance when the review is performed. Appendix C, Example 3 shows a $1,000 cash withdrawal after the open of business but before the automated review ran; the bank used the reduced balance.
Separate accounts, separate reviews. If the debtor has a checking and a savings account, review each one and calculate a separate protected amount for each (212.5(f), 212.6(b)). Do not trace a benefit payment that landed in checking and was transferred to savings. The savings account gets protection only if benefit payments were deposited directly to it in its own lookback.
The same order served twice. The bank performs the account review only once, on first service of a given order. If the same order is served again, the bank does not repeat the review or take any other action on it (212.6(f)).
A new or different order. A second creditor's order, or a new order from the same creditor, gets a new and separate account review with its own lookback period anchored to its own review date (212.6(f)).
Example C. The Example A customer is served with a new order from a different creditor on July 20, reviewed that day.
The earlier review's numbers are not carried forward, and the $1,420 frozen under the April order plays no part in this calculation. The new review stands on its own, with its own window, its own sum and its own balance.
No continuing garnishment. After the review, the bank may not continually garnish later deposits or freeze funds that arrive afterward unless a new or different order is served (212.6(g)). In Example A, the May SSA deposit is not caught by the April order.
State rules that protect more. Where state law protects a higher amount, the bank must comply with both (212.9(b)). New York, for example, bars a bank from restraining $2,500 where exempt payments were directly deposited within 45 days before service (CPLR 5222(h)). Run the federal calculation, run the state calculation, and protect the higher result.
|
Mistake |
What the rule says |
Control |
|
Counting back from the date the order arrived |
Count back from the day before the review |
Record both dates on the worksheet |
|
Including a benefit posted on the review date |
It is outside the period |
Highlight review-date postings |
|
Excluding a payment on the far end date |
It is inside the period |
Second reviewer checks the end date |
|
Using "June 31" or "February 30" |
Use the last day of that month |
Date tool or calendar check |
|
Excluding a co-owner's benefits |
Count all benefit payments |
Pull every XX-coded credit, not only the debtor's |
|
Counting a deposited benefit check or private pension |
Only XX-coded direct deposits from SSA, VA, RRB, OPM |
Filter on ACH coding, not description text |
|
Tracing transfers between accounts |
Prohibited |
Review each account in isolation |
|
Repeating the review when the same order is re-served |
Review only once |
Check the log for prior service |
|
Freezing later deposits |
Not under Part 212 |
Hold limited to the amount set at review |
|
Fee taken from the protected amount |
Prohibited (212.6(h)) |
Fee posting blocked unless non-benefit funds arrived within five business days |
Two practical controls catch most of these. First, use a worksheet that shows the order-received date, review date, period start, period end, each benefit payment with posting date and agency, the sum, the balance at review and the protected amount. Second, have someone other than the processor check the dates and the sum before any hold is placed, at least until the processor has a clean track record.
Related deposit-operations issues come up in the same files. If a benefit recipient has died, Treasury may later reclaim payments under a separate process; see our post on Treasury reclamation. And because benefit payments arrive as ACH credits, staff should also understand where Regulation E applies to the account and where it does not; a garnishment hold is a legal-process action, not an electronic fund transfer error, but customers often raise both in the same call.
A worksheet helps, but processors need to understand why each date falls where it does so they can handle the cases the worksheet does not anticipate. The Federal Benefit Payment Garnishment Rule training teaches how to determine the lookback period, calculate the protected amount and the amount available for garnishment, and handle notices, continuing orders, fees and record retention. It is a practical fit for new legal-order processors and for the second reviewers who check their work.
Part 212 automatically protects the lesser of the account balance or the total federal benefit payments directly deposited during the two-month lookback period. Covered benefits are Social Security and SSI, VA benefits, railroad retirement and railroad unemployment benefits, and Civil Service and Federal Employees Retirement System benefits, delivered by direct deposit with the Treasury "XX" coding. Other funds may still be exempt under federal or state law, but the customer has to assert those exemptions against the creditor; the bank's automatic protection covers only the calculated protected amount.
Start from the date of the account review, not the date the order was served. The period begins on the day before the review and ends on the same calendar date two months earlier. If that date does not exist, such as June 31, use the last day of that month. A review on September 1 has a period from August 31 back to June 30. Weekends and holidays do not change the dates, and a benefit posted on the review date itself is not included.
Yes. The account review must be performed without regard to co-owners or payments to multiple beneficiaries. If the debtor's spouse receives VA benefits into a joint account, those deposits count toward the sum of benefit payments even though the spouse is not named in the order. The rule's own Appendix C example protects a full $7,000 balance where $4,000 of the benefit payments went to a co-owner rather than the debtor.
Withdrawals do not reduce the sum of benefit payments; they only reduce the balance. The protected amount is whichever is lower, so a large withdrawal often means the whole remaining balance is protected. The bank must not try to trace which dollars were spent. The balance that counts is the balance when the review is actually performed, which can include intraday activity before the review runs.
A new or different order against the same account holder requires a new, separate account review with its own lookback period. The same order served a second time does not; the bank performs the review only once per order. The bank also may not freeze funds deposited after a review unless it is served with a new or different order, so a single order cannot be used to keep capturing future deposits.
Not by the automatic Part 212 calculation. The rule only counts benefit payments made by direct deposit with the federal coding in the ACH batch header. A paper benefit check deposited at a teller window is not identifiable as a benefit payment in the account review. The funds may still be exempt from garnishment under federal law, and the customer can assert that exemption against the creditor or in court, but the bank does not include them in the protected amount.


