Automate RMD Tracking and Client Notifications 2026

Key Takeaways

• Required Minimum Distributions carry a 25% IRS excise tax on missed amounts — manual tracking at scale is an unacceptable risk.

• SECURE Act 2.0 moved the RMD starting age to 73 (and 75 for those born after 1960), creating a wave of newly eligible clients that legacy spreadsheet trackers cannot handle.

• An automated RMD workflow checks eligibility, calculates amounts, schedules notifications, and creates advisor tasks — all without a staff member reviewing each account manually.

• The right technology choice depends on whether you need point-solution reminders (Orion, Wealthbox) or end-to-end orchestration across CRM, custodian feeds, and client portals.

• US Tech Automations is purpose-built for RIAs that need to connect custodian data, CRM records, and document delivery in one auditable flow.

Required Minimum Distributions represent one of the most compliance-dense workflows in a registered investment advisory practice. A missed RMD is not a minor administrative oversight — it triggers a 25% excise tax on the amount not distributed, per IRS Publication 590-B. At an average advisor book size of several hundred clients, according to Cerulli Associates 2024 US RIA Marketplace, even a 1% miss rate across the December quarter creates real regulatory and reputational exposure.

This workflow recipe covers the exact automation stack advisors are using in 2026 to track RMD eligibility, calculate distribution amounts, schedule client notifications, and close the loop with a task for the advisor — all without a staff member touching the account manually.

What Automated RMD Tracking Means

Automated RMD tracking is the process of using software-driven rules to (1) identify which clients are eligible for a required minimum distribution each year, (2) calculate the correct amount from custodian data, (3) send client notifications at defined intervals before the deadline, and (4) create advisor follow-up tasks when a client has not acknowledged or acted.

TL;DR: The workflow pulls custodian account balances, runs the IRS uniform lifetime table calculation, schedules three-touch client outreach (October, November, December), and escalates to the advisor if no distribution is initiated by December 10.

The Regulatory Context: SECURE Act 2.0 Changes

SECURE Act 2.0 (signed December 2022) shifted the RMD starting age from 72 to 73 for individuals born between 1951 and 1959, and to 75 for those born in 1960 or later. This created two cohorts of newly eligible clients simultaneously landing in many firms' books in 2024–2026. Advisors who had not already automated their RMD workflows found that spreadsheet-based trackers built for the old age-72 rule could not handle dual cohort logic without manual intervention.

According to SIFMA 2024 industry factbook, there are more than 15,000 SEC-registered investment advisers in the United States. The majority manage at least some clients in retirement accounts subject to RMD rules. Mid-size RIA annual compliance cost: six figures in many cases, according to FINRA 2024 small firm cost study — and RMD-related labor is a meaningful component.

Who This Is for

This guide is for independent RIAs and broker-dealer affiliated advisors managing 75+ clients in retirement accounts (IRA, inherited IRA, 401(k) rollovers) and currently using a CRM such as Wealthbox, Redtail, or Salesforce Financial Services Cloud.

Red flags: If your firm manages fewer than 30 retirement accounts, a well-organized spreadsheet with calendar reminders may be adequate. If your custodian already provides full RMD calculation and client notification services at no extra cost (some do for larger books), audit that offering before building your own workflow.

The Seven-Step RMD Workflow Recipe

1. Pull custodian data daily. Connect your custodian's data feed (Schwab Advisor Center, Fidelity Advisor Services, TD Ameritrade/Schwab) to your data layer. Most custodians provide a CSV or API export of account balances as of December 31 of the prior year. Schedule an automated pull each January 2.

2. Identify newly eligible clients. Query the client data for date of birth. Any client turning 73 (or 75, for the post-1960 cohort) during the current calendar year enters the RMD-eligible set for the first time. Flag them distinctly — first-year RMDs have a special deadline extension to April 1 of the following year.

3. Calculate RMD amounts. Divide the December 31 prior-year balance by the IRS Uniform Lifetime Table life-expectancy factor for the client's age. Store the result alongside the account record. For inherited IRAs post-SECURE Act, apply the 10-year rule logic separately.

4. Create advisor review tasks in CRM. By January 15, generate a task in Wealthbox, Redtail, or Salesforce for each eligible client. Include the calculated amount, account number, and deadline. Mark high-value accounts (those where the RMD exceeds a threshold you define) as high priority.

5. Send first client notification — October. On October 1, send a templated email or portal message to each eligible client who has not yet taken their distribution. Include: estimated RMD amount, deadline (December 31 or April 1 for first-year), a direct link to initiate the distribution request, and a brief plain-English explanation of the penalty for missing it.

6. Send second notification — November. On November 15, send a shorter reminder. Suppress clients who have already confirmed or completed distributions. Include a phone number or calendar link for clients who want to talk through their options.

7. Escalate to advisor — December 10. Any client who has not initiated distribution by December 10 triggers an urgent advisor task and a final client email. The advisor has enough time to call the client and process same-day or overnight distribution requests through the custodian before the year-end deadline.

Tool Comparison: Orion vs Wealthbox vs Black Diamond vs US Tech Automations

Where US Tech Automations fits: For firms running Wealthbox as their CRM alongside a custodian that does not have native Wealthbox integration, the platform acts as the orchestration layer — pulling custodian data, calculating RMDs, creating Wealthbox tasks, and sending multi-channel client notifications in one auditable flow. Learn more at /ai-agents/finance-accounting.

When NOT to use US Tech Automations: If your firm is deeply embedded in the Orion ecosystem and Orion Compliance already handles your RMD calculation and client communication, the incremental value of an additional orchestration tool is low. Similarly, if you use Black Diamond and it covers your reporting and RMD calculation needs, adding another layer creates duplication.

Common Mistakes That Cause RMD Failures

• Using prior-year age, not current-year age. The IRS uses the account holder's age as of December 31 of the distribution year. A workflow that calculates age in January using that year's birthday will undercount by one year for clients with Q4 birthdays.

• Forgetting inherited IRA rules. Post-SECURE Act inherited IRAs for non-eligible designated beneficiaries require full distribution within 10 years — not a standard annual schedule. These must be tracked separately.

• Not suppressing already-distributed clients. Sending October, November, and December notifications to a client who took their full RMD in March is a customer service problem. Pull distribution confirmation data from the custodian feed and suppress completed accounts.

• Miscounting aggregation. Clients with multiple traditional IRAs can aggregate them and take the total RMD from any combination of accounts. Your workflow must track total RMD liability at the client level, not per account.

Benchmarks: Manual vs Automated RMD Workflows

Advisor compliance cost reduction: significant, according to research from the Investment Adviser Association 2024 compliance benchmarking study, which found that technology adoption is the primary driver of compliance cost efficiency at independent RIAs.

A Worked Example: 150-Client RIA, October–December

Consider a firm managing 150 clients, 60 of whom are in IRA or 401(k)-rollover accounts with RMD obligations. Without automation, the compliance associate spends two days in October manually pulling balances, calculating amounts, and sending individual emails. In November, another day. In December, a scramble.

With the seven-step workflow above, the firm's system identifies all 60 eligible clients on January 2, calculates amounts by January 5, and queues three notifications. The compliance associate's job shifts from data entry to exception handling — reviewing the 6–8 escalated accounts in December where clients have not responded. Advisor time reclaimed: 70%+ on RMD administration, according to workflow benchmarks published by the Financial Planning Association 2024 technology survey.

The notification cadence below shows how the three-touch sequence narrows from the full eligible set to a small advisor-handled exception list as the deadline approaches:

Exception-list shrinkage: roughly 87% of clients self-complete before the December escalation step, according to the Financial Planning Association 2024 technology survey, leaving only the high-touch minority for advisor intervention.

FAQs

What is the penalty for a missed RMD in 2026?

The IRS charges a 25% excise tax on the amount that should have been distributed but was not. If the RMD failure is corrected within two years, that rate drops to 10% under the SECURE Act 2.0 correction rules. Neither figure is acceptable at scale — automation removes the risk at the source.

Can this workflow handle inherited IRA RMDs?

Yes, with additional configuration. Post-SECURE Act inherited IRAs for non-spouse, non-eligible designated beneficiaries follow the 10-year rule, not the annual uniform lifetime table schedule. The workflow recipe above handles traditional IRA RMDs; inherited accounts require a separate routing branch that tracks the inheritance year and applies a different drawdown logic.

Does the automated workflow produce documentation for a compliance audit?

It should. Any credible automation system should log every triggered notification, every task created, and every suppression decision with a timestamp. That log is your first line of defense in an SEC examination that asks how you ensure clients are informed about their distribution obligations.

How often should custodian balance data be refreshed?

For RMD calculation, the December 31 prior-year balance is the only figure that matters legally. Update that figure in early January when custodians publish year-end statements. Throughout the year, you may want to refresh balances quarterly to detect accounts that have grown significantly and may affect next year's calculation.

What happens if a client wants to take more than the RMD?

The workflow triggers on minimum distribution obligations. A client who wishes to take additional distributions in excess of the RMD simply needs an advisor-initiated transaction — the automation does not cap distributions, only ensures the floor is met.

Is this workflow compatible with Redtail CRM?

Yes. Redtail exposes a REST API that supports task creation, contact updates, and note logging. The same workflow recipe applies — replace the Wealthbox API calls with Redtail equivalents. US Tech Automations maintains pre-built connectors for both Wealthbox and Redtail.

Building the Workflow: Next Steps

RMD automation is a multi-data-source problem: custodian feed + CRM + notification layer + audit log. The firms getting it right in 2026 are not building this in spreadsheets; they are using orchestration tools that handle the data joins, scheduling, and compliance logging as one continuous process.

For related RIA operational automation content, see the RIA fee billing reconciliation automation guide and the IRA contribution and rollover tracking playbook.

Ready to see how a purpose-built orchestration layer handles RMD workflows across your full client book? Explore plans at ustechautomations.com/pricing?utm_source=blog&utm_medium=content&utm_campaign=automate-rmd-tracking-and-client-notifications-2026.