Tax engagement letter e-signature: how to get letters signed before work starts

A tax engagement letter e-signature workflow sends every client’s letter in one batch in December, records each signature with a timestamp and IP address, and shows on any given morning which letters are still unsigned so that staff chase those and only those. It covers the engagement letter and the consents that travel with it. It does not cover Form 8879, which the IRS treats differently when it is signed away from the office, and a firm that blurs the two ends up either over-securing a routine contract or under-securing the one form that has rules.

Most of what ranks for engagement letter e-signature for accountants is a letter template, or a help page for one tax suite’s e-sign button. Both stop at the moment the letter leaves the firm. This page starts there, because the letter leaving is the easy part. The problem in the second week of January is the pile of letters that left and never came back, and the returns that got started anyway.

Why do so many engagement letters go unsigned?

Because nothing in the client’s week depends on signing one. A W-2 arrives and the client knows they need to do something with it. An engagement letter arrives in early December, three weeks before any form exists, and reads as a formality from a firm they already trust. It gets opened, skimmed, and left in the inbox for the day the documents are ready.

The firm’s process usually makes that worse. The letter goes out as a PDF attachment to a mass email. Signing means printing, signing, scanning and replying, or finding the right button in an e-sign email that landed in a different thread from the one the organizer came in. The organizer, the letter and the consent form each arrive by a different route, so the client does the one that feels urgent and drops the rest.

Then busy season starts and the return gets opened whether the letter is back or not. A preparer with sixty returns in the queue is not going to check a spreadsheet before starting each one, and the firm discovers the unsigned letters in April, when a fee dispute or a scope question surfaces and someone goes looking for the signed copy.

None of the fixes are about the wording of the letter. They are about how it is sent, what it is sent with, what the firm can see after it goes out, and what happens on day eight when it is still open.

How to build the engagement letter and organizer into one send

Start by listing what the client has to do before the firm can begin, and put all of it in one place.

For an individual return that is usually four things. Sign the engagement letter. Sign the Section 7216 consent, if the firm uses client information for anything beyond preparing the return, since that consent has required wording under Rev. Proc. 2013-14 and needs the taxpayer’s own signature. Answer the intake questions that decide what this year’s return needs. Upload the documents, as they arrive, against the list those questions produce. The tax document checklist for clients covers how that list is built and worded.

For a business client, add the entity’s engagement letter, signed by whoever has authority, and the bookkeeping or payroll documents that a Schedule C or an 1120-S needs.

The rule is one link per client that holds all of it. The letter is the first item in the link. The consent is the second. The questions and the document list come after. When a client opens the link on their phone in December, the first thing they see is the letter with a signature field, and the second is the organizer. They do both in one sitting because both are in front of them. A firm that sends the letter through an e-sign tool and the organizer through a portal is asking the client to make two trips, and most clients make one.

One signature per document, not one signature covering a stack. The AICPA professional liability program’s guidance on e-signatures for engagement documentation is direct on that point: if multiple documents require a signature, put an e-signature on each, so that there is never a question about which document was agreed to. The letter and the consent are separate agreements with separate signature events, even when they sit in the same link.

Joint returns need both spouses. An engagement letter signed by one spouse for a married-filing-jointly return leaves the other spouse outside the agreement, and a fee or scope dispute with the unsigned spouse has no letter behind it. The link should carry two signature fields, one for each taxpayer, and the letter should not count as signed until both are in. A firm that has always taken one signature on joint returns should fix that this year, because the e-sign record makes the gap visible in a way a paper file never did.

Build the whole thing as a template. One for a standard individual return, one for individuals with a Schedule C or rental property, one for entities. Each template holds the letter, the consent, the questions and the document list, with the signature fields already placed. Spinning up a client’s copy in December is then a matter of picking the template and filling in the fee, and the firm sends three hundred letters in an afternoon rather than three hundred separately assembled emails.

How to send every engagement letter before busy season

The send has a date, and the date is before the forms exist.

The week after Thanksgiving is right for most firms. The client has nothing to upload yet, and that is fine. What they have is the letter to sign, the questions to answer, and a place to put each form the week it arrives. A letter that goes out in the second week of January, when W-2s are already landing, competes with the documents for the client’s attention and loses.

Send it by email and by text at the same time, from the same link. The email carries the fee, the scope and the deadline in a paragraph. The text carries one sentence and the link. The two channels reach different parts of a client’s attention, and the comparison of SMS and email for document requests goes into when each wins. For a signature request in December, the text is what gets the letter opened, and the email is what the client reads once they have.

The client signs in to a Customer account with a verified email matching the firm’s Client record, then opens the link to read the letter and draw or type a signature. No app download is needed, and the next item appears in the same workflow. The link names the letter and its signer seat; the account and verified email establish who may use it, while the signing record captures the signature event.

Put the fee on the letter, and put the internal deadline on it too. “Documents received after March 20 go on extension” in the letter, and again in the link, sets the expectation in December, when the client is calm, rather than in April, when they are not. A firm that already runs a July calendar for returns on extension will know how much easier that conversation is when the date was agreed in writing four months earlier.

How to track who has signed and who has not

A tax engagement letter e-signature is only useful to the firm if the firm can see it. The state of the letter is the state of the client, and it needs a place to live.

Four states cover it. Sent, meaning the link went out and nothing has happened. Opened, meaning the client has looked at the letter, which matters because an opened-and-unsigned letter is a different problem from an unopened one. Signed, meaning every required signature is in and the record is complete. Questioned, meaning the client replied with a question about the fee or the scope instead of signing, and a person at the firm owes them an answer before anything else moves.

That last state is the one spreadsheets never have, and it is where a share of unsigned letters sit. A client who wants to know why the fee went up is not refusing to sign. They are waiting for a reply, and every automated reminder they receive in the meantime reads as the firm not listening. The tracker should stop reminding that client the moment they reply, and it should show the question to whoever sets fees.

The record behind a signed state is what the firm will need if the letter is ever contested. The guidance above says that documentation retained by the signature system supports enforcement, and that a firm signing without one should fall back on time records and email logs, which is a much weaker position. The record to keep is the timestamp, the IP address and browser from which the signature was placed, and the per-field event log showing each signature and initial as it was added. The view that matters in January is the list, sorted by state, filtered to unsigned. On January 6 it might show two hundred and twelve signed, forty-one opened and unsigned, nineteen never opened, and six with questions. That is the morning’s work, and it is not two hundred and seventy-eight phone calls. It is nineteen texts, forty-one nudges, six replies from a partner, and no work started on any of the sixty-six.

The tracker should also show the signature and the documents on the same row. A client who has signed but uploaded nothing is on track in December and behind in February. A client who has uploaded nine forms and not signed is the case in the last section. Both are visible only if the letter’s state and the document list’s state sit together.

How to chase unsigned engagement letters without losing the client

The chase is where a firm’s tone is set for the year, so it should be planned rather than improvised.

The first reminder goes on day three, by text, one sentence: the letter is waiting, here is the link. Most of the never-opened group signs after this one, because the original email was buried and the text is not.

The second goes on day seven, by email, and it names the consequence. “We start returns in the order letters come back, and we cannot open yours until it is signed.” That is true, so it should be said. A client who learns that their place in the queue depends on a signature signs.

The third is a phone call, on day fourteen, from the preparer who will handle the return. Not from the front desk. The client who has ignored two reminders has usually decided something, and the call is to find out what. Sometimes the fee. Sometimes the client has moved firms and did not say so. Sometimes the link went to a phone number the client stopped using in August, which the firm learns now rather than in March when a document request goes to the same dead number.

Every reminder should come from the list of letters still unsigned, generated that morning, so that a client who signed on Tuesday night does not get chased on Wednesday. Being reminded about something you already did is the fastest way to stop reading a firm’s messages, and one wrong reminder in January costs a February of ignored document requests.

The cadence stops when the letter is signed or when the client says no. A no is a fine outcome in January. It is a terrible outcome in April, after the return is half done.

The hours this costs are the same hours the firm already loses to chasing documents. The AICPA Practice Management Survey puts document chasing at 30% or more of a tax firm’s season, and an unsigned letter is one more item on the same chase list. The hidden cost of chasing clients for documents works through what that share means in hours for a firm of a given size.

Is an e-signed tax engagement letter binding?

Yes. A tax engagement letter e-signature is binding, and the source of that is statute rather than a vendor’s assurance. The federal Electronic Signatures in Global and National Commerce Act, in force since 2000, provides that a signature or contract may not be denied legal effect solely because it is in electronic form, and every state has adopted the Uniform Electronic Transactions Act or its own equivalent. The AICPA program guidance linked above states the practical version: e-signatures are binding and comparable to a wet signature for proving validity, enforceability and admissibility if the letter is ever litigated.

The same guidance is careful about the word “if.” An e-signed document can be enforced, and enforcing one can be more involved than producing a signed piece of paper, because the firm has to show that the person who signed was the client. That is why the record matters more than the signature. A signature image alone proves that someone drew a line. The timestamp, the address and the event log prove when and from where, and the fact that the link went to the client’s own phone and inbox is what ties the line to the person.

Two practices the guidance recommends fit the workflow above without changes. Time the signing close to the conversation about the engagement and before any work begins, which is what a December send does. And have the client review everything the letter refers to, including any standard terms that live behind a link, which means the terms should sit in the same place as the signature field rather than on a separate page the client never opens.

What the engagement letter does not require is any identity check beyond that. There is no statutory knowledge-based authentication step for a service contract, no requirement to capture a login name, and no IRS involvement at all. A firm that runs its engagement letters through the credit-bureau identity quiz its tax software uses for the 8879 is adding friction that the letter does not need, and every added step in December is a letter that does not come back.

Can Form 8879 be e-signed the same way?

No, and this is the boundary that a tax firm’s e-signature workflow has to draw out loud, because the two documents look alike from the client’s side and are governed differently.

Form 8879 is the declaration document and signature authorization for an e-filed return filed by an electronic return originator, in the IRS’s own words. The taxpayer signs it to authorize the ERO to enter their PIN on the e-filed return. It is not a contract between the client and the firm. It is the taxpayer’s signature on the return, held by the preparer, and the IRS sets the rules for how that signature may be taken.

Those rules are in IRS Publication 1345 and the IRS e-file signature authorization FAQ. For a remote transaction, where the taxpayer is not physically in the ERO’s office, the taxpayer’s identity must be verified before the e-signature, and the verification the IRS describes is knowledge-based authentication: the software runs what the credit industry calls a soft inquiry and asks the taxpayer multiple-choice questions such as the name of their mortgage lender, the type of car they financed, or a former address. The e-signature record must then capture the digital image of the signed form, the date and time of the signature, the taxpayer’s IP address, the taxpayer’s login identification, the result of the identity verification, and the method used to sign. The ERO keeps that record, tamper-proof, in access-controlled storage for three years.

In person, the rules relax. When the taxpayer signs in the ERO’s presence, the identity verification is waived for a taxpayer with a multi-year business relationship, which the IRS defines as one whose returns the ERO has originated for a prior year after identifying them. A returning client who walks in and signs on a tablet in the office is covered. The same client signing the same 8879 from their kitchen is not, unless the software ran the quiz first.

The map for a tax firm is this. The engagement letter, the 7216 consent, the fee agreement and the organizer questions are ordinary agreements and go through the firm’s own signing workflow with the record described above. The 8879 goes through the tax software’s e-sign product, which runs the knowledge-based authentication the IRS requires, or it is signed in the office. A firm that routes the 8879 through a general e-signature tool with no identity quiz has a signature the IRS will not accept for a remote transaction. A firm that routes its engagement letters through the 8879 tool is paying per envelope, in December, for a quiz that its clients then fail on the mortgage lender question and call the office about.

Letters and consents in December, through one link, with no quiz. The 8879 in March or April, through the tax software or in person, with the quiz. Written down once, the two workflows stop colliding.

What happens when work starts and the letter is still unsigned?

The firm has to decide this in November, because in February it will be decided by whoever is busiest.

The clean rule is that no return is opened until the letter is signed. It is easy to state, and the letter is the document that defines what the firm agreed to do and what it did not. It also has a cost: a preparer with a free morning and a client who has uploaded everything except a signature loses that morning.

The workable version is that the letter’s state is a blocker on starting, visible to the preparer, that a partner can override with a note. The preparer sees “letter unsigned” on the return and does not open it. If the client is a twenty-year relationship whose letter is sitting in a spouse’s inbox, the partner clears the block, the note says why, and the letter is chased alongside the return. If the client is new, or the fee changed, nobody clears it, and the return waits.

Whichever version the firm picks, the state should be visible where the preparer works, on the return, not in a separate spreadsheet that nobody opens in February. And the signed letter should be a blocker on delivery even if it was not a blocker on starting. A return that goes out the door with no engagement letter behind it is the one that becomes a problem, and delivery is the last point at which the firm can catch it.

The uploaded-but-unsigned case deserves its own mention, because it is common and it feels like progress. A client who uploaded nine documents and skipped the signature is engaged and responsive. They are also, on paper, not a client. The reminder to that client should be short and specific. “Everything is in, thank you. One thing left: the letter needs your signature before we can start, here is the link.” That message gets signed the same day, and the return opens.

The tax preparer solutions page shows what the single link looks like for a firm running individual and small business returns, and the accounting firm version covers the same setup for a firm with entity and bookkeeping clients. The tax document collection guide for CPAs picks up where this page ends, with the documents themselves.

Where zendoc fits in e-signatures

zendoc puts the engagement letter, the 7216 consent, the intake questions and the document list in one workflow template, spins up one copy per client, and sends each client a single link by SMS and email. The client signs in to a Customer account with a verified email matching the firm’s Client record before opening that link on a phone. The letter is a document with signature, initial and date fields placed on the firm’s own PDF, one signature event per document, and every signature is recorded with a timestamp, IP address, user agent and per-field event log that downloads with the flattened PDF. The status view shows every client’s letter and document list together, a client with anything still open gets one grouped reminder three days after the first notice, and staff can see on any morning which letters are still open. It has no knowledge-based authentication step, so a remotely signed Form 8879 stays with the tax software or an in-person signing, as the section above describes.