Series 51 study materials
Series 51 study resources

Seven Months of 529 Rollovers at One Branch

Series 51 · Put your knowledge to work in context.

All case studies

Seven Months of 529 Rollovers at One Branch

During a branch inspection you pull seven months of activity for rep Kline: 31 new 529 accounts, 18 funded by rollovers out of other firms' plans, 11 of them out of a single in-state plan into your firm's out-of-state advisor-sold plan. Median account size is $22,000, and each rollover generated a new sales charge. Seven rollovers involved the same two beneficiaries, all within 11 months. On two rollover forms the client signatures look identical to Kline's handwriting. In March a client gave Kline a $250 restaurant gift card 'for all the college help.' In April a client emailed that her 529 balance was down and 'nobody told me it could lose money'; the email sits in Kline's inbox, unlogged. The branch's written supervisory procedures contain a 529 section, but the designated municipal securities principal transferred out in February and no successor has been named.

1. Sort the findings into ordinary supervisory weaknesses and potential misconduct, and identify what each finding implicates.

Read the worked answer

Potential misconduct - escalate immediately

  • Signature anomalies. Two forms with signatures matching the rep's handwriting points to unauthorized signing or forgery. Preserve the originals, do not rely on a memorializing interview, pull every form Kline touched, contact the affected clients directly, and assess reporting obligations internally and to regulators. This outranks everything else on the list.
  • Seven rollovers for the same two beneficiaries inside 11 months. The once-per-12-month limitation on 529-to-529 rollovers applies per beneficiary and aggregates across all accounts and all plans. Repeated moves for the same beneficiary are not rollovers; they are distributions that make the earnings portion taxable and add a 10% additional tax. If Kline described them as rollovers, that is a material misstatement to the customer.

Supervisory and suitability problems

  • Rollover concentration. 18 of 31 accounts funded by replacement of existing 529s into a higher-cost out-of-state plan, at a median $22,000, requires documented customer-specific justification - loss of home-state tax benefits, added sales charges, and any surrender or CDSC on the surrendered plan. Suitability and fair-dealing standards apply, and a pattern this dense is a classic churning signal.
  • Gift card. A $250 gift exceeds the $100-per-person-per-year limit under the MSRB gifts rule and must not be retained.
  • Unlogged complaint. A written customer complaint about losses and disclosure is a supervisory record, not an inbox item.

Structural failure

  • No qualified principal in place since February: the procedures exist on paper but are not being executed.

2. What must happen with the gift card and the April email, and on what timeline?

Read the worked answer

Gift card

  • It cannot be kept. Return it to the client or, if that is impractical, dispose of it under firm policy (typically donation to charity) and record the disposition.
  • Log it in the firm's gift and entertainment log with date, value, giver and business relationship.
  • Treat it as a conflict-of-interest data point: a client paying a rep in cash-equivalent form shortly after being sold a rollover is exactly the fact pattern that turns a suitability review into an influence-peddling inquiry. Review that client's accounts closely.
  • Remind the rep in writing of the annual limit; a second instance is a disciplinary matter.

April email

  • Log it in the central complaint log on the day it is identified, not later. The delay itself is a finding.
  • The principal - or the interim designee - reviews it, not Kline. Confirm what the client was told about risk, and whether she received the required disclosure that 529 interests are municipal fund securities, are not FDIC-insured or bank-guaranteed, and can lose value, both in the plan disclosure document and on the confirmation.
  • Respond to the client in writing after the review, within the firm's stated complaint-response window; keep the response and the file.
  • Determine whether the matter is reportable under the firm's regulatory reporting obligations and whether it is part of a pattern with the other rollover clients.

Timeline: gift logged and returned, and complaint logged, within the same business day it is identified; substantive response after investigation, typically within days, never left to the rep.

3. The branch manager says the principal vacancy is a staffing issue, not a compliance issue. Respond, and outline remediation.

Read the worked answer

The vacancy is a compliance issue. Supervision rules require written supervisory procedures reasonably designed to achieve compliance and actual supervision by a qualified principal. Procedures nobody is executing are not procedures. Business written during a supervisory gap is unreviewed business, and the firm cannot show it met its obligations for that period.

Immediate (this week)

  1. Designate an interim qualified municipal securities principal with authority over the branch, or restrict 529 activity - no new 529 rollovers - until supervision is restored.
  2. Freeze and review every 529 account opened since February.
  3. Preserve and escalate the signature issue; suspend the rep's 529 authority pending the review.

Remediation (30–60 days)

  • Exception reporting built for 529 business, not bolted on from the equity desk: rollover frequency by rep and by beneficiary, a 12-month lookback per beneficiary across plans, share-class and breakpoint review, and cost comparison of the surrendered versus the purchased plan.
  • Mandatory documented rationale for every replacement of an existing 529.
  • A gift and entertainment log reviewed monthly at the branch level.
  • Complaint intake that bypasses the producing rep entirely.
  • Annual training on 529 mechanics (rollover limits, qualified expenses, state tax recapture) and on supervisory escalation.

The test at the end is not whether the procedures were rewritten; it is whether the exception reports show the pattern and whether someone acted on it.