> For the complete documentation index, see [llms.txt](https://docs.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.filed.com/reference/products/binder/forms.md). # Forms ## What the Forms tab shows The Forms tab displays the tax forms and screens that Filed AI detected and extracted from the client's uploaded documents. It is the interface between the source documents in the Binder and the tax return: Filed AI reads the documents and populates form fields automatically, so the Forms tab shows what the AI extracted and where it came from. Each extracted value is tied back to the source subdocument that drove it, so preparers can verify AI extraction against the original document without leaving the Binder. ## When the Forms tab appears The Forms tab is populated after AI Tax Prep runs for this client; before then it is empty. See the AI Tax Prep section for setup details. ## Reading the extraction grid The Forms tab presents extracted data in a structured grid. Each row corresponds to a form field or line item. The grid shows the extracted value alongside a reference to the source subdocument that the AI read to produce it. Clicking the source reference opens the relevant subdocument in the center viewer at the page where the value appears, making it straightforward to verify extraction accuracy against the original document. The grid columns are **Field**, **Value** (the AI-extracted value), **Entry** (your reviewed/corrected value), and **References** (the AI's explanation and a link to the source subdocument). ## Editing extracted values When a preparer finds that an extracted value is incorrect or incomplete, it can be corrected directly in the Forms tab. **Walkthrough: edit an extracted value** 1. On the Forms tab, each row shows the **Field**, the AI-extracted **Value**, an **Entry** column for your correction, and the **References** explaining where the AI read it. Click into the **Entry** cell for a field and type the corrected value. ![The Forms extraction grid with Field, Value, Entry, and References columns](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-forms/image1.webp) 2. Your entry is saved in the **Entry** column alongside the original AI-extracted **Value**, so both remain visible and the correction is what flows downstream into the return. Changing the underlying source document and re-running tax prep re-extracts the **Value**. ## How Forms relates to tax prep The Forms tab is a quality-check layer between source documents and the tax return. Preparers use it to confirm that Filed AI read each document correctly before the extracted values flow downstream into the return preparation workflow. The Forms tab and the AI Tax Prep workflow are part of the same product and operate on the same extracted data. See the AI Tax Prep section for the full workflow, including how values move from the Binder into the return and what state the forms must be in before they can be used. ## Navigating between forms The Forms tab covers multiple form screens corresponding to the different schedules and statements in the return. **Walkthrough: navigate between forms and verify sources** 1. Use the forms tree in the left panel to switch between form screens (for example, the W-2 under Income and Estimated payments under Payments). The search control at the top of the panel locates a specific form. 2. In the **References** column of any row, click the source reference (the source-document chip with the ↗ icon) to open that subdocument in the center viewer at the page where the value appears, so you can verify the extracted figure against the original. ![The Forms tab with the forms tree and per-row source references](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-forms/image1.webp) --- # 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://docs.filed.com/reference/products/binder/forms.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.