No. Forms 1099 that are e-filed do not require a paper-filed 1096, because the transmission file already contains all the information a 1096 would supply. Drake Accounting builds this transmission file when you create your federal 1099 e-file.
- The transmission file carries the form counts and filer identification a paper 1096 would provide.
- The file location appears as a clickable hyperlink at the bottom of the Federal 1099/1098 Create File screen.
- Prior-year e-filing is available for all Forms 1099/1098 in DAS, so prior-year batches follow the same no-1096 rule.
- The cover-sheet question attaches to the route: e-filed batches need no paper 1096.
- Keep the transmission file with the client's records as the record of what was transmitted.
Do your client's e-filed Forms 1099 need a paper 1096?
That is the short answer you came for, and it comes directly from Drake Software's own knowledge base article on generating, processing and e-filing Forms 1099-MISC and 1099-NEC in Drake Accounting.
If you run a client's 1099 batch out of Drake Accounting and send it through the federal e-file channel, you can stop budgeting time to print, sign and mail a paper cover sheet. The transmission file stands in for it.
This post walks through how that works inside Drake, where to find the file, what applies to prior-year filings, and what to keep in mind when a batch mixes e-filed and paper-filed forms. The goal is simple: you should know, before you hit send, whether paper will follow.
How Drake Accounting builds the transmission file
Drake Accounting builds a transmission file for your federal 1099 e-file right from the Federal 1099/1098 Create File screen, and it shows you where that file landed. The knowledge base article explains: "The location of the Federal e-file will then display as a clickable hyperlink at the bottom of the Federal 1099/1098 Create File screen."
The reason a single file does the work of two forms is worth spelling out. When you e-file, all of that identifying and counting information rides inside the electronic file itself. The knowledge base puts it plainly: "The 1099 transmission file contains all the information that would be supplied by a 1096."
So the file is doing double duty. It carries the summary-level information the 1096 would have provided on paper. Nothing is lost by not printing the 1096. Nothing is missing from the package the IRS receives.
For operations staff this changes the physical workflow. Instead of a stack of forms, a cover sheet, a signature, and a trip to the mailbox, you have one file sitting in a folder on your machine, ready to transmit. The folder path Drake gives you is a concrete one; the knowledge base walks through an example path: "browse to this PC > C drive > DrakeAccounting22/DAS2022data/Client >/efile/federal/1099." Check the path shown on your own screen or in your own version rather than assuming it matches the example.
Where the file sits on disk
The clickable hyperlink at the bottom of the Create File screen is the quickest way in. If you prefer to navigate by hand, follow the descent: the DrakeAccounting data folder for your installed year, then Client, then efile, then federal, then 1099.
Knowing the path matters for two practical reasons. First, you can hand it to a colleague who is picking up the batch. Second, you can confirm the file exists and has a fresh timestamp before you transmit. A stale file from a previous run is the kind of thing you want to catch before it goes out, not after.
Keep in mind that the folder name carries your installed version year. The example path shows that the data folder name includes the year, as in DAS2022data. If you go looking in last year's folder and find nothing, the file may be in the current-year folder instead.
What the transmission file carries instead of a 1096
The transmission file carries the same information a paper 1096 would carry. That is the whole substitution: one file, two jobs.
Think about what a 1096 actually contains when you file on paper. In the electronic route, the count of each form type, the filer identification, and the transmission-level details are all contained in the transmission file. The knowledge base's statement that the file "contains all the information that would be supplied by a 1096" is the authority for this — the file is designed to replace the cover sheet, not merely to accompany it.
This has a knock-on effect on how you review a batch before sending. On paper, your quality check is visual: you hold the 1096 up, read the counts, compare them to the stack. Electronically, your check happens on screen. You review the Create File screen, confirm the forms included, and confirm the file location hyperlink. The review point moves from a printed page to a screen, but the substance of what you are checking does not change: the right forms, the right counts, the right filer.
It also affects what you archive. A paper file keeps a signed 1096 in the client folder as proof of filing. With an e-file, the transmission file itself is the artifact you keep. Store it alongside your client's records, note where it lives, and note when it was transmitted. If a question comes back later about what went out, the file answers it.
A small comparison of the two routes, built from what the knowledge base states:
| Step in the workflow | Paper-filed Forms 1099 | E-filed Forms 1099 |
|---|---|---|
| Cover sheet (Form 1096) needed | Yes | No |
| Where the cover-sheet information lives | On the printed 1096 | Inside the transmission file |
| Where you find the output | Printed forms and 1096 | Clickable link at the bottom of the Federal 1099/1098 Create File screen |
| File location example given | Not applicable | This PC > C drive > DrakeAccounting22/DAS2022data/Client >/efile/federal/1099 |
| Statement from the knowledge base | — | Forms 1099 that are e-filed do not require a paper-filed 1096 |
Prior-year 1099 e-filing in Drake Accounting
Prior year e-filing is available for all Forms 1099/1098 in DAS. That sentence from the knowledge base covers the whole family of forms handled in Drake Accounting's 1099/1098 module — you are not limited to a subset when you are working a prior-year file.
The practical value of this is that your prior-year workflow looks the same as your current-year workflow. You generate the forms, you create the file, you get the hyperlink, you transmit. The paper 1096 question resolves the same way: the batch is e-filed, so no paper cover sheet travels with it.
Where prior-year work differs from current-year work is in the setup and review, not in the cover-sheet rule. Before you build the file, confirm you are working in the correct prior-year data. Before you transmit, confirm the batch holds only the forms you intend to send. A prior-year batch often carries corrections alongside originals, so a deliberate read of the Create File screen earns its time.
One open point worth confirming with Drake's support team before you transmit: the prior-year flagging rules were not confirmed here and are worth asking about directly. If that detail matters for your client's situation, ask Drake directly rather than guessing.
Mixing e-filed and paper-filed 1099s in one client file
The rule you started with — no paper 1096 for e-filed Forms 1099 — governs the e-filed portion of a client's filing. A client file can still contain forms that go out on paper, and those paper forms follow their own path.
The clean way to think about it: the cover-sheet question attaches to the route, not to the client. A batch that leaves through the federal e-file channel carries its cover-sheet information inside the transmission file. A batch that leaves in an envelope needs the paper cover sheet that route calls for.
For operations leads, the useful habit is to decide the route for each batch, before you generate files. Splitting a client's forms into an e-file batch and a paper batch, rather than mixing routes inside one batch, keeps the bookkeeping honest. Each batch then has exactly one output: a transmission file for the electronic batch, printed forms plus cover sheet for the paper one.
When you split, watch the counts. The transmission file's value rests on carrying accurate summary information for what it transmits. Recount after the split, confirm the electronic batch on the Create File screen, and confirm the paper stack against its cover sheet. Three short checks, two clean outputs.
A walkthrough: one client, one batch, one file
Take a client whose 1099 batch you are ready to send through the federal e-file channel in Drake Accounting. The steps are short, and each one has a screen or a file behind it.
You generate the Forms 1099 for the client in Drake Accounting. You open the Federal 1099/1098 Create File screen. You create the file. The screen then shows a clickable hyperlink at the bottom of the Federal 1099/1098 Create File screen pointing to the file location.
You transmit the file. Because the batch is e-filed, you do not print, sign or mail a 1096. The transmission file already holds the information the 1096 would have supplied. You keep the transmission file with the client's records and note where it sits.
That is the entire loop for the electronic route. Everything that used to happen at the printer and the mailbox now happens between a Create File screen and a file folder.
Before you hit transmit: a short check
Run this once for each batch. It takes a minute and it catches the things that are expensive later.
- Route confirmed. This batch is going out electronically, so no paper 1096 will follow it.
- Batch contents confirmed. The forms on the Create File screen are the forms you intend to send for this client.
- File location confirmed. The clickable hyperlink at the bottom of the Create File screen points to the file location in the folder for your installed version.
- Prior-year status confirmed, if applicable. Prior-year e-filing is available for all Forms 1099/1098 in DAS, and you are working in the correct data year.
- Archival noted. You know where the transmission file will live in the client's records after it goes out.
Keeping the paper and electronic records straight after filing
Once a batch has gone out, two things need to stay findable: the transmission file itself, and a plain record of what it contained and when it went. A short note beside it — client, form types, count, transmission date — turns a folder of files into something you can answer questions from months later.
For paper batches, the signed cover sheet plays that same archival role. If a client file ends up with both kinds of batch, keep the two records visually distinct in the folder. One is an electronic transmission artifact, one is a signed paper artifact. Marking which is which saves the next person a decoding exercise.
The habit worth building is the handoff note. When a batch moves from the person who generated it to the person who transmits it, the note travels too: where the file is, what it holds, whether it is current-year or prior-year. The knowledge base gives you the location; the note gives your team the context around it.
What to do if a client asks why no 1096 went with the filing
Tell them the e-filed batch did not need one, and point to the reason: the transmission file already carries the information a paper 1096 would supply, so nothing was left out of what the agency received. That is the whole explanation, and it comes from Drake Software's own documentation for the product you used.
If the client's question is really about proof of filing, shift the conversation to the transmission file. Show them the file, the path it lives at, and your note on what it contained. That is the artifact your electronic route produces in place of a signed paper cover sheet.
If the client's question is about a form that went out on paper, the answer changes with the route. Paper-filed forms follow paper requirements. Keep the two routes clearly separated in your explanation so the client does not read one route's answer as applying to the other.
Closing the loop on your 1099 filing workflow
One file replaces the paper cover sheet. That is the operational fact this whole post hangs on: e-filed Forms 1099 do not require a paper-filed 1096, because the transmission file carries what the 1096 would have.
Build your workflow around it. Generate the batch, create the file, click the hyperlink, confirm the file, transmit, archive. Prior-year batches work the same way, since prior-year e-filing is available for all Forms 1099/1098 in DAS. Paper batches keep their own route and their own cover sheet.
The desk-side summary for your team: the cover-sheet question follows the route. Electronic in, no paper 1096 out. Paper in, paper cover sheet out. When the route is decided before the batch is generated, everything downstream stays simple.
Related guides: Paper or e-file for client reports: 7 steps to compare · Drake state notes: 5 checks before you e-file · E-file a client's extension: 4 software steps.