RMDs During an Advisor Transition: What Advisors Need to Watch - Continuity

Why RMDs become risky during a move

In a stable year, RMDs are mostly a scheduling and paperwork task. In a transition year, you add operational noise:

Accounts are opening and validating registrations
Transfers may move in batches (and cash may arrive later)
System history and cost basis (where applicable) may lag
Banking features and distribution instructions may need rebuilding

That’s why “we’ll handle it later” is a bad plan. RMDs need a named owner and a decision path.

If you want the broader explanation of batching and residuals: Why Advisor Assets Don’t Always Transfer All at Once.

The 4 RMD questions you must answer before the transfer is in motion

Is an RMD required this year for this account? (and is it partial or full?)
How much has already been taken? (and from which account source?)
Where will the remaining distribution be processed? (delivering or receiving platform)
How will the proceeds leave the account? (ACH link, check, wire, recurring withdrawal setup)

These questions sound basic, but they prevent the two most common outcomes: missing the distribution or taking it twice because nobody could verify what already happened.

Where RMDs go wrong during transitions (common patterns)

RMD responsibility isn’t assigned

In many practices, “someone” tracks RMDs. In a transition, “someone” becomes “no one.” Put a name on it, even if it’s temporary.

Distribution history is hard to verify mid-move

If access is changing or statements are in different systems, it can be difficult to confirm whether an RMD was partially taken earlier in the year. That uncertainty causes delays—or duplicate actions.

Cash availability doesn’t match the calendar

The account may transfer in-kind, but the cash needed for a distribution can lag due to settlement, residual sweeps, or waiting on banking setup. Clients then feel “stuck” even when assets arrived.

Banking/distribution instructions are not rebuilt early

If the client expects ACH distributions or checkwriting, those features may need re-establishment at the new platform. If you wait until the week the RMD is due, you’ll be in trouble.

Inherited IRAs add another layer of sensitivity

Inherited IRAs can have specific distribution rules and titling requirements. If those accounts are part of the move, they should be treated as a separate lane.

RMD risk table: issue → impact → clean mitigation

This table is built for ops reality. The mitigation is usually simple—if you do it early.

RMDs during an advisor transition: what to watch and how to prevent problems
Risk	What it looks like	Why it happens	Best mitigation
Unknown RMD status	Confusion “Did we already take it?”	History spread across systems; access changes mid-year	Verify YTD distributions before the move; document the result in the household record
RMD due while assets are in transit	Timing account can’t distribute when needed	Transfer batching, settlement delays, residual cash lags	Plan distribution timing; if needed, process at delivering firm before transfer or stage the transfer
Banking link not ready	Stalled proceeds can’t be sent to client	ACH/checkwriting setup requires verification	Rebuild banking features early and test; don’t wait until the due date
Duplicate distribution	Error client takes RMD twice	Unclear owner; poor documentation of what was already taken	Assign one owner + one source of truth; confirm before initiating any new withdrawal
Inherited IRA handling errors	Rework paperwork delays or special rules missed	Inherited accounts treated like standard IRAs	Segment inherited IRAs into a separate workflow lane and track them closely
Client expectation gap	Stress “Why can’t I get my distribution?”	Clients assume distributions work immediately post-transfer	Set expectation: assets may arrive before distribution/banking is enabled; provide a bridge plan

A practical RMD workflow for transition year accounts

Here’s a workflow that works across most moves, regardless of platform specifics:

Flag all RMD-eligible households during pre-move data prep
Confirm RMD status: required? amount? already taken YTD?
Pick the distribution venue: deliver-side before transfer, or receive-side after assets arrive
Confirm cash path: where will cash be available and when?
Rebuild payout instructions: ACH link, check, wire, recurring distribution setup
Track completion like a deliverable (date, amount, confirmation)

This fits neatly into readiness and tracking workflows: Transition Readiness Assessment and Account Transfer Tracking.

How to talk about RMDs with clients during a move

Clients don’t need every operational detail. They do need clarity. A simple message that works:

We’re tracking your RMD as a separate deliverable during the transition.
We’ll confirm what has already been taken before we move the account.
If timing is tight, we’ll use a bridge plan so you’re not waiting on a transfer for your distribution.

To be honest, clients relax quickly when they realize the distribution deadline has an owner and a plan.

Need RMD tracking built into your transition plan?

Continuity supports operational transition execution and completion-phase controls, including year-of-move retirement tracking and distribution dependencies. If your book includes a meaningful number of retirement households, it’s worth treating RMDs as a planned workstream, not a last-minute task.

Explore: Cost Basis & RMD Cleanup • Completion Phase • Transition Execution

Frequently Asked Questions

Should the RMD be taken before or after the account transfers?

It depends on timing and platform readiness. If the distribution is due soon or banking instructions won’t be ready quickly on the new platform, taking it before the transfer can reduce risk. If timing is flexible, it can be handled after assets arrive—so long as it’s tracked and owned.

What’s the most common RMD mistake during a move?

Not verifying what has already been taken year-to-date. That creates either a missed distribution or an accidental duplicate distribution because the team is guessing.

Do transfer delays affect RMD deadlines?

The deadline is independent of the transfer process. If the account is in motion near a required distribution date, you need a bridge plan and clear ownership so timing doesn’t slip.

Why do banking features matter for RMDs?

Because even if assets arrive, the distribution still needs a payout path (ACH, check, wire). Those features often require setup and verification at the receiving platform, which can take time.

Are inherited IRAs more complicated for RMD tracking?

They can be. Inherited IRAs often require more sensitive titling and documentation and may have different distribution requirements. Treat them as a separate workflow lane during the transition.

What’s a clean definition of “done” for an RMD in the transition year?

Verified requirement, verified amount already taken, distribution executed from the chosen venue, proceeds delivered via the agreed method, and confirmation documented in the household record.

Conclusion

RMDs during a transition are manageable when they’re treated like a deliverable: confirmed requirement, confirmed status, chosen venue, payout path ready, and tracked to completion. The biggest risk is letting RMD tracking become “later” while the move is in motion.

For more advisor transition FAQs and operational explanations, start here: Continuity Advisor Transition FAQ.

For authoritative guidance on required minimum distributions, the IRS RMD guidance is the best external reference: IRS: FAQs on Required Minimum Distributions (RMDs) .