Development Update — May 2026

Short version: GoToMyAccounts is very much alive, very much under active development, and we're closer to a major release than we've ever been. This post explains where things stand, why the gap between visible releases has been longer than usual, and what's coming.

Why it's been quiet on the surface

Behind the scenes, the last couple of years have been the largest engineering effort in the history of the product. The original GoToMyAccounts went live in 2010. The web has changed considerably since then — browsers, security standards, email deliverability rules, payment processor APIs, mobile expectations — and a lot of the original architecture was carrying that weight.

Rather than continuing to bolt new features onto aging foundations, we made the call to rebuild the platform properly. That work doesn't always produce a flashy "new feature" announcement every month, but it's the work that determines whether GTMA is still a thriving product five and ten years from now. Spoiler: it is.

Three tracks, running in parallel

To get from "the legacy app you use today" to "the modern platform we want to give you," we're running three tracks at the same time. This is deliberate — we don't want to disappear for a year and re-emerge with a "big bang" rewrite. We want a smooth handoff.

Track 1 — Legacy GTMA (what you log into today)

This is the version most of you are using right now. We're not adding net-new features here. What we are doing is shipping targeted fixes when something needs immediate attention — particularly around email deliverability and login reliability, which have become moving targets as inbox providers tighten their rules.

There will likely be one or two more substantive updates to the legacy app before it retires. Most notably:

More built-in sending domains for customers who don't use their own custom domain
Smarter default sender addresses to dramatically improve delivery of one-time passcodes, customer invites, and notifications

This addresses the single biggest pain point we hear about — emails not arriving — and it can't wait for the next track.

Track 2 — GTMA Beta (the next-gen portal, nearly ready)

This is the closest to being deployable. It is substantially a new code base. Most of the day-to-day annoyances people have flagged over the years — login flow, two-factor handling, email delivery, payment processing pages — are already addressed here. It's faster, more reliable, and cleaner.

The remaining work to release the Beta to everyone is essentially the new payment-processing front end. The backend for that is about 95% complete, so this is largely surface-level work at this point. We don't anticipate this taking long.

Track 3 — GTMA SPA (the future)

The SPA (single-page app) is a completely new architecture — a faster, more modern web app, the kind of experience you'd expect from a modern SaaS product in 2026. Because we're not bound by legacy compatibility constraints here, development is moving rapidly.

It's currently about 20% behind Track 2 in terms of feature completeness, and it shares the exact same backend as Track 2. That's important: every piece of business logic we ship for Track 2 is automatically usable by Track 3. The SPA work is purely frontend. So as Track 2 hardens, Track 3 isn't far behind — it's effectively a faster, more polished face on the same engine.

Why three tracks instead of one?

Because a clean handoff matters more than a fast one. We don't want a forced migration where you wake up one Monday and everything looks different and something you depended on doesn't work. The parallel approach means:

The legacy app keeps running while the new ones mature
Every backend improvement in Beta benefits the SPA automatically
We can move customers over in batches, with the existing product as a safety net
When the SPA is ready, the transition off Beta is mostly visual — the business logic doesn't change

What's next on the roadmap

A few things we're particularly excited about:

Simple invoicing without QuickBooks. A growing number of GTMA users have told us they're frustrated with Intuit and would love an option to just sign up, invoice their customers, and get paid — no QuickBooks Desktop, no QuickBooks Online, no sync. We're building exactly that. It will start as a streamlined invoicing tool and expand over time into a more complete accounting and reporting system. The goal: a turn-key option for businesses that don't want to be tied to QuickBooks at all.
More default sending domains. We are adding accountportal.app , invoice-portal.app , payment-portal.app , and a few others as additional default home-base domains, so customers who don't run their own domain still get reliable, professional-looking sender addresses.
Improved payment processing pages with cleaner UX and better support for the major processors.

We'll be publishing a separate, more detailed product roadmap article shortly that covers the longer arc.

TL;DR

GoToMyAccounts is not stagnant — it's in the deepest period of active development in its history. The work has been heavy on plumbing and light on shiny new buttons, but that phase is ending. Track 2 (Beta) is in the home stretch, and Track 3 (SPA) is close behind it. Expect to see things start landing publicly very soon.

As always, we're happy to answer questions — just reach out.

— The GoToMyAccounts Team