> 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/troubleshooting/zero-blank-entries.md). # Zero or blank entries after data entry ## What this symptom means This symptom occurs when Filed's data-entry pipeline completes successfully - the data entry and entry validation sub-tasks both finish without error - but the fields in your tax software are empty or contain zero values. The return is not in a failed state; the workflow ran to completion. The values simply did not persist or display in the software. This is distinct from a system error. No error was raised. The pipeline finished and reported success. ## Why it happens The root cause differs by tax software. Common explanations include: * A stale cache in the tax software that needs to be cleared by a recalculation * A misconfiguration in the client's `.DAT` file (CCH Axcess) * A browser-bot session issue that caused entries to appear to succeed but not actually write * A platform-specific sync gap between what the bot entered and what the software stored The resolution steps below are organized by platform because the appropriate first action varies. ## Fix by tax software Identify your tax software below and follow the steps for your platform. ### CCH Axcess Blank entries after a completed data-entry run are a known occurrence with CCH Axcess and are most often caused by a stale cache in the return rather than a failure in data entry itself. Open the return directly in CCH Axcess and click Recalculate. In most cases this clears the cached state and causes the entered values to populate correctly. If the fields are still blank after recalculating, return to Filed and click Re-run Tax Prep to attempt data entry again. If the fields remain blank after both steps, the issue may involve the `.DAT` file configuration. Known causes at this level include an incorrect return configuration or a discrepancy between `.DAT` file version numbers (for example, a V1 versus V2 return ID in the file header). These require engineering review. Contact Filed support to escalate. ### Drake software There is no single confirmed root cause for blank entries in Drake after a completed data-entry run. Click Re-run Tax Prep to attempt data entry again. If the fields are still blank after a second attempt, contact Filed support so the engineering team can investigate. ### UltraTax CS Blank entries in UltraTax after a completed run require engineering review. The engineering team will examine the backup import and data-entry session logs to identify the cause. Report the issue to Filed support and include: * The return ID * Your UltraTax version * The approximate time the run completed, so engineers can locate the correct session recording ## When to contact support Contact Filed support after following the platform-specific steps above if the fields remain blank. Include: * The return ID * Your tax software name and version * Which steps you already attempted (Recalculate, Re-run Tax Prep) * Any confirmation message or error shown in the tax software after your attempts --- # 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/troubleshooting/zero-blank-entries.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.