ProConnect Tax Training for New Preparers: Build Cloud Tax Workflow Fluency

A new preparer completes the official ProConnect Tax training portal.

The employee can create a client, locate common inputs, drag documents into the Import Hub, view the calculated forms, open diagnostics, and find the e-file screen.

The firm assumes the employee is ready for routine returns.

The first live file reaches review, and the manager finds:

• The Intuit Link questionnaire is marked complete, but a prior-year brokerage account is missing and no one asked whether it was closed.
• A W-2 was imported after the preparer had already entered it manually.
• Green imported fields were accepted without comparison to the source document.
• A K-1 import populated income, but basis, at-risk, and passive-activity limitations were never evaluated.
• A prior-year state return did not carry forward, and the preparer treated its absence as proof that no filing was required.
• A critical diagnostic was ignored because the return could still be transmitted.
• An override produced the desired form result without a documented reason or approval.
• A reviewer’s checkmark turned into an unresolved change indicator after another user edited the return.
• The employee transmitted the federal return but did not confirm the related state acceptance.
• The reviewer handoff says only, “Ready for review.”

The employee knows how to use parts of ProConnect Tax.

The employee does not yet own the professional workflow.

The professional evidence chain still has to be visible:

Cloud speed is useful only when the standard moves with it.

Who I Am and Why This Matters

I have practiced public accounting since 1990. I founded my accounting firm in 1993, merged it in 2001 to form Howard, Howard and Hodges, and helped grow the organization from three people to approximately 50 staff across multiple Florida locations and states. Our firm was named PASBA Firm of the Year in 2015.

During filing season, weak preparer development rarely appears under a clean label such as “training failure.”

It appears as manager rescue:

• Reviewers reopening source documents because the preparer did not tie out imported data
• Seniors rebuilding basis, depreciation, state, or trial-balance support
• Managers answering routine navigation questions during deadline weeks
• Returns moving backward through the workflow multiple times
• Comments and diagnostics being treated as task lists rather than evidence of unresolved facts
• Electronic filing being confused with agency acceptance
• The same review note appearing across several returns

Since 2020, I have built and run the SkillAbility accounting workforce development platform used by more than 1,000 accounting professionals across dozens of PASBA firms.

That experience has reinforced one principle:

New preparers become useful when they complete realistic source-to-acceptance returns, receive structured review, correct the work, and prove that the standard transfers to a different assignment.

A product tutorial teaches a feature.

A complete practice return tests application.

A controlled live return validates readiness.

What Is ProConnect Tax Cloud Workflow Fluency?

It combines six forms of knowledge:

• Tax knowledge: The filing rule, form, limitation, election, credit, basis issue, state treatment, and professional standard
• Product knowledge: Client profiles, Input Return, Review Return, forms, Tax Summary, Import Hub, Intuit Link, comments, checkmarks, diagnostics, overrides, user roles, and e-file status
• Cloud workflow knowledge: Permissions, simultaneous activity, status ownership, imported-data provenance, real-time changes, browser security, and remote-work controls
• Firm knowledge: Workpapers, naming, assignments, authority, review gates, escalation, release, retention, and client communication
• Client knowledge: What happened during the year, which documents should exist, what changed, and what the taxpayer has not yet explained
• Professional judgment: What is missing, contradictory, unusual, unsupported, material, or beyond the preparer’s authority

A workflow-fluent preparer can answer:

• Why should this source document or schedule exist?
• Who supplied it, and which taxpayer, entity, year, activity, and state does it belong to?
• Was the amount entered manually, imported from a document, imported from a spreadsheet, transferred from another return, or calculated by the software?
• Which form lines and state results did the input affect?
• What changed from the prior year, and why?
• Which checkmarks or comments remain unresolved?
• What does each diagnostic indicate at the fact, tax, software, or e-file level?
• Which issue requires research or reviewer approval?
• Who is authorized to release and transmit the return?
• Has every federal and state filing been accepted?

That is a higher standard than “the employee can navigate ProConnect.”

Why ProConnect Product Training Alone Does Not Prove Readiness

Intuit provides substantial official learning resources for ProConnect Tax, including getting-started guidance, a training portal, live and recorded webinars, product support articles, an education resource center, and in-product help. Those resources are the right place to learn the current interface and features.

They can teach the employee how to:

• Create and access returns
• Navigate Input Return and calculated forms
• Use Intuit Link and the Import Hub
• Import common source documents and structured data
• Review diagnostics and suggestions
• Use comments and review checkmarks
• Prepare and transmit an electronic filing

The firm still has to teach:

• Which returns the employee may prepare
• What complete client information means
• How prior-year data is challenged rather than copied
• How imported values are verified
• How workpapers make source-to-return traceability visible
• Which diagnostics may be resolved, ignored, or escalated—and by whom
• Who may use an override, adjustment, estimate, election, or manual treatment
• How federal, state, K-1, basis, and related-return issues are coordinated
• What “ready for review” means in observable terms
• Who may print, release, transmit, and communicate the final result

Use Intuit’s official ProConnect Tax training resources for current product instruction.

Use the firm’s realistic practice files and readiness gates to decide whether the employee can perform the work.

For the broader model, read How to Develop Accounting Staff Without Relying on Shadowing.

What Current IRS and ProConnect Data Tells Firms

Professional preparers still carry most reported individual e-file volume

Through May 8, 2026, the IRS reported approximately 141.0 million electronically filed individual income-tax returns. Approximately 75.3 million were received from tax professionals, compared with approximately 65.7 million self-prepared filings.

At that scale, small preparer weaknesses become large review queues.

The preparer population is broad

IRS data current as of July 1, 2026 reported 872,363 individuals with current 2026 PTINs. The same table listed 207,979 CPAs, 68,177 enrolled agents, and 72,045 Annual Filing Season Program records of completion, while noting that some preparers hold more than one credential or qualification.

Source: IRS federal tax return preparer statistics.

ProConnect combines cloud access with automation and review controls

Current Intuit materials describe ProConnect Tax as a cloud-based professional tax platform with built-in diagnostics, QuickBooks-connected workflows, document imports, IRS transcript access, collaborative work, tax-planning integration, and support for thousands of federal and state forms.

Those capabilities can reduce repetitive work and shorten handoffs.

They also create a false signal of competence when a new hire can move information quickly but cannot verify it.

What Changes When the Tax Workflow Is Cloud Based?

A cloud platform removes installation barriers and can make the same return available to authorized users from different locations.

That convenience does not remove process risk. It changes the risk.

1. Access becomes part of the training design

The employee should receive the minimum role and client access needed for the approved training scope. Return data entry, importing, printing, e-filing, reporting, client portals, transcripts, and tax planning may be governed by different permissions.

A weak onboarding process gives broad access because it is convenient.

A strong onboarding process aligns permissions with demonstrated capability.

2. Real-time collaboration can blur ownership

Comments, mentions, status changes, imported documents, calculated changes, and reviewer activity can all occur within the same cloud workflow.

The firm must define:

• Who owns the next action
• Who may edit after preparer sign-off
• How a changed reviewed field is identified
• Which comments are open items versus permanent documentation
• When a return returns to the preparer
• What must be re-reviewed after a change

3. Imports create provenance risk

A value may arrive from an uploaded PDF, a financial institution, a spreadsheet, a prior-year file, another ProConnect return, QuickBooks-connected data, or manual entry.

The preparer must know not only what the number is, but how it entered the return.

4. Product changes arrive continuously

Cloud software can change without a traditional annual desktop installation. Training screenshots and procedures age quickly.

Teach stable professional questions first:

• What fact is being represented?
• What source supports it?
• What did the system do automatically?
• How was the result verified?
• What requires reviewer judgment?

5. Security is part of performance

Remote access, client portals, cloud storage, browser sessions, email notifications, and user permissions all touch taxpayer data.

A preparer who can complete the tax calculation but cannot protect the information is not ready for client work.

The IRS states that professional tax preparers are required to create and maintain a Written Information Security Plan. Firms should incorporate their WISP, multifactor-authentication rules, approved devices, secure document-transfer procedures, incident reporting, and access-removal steps into new-hire training.

See the IRS resources on Written Information Security Plans and Publication 4557, Safeguarding Taxpayer Data.

The Twelve ProConnect Return-Readiness Gates

A return does not pass a gate because the cloud workflow displays a green status.

It passes because the required evidence exists.

Define the Firm’s ProConnect Operating Standard

ProConnect supports flexible users, client access, imports, comments, diagnostics, printing, and e-file workflows.

Flexibility becomes inconsistency when every preparer invents a personal method.

Standardize the return file

Document the firm’s expectations for:

• Client naming, assignment, tax year, return type, and status
• Intuit Link invitations, questionnaire templates, document requests, and completion states
• Source-document indexing, workpaper naming, tick marks, sign-off, and retention
• Prior-year comparison and carryover validation
• Manual input versus imported-data identification
• Document, spreadsheet, K-1, depreciation, and Schedule D import verification
• Comments, mentions, attachments, open items, and review-note closure
• Review checkmark meaning and changed-field procedures
• Diagnostic categories, ignore authority, overrides, and adjustments
• State-return activation, sourcing, apportionment, and related-return coordination
• Preparer self-review and reviewer handoff
• Print, signature, release, transmission, acknowledgement, rejection, and acceptance controls

Define authority by role

A new preparer may be allowed to enter routine source information while lacking authority to independently:

• Add or remove a filing jurisdiction
• Change filing status based on unresolved facts
• Approve a material estimate
• Select, revoke, or suppress an election or form
• Use an override or adjustment that changes a calculated result
• Finalize basis, at-risk, passive-loss, credit, or loss-limit conclusions
• Ignore an unfamiliar critical diagnostic
• Release, print, or transmit a return
• Send client-facing tax advice without review

Build approved examples

For each primary return type, maintain:

• A complete source-document packet
• A prior-year return and expected-source checklist
• A strong prepared ProConnect practice file
• An indexed workpaper set
• An import-verification record
• A diagnostic-resolution record
• A reviewer handoff
• An authorization and e-file checklist
• A weak version containing planted errors

Define “review ready” in observable terms

It should not mean:

“The preparer reached the end of Input Return.”

It should mean:

• Complete source information or visible exceptions
• Validated prior-year and imported data
• Traceable material amounts
• Reasonable federal and state results
• Supported positions, estimates, overrides, and adjustments
• Resolved or documented diagnostics
• Completed checkmark and change review
• A reviewer handoff that identifies the actual decisions

See The Real Tax Season Bottleneck Is Review for the broader review-ready standard.

Users, Permissions, PTINs, EFINs, and Security

Cloud workflow fluency starts before the employee opens a return.

Confirm preparer and firm credentials

• Current PTIN where the employee is paid to prepare or substantially assist in preparing federal returns
• Professional license or enrolled status where applicable
• Continuing-education obligations
• Signing, representation, advice, and client-communication authority
• Firm EFIN approval and registration where electronic filing is performed

The IRS states that anyone paid to prepare or assist in preparing federal returns or claims for refund must generally have a PTIN. See the IRS PTIN FAQ.

Assign access based on the job—not convenience

Intuit’s current permissions structure separates Standard and Advanced user capabilities. Current help materials state that advanced tax permissions include functions such as e-filing, printing returns, certain Intuit Link actions, reporting, transcript access, and tax-planning outputs.

The training implication is simple:

Do not give a new preparer release authority merely because the person needs data-entry access.

Use Intuit’s current user and permission guidance when configuring roles.

Complete a security-readiness check

• Unique user identity—no shared credentials
• Multifactor authentication
• Approved device, browser, operating system, and updates
• Screen-lock and clean-desk rules
• Approved remote-work network and privacy expectations
• Secure client-document transfer
• Prohibited local downloads or removable-media practices
• Phishing and credential-theft reporting
• Access-removal process for departures or role changes
• WISP acknowledgement and incident-response contacts

Security training should be tested with scenarios, not documented only by a signed policy.

For a broader readiness framework, use the Tax Season Readiness Checklist for CPA Firms.

Intuit Link, Organizers, and Source Completeness

Intuit Link can support questionnaires, document requests, client uploads, messages, progress tracking, and return delivery.

That workflow is valuable.

It does not prove the client file is complete.

Teach the difference between client completion and preparer completion

A client may mark a request complete while:

• A prior-year account is missing
• A “does not apply” response contradicts another document
• A new business, rental, state, dependent, or digital-asset fact is buried in a comment
• An uploaded PDF is incomplete or unreadable
• A corrected form is present without the original being removed
• An estimated payment amount lacks date and proof
• A document belongs to the spouse, another entity, or another year

Intuit’s organizer statuses can help a team distinguish unanswered items, items needing review, and information ready for entry. The firm should define exactly what each status means internally.

See Intuit Link organizer statuses.

Build an expected-source list from the prior year

For an individual return, the preparer may expect:

• W-2s and wage statements
• Interest, dividend, brokerage, retirement, Social Security, unemployment, and government-payment forms
• K-1s
• Business, rental, farm, royalty, and foreign-activity records
• Mortgage, charitable, medical, education, childcare, and energy information
• Estimated payments and prior-year refund applications
• Digital-asset activity
• Dependent, filing-status, residency, and identity-protection information
• IRS and state notices

For a business return, the preparer may expect:

• Final or adjusted trial balance
• General ledger and supporting schedules
• Book-to-tax adjustments
• Fixed assets and disposals
• Officer, partner, shareholder, and ownership data
• Basis, capital, debt, distributions, and contribution support
• Payroll, contractor, retirement, and fringe-benefit information
• State apportionment, nexus, and payment records
• Related-entity and K-1 coordination

Require a visible intake conclusion

The preparer should state one of three outcomes:

• Complete for preparation: Expected sources are present and contradictions are resolved.
• Preparation may proceed with controlled open items: The missing information does not compromise current work, and the open item is assigned and visible.
• Stop: The file is too incomplete, contradictory, or risky to continue.

That conclusion prevents “client uploaded documents” from becoming a substitute for intake judgment.

Prior-Year Analysis and Expected-Source Validation

The prior year is a research source.

It is not a template to copy blindly.

Require a prior-year change map

Before input, the preparer should identify:

• Taxpayer and entity identity changes
• Filing status, dependents, addresses, and residency changes
• Recurring employers, financial accounts, K-1s, rentals, businesses, and states
• Carryovers, basis, suspended losses, credits, depreciation, elections, and methods
• Estimated payments and overpayments applied
• Prior notices, amended returns, extensions, and unresolved issues
• Large income, deduction, tax, refund, and balance-due variances

Classify every material prior-year item

The software may carry information forward.

The preparer must decide whether it still belongs.

Input Return, Forms Review, and Source-to-Return Traceability

ProConnect separates data entry from calculated-form review. New preparers should learn both directions:

• Source to input to form: Where did the information enter, and what did it affect?
• Form to input to source: Why is this amount on the return, and what supports it?

Intuit’s forms review tools can allow users to view calculated forms, refresh results, jump from highlighted form lines to inputs, and inspect calculation details where available.

See Intuit’s guidance on entering data and finding inputs.

Train input in context

For every material entry, the preparer should identify:

• Taxpayer, spouse, entity, owner, beneficiary, or activity
• Tax year and period
• Federal, state, and local relevance
• Source document or workpaper
• Manual versus imported origin
• Related limitation, carryover, basis, election, or disclosure
• Expected calculated forms

Review the return as a financial story

After calculation, the preparer should review:

• Total income and its major components
• Adjustments and deductions
• Taxable income and tax
• Credits and limitations
• Payments, withholding, estimates, and extensions
• Refund, balance due, penalties, and payment instructions
• Federal-to-state differences
• Prior-year variances

The ProConnect Tax Summary can display key figures and prior-year comparisons. That makes it useful for reasonableness review—but only when the underlying prior-year information is valid.

See Using the Tax Summary in ProConnect Tax.

Build source-to-return traceability

A reviewer should be able to answer, without reconstructing the file:

• Where did this amount come from?
• How was it entered?
• What was verified?
• What judgment was applied?
• What remains unresolved?

Use the Workpaper Review Checklist to define evidence expectations.

Import Hub, Document, Spreadsheet, and K-1 Controls

Importing reduces keyboard entry.

It does not transfer accountability.

Document imports

Current Intuit guidance describes document import through the Input Drawer or Import Hub for supported forms such as W-2s and several 1098 and 1099 documents. Imported fields may be visually identified, allowing the preparer to see which values came from the import process.

Every document import should include:

• Taxpayer and year confirmation
• Document type and issuer confirmation
• Complete-page review
• Field-by-field comparison for material values
• Duplicate check against manual and prior imports
• Correct destination input
• Federal and state treatment review
• Workpaper sign-off identifying who verified the import

Read Intuit’s current document-import guidance for supported documents and limitations.

Spreadsheet imports

ProConnect supports spreadsheet imports for certain structured data, including categories such as depreciation, dispositions, and owner or beneficiary information depending on return type.

Require:

• Approved template and version
• Control totals before import
• Field mapping review
• Exception and rejected-row review
• Post-import control total
• Form and state-output review
• Retention of the imported file and reconciliation

See How to import tax data from a spreadsheet in ProConnect Tax.

K-1 imports

Current Intuit instructions allow Schedule K-1 data to be imported into individual returns from ProConnect business returns and, in certain circumstances, from other tax software.

The most important training warning is explicit in Intuit’s documentation:

Imported K-1 amounts are not adjusted for basis or at-risk limitations.

The preparer must separately evaluate:

• Correct taxpayer, spouse, entity, and activity
• Federal and state transfer
• Basis and debt basis
• At-risk limitation
• Passive-activity limitation
• Section 179 and other separately stated items
• Qualified business income information
• State withholding, composite tax, and credits
• Disclosures, elections, and footnotes

See Intuit’s K-1 import guidance.

Connected-data imports

When books and tax data connect, train the preparer to distinguish:

• Book amount
• Tax classification
• Book-to-tax adjustment
• Permanent difference
• Temporary difference
• State adjustment
• Owner-specific treatment
• Unsupported or unreconciled amount

Connected data can eliminate duplicate entry.

It cannot eliminate book-to-tax judgment.

Comments, Checkmarks, and Collaborative Review

Cloud collaboration should reduce handoff friction.

Without a standard, it can scatter the audit trail across comments, emails, workpapers, and verbal conversations.

Use comments for defined purposes

Current ProConnect comments can include titles, substantial text, attachments, user mentions, in-product notifications, and email notifications.

The firm should distinguish:

• Open item: A missing fact, document, decision, or action
• Reviewer question: A question requiring preparer response
• Permanent documentation: A conclusion that should remain with the file
• Workflow instruction: An assigned next step
• Client communication note: What was requested, received, or explained

See Using comments in ProConnect Tax.

Define what a review checkmark proves

ProConnect review checkmarks can mark reviewed fields. If a marked field later changes through calculation or another user’s edit, the checkmark can change to an alert requiring re-review.

That is useful only when the firm defines the procedure behind the mark.

A checkmark should not mean:

“I looked at this line.”

It should mean something observable, such as:

• Tied to the source document
• Reconciled to the workpaper
• Compared with prior year
• Calculation tested
• State effect reviewed
• Reviewer-approved treatment

See Track calculated changes with checkmarks.

Teach change control

Before release, the preparer or reviewer should inspect unresolved changed-field alerts and determine:

• What changed
• Who or what changed it
• Which forms and states were affected
• Whether prior review procedures remain valid
• Whether the reviewer handoff or client result must be updated

Cloud collaboration is not complete until changed work is re-owned.

Diagnostics, Overrides, and Professional Judgment

Diagnostics are prompts for investigation.

They are not a substitute for investigation.

Teach the current diagnostic categories

Intuit’s current guidance describes:

• Fatal diagnostics: Conditions expected to trigger agency rejection and that cannot be ignored
• E-file critical diagnostics: Conditions that prevent e-filing until resolved
• Extension diagnostics: Conditions that prevent extension e-filing until resolved
• Critical diagnostics: Conditions that may risk an agency response but may not block e-file
• Overrides: Manual entries that bypass program calculations
• Suggestions: Informational items requiring review

See Intuit’s diagnostic definitions.

Use a diagnostic-resolution protocol

For each material diagnostic, the preparer should document:

1. The message and reference number
2. The affected return, form, state, and input
3. The underlying fact or rule
4. The source evidence reviewed
5. The correction, explanation, ignore decision, or escalation
6. The effect on federal, state, related returns, and e-file
7. The reviewer approval required

Do not train people to optimize the diagnostic count

A shorter list can mean the return improved.

It can also mean:

• Information was deleted
• A state was removed
• A form was suppressed
• An issue was ignored
• An override forced a result
• The return became less complete

Control overrides and adjustments

Intuit explains that override fields replace program calculations, while adjustment fields change the calculated amount. Some override or adjustment entries can affect form generation or e-file eligibility.

New preparers should not use them as troubleshooting shortcuts.

Require:

• Reason for the manual treatment
• Tax authority or approved firm procedure
• Source and calculation support
• Federal and state impact
• Reviewer approval
• Clear workpaper documentation

See Using overrides and adjustments in ProConnect Tax.

Professional standards still govern the result

Circular 230 establishes competency, diligence, and ethical-conduct expectations for practitioners before the IRS. The AICPA’s revised Statements on Standards for Tax Services became effective January 1, 2024 for AICPA members providing tax services.

The training implication is direct:

• The software result is not tax authority.
• A client answer may require follow-up when it appears incomplete, inconsistent, or unreasonable.
• A cleared diagnostic does not prove a supportable position.
• An imported value must be verified.
• Uncertainty must be visible to the reviewer.
• The preparer must know when to stop.

External references: IRS Circular 230 resources and AICPA information on the revised SSTS effective date.

Professional skepticism should be trained deliberately. See Professional Skepticism Training for Junior Accountants.

Individual, Business, and State-Return Training Pathways

Individual returns

Start with approved routine scenarios before adding complexity.

A first-stage individual return may include:

• W-2 income
• Interest and dividends
• Retirement or Social Security income
• Itemized deductions
• Estimated payments
• One resident state

Then add controlled complexity:

• Brokerage imports and basis corrections
• Dependents and due-diligence issues
• Schedule C or rental activity
• K-1s
• Digital assets
• Education, energy, business, or foreign credits
• Multiple states
• Prior-year carryovers and amended-return facts

Business returns

A business-return pathway should include:

• Entity identity, ownership, tax year, and filing scope
• Trial-balance and general-ledger reconciliation
• Book-to-tax adjustments
• Fixed assets and disposals
• Balance-sheet and retained-earnings reconciliation
• Owner, partner, shareholder, or beneficiary information
• Capital, basis, debt, contributions, and distributions
• Payroll and officer-compensation review
• K-1 and related individual-return coordination
• State apportionment, nexus, composite filings, and withholding

A trial balance that imports without an error is not a completed business return.

The preparer must reconcile what the import did to the tax forms.

State and multistate training

State returns should not be treated as automatic federal attachments.

Require the preparer to identify:

• Residency and domicile
• Move dates
• Source of wages, business income, rentals, gains, and K-1 items
• Nonresident and part-year obligations
• Withholding and estimated payments
• Credits for taxes paid to other states
• Apportionment and allocation
• Composite, withholding, franchise, local, and city obligations
• State-specific additions, subtractions, elections, and attachments

A state return disappearing after an input change is a warning to investigate—not an efficiency gain.

Preparer Self-Review and the Reviewer Handoff

The preparer should review the return before asking the reviewer to review it.

The minimum self-review sequence

1. Reconcile the source packet and open-item list.
2. Confirm prior-year items and current-year changes.
3. Review imported-data provenance and verification.
4. Trace material form amounts back to inputs and sources.
5. Review the Tax Summary and prior-year variances.
6. Review federal, state, and related-return consistency.
7. Resolve or document diagnostics.
8. Inspect overrides, adjustments, estimates, elections, and disclosures.
9. Review comments, mentions, checkmarks, and changed-field alerts.
10. Confirm client action, signatures, payments, and remaining decisions.

Use a decision-ready reviewer handoff

A strong handoff should include:

• Return scope and filing jurisdictions
• Major current-year changes
• Missing or controlled open items
• Material imports and how they were verified
• Large federal and state variances
• Basis, loss, credit, state, estimate, election, or disclosure issues
• Overrides or adjustments
• Diagnostics ignored or requiring reviewer attention
• Client questions and communication needs
• Specific decisions requested from the reviewer

The goal is not to eliminate review.

The goal is to stop making the reviewer reconstruct the preparation process.

Use the Staff Accountant Competency Checklist to define controlled client-work readiness.

Authorization, E-File, Rejections, and Confirmed Acceptance

Transmission is an event.

Acceptance is the outcome.

Teach the complete release sequence

1. Preparation and self-review complete
2. Reviewer approval complete
3. Client-facing return and instructions reviewed
4. Required authorizations obtained
5. Payment, direct-debit, extension, and voucher instructions confirmed
6. Federal and state electronic records selected
7. Return transmitted by an authorized user
8. Acknowledgements monitored
9. Rejections investigated and corrected
10. Every required filing accepted
11. Confirmation and client delivery completed
12. Post-filing actions assigned

Current Intuit guidance states that ProConnect e-filing requires an approved EFIN and that the EFIN must be registered with Intuit. The current help page also distinguishes preparation, transmission, acknowledgement status, and rejection resolution.

See How to e-file a tax return in ProConnect Tax and How to resolve e-file rejections.

Use acceptance evidence

The employee should be able to produce:

• Federal acknowledgement
• Each state acknowledgement
• Rejection code and resolution where applicable
• Final accepted status
• Client confirmation and delivery record
• Payment or follow-up instructions

A return is not complete because the e-file button worked.

It is complete when the firm has evidence that every required filing reached its intended outcome.

The Complete 30-Day ProConnect Training Plan

Days 1–5: Product, firm, and security foundations

Objectives

• Complete assigned official ProConnect training modules
• Understand users, roles, client access, and prohibited actions
• Review the firm’s WISP, secure document procedures, and incident reporting
• Learn client profiles, Input Return, Review Return, Tax Summary, diagnostics, comments, checkmarks, Import Hub, Intuit Link, and e-file status
• Understand the firm’s workpaper index and review-ready definition

Evidence

• Product knowledge assessment
• Security scenario assessment
• Correctly configured practice user and client access
• Ability to explain the twelve readiness gates

Days 6–10: Routine individual return from source to forms

Objectives

• Review a prior-year return and build an expected-source list
• Process a realistic organizer and source packet
• Enter and import routine individual data
• Trace calculated forms back to inputs and sources
• Review the Tax Summary and prior-year changes
• Prepare indexed workpapers

Evidence

• Complete routine 1040 practice return
• Source-to-return traceability test
• Import-verification worksheet
• First reviewer handoff

Days 11–15: Imports, states, diagnostics, and collaboration

Objectives

• Use Intuit Link and organizer statuses correctly
• Validate document and spreadsheet imports
• Use comments and mentions for defined purposes
• Apply review checkmarks and investigate changed-field alerts
• Resolve routine diagnostics and escalate unfamiliar items
• Prepare a resident and nonresident state return

Evidence

• Practice return with missing and duplicate documents
• Diagnostic-resolution log
• Changed-field re-review exercise
• State-source explanation

Days 16–20: Business return and K-1 coordination

Objectives

• Reconcile a trial balance and book-to-tax adjustments
• Review fixed assets and ownership data
• Prepare a routine 1065 or 1120S practice return
• Import a K-1 into an individual return
• Identify basis, at-risk, passive, state, and disclosure issues not resolved by import
• Coordinate business and owner returns

Evidence

• Reconciled business return
• K-1 import-verification record
• Basis or limitation escalation memorandum
• Business-to-individual tie-out

Days 21–25: Planted-error self-review and reviewer loop

Objectives

• Find missing, duplicated, misclassified, and unsupported items
• Investigate unreasonable federal and state results
• Correct invalid diagnostic resolutions
• Identify inappropriate overrides or adjustments
• Respond to reviewer comments and resubmit the return

Evidence

• Planted-error detection score
• Corrected practice return
• Review-note response quality
• Evidence that repeated errors declined

Days 26–30: Release simulation and controlled live-readiness decision

Objectives

• Complete final self-review
• Prepare a decision-ready reviewer handoff
• Simulate authorization, print, release, transmission, rejection, and acceptance
• Complete a different return without step-by-step navigation
• Demonstrate correct escalation and communication

Evidence

• End-to-end capstone return
• 100-point readiness scorecard
• Manager decision on permitted live-return scope
• Written restrictions, checkpoints, and next milestones

This is the same principle behind scenario-based accounting training: practice decisions before the live client and deadline absorb the cost of the first attempt.

The 30/60/90-Day Live-Work Progression

Days 31–60: Controlled routine returns

The employee may receive a defined class of returns with:

• Approved client access
• Limited return types and states
• Required intake checkpoint
• Required pre-review checklist
• Manager approval for diagnostics, estimates, elections, overrides, and unfamiliar issues
• No independent release or transmission authority unless separately approved

Days 61–90: Expanded complexity based on evidence

Expand scope only when metrics support it:

• First-pass quality is improving
• Repeated notes are declining
• Imported-data errors are rare and detected internally
• Reviewer handoffs are decision ready
• Escalation occurs at the right time
• Federal and state acceptance is tracked correctly

After day 90: Independence is scoped, not declared

An employee may be independent on routine resident 1040s and still require direct review on:

• Multistate filings
• K-1 limitations
• Complex business returns
• Foreign reporting
• Unusual elections
• Material estimates
• Overrides and paper-file conditions
• Client advice

Use the 12 Accounting Onboarding KPIs to measure whether expanded responsibility is earned.

100-Point ProConnect Readiness Scorecard

Suggested readiness rule: Require at least 80 points overall, no zero in any category, no unresolved security or integrity failure, and manager approval of the permitted live-work scope.

A total score should not hide a critical weakness.

A preparer with excellent input speed and poor diagnostic judgment is not ready.

Realistic ProConnect Practice Scenarios

Scenario 1: The “complete” organizer

The client marks every Intuit Link request complete. The prior year shows two brokerage accounts, but only one consolidated statement was uploaded. The preparer must identify the missing expected source, determine whether the account closed, and prevent premature completion.

Scenario 2: The duplicate import

A W-2 was manually entered before the source document was imported. The preparer must identify the duplication, preserve the correct record, verify state wages and withholding, and document the correction.

Scenario 3: The green K-1 fields

A partnership K-1 imports successfully and the fields appear complete. The practice file contains insufficient outside basis and passive-activity support. The preparer must recognize what the import did not solve and escalate.

Scenario 4: The changed checkmark

A reviewer marks a material credit field complete. Another user changes a related input, causing the reviewed field to change. The preparer must identify the change, assess all affected forms and states, and return the item to review.

Scenario 5: The critical diagnostic that can be ignored

The return can be transmitted despite a critical diagnostic. The preparer must determine whether the message is informational, factually inapplicable, or evidence of an unresolved tax or filing issue. The exercise is scored on reasoning, not message removal.

Scenario 6: The forced result

An override creates the expected refund. The preparer must remove the shortcut, identify the underlying input or tax issue, research or escalate, and document any approved manual treatment.

Scenario 7: Federal accepted, state missing

The federal return is accepted. One state is rejected and another remains pending. The preparer must resolve the rejection, track the pending filing, communicate accurately, and prove final acceptance.

Scenario 8: The cloud-access incident

A preparer receives an unexpected multifactor prompt after clicking an email notification. The employee must stop, report the event, avoid entering credentials, and follow the firm’s incident-response process.

These scenarios build judgment before live client work. They also expose whether the employee can apply the standard without a manager narrating every click.

What the Firm Should Measure

Do not judge ProConnect training by video completion alone.

Measure work.

The most important trend is not whether the preparer becomes faster.

It is whether useful output rises while corrections, repeated notes, and manager rescue fall.

Common ProConnect Training Mistakes

Mistake 1: Treating cloud access as readiness

Being able to work from anywhere says nothing about whether the work is right.

Mistake 2: Giving advanced permissions too early

Broad access creates operational and security exposure without improving learning.

Mistake 3: Training isolated inputs instead of complete returns

The employee learns screens but not the relationship among intake, evidence, forms, states, review, and filing.

Mistake 4: Trusting imported fields because they are visually identified

Color or status identifies provenance. It does not prove accuracy.

Mistake 5: Treating organizer completion as source completeness

The client controls the response. The preparer owns the completeness conclusion.

Mistake 6: Counting cleared diagnostics

The metric rewards message removal instead of correct investigation.

Mistake 7: Using checkmarks without a procedure

A mark with no defined meaning creates the appearance of review rather than evidence of review.

Mistake 8: Letting comments replace workpapers

Comments are useful for collaboration. Material conclusions still need durable, organized support.

Mistake 9: Allowing overrides as troubleshooting shortcuts

A forced result can conceal the real input, tax, form, or software issue.

Mistake 10: Ending training at transmission

The employee never learns acknowledgement, rejection, correction, acceptance, and client follow-up.

Mistake 11: Expanding scope because 30 days passed

Calendar time is not evidence.

Mistake 12: Using live client work as the first complete practice

Clients should validate readiness.

They should not host the first attempt.

For a broader onboarding system, read CPA Firm Onboarding Software: How to Ramp New Hires Without Manager Rescue.

Frequently Asked Questions About ProConnect Tax Training

What is the best way to train a new preparer in ProConnect Tax?

The best approach combines current Intuit product training with complete practice returns, firm-specific workpapers, planted errors, reviewer feedback, readiness gates, and controlled live work. Product instruction teaches features. Complete returns prove whether the employee can apply tax knowledge, source validation, imports, diagnostics, review, security, and e-file controls as one workflow.

How long does ProConnect Tax training take?

A focused employee can build baseline workflow fluency in approximately 30 days when training is structured and full time. That does not mean unrestricted independence. Most firms should follow with a 30/60/90-day controlled live-work progression based on return complexity, first-pass quality, repeated errors, escalation judgment, and reviewer evidence.

Is Intuit’s official ProConnect training enough for a new tax preparer?

It is an essential product foundation, but it cannot define your firm’s client-intake standard, workpapers, review-ready criteria, authority limits, diagnostic escalation, state procedures, or release controls. The firm must add realistic practice and performance verification.

What should a new ProConnect preparer know before receiving live returns?

The employee should understand security, permissions, client intake, prior-year review, source completeness, manual and imported input, forms review, federal and state reasonableness, diagnostics, comments, checkmarks, overrides, self-review, reviewer handoff, authorization, and acceptance tracking. The person should demonstrate those capabilities on realistic practice files.

How should firms train Intuit Link?

Train Intuit Link as an intake and communication workflow, not merely a portal. Preparers should learn to create expected-source lists, interpret organizer statuses, review client answers, identify contradictions, control open items, verify uploaded documents, and state whether a file is complete enough to proceed.

How should imported documents be reviewed?

Confirm the taxpayer, year, issuer, document type, completeness, extracted values, destination input, duplicates, federal treatment, state treatment, and resulting forms. Retain evidence that the import was verified. An imported field is not automatically a correct field.

Does ProConnect K-1 import handle basis and at-risk limitations?

Intuit’s current guidance states that imported K-1 amounts are not adjusted for basis or at-risk limitations. The preparer must separately evaluate basis, at-risk, passive-activity, state, disclosure, and related-return issues.

What is the difference between a ProConnect diagnostic and a review note?

A diagnostic is a software-generated message about a condition in the return or electronic filing. A review note is a firm-generated instruction, question, correction, or coaching point. Both require professional interpretation. Neither should be treated as a task to close without understanding the underlying issue.

Can a critical diagnostic be ignored in ProConnect Tax?

Some critical diagnostics may not block e-file and may be marked ignored when the firm determines they do not apply. That decision should follow source review, tax analysis, documentation, and the firm’s approval rules. Ignoring a message can still create rejection or substantive risk when the conclusion is wrong.

What do review checkmarks prove?

Only what the firm defines them to prove. A checkmark should represent a specific procedure such as source tie-out, calculation review, prior-year comparison, or reviewer approval. If a checked field later changes, the affected item should be re-reviewed before release.

How do you know when a new ProConnect preparer is ready for live work?

Use observable evidence: accurate complete practice returns, missing-source detection, verified imports, reasonable federal and state results, correct diagnostic handling, good self-review, decision-ready reviewer handoffs, security compliance, and a passing readiness score. Then assign a limited class of live returns with checkpoints and review.

What is the most important ProConnect training metric?

Measure whether useful review-ready output rises while reviewer corrections, repeated notes, diagnostic mistakes, manager interruptions, and acceptance follow-up errors fall. Faster data entry without lower rework is not successful training.

To cloud tax workflows your reviewers can actually review,

Vincent Howard, CPA
Managing Partner, Howard, Howard and Hodges
SkillAbility for Accounting Firms

ProConnect Tax, ProConnect Tax Online, Intuit Link, Intuit Tax Advisor, QuickBooks, Intuit Accountant Suite, and related product names are trademarks or services of Intuit Inc. SkillAbility is not Intuit and does not represent that this article replaces current Intuit product training, documentation, software updates, support, licensing, terms, tax-law guidance, or professional standards.

© 2026 SkillAbility for Accounting Firms. This article provides general educational information and does not replace tax, accounting, legal, employment, human-resources, cybersecurity, software, professional-standards, or regulatory advice.