A client calls about a letter from the IRS concerning 2023. The preparer who handled 2023 left in the spring, and their filing convention left with them.
The short answer
Client first, then fiscal year, then document type — and the reason the order matters is that every request starts with a client and a period. A workflow uses the Read Details from File step to identify the client, the year and the document type from the contents, the Rename step to name each file date-first, and the Move step to file it. Applying the structure automatically is the part that makes it survive staff turnover, because a convention that depends on each person remembering it lasts exactly as long as the person who wrote it.
Steps this uses
Before and after
As they arrive
After the workflow
Four documents filed by the client and the year printed on them, not the year they happened to arrive.
Setting it up
This is the sentence. Send it to the builder and the steps below appear on a canvas, wired and named, for you to change before anything runs.
When a client document arrives by email or upload, read the client, the fiscal year and the document type off it, rename it date-first, and file it under the client, then the year, then the document type.
Three levels. Firms that add a fourth — by preparer, by engagement, by quarter — find that the fourth is the one nobody applies consistently, and one inconsistent level undoes the other three.
Surname first for individuals, legal name for entities, and never both. "Smith, John" and "John Smith" become two folders the first time somebody is in a hurry, and merging them afterwards is worse than the original problem.
The Read Details from File step reads the tax year off the form rather than taking it from the date of upload. A 2024 K-1 arriving in 2026 belongs in 2024, and this is the single most common misfiling by hand.
Two clients with similar names, or a document naming an entity and its owner, is where automated filing goes wrong. Ask a Person to Approve puts those in front of somebody with the destination shown before anything moves.
This is the misfiling that costs the most and is noticed the latest. A corrected 1099 for 2024 arrives in 2026; a K-1 from a partnership arrives nine months after year end. Filing by when a document showed up puts it in a folder where nobody will look for it, and the error is invisible until somebody is reconstructing a year under pressure. Reading the period off the document removes the judgement entirely.
Every other part of the structure tolerates a little drift. Client names do not, because a duplicate folder splits a client's history in two and nothing surfaces the split. Pick surname-first for individuals and legal name for entities, apply it automatically, and the question of what to call a folder stops being asked at the moment somebody is least careful about answering it.
It files and finds documents. It does not prepare a return, reconcile an account, or tell you a client is missing a form. It makes a handover survivable — which is the case it earns its place in, because the cost of a bad structure is paid by whoever inherits it rather than whoever created it.
FAQ
Client, then fiscal year, then document type, with files named date-first in ISO form. Three levels is the limit that gets applied consistently; a fourth tends to be the one people skip, and one inconsistent level undermines the rest. The same structure for every client is what makes a handover possible.
By tax year, read off the document. A corrected 1099 for 2024 can arrive in 2026, and filing it by arrival date puts it where nobody will look. This is the most common manual misfiling, and it is usually discovered under time pressure.
Pick one naming convention — surname first for individuals, legal name for entities — and have it applied automatically rather than typed. Duplicates form when somebody in a hurry enters a name differently, and nothing surfaces the split afterwards, so the client's history quietly exists in two places.
Those go to review rather than being guessed. A K-1 names the partnership and the partner, and which folder it belongs in depends on whose engagement it relates to — a decision, not a fact on the page. A person decides, with the proposed destination shown first.
Client, year and type, applied by the system rather than remembered by a person.
5 GB free · No credit card required