> 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/guides/getting-started/before-you-start-checklist.md). # Before you start checklist Five minutes verifying these items now prevents hours of rework on your first return. ## Tax software requirements Every client must already exist as a current-year client in your tax software before you work on them in Filed. For rolled-forward clients, confirm the rollforward is complete. For new clients, create the record in your tax software first. New clients need these four fields populated in the tax software record before anything is sent to Filed: * Taxpayer name * Social Security Number (SSN) * Date of birth * Filing status Filed writes prepared data back into the tax software record. The record must already exist to receive it; Filed does not create tax software records. ## Prior-year return A prior-year return is strongly recommended for every client. Filed's AI uses it to understand the client's tax history, carryovers, and baseline figures, and to build the missing-documents checklist. The upload step marks it optional, but AI Tax Prep is significantly more accurate with it. Upload it during the document upload step when creating the client, or add it to the client's Binder any time before running AI Tax Prep. See [Best practices for preparing your documents](/guides/getting-started/best-practices-for-preparing-your-documents.md) for upload guidance. ## Client name consistency across systems Client names must match exactly across tax software, practice management, and document management systems. Mismatches stop Filed from linking the client record to the correct files from integrated systems. Use the exact name as it appears in the tax software as the canonical form everywhere else. ## Document readiness Before uploading to Filed, confirm: * All source documents for the tax year are collected and accessible (W-2s, 1099s, K-1s, organizer, and any other relevant documents) * Documents are in a readable format - scanned PDFs should be legible, upright, and fully in frame * Complex documents (Schedule K-1 with attachments, carryover schedules) are complete, not partial See [Best practices for preparing your documents](/guides/getting-started/best-practices-for-preparing-your-documents.md) for document-type-specific guidance. ## Document management sync check (if using integrations) For firms using a document management integration (Google Drive, SharePoint, SmartVault, Box, or Dropbox): * Confirm the integration is connected and showing as active in Plugins > Integrations * Confirm the client folder in your DMS or PMS sits within a location Filed has access to - specifically, the folders granted during integration setup * Confirm documents have already been added to the connected folder; Filed syncs in real time, so anything present now is immediately available If you are not using integrations, manual upload via the Add Client flow is always available. ## Understanding what Filed produces Before your team runs its first return: * Filed produces draft returns - these are starting points, not final returns * Professional review and sign-off are required before filing * AI flags and discrepancies surfaced by AI Review are a guide, not a comprehensive audit Review every return before it leaves your firm, as you normally would. ## You are ready - next steps * Workspace not yet set up: [Set up your workspace](/guides/getting-started/set-up-your-workspace.md) * Workspace ready: [Adding your first client](/guides/getting-started/adding-your-first-client.md) --- # 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/guides/getting-started/before-you-start-checklist.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.