> 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/tax-software/lacerte.md). # Lacerte Filed integrates with Lacerte through the Filed Desktop app - a lightweight Windows application that runs on the same machine as Lacerte and communicates with it via Intuit's ODBC interface. Lacerte is the only tax software integration that supports the restore capability, allowing Filed to roll a return back to its pre-data-entry state if a correction is needed. ## What this integration does Filed supports four capabilities with Lacerte: * **Sync client list** - Filed imports your Lacerte client roster through the Desktop app so it can match prepared returns to the right clients. * **Read return data** - Before AI preparation begins, Filed captures a snapshot of the client's current Lacerte return. This snapshot is also the restore point used if data entry needs to be undone. * **Enter return data** - After AI preparation is complete, Filed writes the finished data entry directly into the client's Lacerte return on your desktop. * **Restore return data** - If data entry produced an incorrect result or source documents changed after the run, Filed can roll the return back to the snapshot taken before entry began. This is unique to the Lacerte integration. ## Prerequisites * Lacerte installed on a Windows workstation. * The Filed Desktop app installed and running on the same machine. * Intuit SDK consent granted during the initial pairing (the Desktop app handles this step). * The Lacerte client must be closed whenever Filed reads or writes data. ## Connecting Lacerte to Filed Lacerte uses a device-registration pairing model. Filed generates a pairing token that you paste into the Filed Desktop app to link the machine as a Lacerte surface. There is no cloud-only path for Lacerte - the Desktop app must be running. ### Granting Intuit SDK consent During the first-time pairing, the Filed Desktop app briefly minimizes itself so that Intuit's SDK consent dialog is visible. This dialog would otherwise be hidden behind other windows. Accept it to allow Filed to communicate with Lacerte via ODBC. This step occurs only once during setup. If consent is later revoked in Intuit's settings, a "Re-authenticate" prompt will appear in Filed. ## Tax prep workflow Once the Desktop app is connected and the client list has synced, the workflow runs as follows: 1. **Sync client list** - Filed syncs the Lacerte client roster automatically through the Desktop app when the connection is active. 2. **Start Tax Prep** - Open the client in Filed and click Start Tax Prep. Filed checks that the client is not currently open in Lacerte, then reads the current return data and records a snapshot. 3. **AI preparation** - Filed's AI prepares the return using the source documents you have uploaded and the captured return data. 4. **Data entry** - Filed enters the prepared data into the Lacerte return on your desktop automatically. Status updates to "Data Entry Completed." 5. **Review** - Open the return in Lacerte and complete your CPA review before filing. ## Restoring a return to its pre-data-entry snapshot If Filed's data entry produced an incorrect result, or if source documents changed after the run and you want to re-run preparation with updated information, the Restore capability lets you roll the Lacerte return back to exactly the state it was in before Filed began data entry. **What happens during a restore:** Filed dispatches a restore action to the Desktop app, which applies the stored pre-data-entry snapshot to the return in Lacerte via the ODBC interface. The original snapshot artifact is retained. **When to use restore:** * Data was entered incorrectly. * Source documents changed after data entry completed. * You want to re-run AI preparation with updated information. **How to trigger a restore:** In Filed, open the client, go to the Output tab, and click Restore return. Confirm the action when prompted. **Limitations:** Restore only goes back to the most recent pre-data-entry snapshot for the current preparation run. It cannot restore across multiple preparation runs. ## Troubleshooting ### Desktop app not connected or Lacerte not responding The Filed Desktop app must be running and the ODBC connection to Lacerte must be healthy for any operation to work. Open the Filed Desktop app on the Lacerte workstation and verify it shows "Connection active." Also confirm that Lacerte itself is running. Restarting the Desktop app usually re-establishes the ODBC link if it has dropped. ### "Lacerte device unpaired" error This means the desktop surface registered during setup is no longer accessible or has been deleted. Reconnect Lacerte in Filed and complete the device-registration pairing again with the current machine. ### Client is open in Lacerte - data entry blocked Filed runs a preflight check before reading or writing and blocks the operation if the target client is open in Lacerte. Close the client in Lacerte and retry the action in Filed. The Desktop app will prompt you to close the client and can resume automatically once Lacerte reports the client is closed. ### Data entry retries and partial failures If a field cannot be entered, it is marked as failed in the output summary. Review the output summary and manually correct any failed fields in Lacerte before filing. ### Restore is not available for this return Restore requires a pre-data-entry snapshot captured during the read step. If the read step did not complete successfully, no snapshot was taken and restore is not possible. In this case, correct the return manually in Lacerte. ## Frequently asked questions **Does the Filed Desktop app need to be running at all times?** It needs to be running whenever Filed performs an operation - client list sync, reading return data, entering data, or restoring. If the app is closed or the machine is off when an operation is triggered, the operation will wait or fail. An always-on workstation is strongly recommended. **Can I use Lacerte from a remote desktop or hosted environment?** The Filed Desktop app must be installed on the Windows machine that has Lacerte installed. If Lacerte runs inside a remote desktop session, the Desktop app must run inside that same session or on the host machine that Lacerte is running on. **What is the difference between Read return data and Restore return data?** Read return data captures a snapshot of the return before preparation begins and uses it as input to AI preparation. Restore return data takes that same captured snapshot and applies it back to Lacerte, undoing all data entry that has occurred since. **Can I restore a return more than once?** Each preparation run produces one snapshot. You can trigger the restore for the current run as many times as needed - restoring multiple times from the same snapshot is safe. However, restoring from a snapshot created by a previous preparation run is not supported. **Does Filed sync Lacerte client data automatically, or do I need to trigger it?** The Desktop app enables automatic sync when it is connected. You do not need to manually trigger a client list refresh as long as the Desktop app is running. **What happens if the Intuit consent dialog doesn't appear during setup?** The Desktop app minimizes itself to make the dialog visible. If the dialog does not appear, check whether another window is covering it, or check Intuit's SDK settings to confirm consent has not already been granted. If consent was previously granted and revoked, a "Re-authenticate" prompt will appear in Filed when you next try to perform an action. --- # 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/tax-software/lacerte.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.