> 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/products/ai-tax-prep/rerunning-after-new-documents.md). # Re-running after new documents ## When this applies A client's Binder often keeps growing after the first AI Tax Prep run: a late K-1 arrives, a corrected 1099 comes in, or a customer uploads a document that was missing at intake. This page covers what happens to the return when you re-run AI Tax Prep after new documents like these have been added to the Binder. For the broader mechanics of a rerun, see [Rerunning and re-exporting](/reference/products/ai-tax-prep/rerun-and-match-and-update.md). This page focuses specifically on the "new documents added" case. ## What happens when you re-run Re-running picks up every document currently in the Binder, including anything added since the last run, not just what was there originally. * **New or corrected data from the added documents is entered.** If a new document introduces a value Filed hasn't planned for yet, that value is written in. * **Existing entries are not overwritten if the field already has a value.** Re-running does not blindly re-enter every field. A field that already holds a value in tax software is left alone; only fields that are still blank get the newly extracted data written into them. In other words, a rerun after new documents is additive: it fills in what's missing rather than replacing what's already there. ## At a glance | Scenario | Does the new data go into Filed? | Does rerunning overwrite what's already in tax software? | What you need to do | | ------------------------------------------------------------------------ | ------------------------------------------------------------------ | -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | A new document is added to the Binder | Yes | No, as long as the field is currently blank | Re-run tax prep from the Forms or Summary tab | | A corrected document is added, replacing one already used in a prior run | Yes, but only into fields you've cleared out in tax software first | No, if the field still has a value in it | Clear the field in tax software (or make the correction directly in the Binder), then re-run | | A correction or new addition is made directly on the Binder's Forms tab | Yes | Yes, the edited field is overwritten | Send to tax prep from the Forms tab. For a small, one-off change, it's usually faster to just make the edit directly in tax software instead | ## Editing the Forms tab directly Editing a value on the Binder's Forms tab and sending it to tax prep is the one path that does overwrite an existing entry, since it's a deliberate edit rather than a passive rerun. This is the right tool when you need a correction to actually replace what's in tax software. See [Forms](/reference/products/binder/forms.md) for how to edit a value there. For a single small correction, it's often quicker to just make the change directly in tax software rather than routing it through Filed. ## Why this matters for corrected documents Because existing values are only left alone when the field is blank, a rerun is reliable for filling in gaps left by newly added documents, but it is not the tool for pushing a corrected number into a field that's already populated. If a new document corrects a value that was already entered, that field needs a manual check afterward. Re-running alone will not overwrite it. If you need a correction to actually overwrite what's in tax software, make the correction directly in the Binder before sending to tax prep. See [Should I re-run tax prep after uploading additional documents?](/reference/products/ai-tax-prep/frequently-asked-questions.md#should-i-re-run-tax-prep-after-uploading-additional-documents) for the decision guide on when a rerun is the right move versus a manual correction. ## Before you re-run * Confirm the new documents have finished processing and appear in the Binder's Docs tab before triggering a rerun. See [What is the Binder?](/reference/products/binder.md). * Download a fresh backup first. See [Reverting tax prep with a backup](/reference/products/ai-tax-prep/reverting-with-backups.md). This is your fastest way back to a known state if a field doesn't land the way you expected. ## After the rerun Review the Summary tab's Confirmed / Flagged / Pending / Manual counts as you would after any run, and check that fields fed by the new documents landed where expected. See [Summary tab](/reference/products/ai-tax-prep/summary-tab.md#after-data-entry-completes). --- # 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/products/ai-tax-prep/rerunning-after-new-documents.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.