> For the complete documentation index, see [llms.txt](https://help.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filed.com/reference/plugins/integrations/tax-software/proconnect-tax/proconnect-tax-prep-and-data-entry.md). # Tax prep and data entry ProConnect tax prep starts from an existing return. Filed reads that return in the signed-in ProConnect browser session, reconciles it with the client's source documents, and writes only the planned changes back to the same return. ## Before you start Confirm that: * ProConnect shows as **Connected** in Filed. * The latest client sync has finished. * The dedicated Filed user can access the client. * The client has an eligible **2025 individual (`IND`) return** in ProConnect. * The client's source documents have been uploaded to Filed. The client name in Filed can differ from the taxpayer name in ProConnect. Treat the ProConnect client and return shown in the selector as the write target and verify both before continuing. ## Select the exact return 1. Open the client in Filed and start **AI Tax Prep**. 2. In **Connect a tax software**, select the active **Intuit ProConnect Tax** connection. 3. Expand **Identify the client in the tax software** and select the matching ProConnect client. 4. Under **2025 individual return**, select the exact return you want Filed to prepare. 5. Turn on **Enter the return into the tax software** if data entry should run automatically after reconciliation. 6. Review any selected protocols and click **Run tax prep**. If the selected client has one eligible return, Filed selects it automatically. If several eligible returns have the same display name, Filed labels them **Return 1**, **Return 2**, and so on. Return IDs remain internal and are not shown as the primary label. If the return selector says that no eligible return was found, [sync ProConnect](broken://pages/gcXKaJzI33DxinkjkXhc#sync-the-client-list) and verify the return is a 2025 individual return. Filed does not substitute another return or fuzzy-match by client name. ## What happens during the run ### 1. Existing-return read and backup Filed signs in to ProConnect and reads the selected return across the supported input screens. This initial read includes prior-year information carried in the return and current-year data already entered by a human preparer. The complete read serves two purposes: * the existing-return context used during reconciliation; and * the immutable **Before data entry** recovery snapshot for this run. There is no `.DAT` import or export in the ProConnect workflow. ### 2. Extraction and reconciliation Filed extracts the uploaded source documents and compares them with the existing ProConnect return. Reconciliation decides whether each item should create a new row, update an existing field, remain unchanged, or be sent for human review. The resulting data-entry plan is tied to the selected ProConnect client and return. Filed validates that target before dispatch and validates the complete payload again inside the authenticated browser before changing the return. ### 3. Data entry and verification Filed applies the plan through ProConnect's input screens using read-modify-write operations. It then reads the affected values back from ProConnect and compares them with the planned values. The result appears as: * **Confirmed** - the value read back from ProConnect matches the planned value. * **Flagged** - the value needs human review because the written and verified values differ or the result is uncertain. * **Pending** - verification has not resolved the field yet. * **Manual** - Filed did not enter the field automatically. In the Binder, each ProConnect screen is shown with a readable form prefix, such as **W-2 ยท s11**. Open **Technical details** only when you need the underlying screen, field, or operation identity. ### 4. Draft return PDF After data entry, Filed asks ProConnect to print the return. When ProConnect produces the PDF, the AI Tax Prep summary shows a **Draft return** preview with an **Open** button. The same PDF can be passed directly to AI Review. ## Run data entry later from the Binder If you ran extraction and reconciliation without enabling data entry: 1. Open the client's **Binder > Forms**. 2. Review the planned forms and source references. 3. Click **Send to data entry**. 4. Confirm the selected ProConnect return and start the entry run. Filed reuses the exact client and return saved with the tax-prep run. If the saved return is no longer eligible, select a current 2025 individual return before continuing. ## Review the completed work From the AI Tax Prep summary: * Check the Confirmed, Flagged, Pending, and Manual totals. * Open a form to compare **Planned**, **In ProConnect**, and **Result** values. * Use source links in the Binder to verify values against the uploaded document. * Preview or open the draft return PDF when available. * Open **Backups** to see the snapshots associated with the run. See [ProConnect backups and recovery](/reference/plugins/integrations/tax-software/proconnect-tax/proconnect-backup-and-recovery.md) before requesting a rollback. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.filed.com/reference/plugins/integrations/tax-software/proconnect-tax/proconnect-tax-prep-and-data-entry.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.