Automations/Finance
Organize Prior Year Returns So Next Season Starts With Them
Every return starts by finding last year's. It is in a folder named after the season it was prepared in, under a filename that says "final", next to two other files that also say final.
The short answer
A return belongs to a tax year, not to the season it was prepared in, and the distinction matters because the two differ by several months and sometimes by years when a late or amended return is involved. A workflow uses the Read Details from File step to read the taxpayer and the tax year off the return itself, the Rename step to name it by that year, and the Move step to file it under the client and year — so next season's starting point is a predictable path rather than a search.
Steps this uses
Before and after
What actually changes
As they arrive
- return final.pdf
- return final v2.pdf
- 2026 season/smith.pdf
- amended.pdf
After the workflow
- Okafor, D/2023/2023-return-as-filed.pdf
- Okafor, D/2023/2023-return-amended-as-filed.pdf
- Okafor, D/2024/2024-return-as-filed.pdf
- Okafor, D/2025/2025-return-as-filed.pdf
Four returns filed by the tax year printed on them, with the amended one distinguishable from the original.
Setting it up
Described once, then it runs
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 return is uploaded, read the taxpayer and the tax year off the return itself, name it by that year and whether it is as filed or amended, and file it under the client and year.
Tax year, from the return
Read off the document, not taken from the folder it was in or the date it was created. A 2023 return prepared in 2026 belongs in 2023, and this is the misfiling that costs the most time next season.
Mark amended returns as amended
An amended return and the original both belong to the same year, and both need keeping. The filename has to distinguish them or the folder holds two documents that look like the same thing.
Run it over the archive
The On a Schedule trigger works through returns you already hold, not just new ones. The backlog is the actual problem — this year's return is easy to find and 2019's is not.
Keep the as-filed version distinct
What was filed and what was drafted are different documents. Only one of them answers a question from a tax authority, and it should be obvious which.
Preparation season is not the tax year
They diverge by a few months in the ordinary case and by years in the interesting ones: an extension, a late filing, an amendment prepared long afterwards. Organizing by season puts a 2023 return in a 2026 folder, where nobody looking for 2023 will go. Reading the year off the return removes the judgement and makes the path predictable, which is the property that matters when the next preparer is somebody else.
Last year's return is this year's most valuable document
It carries the carryforwards, the depreciation basis, the elections made, the entities involved. Every engagement effectively begins by finding it, which means the time spent looking is paid once per client per year, forever. That is a small amount of work multiplied by a large number, and it is the strongest argument for getting this particular structure right.
What it does not do
It names and files returns. It does not read carryforward figures into this year's return, compare years, or import into tax software — that is what the software's own prior-year import is for, and it works from data rather than from a PDF. This makes sure the document that import depends on is where it should be.
Then build
Variations worth building next
When a scanned stack of old returns is uploaded to the Archive Scans folder, split it into one file per return, read the taxpayer and tax year off each, name it by that year and whether it is amended, and file it under the client and year.
Digitizes a paper archive of returns into the same client and tax year structure as new ones.
When a return is filed into a client's tax year folder, read the taxpayer, the tax year and whether it is as filed or amended, and send those details to our practice management app.
Keeps the practice system's record of which returns are on file in step with the folders.
Every week, go through the client return folders, find files with draft or final v2 in the name, and move them to a Drafts subfolder under the same client and year.
Leaves the as-filed return as the obvious file in each year folder, with drafts kept but out of the way.
Limits
What to know before you build it
It can work through what is already there
This one runs on a schedule over a folder you point it at, so the documents sitting in it now are read and filed alongside the ones that arrive later. A large backlog is an overnight job rather than an instant one, because each document is read rather than pattern-matched.
What you need to run it
Pointed at a folder in The Drive AI, this works on every plan including the free one, because the files are already here. Pointing it at a Google Drive, OneDrive, SharePoint or Dropbox folder instead means connecting that account, which is on the Max plan or any team workspace.
FAQ
Common questions
How should prior year tax returns be organized?
By client, then tax year, with the year read off the return itself rather than taken from when it was prepared. The two differ by months in ordinary cases and by years for late or amended returns, and organizing by preparation season puts returns where nobody will look for them.
How do you handle amended returns?
Keep both, in the same tax year folder, with the filename distinguishing the amended version from the original. They belong to the same year and both need retaining, so a name that does not distinguish them leaves a folder with two documents that appear to be the same thing.
Can it reorganize returns I already have?
Yes. A workflow can run on a schedule over the archive rather than only on new returns, which matters because the backlog is the problem — the current year is easy to find and returns from several years ago are not.
Does this import prior year data into tax software?
No. Tax software has its own prior-year import and it works from data rather than a PDF. This makes sure the document is filed where it can be found, which is the part that goes wrong when a client changes preparer or a practice changes staff.
Next season starts here.
Filed by the tax year on the return, not the season it was prepared in.
5 GB free · No credit card required