Every December, somewhere in your book, a client is sitting on an IRA distribution they haven’t taken yet. Maybe they turned 73 in March and nobody flagged it. Maybe the custodian’s calculation doesn’t match what your CRM thinks the account is worth. Maybe the reminder went out once, in October, and got buried under three other emails.
This is the part of the job that doesn’t show up on a fee statement but eats a real chunk of your team’s week. And when it goes wrong, the client doesn’t pay a small penalty. They pay 25% of the shortfall to the IRS, and then they call you asking how this happened.
Let’s look at what actually consumes the time here, and what it looks like when an AI agent handles the tracking, the math check, and the nagging.
The manual RMD process most firms are still running
If you sat down and mapped the current workflow for RMD season, it probably looks something like this.
Someone, usually a paraplanner or ops person, runs a report pulling clients by date of birth to find who’s turning 73 (or hits their required distribution year under the SECURE 2.0 rules) in the current tax year. That report gets cross-checked against a spreadsheet, because the CRM’s birthday field and the actual custodian account records don’t always agree on which accounts are subject to RMDs. Inherited IRAs have their own rules. Still-working exceptions for employer plans have theirs.
Once the list is built, someone has to pull the prior year-end balance from each custodian, run the calculation against the IRS Uniform Lifetime Table, and check it against whatever the custodian’s own portal says the required amount is. These two numbers should match. They don’t always. Custodians make errors too, and if your firm signed off on a wrong number, that’s on you in a compliance review.
Then comes the reminder cycle. A single email in Q3 is not a notification system, it’s a hope. Firms doing this well are sending three or four touches across the year, starting in Q1 so clients have time to plan tax withholding, then following up as December approaches, then escalating for anyone who still hasn’t acted by early December.
For a firm with 150-300 IRA holders over 73, this is easily 5 to 10 hours a week during peak season for one person, spread across pulling reports, checking math, and chasing emails. It’s not complex work. It’s just relentless, detail-heavy, and unforgiving if you miss someone.
What this actually costs the firm
Most owners underestimate this because the cost doesn’t show up as one line item. It’s spread across paraplanner hours, adviser time spent on “why didn’t I get reminded” calls, and the occasional client who misses a deadline and now needs a corrective distribution conversation you’d rather not have.
Across the firms we work with in this size range, RMD tracking failures, missed reminders, and the rework they generate typically sit inside the same $70,000 to $200,000 annual leakage band we see for manual back-office work generally at firms your size. That’s not one disaster. It’s dozens of small gaps, each costing a few hours of skilled time or a client’s confidence.
If you want a clearer read on where this shows up specifically in your firm, that’s exactly what the AI audit for financial advisory firms is built to surface. It’s not a generic efficiency review. It’s a look at where your team’s hours are actually going against distribution deadlines, meeting prep, and document turnaround.
What an automated RMD notification system looks like end to end
Here’s how we’d build this as a working agent rather than a report you still have to act on manually.
Step 1: Age and account detection. The agent runs continuously against your CRM and custodian feeds, not once a quarter. It flags any client crossing an RMD trigger age, including the nuances around still-working exceptions, inherited IRA rules, and the first-year delay option that lets clients push their first distribution into April of the following year. It also flags accounts that were missed in prior manual reviews, which happens more often than firms expect.
Step 2: Calculation and verification. Rather than trusting one source, the agent pulls the prior year-end balance from the custodian, calculates the required distribution against the correct IRS table for that client’s situation, and cross-checks it against the custodian’s own stated RMD figure. If the two numbers disagree by more than a rounding difference, it flags the discrepancy for a human to resolve instead of letting either number go unchecked. This is the step most manual processes skip because it’s tedious, and it’s the step that actually prevents wrong distributions.
Step 3: Multi-touch client communication. Instead of a single reminder, the agent runs a sequenced outreach: an early-year notice with the calculated amount and suggested timing for tax planning, a mid-year check-in, and a firm reminder as the deadline approaches. Each touch is personalized with the client’s actual dollar figure, not a generic “you may have an RMD due” template. For clients who haven’t acted by early December, it escalates to the adviser directly with a one-line summary instead of a spreadsheet row.
Step 4: Documentation and audit trail. Every calculation, every reminder sent, and every client response gets logged automatically. When a compliance reviewer or an auditor asks “how do you know Mrs. Patterson took her RMD on time,” you have a timestamped record instead of a memory.
The result is that nobody on your team is manually building a birthday report in February, and nobody is discovering in late November that a client’s account got missed entirely.
Where this fits into the bigger picture
RMD notifications are one piece of a larger pattern we see across advisory firms. The manual, detail-heavy work that eats adviser and paraplanner time isn’t limited to distributions. It shows up in meeting prep, in compliance documentation, in onboarding.
We build this as part of a broader set of operational agents under Omni ops. The Meeting Prep Agent pulls portfolio data, recent communications, and goal progress into a one-page brief before every client meeting, which matters a lot when that meeting is the same conversation about an upcoming RMD. The Advice Document Agent drafts the SOAs, ROAs, and file notes that document the advice given around that distribution, built from the meeting transcript and your firm’s own compliance template rather than a blank page. Together with an RMD notification workflow, these agents cover the full arc from “client turns 73” to “distribution taken, documented, and filed” without a paraplanner manually stitching each piece together.
If your firm is also feeling the drag on the front end, the Client Onboarding Agent runs guided fact-finds and collects KYC documentation for new households, which matters because IRA rollover clients often arrive mid-life with RMD questions already on the table. Getting that data captured cleanly the first time means the RMD tracking system has accurate birthdate and account data from day one instead of inheriting gaps from a rushed onboarding.
You can see how these pieces connect in the broader library of guides we publish on operational automation for advisory practices, and in the insights we share on where firms this size are actually losing time.
Why “set it up and check back in December” doesn’t work
A few firms try to solve this with a one-time spreadsheet build rather than a live system. It works for about one cycle. Then a client’s birthdate gets corrected in the CRM but not the tracking sheet, or a new custodian relationship gets added and nobody updates the pull, or the person who built the spreadsheet leaves and takes the institutional knowledge with them.
The agent-based approach avoids this because it’s tied directly to your live data sources, not a snapshot someone exported in January. When a custodian relationship changes, when a client’s account type shifts from traditional to inherited, when SECURE 2.0’s age thresholds get adjusted again by regulation, the system updates against the source data rather than requiring someone to remember to rebuild the report.
That reliability is the actual value here. Not that it’s faster, though it is. It’s that it removes the single point of failure that comes from one person’s memory and one spreadsheet’s accuracy.
Getting a clear read on your own numbers
Most firm owners we talk to have a rough sense that RMD season is a grind, but they haven’t actually quantified what it costs in hours or what the exposure looks like if a distribution gets missed. That’s worth 60 minutes to find out precisely.
An Omni Audit is built for exactly this. No deck, no sales pitch dressed up as a workshop. We sit down with you or your ops lead for 60 minutes, look at how your firm currently tracks RMDs, meeting prep, and documentation, and hand you three concrete outputs: where the hours are actually going, what a working agent would look like for your specific workflow, and a realistic estimate of what it’s worth to fix. You walk away with something usable whether you engage us further or not.
If you want to see that mapped against your own client list and custodian setup, book a 60-min Omni Audit and bring whatever tracking process you’re using today, even if it’s just a spreadsheet. We’ll work with what you have.
The real question to ask your team this week
Before RMD season peaks again, ask whoever owns this process a simple question: how would we know if we missed someone? If the answer involves “we’d probably catch it” rather than a specific system check, that’s your signal.
The firms that get this right aren’t smarter about tax rules than everyone else. They’ve just removed the dependency on one person remembering to run a report and one spreadsheet staying accurate all year. An agent that watches ages, checks the math against custodian data, and sends reminders on a schedule doesn’t forget, doesn’t get pulled onto a bigger client fire in November, and doesn’t leave the firm taking institutional knowledge with it.
If you’re curious what this specific workflow would look like mapped against your own book of IRA clients, see Omni for financial advisory firms and get the specifics rather than a general estimate. And if you’d rather talk it through directly, book my Omni Audit and we’ll go through your current process together, no deck required.
You can also browse more on how firms in this range are automating the operational side of advice delivery over on our blog, where we cover the practical mechanics behind agents like these rather than just the theory.