Intuit Sign in Pro Tax: License Requirements and PDF Pitfalls
QuickBooks Pro Tax users running into Intuit Sign limitations, from license eligibility to Microsoft Print to PDF issues that affect signature appearance.
QuickBooks Pro Tax practitioners who need client signatures are running into a few predictable roadblocks with Intuit Sign, from license eligibility to a subtle PDF rendering problem that can undermine the whole process.
What Intuit Sign actually does
Intuit Sign is the vendor’s built-in eSignature tool for Pro Tax. It lets you request signatures on T1, T2, T3, and other forms without chasing email attachments or managing separate files. The service adds time stamps and authentication certificates to signed documents, supports multiple signers on the same return, and stores everything in the cloud for seven years. Clients do not need to create an account. They receive a one-time access code and sign from a browser.
The dashboard shows which requests are complete and which are still outstanding, and you can set reminders and expiry dates on pending signatures.
License eligibility trips people up
Intuit Sign is not included with every Pro Tax license. You need a T1, T2/CO-17, T3, or Federal Tax Suite ProFile license, plus a separate Intuit Sign license on top of that. The tool does not work with trial licenses, OnePay licenses, or ProFile 20 licenses. If you fall into one of those categories, the Request eSignature option simply will not function the way you expect.
This catches practitioners off guard when they are on a trial or a limited license and assume the feature is broken. It is not broken. It is a licensing gate.
The Microsoft Print to PDF problem
One practical issue that surfaces repeatedly involves how you generate the PDF before uploading it to an Intuit Sign request. If you print from Pro Tax using Microsoft Print to PDF, the resulting file can cause problems with how signatures appear on the document. The signature may not render correctly, or it may land in the wrong position on the page.
The workaround is straightforward: avoid Microsoft Print to PDF for documents that will go through Intuit Sign. Use Pro Tax’s own export or print-to-file options instead. The difference matters because a misaligned or missing signature can delay a return or force you to resend the entire request.
Document limits and the T1032 exception
When you open the eSignature forms window from Pro Tax, you can select up to five documents to include in a single request. There is one hard exception: the T1032 form must be sent by itself. If you select a T1032, no other documents can accompany it in that submission.
You can also mix preselected forms with uploaded documents, but the combined total still cannot exceed five. This limit applies to the request itself, not to your overall usage, so you can send multiple batches if you have more than five documents to collect.
What the client sees
From the client side, the process is deliberately low-friction. They receive a notification with a one-time access code, open the link, and sign directly in the browser. No account creation, no password to remember. The signed document gets time stamped and stored automatically.
For practitioners, the trade-off is that you are relying on Intuit’s infrastructure for both delivery and storage. The seven-year cloud retention is useful for compliance, but it also means your signed documents live in Intuit’s environment, not on your own file server.
Practical takeaways
Check your license type before troubleshooting. If you are on a trial, OnePay, or ProFile 20 license, Intuit Sign will not work regardless of your settings. When generating PDFs for signature requests, skip Microsoft Print to PDF and use Pro Tax’s native export. And remember the five-document cap, with the T1032 standing alone as the one form that cannot share a batch.
These are not bugs. They are constraints of the tool, and knowing them upfront saves a round of resending documents and chasing clients for signatures that never arrived.