SurgeTK News Center

This release is about what a Redtail sync keeps. A client you delete in SurgeTK stays deleted. An account type you set stays set. Your firm can keep children and grandchildren out of households. The Homework sheet also keeps the spacing you type in its notes, and it saves the meeting time in the time zone you choose.
​

Most of what follows is live for every firm and happens on its own. Three items ask for a step from you. The Family members filter stays off until an Admin ticks a relationship. A meeting time typed before this release may need to be entered again with its time zone. A client deleted before this release is not yet on the Deleted contacts list. Each is marked below.
​

Deleted clients stay deleted

A Redtail contact you delete in SurgeTK no longer comes back on the next sync.

• A deletion is remembered. SurgeTK kept no record of a deletion before. Any sync that read the contact again brought the client back: a normal sync when the contact changed in Redtail, and every full read after a reconnect or "Re-read every contact". SurgeTK now records each deletion, and every sync leaves those contacts out.
• Every way to delete counts. Deleting a client, removing a member in Edit Household, and deleting a whole household each record the deletion of every Redtail contact involved.
• Find them in Sync Filters. Go to Settings, Integrations, Redtail, then Sync Filters. The new Deleted contacts card lists each contact with the name, the date, and who deleted it.
• Restore brings a contact back. Click Restore to take the contact off the list. The next sync that reads that contact adds them back. Restoring does not start a sync, and Restore is unavailable while a sync is running. Only Admins can restore.
• Sync history shows the count. The sync history drawer shows "deleted in SurgeTK, left out" with the number of contacts the run skipped.
• "Re-read every contact" no longer brings deleted clients back. The checkbox text now says so.
• A reconnect with the same username keeps your normal sync. Every reconnect used to make the next sync a full read of every contact. Now only a change of Redtail environment or username does. Entering a new password after a Redtail password change keeps the incremental sync. Disconnect still resets it.
• Clients deleted before this release are not on the list until SurgeTK adds them. Until then, if one of them comes back after a sync, delete it once more and it stays out.
• Zoho is unchanged. This applies to Redtail contacts only.

An account type you set is kept

A Redtail sync no longer replaces the account type you chose.

• Your type wins. Every sync used to write Redtail's type over every account, so an account you changed from Other to IRA went back to Other on the next sync. A type you set in the account window is now kept through every sync.
• A real type is never changed to Other. When Redtail has no type for an account, or one SurgeTK cannot classify, the sync leaves the type SurgeTK already has. This applies to every account, not only the ones you edited.
• The account window shows the difference. When Redtail's type differs from the one in SurgeTK, a line under Account Type says so, such as Redtail says: Other ("Fee-Based Account"). It shows in view and in edit mode.
• "Use Redtail's type" hands the type back. Click the button next to that line to take Redtail's type. From then on the sync updates that account's type again.
• Sync history shows the count. The drawer shows "kept your account type" with the number of accounts the run left alone, next to "kept your status".
• Reports follow your type. For an account whose type you set, Buckets, Guardrails, the Net Worth report and the RMD table read your type. Before, they could read Redtail's label first.
• A type from an account import is kept too. A recognized type in your import file is not replaced by a later sync.
• Set a reverted type again. If a sync changed one of your types back before this release, open the account, set the type, and save. It stays from then on.
• Zoho is unchanged. A Zoho sync still writes Zoho's type.

Keep children and grandchildren out of households

A firm on Redtail can now choose which family relationships come across.

• A new Family members card in Sync Filters. Go to Settings, Integrations, Redtail, then Sync Filters. Tick the relationships to keep out. Child, Grandchild and Other are offered to start. After a sync, the card also offers the relationship names your own Redtail families use. Spouse is never offered.
• Why this was needed. Everyone linked in a client's Redtail family came across, whatever their category or status, so a child with the same status as a spouse could not be filtered out. The relationship Redtail stores for each family member is now the control.
• New imports only. A ticked relationship stops new members from coming in. Members already in SurgeTK are not removed. Delete those by hand, and with this release they stay deleted. An excluded member's own accounts stop syncing.
• The head of household always comes across.
• Your category and status filters still apply. A child whose own Redtail contact passes those filters still imports as a contact in their own right. Those filters remain the control for that.
• Sync history shows the count. The drawer shows "Family members kept out by relationship".
• Nothing changes until you tick a relationship. The list starts empty.

Homework notes keep what you type

Meeting Notes, the Homework column and Client Questions keep your spacing on screen, in Print and in the PDF.

• Indents, tabs, spaces and blank lines are kept. They were saved before, but the sheet, the printed page and the PDF collapsed them.
• Tab indents. In an open note box, Tab inserts an indent at the cursor, or indents every selected line. Shift+Tab removes one indent. Tab used to move out of the box and save.
• Ctrl+Enter saves. Cmd+Enter on a Mac. Escape still cancels, and clicking away still saves. A one-line hint under the box names the keys. It never prints.
• The cursor lands at the end. The box used to open with all the text selected, so the first key press replaced the note.
• The box grows as you type. There is no inner scrollbar.
• Special characters print as typed. A "<", "&", "$" or quotation mark in a note could lose text or print as markup on the sheet and in the client PDF. Each prints as typed now.
• Insurance notes and tax-year notes keep their line breaks when you view them.
• The sticky note on a Value Add no longer doubles blank lines when you save it.
• Snapshots and generated packets keep their old layout. A saved snapshot or a Surge packet already generated shows the notes as it did when built. Build it again to pick up the spacing.
• Notes are plain text. There is no bold, color or font change.

Homework meeting time is saved in your time zone

A meeting time typed on the Homework sheet now saves and shows at the hour you typed.

• The hour no longer shifts. A typed time was read in the wrong time zone, so 2:00 PM could print as 7:00 AM, and saving the sheet again could move it once more. The time you type is now read in the meeting's time zone, and saving without a change moves nothing.
• Pick the time zone in the Meeting details card. With Annotations on, click the meeting line on the sheet. The card now has a Time zone select with Eastern, Central, Mountain, Arizona, Pacific, Alaska, Hawaii, UTC, and your browser's zone. A record with no zone takes your browser's zone the first time you save a time.
• Every place shows the same time. The sheet header, the Meeting details card, the inline edit box and the Surge composer table all show the meeting's time zone. The Surge table adds the zone when it differs from yours, such as 2:30 PM CST. The zone is still not printed on the sheet.
• Meetings synced from a Surge calendar were never affected. They always carried their time zone.
• A time typed before this release may still be wrong. Check the meeting line on the sheet. If the hour is wrong, open the Meeting details card, set the Time zone and the time, and save.

Smaller fixes

• A Zoho sync survives a dropped connection. A sync that lost its connection to Zoho partway through failed with no retry. It now retries that page up to three times before it gives up.

Updated in the Help Center

These articles now describe the behavior in this release.

• Syncing with Redtail
• Sync Filters: Control Which CRM Records Come Into SurgeTK
• Why do children or other family members appear in my households?
• Meeting Worksheet (Homework)
• Why a Client or Account Is Missing From a Report
• Importing Account Data
• Redtail integration: technical reference

This release is about the RMD table on the Homework sheet. It follows IRS Publication 590-B for every account it should cover, including inherited accounts. It shows the arithmetic behind each figure, and your firm can change the inputs. Value Add pages also fit cleaner on an iPad and a phone.

Most of what follows is live for every firm and happens on its own. The new RMD settings start at the IRS defaults, so they change nothing until an Admin saves a change. Two items ask for a step from you. An inherited account needs a date of death for an exact figure. Saved snapshots and Surge packets keep their old figures until you build them again. Both are marked below.
​

RMD table on the Homework sheet

The table now includes every account the IRS rules cover. Expect more rows, most of all if you sync from Redtail.

• Accounts already in the table keep their amount. An IRA or 401(k) that was in the table before, and is not a Roth and not inherited, shows the same figure as before.
• More retirement plans are included. 401(a), 403(b), 457(b), TSP, and profit sharing and Keogh accounts now get a row. The table used to leave them out.
• IRAs synced from Redtail are recognized. Redtail keeps two type fields for each account: the tax-qualified type, such as Traditional IRA, and the account type, which is often a product name, such as Fee-Based Account or Brokerage Account. The RMD table read the product name first, so many IRAs synced from Redtail never got a row. It now reads both fields.
• An owner who turns 73 this year is included now. The IRS counts the age an owner reaches during the year, so the first RMD is for the year the owner turns 73. The account used to appear only after the birthday.
• Accounts owned by anyone in the household are included. The table used to check only the two clients in the sheet header.
• Some rows leave the table. A Roth IRA that is not inherited no longer shows an RMD, even when your CRM labels it only as IRA. A row whose RMD rounds to $0 is hidden. A Coverdell Education IRA is no longer treated as an IRA.
• Sheets pick up the change on their own. A Homework sheet recalculates the next time someone with edit access opens it, or when you click Refresh. New Surge packets use the new figures.
• Snapshots and generated packets keep their figures. A snapshot you saved, a Surge packet already generated, and an archived household keep the figures they were built with. To use the corrected figures, save a new snapshot or generate the packet again.

Inherited accounts

Inherited accounts use the IRS Single Life table, and the account window has a place for the details that make the figure exact.

• The Single Life table replaces the owner's table. An inherited account used the Uniform Lifetime Table, the one for account owners. That understated the amount, and a beneficiary younger than 72 got no row at all. An inherited account now appears whatever the beneficiary's age.
• The factor follows the IRS method. A surviving spouse uses the factor for their own age each year. Any other beneficiary uses the factor for their age in the year after the death, less one for each year since. When the owner died in 2020 or later and the 10-year rule applies, the last year shows the full balance, and the row's card shows the year the account must be empty. An inherited Roth under the 10-year rule shows no annual amount.
• Record the date of death for an exact figure. Without a date of death, the amount is an estimate from the beneficiary's current age, and the row's card says so. The account window had no place for these details before, so every inherited account starts as an estimate.
• The account window has a new Inherited Account section. Open the account and go to the Details tab. Check "This account was inherited", then set Relationship to Deceased and Date of Death. Deceased Name is optional. The section appears when the account type is a retirement type, such as IRA or Inherited IRA. A new account typed Inherited IRA checks the box for you.

RMD settings for your firm

Admins can now change how the RMD table is calculated for every household in the firm. Every setting starts at the IRS default.

• Find it in Settings, Value Adds, Homework. Click Show Settings on the Homework card, then go to RMD Calculation. Only Admins can change these settings. Everyone else sees them read-only.
• You do not have to change anything. A firm that keeps the defaults gets the corrected calculation described above. A worked example, such as $500,000 ÷ 24.6 = $20,325, updates as you change the controls, before you save.
• Beginning age. Any whole age from 72 to 80. The default is 73. The IRS beginning age is 73 today and rises to 75 in 2033. You can set 75 sooner.
• Base value. The default uses the December 31 value and falls back to the current balance. Choose "Use the December 31 value only" to require a December 31 value. With that choice, an account with no December 31 value shows no amount.
• Account types. IRA, 401(k), 401(a), 403(b), 457(b), TSP, and Profit sharing / Keogh. All seven are on by default. Turn one off to leave that type out of the table.
• Inherited accounts and empty rows. "Always include inherited accounts" is on by default. "Show rows with no RMD amount" is off by default. Turn it on to find accounts that are missing a December 31 value.
• A custom table for account owners. The default is the IRS Uniform Lifetime Table. You can enter your own factors instead. Inherited accounts always use the IRS Single Life table.
• Saving applies to the whole firm. Saving recalculates the RMD table on every Homework sheet in your firm. Snapshots and generated Surge packets keep their figures. "Reset RMD settings to platform defaults" puts every setting back.

RMD explanations on the sheet

The Homework sheet now shows how each RMD figure was reached. Nothing new prints.

• Click the RMD heading. Its card, How this RMD is calculated, names the table, the beginning age, the base value rule and the account types your firm uses, with a worked example. An Admin can change the beginning age, the base value and the empty-row setting from this card. Saving there recalculates every Homework sheet in your firm.
• Click any row. Its card shows the base value, the factor and the result. For an inherited account it also shows the relationship, the year of death and any 10-year deadline.
• A row with no amount says why. Its card names the reason, such as a missing date of birth or a missing December 31 value. These rows show only when "Show rows with no RMD amount" is on.
• The cards belong to Annotations. They are on by default. Use the Annotations button on the Value Add page to turn them off or on. They never print.
• The figure is a planning aid, not a tax determination. It does not model the still-working exception for employer plans or the Joint Life table for a spouse more than ten years younger.

Value Adds on iPad and phone

Every Value Add page now fits the screen on an iPad, a phone or a narrow browser window.

• The report fits the screen. On a narrow screen, every Value Add page scrolled sideways and the report was cut off on the right. The report now scales down to fit and stays centered. It goes back to full size when the window gets wider or an iPad turns to landscape.
• The page buttons are within reach. On a narrow screen, Refresh, Save, Print, Download, Annotations and the snapshot list could not be reached. A new button next to the Value Add switcher opens them in a side panel. The panel is named for the Value Add you are on, such as Homework Actions.
• The Value Add switcher stays on screen. Its menu hung past the right edge of a narrow screen. It now opens inside the window.
• Desktop, printing and PDFs are unchanged. Print and Download still produce the full-size report.

Smaller fixes

• Calendly sync keeps the meeting status you set. A sync set every synced meeting back to Scheduled, including meetings you had marked Completed or Canceled. A meeting that is still booked in Calendly now keeps your status through every sync.
• Export History shows the right result. When an export failed while another export was running, the Reports page could mark the wrong one as failed. Each export now records its own result.
• Settings checkboxes keep their shape on a phone. On a phone screen, checkboxes and radio buttons on the Settings page stretched into wide ovals. They are normal size again.

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.

This release is about work that finishes on its own. A surge now completes even when the connection to your browser is lost partway. A Zoho sync updates only the withdrawals it reads and leaves the rest of the account alone. And a Redtail contact with an empty name no longer stops a sync partway.

Everything below is live for every firm and happens on its own. Nothing here asks you to turn something on.
​

Surge runs

A surge finishes even when your browser tab or the web server loses the connection during the run.

• A run no longer depends on the tab that started it. A surge run is now recorded in SurgeTK from the moment it starts, with one entry per household. The packets build in the background as before, and the run is closed by that same background process when the last packet lands. Closing a tab, a dropped connection, or a routine server restart during a long batch no longer leaves the run open.
• A run that goes quiet is closed for you. If a run stops making progress for ten minutes, SurgeTK checks each household that has not finished. A household whose packet is already built is counted as done, a household whose job is still queued is left to run, and the batch closes with its ZIP once nothing is outstanding. A run cannot stay on the progress screen indefinitely.
• The ZIP and the run report describe the same households. Every household that produced a packet is included in the ZIP and counted in the run summary, including a household the report lists with an issue. The households listed as included and the households listed with issues now add up to the run.
• Run history shows what is in progress. The run history table and the run report now show a run that is still running, and the households in it that have not started yet.
• A run without an archive says so. If the ZIP could not be created, the completion message tells you the archive is missing instead of reporting a download, and the run detail opens so you can see each household's result.
• Every run logs its completion. The activity log now records a Surge run completed entry for every run that recorded a start.

Zoho systematic withdrawals

A sync updates the withdrawals it reads and leaves the rest of the account alone. This section applies to firms that sync Distribution records from Zoho.

• Each withdrawal is matched to its Zoho record. When a sync reads a changed Distribution record, it updates that one withdrawal on the account in place. The other withdrawals on the account are not touched by that run.
• Withdrawals you entered in SurgeTK stay. A withdrawal with no Zoho record is yours, and a sync never removes it. If Zoho later sends a record with the same amount, frequency and withholding, the two are treated as one withdrawal rather than shown twice.
• A withdrawal leaves an account only when Zoho confirms it. A withdrawal is removed only when a complete read of Zoho shows the record is gone, or now belongs to a different account. A record the run could not read in full is kept for you to review rather than removed. A record moved to a different account in Zoho can stay listed on its old account until the next Deep sync.
• Editing or importing an account keeps the Zoho link. Saving an account from the account window, or importing accounts from a spreadsheet, now keeps the link between each withdrawal and its Zoho record, so the next sync updates those withdrawals in place instead of adding a second copy. An imported row that matches a Zoho withdrawal exactly is not added twice.
• What to check on an account. Guardrails, Buckets and Homework read the withdrawals listed on the account. If an account shows the same withdrawal twice, delete the copy that did not come from Zoho; the sync will not add it back. If a withdrawal is missing, add it in Zoho and run a sync, or add it in SurgeTK.

Redtail contacts

A contact with an empty name no longer stops a sync partway.

• An empty first or last name gets a placeholder. A Redtail contact whose first name or last name is blank, which is common when a trust or a business is entered as an individual contact, now syncs with (Unknown) in the empty half. The sync completes, and the contact's household and accounts sync with it. A contact with both halves blank keeps the name Unknown Client as before.
• Enter the name in Redtail and it flows through. The next sync replaces the placeholder with the name you entered. There is nothing to change in SurgeTK.
• The sync shows the contacts to fix. The sync history drawer has a new Name placeholders card listing each contact that received a placeholder, with its Redtail id. The sync report carries the same list.
• Contacts already affected correct themselves. A contact that received a placeholder before this release, or whose sync ended partway because of an empty name, is repaired on the next sync. There is nothing to click.

Redtail sync

Your status filter now decides who is in a household, and a full re-read is one checkbox away.

• Skipped statuses now apply to family members too. When the sync imports a client, it also imports the contacts in that client's Redtail family, so a spouse who carries a non-client category still lands in the household. Those family members now respect the statuses you skip. Add Child of Client, Grandchild of Client, or whichever status your firm uses for adult children to the skipped list, and they stay out of their parents' household. The note under Contact Statuses in the filter window explains this. A family member already in SurgeTK stays until you remove them.
• A list of statuses to import is not applied to family members. If your filter names the statuses to include rather than the ones to skip, a spouse whose status is Spouse of Client still comes in with the client. Only a skip list changes who joins a household.
• Re-read every contact. The sync window has a new checkbox, Re-read every contact. A normal sync asks Redtail only for the contacts that changed since your last sync. Tick the box to read all of them: slower, but it applies your current filters to every contact. You no longer need to disconnect and reconnect Redtail to do this, and your saved filters stay in place. The box is unticked each time the window opens, so a full re-read is a one-time choice.
• A full re-read can bring a household back. It reads every contact that matches your filters, including contacts behind a household you removed in SurgeTK. Before you tick the box, exclude those contacts in Redtail or skip their status in your filters.
• Saving a filter tells you when a full re-read is needed. When you save a change to your Redtail filters, SurgeTK reminds you that filters apply to the contacts your next sync reads, and points you at the checkbox. Saving a filter never starts a sync on its own.
• A retired Redtail value stays in your filter. A category or status you selected that Redtail has since renamed or removed still shows in the filter window, marked (no longer in Redtail), and stays saved until you untick it. If Redtail cannot be reached while the window is open, your saved selections are kept as they are.

Value-Add PDFs

Every PDF is checked before it is saved or sent.

• A PDF is checked for its content before it leaves SurgeTK. A Value Add, a Quick Preview and each page of a surge packet are now checked for a rendered Value Add before the PDF is saved, downloaded or emailed. A page that did not render as a Value Add is reported in the run instead of being kept as a PDF. In a surge packet, the packet ships without that page and the household is listed with an issue.

This release is about what a sync leaves behind. An advisor you take off a household in Zoho now stays off, Redtail Account As Of dates read correctly, and the Homework sheet prints as one page in surge packets.
​

Everything below is live for every firm and happens on its own. Nothing here asks you to turn something on.

Household advisors

Your Zoho Lead Advisor field is now the answer in both directions.

This section applies to firms that map a Lead Advisor field in their Zoho household mapping.
​

An advisor removed in Zoho is now removed in SurgeTK. Each household the sync reads is reconciled: the advisors Zoho lists are added, the advisors the sync applied earlier and Zoho no longer lists are removed, and the servicing advisor is repaired when it pointed at one of the removed advisors. The writing advisor is never changed by a reassignment in Zoho. The first sync after this release does the cleanup in one run.
​

Advisors you added yourself stay. An advisor SurgeTK has never seen in Zoho on that household is treated as yours and is left alone. An advisor Zoho has listed at any point follows Zoho, so make that change in Zoho rather than in SurgeTK. A name Zoho still lists is added back on the next sync.
​

Removing someone from your team clears their Zoho link. Removing a user, or taking away their advisor seat, now also clears the Zoho advisor name linked to them, so the sync cannot put them back on households. Linking a Zoho name to a different user moves those households, along with their servicing and writing advisor, to the new user, and a link that fails partway can be retried safely. Only users who hold an advisor seat are considered when a Zoho name links itself.
​

A mapping mistake cannot empty your households. If more than half of your assigned households would change advisor in a single run, the removals are skipped for that run, and a Deep sync applies them once you have confirmed the mapping and the linked names. If nearly every household comes back with an empty Lead Advisor field, no sync mode applies it, because that is a mapping problem rather than a real reassignment. When Zoho lists a name SurgeTK cannot match to a user, which is what a renamed picklist value or a brand new advisor looks like, the previous advisor is kept on that household until you link the name in the Unlinked Zoho Advisors list in Settings.
​

Removals need a complete view of the household. A firm whose households match Zoho by name gets removals from a Deep sync only; other runs add without removing. After any run that had to skip or hold a removal, the sync stops re-applying advisors to households outside that run, and starts again only after a full sync that applies everything it sees. A removal you make by hand therefore stays, including on a household Zoho no longer sends at all.

The sync shows its work. The sync history drawer has a new Household advisors card: advisors added, advisors removed, servicing advisors repaired, households Zoho now leaves with no advisor at all, and any links cleared, each with the name and the reason. Every changed household also gets an activity log row, so an advisor change made by a sync is as visible as one made by hand.

Redtail account dates

Account As Of dates read correctly. Redtail holdings carry an as-of date whose digit order depends on the feed that wrote it inside Redtail. Some feeds send the year first, others send the month first. Each date is now read by its own layout.
​

A date SurgeTK cannot read is left off instead of guessed. A value that does not spell a real day, or that lands before 1900 or more than a year from now, no longer reaches the account.
​

Accounts showing an incorrect As Of year correct themselves on the next sync. There is nothing to click. The next Redtail sync rewrites the date from the holdings it reads. The balances beside those dates were current the whole time.

Homework sheet

Page one prints as one page again. In surge packets and from the household Print button, the Meeting Notes box could run past the bottom of page one, push the Action Items table onto a page of its own, and leave a nearly empty page behind it. The sheet is now sized for one printed page on every path.
​

Downloads and Quick Preview were always correct. A report downloaded or emailed from the household page, and the surge Quick Preview PDF, printed correctly throughout. Only surge packets and the Print button were affected.
​

Packets built between August 30 and September 4 keep the split. A saved packet keeps the layout it had when it was saved. Regenerate any packet from that window to pick up the fix.

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.

This release includes a brand new Value Add! It also adds a lifecycle to your book. Households you no longer serve can be archived instead of deleted, accounts can be closed and reopened, and your CRM syncs can mark records closed instead of removing them. Alongside that, the Welcome page now carries product update videos, household totals agree everywhere they appear, and spreadsheet imports and CRM syncs can no longer run over each other.

Everything below is live for every firm. Nothing changes on its own: archiving, closing, and the new CRM behaviors are all actions you take or settings you choose. Items that need you to turn something on are marked Optional.

Roth Conversion Letter

A new one page client letter that turns a filed tax return into a conversion conversation. Optional. Turn it on in Settings, Value Adds.

• What it is. A client facing tax strategy letter built from the household's filed tax year. It recaps the client's taxable income, tax bill, marginal rate, and long term capital gains rate, then states in plain dollars how much more taxable income they could take next year before crossing into a new bracket. It follows the Tax Strategy Review letter advisors have mailed for years, with the math and the mail merge done for you.
• The figures come from the Taxes tab. Filing status, adjusted gross income, taxable income, tax after credits, and the recorded Roth conversion all come from the household's stored tax year, so nothing is typed twice. Editing tax data marks the letter stale, and it regenerates with the corrected figures.
• The bracket math backs the conversion out. Next year's headroom is worked out from taxable income with the one off conversion removed, so a client who converted last year is not told they have less room than they really have. The letter reports the room left inside the current bracket, and separately the full width of the bracket above it for firms that want to show the aggressive option. Rates come from the IRS tables for the relevant year.
• Every word is yours. Settings, Value Adds, Roth Conversion Letter holds the title, salutation, opening paragraph, education bullets, the consider callout, closing paragraph, sign off, and disclaimer. Edit any of them once and every household's letter follows.
• Seventeen data points drop into any sentence. Household name, firm name, advisor name, tax year, letter year, filing status, AGI, taxable income, tax bill, both conversion amounts, marginal rate, that rate written in cents, long term capital gains rate, bracket headroom, next bracket rate, and next bracket room. Place any of them anywhere in your wording and they resolve per household.
• A sentence that cannot be true is never printed. A bullet whose figures do not resolve for a household hides itself. A client already in the top bracket never sees the next bracket line. The conversion sub bullet appears only when that household actually recorded a conversion that year. The salutation hides entirely rather than open the letter with a stray comma.
• The conversion suggestions can be switched off. One toggle removes the whole consider callout, which leaves a clean tax recap with no conversion recommendations. On by default.
• You can review any year. The letter opens on the household's most recent stored tax year, which is what surge packets and saved copies always use. A dropdown on the letter page lets you look at an earlier year, with a banner saying which year you are viewing. Those views are ad hoc and never save over the household's copy.
• A household with no tax data says so. Instead of a letter full of blanks, the page renders a clear "Tax data needed" state and flags the value add.
• Edit it from the letter itself. Annotation cards on the letter open the salutation, intro, and closing for firm wide editing, and the tax data card opens that household's Tax Year modal so you can correct a figure without leaving the page.
• It joins surge packets only when you say so. Unlike older value adds, a missing setting is never treated as on. The letter is in a packet only after your firm turns it on.

Archiving Households

• Archiving keeps everything. Accounts, value adds, saved reports, surge packets, tax years, and history all stay reachable. The household simply stops counting: it leaves the household list's default view, the banner statistics, and new surges skip it unless an admin includes it deliberately. Restoring takes one click and puts everything back exactly as it was.
• Archive from the row menu or in bulk. Pick a reason, add an optional note, and choose whether to capture final value add snapshots. Every archive and restore offers an immediate Undo in its toast.
• The household list understands Archived. A new Active, Archived, All view sits above the list. Archived households show a muted row and an Archived chip carrying the reason and date in its tooltip.
• The household page says so plainly. An archived household's page carries a banner naming when and why it was archived, with a Restore button in it. Edit and add actions are visibly disabled with an explanation instead of failing silently.
• Archived households are read only. Every write path is blocked on the server across 61 routes: editing members, adding accounts, changing advisors, generating value adds. The block answers with a clear message telling you to restore the household first.
• Value adds freeze at the moment you archive. Archiving saves a final dated copy of every value add your firm has enabled, including ones nobody had opened for that household yet. Opening a value add on an archived household shows the values captured at archive time, clearly labeled, instead of recomputing numbers that drift as rates and settings change. This is the compliance record of what the client was shown. If one value add fails to render during capture, the archive still completes and says so, for example "Household archived, 6 of 7 value adds captured", and the affected tile reads "Not captured" with the explanation in its tooltip.
• Archived households stay findable. Global search still returns them, marked with a chip, so a compliance lookup never comes up empty. The surge composer gains a Household Status filter so admins can include archived households deliberately, and any that are skipped are reported in the run detail as Skipped rather than disappearing.
• Deleting a household with saved reports warns first. Deleting is permanent and always was. If a household still holds saved value add snapshots or surge packets, the delete now stops, tells you how many records would become unreachable, and offers archiving instead. You can still delete deliberately.
• Exports and reports say what they include. Exports gain a Household Status column and an Exclude archived households toggle that remembers your choice.
• Peripheral surfaces respect it. Surge meetings can no longer be scheduled on an archived household, and bulk advisor assignment skips archived households instead of silently editing them. Undoing an accidental restore keeps the household's original archive date.

Closing and reopening accounts

An account that has closed stays on the household as a record instead of disappearing.

• Close with a reason and an optional backdated date, and reopen at any time. Closing keeps the account's last known value and full history: that record is the compliance answer to "what did this account hold when it closed". A closed account immediately leaves the household's total investable assets, and reopening puts it back. The household total in the header updates the moment you close or reopen, with no page reload.
• The Accounts tab shows the state. Closed accounts appear muted with a Closed, Transferred, or Inactive chip and the close date in the tooltip. The row menu offers Close account, with a required reason and optional date, and Reopen.
• The account modal edits it. The Details tab shows status, close date, and close reason, with a Closed chip in the title bar. You can close, reopen, or correct the date and reason of an account that is already closed. Corrections are audited the same way as the original close.
• Every transition is traceable. Each close and reopen writes exactly one audit row and one account history row, so the change is always attributable to a person and a moment.
• Closed accounts can be hidden without being deleted. Optional. A Hide closed accounts preference keeps closed accounts off the household account list by default. The list says how many are hidden, and one click shows them again, so a closed account is always reachable if you need to reopen it or check its history.
• Closed accounts can be exported. The accounts export gained optional Account Status, Date Closed, Close Reason, and CRM Status columns, so you can pull everything that closed in a quarter with dates and reasons. Existing exports are unchanged unless you add the new columns.

Value adds and closed accounts

A closed account is treated by period, not by blanket.

• Balance sheet reports drop closed accounts outright. Net Worth and investable totals leave them out, because money that left is not on the balance sheet.
• Homework and the 1099 Letter ask a better question. Both report a period, so they ask whether the account was closed before the period began. An account closed during the tax year still counts for that year's distributions, RMD, and 1099, because the client still receives a 1099 for it. An account closed before the year began is out.
• Every figure on the Homework sheet follows the same rule. The RMD table, the Cash Flow tiles, the prior year AGI, and the Net Worth line now agree with each other and with what the account's Exclusions tab says.
• The exclusion report explains the year rule. A closed account excluded from Homework or the 1099 Letter now says why in period terms, for example "Closed before the 2026 tax year began", instead of a bare "Closed account". An account with no recorded close date is excluded and the report says exactly that, rather than guessing a year. A manual include override on the Exclusions tab still beats the closed rule.

Household totals

One rule, so the same household shows the same number everywhere.

• The details header, the households list, and the export now agree. All three previously worked the total out differently: two recomputed it fresh and left out closed and cash accounts, while the stored figure behind the export was a running total that included everything and was updated by eight different parts of the app in eight slightly different ways.
• The rule. Closed accounts and cash equivalent accounts (checking, savings, money market, CDs) are left out, and anything you have set by hand on an account's Exclusions tab wins either way.
• Totals that had drifted are corrected in one pass. Because the stored figure only refreshed when someone touched an account, households nobody had edited kept an old number indefinitely. A one time correction runs with this release. On a book of 1,563 households, 475 had a stored figure that was wrong, most of them showing nothing at all against a real balance.
• Closed accounts no longer count as net worth. A closed account holds nothing, so it no longer counts toward a household's monthly net worth snapshot. Cash accounts still do: a checking balance is net worth even though it is not money under management.
• A household whose accounts are all closed no longer shows a distribution. The details header worked out investable assets one way and monthly distribution another, so a household holding only a closed account could show no assets and a monthly distribution at the same time. Both figures now come from the same accounts.
• One export column renamed. "Total Account Value (all accounts)" is now "Total Account Value", because it is no longer a different number from the one on screen.

CRM syncs

Your decisions outrank the CRM, and a sync can now mark records closed instead of deleting them.

• A sync no longer overwrites an account status you set. When you close or reopen an account by hand, or through a previewed import, that decision outranks Redtail and Zoho. Previously a sync could write its own status straight back over yours. The rest of the account, its value, holdings, and owners, keeps syncing as before. Nothing changes for accounts whose status comes from the CRM.
• The account row tells you when the CRM disagrees. An account whose CRM record disagrees with the status you set carries a "CRM: Closed" or "CRM: Active" chip, and the tooltip shows the CRM's own wording. You find out on the row instead of finding out from a report that dropped the account.
• Sync history reports what a sync left alone. The drawer counts the accounts whose status the sync declined to overwrite, next to the existing count of accounts it declined to delete, and gains a Household lifecycle card showing what each run evaluated, archived, and restored.

Redtail

• The Closed Account Filter can mark instead of delete. Optional. Instead of removing an account the moment Redtail marks it Closed, Transferred, or Inactive, the sync can keep it and mark it closed. A closed account leaves your total investable assets and every value add, but its balance history, transactions, and beneficiaries stay on the household as a permanent record. Firms using the delete behavior today keep it until they choose the new mode in the Sync Filters modal.
• The sync now finds real close dates. Redtail reports that an account is closed but its main account record carries no close date, so closed Redtail accounts had no date on file and date based value add rules had to leave them out. The sync now asks Redtail's account detail endpoint for the close date whenever it sees a closed account without one, so Homework and the 1099 Letter can place the account in the right year.
• Reopening an account in Redtail clears its close date. A sync could add a close date but never remove one, so an account reopened in Redtail kept its old date and stayed out of totals and value adds while the account list showed it as active. A sync that reports the account as Active now clears the date. Only Active clears it: a label the sync cannot recognize, such as your own "Liquidated" or "Under Review", leaves the date alone.
• Contact statuses can drive household lifecycle. Optional. A new section in the Sync Filters modal maps each of your Redtail contact statuses to what it means: still a client, no longer a client, or deceased. On top of the map, you choose what the sync does when every member of a household is deceased or no longer a client: nothing, suggest archiving, or archive automatically. Suggestions appear on the Households page with the reason, and applying one opens the normal archive dialog with the reason filled in. Dismissing a suggestion is remembered. Automatic mode captures final value add snapshots as it archives, never touches a household you archived or restored by hand, and restores a household it archived if the contacts become active again in Redtail.
• Contacts you already imported keep updating even when filtered. Contact filters now gate new imports only. Previously, a contact whose Redtail status changed to one your filter excludes stopped updating entirely, which meant the exact changes worth knowing about, such as a client passing away or leaving the firm, were the ones that never arrived. An already imported contact keeps receiving updates, including the date of death and termination date Redtail carries, which SurgeTK now stores on the client.
• Every contact's accounts refresh on every sync. Account balances and holdings now refresh for every contact on each sync, not only for contacts changed since the last sync. Custodian feeds update accounts without touching the contact record, so the previous incremental pass missed those updates. The contacts stage stays incremental.
• Closing and reopening from Redtail is on the record. The account records that Redtail made the change and when, and the activity log gets one entry per change plus one summary per sync. Steady states write nothing: an account that stays closed sync after sync does not fill your log. Sync history shows how many accounts each run marked closed, reopened, and found close dates for.

Zoho

• A sync no longer clears fields you did not map. Every sync used to blank an account, asset, or liability field that had no Zoho column mapped, so a custodian, 1099 form, or close date typed by hand was wiped on the next run. Unmapped fields are now left alone. A mapped column that is blank in Zoho still clears the SurgeTK value.
• A client you marked Deceased stays Deceased. When no Zoho life status field is mapped, the sync no longer resets a client you marked Deceased back to Living on every run.
• Excluded households can be archived instead of deleted. Optional. The Household Sync Filtering card has a new choice. Instead of removing a household, with all its accounts and history, when its client type matches one of your excluded values, the sync can archive it. Final value add snapshots are captured as it archives. Households you archived or restored by hand always win over the sync.
• A Zoho status field can drive household lifecycle. Optional. A new Household Status Mapping section lets you pick any Zoho picklist field on your households module and map each value to Active or Archived. Values you leave unmapped change nothing.
• Closed accounts can be kept instead of deleted. Optional. Close out Filtering has a new Closed Accounts choice, on both Investable Assets and, for the first time, Bank Accounts. The sync can keep every closed account, marked closed with its close date, rather than skipping and deleting accounts closed before the cutoff year. In this mode the cutoff year controls display: accounts closed before it are hidden on the household account list, with a one click reveal. The mapping modal states in plain words which behavior is currently active.
• The closed account cleanup only deletes what is provably Zoho's. For firms that keep the delete behavior, the cleanup now requires the SurgeTK account to actually be linked to Zoho before deleting it. Previously it matched by account number alone, so a hand entered account that happened to share a number with a closed Zoho account could be deleted. Accounts spared by this check are counted in sync history. The cleanup also removes the deleted accounts' one time transactions, which previously stayed behind pointing at nothing.
• Accounts that vanish from Zoho are flagged on the household. When the stale record check confirms an account is no longer in your feed, its row carries a "No longer in Zoho" chip with the date. If the account was closed in Zoho, the row menu's Close action is one click away, and the chip retires once the account is closed.
• Closing and reopening from Zoho is on the record. The account records that Zoho made the change and when, and the activity log gets one entry per change. Steady states write nothing.

Imports

Imports and syncs take turns, and an import can now set account and household status.

• A spreadsheet import and a CRM sync can no longer run at the same time. Both write the same account and household records, so running them together could silently drop one side's changes. Whichever starts first holds the firm's slot, and the other is turned away with a clear message naming what is currently running.
• Imports can close and reopen accounts. The account import gains three optional columns: Account Status, Date Closed, and Close Reason. A row saying Closed, Transferred, or Inactive closes the account with the date and reason from the file; a row saying Active reopens a closed account and clears its close date. A blank cell always preserves what is stored, an unrecognized value warns and writes nothing, and an account missing from the file is never touched. Nothing is inferred, and a close set by hand or by import outranks CRM syncs.
• Imports can archive and restore households. The contact import gains a Household Status column with a reason and date. An import row that touches an archived household still applies, because backfilling records is legitimate, but the run warns you and counts those rows in the report.
• The import warns before money lands on a closed account. A row that gives a closed account a new value, and a one time transaction import that targets a closed account, warn in the report and in the preview. The value still applies, because backfilling history is legitimate, and the account is never reopened by accident.
• Imports tell you what they closed. The live progress panel says "3 accounts closed", and the count stays visible after a refresh while the undo window is open. Each closed or reopened account gets a proper activity log entry, the same way a manual close does, and the activity log gained Close and Reopen filters.
• Insurance imports understand Policy Status. The insurance import gains a Policy Status column. Recognized values, now including Paid Up, Pending, Matured, and Terminated, are stored; an unrecognized value warns instead of being silently dropped.
• Contact imports accept more spellings of Living and Deceased. A cell such as "deceased", "Yes", "D", or "dead" used to fail the whole row with a validation error. The import now normalizes it. A blank or unrecognized cell leaves the client's existing value unchanged and never fails the row.
• Templates include the new columns. The downloadable account, insurance, and contact templates carry the new status columns, plus a second sheet listing the accepted values.

Welcome page

Product updates now live in the app.

• The Welcome page leads with what is new. Once your firm has finished its setup tasks, the latest update video is featured with its title, date, and a short description, and every earlier update sits in a library below it. Selecting any update plays it in place. Firms still setting up keep the setup tasks at the top, with the updates underneath.
• New updates are flagged until you have seen them. An update published since your last visit carries a New chip, and the Welcome item in the sidebar shows a small dot until you open the page. Updates older than 30 days are never flagged, so a new user does not see a wall of New chips.
• Setup tutorials stay one click away. For firms that have completed setup, the task list and the intro video move behind a Tutorials button in the page header. Replayable workflows and tours work exactly as before.

Surge packets

A packet run survives a dropped connection, and a broken page never reaches the client.

• Progress survives a closed laptop. Surge and sync progress are now saved as the run proceeds and replayed when your browser reconnects, so a network gap or a sleeping laptop no longer leaves the progress overlay stuck or skips the download at the end.
• A broken value add page no longer ships as a PDF. If a value add fails to render during a surge, it is now recorded as failed and the run continues. Previously the error page itself was converted to PDF and packed into the client's packet.
• Surge warns when every account is closed. A household whose accounts are all closed carries an "All accounts closed" warning in the composer, so an empty looking packet is explained before it is sent. Warnings no longer count closed accounts, so a missing withdrawals warning cannot be masked by a closed account's leftovers.

Households and billing

• Households show an effective rate beside Annual Billing. The household details page now shows what your annual billing works out to as a percentage of the household's billable assets, with the calculation explained in the tooltip and written out as a receipt row in the billing breakdown modal. Billable assets are the accounts that count toward AUM, less employer sponsored plan types (401(k), 403(b), 457(b), Pension, Profit Sharing, Keogh, TSP, Deferred Comp), because those are typically not billed. The dollar figure beside it is unchanged and still matches recorded billing exactly. The rate does not render when billing is not recorded or billable assets are zero.

Value add settings

• The Guardrails and Buckets distribution rate cells can be shown again. Optional. Settings, Value Adds gains a checkbox for each of the two reports that restores the Upper and Lower Guardrail distribution rate cells, which have been blank since they were removed. When turned on, both cells show your firm's available rate to one decimal, and the cells regain their borders. A small preview in the settings panel shows exactly what each state looks like. Off by default, so nothing changes unless you turn it on. The manual value add creator honors the same setting.

Smaller corrections

• Select all across pages follows your current filters. On the Households page, ticking "Select all N households" and then deleting or assigning advisors used to act on every household in the firm. It now acts only on the households matching the search text and advisor filter you are looking at, which is what the count in the toolbar already promised.
• The household import walkthrough covers the whole wizard. The guided tour never learned about the Choose Your Client Import Type screen, so it ran one screen ahead, and picking Household Taxes mid tour left you stranded. Both paths are now covered, and the final step says Import instead of Done, matching the button.
• Dialog and toast polish. Confirmation dialogs drop the decorative icon, single line notifications no longer render with an empty body, and a delete dialog dismissed quickly can no longer leave the page locked behind an invisible backdrop.

This release corrects RMD and withdrawal figures on the Homework sheet, adds a review step and safer month scoping to transaction imports, merges import and sync history into one view, and restores PDF generation.

No action is required. All items below are live for every firm.

Homework sheet

Corrected RMD figures and account coverage.

• RMD figures use the current IRS Uniform Lifetime Table. Factors are selected by the age reached during the distribution year, matching IRS methodology. Previously displayed RMDs were overstated by roughly 7 percent at common ages. Figures correct themselves the next time the value add is generated.
• QCD accounts appear in the withdrawal tables. Accounts with "QCD" in the name or type were previously classified as cash and excluded from the Homework grids. They and their withdrawals now show. Plural "CDs" still classifies as cash.

Transaction imports

Monthly files replace only their own months, and nothing is written before you approve it.

• Replacement is scoped to the months in your file. For each account and transaction type, only the calendar months present in the file are replaced. Monthly backfills work one file at a time in any order, and re importing a corrected file cleanly replaces that month.
• A review step runs before anything is written. After mapping columns, a Review and confirm step shows a dry run: transactions to be added, existing transactions to be replaced, a month by month breakdown, rows protected because they came from your CRM, and any rows needing attention. Nothing is written until you confirm.
• Replaced transactions are reported. The progress panel gains a Replaced section, and the downloadable report lists every replaced transaction.
• Transactions synced from your CRM are protected. A file import never deletes a transaction that came from a CRM sync. Matching rows are skipped and reported.
• Dates are correct in every time zone. The day in your file is the day shown in the transactions table, the edit form, and every value add. The add transaction form defaults to your local date.
• Value adds refresh after transaction changes. Imports, undos, and manual add, edit, or delete all mark value adds stale.
• Picker tiles advance on selection. Choosing a data type, account type, or client sub type moves to the next step directly.

Import and sync history

One history for everything that changed your data.

• File imports and CRM syncs share one history. The Imports page lists both together, sorted by date. Search covers file name, import type, and sync provider.
• Sync rows summarize themselves. Each row shows provider, Deep or Incremental, status, and a created, updated, and removed rollup.
• "What changed" opens the full detail. A drawer shows change counts, a per entity table of what was created, updated, removed, and skipped, and a data hygiene section covering stale rows removed, households refreshed, systematic entries cleared, and value adds flagged. Skipped rows state their reason and list the parent records you can fix. Truncated feeds and failures are called out at the top.

CRM sync reliability

Syncs are more resilient and withdrawal totals are more accurate.

• Deleted CRM records no longer count toward withdrawal totals. Records removed in your CRM are now cleared from SurgeTK, so displayed withdrawals reflect current data. Manually entered transactions are never touched, and affected households regenerate with corrected figures.
• Identical systematic withdrawals stay separate. Two systematic entries of the same amount no longer collapse into one.
• Syncs run on a dedicated background worker. A deploy or restart no longer interrupts a sync in progress. Progress still streams to the page.
• Support for high record volumes. Verified well beyond our largest firm's data set.

Zoho

New Distribution History sync for firms using Zoho.

• A new "Distribution History" card on the Investable Assets tab of the field mapping modal imports monthly distribution records, populating both the Homework withdrawal and deposit tables. Withdrawals display gross, before withholding, with taxes taken from each record. The 12 month window ends on the last completed month. Turning the section on removes overlapping one time transactions so nothing double counts, and unmapping it reverses cleanly. Nothing changes for firms that do not map the section.

Documents and packets

• Surge packet and value add PDF generation is restored. Downloads affected between August 12 and this release now generate correctly. The rendering environment is pinned so the issue cannot recur.

This release covers tax data flowing into the Homework sheet, a new Zoho Taxes sync, clearer sync results and controls for both Redtail and Zoho, a per-security holdings view, and accuracy improvements to AUM totals and imports.

No action is required. All items below are live for every firm.

Homework Sheet

Tax figures come from the Taxes tab, and the sheet is edited in place.

• Tax figures read from the Taxes tab. AGI, taxable income, and total taxes come from the household's most recent recorded tax year, and the year label shows the actual year. The marginal bracket is derived from taxable income and filing status. Figures previously entered on the sheet keep showing for households with no recorded tax year, so nothing goes blank.
• Tax edits open the tax year form. Clicking a tax figure opens the same Add or Edit Tax Year form the Taxes tab uses, so both places always agree.
• Everything else is edited directly on the sheet. Meeting type, date, and a new location field, agenda items, action items, the homework column, meeting notes, client questions, and cash flow figures are all edited in place. The Edit Fields modal is retired, and everything it covered is still editable.
• Header fields explain themselves. Every header figure carries an annotation card stating where it comes from, including blank fields, which explain where they fill in from. The Primary Residence card lists the matched home and its loans and opens each record. The Income card lists the household members whose income contributes.
• Client details open the client form. Job, employer, and retirement date cells open the Edit Client modal directly.
• The household summary shows the derived bracket. The Marginal Tax Bracket box on household details derives from the same tax data and opens the Taxes tab. A manually entered bracket remains the fallback.
• Blank figures render cleanly. An unrecorded mortgage payment no longer prints $0, and a missing interest rate no longer leaves a stray "@".

Zoho Sync

Tax years sync from Zoho, and sync results state exactly what happened.

• Taxes now sync. Map the new Taxes section in the field mapping modal and tax years flow from Zoho into each household's Taxes tab — the same tax data that powers the Homework sheet. Blank Zoho fields never overwrite figures already on file.
• Renamed records stay matched. Renaming an account, asset, liability, or insurance record in Zoho updates the matching SurgeTK record in place rather than creating a second one.
• Records removed from Zoho are flagged, never auto-deleted. A record that leaves Zoho is marked "No longer in Zoho" with the date on the unlinked lists, and removal stays in your hands. Flagging is deliberate: a record must be absent across full syncs at least a day apart before it is marked.
• A running sync can be cancelled. Cancel stops the sync at the next safe point, and a cancelled run is labeled as cancelled rather than completed.
• Deep sync on demand. An Advanced option on the sync confirmation runs a full sweep of every record rather than only recent changes.
• Mapping dropdowns are searchable. Type in any dropdown in the field mapping modal to filter by field name, matching anywhere in the name.
• Mapping guidance is easier to find. Info tooltips throughout the mapping modal appear on hover and keyboard focus, and the External Household ID tooltip explains how records link to households.
• Configuration problems are reported plainly. A sync that cannot run because of a mapping issue reports the specific problem instead of finishing with nothing to show.

Redtail Sync

Results you can act on.

• Completion messages show real counts. A finished sync reports how many records were added or updated, and a run with no changes says "no changes found".
• Completed, cancelled, and failed runs are distinguished. Each outcome shows its own message, so a run that did not finish cleanly is never presented as a normal completion.
• Credential problems are called out. If Redtail sign-in stops working, the sync says so, the integration card shows an "Action needed" notice, and a Reconnect Redtail button appears in place of Retry.
• Admins are notified. Firm admins receive an in-app notification when a sync needs attention, cleared automatically once a healthy sync completes.
• No window is skipped. If a run has a problem partway through, the next sync picks up from the last fully clean run, so changes made in between are never missed.
• Timestamps read "Last successful sync". Hover labels on the sync buttons reflect the most recent clean run.
• Reconnecting keeps your settings. Reconnecting Redtail preserves your contact and account filter settings.

Securities

See who holds a security, position by position.

• Click any security for its account exposure. The Securities page in Settings opens a full detail view listing every position holding that security: owner, household, custodian, account type, units, value, and the custodian's price date, with summary tiles at the top.
• Search, filter, and export. Positions can be searched and filtered by status, and the filtered set exports to CSV.
• Out-of-date valuations stand out. A position whose price date lags the rest of that security's feed is flagged as stale, so one account left behind by a custodian feed is easy to spot.
• The page appears where it applies. The Securities page shows for firms with a Redtail connection.

Accounts and Totals

AUM reflects open accounts.

• Closed accounts no longer count toward AUM. Accounts with a close date are excluded from the household banner, the household header, member cards, and Buckets and Guardrails generation, so totals reflect the accounts actually under management.
• Exports say what they include. The CSV export columns that sum every account, open or closed, are labeled "(all accounts)".
• Select all means every page. On the unlinked record lists, "Select all" applies bulk actions to every matching record across all pages, and confirmation dialogs state the full count.

Imports

Allocation columns import at face value.

• All mapped allocation columns are applied. Cash, income, annuities, and growth mappings carry through every mapped column, and additional columns can be added on both the account step and the buckets step.
• Excel percentages import as displayed. A cell formatted as 25% imports as 25, matching what the spreadsheet shows on screen.

Also in This Release

• Letters open with the household's name. The 1099 letter begins with a salutation built from the household's name, and householdName is available as a data point in any 1099 text block.
• Value add tiles wrap. Firms with many value adds see tiles wrap to a new row instead of compressing onto one line.
• Interrupted syncs recover on their own. If a sync is interrupted mid-run, its status resets automatically within a couple of minutes and the page updates in place.

This release covers billing accuracy and imports, Redtail sync coverage, a new holdings layer that drives Buckets allocation, and name handling across beneficiary reports.

No action is required. All items below are live for every firm.
​

Billing

Annual Billing totals now reflect imported account billing. Household billing rolls up account level billing alongside household fees.

• Prior year billing stays visible: when the current calendar year has no billing recorded, the most recent year with data is shown instead, labeled with the year it came from
• Breakdown opens from the billing box: click anywhere on the Annual Billing box to see the breakdown. The box is keyboard accessible
• Breakdown reads as a receipt: period and total appear at the top, followed by account billing, household fees, and total. Estimated figures carry an "Includes projection" badge, and coverage is explained in one sentence
• Household fees moved into Edit Household: the Edit Household modal now has Details and Billing tabs, with fee entry on the Billing tab. The standalone Household Fees modal is retired

Billing imports

Custodian files match your accounts more reliably.

• Account numbers match regardless of formatting: dashes, spaces, and letter case are ignored, so a custodian file listing 38064644 matches an account stored as 3806-4644. Accounts that could match more than one record are reported rather than guessed
• Negative amounts are accepted: fee adjustments and refunds import as written
• Re-running a file is safe: rows for the same account and period sum within a file, and re-importing replaces the stored value for that period rather than adding to it
• Import results state what happened: the completion toast reports imported and failed counts with the most common reason, and each failure explains how to correct it
• A billing import guide is included: it covers matching rules, negative adjustments, multi row summing, one period per file, and where imported billing appears afterward
• Upload step is easier to read: Billing Type, Billing Cycle, and Period sit in a single row in a centered column, with the drop zone aligned to it
• Period labels are shown in UTC: a calendar year 2025 file reads as 2025 rather than shifting a day by timezone

Redtail sync

Broader coverage and faster incremental syncs.

• Addresses now sync: contact addresses come across with the rest of the contact record
• Incremental syncs only pull what changed: syncs after the first one complete substantially faster
• A single problem record no longer stops a sync: each contact is handled independently, so the rest of the page continues
• Systematic withdrawals are protected: existing withdrawal data is never replaced with an empty result, and inferred withdrawals that exceed the account value are discarded
• Custodian names fill in more often: when the primary field is empty, the feed aggregator is used
• Account pages are fully paginated: households with many accounts sync completely

Holdings and allocation

Position level data from Redtail, and Buckets allocation calculated from it.

• Holdings sync with each account: positions are refreshed on every sync, with the as of date reflecting the actual feed price date
• Allocation is calculated from positions: when every holding in an account is classified, the cash, income, annuities, and growth split is derived from the positions themselves. Manually entered splits always take precedence
• Positions appear in the Allocation tab: each account modal shows the holdings under the split they produced, with the relationship stated on screen
• Systematic Withdrawals has its own tab: withdrawals moved out of Transactions into a dedicated third tab
• Securities page for administrators: Settings has a Securities page listing every held security by value, with a bucket dropdown, source labels, search, and reset to automatic. Changes re-roll the affected accounts

Beneficiary reports

One person appears as one row.

• Names match without regard to capitalization: a beneficiary entered as "JOHN SMITH" by a sync and "John Smith" in the account modal is treated as the same person and receives a single line with a single share
• Existing reports correct themselves: reports saved before this release apply the new matching the next time they are viewed. Nothing needs to be regenerated
• Duplicate beneficiary records are no longer created: account entry, Redtail sync, and Zoho sync all match existing beneficiaries consistently

Name display

Names in all caps or all lowercase are standardized.

• Organizations are title cased: entities read "Kitsap Humane Society", "Smith Family Trust", and "Estate of William Thompson"
• Acronyms are preserved: ASPCA stays ASPCA
• Deliberate capitalization is left alone: a name already written with mixed case, such as "Marguerite O'Brien", "Jan van der Berg", or "ABC Charity, Inc.", is treated as intentional and is not rewritten
• Organization word order is preserved: "ABC Charity, Inc." is not reordered

Sync status and value adds

• The sync button stays visible while a sync runs, reading "Syncing" for the duration
• Last sync time on hover: hovering the Redtail or Zoho button shows when the last sync completed, updated in place when a sync finishes
• Value add annotations are on by default. If you have previously turned annotations off, your setting is kept
• Breakdown accounts are grouped by owner: Buckets and Guardrails breakdowns group accounts under the household member who owns them, individuals first, then joint, then unowned. Single owner households keep the flat list
• Value add reports refresh when underlying data changes: cached report data is rebuilt when accounts, holdings, or security classifications change

Also in this release

• Integrations moved to the Imports page: the entry point is now a button in the Imports page header rather than a sidebar item
• Client member cards show the edit control on hover: the edit pencil appears on hover or keyboard focus