Keeping W-2 and 1099 requests organised begins with a sort almost nobody performs: whether the form in the message is one your client received or one your client has to send out. Those are two different jobs. They share a word, a month and a mailbox, and very little else.
- One client is frequently both at once. The owner of a small company takes a W-2 from it, gets a 1099 from the bank, and has to issue three more to contractors. So the sort is per form, not per client.
- Nothing in this class can be chased before it exists, and unusually, the day it will exist is published in advance rather than chosen by anybody you can write to.
- The question is never whether a form arrived. It is whether all of them did, and the mailbox has no way of answering that. Last year’s return does.
- The forms your client has to issue are a production run against a single date, and most of what decides how it goes was settled in June.
Two jobs, one word
For a personal return you are on the receiving end. Forms come to the client from employers, banks, brokers, platforms and pension administrators, and your work is collection: getting hold of documents that other organisations have already produced and posted somewhere.
For a business client with employees or contractors you are on the producing end. Forms go out from the client to people who worked for them, and copies go to the agency. Your work there is not collection at all. It is a small manufacturing run with a deadline, a population and a penalty for missing it.
The mailbox cannot see the difference, because the words a client uses are identical. Do you have my 1099. I need to do my 1099s. Attached is the 1099. Those three sentences belong to three different jobs, and the third one is ambiguous even after you open the attachment.
Everything downstream of the sort differs, which is why the sort has to come first.
Who is waiting is different. On the collection side it is you, and a desk in your office that cannot start. On the issue side it is a contractor who cannot file their own return, and an agency with a date.
What late costs is different. A W-2 that reaches you in March delays one return. A batch of forms your client failed to issue is charged per form, and the charge climbs with how late they are. One is a scheduling problem and the other is a bill.
What finished means is different. On the collection side a form is done when it is in the file and matched to a line. On the issue side it is done when it has been filed with the agency and separately furnished to the person named on it, which is two acts, not one, and firms lose the second more often than the first.
And who can act is different. On the issue side your client holds every input, so the whole job is answerable today if somebody chases the right person. On the collection side a form that has not been issued cannot be produced by anybody, however firmly you ask.
So the first thing recorded against a message in this class is which direction the form is travelling. It costs a second on arrival. Reconstructed in the third week of January, from a thread where the client wrote 1099 four times meaning two different things, it costs considerably more.
Nothing here can be chased before it exists
A document can be missing for about six reasons and only one of them is forgetting; that argument, and what to do about the other five, belongs to managing client document requests. W-2s and 1099s sit almost entirely inside one of those reasons. They have not been issued yet.
What makes this class unusual, and genuinely easier than the rest of the mailbox, is that the day it will exist is not a guess. It is set in law and published, and it is the same day for every one of your clients.
The shape in the United States is familiar enough to state plainly, though it is worth checking against the year rather than against memory. Wage forms and the ones covering payments to contractors are due to their recipients at the end of January. Brokerage consolidated statements come later, around the middle of February, and brokers routinely take the extension that pushes them past it. Anything flowing through a partnership or an S corporation is not one of these forms at all and can arrive months after the spring deadline, though your client keeps it in the same mental envelope and will describe it with the same word.
Three things follow, and the first is the one firms find hardest to hold.
A chase before the issue date is not a chase. It is a message asking somebody to hurry up about something that does not exist, and a client who receives two of those learns something about your dates that will cost you in April. The correct treatment for the whole of January, for most of the collection list, is silence with a diary entry behind it.
After the issue date, silence starts carrying information for the first time. The form now exists, so the client either has it and has not sent it, or does not have it. Those are different problems with different next messages, and the second is much more common than firms expect. A client who moved house in the autumn has forms sitting in a hallway they no longer own. A client who left a job in June has a W-2 posted to an address they gave that employer in 2021. And a growing share of these forms are never posted at all: the payer furnishes them behind a login, and the notification that the form is ready arrives as an email that looks exactly like the marketing from the same sender. Nobody is ignoring you in any of those cases, and all three are settled by a question rather than by a reminder.
The third follows from the first two, and it is the cheapest message in the whole season. Tell the client the dates in January, before they ask. Two sentences saying that their brokerage statement is not expected until the middle of February, and that there is nothing to do about it until then, will stop three anxious messages and one premature start on a return. It also quietly moves the relationship onto your calendar rather than onto their sense of how long is too long.
The practical instrument, then, is not a chase list. It is a list of expected forms, each carrying the date it should exist by, and the follow-up date derived from that date rather than from the day you sent the request. For everything else a practice waits on, the clock starts when you ask. Here it starts when the payer is obliged to post. What that date then has to leave room for is the work still to be done once the form arrives, and how much room that needs shrinks every week of the season, which is worked out in inbox zero during busy season.
The count nobody has
For every other item in a practice mailbox you know what you asked for. A missing bank statement is missing against a request that names it. That is what makes the reconciliation possible at all, and running the firm inbox is where reading arrivals against a list gets its full treatment.
This class breaks that, and it is the only part of the job that is genuinely hard.
You do not know how many forms exist. The client does not know either, which is worse, because they will answer confidently when asked. Nobody in the transaction has a complete list except the agency that receives the copies, and it will share its version about eighteen months later, in the form of a notice.
So the list has to come from somewhere other than the client’s memory, and the only reliable source a practice already owns is last year’s return. Every payer that reported last year is enumerated in it, with an amount against each. That is the starting count, and it is wrong in exactly the ways the year changed.
What moves it is a short and predictable set of events. A job changed, so there are two wage forms and one of them is going to the old address. An account was opened, or closed, or moved to a different institution, which usually produces two partial-year forms where there was one. Money came out of a retirement account. A house was refinanced, which is not one of these forms but arrives with them and gets counted as one. A side business had its first year. A platform crossed a reporting threshold and issued something the client has never seen before and does not recognise as tax paperwork.
Which points at the January message that does more work than any request for documents. Send the client the list. Here are the eleven payers we saw last year; tell us which of these are gone and what is new. A client can answer that from a phone, in three minutes, without opening a filing drawer, and the answer is worth more to you in January than any of the documents would be, because it fixes the denominator. Everything you do afterwards is measured against it.
It also replaces a question that cannot be answered. Is that everything gets a yes from somebody who has no way of knowing, and that yes is then treated by both sides as a fact. Ask about events instead of about forms. Did you change jobs, close an account, take money out of a pension, sell anything, do any work on the side, receive money through an app. People remember events. Almost nobody remembers paperwork, and the form they are least likely to remember is the one from the payer they dealt with once.
One refinement is worth the trouble. The absences are not equally serious, and the count as usually kept treats them as though they were. A missing interest form for a few dollars costs a rounding error in tax and a matching notice much later. A missing form for contract work is a return that is wrong by a material amount and a conversation that is genuinely unpleasant. Last year’s amounts are sitting right beside last year’s payers, so the list you are reconciling against can be ordered by what an absence would cost. That ordering is what tells you which single missing item justifies a phone call on the fourth of March, when the other six do not.
Fourteen attachments and no message
Deliveries in this class have a shape of their own, and it defeats the ordinary way of tracking a request.
The client sends everything at once, or in six goes over three weeks. The files are named by the phone that took the photographs. One PDF holds nine separate forms scanned in a single pass. One consolidated statement runs to sixty pages and contains several forms inside it along with pages of transaction detail. There is often no message at all above the attachments, or a single line reading here you go.
What you are reconciling, then, is a heap against a list, and the heap has no labels. Two failures come out of that, and they cost differently.
The first is that the matching gets postponed to preparation. The heap sits in the thread until somebody opens the client’s file three weeks later, at which point the missing item is discovered with three weeks less room to do anything about it. This is the ordinary way a February delivery becomes an April problem, and it is entirely a scheduling failure rather than a client one.
The second is double counting. A broker sends paper and posts the same form behind a login, so the client forwards it twice, from two sources, under two filenames. A firm counting arrivals rather than matching them to expected forms ends up with a count that is too high and a file that is missing something else.
Three habits handle almost all of it, and none of them is elaborate.
Ask for a number in the message. Attached are nine items reads as a courtesy and functions as a checksum: it makes a truncated send or a failed attachment visible on the day rather than in March. Clients do this happily once asked, because counting what you just scanned is easier than describing it.
Match on arrival, not at preparation. This is the discipline the whole guide rests on and it is the one that gets dropped first in a busy week, which is precisely when it is worth the most. What it costs is a minute per delivery. What it buys is knowing, on the fourth of February, which of the expected forms are still out, while there is still a February in which to ask.
And acknowledge with the lines it closed, not just with thanks. The case for writing a receipt at all is made properly in the chasing guide, and it holds here unchanged. What is specific to this class is that a single consolidated statement often satisfies four or five lines at once. If the acknowledgement does not say which, the client will go looking for the individual pieces and send them separately, and now you are matching duplicates while they believe they are still behind.
The naming convention, incidentally, is yours and not the client’s. Asking two hundred people to rename files before sending is an instruction most will not follow and none will follow twice. Rename on arrival, in the moment you are matching anyway.
The issue side is a production run
Turn the direction around and the job stops looking like collection at all.
Your client paid people during the year. Some of those payments require a form to be issued to the person and filed with the agency, all of it against a date near the end of January that applies to the whole population at once. There is no staggering it and no partial credit.
Almost none of the work that decides how that month goes happens in that month. Two inputs settle it, and both are gathered while nobody is thinking about tax forms: who was paid, and whether the client holds the details of the people they paid.
The second is where practices lose their Januaries. A client paid eleven people and holds four completed taxpayer identification forms. The other seven have to be obtained now, in the third week of January, from people who have already been paid in full and have no reason left to answer an email from an accountant they have never met. That is the hardest chase in the practice’s year, and it is hard for a structural reason rather than a personal one: the only moment when anybody had any pull was the moment before the money moved.
Which makes the repair a standing rule at the client rather than a campaign at your end. No first payment to a new payee until the form is on file. That sentence is a bookkeeping instruction, it belongs in a conversation in June, and it converts an eleven-message January into nothing at all. It is also the kind of thing a firm says once, hears agreed, and never checks; the check is a two-line question in the autumn asking how many new payees there have been and how many forms are held.
What the mailbox genuinely owns on this side is smaller and more concentrated.
There is the approval loop, which is the most consequential exchange of the month. Before anything is filed the client has to confirm the list of recipients and the amounts, because a filed form is a good deal harder to withdraw than an unfiled one is to prepare. That message wants the list in the body where it can be read on a phone, a plain request to confirm or correct, and a date attached at the moment it goes out rather than when it starts to feel late. The date is not negotiable and it is not far away, which is one of the few times in a practice that a firm chase in the first week is simply correct.
There is the classification question, and it never arrives as a question. It turns up as one sentence in the middle of a message about something else, in the third week of January: do we need to do one for the man who redid the office. That is not an email to be answered in the thread. It is an advice question with a hard deadline behind it, and what the mailbox owes is catching it as a dated item on the day it lands rather than letting it be handled as the fourth paragraph of a reply about something unrelated.
And there is the furnishing run, which is the part that gets forgotten because it looks like nothing. The forms have to reach the people named on them as well as the agency, and where the practice is the one sending them, that is an outbound mail run to a list of strangers, from an address they do not recognise, in the busiest fortnight of your year. The bounces from that run are the important output and the one nobody reads. A bounce there is not a nuisance; it is a copy that did not get furnished, and it belongs on the list of things you are waiting on rather than in a folder of delivery notifications.
The form that arrives after the work is done
There is one more property this class has and no other document in the practice shares. It gets corrected, routinely, after everything is finished.
A broker revises a consolidated statement in March. A payer discovers an error and reissues. The corrected form arrives weeks after the return was prepared, sometimes after it was filed, and it arrives as an ordinary email from a client whose work is complete.
That is a mailbox problem before it is a tax one. When a job is finished it drops off every list in the firm. It is out of the workflow system, off the preparer’s desk, and out of everybody’s head, which is the entire purpose of finishing it. A message about that client now has nowhere to land, and the fact that their return is done is exactly why the message gets a quick reply rather than a proper reading.
Three things make it survivable, and the first is written in January.
Tell the client, in the message that delivers the finished return, that a corrected form may still arrive and that it should be sent on without their deciding whether it matters. That sentence costs nothing, it goes into the delivery template once, and it converts a client who quietly files a corrected form in a drawer into a client who forwards it. Most of the exposure here comes from corrections that were received by the taxpayer and never reached the practice at all.
Second, whether a correction is worth acting on is a judgement with a threshold, and it belongs to somebody who is allowed to make it. The failure mode is not a firm deciding wrongly. It is a corrected form being read by whoever opened the message, filed as noise because the return has gone, and never put in front of the person who would have recognised the number.
Third, the correction that arrives before filing is the cheap one, and it is the one most likely to be missed, because everyone has already stopped watching that client. A firm with a lot of brokerage clients usually knows this and holds those returns for a while. That is a decision about when work is released rather than about mail, but the mailbox is where the evidence for it shows up.
Where does Point fit?
Every part of this ran on a spreadsheet and a telephone long before software offered to help with any of it, and a careful firm can still run it that way. A tool changes only which half of it a person has to carry. The list of expected forms, the threshold on a correction and the decision about who is a contractor stay exactly where they are.
Three of Point’s capabilities do most of the work on the collection side.
Attachments come out of the threads they arrived in and gather into one place, dated, each still joined to the message that brought it. That is the raw material of the heap-against-list problem: a delivery of fourteen photographs stops being fourteen photographs inside a conversation and becomes fourteen items you can work through.
You can put a question to a document and get an answer with a pointer to the page it came from, which in this class is more useful than anywhere else in a practice. Most of what a client sends you is a scan with no covering note, and the only way to know what a sixty-page statement contains is to read it. Asking it which forms are inside, and being shown where, is the shortest route from arrived to matched.
And a standing request covers the named form you are actually waiting on. Ask to be told when a particular client’s consolidated statement lands and you hear once, on the day, instead of looking. Against a class of documents whose arrival dates are published in advance, that is close to the whole discipline: set the watch in January, then stop thinking about it.
Waiting works here as it does for everything else the firm is owed. A request you sent stays visible with your own date on it and returns on that date, which for these forms comes off the day the payer had to post rather than the day you asked. If the thing has already come in, the reminder marks itself as likely settled and sits there until you say so, so nobody chases a statement the morning after it arrived. And an ask sitting halfway down a long message becomes an item with a date on it, with nobody lifting it out by hand, which is the shape the January classification question always takes and very often the shape of the March correction too.
The ranking matters most in the fortnight when the volume is worst. Point grades each message on two questions, how much it matters and how soon it needs you, rather than on when it turned up, so a client’s confirmation of the amounts to be filed is not underneath two hundred deliveries, and a bounce from a furnishing run is not underneath anything. What that grading actually measures is a subject of its own. A one-line summary sits on every thread, and against this class of mail that line is usually all you needed: what the attachment is, and which year it covers.
Drafts come back sounding like you, so the acknowledgement naming which expected lines a statement just closed is an edit rather than a composition. Every kind of action carries its own setting for how much Point finishes on its own, and all of them ship at review: the work is done, then it waits. The dial covers that setting properly. Acknowledging a delivery is the first one worth raising. Anything touching what gets filed is not, and the message asking a client to confirm the amounts wants somebody reading it before it goes, every year. Each action lands in a log, in order and timed, and the log is also where you take one back. The exception is the one no mail software gets around: a message already sitting with the person you sent it to.
Nothing has to move for any of it. Point signs in to the account the firm is already on, Google or Microsoft, and the address at the top of your January letter is unchanged.
What Point does not have is the count. It holds no list of expected forms, it has never seen last year’s return, it cannot certify one form type against another, and it has no view on whether eleven payees have eleven completed forms behind them. It files nothing with anybody. Those are the judgements this job is actually made of, and they do not move. The complete list of what Point does sits on the benefits page; Point for accountants is the same list arranged around a firm’s year. Whether a tool should be reading mail with client tax documents in it at all is a prior question, and what a firm should satisfy itself about first is where that one is settled.
Common questions
When should we chase a client for a missing W-2 or 1099?
Not from the day you asked, which is the habit carried over from every other request, but from the day the form was due to be posted to them. Before that date there is nothing to chase and a reminder does active damage, because it teaches a client that your dates are approximate. After it, the useful message is a question rather than a nudge: has it reached you, and if not, is it going to an old address or sitting behind a login. For brokerage statements the date is later than most clients expect and later than most firms remember, which is why a February chase on one of those is usually wrong.
How do we know a client has sent us everything?
You cannot get that from the mailbox, and you cannot get it by asking, because the client does not know either and will say yes. It comes from last year’s return, which lists every payer that reported, and from a short set of questions about events rather than about paperwork: jobs changed, accounts opened or closed, money taken out of a pension, anything sold, work done on the side, money received through an app. Send the list of last year’s payers in January and ask what is gone and what is new. That single message fixes the number you are counting against, and everything else in the season is measured against it.
Would a scanning or auto-import tool solve the 1099 pile?
It solves the half you can see, which is worth having. Reading a form and getting the numbers onto a return without typing is real work removed, and the tools are good at it. What none of them can do is the half this guide is about: a tool that reads what arrived has no opinion about what did not. It cannot know that this client had two employers rather than one, that an account was closed in June, or that a statement is still to come from a broker who has taken the extension. The pile is not the problem. The gap between the pile and last year’s payer list is the problem, and that stays a reconciliation somebody has to hold.
A client asks in January whether they need to issue a 1099 to somebody. What does the mailbox owe?
Only two things, and both are about handling rather than about the answer. Catch it, because it will not arrive as a question; it will be one sentence inside a message about something else, and the deadline behind it is a fortnight away. And take it out of the thread, because it is advice with a filing date attached rather than a reply to be written at the bottom of a message about bank statements. Then, if the answer is yes and the client does not hold the payee’s details, the honest thing to say is that this year will be awkward and next year does not have to be: no first payment to a new payee until the form is on file, agreed in June rather than in January.
A corrected form arrived after we filed. Whose problem is that in the mailbox?
Structurally it is nobody’s, and that is the whole difficulty. A finished return has left every list in the firm, so a message about it lands with nothing watching for it and gets answered quickly rather than read carefully. Three habits cover it. Say in the delivery message that a corrected form may still turn up and should be forwarded without the client judging whether it matters, since the corrections that never reach you are the expensive ones. Make sure a correction reaches somebody allowed to decide whether it moves anything. And remember that the same form arriving before you file is the cheap version and the one most likely to be missed, because by then nobody is watching that client either.
The short version
W-2s and 1099s cover two jobs that share a word: the forms your client receives, which you collect, and the forms your client has to issue, which you produce. Sort every message by which one it is before anything else, because the deadline, the cost of being late and the meaning of finished all differ. On the collection side, nothing can be chased before it exists and the issue dates are published, so the instrument is a calendar of expected arrivals rather than a chase list, and January’s most useful message tells the client what is not due yet. Then hold a count, because the real question is whether all of them came, and the only list worth reconciling against is last year’s payers plus what changed. Match deliveries on arrival rather than at preparation, and acknowledge which expected lines a statement closed. On the issue side, the month is decided by whether the client holds the details of everyone they paid, which is a rule agreed in June rather than a chase run in January, and the furnishing bounces matter as much as the filing. Finally, expect a corrected form after the work is done and decide in advance who reads it. What all of this feels like from inside a firm living through the weeks rather than as a method is told in tax season without the inbox spiral, each of the practice’s other repeating jobs is taken on its own terms elsewhere in this collection, and the buying question is worked through in AI email for accountants.