What each ProSeries option addresses
Compare the job and the operating requirements. A future integration belongs in planning, while today's selection needs an available workflow.
| Option | Document or preparation job | Decision to resolve |
|---|---|---|
| Intuit Tax Import | Financial-institution data download | Participating source and client access |
| ProSeries Tax Scan & Import | Scanned PDF processing for Professional 1040 returns | Edition, source coverage, and pre-import review |
| GruntWorx | Document organization and Populate for ProSeries | Service selection, setup, and tax year |
| TaxAutomate | Client collection, reviewed binder, and approved ProSeries preparation | Paired workstation or configured import-file delivery |
| Juno | ProSeries integration publicly marked coming soon | Current launch and onboarding status |
Official public sources reviewed September 5, 2026. Provider descriptions are not independent product testing or a performance ranking. Confirm current scope and commercial terms for your firm.
Choose the import you actually need
A ProSeries firm asking for automation may need to download a bank statement's data, process a scanned PDF, or stop chasing the client for the statement. Those are different purchase decisions. Identify the slowest handoff in your current return process before comparing tools.
Intuit separates financial-institution Tax Import from the scanned-document add-on. Its support documentation limits Scan & Import to ProSeries Professional's Individual 1040 module; Basic does not include that scanning option. A demonstration in the wrong edition cannot establish the workflow your office will receive.
Follow a submitted PDF through HomeBase
Intuit describes background processing, status updates in HomeBase, and a Pre-Import tool. Use those stages as checkpoints in the evaluation: who submits the file, who notices it is ready, and who reviews the proposed data? A staff member should be able to distinguish a processing job from a return that is ready for professional review.
Bring a packet containing a late replacement statement. Ask what happens if some values were already imported before the replacement arrived. Record which source is current and which return fields require attention. The useful result is a repeatable correction process, including the preparer's review of the existing return.
Shortlist available preparation workflows
GruntWorx lists ProSeries support for Populate. Juno's dedicated ProSeries page, by contrast, explicitly describes a forthcoming integration. That status is a reason to separate a future evaluation from a current purchase, not to infer an undocumented launch date.
TaxAutomate's available ProSeries workflow connects client requests, a bookmarked binder, source review, and approved preparation work. Delivery can use a paired Windows workstation or the configured import-file option. The demonstration should identify which path your firm will operate and show the final ProSeries review.
Evaluate a complete client engagement
Use one ordinary client packet and one packet that needs a response before preparation can finish. Have the employee who normally gathers documents and the preparer who normally enters them participate. Keep the same source files, edition, tax year, and starting return state across demonstrations.
Record staff time separately for collection, source review, delivery, and corrections. Then compare total cost for the services your firm will use. Keep diagnostic review, calculated results, tax decisions, and filing with the responsible professional; an imported value alone does not establish that the engagement is complete.
- Confirm Professional versus Basic and the return module.
- Show the controlling source when a corrected document arrives.
- Identify who owns a failed or incomplete import.
- Check the prepared result inside the existing ProSeries return.
Sources, scope, and detailed evaluations
Official public sources reviewed September 5, 2026. Provider descriptions are not independent product testing or a performance ranking. Confirm current scope and commercial terms for your firm.
TaxAutomate publishes this guide and offers one of the workflows discussed. Its product descriptions reflect the current integration catalog. Competitor descriptions are attributed to the linked first-party sources; an undocumented feature is not treated as an unavailable feature. Product names belong to their respective owners, and this guide does not imply their endorsement of TaxAutomate.
See your ProSeries workflow in a demo
Bring your ProSeries edition, typical source packet, and preferred workstation or import-file process. See collection, approval, delivery, and preparer review together.
Book a DemoSources and limitations
- ProSeries Tax Import versus Tax Scan and Import — Intuit; reviewed September 5, 2026.
- ProSeries Scan and Import: edition, return scope, and processing — Intuit; reviewed September 5, 2026.
- Intuit document automation — Intuit; reviewed September 5, 2026.
- GruntWorx supported software and workflow FAQ — GruntWorx; reviewed September 5, 2026.
- Juno ProSeries integration status — Juno; reviewed September 5, 2026.
- TaxAutomate for Intuit ProSeries: workflow and connection — TaxAutomate; reviewed September 5, 2026.
This article is educational and is not tax, legal, accounting, security, or investment advice. Product capabilities and tax requirements can change. Confirm current vendor scope and authoritative guidance for the relevant facts, tax year, and jurisdiction.
How this article was prepared
We separate current sourced facts from operational recommendations, avoid invented performance claims, and show the primary sources and review date used.
Read the editorial methodology