Imagine moving $50,000 from one IRA to another, depositing every dollar back within 60 days, and still ending up with a fully taxable distribution plus a 10% penalty. No money went missing. No deadline was blown. You simply did it twice in twelve months — and the second move was disqualified the moment the cash hit your account.
That is the trap inside the IRA once-per-year rollover rule. It is one of the most misunderstood corners of retirement planning, and the version most investors think they know was rewritten by a single Tax Court case more than a decade ago. If your mental model still says "one rollover per IRA per year," it is wrong, and the mistake is expensive.
What a "Rollover" Actually Means
The word "rollover" gets used loosely, which is exactly why people get burned. In IRA terms, a 60-day rollover is a very specific transaction:
- You take a distribution from your IRA. The custodian sends you the money — a check in your name, or a deposit into your personal bank account.
- You then have 60 calendar days to redeposit that money into an IRA (the same one or a different one).
- If you make the deadline, the IRS treats the round trip as if the distribution never happened. No tax, no penalty.
This is sometimes called an indirect rollover because the money passes through your hands. And because it passes through your hands, it is the only type of IRA-to-IRA move subject to the once-per-year limit.
Contrast that with a trustee-to-trustee transfer, where the money goes directly from one custodian to another and never touches your bank account. You request the move, and Custodian A sends the funds straight to Custodian B. You never receive a check made out to you personally.
That distinction — money in your hands versus money moving between institutions — is the single most important concept in this entire article. Get it right and the once-per-year rule almost never affects you.
The Rule, As It Actually Works Today
Here is the current rule, stated plainly:
You may complete only one IRA-to-IRA 60-day rollover in any rolling 12-month period, counting all of your IRAs together as if they were a single account.
Three details inside that sentence trip people up.
"One rollover" — not one per account. You could own six IRAs at four different custodians. You still get exactly one 60-day rollover among all of them.
"All of your IRAs together." The aggregation is total. Traditional IRAs, Roth IRAs, SEP IRAs, and SIMPLE IRAs are all thrown into the same bucket. A 60-day rollover from your Roth IRA uses up the same single allowance that would have covered your traditional IRA. There is no separate Roth budget.
"Rolling 12-month period" — not a calendar year. The clock is not the tax year. It runs 365 days from the date you received the first distribution. If you took a distribution on March 1, you cannot start another 60-day rollover until the following March 1 — even if a new January arrives in between.
One more boundary worth stating: the limit is per person, not per household. Spouses each get their own single rollover, but you cannot "borrow" your spouse's allowance for your own IRA.
How One Tax Court Case Changed Everything
For years, IRS Publication 590 — the agency's own guidance — said the once-per-year limit applied separately to each IRA. Investors and advisors relied on that language. It meant a person with several IRAs could chain multiple 60-day rollovers in the same year, one per account.
Then came Bobrow v. Commissioner (T.C. Memo 2014-21). The taxpayer in that case used a sequence of distributions from two of his own IRAs — and his wife's — to effectively borrow money interest-free for months at a time, redepositing each amount just inside its 60-day window. He treated each IRA's rollover as independent, exactly as the IRS publication suggested.
The Tax Court disagreed. It ruled that the once-per-year limit in the tax code applies on an aggregated basis across all of a taxpayer's IRAs — not account by account. The court reasoned that because the Internal Revenue Code already treats a person's IRAs as a single pool for other income-tax purposes, the same aggregation should govern the rollover limit.
The result was striking: the Tax Court's own decision contradicted the IRS's published guidance. The IRS accepted the ruling, withdrew the old account-by-account interpretation, and announced it would enforce the aggregated rule for distributions occurring on or after January 1, 2015, giving taxpayers a transition period.
So if you learned the "one per account" version, you did not learn it wrong — you learned it outdated. The rule changed, and it changed because of one aggressive strategy that pushed the old interpretation past its breaking point.
What Does NOT Count Toward the Limit
This is the good news, and it is substantial. The once-per-year rule is far narrower than its reputation. The following moves are completely exempt — you can do them as often as you like:
- Trustee-to-trustee transfers. Because the money never reaches you, a direct transfer is not a "rollover" for this purpose at all. You can transfer IRA funds between custodians ten times a year if you want. This is the workaround, and it is the entire game.
- Roth conversions. Converting a traditional IRA to a Roth IRA is a taxable event, but it does not consume your once-per-year rollover. Convert as often as makes sense.
- Rollovers from an employer plan to an IRA. Moving money out of a 401(k), 403(b), or similar workplace plan into an IRA is not an IRA-to-IRA rollover. It does not count, and it does not block a separate IRA-to-IRA rollover.
- Rollovers from an IRA to an employer plan. The reverse direction is also exempt.
- Direct rollovers within employer plans. Plan-to-plan moves are outside the rule entirely.
Notice the pattern: the once-per-year limit applies to exactly one transaction type — an indirect, 60-day, IRA-to-IRA rollover where you personally receive the cash. Everything else is fair game.
The Cost of Getting It Wrong
Suppose you do a second 60-day IRA-to-IRA rollover inside the same 12 months. The redeposit is invalid as a rollover. The IRS does not give you a do-over, and — critically — it cannot waive this rule even when it can waive other rollover errors. Here is the damage:
The distribution becomes fully taxable. The amount you pulled out is ordinary income for the year. A $50,000 distribution adds $50,000 to your taxable income.
A 10% early-withdrawal penalty may apply. If you are under 59½ and no exception fits, add 10% of the distribution on top of the income tax.
The redeposit becomes an excess contribution. The money you put back was not a valid rollover, so the IRS treats it as a regular contribution. It almost certainly exceeds your annual contribution limit. Excess contributions carry a 6% excise tax — and that 6% is charged every year the excess (and its earnings) stays in the account, until you remove it.
To avoid the recurring 6% tax, you generally must withdraw the excess contribution, plus any earnings on it, by your tax-filing deadline. Untangling this is unpleasant, and it often requires a tax professional.
That is the full picture: one income-tax hit, one possible 10% penalty, and a 6% excise tax that compounds annually if you do not clean it up fast.
The 60-Day Deadline Is a Separate Trap
The once-per-year limit and the 60-day clock are two different rules, and you can violate either one independently.
If you miss the 60-day redeposit window, the distribution is taxable for the same reasons above. But here there is some mercy. The IRS will waive a missed 60-day deadline in genuine hardship situations — and it offers a self-certification process so you do not have to apply for a private letter ruling. Qualifying reasons include serious illness, death in the family, disability, incarceration, a financial institution's error, a misplaced (and never cashed) distribution check, postal error, severe damage to your home, and similar circumstances beyond your control.
Self-certification is a written statement to your IRA custodian asserting that you qualify. It lets you complete the late rollover — but it is not an automatic IRS blessing. If you are later audited and the IRS finds the reason did not qualify, the taxes and penalties come back.
And remember the hard limit: the IRS can forgive a late rollover. It cannot forgive a second rollover that breaks the once-per-year rule. Hardship does not help you there.
How to Stay Safe: A Practical Playbook
The strategy here is almost embarrassingly simple.
Default to trustee-to-trustee transfers for every IRA move. When you consolidate accounts, switch custodians, or chase a better fund lineup, instruct the institutions to move the money directly. Never ask for a check made out to you. A direct transfer sidesteps the once-per-year rule, sidesteps the 60-day clock, and sidesteps the entire problem. There is no annual limit on direct transfers.
Treat the 60-day rollover as a last resort. The only real reason to take a distribution into your own hands is short-term access to the cash — and that is precisely the strategy Bobrow shut down. If you do not need the money in your pocket, do not route it through your pocket.
If you must do a 60-day rollover, do exactly one, and log the date. Write down the date you received the distribution. You cannot begin another IRA-to-IRA 60-day rollover until 365 days later.
Watch the custodian default. Some custodians, when you close an account, will mail you a check by default. That single check can quietly consume your one allowance for the year — or break it, if you have already used it. Always specify a direct transfer in writing.
Check the 1099-R. Distributions are reported on Form 1099-R, and your redeposits should be reflected so the rollover is not taxed. Reconcile these forms when they arrive rather than discovering a problem during an audit.
Keep Your Financial Records Clear from Day One
Rollover mistakes are rarely about bad intentions — they are about lost track of dates, custodian checks that arrived unannounced, and a fuzzy memory of "did I already do one this year?" The defense is good record-keeping: a dated log of every distribution and redeposit, every transfer, every account move.
Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in, and a permanent, version-controlled trail you can search the moment a question comes up. Whether you are tracking retirement accounts, transfers, or your whole financial picture, get started for free and see why developers and finance professionals are switching to plain-text accounting.