How to automate tax data entry in ProSeries while keeping professional review in place

The short answer: automate the keystrokes, not the review

Yes—you can automate tax data entry in ProSeries, and you can do it without giving up an inch of professional control. The mechanical work that consumes most of a preparer's time—reading a client's W-2s, 1099s, 1098s, and K-1s and transcribing those figures into the return—is exactly the part that automation handles well. AI can classify each document, extract the numbers, and populate the correct fields in ProSeries, then hand a preparer a drafted return that is ready to review.

What automation does not do is replace ProSeries or replace the preparer. ProSeries remains your system of record for calculation, diagnostics, and e-file. The professional still opens the return, verifies every material figure against source documents, makes the classification and judgment calls, resolves flagged items, and signs. That division is not a marketing preference—it is how the U.S. tax system assigns responsibility. The IRS requires anyone who prepares federal returns for compensation to hold a valid PTIN, sign the returns they prepare, and stand behind their substantive accuracy. No tool changes who is on the hook.

So the practical question this guide answers is narrow and useful: how much of a ProSeries return can AI populate correctly and pre-check before the preparer opens it, and how do you keep review firmly in human hands? We will look at what ProSeries already does, where the data-entry gap still lives, and how an AI layer fills it without disturbing the workflow your firm already runs.

What ProSeries already automates on its own

Before adding anything, it is worth being honest about what Intuit ProSeries already gives you, because a good automation strategy builds on those tools rather than duplicating them.

Forms-based entry, diagnostics, and calculation

ProSeries uses forms-based data entry that mirrors the returns themselves, with one-click access to the calculation behind each field. Intuit describes more than 1,000 diagnostics that surface mistakes before e-file, plus Quick Entry sheets and a clear view of each calculation. This is the engine you keep. AI-assisted data entry is not a substitute for the ProSeries calculation and diagnostics layer—it feeds it.

Tax Import and Scan and Import

ProSeries also ships genuine import tooling. The Tax Import add-on can pull W-2, 1098, and 1099 data directly from participating financial institutions and payroll providers into a 1040, and the Scan and Import feature reads scanned source-document PDFs. Both paths deliver data into the return only after a review step: when processing finishes, the preparer opens the return and a pre-import or reviewer tool shows the imported values before they populate the form. Intuit's own Scan and Import documentation walks through this sequence—Import menu, Tax Import, Import Client Data from Scanned PDF, then review before populating.

These features are useful, and firms that already run them should keep doing so. But they have real edges. Tax Import depends on the financial institution supporting the connection; Intuit notes that when a client has enabled extra security such as two-factor authentication, Tax Import cannot connect and the documents must be entered manually. Scan and Import is a ProSeries Professional feature and is not available in ProSeries Basic. And the coverage is uneven across the long tail of documents a real client folder contains.

Where the data-entry gap still lives

The honest picture is that ProSeries automates the returns it can reach cleanly, and leaves the rest to keystrokes. That leftover is where preparation time actually goes.

Consider the documents that resist the built-in paths. A client photographs a W-2 with a phone instead of scanning it. A 1099-DIV arrives from a small institution that does not participate in Tax Import. A K-1 comes as a PDF attachment. A brokerage account produces a consolidated 1099 with pages of 1099-B detail. Every one of those still gets typed, line by line, into ProSeries by a person.

Brokerage statements are the sharpest example. ProSeries offers several methods for entering 1099-B transactions—a summary total with an attached PDF of detail, manual Quick Entry line by line, Tax Import, or Scan and Import—but each carries friction. Wash-sale losses from Box 5 must be entered so they can be tracked; adjustments route to a separate worksheet; and firms report that when multiple brokers are involved, a later import can overwrite an earlier one, forcing manual re-entry of the second and third statements. These are exactly the fields most likely to be miskeyed and most tedious to reconcile.

There is also a coverage question inside the ProSeries product line itself. Scan and Import is a ProSeries Professional capability; firms on ProSeries Basic do not have it, so their document-to-field path is largely manual. And even where the tools exist, the preparer still has to organize the folder first—deciding which PDF is a W-2 and which is a 1099, splitting a single scanned bundle into separate documents, and matching each one to the right client and return. That sorting work happens before any import runs, and it is pure overhead.

This is the gap an AI data-entry layer targets: the documents and fields ProSeries cannot import cleanly, plus the classification and completeness checks that no import tool performs. The goal is not to route around ProSeries but to arrive at the ProSeries review screen with more of the return already populated and pre-checked.

How AI automates ProSeries data entry, step by step

A well-built AI workflow mirrors the steps a ProSeries preparer already follows and simply removes the manual document handling, keeping the professional at every decision point. In practice it runs as a defined pipeline:

1. Secure document intake. The client uploads documents through a portal, or the firm scans them. Files are encrypted and organized by client and return, so nothing is loose or mislabeled at the start.
2. Classification. AI identifies each document by type—W-2, 1099-NEC, 1099-DIV, 1099-INT, 1099-B, 1098, K-1, driver's license—regardless of whether it is a clean scan, a phone photo, or an unusual layout, so each one routes to the right place in the ProSeries return.
3. Extraction and field mapping. The system reads each field and maps the value to the correct ProSeries input—wages to the W-2 worksheet, mortgage interest to Schedule A, dividends to the 1099-DIV worksheet—replacing the keystroke-by-keystroke transcription that consumes most preparation time.
4. Completeness and exception checks. The workflow compares this year against the prior year, detects forms that appear to be missing, and flags figures that look inconsistent—so gaps surface as questions rather than silently entered errors.
5. Professional review in ProSeries. The preparer opens the populated return in ProSeries, runs its diagnostics, verifies flagged items and every material figure against the source documents, resolves exceptions, applies judgment, and approves the return for signature and e-file. This step is never automated away.

The output is a ProSeries return that reaches review already populated and pre-checked, so the professional spends scarce time on verification and judgment rather than typing. Note that this design deliberately keeps ProSeries as the review and filing environment. Automation deposits data into the return; the preparer works it inside the software they already know. For more on the general shape of this pipeline, see how tax preparation automation works.

The automation boundary: which fields, and which judgments stay human

The single most important design decision in automated data entry is drawing a hard, visible line between what the software populates and what the professional owns. Get this line right and automation is a defensible time-saver; blur it and you have built a way to file unreviewed errors faster.

Fields automation should populate

Direct, labeled, single-value fields are where automation is strong: wages, federal and state withholding, EIN and payer identifiers, interest and ordinary dividends, mortgage interest and points, and the straightforward boxes of a 1099-NEC. These are transcription tasks with a right answer printed on the document. The value of automation here is speed and the elimination of transposition errors—not judgment.

Judgment fields that stay with the preparer

Other fields look like data entry but are actually decisions, and those belong to the professional every time. Whether a payment is self-employment income on a Schedule C or belongs elsewhere; how to characterize a K-1 item; whether a 1099-B lot is a wash sale that ProSeries must track separately; whether a client qualifies for a credit; how to handle a basis question the document does not answer. Automation can surface the underlying figures and flag the ambiguity, but a human decides. Large language models can also produce confident-sounding output that is wrong, so a figure that "looks right" is not the same as a figure that is right—which is precisely why the ProSeries diagnostics run and the preparer verifies before signing.

Task in the ProSeries workflow	Before automation	With AI data entry
Classifying and sorting client documents	Preparer sorts the folder by hand	AI classifies each document by type and routes it
Keying labeled fields (wages, withholding, interest)	Manual transcription into ProSeries worksheets	AI populates the fields; preparer verifies against source
Catching a missing 1099 or 1098	Noticed—or not—during preparation	Flagged automatically via prior-year and cross-doc checks
Classification and judgment calls (Sch C vs. other, wash sales)	Preparer decides	Preparer decides; AI surfaces the figures and the ambiguity
Running diagnostics, reviewing, signing, e-filing	Preparer, inside ProSeries	Preparer, inside ProSeries—unchanged

The pattern is consistent: automation clears the mechanical rows, and the professional keeps every row that requires interpretation. The profession has said as much directly. The AICPA's revised Statements on Standards for Tax Services, effective January 1, 2024, added a standard on reliance on tools stating that a member may reasonably rely on a tool, but "use of the tool does not absolve the member of their professional obligations." That is the correct mental model for AI in a ProSeries workflow.

Missing documents and exception flags: the part ProSeries import does not do

Straight import tools answer one question—"what does this document say?"—but not the more dangerous one: "what is missing?" A silent gap is how an incomplete return reaches a client. This is where an AI layer earns its place alongside ProSeries.

A strong workflow performs completeness reasoning that no field-level import performs. It compares the current year's documents against the prior-year return: if last year had a 1099-INT from a bank and a Schedule E rental, and this year those documents have not arrived, that is a flag, not an assumption. It reads cross-references inside documents—a brokerage summary that lists a 1099-DIV the client has not yet uploaded, or a K-1 footnote pointing to a statement that is absent. And it surfaces year-over-year anomalies, such as dividend income that jumped materially, so the preparer can ask whether a document is missing or the change is real. Missing-document detection is important enough that it is a discipline of its own; see missing-document detection for tax returns.

Two kinds of flags are worth distinguishing, because they call for different preparer actions. A missing-document flag says the evidence suggests a form should exist but has not arrived—this becomes a client request. An inconsistency flag says a value looks wrong relative to context: a withholding figure that is implausibly large, a state code that does not match the address, a dividend total that does not reconcile to the brokerage summary. That second kind is a verification prompt aimed straight at the ProSeries field before diagnostics even run. Good automation labels each flag with the reason it fired and the document it came from, so the preparer can resolve it in seconds rather than re-reading the whole folder.

The payoff is that gaps become questions the preparer resolves before review, rather than blanks that survive into a filed return. Automation does not decide the return is complete—it assembles the evidence so the professional can decide, quickly and with the exceptions already in front of them.

The data-security duties you keep when you automate

Adopting an AI layer in front of ProSeries is not only an accuracy question—it is a data-handling question, and the rules are stricter than many firms assume. These duties do not transfer to a vendor; they remain the firm's.

IRC §7216: consent to use or disclose return information

Section 7216 imposes criminal penalties on preparers who knowingly or recklessly disclose or use a taxpayer's return information for purposes other than preparing the return, unless an exception or the taxpayer's consent applies. The IRS's Section 7216 Information Center lays out the framework and its exceptions. The practical implication for AI: if a tool uses client tax data in ways that go beyond preparing that client's return—training external models, sharing with third parties—you may need specific, informed taxpayer consent. Before you route ProSeries client data through any AI service, confirm exactly how that data is used and whether §7216 consent is required.

The FTC Safeguards Rule and your WISP

Paid tax preparers are treated as "financial institutions" under the Gramm-Leach-Bliley Act, which places them under the FTC Safeguards Rule. Every firm must maintain a Written Information Security Plan (WISP); the IRS reinforces the same expectation through Publication 4557, Safeguarding Taxpayer Data, and the Security Summit's WISP template. There is no small-firm exception—solo and seasonal ProSeries preparers are covered too. Any AI tool that touches client documents becomes part of the environment your WISP must account for, so encryption in transit and at rest, access controls, data location, and retention are procurement questions, not afterthoughts. For a working list, see our security checklist for AI software in a tax practice.

What to verify with any ProSeries automation vendor

"Works with ProSeries" is not the same as a tested, supported path into your specific version—confirm it. Ask how the drafted data reaches the return, how client data is encrypted and who can access it, where it is stored and for how long, and whether the vendor uses your data to train models (a §7216 question). Ask to see the source-to-field trail a reviewer can inspect, because due diligence and preparer-penalty exposure both require verifiable work. These belong in the evaluation right next to accuracy. Our guide to evaluating AI tax preparation software covers the full checklist.

A practical example, start to finish

Consider a firm preparing an individual return in ProSeries for a client with two W-2s, a mortgage interest statement, and a brokerage account. The following figures are illustrative, not statistical claims.

Traditionally, a preparer might spend 45–60 minutes keying documents into ProSeries before any real analysis begins—typing each W-2 box, the 1098, and the brokerage detail line by line, then hoping nothing was left out. In an AI-assisted workflow, the client uploads the documents through a secure portal; the system classifies and extracts them, populates the correct ProSeries worksheets, and flags two things: a 1099-DIV referenced on the brokerage summary that has not yet been provided, and dividend income materially higher than the prior year.

The preparer opens the populated return in ProSeries, runs its diagnostics, sees both flags, and requests the missing 1099-DIV. They verify the entered W-2 and 1098 figures against the source documents, reconcile the brokerage activity—checking that wash-sale losses are tracked separately as ProSeries requires—apply judgment to the investment income, confirm there are no credit-eligibility questions that require a client interview, and approve the return for signature and e-file. ProSeries never left the picture; it did the calculation, the diagnostics, and the e-file, exactly as it always has.

The repetitive work compressed from most of an hour to a few minutes; the professional's time shifted to the verification, reconciliation, and advice that clients actually pay for—and their name goes on a ProSeries return they genuinely checked. That is the honest promise of automating ProSeries data entry: not a ProSeries replacement and not a preparer replacement, but a data-entry assistant that lets credentialed professionals do more of the work only they can do. The same approach applies if your firm runs Drake or Lacerte.

Frequently asked questions

Does automating ProSeries data entry replace ProSeries?

No. ProSeries stays your system of record for calculation, diagnostics, and e-file. An AI layer reads client documents and populates the correct ProSeries fields; the preparer then reviews, runs diagnostics, and signs inside ProSeries as usual. Automation feeds ProSeries—it does not replace it.

How is this different from ProSeries Scan and Import or Tax Import?

ProSeries Tax Import and Scan and Import are useful but have edges: Tax Import depends on the financial institution supporting the connection and cannot connect when two-factor authentication is enabled, and Scan and Import is not available in ProSeries Basic. An AI layer targets the documents those tools cannot reach cleanly—phone photos, non-participating institutions, unusual layouts—and adds classification and missing-document checks that import tools do not perform.

Who is responsible if an automated ProSeries return is wrong?

The signing preparer. The IRS holds the paid preparer primarily responsible for a return's substantive accuracy regardless of whether software or AI assisted, and preparer penalties attach to the person who signs. That is why verifying every material figure in ProSeries against source documents remains a mandatory control.

Can AI handle 1099-B and brokerage statements in ProSeries?

It can extract and populate the underlying figures, which is the tedious part. But wash-sale losses that ProSeries must track separately, basis adjustments, and multi-broker reconciliation are judgment and review tasks the preparer owns. Automation surfaces the figures and flags the ambiguity; the professional decides and verifies.

Do I need client consent to run their ProSeries data through an AI tool?

Possibly. If the tool uses client return information beyond preparing that client's return—such as training external models—IRC §7216 may require specific, informed taxpayer consent. Confirm data use, retention, and model-training practices, and account for the tool in your Written Information Security Plan under the FTC Safeguards Rule.

Sources and methodology

This article is based on Intuit ProSeries product and support documentation, published IRS guidance, the Internal Revenue Code preparer provisions, FTC and AICPA standards, and Tax Automate product documentation. Illustrative figures are labeled as such and are not statistical claims. Product features and rules are current as of publication and should be verified for the applicable tax year and software version.

• Intuit — ProSeries Tools and Features
• Intuit — ProSeries Tax Import (Scan and Import)
• Intuit — Importing Scanned Source Documents with ProSeries Scan and Import
• Intuit — Methods for Entering 1099-B Stock Transactions in ProSeries
• IRS — PTIN Requirements for Tax Return Preparers
• IRS — Section 7216 Information Center
• IRS — Publication 4557, Safeguarding Taxpayer Data (PDF)
• FTC — Safeguards Rule: What Your Business Needs to Know
• AICPA — Statements on Standards for Tax Services (SSTS)