Skip to content
AI & Automation

CCH eSign vs DocuSign for Tax: Which Fits Your Firm in 2027

Nov 17, 2026

The short answer: pick by the tax software you already run

If you are weighing cch esign vs docusign for tax, choose CCH eSign when your returns already run through a Wolters Kluwer tax product and most of your signing is Form 8879. Choose DocuSign when you need one signing tool for engagement letters, templates and bulk sends across the whole firm.

Form 8879 is the IRS signature authorization a taxpayer gives before an electronic return is transmitted, and a remote e-signature version has to meet IRS identity-verification rules.

Settle one naming question first. CCH eSign's signing engine is AssureSign, and Wolters Kluwer's training material ties the product to Nintex. AssureSign itself was acquired by Nintex on June 2, 2021, according to CB Insights (2021), so ask which company's terms, support and data handling apply to your account.

The TL;DR: CCH eSign fits a firm built around CCH tax workflows, but its pricing is quote-based and its current feature list was hard to confirm. DocuSign fits a firm that wants one tool for many document types and publishes per-user prices. Neither product removes the IRS identity-check duty, which the preparer still has to run and document.

Key Takeaways

  • CCH eSign is the option built around Form 8879 inside a tax-prep workflow. Its pricing is quote-based, so get the fee schedule in writing before you budget.

  • DocuSign is the only one of the three options with published per-user prices, and its Business Pro tier is where bulk sending, payment collection, PowerForms and API access sit.

  • Intuit's tax-product eSignature was announced in 2014 as built on DocuSign technology for Forms 8878 and 8879. Its FAQ lists no prices.

  • Whichever tool you choose, the IRS identity check applies to every remote signing, and a failed check has a defined handwritten fallback.

  • Decide now who keeps the signed record and for how long, because the IRS sets a retention period for remote signings.

How we evaluated these tools

This is an informed buyer's guide built from public pages, not a hands-on trial. Six criteria carry the weights below. The weights are our analysis, not vendor data. The facts under each criterion come from the cited pages, and where a page did not state something, the table says so.

CriterionWeightWhy it carries this weight
Form 8879 identity workflow (KBA, fallback, records)25%The IRS rules apply to every remote signature, whichever tool you pick
Fit with your tax software25%A send from the tax software avoids a separate upload and re-keying step
Annual cost at your user count20%Per-user pricing scales with headcount, and quote-based prices cannot be compared until you get a quote
Non-tax documents and templates15%Engagement letters, Form W-9 and Form 4506-T requests can outnumber 8879s
Audit trail and record retention10%The IRS sets record-keeping duties for remote signings
Admin and integration controls (API, SSO)5%Matters mainly if you build workflows outside the tax software

Our read: if Form 8879 is most of your signing volume, the first two rows decide the choice. If engagement letters and templates are most of your volume, the non-tax row moves up and DocuSign's breadth carries more weight.

What the IRS requires before any remote signature

Identity verification is not a one-time setup. The IRS FAQ says it "must be completed every time a taxpayer electronically signs Form 8878 or 8879, with two exceptions." The exceptions cover a taxpayer who signs in the ERO's physical presence within a multi-year relationship, meaning the ERO has prepared the taxpayer's returns before and verified identity. The method is knowledge-based authentication, which the IRS describes as questions about personal and financial history, and the IRS adds that "this is not a credit check."

Failed KBA: handwritten signature after 3 attempts according to IRS (2026). A taxpayer who cannot clear the check cannot e-sign, and the ERO must then obtain a handwritten signature.

For remote signings, the system must record the taxpayer's IP address and login ID, and the ERO must keep a tamper-proof record for 3 years from the due date or the IRS receipt date, whichever is later, according to IRS (2026). That retention duty falls on your firm whichever signing product you buy.

A 2021 article in The Tax Adviser (2021) reached the same reading, quoting that identity verification "must be done each time a taxpayer remotely signs Form 8878 or Form 8879." The article is archived, so check the current IRS guidance before you configure anything.

Pricing and total cost

Business Pro: $45 per user per month on a one-year term according to DocuSign (checked 2026). The same page lists Standard at $30 per user per month, Personal at $11 per month for one user, and annual totals of $132, $360 and $540 for those tiers, with Enhanced shown as custom. Standard and Business Pro each allow 100 envelopes per user per year. The page shows dollar signs without naming a currency and says additional tax may apply. Third-party sites list different DocuSign prices, so this guide uses only DocuSign's own page.

Pricing checked November 14, 2026.

CCH eSign is quote-based. The CCH pages this review could not retrieve were unavailable, and no retrievable source showed a price, so request a quote in writing. Intuit's eSignature FAQ lists no prices and states that "additional terms, conditions and fees apply" and that pricing is "subject to change at any time without notice."

VendorPlanPublished priceAnnual totalIncluded signing capacity
DocuSignPersonal$11 per month$1325 envelopes per month
DocuSignStandard$30 per user per month$360100 envelopes per user per year
DocuSignBusiness Pro$45 per user per month$540100 envelopes per user per year
DocuSignEnhancedQuote-basedQuote-basedCustom limit
CCH eSignNot publishedQuote-basedNot publishedNot published
Intuit eSignatureEnvelope planQuote-basedNot published5 eSignatures included

Table figures come from the DocuSign page cited above. Rows marked Quote-based or Not published had no public figure on the pages reviewed.

Running the numbers for a six-person firm

Take an illustrative six-person firm, not a real customer, that wants bulk sends for year-end engagement letters and an API connection to its tax workflow. Using the annual totals cited above, six Business Pro seats at $540 each come to $3,240 a year, and six Standard seats at $360 each come to $2,160, so the step up is $1,080 a year. Standard's 100 envelopes per user give six users 600 envelopes a year, but the extra $1,080 buys what Standard lacks: bulk sending, PowerForms and API access. The API is the part that matters for a custom workflow. In DocuSign's REST API the signer list sits under recipients.signers in the create-envelope request, which is documented in the DocuSign REST API reference, so an outside workflow cannot build a signer list on Standard.

Feature matrix: what public pages confirm

CapabilityCCH eSignDocuSign StandardDocuSign Business Pro
Form 8879 identity check (KBA)Described in 2014 trade coverage; confirm current setupNot confirmed on pages reviewedNot confirmed on pages reviewed
Send from tax-prep softwareYes, per 2014 trade coverageNot confirmedNot confirmed
Bulk sendNot confirmedNoYes
API accessNot confirmedNoYes
Shared templatesNot confirmedYesYes
Real-time audit trailNot confirmedYesYes
Payment collectionNot confirmedNoYes
PowerFormsNot confirmedNoYes
SSONot confirmedNoNo (Enhanced is quote-based)
Published priceQuote-based$30 per user per month$45 per user per month

"Not confirmed" means no page this review could open stated the feature. It is a question to put to the vendor, not a "no." Our read: DocuSign's public feature comparison is easier to verify, while CCH's public detail is older and thinner.

Vendor profiles

CCH eSign: built around Form 8879 in a Wolters Kluwer workflow

CCH's 2014 e-sign launch cost reference: $18 per return in 2014 according to CPA Practice Advisor (2014). The trade article reported that figure as firms' direct cost for physical signatures, and it said the product aimed to cut that by nearly 75%.

Best fit: firms that already prepare returns in a Wolters Kluwer tax product and want Form 8879 signing to start from that workflow. The 2014 article describes the preparer sending the taxpayer and spouse a secure link from the tax-prep software, the signers verifying identity and reviewing the return, and then the e-file status updating.

Limitations: the only CCH description this review could open is that 2014 article, and CCH's current pages were not retrievable. Wolters Kluwer's other listed uses, such as engagement letters, Form W-9 and Form 4506-T, could not be verified on an opened page. Its eSign engine is tied to AssureSign, now owned by Nintex, so you are dealing with two companies' terms.

Implementation: confirm the activation path, the signing provider and any fee schedule in writing before you budget. Ask which company runs the signing step and where signed documents are stored.

Skip it if you need engagement letters and bulk sends at volume and cannot get pricing in writing.

Evidence: the 2014 CPA Practice Advisor article above and the CB Insights record of the AssureSign acquisition.

DocuSign: one signing tool across the firm

Best fit: firms that send many non-tax documents, want shared templates, and accept per-user pricing. Standard at $30 per user per month has no bulk send, API access or PowerForms, according to DocuSign (checked 2026), so the Business Pro tier is the one to quote for workflow work.

Limitations: the DocuSign pages reviewed do not say whether Form 8879 identity checks are built in. Treat the KBA setup as a question to answer in writing before you rely on it. Enhanced pricing is quote-based, and the FAQ on the pricing page mentions monthly options it does not price.

Implementation: the REST API creates envelopes with the signer list under recipients.signers. API access is included in Business Pro and not in Standard.

Skip it if you will only ever sign Form 8879s and never use templates or the API, because you would pay per user for features you do not use.

Evidence: the DocuSign pricing page and the DocuSign REST API reference cited above.

The Intuit route: DocuSign technology inside tax software

Accounting Today (2014) reported that Intuit would integrate DocuSign's digital transaction management and eSignature technology into its professional tax software to handle Forms 8878 and 8879.

Included signatures: 5 eSignatures with tax software according to Intuit (undated FAQ). The FAQ lists Lacerte, ProConnect and ProSeries, says identity checks include knowledge-based authentication that "is required for Forms 8878 and 8879," and limits electronic signatures to individual returns: "electronic signatures are only accepted for the Individual Modules." For a married-filing-jointly return, up to two recipients may be included.

Best fit: ProConnect, Lacerte or ProSeries users who sign individual returns and want signing inside the tax product. Limitation: no prices on the FAQ, and envelopes count against the plan allowance once sent.

Implementation: where the signing handoffs break

Most failures happen between systems rather than inside the signing tool: the wrong signer list, a spouse with no email address, or a failed identity check that nobody owns. A workflow layer can close those gaps, and it can also add risk if no one owns it.

A proposed, configurable workflow from US Tech Automations would start on a trigger: a return is marked ready for client signature in the firm's tax workflow or export. The action then builds the signing request. On DocuSign, that call creates the envelope with the signer list under recipients.signers, and it needs an API-enabled plan (Business Pro per the comparison above) and a service account with its own access controls. The output is a sent-envelope record with the envelope identifier and the signer list. The human review point comes before the send: a preparer checks the signer list and, on joint returns, confirms the spouse's email address, because a wrong address is the cheapest error to catch and the slowest to fix after the client has been emailed.

The second proposed workflow handles identity failures. The trigger is a failed knowledge-based check returned by the signing tool. The action allows re-attempts up to the IRS limit, then routes the file to a preparer queue for a handwritten Form 8879. The output is a log entry with the signing method, timestamp, check result and, for remote signings, the IP address and login ID, kept for the IRS retention period. The prerequisite is that the signing tool exposes the check result and those fields through its API or export. If it does not, the log cannot prove the step, and the design should stop there. The preparer keeps the decision on the handwritten fallback and signs off on the retained record. For a CCH-centered firm this workflow is conditional, because this review could not confirm from public documentation that CCH eSign exposes an API for outside workflows.

StepOwnerPrerequisiteHuman review point
Trigger signing requestPreparerReturn marked ready in tax workflow or exportConfirm signer list and spouse email on joint returns
Send envelopeOperations leadAPI access on the chosen planCheck the template and document version
Identity checkSignerKBA through the signing toolReview failures before any retry
FallbackPreparerHandwritten Form 8879 pathConfirm the signed form before transmission
Store recordOperations leadRetention location and access controlsPeriodic spot check of retained records

Who this is for, and who should skip each

CCH eSign suits a firm already on Wolters Kluwer tax software whose signing is mostly Form 8879, and whose owner is willing to wait for a quote. DocuSign suits a firm with many document types, templates and per-user budgets that can absorb the Business Pro tier. Intuit's route suits a ProConnect, Lacerte or ProSeries shop that signs individual returns in the product.

Red flags: the vendor will not confirm the identity-check setup in writing; the firm has many users but no quote; or the plan chosen for a custom workflow has no API access.

When NOT to use US Tech Automations: a simpler tool wins when your firm signs only a handful of Form 8879s a month and your tax software already sends and records them, because a custom layer then adds upkeep without removing work. It also loses when you want a single vendor's support for signing alone, since buying the tool with its own support is simpler than adding an integration. And it is the wrong choice if no one can own an API key, its access controls and ongoing maintenance.

Zapier, Make, n8n, or an in-house script

Zapier, Make and n8n can call the DocuSign API and, when configured, support run histories, retries, error branches and audit logs. The buyer still has to design and own the parts those tools do not decide: idempotency, so a retry does not send a second envelope; escalation paths for failed identity checks; access controls on the API key; and ongoing maintenance when either product changes. A proposed US Tech Automations design could configure the same steps with a named human review queue and a fixed record set, but it depends on the same API prerequisites and still needs a firm owner. For a small firm with one or two signing workflows, a no-code tool you already run may be enough.

Decision checklist before you buy

  • Confirm in writing whether the signing tool runs the Form 8879 identity check, and what happens after a failed attempt.

  • Ask for a quote from CCH and Intuit if either is on your shortlist, and compare it to the DocuSign annual totals.

  • Check whether you need API access or bulk sends in year one; if you do, the DocuSign comparison points to Business Pro.

  • Ask who stores the signed record, where it sits, and how you would produce it on request.

  • Name the person who owns the signing workflow after go-live, not just the person who buys it.

Common mistakes that cost firms time

  • Buying on list price alone when one vendor publishes per-user prices and the other does not.

  • Assuming a tax-software integration covers every document type, which the Intuit FAQ does not support for business returns.

  • Treating the identity check as a setup step rather than a per-signing duty, which the IRS FAQ makes explicit.

  • Choosing Standard for API work, when the comparison places API access in Business Pro.

  • Forgetting the retention record, which the IRS requires to be kept for 3 years from the due date or receipt date, whichever is later.

Frequently asked questions

Is CCH eSign still built on AssureSign?

Public material points that way: Wolters Kluwer's training listings describe the Nintex/AssureSign tie-up, and Nintex acquired AssureSign on June 2, 2021. Confirm the current provider in writing, because the training material was the only source this review could see.

Does DocuSign handle IRS Form 8879 on its own?

The DocuSign pages this review opened do not say. Ask DocuSign for its identity-verification setup for Form 8879 before you rely on the standalone product for that form.

Which costs less for a six-person firm?

On DocuSign's published annual totals, six seats cost $2,160 on Standard or $3,240 on Business Pro, as the worked example shows. CCH and Intuit prices are quote-based, so you can only compare them after you request quotes.

Do I need Business Pro for an API connection?

Yes. DocuSign's plan comparison places API access in Business Pro and not in Standard.

Can Intuit eSignature replace both?

Only for individual returns in ProConnect, Lacerte or ProSeries, because its FAQ says electronic signatures are only accepted for the Individual Modules.

Does the IRS require identity checks on every remote signature?

Yes. The IRS requires identity verification each time a taxpayer electronically signs Form 8878 or 8879, with the two exceptions the FAQ lists.

Conclusion: start from where your Form 8879 work begins

If your Form 8879 work starts inside a CCH workflow, get CCH eSign pricing and the signing provider in writing before you commit. If you need many document types and an API, quote DocuSign's Business Pro tier. In either case, own the identity check and the retained record yourself, and see how US Tech Automations configures this for a firm's own tax and signing stack.

About the Author

Garrett Mullins
Garrett Mullins
Workflow Specialist

Helping businesses leverage automation for operational efficiency.