SurgeTK Release Notes - September 19, 2026

This release is about SurgeTK reading your accounts the way you typed them. A retirement plan entered as 401(k), 403(b) or 457(b) now classifies as a retirement plan, a trust named as the primary beneficiary is no longer reported as an incomplete designation, and two new settings let you turn the Missing Beneficiaries callout off.

Most of what follows is live for every firm and happens on its own. Two settings in the Beneficiary section stay off until you turn them on, and one change asks you to generate a report again. Both are marked below.
​

Account types

A retirement plan typed with parentheses is recognized again, and the type list has one entry per type.

• 401(k), 403(b) and 457(b) are classified correctly. An account whose type was stored with parentheses was not matched as a retirement plan. It received no 1099-R default, was left out of the 1099 letter, and was grouped under Other Assets on the Net Worth report. The same account stored as 401k or 403b was matched correctly, so two accounts holding the same kind of plan could be reported differently. All spellings now classify as employer plans.
• Reports you already generated keep their earlier figures. This change is in how an account is read at the time a report is built, so a report generated before this release still shows the old grouping. Generate the 1099 letter and the Net Worth report again for any household holding a 401(k), 403(b) or 457(b) to pick up the correction. Nothing else is needed.
• 401(a) is now an account type. It was missing from the list. It is treated like the other employer plans: recognized by the 1099 letter and the Net Worth report, and left out of billable assets. No firm has an account set to 401(a) today, so no billing figure changes because of this.
• The type list shows one spelling per type. 401k and 403b were listed beside 401(k) and 403(b). The duplicates are gone.
• An account already saved with an older spelling is left alone. An account stored as 401k, or carrying a type from your CRM that the list does not offer, now shows that value in the dropdown and saves back unchanged. Opening one of these accounts no longer shows an empty type field.
• Imports read the parenthesised spellings. A spreadsheet column reading 403(b) or 457(b) was imported as Other. It now imports as the correct type, and 401(a) is recognized as well.

Beneficiary report

A trust named as the primary beneficiary is no longer reported as an incomplete designation, and you can turn the callout off.

• A trust as the only primary no longer shows a missing contingent. When every primary beneficiary on an account is a trust and no contingent is named, the report prints the primary line on its own. A trust carries its own successor terms, so the contingent line was noise you could not remove. SurgeTK reads TRUST, TR, TTEE and TRUSTEE as whole words in the beneficiary name.
• A person named beside a trust still gets the flag, and so does a missing primary. Those are real gaps in a designation, and the report still says so.
• You can hide the callout for your whole firm. Settings, Value Adds, Beneficiary has a new checkbox: Hide the "Missing Beneficiaries" callout. When an account has no beneficiary in a tier, the report leaves that line blank instead of printing Missing Beneficiaries. This setting is off until you turn it on. It is read when a report is viewed, so it applies to every Beneficiary report the next time each one is opened.
• You can hide it for one account. The account window's Beneficiaries tab has a new checkbox: This account intentionally has no beneficiaries. Use this for an account where an empty tier is correct. Saving the account marks the Value Add stale, so it rebuilds with your change. This setting is also off until you turn it on.
• Per stirpes now survives a Redtail sync. A Redtail sync replaced the whole beneficiary record on an account, which quietly cleared the per stirpes setting you had entered in SurgeTK. The sync now updates the primary and contingent lists in place and leaves your own settings alone. The new intentionally-no-beneficiaries setting is kept the same way.

Signing in

An address that already belongs to a firm now points you at that firm instead of offering to start a new one.

• A sign-in from a known firm domain leads with Request Access. Signing in with a work address that was never invited used to offer to create a new firm, which could produce a second copy of a company already using SurgeTK. When your email domain belongs to exactly one firm in SurgeTK, the onboarding screen now names that firm and offers Request Access first.
• It is a prompt, not a wall. Select "This isn't my firm" to clear the notice and carry on creating a firm. A domain can genuinely cover two practices.
• It stays quiet when the domain cannot identify one firm. Shared email providers and broker-dealer domains never match, and a domain used by more than one firm in SurgeTK does not raise the notice. The notice appears only when there is a single clear answer.