The return was never
the slow part.

No, and any firm promising that is describing a product for the simple returns that already went to consumer software. The clients worth having are the ones whose situation is nuanced enough to need professional judgement, and judgement is the part we deliberately leave alone. What we automate is everything surrounding it: working out what documents this engagement needs, collecting them securely, checking what arrived, chasing what did not, extracting the figures into reviewable form, and keeping the client informed. The value is increasing how much professional work each preparer can get through, not replacing the professional.

Industry surveying puts client-side delay at the top. In Wolters Kluwer’s annual survey of close to two thousand US accounting firms, respondents ranked late and unprepared clients as their number one challenge, and published accounts from firms describe spending up to about a third of engagement time on document collection, with individual preparers reporting several hours a week chasing documents during season. Those are third-party figures rather than measurements of your firm — which is why the first thing we do is look at one of your real engagements rather than assume the averages apply to you.

The Gramm-Leach-Bliley Act and the FTC Safeguards Rule, reinforced by the IRS through Publication 4557, with a written information security plan required for firms filing eleven or more returns a year and a template published in IRS Publication 5708. It is worth being blunt about what it is not: HIPAA does not apply to a CPA firm simply because the data is sensitive, and a vendor attaching that label to a tax workflow either does not know the difference or is counting on you not to. Where your firm does hold health information for a specific engagement, that is a real conversation with a real answer, and we will have it properly rather than by putting a badge on a page.

Some will not, and a system that only works when every client behaves is not a system. So the vault is the preferred path rather than the only one: documents that arrive by email are still classified, checked and matched to the checklist, and the client sees status without having to learn anything new. What changes is that the burden of tracking moves off your staff. In practice the portal adoption problem is usually a request problem — clients ignore "please upload your documents" and respond to "we need page two of your passport and the Q4 payroll report, here is the link".

No. Practice management tells you what the jobs are and where they stand; it does not go and get the documents, work out that a client uploaded last year’s K-1, or write the follow-up naming the two missing items. We build the layer that does that work and then writes the result back, so job status reflects reality rather than someone remembering to update it. If your practice-management system genuinely already does this well for your engagement types, we will say so rather than sell you a second one.

They are a normal part of this work rather than an edge case — foreign account statements, receipts for foreign tax paid, photographed passport pages. Documents are checked for legibility on arrival, so an unusable scan produces a specific re-upload request the same day instead of surfacing during review in March. Where a document is in another language, it is translated with the original kept alongside it, because the preparer needs to be able to see what the source actually said.

It starts with one engagement type, mapped end to end with your team — usually the one that causes the most back-and-forth rather than the most common one. That map produces a scope, a definition of what counts as working, and a fixed price, all agreed in writing before any build starts. Pricing depends on how many engagement types you want covered and which systems have to be connected, so there is no list price, and we would rather scope one type properly than sell you a firm-wide programme you cannot absorb during season.