> 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/rerun-and-match-and-update.md). # Rerunning and re-exporting ## What "rerun" means today Clicking **Re-run tax prep** on the Forms tab or Summary tab restarts the full AI Tax Prep pipeline for a client: extraction, reconciliation, planning, and (if enabled) data entry all run again from scratch. This is a full restart, not a small patch - see [Forms tab](/reference/products/ai-tax-prep/forms-tab.md#action-buttons). It is admin-only and charges additional credits, so it should be used when a material change genuinely warrants a fresh pass - for example, a late K-1 that changes the form plan - not for supplementary documents that don't change what needs to be entered. 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. ## Why re-export risked overwriting existing entries A rerun (or a re-export of previously entered data) means Filed is writing into a return that may already have entries in it - either from an earlier Filed run or from manual work done in tax software since. Naively re-entering every planned field risks clobbering something that was already correct, or something a preparer deliberately changed after the first run. ## Match-and-update: reading before writing To avoid that, a rerun is designed to read the current state of the return from tax software before writing anything, and update only where the new plan and the current value actually differ - rather than blindly re-entering every field. In practice this means: * Fields where the current tax-software value already matches what the new plan calls for are left alone. * Fields where the plan has a new or changed value are updated. * Manual corrections made directly in tax software since the last run are meant to be respected rather than silently overwritten, wherever Filed can tell the difference between "stale" and "intentionally corrected." This reconciliation logic is the same mechanism referenced in [How Filed processes the documents](/reference/products/ai-tax-prep/workflow-overview.md#how-filed-processes-the-documents): reconciliation compares extracted data against the prior tax-software state to resolve sources of truth. ## Recommended precaution before any rerun or re-export Because this logic is actively being refined, download a fresh backup before triggering a rerun or re-export on a return with existing entries you care about - see [Reverting tax prep with a backup](/reference/products/ai-tax-prep/reverting-with-backups.md). If a rerun does overwrite something unexpectedly, the **Before data entry** backup from that specific run is the fastest way back to a known state. ## After a rerun Treat the Summary tab's Confirmed / Flagged / Pending / Manual counts as freshly generated for this run - review them the same way you would after a first-time run, rather than assuming only the changed fields need a look. 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/rerun-and-match-and-update.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.