Tax-prep organization, not tax advice
Gathering tax documents stalls on one question, repeated dozens of times: "Where does this come from again?" You know you need a year-end statement, but is it in the bank portal, mailed by a brokerage, or issued by a platform you logged into once last spring? A source map answers that question once and keeps the answer. It is a plain reference that pairs each expected document with its origin, the specific account, platform, payer, or party that issues it, plus where to go and which login to use. Cash Workspace lets you build this map as a record set with the actual source documents attached as they arrive, so the map and the files live in one place. This page is organizational guidance for assembling your own document set, not tax advice; it does not tell you which documents your situation requires or how to file. It maps where things come from so the fetching is fast.
The problem
The slow part of tax prep is rarely filing the documents you already hold. It is the hunting, retracing which portal a statement lives in, which email address a platform sends to, which family member holds the original. A source map removes that friction by recording the origin of each expected document before you start fetching, so the gathering pass becomes a checklist of known destinations instead of a memory test. It deliberately stops at origin: it does not tell you whether each item has arrived yet (that readiness view is a separate record), and it does not log your open questions about a document. It answers one thing well, where to go to get each file.
Build the map
The goal is a stable reference you build once and refine each year. Create one record per expected document, fill in its origin fields, and attach the real file to that same record once you fetch it, so the map doubles as the home for the document it points to. Cash Workspace does not connect to any source or pull documents for you; every file is uploaded by hand. The map simply tells you where to go.
Inside Tax Prep 2025, add a folder named Document Sources. This is where the source map lives, separate from the folders that hold sorted, finished documents. Keeping the map in its own folder means the where-to-fetch reference stays distinct from the gathered set.
Make a record for each document you expect, named for the document itself, for example Year-End Bank Interest Summary, Brokerage Year-End Statement, or Mortgage Interest Statement. Name the document, not the source, so the map reads as a list of things to collect.
For every record, record the source/issuer, the source type (online account, mailed, person/party, in-platform), where to fetch it (portal name plus URL or the mailing it arrives in), and which login identity to use. This is the heart of the map, the answer to where does this come from.
Add a delivery method note: downloaded from a dashboard, emailed to a specific address, mailed to a home address, or handed over by a person. For person/party sources, note who to ask and how, so a request can go out early.
When you retrieve a file, attach it to its source record. The map record then holds both the origin reference and the actual document, so next year you can see exactly where last year's copy came from. Note that whether an item is still outstanding belongs on your readiness tracker, not here.
Once a record set is built, copy it forward each year and update only what changed, a new platform, a closed account, a different login. The map becomes a standing reference that gets faster every year instead of being rebuilt from memory.
Record structure
These are the metadata fields that make a source map useful. They describe origin and retrieval only, not status and not content. Record them once per expected document.
Example setup
Here is how a Document Sources folder might look for a self-filer with a small side business. Each record names a document and carries its origin fields; the real file is attached to its record once fetched. This is illustrative structure, not a list of which documents anyone is required to gather.
Source: First Northwest Bank. Type: online account. Where: bank portal, Statements & Documents tab. Login: personal account (jordan@email). Delivery: downloaded PDF. Note: usually posts late January. File attached once downloaded.
Source: Maple Street Brokerage. Type: online account. Where: brokerage dashboard, Tax Documents section. Login: personal account. Delivery: downloaded; also mailed. Note: consolidated statement may arrive in two parts.
Source: side-business marketplace platform. Type: in-platform dashboard. Where: seller dashboard, Payouts > Year-End. Login: business account (shop login). Delivery: downloaded from dashboard. Note: not emailed, must log in to pull.
Source: home loan servicer. Type: mailed + online. Where: servicer portal, Documents; paper copy mailed to home. Login: personal account. Delivery: mailed envelope, download as backup.
Source: co-owner Dana Ruiz (person/party). Type: person/party. Where: not a portal, request by email. Login: n/a. Delivery: emailed by Dana. Note: send request early January, Dana compiles manually.
Source: prior employer payroll provider. Type: online account. Where: payroll provider self-service portal. Login: separate employee portal login (reset password if needed). Delivery: downloaded PDF. Note: access may expire after employment ends, fetch early.
Common mistakes
How it helps
Create a record for each document you expect, hold its origin fields in one place, and keep the whole map inside a Document Sources folder within the year's tax-prep folder.
When you fetch a document, attach it to the record that maps its origin, so the map and the actual file live together and next year's hunt is instant.
Keep a Document Sources folder per tax year and copy the record set forward each year, updating only the sources that changed. The map gets faster, not slower, over time.
Cash Workspace does not sync with your bank, log in to platforms, or pull documents. It does not read your files or extract data. You fetch each document from its source; the map just tells you where that source is. It is free.
Related
The companion readiness view: mark each expected item gathered, in progress, or still missing. Use the source map to know where to fetch, and the tracker to know what is still outstanding.
The intake job that turns a chaotic mixed pile of statements, forms, and receipts into a structured single-filer tax-prep folder, the structure your source map sits inside.
The mechanical workflow for linking one backup or proof to the underlying record it supports within a tax-prep set, the same attach action used to file a fetched document onto its source record.
A running log of open questions tied to specific documents while you assemble for your own filing, for the annotations the source map deliberately leaves out.
A starting reference for which document types people commonly organize at tax time, useful for deciding what to add as expected records before you map each one's origin.
The broader hub for organizing business records into folders and records, the wider context your tax-prep document set fits within.
FAQ
Cash Workspace helps you organize where your tax documents come from and attach the files once you fetch them. It is not tax, legal, or accounting advice, and it does not tell you which documents your situation requires or how to file. It does not connect to your bank, log in to any platform, or download documents for you, and it does not read or extract data from your files. Every document is fetched and uploaded by you. For guidance on what your filing requires, consult a qualified professional.
Start a free Cash Workspace, create a Document Sources folder inside this year's tax-prep folder, and add one record per expected document with its origin fields. Next year, copy it forward and update only what changed. It is free to use, operated by HELPERG LLC. Questions? Reach us at info@helperg.com.