Product updates and release notes from SurgeTK
Product update

SurgeTK Release Notes August 30th, 2026

Jevohn avatar
Shared by Jevohn • August 31, 2026

This release is about the reports your clients hold in their hands. The Beneficiary report now says Missing Beneficiaries instead of leaving a blank, keeps a client's name on the same page as their accounts, and prints middle initials correctly. Accounts holding a zero balance leave your planning reports, closed insurance policies leave them too, and spreadsheet imports read dollar amounts the way people actually type them.

Everything below is live for every firm, and most of it is automatic. Items that need you to turn something on are marked Optional.

Beneficiary report

The report your clients read to check their estate plan now says more and breaks less.

  • Missing beneficiaries are named, not blank. An account with no primary beneficiaries now prints Missing Beneficiaries in the primary slot, and an account with primaries but no contingents prints it in the contingent slot, with the tier named in the Type column so it is clear which designation is absent. An account with no beneficiaries at all carries a single Missing Beneficiaries line. A blank cell could mean nothing was designated or the data had not come over; the report now says which, and the gap becomes the conversation the report exists to start.
  • A client's name stays with their accounts. A page break can no longer leave a client's name and the column headers stranded at the bottom of one page while every account row starts on the next. It is fine for a name, the headers, and an account or two to appear and then continue; a heading with nothing under it is not, and no longer happens. When a long table does continue onto the next page, the column headers repeat there.
  • The report clears its footer. On reports longer than one page, content now reserves room for your firm's footer on every page instead of running into it on later pages.
  • Middle initials print correctly. A middle initial recorded in lowercase, such as Mary a Smith, now prints as Mary A Smith. Single letter initials are no longer treated like the word "a".
  • One person, one summary row. A beneficiary recorded with a middle initial on one account and without it on another, such as John Smith and John A Smith, no longer splits their total across two summary rows. The fold is deliberate and cautious: names only combine when the rest of the name matches exactly, so two different people are never merged.
  • Already saved copies keep their old layout. These changes apply to reports the moment you open or generate them. A snapshot or surge packet saved before this release keeps what it was saved with until you regenerate it.

Zero balance accounts

An account holding nothing no longer pads the reports.

  • Accounts at exactly zero leave your Value Add reports. An open account whose balance is exactly zero no longer appears on Buckets, Guardrails, Net Worth, Beneficiary, or Homework. Rows of empty accounts made reports longer without telling the client anything.
  • The 1099 Letter keeps them on purpose. The letter reports a tax year, and an account holding nothing today can still owe forms for that year's activity, so it stays.
  • The account modal explains it. The Exclusions tab shows the zero balance as the reason an account left each report, and a manual include on that tab wins, exactly as it does for closed accounts.
  • A blank balance is no longer stored as zero. When your CRM sends an account without a readable balance, SurgeTK now stores no value instead of writing zero. An unknown balance is not the same thing as an empty account, and accounts with no stored balance stay on your reports. A spreadsheet cell containing only a currency symbol now warns instead of quietly storing zero.

Closed insurance policies

Your CRM's policy status can now reach SurgeTK. Optional. Map the field in Settings, then run a sync.

  • Zoho syncs can carry policy status. A new Policy Status row on the insurance card of the Zoho mapping lets you pick the field your firm uses. The sync understands the common vocabulary: In Force, Lapsed, Expired, Surrendered, Terminated, Cancelled, Closed, Paid Up, Pending, and Matured. A value the sync does not recognize leaves the stored status alone rather than guessing.
  • Policies whose coverage ended leave the reports. A policy marked Closed, Lapsed, Expired, Surrendered, or Terminated no longer appears on the Beneficiary or Net Worth reports. Paid Up, Pending, and Matured policies remain, because that coverage still exists.
  • Existing policies pick up their status on the next full sync. After mapping the field, run a sync so policies already in SurgeTK read their status from Zoho. Until then they keep the status they have.

Accounts without a type

An untyped account is now explained instead of silently dropped.

  • A type recorded in a secondary CRM field now counts. A Redtail account whose registration lives only in its tax qualified type field was treated as having no type at all, which silently dropped it from Guardrails, Buckets, Beneficiary, and Net Worth. It now classifies by that field, so a real IRA with an empty account type field lands in the right place on every report.
  • A genuinely untyped account says so on the report. An account excluded only because nobody set its type is now named in a note printed on the report itself, above the disclaimer, and flagged on the Guardrails and Buckets pages in the app. Setting the type clears the note. An include on the account's Exclusions tab puts the account back regardless.

Imports

The account import reads money correctly and finishes what it starts.

  • Dollar formatting imports correctly. An account value typed as $1,234.56 now imports as one thousand two hundred thirty four dollars and fifty six cents. It used to import as 1.
  • One bad row no longer stops the run. An account that fails to import is recorded in the report with its reason and the import moves on to the next row. The report is also saved as the run proceeds instead of only at the end, so an import interrupted partway still leaves a complete record of what landed, with undo covering all of it.