> 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-backup-and-recovery.md).

# Backups and recovery

Filed captures the selected ProConnect return before it performs data entry. This gives support a precise recovery point if a workspace reports that a run added, changed, or removed the wrong data.

## Backups created during tax prep

The AI Tax Prep summary can show these records in **Backups**:

| Backup            | What it represents                                                                                                                 |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| Initial           | The return read at the beginning of tax prep. For ProConnect, this is also the existing-return context used during reconciliation. |
| Before data entry | The complete selected return immediately before this run writes anything.                                                          |
| After data entry  | The return read after entry and verification finish.                                                                               |

The ProConnect backup is a structured snapshot, not a `.DAT` file and not a file you import through the ProConnect user interface. You can download it for audit purposes, but restoration is handled by Filed support.

## What an exact-run restore does

A restore reverses the operations recorded for one data-entry run:

* Values updated by the run are returned to their pre-entry values.
* Rows or form instances created by the run are removed when safe.
* Values cleared by the run are restored from the pre-entry snapshot.
* Fields the run did not change are left alone.

Before each reversal, Filed checks the value currently in ProConnect. If a preparer changed that value after the Filed run, the restore records a **conflict** and preserves the newer preparer edit instead of overwriting it.

The recovery result separates operations into restored, already restored, conflicts, and failed. Filed performs a fresh return read after recovery so support can verify the resulting state.

## Request a restore

ProConnect restoration is currently a support-assisted backoffice action. Contact Filed support and include:

* The Filed workspace and client name.
* The ProConnect client and return you intended to use.
* The approximate date and time of the data-entry run.
* Why the run must be restored.
* Whether anyone edited the return in ProConnect after the run.

Support will verify the exact run and taxpayer before starting recovery. A restore has no preview step; after confirmation it executes against the selected run and reports any preserved conflicts.

{% hint style="warning" %}
Do not delete the Filed connection or the selected ProConnect return while a recovery request is being investigated. Avoid additional automated data-entry runs on the same return until support confirms the recovery result.
{% endhint %}

## After recovery

Review the return directly in ProConnect. If conflicts were preserved, compare those fields with the source documents and decide whether the newer preparer values should remain. The original tax-prep summary continues to describe the original run; it is an audit record and is not rewritten to look like the run never occurred.


---

# 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-backup-and-recovery.md?ask=<question>&goal=<endgoal>
```

`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.