To e-file a client's extension, check selections, clear diagnostics, follow the applicable authorization process, then validate, send, and confirm the result. Those four steps cover the extension work most offices do in a season, whatever software they use.
When a client needs more time, the extension is one of the simplest forms your office sends all season. That simplicity is what makes it easy to get wrong. A form can look finished on screen and still fail validation. The right client can have the wrong extension box checked. Partners and operations leads are often the people who catch these problems after the send, when they are hardest to fix.
Keep signature authorization and payment handling separate, because the payment question comes up again in Step 3.
Most of these problems come from a skipped small step rather than a hard tax question. The four steps below are built around that. The first two make sure the right form is ready. The last two address the applicable authorization process and make sure the send actually goes through.
The steps are general, and every product labels things a little differently. Treat them as a checklist, and open your own software's help pages for the exact screens. This guide is written for the preparer who sends the extension and for the partner or operations lead who reviews the outcome.
Step 1: Confirm the client and the extension selections
Start with the client, not the form. Open the return for the client you intend to extend. The name on the extension has to match the name on that return. A mismatch is easy to miss when two returns from the same household, or a prior-year copy, sit open side by side. If you are working from a prior-year copy, treat it as a source of questions, not as an answer.
Next, look at which extensions are selected. The Intuit help article for Lacerte tells you to verify that the client name is correct and that the correct extensions are selected under Federal and State Extensions when they apply, and then choose Next ( Intuit, "File extensions in Lacerte").
The words "when they apply" carry weight in that sentence. Lacerte lists selections under Federal and State Extensions. A client can need one without the other, and a state box checked out of habit can be as wrong as a federal box that was missed. Read each box on the screen rather than trusting what appears by default, and treat each one as its own decision.
Think about what the client actually asked for, too. If the client said they needed more time to gather documents, the extension should match that conversation. If the request is unclear, settle it with the client before you open the software, not after the form is already set.
A useful test is to imagine explaining each box to the client. If you could not explain why a box is checked, it is not ready.
One practical habit is to split the work. One person sets the selections, and a second person reads them back against the client file before anything is sent. The second read gives someone else a chance to question the selections. It is cheap, and it catches the errors that are hardest to spot after you have stared at the same screen for an hour. Busy weeks are when the second read gets skipped, and those are exactly the weeks when it matters most.
Carryover from last year saves time, but it can also carry an old choice into a new season without anyone noticing. A familiar selection deserves the same attention as a new one, because it is the one most likely to slip past.
Clients sometimes change their minds about the extension after the selections are set. When that happens, reopen the selections and read them again from the top, rather than editing one box and moving on.
Clients with more than one extension need extra care. Give each extension its own pass through these steps, with the client name, the federal box, and any state boxes written out in front of you. When one client has a federal extension and a state extension, or two separate forms, it is easy to finish the first and assume the second followed.
Step 2: Clear the extension diagnostics and validation errors
Before you send, read the e-file critical diagnostics, and give special attention to any that reference the extension. Diagnostics are easy to dismiss when the return looks right on screen, especially when the message seems to point at another part of the return. A diagnostic that names the extension is the software pointing at the form about to leave your office, so read it as a message about that form.
Not every message is critical, and it is tempting to treat a non-critical one as optional. Read those too, and decide on purpose whether each one is safe to leave alone. A decision made deliberately is different from a message scrolled past.
It helps to sort messages by type before you act on them. A message about a missing entry usually points to a blank field on the return. A message about the form itself usually points back to the extension selections from Step 1. Some messages will not make sense on first read. Rather than guessing, find the field the message names and look at what is entered there.
Validation errors are a separate problem. If you get one when you try to e-file the extension, make sure the extension is generating on the Forms tab. If the form is not generating there, fix that before you try the send again. Repeating the same send without a change only repeats the problem.
Do not change things you do not understand just to make a message go away. A change made only to clear a warning can create a new problem somewhere else on the return. Clearing a diagnostic should mean you know what it said and why the form is now correct.
If a message returns after you cleared it, the earlier fix did not hold. Look at what changed in between, rather than clearing the same message a second time.
Timing matters too. Set aside time for diagnostics when you schedule the extension work. A rushed hour is when messages get dismissed, and an unhurried hour is when they are read properly. Clear diagnostics as you prepare each extension, not at the end of a long batch. A batch can hide one repeated problem across many files, so where your software allows, work in smaller groups.
When the same message keeps appearing across several clients, stop and find its cause before you clear the next one. A message that repeats often points to a shared setting or a habit in the process. Fixing that cause protects the files that have not been opened yet.
Step 3: Collect the client's signature authorization when applicable
If your client's extension uses the self-select PIN process, the IRS guidance on that method for Forms 1040 and 4868 sets out how the authorization form is handled ( IRS, "Self-select PIN method for Forms 1040 and 4868 Modernized e-File (MeF)"). That page is the reference to cite when someone asks what the client signs and how the form moves between the client and your office.
The table covers that self-select PIN method for Forms 1040 and 4868; do not apply its authorization steps automatically to other extensions, such as Form 7004 in Step 4.
| Part of the process | IRS self-select PIN guidance | What your office should do |
|---|---|---|
| Give the client the form | Provide Form 8878/8879 with a copy of the completed return or tax document, in person, by U.S. mail, by private delivery service, by e-mail, by fax, or through an internet website | Pick a route the client can actually use, and make the choice early |
| Client completes the form | The client reviews the return, then supplies the date, a pen and ink signature, and a five-digit PIN | Let the client complete those entries |
| PIN choice | Any five digits except all zeros | Let the client choose, and keep the choice inside the rule |
| Client returns the signed form | If the client cannot return it to your office, the client may return it by mail or fax | Ask early which return route works for the client, and keep the signed copy with the return |
| Payments | Form 8879 should not be used to transmit any payments | Keep any payment on its own track, separate from the signature form |
Start with the first row. The copy of the return you attach is the document the client is authorizing, so it should be the same version you plan to transmit, not an earlier draft. That matching copy lets the client see exactly what they approve.
For an extension using this self-select PIN process, collect the signed authorization before transmission. An extension that goes out ahead of the signed form is the situation the opening of this post warned about, and the fix then happens after the send, when it is hardest to make.
The client completes the form fields. A blank date or a missing signature is easy to overlook when the rest of the page looks finished, so look at every field before the form goes into the file. If a form arrives with a blank field, send it back to the client rather than completing it yourself.
The office's job is to keep that choice inside the rule and to avoid picking it for them. Remind clients that the PIN is theirs to set and keep to themselves.
When you ask a client to sign, explain in a sentence or two what the form is and why it is needed. A client who understands the step is more likely to return the form promptly and to read the return before signing. For related checks, see the guide to signature rules before you e-file.
Follow-up is part of the process. Tell the client early when you need the form back, and say what happens if it is late. A client who knows the timing is more likely to return the form in time, and you avoid a rushed send later in the week.
Ask clients early which route works for them, so the fallback does not become the default. When a form comes back that way, the authorization and the return should stay together.
Payments need their own handling, and mixing the two makes later questions harder to answer. If a client is paying along with an extension, do not treat the signature form as a payment record.
The person who sends the form does not have to be the person who receives it back. Pass the signed form on together with the copy of the return, rather than separately, so the next person can read both at once.
Step 4: Send the extension and confirm the result
Once the diagnostics are cleared and any applicable authorization steps are satisfied, you can send. In Lacerte, once the extension is validated, select Send e-file Returns Now. If the extension has not validated, the send step is not the place to find out why.
Before you press the button, go back through the first three steps. The client name, the federal and state boxes, the cleared diagnostics, and any required signed authorization should all be in order. If any item is missing, hold the extension and fix the gap. Holding one extension briefly is easier than explaining a bad one to a client or a reviewer.
If the software will not transmit the extension, resist the urge to change the return's data until something sends. Keep the message you saw in front of you, leave the file as it is, and work through the help pages first. Changing data to force a send is how one problem becomes two, and it makes the file harder to follow later.
When a transmission is rejected, read the reason the software gives before you change anything. Rejections are often easier to fix than they look, but only once the cause is clear. Fix the cause, then send again through the same steps.
Partnership returns can need more than one extension form. In Drake, the 7004 screen for a Form 1065 return has a box labeled "Send additional extension form…" that lets you e-file an additional extension form ( Drake Software, "Drake Tax - 1065: Extension Form 7004"). If you are working on a partnership extension, open that screen before you mark the job complete. Do not assume the second form inherits the first form's settings. Each one has its own selections, so check the additional form's client name, selections, and diagnostics too. See also the guide to business extension checks before transmitting.
Handoffs matter at this stage. When one person prepares the extension and another sends it, the sender should know what the preparer cleared and what remains open. A short message that lists the cleared diagnostics, the authorization status, and any open question is enough. Without it, the sender either repeats the work or assumes it was done, and both outcomes waste time in a busy stretch.
After you send, read what your software reports for the transmission and save that result to the client file. If the result is not what you expected, go back to the diagnostics and the applicable authorization steps before you resend anything.
Once an extension is sent, the work is not finished for the client either. Tell them what was filed and what is still open, such as a payment, so they are not left wondering whether the extension went through.
Partners and operations leads see patterns that no single preparer can. If the same gap shows up on several files, change the process instead of asking people to try harder. Pay attention to which step caused the most trouble this time, and give that step the most attention next time.
Vendors describe these screens differently, and menus and labels change from year to year. That is why the four steps work best as a framework rather than a script. Update your office's version whenever your software changes, and share it with everyone who sends extensions.
Start with your next extension, and walk a single client through the four steps from beginning to end.
This is general guidance, not legal or tax advice.
Tracking returns this season? Tax Season Return Status Board gives each return a row with its preparer, its stage, the days it has sat in that stage and past deadline or due soon flags.