Advisors should handle Medicare IRMAA follow-up before clients receive confusing premium notices. Build an age-65 and retirement-income watchlist, review MAGI-sensitive events, document life-changing-event possibilities, coordinate tax questions, and keep reminders in the CRM so clients are not surprised by higher Part B or Part D premiums.
IRMAA is not just a Medicare premium footnote. It is a client-service moment that often appears after a Roth conversion, business sale, large capital gain, severance payment, retirement transition, or spouse's death. The client may blame Medicare, the tax return, or the advisor, depending on who explains the issue first.
The practical answer is a repeatable follow-up workflow. Advisors need a way to spot households before the notice arrives, explain what income Medicare is using, and route appeal or tax questions without making the client feel abandoned in a government form maze.
Medicare lists the 2026 standard Part B premium at $202.90.
SSA POMS describes IRMAA determinations as generally using tax data from two years prior.
SSA POMS shows IRMAA can move high-income beneficiaries to a larger share of program cost.
Start with the clients who will be surprised
The first IRMAA list is not every Medicare-age client. It is the households most likely to be surprised by a premium change. That includes clients approaching 65, clients retiring after high-income years, widows and widowers with a changed filing situation, business owners after a sale, clients taking large Roth conversions, and households with major capital gains.
Medicare.gov's cost page explains that people with higher income may pay more for Part B and Part D. The problem for advisors is timing. The client may see the premium increase long after the planning event that helped create the income spike.
Explain MAGI in plain language
Clients usually hear "income-related monthly adjustment amount" and tune out. The advisor needs a simpler explanation: Medicare looks at a version of income from a prior tax year, and certain planning decisions can push that number above a threshold. That does not mean the planning decision was wrong. It means the premium effect should be part of the review.
SSA POMS describes MAGI for IRMAA as adjusted gross income plus tax-exempt interest. That is a useful sentence for advisors because it connects the notice to real planning events: Roth conversions, gains, business income, municipal-bond interest, severance, and portfolio changes.
Example: a newly retired executive converts part of an IRA to a Roth in the first low-income year after work. The long-term tax plan may still make sense, but the client needs to know that Medicare premiums can react to the income number later. The service issue is not avoiding every premium increase. It is making sure the client hears about the tradeoff before the notice arrives.
Separate planning value from premium surprise
The advisor should not treat every IRMAA trigger as a planning mistake. A Roth conversion, capital gain realization, or business-exit event can still be beneficial. The issue is whether the household understood the premium side effect and whether the firm documented that conversation clearly.
SSA's IRMAA table guidance shows that higher-income beneficiaries can pay a larger share of Part B and Part D program cost. That makes the dollar impact visible enough to include in planning notes, especially when a client is comparing taxes, cash flow, and Medicare premiums in the same year.
Build a life-changing-event review path
Some IRMAA situations are not about ongoing income. They are about life changing faster than tax data. Retirement, marriage, divorce, death of a spouse, work reduction, work stoppage, loss of income-producing property, pension changes, and employer settlement payments can all change the story the client needs to tell Social Security.
Medicare's IRMAA notice page tells beneficiaries that the notice explains what information was used and what to do if it is wrong. Advisors should turn that into a service workflow: collect the notice, identify the income year used, ask whether a life-changing event occurred, and coordinate the documentation path with the client and tax professional.
- Ask clients to send the notice before calling Medicare or Social Security alone.
- Record the tax year used for the determination.
- Flag possible life-changing events and missing documentation.
- Coordinate tax questions with the CPA before the client submits forms.
- Set a CRM task to confirm whether the client received a revised determination.
Use age-65 onboarding to prevent confusion
Age-65 onboarding should include more than Medicare enrollment reminders. It should include a short premium-planning conversation for high-income households and recently retired clients. The advisor can explain that Medicare premiums are not always flat, that prior-year income matters, and that planning events may affect future premiums.
Medicare's 2026 cost publication lists the 2026 standard Part B premium at $202.90 and explains that people with higher income may pay more. That one official source gives the advisor a clean way to frame the issue without sounding like the firm is inventing a hidden fee.
The best client education is specific. "You are approaching Medicare, and your income history may affect premiums" is stronger than a generic reminder to review coverage. It tells the client why the advisor is bringing up the topic and why a tax return, retirement date, or income event belongs in the planning conversation.
Turn IRMAA into a CRM workflow
IRMAA follow-up should live in the CRM because the work crosses tax returns, client notices, planning notes, and deadlines. A spreadsheet can hold a list, but the CRM should carry ownership: who needs education, who sent a notice, who may have a life-changing event, who needs CPA coordination, and who is waiting for a revised determination.
For a small firm, the workflow can stay simple. Create tags for age-65 review, high-income Medicare review, notice received, life-changing event review, CPA coordination, and revised determination pending. Then review the list weekly during enrollment season and monthly the rest of the year.
Where a Bloomie helps without replacing advisor judgment
A Bloomie can keep the recurring operational pieces moving. It can maintain the age-65 and Medicare watchlist, prepare client education drafts, scan CRM notes for income events, create reminder tasks, summarize which households have notices, and prepare a weekly exception report for the advisor.
Bloomie Staffing works more like an AI staffing agency than another disconnected software subscription. In an IRMAA workflow, a reliable Bloomie handles the tracking, reminders, drafts, and status reporting while the advisor keeps the planning judgment, tax-professional coordination, and client relationship.
Questions Advisors Ask
When should advisors start Medicare IRMAA follow-up?
Advisors should start Medicare IRMAA follow-up before fall enrollment season, ideally when tax returns, retirement-income changes, Roth conversions, and age-65 transitions are being reviewed. The workflow is to flag affected households, identify life-changing events, prepare client education, and coordinate appeal or tax questions with the right professional.
What income does IRMAA use?
IRMAA generally uses modified adjusted gross income from a prior tax year. SSA POMS describes MAGI as adjusted gross income plus tax-exempt interest, which is why Roth conversions, capital gains, business exits, and one-time income events can matter for Medicare premium planning.
Can an AI employee help advisors with IRMAA follow-up?
Yes. A Bloomie can maintain the age-65 and Medicare-review list, prepare IRMAA education drafts, flag households with income events, create CRM reminders, and summarize appeal documentation status. The advisor still handles planning judgment, tax coordination, and client conversations.
Ready to make Medicare follow-up feel staffed?
Bloomie Staffing helps financial advisors hire reliable AI employees for age-65 tracking, IRMAA education drafts, CRM reminders, tax-question routing, client notice follow-up, and recurring service workflows.