# Home Help, guides, and answers for using Filed. Search for what you need, or browse by topic below.
Getting startedSet up your workspace and run your first client end to end./pages/OSdBnqbf2iPvKJPFwJWd
ProductsAI Tax Prep, Binder, AI Review, AI Tax Planning, and Chat./pages/a0ecVzhaUfsYMvK6TvKx
ClientsThe client hub, files, statuses, and assignments./pages/qBcqFu6Rvsw6J7qPQvf1
Plugins & integrationsTax software, document management, email, and Prowork./pages/SL6ohLZBGjiy7QnwZPDQ
PlaybookEncode your firm's preferences and protocols./pages/acRSQXiqG5Xi2EPy0qdh
Workspace & settingsMembers, single sign-on, credits, and notifications./pages/3pigdAJjwXBgOksixyd7
TroubleshootingFix returns that are stuck, paused, or showing errors./pages/UF5Jkc1aL7jjouahRUaz
SupportReach the team, share feedback, and read the FAQ./pages/MleX8eZLd7mPYPKjEoqR
*** ## Popular articles * [Adding your first client](/getting-started/getting-started/adding-your-first-client) * [Run AI Tax Prep](/reference/products/ai-tax-prep/workflow-overview) * [Why is my return stuck in processing?](/reference/troubleshooting/return-stuck-in-processing) * [Connect CCH Axcess](/reference/plugins/integrations/tax-software/cch-axcess) * [Connect Intuit ProConnect Tax](/reference/plugins/integrations/tax-software/proconnect-tax) * [Set up single sign-on (SSO)](/reference/workspace-and-settings/sso) *** ## Still need help? Can't find what you're looking for? See [Getting support at Filed](/reference/support/getting-support-at-filed) to reach the team. # Introduction This section walks a new firm admin from a blank workspace to a completed first client. Most firms are fully configured within an hour. ## What you will accomplish By the end of this section, you will have: * A workspace with your firm's name, description, and logo * Your team invited and assigned access levels * Integrations connected to your existing tax software, document management, and practice management tools * Your first client created with source documents uploaded and organized in the Binder * A clear picture of how the Filed products work together across a return ## How this section is organized * [**What is Filed?**](/getting-started/getting-started/what-is-filed) - The key objects in Filed: workspace, clients, the client hub, the products, Playbook, and Plugins. * [**Set up your workspace**](/getting-started/getting-started/set-up-your-workspace) - The guided onboarding wizard, from firm creation to team invite. * [**Before you start checklist**](/getting-started/getting-started/before-you-start-checklist) - Prerequisites to verify in your tax software, DMS, and PMS before running any return. * [**Best practices for preparing your documents**](/getting-started/getting-started/best-practices-for-preparing-your-documents) - How to prepare and upload documents for best AI results. * [**Adding your first client**](/getting-started/getting-started/adding-your-first-client) - Creating a client record and reaching the client hub. * [**Your first client, end to end**](/getting-started/getting-started/your-first-client-end-to-end) - A walkthrough threading all the products for one client. ## Recommended path **Firm admin (new workspace):** Start at "What is Filed?" and follow every page in order. **Staff member joining an existing workspace:** Skip to "Before you start checklist," then "Adding your first client." ## Need help along the way? Open the in-app chat from the page where the issue occurs - the support team sees the context of the screen you are on. The chat icon is available on every screen. For SLAs and escalation paths, see the Support section. # What is Filed? Filed is an AI tax-prep platform for accounting firms. It reads client documents, organizes them, prepares draft returns, and checks the draft against the source - all within a workspace your team shares. ## How Filed works The short version: documents go in, Filed organizes and prepares them, and a reviewed draft comes back inside your tax software. Your team stays in control of every decision. The full arc, from intake to filing. 1. **Documents come in.** Filed pulls each client's files automatically from your connected document and practice management systems - or you drop them in by hand or send them from any app with the [Filed Printer](/reference/plugins/filed-printer). 2. **Filed organizes everything.** Filed AI splits and classifies each file into individual documents, tagged by type, issuer, and tax year, in the client's [Binder](/reference/products/binder). 3. **Filed prepares the return.** [AI Tax Prep](/reference/products/ai-tax-prep) extracts the figures, maps them to the right forms and screens, and flags anything that needs a closer look. 4. **Filed checks the work.** [AI Review](/reference/products/ai-review) compares the draft against the source documents and surfaces discrepancies, missing items, and errors - ranked by severity, with the supporting evidence attached. 5. **Your team reviews and signs off.** Professionals review against the source, resolve flagged items, and sign off, with a human-readable audit trail that traces every entry back to its source. 6. **The return lands in your tax software.** Filed enters the prepared data into your tax software, so nothing is re-keyed by hand. Filed accelerates tax prep; professional judgment completes it. Every return should still be reviewed before filing. ## Workspace A workspace is the top-level container for a firm, holding all clients, team members, integrations, and settings. Each firm has one workspace, identified by a name and an optional description and logo. Member roles are **admin**, **L1**, **L2**, and **L3**. Admins manage settings and integrations; staff roles (L1-L3) carry different permission levels. Roles can be assigned at invite time and changed later from Settings > Members. ## Clients A client record contains a name, a return type, and a tax year. The supported return types are: | Return type | Entity label | | ----------- | -------------- | | 1040 | Personal | | 1041 | Trust & Estate | | 1065 | Partnership | | 1120 | Corporation | | 1120S | S-Corporation | | 990 | Nonprofit | Each client is assigned an auto-generated external ID in the format `CLT-{year}-{XXXXXX}` (for example, `CLT-2025-A3B9FZ`), where the last six characters are randomly generated uppercase letters and digits. ## The client hub Each client has a hub page with task tiles for the products. It is the main working surface for a client's return, where all product work is initiated and tracked. Once a client is created and documents are uploaded, the hub reflects the current processing state of each product. ## The products Filed surfaces products as task tiles on every client's hub: | Product | What it does | | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Binder** | The organized document workspace for a client. Filed AI splits every uploaded file into individual documents classified by type, issuer, and tax year. | | **AI Tax Prep** | Reads source documents, extracts figures, maps them to the correct forms, and optionally enters the prepared data into connected tax software. | | **AI Review** | Compares a draft return against source documents in the Binder and surfaces discrepancies, missing items, and potential errors ranked by severity (Critical, High, Medium, Low). | | **AI Tax Planning** | Forward-looking tax analysis and planning for the client. | | **Chat** | A context-aware AI assistant scoped to one client's documents and return data. Answers cite their source in the Binder. | The products are designed to be used in sequence across a return: Binder organizes the documents, AI Tax Prep prepares the draft, AI Review checks it, AI Tax Planning advises, and Chat answers questions throughout. See [Your first client, end to end](/getting-started/getting-started/your-first-client-end-to-end). AI Tax Prep, AI Review, and AI Tax Planning are gated by feature flags; tiles show "Disabled for your firm" when not enabled for the workspace. ## Playbook The Playbook is where firm-level protocols are encoded so AI behavior stays consistent across all clients and team members. Protocols can be set per product (Chat, Binder, AI Tax Prep, AI Review, AI Tax Planning) and scoped to an individual user or the whole workspace. Individual protocols are labelled "Yours"; workspace-wide ones are labelled "Firm's." The Playbook is accessible from the left navigation. ## Plugins Plugins connect Filed to the tools the firm already uses. There are two categories: * **Integrations** - connect tax software (CCH Axcess, Lacerte, UltraTax CS, Drake), document management systems (Google Drive, SharePoint, SmartVault, Box, Dropbox), and email (Gmail, Outlook, IMAP). Once connected, client files flow in automatically and prepared data flows back out. * **Prowork** - surface-level extensions that bring AI capabilities into tools where the team already works. Plugins are managed from the Plugins section in the left navigation. # Setup This guide is for the person creating the workspace - typically the firm admin or managing partner. * Teammates joining an existing workspace skip this flow and start from the client hub. Everything configured here can be adjusted later in Settings or Plugins. The onboarding wizard runs once for new workspaces and walks through five screens: firm details, workflow description, AI integration analysis, team invite, and a completion summary. ## Step 1: create your firm The first screen is titled "Welcome to Filed" and collects three things: * **Firm name** (required) - becomes the workspace display name shown across the product. Example placeholder: "Chen & Torres CPA." * **Describe your firm** (optional textarea) - a free-text description of your firm's specialization and location. Example: "We're a CPA firm specialising in small business tax returns and bookkeeping in New York." This description is used to give the AI context about your practice. * **Logo** (optional) - drag-and-drop or click to upload; appears across the workspace. ## Step 2: connect your tools The second screen is titled "Where do you keep your client data?" It contains a single required textarea, **Describe your document storage and workflows**, with an example placeholder: "We use Karbon for client management, store source docs in Google Drive, and file returns through UltraTax. Clients send us documents by email." Describe your firm's tax software, document management system, practice management system, and how clients deliver documents. Filed reads this to determine which integrations to configure. Two CTAs appear: * **Analyze my workflow** submits the description and continues to the next screen. * **Skip for now** skips integration setup; integrations can be configured later from Plugins. ## Step 3: answer the AI follow-up questions Filed's AI picks up the workflow description and asks targeted follow-up questions to confirm which integrations to configure and how to connect them. Expect a short back-and-forth. When the analysis completes, a summary of suggested integrations appears. If the AI gets stuck, a "Try again" option appears alongside "Skip for now," which goes directly to the invite step. ## Step 4: invite your team The invite screen shows your firm name as the heading and "Bring your team on board" as the subtitle. The **Email addresses** field accepts multiple addresses separated by commas, semicolons, or spaces, and each becomes a pill tag. New invites default to the **L1** role, changeable later from Settings > Members. "Send invitations" dispatches invites to all entered addresses. "Skip for now" advances to the completion screen; you can invite teammates at any time from Settings > Members. ## Step 5: your workspace is ready The completion screen is titled "You're ready to start." It shows a three-item recap: * Firm created - with a link to open firm settings * Tools connected (count) - with a link to manage or add integrations in Plugins * Teammates invited (count) - with a link to manage the team "Go to your workspace" navigates to the clients list. If no clients exist yet, the list is empty, which is expected. The next step is [Adding your first client](/getting-started/getting-started/adding-your-first-client). ## What you can change later Nothing set during onboarding is permanent: * **Firm name and logo** - * **Integrations** - Plugins > Integrations (add, edit, or remove at any time) * **Team members** - Settings > Members (invite, change roles, or remove) * **Binder configuration** - Settings > Binder * **SSO** - Settings > SSO # 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](/getting-started/getting-started/best-practices-for-preparing-your-documents) 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](/getting-started/getting-started/best-practices-for-preparing-your-documents) 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](/getting-started/getting-started/set-up-your-workspace) * Workspace ready: [Adding your first client](/getting-started/getting-started/adding-your-first-client) # Best practices for preparing your documents ## How Filed processes your documents When documents are uploaded, Filed's AI splits multi-document PDFs into individual pages, classifies each by document type, issuer, and tax year, and routes each item into the client's Binder. Source quality directly affects extraction quality: a clean, complete, legible document produces more accurate results than a skewed scan or a partial file. ## Most documents need no special preparation Most documents - W-2s, 1099-INT, 1099-DIV, 1099-NEC, 1099-R, 1098 mortgage interest statements - are standardized forms that Filed handles automatically. Upload them as-is; extra preparation does not improve results for these. ## Documents that need extra attention The following document types are more complex or variable in format, so a little preparation makes a meaningful difference to AI accuracy. ### Schedule A - itemized deductions Before uploading documents that will drive Schedule A, confirm you have: * Medical and dental expense receipts or totals * Property tax statements and state income tax records (taxes paid) * Form 1098 for mortgage interest - confirm the lender name and loan number match the prior year * Charitable contribution receipts with amounts; note whether any non-cash donations require Form 8283 * Casualty and theft loss documentation if applicable If the client has a mix of standard-deduction and itemized years, include the organizer or workpaper that clarifies the current-year intent. ### Sale of home or rental property For a home sale, include Form 1099-S for proceeds. For a rental property disposition, gather: * Form 4797 data (original cost, improvements, accumulated depreciation) * Schedule D inputs * Prior-year depreciation schedules, if the property was previously rented * The settlement statement (HUD-1 or Closing Disclosure) for basis calculation Include the prior-year return page showing the property on Schedule E or Form 4562 so Filed can trace depreciation history. ### All carryovers Carryovers do not appear on any current-year source document - they live in prior-year returns and specific forms. A prior-year return is required in all cases (see [Before you start checklist](/getting-started/getting-started/before-you-start-checklist)). For complex situations, also include: * Form 8582 (passive activity loss carryovers) * Schedule D carryover worksheet (capital loss carryovers) * Form 1045 Schedule B (NOL carryovers) * Form 1116 (foreign tax credit carryovers) * Form 8606 (IRA basis) * Form 3800 (general business credit carryovers) Filed detects carryovers automatically from the prior-year return; these supplemental forms improve accuracy for complex situations. ### Form 8829 - home office deduction Prepare the following before uploading: * Total square footage of the home * Square footage used exclusively and regularly for business * Lease or mortgage statements for the property * Utility and home expense totals for the year If this is the client's first-year home office claim, flag it explicitly in the organizer or a cover note so Filed AI can apply the correct method (simplified vs. regular). ### Schedule K-1s - partnerships and S-corporations K-1s are among the most variable and attachment-heavy documents. For each entity the client is invested in, gather: * Complete K-1 form (from Form 1065 for partnerships, Form 1120S for S-corporations) * QBI statements (Section 199A deduction supporting detail) * Schedule K-2 and K-3 if the entity has foreign activities * Basis worksheets if the client has a basis limitation situation * Supplemental schedules from the entity (state modifications, AMT adjustments) Upload each entity's K-1 package as a single PDF. Do not separate the K-1 from its attachments. ### Schedule C, E, and F - business, rental, and farm income * **Schedule C:** Upload the client's income and expense summary, contractor and 1099-NEC records, and any business mileage log. * **Schedule E (rental):** Include rent rolls, expense receipts by category, and depreciation schedules for each property. * **Schedule F (farm):** Include income records (1099-PATR, crop insurance proceeds) and the expense ledger; note whether the client uses the accrual or cash method. If the client uses accounting software (QuickBooks, Wave, or similar), a P\&L export in PDF is the most efficient input for all three. ## File format and quality tips * **PDF is the preferred format.** JPG and PNG are supported, but extraction accuracy is lower for image files. * **Scanned documents** should be upright, fully in-frame, and legible. Skewed scans, cut-off edges, and low-contrast pages reduce accuracy. * **Multi-document PDFs** are fine. Filed's AI splits and classifies each page automatically. * **ZIP files** are supported and automatically expanded on upload. * **Password-protected PDFs** are not supported. Remove protection before uploading. ## When in doubt, upload more When unsure whether a document is relevant, include it. Filed's AI classifies it and surfaces it in the Binder, and extra context rarely hurts. Misclassified documents can be removed from the Binder after upload. # Adding your first client ## Before you add a client Three things should be in place: * The workspace is set up ([Set up your workspace](/getting-started/getting-started/set-up-your-workspace)) * The client exists in your tax software with the correct name, SSN, date of birth, and filing status ([Before you start checklist](/getting-started/getting-started/before-you-start-checklist)) * Source documents are gathered and ready to upload ([Best practices for preparing your documents](/getting-started/getting-started/best-practices-for-preparing-your-documents)) ## How to open the add client flow The Add Client flow is a two-step modal opened from the clients list. For your first client, the clients list is the default landing page after workspace setup. {% embed url="" %} **Walkthrough: add your first client** 1. From the clients list, click **New client**. On **Step 1 (Add a Client)**, enter the **Client name**, **Client type**, and **Tax year**, then click **Continue**. ![Step 1: the client details form](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/adding-first-client/image1.webp) 2. On **Step 2 (Upload their source documents)**, add the client's source documents via the drop zone or **Browse files**, then click **Create client**. ![Step 2: the document upload drop zone](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/adding-first-client/image2.webp) 3. Filed processes the documents and opens the new client's hub, where the product tiles (Binder, Chat, AI Tax Prep, AI Review, AI Tax Planning) become available as the binder is built. ## Step 1: enter client details The first step is labelled "Add a Client" and is Step 1 of 2. It captures three fields: * **Client name** (required) - use the exact name as it appears in the tax software. Example placeholder: "Johnson & Associates LLC." * **Client type** (required, dropdown) - options are: Personal (1040), Trust & Estate (1041), Partnership (1065), Corporation (1120), S-Corporation (1120S), Nonprofit (990). The client type determines which forms Filed will prepare and which document prompts appear in step 2. * **Tax year** (required, dropdown) - Client type cannot be changed after the client is created. Confirm it before continuing. ## Step 2: upload source documents The second step is labelled "Upload their source documents." It shows a drag-and-drop drop zone that accepts multiple files, and ZIP files are expanded automatically. Filed begins processing when you click "Create client". The upload screen shows context-sensitive guidance based on the client type selected in step 1: * **Personal (1040):** W-2, 1099 forms (INT, DIV, MISC), prior-year 1040, and any organizer or workpapers * **Trust & Estate (1041):** prior-year 1041, beneficiary information, and relevant income and expense documents * **Partnership (1065):** profit and loss statement, partner information, prior-year 1065 * **S-Corporation (1120S):** balance sheet, P\&L, payroll and contractor records, shareholder transactions, prior-year 1120S * **Corporation (1120):** balance sheet, P\&L, payroll records, prior-year 1120 * **Nonprofit (990):** no document prompts are shown for Nonprofit clients; the drop zone appears without a suggested document list. The "Create client" button is disabled until at least one upload has completed. Clicking "Create client" finalizes the record and navigates to the new client's hub page. Additional documents can be uploaded at any time from the client's Binder. ## What happens after you create the client The client hub opens immediately, showing the product tiles: Binder, AI Tax Prep, AI Review, AI Tax Planning, and Chat. Filed automatically classifies the uploaded documents into the Binder. AI Tax Prep becomes available once the Binder finishes processing, which typically takes a few minutes depending on document volume. The client is assigned an auto-generated external ID in the format `CLT-{year}-{XXXXXX}` (for example, `CLT-2025-A3B9FZ`), visible in the client detail panel. The next step is [Your first client, end to end](/getting-started/getting-started/your-first-client-end-to-end). ## Adding clients in bulk The Add Client flow is the manual, one-at-a-time path. Firms with existing client rosters can sync them automatically: CCH Axcess, UltraTax CS, and Lacerte support client-list sync, configured in Plugins > Integrations. Detailed integration setup is covered in the Integrations section. # Your first client, end to end This page walks through a complete return for one client using all the Filed products in sequence. By the end, the client's documents are organized, questions are answered, the draft is reviewed, and data is entered into tax software. Prerequisites: a workspace is set up and a client has been created with at least one document uploaded. See [Adding your first client](/getting-started/getting-started/adding-your-first-client) if you haven't done this yet. Allow 30-60 minutes for a first run on a typical 1040. ## Before you start The client hub should be open, with the product tiles visible: Binder, AI Tax Prep, AI Review, AI Tax Planning, and Chat. If Filed is still processing the uploaded documents, the Binder tile shows a processing state; wait for it to complete before starting AI Tax Prep. ## Step 1: upload the client's documents Source documents reach Filed through one of three paths: * **Manual upload**: drag-and-drop in the Add Client flow or directly into the Binder. * **Document management integration**: Google Drive, SharePoint, SmartVault, Box, or Dropbox. * **Filed Printer**: a virtual printer that sends documents to Filed from any application on your desktop. A typical 1040 document set includes the prior-year return (required), W-2s, 1099s, K-1s, organizer or workpapers, and any supplemental schedules. See [Best practices for preparing your documents](/getting-started/getting-started/best-practices-for-preparing-your-documents) for type-specific guidance. **Walkthrough: upload documents in the Add Client flow** 1. In the **Add Client** flow, on **Step 2 (Upload their source documents)**, drag the client's files onto the drop zone (or use **Browse files**). Each file shows an upload progress indicator, and ZIP archives are expanded automatically. Click **Create client** once at least one upload completes. ![The Add Client upload step with the document drop zone](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/adding-first-client/image2.webp) 2. Filed opens the new client's hub and begins building the Binder. The **Binder** tile first shows a processing state, then updates to reflect the organized documents - a missing-documents count and an observations count once binder creation completes. ![The client hub with the Binder tile showing document signals after processing](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/source-files/image1.webp) ## Step 2: review the organized Binder The Binder is the per-client document workspace. Filed AI splits each uploaded file into individual subdocuments, classifies each by document type, issuer, and tax year, and places them in the Binder. A single uploaded PDF can produce multiple Binder entries. The Binder has three tabs: * **Docs**: all classified documents grouped by category. * **Forms**: tax-prep values extracted by AI Tax Prep (empty until AI Tax Prep has run). * **Leads**: AI Review leadsheets (empty until AI Review has run). The layout is a three-panel view: document list on the left, document viewer in the center, and a Notes & flags panel on the right. The Docs tab shows two key signals: a missing-documents checklist (document types expected for this return type that are not yet in the Binder) and Filed AI observations (notes and flags on documents needing attention). **Walkthrough: review the organized Binder** 1. Open the **Binder** and stay on the **Docs** tab. The left panel lists the classified source documents grouped by category (for example, Income and Payments). Click a document to open it in the center viewer, with the **Notes & flags** activity panel on the right showing the AI's notes anchored to that document. ![The Binder Docs tab: document list, center viewer, and Notes & flags panel](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-docs/image1.webp) 2. Click **Missing documents** at the top of the left panel to see the checklist of document types expected for this return type that are not yet in the Binder. Each item explains why it is expected and offers **Upload**, **Dismiss**, and **Comment** actions. ![The missing-documents checklist with per-item explanations](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-docs/image2.webp) ## Step 3: ask Chat about the client Per-client Chat is scoped to one client's full document set and return data. Every answer cites its source document so you can trace it back to the Binder. Chat is available from the Chat tile on the client hub and from within the Binder. Chat is useful throughout the return, not only at the start. Common uses include looking up a specific figure, summarizing income sources before prep, checking what documents are still missing, and explaining complex documents like K-1s. ### Example 1: look up a specific figure or document Prompt: "What were the total wages on the W-2?" Chat returns the value with a citation to the specific W-2 in the Binder. You can click the citation to open the document at the relevant page. ### Example 2: summarize the client's tax situation Prompt: "Give me a summary of this client's income sources this year." Chat returns a structured overview of income types and amounts drawn from the classified documents in the Binder - useful as a pre-prep orientation before running AI Tax Prep. ### Example 3: check what is missing Prompt: "What documents are still missing for this return?" Chat reads the Binder's missing-documents checklist and lists the gaps, so you know exactly what to chase from the client before proceeding. ### Example 4: compare against the prior year Prompt: "How does this year's income compare to last year?" Chat compares figures across the current and prior-year documents in the Binder. This requires a prior-year return to be present, which is strongly recommended for every client (see [Before you start checklist](/getting-started/getting-started/before-you-start-checklist)). ### Example 5: explain a complex document Prompt: "Explain the Box 20 codes on this K-1." Chat interprets the document, explains each code's tax treatment, and points to where the relevant entries appear in the Binder. ### Example 6: find and jump to supporting evidence Prompt: "Where is the charitable contribution recorded?" Chat identifies the relevant document, states the amount, and provides a deep link into the Binder document at the exact page. ## Step 4: run AI Review AI Review cross-checks a draft return against the source documents already in the Binder and surfaces findings ranked by severity: Critical, High, Medium, and Low. Findings appear as structured leadsheets in the Binder's Leads tab. Before running AI Review, make sure the Binder contains all available source documents. AI Review uses whatever is in the Binder at the time of the run, so a more complete Binder produces better findings. **Walkthrough: run AI Review** 1. Launch **AI Review** from the client hub tile. On **Step 1**, upload the draft return PDF, then click **Next: Confirm source documents**. ![AI Review step 1: upload the draft return](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/ai-review/image1.webp) 2. On **Step 2**, confirm the binder source documents look complete, then click **Start review**. ![AI Review step 2: confirm the binder source documents](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/ai-review/image2.webp) 3. AI Review runs (an in-progress loader is shown) and, when complete, opens a results summary with the total findings and a breakdown of Critical, High, Medium, and Low counts. Click **Open leadsheets** to work through each finding in the Binder's **Leads** tab. For the full results walkthrough, see [AI Review](/reference/products/ai-review) and [Leadsheets](/reference/products/binder/leadsheets). ![The AI Review in-progress loader](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/ai-review/image3.webp) ## Step 5: run AI Tax Prep AI Tax Prep reads the organized Binder documents, extracts figures, maps them to the correct forms, and flags items for attention in Pre-Entry Notes. If a tax software integration is connected (CCH Axcess, Drake, Lacerte, or UltraTax CS), Filed can enter the prepared data directly into the return, with no re-keying. Extraction and Pre-Entry Notes work whether or not a tax software integration is connected. The connection is required only for automated data entry. **Walkthrough: run AI Tax Prep** 1. From the client hub, open the **AI Tax Prep** tile. Filed processes the Binder documents (a processing state shows while it runs) and produces a **Task result** page summarizing what it extracted: the forms detected, counted under **Forms**, **Documents**, and **Gaps**, with a **Forms extracted** breakdown (for example, W2, Taxpayer Info, Estimated Payments, Charitable Contribution). ![The completed AI Tax Prep task result with extracted form counts](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/ai-tax-prep-result/image1.webp) 2. Click **Review results in binder** to open the **Forms** tab, where you verify each extracted value against its source. The AI's Pre-Entry Notes appear in the Binder's **Observations** view (see [Pre-Entry Notes notifications](/reference/products/ai-tax-prep/pre-entry-notes-notifications)). ![The Observations list of AI Pre-Entry Notes](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/observations/image1.webp) If a tax software integration (CCH Axcess, Drake, Lacerte, or UltraTax CS) is connected, the result page also offers a data-entry step to push the prepared values into the return. ## The final value After completing this walkthrough, the firm has: * An organized, classified Binder with all client documents accessible in one place * Quick answers from Chat, each traced to a source document * A reviewed return with findings ranked by severity and resolved or noted * Prepared data entered into tax software, ready for final review and filing Next steps worth exploring: the [Playbook](/reference/products) for encoding firm-level preferences, and [Plugins](/reference/products) for adding or adjusting integrations. # Clients The Clients section is the starting point for all client work in Filed. From here you can find any client, check their status at a glance, assign team members, and open the client hub to run AI-powered tax tasks. ## The client list at a glance The client list displays every client in your workspace as a sortable table. Each row shows: * **Name**: the client's display name, which is editable after creation. * **Return type**: the tax form associated with the client (for example, 1040, 1065, or 1120S). * **Status**: a composite badge reflecting both the client's current binder creation state and whether they have been archived. See [Client Statuses](/reference/clients/client-statuses) for the full breakdown. * **Assigned**: stacked avatars showing team members assigned to this client. Up to three avatars are shown; additional assignees appear as a +N count. * **Created**: the date the client was added to the workspace. The list defaults to newest clients first. You can sort by Name, Status, or Created date by clicking those column headers. ## Searching for a client The search bar at the top of the list filters clients by name in real time as you type. On a long list, it is the fastest way to jump to a specific client. ## Filtering and sorting Four controls let you narrow the list: * **Status filter**: limits the list to clients in a particular state. Options are All statuses, Active, Processing, and Failed. Archived clients are excluded from this filter; use the Archived toggle (described below) to see them. * **Assignee filter**: narrows the list to clients assigned to a specific team member. Useful for reviewing a preparer's workload. * **Sort**: click the Name, Status, or Created column header to sort. Created defaults to newest first (descending). Multiple filters combine: selecting "Active" and a specific assignee shows only active clients owned by that person. ## Viewing archived clients Archived clients are hidden by default. Turn on the **Archived** toggle in the toolbar to reveal them alongside active clients. They display a gray "Archived" badge in the Status column. **Walkthrough: view and restore archived clients** 1. Turn on the **Archived** switch in the client list toolbar. The list shows archived clients, each with a gray **Archived** status badge. ![The client list filtered to archived clients with gray badges](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/clients-archived/image1.webp) 2. To restore one, open the archived client's hub and use the **⋯** actions menu, which shows **Unarchive** in place of Archive. Confirming returns the client to the active list. (See [The client hub](/reference/clients/the-client-hub) for the actions menu.) ## Creating a new client The **New client** button in the top-right corner opens a two-step creation wizard covering client details and document upload. **Walkthrough: create a new client** 1. Click **New client**. On **Step 1 (Add a Client)**, enter the **Client name**, choose the **Client type** (return type) and **Tax year**, then click **Continue**. ![Step 1 of the new-client wizard with name, type, and tax year](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/add-client/image1.webp) 2. On **Step 2 (Upload their source documents)**, drag files onto the drop zone or **Browse files** to add source documents (W-2s, 1099s, organizers, prior-year return). Click **Create client**. The client appears in the list with a **Processing** badge while Filed builds the binder, then switches to **Active** when processing completes. ![Step 2 of the new-client wizard with the document drop zone](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/add-client/image2.webp) ## Bulk actions Select multiple clients using the checkboxes at the left of each row. A bulk action bar appears with the following options: * **Archive**: moves all selected clients to archived status. Client data is preserved and the action is reversible. * **Delete**: permanently removes all selected clients and their data. This cannot be undone. * **Create bulk task** dropdown: lists Run bulk tax prep, Run bulk tax review, and Run bulk tax planning. These options are not yet available; each currently shows a "Disabled for your firm" tooltip. **Walkthrough: bulk actions** 1. Select two or more clients using the row checkboxes. A bulk action bar appears showing the selected count, a **Create bulk task** dropdown, **Archive**, and **Delete**. ![The bulk action bar with multiple clients selected](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/clients-bulk-actions/image1.webp) 2. The **Create bulk task** dropdown lists Run bulk tax prep, Run bulk tax review, and Run bulk tax planning. These are not yet enabled for every firm; a "Disabled for your firm" tooltip appears where unavailable. ![The Create bulk task dropdown options](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/clients-bulk-actions/image2.webp) 3. **Archive** opens a confirmation showing how many clients will be archived; they are hidden from the active list and can be unarchived later. **Delete** permanently removes the selected clients and cannot be undone. ![The bulk Archive confirmation dialog](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/clients-bulk-actions/image3.webp) ## Editing and deleting a client Per-client edit, archive, and delete actions live in the **⋯ actions menu inside the client hub** (open a client, then use the ⋯ button in the header). The menu has three actions: * **Edit client**: opens a dialog where you can change the client's name. Return type is read-only after creation. * **Archive / Unarchive**: moves the client to archived status or restores them. Archived clients retain all documents, binder content, and task history. See [Client Statuses](/reference/clients/client-statuses) for what archiving means. * **Delete client**: permanently deletes the client and all associated data. A confirmation dialog warns that this action cannot be undone. Use archiving instead if you may need the client's data in the future. For a step-by-step walkthrough of these dialogs, see [The client hub](/reference/clients/the-client-hub#client-actions-menu). To archive or delete several clients at once, use the bulk action bar above. ## In this section | Page | What it covers | | --------------------------------------------------------- | ------------------------------------------------------------------------------ | | [The Client Hub](/reference/clients/the-client-hub) | The per-client workspace: the header, the AI product cards, and client actions | | [Managing Files](/reference/clients/managing-files) | Uploading and organizing source documents in the Files panel | | [Client Statuses](/reference/clients/client-statuses) | What each status means and how to filter by status | | [Assigning Clients](/reference/clients/assigning-clients) | Adding and removing team members assigned to a client | # The client hub The client hub is the per-client workspace where all AI-powered tax work happens. It opens when you click any client in the list. ## What is the client hub? The hub is a single page scoped to one client and tax year. It shows a header with key client details and a grid of product cards, each launching a specific AI tool. If a client's documents have never been processed, the hub shows an initial upload view instead of the card grid, prompting you to upload documents first. ## Reading the client header The header identifies the client at a glance. It displays: * **Client name**, with a pencil icon to edit it inline. * **Return type and tax year**: for example, "Personal . 1040 . 2025". Return type is set at creation and cannot be changed. * **Status label**: shows "Active" once documents have been processed, "Processing" while the binder is being created, "Failed" if binder creation encountered an error, or "Archived" in red if the client has been archived. On mobile, the header also contains a **Files** button that opens the full-screen Files panel. ## The product cards The card grid is the launchpad for all AI tools on this client. Each card shows a tool name, a short description, and a live badge reflecting the current task state. Cards are always visible, but some require processed documents or a firm-level feature flag before they become active. ### Binder "View the organized binder." The Binder organizes all uploaded documents into a structured view. It is always shown regardless of feature flags, but becomes interactive only once documents are processed. Badge states for the Binder card: | Badge | Meaning | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Processing | Documents are currently being added to the binder | | Missing + Observations | When binder creation completes, the card always shows both a missing badge and an observations badge together: the missing badge is red "N Missing" when N is greater than 0, or green "0 Missing" when none are missing, alongside a grey "N Observations" badge. Click the missing badge to filter the binder to missing documents. | | Failed | The binder creation workflow encountered an unrecoverable error. | ### Chat "Ask any question about this client." Chat lets you ask natural-language questions about the client's documents and data. It becomes active once documents are fully processed (client status Active). Until then, the card shows the tooltip "Available once documents are processed." ### AI Tax Prep "Automate form extraction and data entry." AI Tax Prep extracts data from source documents and prepares it for entry into your tax software. This card requires the `tax-prep` feature flag to be enabled for your firm. Badge states: | Badge | Meaning | | -------------------- | ---------------------------------------------------------- | | Processing | Tax prep is running | | Ready for data entry | Extraction is complete; the return is ready for data entry | | Done | Data entry preparation is complete | | Failed | Tax prep encountered an error | ### AI Review "Catch mistakes on your draft return." AI Review checks a draft return for errors and inconsistencies. This card requires the `tax-review` feature flag. Badge states are Processing, Done, and Failed. ### AI Tax Planning "Personalized tax strategies." AI Tax Planning generates planning recommendations based on the client's data. This card requires the `tax-planning` feature flag. Badge states are Processing, Done, and Failed. ## Card states and what they mean Two disabled reasons can appear on any card: * **"Available once documents are processed"**: shown on Binder and Chat when the client's binder creation is not yet complete. The client must reach Active status before these tools are accessible. * **"Disabled for your firm"**: shown on AI Tax Prep, AI Review, and AI Tax Planning when the corresponding feature flag is not enabled for your workspace. Contact your account representative to enable a feature. | Card | Processing | Ready / Active | Done | Failed | Disabled reason | | --------------- | -------------------------- | ------------------------ | ---- | ------------------------- | ---------------------------------------- | | Binder | Processing badge (spinner) | 0 Missing + Observations | - | Failed or N Missing badge | "Available once documents are processed" | | Chat | Not applicable | Active (clickable) | - | - | "Available once documents are processed" | | AI Tax Prep | Processing badge | Ready for data entry | Done | Failed | "Disabled for your firm" | | AI Review | Processing badge | - | Done | Failed | "Disabled for your firm" | | AI Tax Planning | Processing badge | - | Done | Failed | "Disabled for your firm" | ## Client actions (⋯ menu) The ⋯ menu in the client hub header provides three actions: * **Edit client**: opens a dialog to rename the client. Return type cannot be changed after creation. * **Archive** (or **Unarchive** if the client is already archived): moves the client off the active list while preserving all data. The confirmation dialog reads: "This client will be hidden from the active list. You can unarchive this client if needed." See [Client Statuses](/reference/clients/client-statuses) for what archiving means. * **Delete client**: permanently deletes the client and all associated data. A confirmation dialog warns that this action cannot be undone. This option appears separated from the others and is displayed in red. **Walkthrough: the client actions menu** 1. From inside a client hub, click the **⋯** button in the header to open the actions menu. It lists **Edit client**, **Archive**, and **Delete client** (Delete is separated and shown in red). ![The client actions menu open](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/the-client-hub-actions-menu/image1.webp) 2. **Edit client** opens a dialog where the **Name** field is editable and the **Return type** is greyed out (it cannot be changed after creation). Click **Save** to apply, or **Cancel** to close. ![The Edit client dialog with an editable name and greyed-out return type](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/the-client-hub-actions-menu/image2.webp) 3. **Archive** opens a confirmation explaining the client will be hidden from the active list and can be unarchived later. ![The Archive confirmation dialog](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/the-client-hub-actions-menu/image3.webp) 4. **Delete client** opens a confirmation that warns the client and all of their data will be permanently deleted and the action cannot be undone. ![The Delete client confirmation with its permanent-deletion warning](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/the-client-hub-actions-menu/image4.webp) ## Navigating between clients To return to the full client list, use the **Clients** link in the left navigation or your browser's back button. Each client hub has a unique URL scoped to that client's ID, which you can bookmark or share with a colleague who has access to the workspace. # Managing files The Files panel is where you upload and review source documents for a client. Files uploaded here drive the Binder, AI Tax Prep, and all other AI tools in the client hub. ## The files panel On desktop, the Files panel appears as a right sidebar within the client hub. On mobile, the **Files** button in the client header opens it as a full-screen dialog. Both views show the same content and controls. ## How files are organized Files are grouped by their source, called a document provider. Each provider appears as a collapsible folder labeled with the source name and a file count. "Manual upload" holds files you upload directly in Filed. If your workspace is connected to a document management system, files synced from that integration appear in their own labeled folder alongside manual uploads. ## Uploading files The **Upload more files** button at the bottom of the panel opens an upload sheet where you can add documents for this client. *Tip: There isn't a limit to how many pages you can upload at once, but we recommend less than 500 pages.* **Walkthrough: upload more files to a client** 1. At the bottom of the **Files** panel, click **Upload more files**. The **Upload more** sheet opens, asking where to bring documents in from. Choose **File upload**. (If your workspace is connected to a document management system, that integration is also listed here as a source.) ![The Upload more sheet with the File upload source](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/managing-files/image1.webp) 2. Select files with the file picker or drag them onto the drop zone. You can add multiple files at once, and ZIP archives are expanded automatically - each file inside is uploaded individually (see [Supported file types](#supported-file-types)). 3. Each new file enters the processing pipeline with a **running** status and moves to **completed** when it has been added to the binder. While files are processing, the client's status reflects the work in progress and returns to **Active** once binder creation finishes; the Binder card badge then shows "0 Missing" if every file was extracted successfully. ## Searching within files A search input at the top of the file list filters rows in real time as you type. It appears only when the panel contains at least one file. If nothing matches, the panel shows a "No files match" empty state. ## Viewing file details Each file row displays: * A file-type icon indicating the format. * The **filename**. * A meta line showing the MIME type, how long ago the file was uploaded (for example, "2 hours ago"), and the file's current processing status. File-level processing statuses are running, completed, and failed. ## Downloading files The Files panel header contains a download icon. Clicking it downloads all files for this client. ## Expanding the files panel An expand icon in the Files panel header opens a larger view of the file list, giving more room to browse or search when a client has many documents. ## File processing states After upload, each file passes through a processing pipeline with three possible states: | Status | Meaning | | --------- | ------------------------------------------------------------------------ | | running | The file is currently being added to the binder and analyzed | | completed | The file was processed successfully; its data is available in the Binder | | failed | The file could not be processed | The aggregate result appears in the Binder card badge on the client hub: "0 Missing" if all files complete successfully, or "N Missing" where N is the count of files that could not be extracted. For the client-level status these results affect, see [Client Statuses](/reference/clients/client-statuses). ## Supported file types Filed accepts the following file types for source document uploads: Best practices: * Include internal context, handwritten notes, organizers, workpapers, and more. * Filed cannot read password protected files * Strongly recommend including prior year tax return in order to Filed to generate a year-over-year comparison (in lead sheets) and a list of missing documents. | Format | Extension(s) | | --------------- | ------------ | | PDF | .pdf | | PNG image | .png | | JPEG image | .jpg, .jpeg | | CSV spreadsheet | .csv | | Excel workbook | .xlsx | | Word document | .docx | | ZIP archive | .zip | ZIP files are automatically extracted on upload: each file inside the archive is unpacked and uploaded individually. Nested files within a ZIP are expanded the same way. Draft return uploads (AI Review) and prior-year return uploads (AI Tax Planning) accept PDF only. ## Troubleshooting failed files A file with a "failed" status could not be processed by Filed's binder creation pipeline. Common causes are corrupted files, password-protected PDFs, or files whose extension matches an accepted format but whose internal content does not. To recover, confirm the file opens correctly on your computer (and, for PDFs, that it is not password protected), then re-upload it. If the problem persists, contact support with the filename and client name. A failed file affects the Binder card badge (showing "N Missing") but does not stop you working with successfully processed files. If the client itself shows a "Failed" status badge, see [Client Statuses](/reference/clients/client-statuses) for what triggered that state. # Client statuses Each client carries two overlapping status signals: a lifecycle state (Active or Archived) and a processing state derived from the most recent binder creation (Active, Processing, or Failed). Both combine into the Status badge shown in the client list and the client hub header. ## How statuses work Every client has a stored lifecycle status of `active` or `archived`. On top of that, Filed derives a display status from the latest binder creation workflow: * **Lifecycle `archived`**: the badge always shows Archived, regardless of binder creation state. * **Lifecycle `active`**: the badge reflects the binder creation outcome - Active (completed), Processing (running), or Failed. So the Active, Processing, and Failed badges only appear for clients that have not been archived. ## Active A client is Active when their most recent document binder has been successfully created. All product cards in the client hub are available and interactive. This is the normal working state. The Active badge appears in green. ## Processing A client shows Processing while binder creation is running, typically just after a client is created with documents or when new files are added. The badge displays an animated spinner. While a client is Processing, the tools are not yet available: * **Chat** is disabled with the message "Available once documents are processed." * **Binder** shows a Processing badge and is not interactive. * **AI Tax Prep**, **AI Review**, and **AI Tax Planning** require processing to complete before they can run. ## Failed A client shows Failed when the binder creation workflow encountered an error that prevented documents from being fully processed. The Failed badge appears in red. When a client is in the Failed state, the Binder card shows a red "Failed" badge. (The "N Missing" badge is a different signal: it appears when binder creation completes but N expected documents were not found, and clicking it filters the binder to those documents. It does not indicate a workflow failure.) To recover, open the Files panel, re-upload the affected files, and wait for binder creation to run again. If the problem persists, contact support with the client name and the names of the affected files. ## Archived Archiving moves a client off the active list without deleting any data. The client retains all uploaded documents, binder content, task history, and assignees. The Archived badge appears in gray. Archived clients are hidden by default. To view them, turn on the **Archived** toggle in the client list toolbar. To restore one, open its ⋯ menu and select **Unarchive**. Archiving is the right choice when a client's work is complete for the year and you want to keep the record without cluttering the active list. Unlike deletion, archived clients can be restored at any time. ## Deleted Deleting a client permanently removes the client record and all associated data: documents, binder content, task results, and assignees. Deletion is initiated from the ⋯ menu and requires confirmation. The dialog states: "This permanently deletes the client and all of their data. This action cannot be undone." A deleted client cannot be recovered. If there is any chance you will need the data later, archive instead. `Deleted` is maintained as an internal database state but is never shown as a badge in the product. Once a client is deleted, they no longer appear anywhere in Filed. ## Status reference table | Status | Trigger | Badge appearance | Product cards available | Recommended action | | ---------- | -------------------------------------- | ---------------- | -------------------------------------------------- | -------------------------------------------------------------- | | Active | Binder creation completed successfully | Green "Active" | All cards | None: normal working state | | Processing | Binder creation is currently running | Animated spinner | None (Binder and Chat disabled; AI tools disabled) | Wait for binder creation to complete | | Failed | Binder creation encountered an error | Red "Failed" | None (Binder shows a red "Failed" badge) | Re-upload affected files; contact support if issue persists | | Archived | Client was manually archived | Gray "Archived" | Not applicable | Unarchive to resume work, or leave archived for record-keeping | ## Filtering by status The **Status** filter in the client list toolbar lets you show only clients in a given state. Available options are: All statuses, Active, Processing, and Failed. Archived clients are not included in any status filter option. They are hidden from the list entirely until you enable the **Archived** toggle. The Archived toggle and the Status filter work independently: when both are active, you see archived clients filtered to whatever additional criteria you have set. # Assigning clients Assignment links workspace members to a client so the right preparer or reviewer owns the work. Each client can have multiple assignees, and assignments are visible directly in the client list. ## How assignment works Assignment operates at the client level, not at the individual form or task level. Any member of your workspace can be assigned to any client. Key behaviors: * **Multiple assignees**: a client can have any number of assignees at once. There is no limit. * **Auto-assignment on creation**: the person who creates a client is automatically added as the first assignee. * **Visibility in the list**: the Assigned column shows stacked avatars, up to three. If more people are assigned, it shows a "+N" count for the remainder. ## Assigning a team member to a client The Assignees popover can be opened from the avatar stack or assign icon in the client hub header. It shows a searchable list of all workspace members with their name, email, and role. A checkmark indicates current assignees. **Walkthrough: assign a team member** 1. Open the client and click **Assign** (the avatar stack or assign icon) in the client hub header. The Assignees popover opens with a **Search people...** box and a list of every workspace member showing their name and role. ![The Assignees popover with the search box and member list](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/assigning-clients-assign-member/image1.webp) 2. Click an unassigned member. A checkmark appears next to their name and their avatar is added to the stack in the header. ![A member assigned, with the checkmark and header avatar updated](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/assigning-clients-assign-member/image2.webp) ## Removing an assignee Clicking a checked team member in the Assignees popover unassigns them from the client immediately. **Walkthrough: remove an assignee** 1. Open the Assignees popover for a client that has one or more assignees. Current assignees show a checkmark. ![The Assignees popover with multiple assignees checked](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/assigning-clients-remove-assignee/image1.webp) 2. Click a checked member to unassign them. The checkmark disappears and their avatar is removed from the header stack immediately. ![The assignee removed, with the checkmark and avatar gone](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/assigning-clients-remove-assignee/image2.webp) ## Reassigning a client Assignees can be added or removed at any time without affecting the client's data or status. To transfer ownership, open the Assignees popover, uncheck the current assignee, and check the new one. Because multiple assignees are supported, you can also add the new person before removing the previous one. **Walkthrough: reassign a client** 1. Open the Assignees popover. The current assignee is checked. ![The Assignees popover showing the current assignee](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/assigning-clients-reassign/image1.webp) 2. Uncheck the current assignee, then click a different workspace member to check them. The header avatar stack updates to reflect the new assignee. ![Reassigned to a different member, with the header avatar updated](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/assigning-clients-reassign/image2.webp) ## Bulk actions from the client list Selecting clients in the list reveals a bulk action bar. Note that **assignment is not a bulk action** - you assign clients one at a time from each client's Assignees popover (see [Assigning a team member to a client](#assigning-a-team-member-to-a-client)). The bulk bar is for running AI tasks across several clients and for archiving or deleting them. **Walkthrough: use the client-list bulk actions** 1. In the client list, tick the row checkboxes for the clients you want to act on (or use the header checkbox to select all). A bulk action bar appears showing the selection count and the actions **Create bulk task**, **Archive**, and **Delete**. 2. Open **Create bulk task** to run an AI task across every selected client at once: **Run bulk tax prep**, **Run bulk tax review**, or **Run bulk tax planning**. **Archive** and **Delete** apply to all selected clients together. ![The client list with two clients selected and the Create bulk task menu open](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/client-list-bulk-actions/image1.webp) ## Filtering the client list by assignee The **Assignee** filter in the client list toolbar narrows the list to clients assigned to a specific workspace member - useful for reviewing a preparer's workload or finding clients with no assignee. It combines with the Status filter: for example, showing all "Failed" clients assigned to a particular team member. ## Roles and permissions Workspace members are assigned one of four roles: Admin, L1, L2, or L3. ## Frequently asked questions **Can a client have multiple assignees?** Yes. There is no limit on the number of team members assigned to a single client. **What happens to assignments when a client is archived?** Archiving a client preserves all existing data, including assignments. If you unarchive the client, the same assignees remain associated with it. **Can I see all clients assigned to a specific person?** Yes. Use the Assignee filter in the client list toolbar to filter by any workspace member. **Is there a way to set a default assignee for newly created clients?** No. There is no default-assignee setting (Settings has only the Firm, Appearance, Members, SSO, and Binder tabs). The member who creates or imports a client is automatically assigned to it, and you can change assignees afterward from the client. **What happens if an assigned user is removed from the workspace?** # Products Filed surfaces products as task tiles on every client's hub. They are designed to work in sequence across a return, though each can be used independently. ## What the products are | Product | Tile description | What it does | | ------------------- | ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Binder** | "View the organized binder" | The organized document workspace for a client. Filed AI splits every uploaded file into individual documents classified by type, issuer, and tax year. Your team annotates, reviews, and signs off within the Binder. | | **AI Tax Prep** | "Automate form extraction and data entry" | Reads source documents in the Binder, extracts figures, maps them to the correct forms, surfaces items for attention in Pre-Entry Notes, and optionally enters prepared data into connected tax software. | | **AI Review** | "Catch mistakes on your draft return" | Compares a draft return against Binder source documents; surfaces discrepancies, missing items, and potential errors as structured leadsheets ranked by severity (Critical, High, Medium, Low). Supported return types: 1040, 1041, 1065, 1120, 1120S, 990. | | **AI Tax Planning** | "Personalized tax strategies" | Forward-looking tax analysis and planning for the client. | | **Chat** | "Ask any question about this client" | A context-aware AI assistant scoped to one client's documents and return data. Answers cite their source in the Binder. Available from the client hub tile and from within the Binder. | AI Review and AI Tax Planning are gated by feature flags. When not enabled for a workspace, the tiles display "Disabled for your firm." ## How they fit together The natural sequence across a return is: 1. **Binder** organizes the uploaded documents - splitting, classifying, and flagging missing items. 2. **AI Tax Prep** reads the Binder and prepares the draft return, extracting figures from classified documents. 3. **AI Review** takes the draft return and cross-checks it against the Binder documents, surfacing discrepancies for the reviewer to resolve. 4. **AI Tax Planning** provides forward-looking analysis once the current-year picture is clear. 5. **Chat** is available throughout - useful for lookup, summarization, and document explanation at any stage. The [Playbook](/getting-started/getting-started/what-is-filed#playbook) shapes how each product behaves across clients: firm-level protocols set in the Playbook are applied automatically by the AI in each product. ## Where you run them Each product appears as a task tile on the client hub. Tiles show the current status of that product for the client: * **Processing** - the product is currently running * **Done** - the most recent run completed successfully * **{N} Missing** - the Binder has flagged missing document types * **Observations** - the Binder has AI observations on existing documents * **Ready for data entry** - AI Tax Prep has completed extraction and is ready to enter data into tax software * **Failed** - the run encountered an error A firm-wide **Analyst** is also accessible from the left navigation. Its scope is the entire workspace, useful for cross-client queries, pipeline overviews, and general tax research. The Home page also has a quick-entry "Ask a question" box that opens a new Analyst thread. ## In this section * [**AI Tax Prep**](/reference/products/ai-tax-prep) - automate form extraction and data entry into connected tax software * [**Binder**](/reference/products/binder) - organize, annotate, and review client documents * [**AI Review**](/reference/products/ai-review) - catch mistakes on a draft return * [**AI Tax Planning**](/reference/products/ai-tax-planning) - personalized tax strategies for clients * [**Chat and Analyst**](/reference/products/chat-and-analyst) - ask the AI about one client or across the firm # AI Tax Prep AI Tax Prep automates the two most time-consuming steps in preparing an individual return: reading the client's source documents and entering data into tax software. Filed: * Reads every uploaded document * Extracts structured data from supported forms * Surfaces issues and missing-document flags via Pre-Entry Notes * Optionally drives the data-entry bot to fill the return in the firm's connected tax software The product card on the client page labels this: "Automate form extraction and data entry." ## In this section These articles walk you through every part of AI Tax Prep, from first run to final data entry. * [Workflow Overview](/reference/products/ai-tax-prep/workflow-overview) - the full pipeline from setup through automated data entry * [Forms Tab](/reference/products/ai-tax-prep/forms-tab) - AI-detected forms organized by category * [Source Files Tab](/reference/products/ai-tax-prep/source-files-tab) - all uploaded source documents * [Pre-Entry Notes Tab](/reference/products/ai-tax-prep/pre-entry-notes-tab) - issues, missing documents, and excluded documents * [Pre-Entry Notes Notifications](/reference/products/ai-tax-prep/pre-entry-notes-notifications) - how to read Priority and Warning flags * [Summary Tab](/reference/products/ai-tax-prep/summary-tab) - pipeline status and data-entry results * [Verifying Entries](/reference/products/ai-tax-prep/verifying-entries) - reviewing the Forms tab before entry and confirming a written value matches what it meant to enter * [Client and Version Matching](/reference/products/ai-tax-prep/client-and-version-matching) - linking Filed to the correct client and return version, and what happens when it's wrong * [Reverting with Backups](/reference/products/ai-tax-prep/reverting-with-backups) - restoring a return to a prior state * [Rerunning and Re-Exporting](/reference/products/ai-tax-prep/rerun-and-match-and-update) - what a rerun does and how it avoids overwriting existing entries * [Re-running After New Documents](/reference/products/ai-tax-prep/rerunning-after-new-documents) - what happens when you re-run after adding documents to the Binder * [Video Walkthrough](/reference/products/ai-tax-prep/video-walk-through) - end-to-end product demonstration * [Downloading Client Files](/reference/products/ai-tax-prep/downloading-client-files) - how to download source documents and tax software backups * [Frequently Asked Questions](/reference/products/ai-tax-prep/frequently-asked-questions) - K-1 extraction, editing AI work, uploading more documents ## Before you start * The client must be created in Filed. * Source documents must be uploaded to the client's Files panel. Filed cannot extract from a return that has no documents. * Connecting a tax software is optional. Extraction, Pre-Entry Notes, and the Forms and Source Files views all work without a connected software. The connection is required only for the automated data-entry bot to fill the return. See the [Connecting Tax Software](https://github.com/filedcom/help/blob/main/filed-help-center/getting-started/connecting-tax-software.md) guide. ## Supported tax software for data entry The automated data-entry bot currently supports: * CCH Axcess Tax * Drake Software * Lacerte * ProConnect * UltraTax CS Connecting tax software is optional. Filed always reads and extracts from the client's forms regardless of whether a connection exists; the connection is required only to enable the bot to enter the return on the firm's behalf. # Workflow overview AI Tax Prep runs as a background pipeline. Once started, Filed processes all uploaded documents, builds a data-entry plan, and optionally drives a bot to fill the return in the firm's tax software - all without requiring the preparer to stay on the page. ## Setting up tax prep for a client The first time a preparer opens AI Tax Prep for a client, an initiation screen appears. It presents two collapsible steps, "Connect a tax software" and "Identify the client in the tax software", with a data-entry toggle below them and a "Run tax prep" button. The screen's subtitle explains the core tradeoff: "Skip any step you don't need. We'll always read the client's forms; connecting a tax software unlocks data entry so we can enter them for you." **Walkthrough: the tax prep setup screen** 1. From the client hub, open **AI Tax Prep** to reach the setup screen. It has two collapsible steps - **Connect a tax software** (with a Connect tax software button) and **Identify the client in the tax software** - plus an **Enter the return into the tax software** toggle and a **Run tax prep** button. Filed always reads the client's forms; connecting a tax software is only needed to unlock data entry. ![The tax prep setup screen with the first step expanded](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/tax-prep-initiate/image1.webp) 2. Expanding **Identify the client in the tax software** reveals where you pick the matching client; until a tax software is connected it prompts you to connect one first. You can skip steps you don't need. ![The setup screen with the second step expanded](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/tax-prep-initiate/image2.webp) ### Step 1 - connect a tax software This step authorizes the data-entry bot to sign in to the firm's tax software on behalf of the firm. Without a connection, Filed will still read and extract from every uploaded document - the connection is only required for automated entry. Choosing "Skip" moves to Step 2 without connecting. ### Step 2 - identify the client in the tax software This field is the identifier used in the firm's tax software to locate the client's return. The bot uses it to open the correct return before filling fields. Step 2 is locked until Step 1 is complete or explicitly skipped. ### Step 3 - enable automated data entry The "Enter the return into the tax software" toggle controls whether the bot runs after extraction. It is grayed out unless a tax software connection is active (or skipped) and a client ID has been entered. When the toggle is off - or when Steps 1 and 2 were skipped - only extraction and planning run. ## Running tax prep **Walkthrough: run tax prep** Click **Run tax prep**. Filed redirects to the active pipeline view, which shows "Running tax prep" with a live processing indicator (for example, "Extracting tax forms"). The page updates automatically as each phase completes, so you can leave and come back. ![The active tax prep pipeline view with a processing indicator](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/tax-prep-running/image1.webp) ## How Filed processes the documents After the pipeline starts, a real-time progress view appears showing each phase as it completes. The pipeline works through these stages: **Document processing and extraction.** Filed reads every uploaded document, splits multi-form PDFs into individual sub-documents, and classifies each by form type and issuer or owner. Extraction runs in parallel across all detected forms. **Reconciliation.** The AI compares extracted data against the prior-year tax software backup when one is available. It builds a per-field data-entry plan, resolving sources of truth and flagging conflicts it cannot resolve automatically. **Planning and finalization.** Filed finalizes the forms list, generates Pre-Entry Notes (issues, missing documents, excluded documents), and writes the summary. The pipeline view shows each phase with a spinner while active and a check mark when complete. Processing time varies by document volume. The preparer can navigate away at any point; the pipeline continues in the background and the view updates automatically when each phase completes. ## Reviewing results After processing completes, four areas of the product are populated: * **Summary** - current status and, after data entry, entry results by field. See [Summary Tab](/reference/products/ai-tax-prep/summary-tab). * **Forms** - all tax forms the AI detected, organized by category. See [Forms Tab](/reference/products/ai-tax-prep/forms-tab). * **Pre-Entry Notes** - issues, missing documents, and excluded documents. See [Pre-Entry Notes Tab](/reference/products/ai-tax-prep/pre-entry-notes-tab). * **Source Files** - every uploaded source document with a viewer. See [Source Files Tab](/reference/products/ai-tax-prep/source-files-tab). ## Automated data entry If the data-entry toggle was enabled at setup and the pipeline completed planning successfully, the data-entry bot runs after extraction. The progress view shifts to a data-entry display showing the current phase: * **Setup** - the bot is preparing and building the data payload. * **Entering** - the bot is actively filling forms in the connected tax software. * **Verifying** - post-entry validation is running; the bot checks its own entries and retries fields where the written value does not match the expected value. The view updates automatically. The Backups panel is visible throughout, showing the current backup count. ### Task status indicators The client tile and the AI Tax Prep view both reflect the pipeline's current state: | Status | What it means | | -------------------- | -------------------------------------------------------------------------- | | Processing | The pipeline is actively running. | | Ready for data entry | Extraction and planning are complete; the data-entry bot has not run yet. | | Done | The full process is complete, including data entry if it was enabled. | | Failed | The pipeline encountered an error it could not recover from automatically. | When the pipeline fails during data entry, the view shows the specific error and the recommended recovery action. The error codes and their meanings are: | Error | What it means | Recovery | | --------------------- | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | | INVALID\_CREDENTIALS | Filed could not sign in to the tax software. | Update the software connection before retrying - repeated failed sign-ins can lock the account. | | CAPTCHA\_FAILED | The login check could not be passed automatically. | Usually clears on its own; try again in a few minutes. | | CLIENT\_NOT\_FOUND | The client ID entered at setup does not match a return in the tax software. | Check the client ID against the software, then try again. | | CLIENT\_ALREADY\_OPEN | The return is open in another session. | Close it in the other session, then try again. | | NOT\_REGISTERED | The tax software is not set up on the workstation. | Register the software on the workstation, then start tax prep again. | | TIMEOUT | The tax software did not respond within the expected window. | Usually clears on its own; try again in a moment. | | UNKNOWN | The pipeline paused for an unexpected reason. Nothing is lost. | Start again - Filed will pick up where it left off. | ## What happens next After AI Tax Prep completes, the recommended next steps are: * Review the [Summary Tab](/reference/products/ai-tax-prep/summary-tab) to see field-level data-entry results. * If Flagged fields appear, open the Binder to inspect each flagged entry against its source document. * If Manual fields appear, enter those items directly in tax software - they come from form types the bot does not currently support. * When a draft return PDF is available in the Summary, click "Run AI Review" to have the AI check the completed return for issues. # Forms tab The Forms tab shows every tax form and screen the AI determined must be prepared, based on what it found in the uploaded documents. It is the AI's bill of work: what will go into the return. The key distinction between tabs: the Forms tab shows what the AI will prepare; the Source Files tab shows what was uploaded. ## Form categories The AI organizes detected forms into categories that follow the binder's category order for the return type, such as General, Income, Adjustments / Deductions, Retirement and Penalty Forms, Taxes / Credits, Payments, and Other Forms / Filings. Grouping is automatic; a form with no category falls into Other Forms / Filings. Workspace admins set the category order per return type in Settings under the Binder section. The user cannot rearrange categories inline. ## Reading the form list Each row in the form list represents one tax screen. A "screen" maps to how the tax software receives data: one W-2 from one employer is one screen; a second W-2 from a different employer is a second screen. If a client has three W-2s from three employers, three W-2 rows appear in the list. Each row shows the form or screen name and the uploaded source document the AI used to detect it. The same form type may appear multiple times when there are multiple payers or sources. ### How screens are named Screen names follow the pattern: form type plus an identifying label, typically the payer or entity name. For example, "W-2 - Acme Corp" and "W-2 - Riverside Medical" are two distinct screens even though both are W-2 entries. The label comes from the issuer field the AI extracted from the document. ## Action buttons **View.** Opens the source document that led the AI to include this form. Use this to verify the AI's reasoning before taking any other action. **Exclude.** Removes the form from the preparation list. Excluded items are moved into the binder's "Excluded / Not Taxable" category. Use Exclude when a form is a duplicate, superseded by a corrected version, or genuinely not needed for this return. **Upload files.** Adds a document to this client without leaving the Forms tab. The uploaded file is added to Source Files and, when material, may prompt a re-run of tax prep to pick up new forms. **View Playbook.** Opens the firm's rules for automatically routing forms to tax software. **Re-run tax prep.** Restarts the full pipeline. This charges additional credits and should be used only when a material change in documents warrants it - for example, when a late K-1 arrives that changes the form plan. ### Access restrictions "Re-run tax prep" and "View Playbook" are visible only to users with admin-level access. These controls are not shown to preparers at lower permission levels. Re-running charges additional credits; do not use it for supplementary documents that do not change the form plan. ## Derivative forms The AI automatically adds forms that are triggered by other detected forms. Examples: * A K-1 with Section 199A amounts triggers the K-199 (QBI) screen. * A Form 1095-A triggers Form 8962 (Premium Tax Credit). * HSA contribution data triggers Form 8889. * Schedule K-3 data from a partnership K-1 triggers the K-3 foreign transaction screens. Filed handles derivative detection automatically. Preparers do not need to know or apply these rules manually. ## Excluding a form **Walkthrough: exclude a form** 1. Open the form in the binder and confirm the AI's source first - in the Forms grid, the **References** column links to the source subdocument so you can verify why the form was included. 2. To exclude it from the return, move the form's subdocument into the binder's pinned **Excluded / Not Taxable** category from the Docs tab (drag it there, or use the document's category controls). Excluded items stay in the binder for reference but are kept out of the prepared return. See [Organizing documents](/reference/products/binder/organizing-documents) for moving documents between categories. When a form appears in the list but should not be part of this return, follow this approach before excluding: 1. Click View to read the source document and understand why the AI included the form. 2. If the form is genuinely unnecessary (a duplicate, a superseded original, or irrelevant to this return), click Exclude. The form is removed from the preparation list and moved into the binder's "Excluded / Not Taxable" category. Excluded items remain visible in the binder's "Excluded / Not Taxable" category. If an exclusion was made in error, the record of it is there. # Source files tab The Source Files tab lists every document uploaded for this client. It is the document viewer - the raw material the AI worked from. The key distinction: the Forms tab shows what the AI will prepare; the Source Files tab shows what was uploaded. ## Navigating the document list The uploaded source files live in the **Files** panel on the right of the client page. This is the list of original uploaded files - what the AI worked from - separate from the AI's internal sub-document splits shown in the Binder. **Walkthrough: open and view a source file** 1. On the client page, the **Files** panel lists every uploaded file grouped by upload source (for example, **Manual upload**). Click the group's chevron to collapse or expand it, and use the search box to find a file by name. The header has controls to download all files and to expand the panel. ![The Files panel on the client page listing uploaded source files](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/source-files/image1.webp) 2. Click a file to open it in the document viewer. The viewer shows the page count, page navigation, zoom and rotate controls, a thumbnail/page panel toggle, search, and a download button. ![A source document open in the viewer with page and zoom controls](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/source-files/image2.webp) Each row in the list represents one uploaded file, showing the filename and the upload source (manual upload or connected integration). The list can be collapsed and expanded to reduce visual clutter when a client has many files. ### Expanding multi-page documents Documents with multiple pages show an expand control (a blue arrow) next to the file row. Clicking it reveals individual pages so the preparer can navigate directly to a specific page - useful when a Pre-Entry Note references a particular page in a long PDF. ### Viewing a document Each row has a View button. Clicking it opens the document in the viewer. This is the primary way to examine a source document when a Pre-Entry Note or a flagged form requires investigation. ## How documents are organized Documents appear in the order they were uploaded or synced. Each uploaded file may contain multiple forms; Filed splits them internally into sub-documents during processing - for example, a single PDF containing a W-2 and a 1099-INT becomes two sub-documents. The Source Files tab shows the original uploaded files, not the AI's internal sub-document splits. ## Adding more documents after tax prep runs To add a document to an existing client, use the Files panel on the client page or the "Upload files" button on the Forms tab. Filed adds the file to the client's source files without creating a new client record. If the new document is material - for example, a late K-1 that introduces new forms the AI has not seen - consider whether to re-run tax prep. Re-running charges additional credits and is restricted to admin-level users. **Do not re-upload the client from the Clients list or home page.** Doing so creates a new, duplicate client record. Always add files to the existing client via the client page Files panel. See [Frequently Asked Questions](/reference/products/ai-tax-prep/frequently-asked-questions) for guidance on when to re-run after uploading additional documents. ## Downloading source files Source files can be downloaded from the client page's Files panel using the download button in the panel header. See [Downloading Client Files](/reference/products/ai-tax-prep/downloading-client-files) for full instructions. # Pre-entry notes tab Pre-Entry Notes is the AI's transparency layer. Before any data enters tax software, Filed surfaces everything it noticed during extraction: conflicts between documents, expected documents that were not uploaded, and documents it chose not to extract from. The goal is to let the preparer make informed decisions before the return is finalized. In the product these surface inside the Binder's Documents screen as two lists, Observations and Missing documents, alongside the binder's "Excluded / Not Taxable" category for documents the AI set aside. ## Observations Observations lists every issue the AI flagged during extraction and reconciliation. Each entry shows the affected form or field, the AI's explanation of what it found, and a severity level. Severities are Critical, High, Medium, and Low. See [Pre-Entry Notes Notifications](/reference/products/ai-tax-prep/pre-entry-notes-notifications) for what each severity means and how to respond. ## Missing documents The Missing documents view shows documents the AI expected to find but that were not uploaded. Filed identifies missing items by comparing uploaded content against the prior-year return: if a form appeared in the prior year but no equivalent was uploaded for the current year, Filed flags it here. Each entry shows what is missing and the AI's reason for expecting it. Each missing-document entry has an Upload action. If the document is genuinely not needed this year, for example a prior-year K-1 from a partnership the client no longer holds, the entry can be dismissed without uploading. The summary line at the top of the list reads: "Based on prior year return the client is missing documentation for X / Y items." The fraction shows how many items remain unresolved out of the total detected. Missing-document entries also appear as annotation flags on the source documents in the Binder, anchored to the location where the AI detected the gap. ## Excluded documents Documents the AI decided not to extract from are moved into the binder's "Excluded / Not Taxable" category, rather than a separate Pre-Entry Notes filter. The AI excludes a file when a more authoritative version exists (for example, an original W-2 when a corrected W-2C was also uploaded), when the document is a duplicate, or when it is not relevant to this return. If an exclusion was made in error, either by the AI automatically or by a preparer using the Exclude button on the Forms tab, the record is in that binder category. The form can be re-included by returning to the Forms tab. ## Reviewing Pre-Entry Notes before data entry The recommended sequence before triggering the data-entry bot: 1. Open Observations and review the Critical and High items first. These represent detected problems that are most likely to produce incorrect entries if left unaddressed. 2. Review the Medium and Low items and decide whether each is a real issue or a false positive. 3. Check Missing documents and upload anything material before entry runs. 4. Confirm the binder's "Excluded / Not Taxable" category is correct. ## How to respond to a specific note **Higher-severity issue (Critical or High).** Open the relevant document, compare the flagged values, determine which is correct (check source documents or consult the client), and correct the value in tax software during or after entry. **Lower-severity issue (Medium or Low).** Review the underlying document and decide whether the AI found a real problem or a false positive. If it is a false positive, proceed without action. **Missing document.** Upload the file via the Files panel on the client page or via "Upload files" on the Forms tab. If the document is intentionally absent this year, dismiss the entry. **Incorrectly excluded document.** Return to the Forms tab. Use View to inspect the document, then remove the exclusion. ## Binder cross-reference AI-flagged items are also surfaced in the Binder as colored annotation marks anchored to the exact location in the source document where the issue was detected. The Observations screen in the Binder shows a consolidated list of all flags and notes, each linked to its source page. # Pre-entry notes notifications Every item in the Observations list carries a severity level: Critical, High, Medium, or Low. The level tells the preparer how urgent the issue is and what kind of response it typically requires. ## The severity levels Filed uses four severity levels, from most to least urgent: Critical, High, Medium, and Low. * Critical and High generally indicate a conflict or data problem that, if left unaddressed, could make the return incorrect. These warrant a decision before or during tax software entry. * Medium and Low generally indicate an ambiguity or potential issue the AI is surfacing for awareness. The AI is being transparent about something it could not resolve definitively, and these may not require action. ## Higher-severity notifications (Critical and High) A higher-severity notification represents a detected conflict or discrepancy that needs a human decision before the return can be considered accurate. A common example is an SSN mismatch: the SSN on the 1040 does not match the SSN on a Form 1098. Filed cannot determine which is correct automatically. Opening the source documents side by side lets the preparer find the correct value and confirm it in tax software during or after entry. Other situations that typically generate higher-severity notifications: * Conflicting values across two documents for the same field (EIN, name, dollar amount). * Extracted data the AI has low confidence in due to document quality or ambiguous formatting. * Fields that require a human decision before a value can be written to the return. ### How to respond to a higher-severity notification **Walkthrough: respond to a conflict observation** 1. In the binder's **Observations** view, find the observation that flags a conflict - for example, "W-2 Box 3 (Social Security wages, $102,000.00) differs from Box 1 (wages, $102,200.00) by $200.00." Each card shows the source document and the AI's full explanation; use **Show more** to read the complete reasoning. 2. Click **View in source doc**. The source document opens with the observation pinned as an annotation on the exact field, and the AI's note appears in the Notes & flags panel on the right. Compare the figures on the document to decide the correct value before it is entered. ![An observation opened in its source document with the AI note pinned to the field](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/observations/image2.webp) Resolve higher-severity items before the data-entry bot runs where you can. An unresolved conflict means the bot may write an incorrect value or skip the field. ## Lower-severity notifications (Medium and Low) A lower-severity notification reflects something the AI noticed but could not definitively classify as a problem. The preparer's judgment is required. A common example is a potential K-1 duplication: the AI sees two K-1s from what appears to be the same partnership. Upon review, they are from two separate partnership interests with different EINs and separate schedule breakdowns. Both are legitimate and two screens are needed, so this is not a real duplicate. Other situations that typically generate lower-severity notifications: * Apparent duplicates that are actually distinct items, for example two K-1s from related but separate entities. * Amounts that look unusual compared to prior year but are legitimate current-year figures. * Edge cases the AI is surfacing for human confirmation rather than acting on autonomously. ### How to respond to a lower-severity notification **Walkthrough: review and resolve a low-priority observation** 1. Open an informational observation - for example, "W-2 Box 5 (Medicare wages, $102,000.00) same as Box 3 - consistent. Informational." Read the AI's reasoning, and use **View in source doc** if you want to confirm the figure against the original. 2. Decide the outcome. If the item is a false positive, click **Dismiss** to remove it from the list. To leave a note for the file or a colleague instead, click **Comment** and reply in the thread that opens in the Notes & flags panel. ![The comment thread on an observation with a reply composer](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/observations/image3.webp) If a lower-severity item turns out to be a real issue after review, correct it. If it is a false positive, note it for the file and proceed without action. ## Finding notifications in the UI **Walkthrough: open the Observations list** 1. From the client hub, the Binder tile shows an "N Observations" badge. Open the Binder and select **Observations** in the left panel (it also carries a count). 2. The **Document observations** view opens - a consolidated list of every finding the AI surfaced while sorting the documents, grouped by document category (Income, Payments, and so on). Each card shows the source document, the finding text, and the actions **View in source doc**, **Dismiss**, and **Comment**. Every observation is also pinned as an annotation on the page it came from. ![The Document observations list grouped by category with per-observation actions](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/observations/image1.webp) The consolidated list groups observations by document category rather than by a severity column; open an individual card to read the AI's full explanation and decide how to respond. ## Binder cross-reference After data entry completes, the same issues that generated these notifications are also visible as colored annotation marks in the Binder, anchored to the exact page and location in the source document where the AI detected the discrepancy. The Binder's Observations screen shows a consolidated list. # Summary tab The Summary tab reflects the client's current position in the tax prep pipeline. What it displays changes as the pipeline moves through its stages: processing, ready for data entry, and complete. ## While processing While the pipeline is running, the page shows a live progress view. Each pipeline phase (binder creation, extraction, reconciliation, planning) appears as a step with a spinner while active and a check mark when complete. The preparer can navigate away; the view updates automatically when the next phase begins and when the pipeline finishes. ## After extraction: ready for data entry When extraction and planning are complete but the data-entry bot has not run yet, the Summary shows the current state as a task result. Three counts are shown: * **Forms** - the number of tax screens the AI built a data-entry plan for. * **Documents** - the number of uploaded source documents the AI extracted from. * **Gaps** - fields or screens the AI could not fully resolve, also visible in Pre-Entry Notes. The Backups panel is present from this point forward. When a prior-year return was imported, an "Initial" backup appears here showing the state of the tax software return before Filed ran anything. This is the correct moment to review the [Forms Tab](/reference/products/ai-tax-prep/forms-tab) and [Pre-Entry Notes Tab](/reference/products/ai-tax-prep/pre-entry-notes-tab) before triggering data entry. ## After data entry completes When the data-entry bot finishes, the Summary shows a completion view with an animated check mark and a "Tax prep complete" badge. The view reports how many forms were entered and how many fields were confirmed, then presents four stat cards: | Card | What it counts | | --------- | ---------------------------------------------------------------------------------------------------------- | | Confirmed | Fields the bot entered and the post-entry validation pass confirmed as correct. | | Flagged | Fields the bot entered but that the validation pass flagged for human review. | | Pending | Fields that are in scope but were not yet confirmed by the validation pass. | | Manual | Fields from form types the bot does not currently support; these must be entered manually in tax software. | When Flagged is greater than zero, an amber alert banner appears: "N fields flagged for review - Open the forms in the binder to review flagged entries." ### Draft return PDF When the tax software produces a draft return PDF after entry, the Summary embeds a preview panel showing the PDF. Two buttons appear above it: * **Run AI Review** - starts an AI review pass on the draft return to check for issues. * **Review results in binder** - opens the Binder's Forms screen to review entered values against source documents. ### Forms list Below the stat cards, the completed view lists each entered form with its confirmed-field count (green check mark) and flagged-field count (amber alert icon). Clicking any row opens the form in the Binder. ## The backups panel The Backups panel, accessible via the archive icon in the Summary, shows automatic snapshots of the tax software return. Three backups are created during a full AI Tax Prep run: | Backup label | When it is created | | ----------------- | ------------------------------------------------------------------------------------------------ | | Initial | Before Filed runs anything - the state of the return as it existed in tax software at the start. | | Before data entry | Immediately before the bot begins filling fields. | | After data entry | After the bot finishes. | Each backup has a download button. For desktop and file-based integrations, the download can be a native tax software backup. ProConnect produces a structured recovery snapshot instead; it cannot be imported through the ProConnect user interface. The most important recovery scenario: if a problem is discovered after the bot runs, use the **Before data entry** backup to identify the pre-Filed state. For ProConnect, contact Filed support for an exact-run restore; see [ProConnect backups and recovery](/reference/plugins/integrations/tax-software/proconnect-tax/proconnect-backup-and-recovery). The Backups panel is visible whenever a backup exists - while the bot is running, while the pipeline is idle between phases, and after the pipeline completes. ## Admin-only controls A gear icon and a "View Playbook" button appear in the Summary for admin-level users. The gear opens firm-level preferences for AI Tax Prep. "View Playbook" shows the firm's rules for automatically routing forms to tax software. These controls are not shown to preparers at lower permission levels. ## What to do after reviewing the Summary tab * **If Flagged is greater than zero:** click "Review results in binder" and inspect each flagged field against its source document. The Binder shows the AI's citation for every entered value. * **If Manual is greater than zero:** open tax software and enter the listed form types manually. The Summary lists which forms are unsupported. * **When a draft return is available:** click "Run AI Review" to run an AI check on the completed return. * **If something went wrong during entry:** open the **Before data entry** backup and follow the restore method for the connected tax software. ProConnect restores are support-assisted. ## TaxPrepSummaryStatus values The following status values drive what the Summary displays. They are exposed in the GraphQL API and may be useful for integrations or support troubleshooting: | Status | Meaning | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------- | | READY\_TO\_PLAN | Extraction complete; reconciliation has not run yet. | | READY\_TO\_ENTER | Reconciliation complete; the data-entry bot has not run yet. | | NOTHING\_TO\_ENTER | Reconciliation ran but produced no actionable per-field targets. | | PLAN\_UNSUPPORTED | A data-entry plan was built, but every planned form is outside the bot's supported list. Manual entry is required. | | NEEDS\_REVIEW | The bot ran and produced results, but some entries need human review. | | PARTIAL\_MANUAL | The bot completed everything it could support, but some planned forms are outside its support list and still need manual entry. | | READY | The bot ran successfully and all entries are confirmed. | # Verifying entries ## Two checkpoints, before and after entry Filed gives you a chance to catch problems at two different points: before the data-entry bot ever touches tax software, and after it finishes. Both matter, and they catch different kinds of issues. ## Before data entry: the Forms tab Before the bot runs, the [Forms tab](/reference/products/ai-tax-prep/forms-tab) shows every form and screen the AI plans to prepare, along with the source document behind each one. This is the moment to review the AI's plan - open a row's source reference, confirm it's reading the right document, and exclude anything that shouldn't be part of the return - before that plan gets written into tax software. See [Reading the form list](/reference/products/ai-tax-prep/forms-tab#reading-the-form-list) and [Excluding a form](/reference/products/ai-tax-prep/forms-tab#excluding-a-form). [Pre-Entry Notes](/reference/products/ai-tax-prep/pre-entry-notes-tab) is the companion review surface at this same stage: conflicts, missing documents, and anything the AI set aside, all surfaced before entry fires. ## How do I know everything exported correctly? After the data-entry bot fills a return, Filed does not just assume the values landed correctly. It reads each field back out of the tax software and compares it against what it meant to enter. This is the verification pass referenced as "Verifying" in the pipeline view (see [Workflow overview](/reference/products/ai-tax-prep/workflow-overview#automated-data-entry)), and its result is what drives the Confirmed / Flagged / Pending / Manual counts on the [Summary tab](/reference/products/ai-tax-prep/summary-tab). ## What gets compared For every field the bot enters, Filed tracks two things: * **The intended value** - what Filed extracted from the source documents and meant to write into that field. * **The verified value** - what Filed reads back from the tax software field after entry. If the two match, the field is marked Confirmed. If they differ, the field is Flagged for review. Values are compared with normal tax-value normalization, so formatting differences alone (commas, cent rounding, currency symbols) do not cause a false mismatch. ## Where to review a flagged field A flagged field does not mean the AI entered the wrong number; it means the value written into tax software did not read back the way Filed expected, and a human should confirm which value is correct. Open the flagged form from the Summary tab's forms list or from the Forms tab directly, and the Binder shows the AI's source citation for the field alongside the value that was entered. Compare the source document to the entered value to decide whether to correct it in tax software or clear the flag. See [Forms tab](/reference/products/ai-tax-prep/forms-tab) for how source references work on each row. ## Why a field might be Pending instead of Confirmed or Flagged Pending means the field is in scope for verification but the pass has not resolved it yet. This can happen while the bot is still running, or for fields where the tax software's own recalculation (for example, a computed subtotal) has not settled at the time Filed reads the value back. Pending fields are not errors; revisit the Summary tab after the pipeline finishes to see whether they resolved to Confirmed or Flagged. ## Manual fields are not verified Manual fields come from form types the data-entry bot does not currently support, so nothing was entered for Filed to verify. These must be entered directly in tax software; see the "Manual" row on the [Summary tab](/reference/products/ai-tax-prep/summary-tab#after-data-entry-completes). ## Relationship to backups Verification confirms individual field values; it does not undo an entry. If a flagged or incorrect value needs to be rolled back, use the Backups panel described in [Summary tab](/reference/products/ai-tax-prep/summary-tab#the-backups-panel) to restore the return to a prior state rather than correcting fields one at a time. # Client and version matching ## Why this step matters Before the data-entry bot can fill a return, Filed needs to know exactly which client record - and which version of that client's return - to write into. Getting this wrong means data lands on the wrong return, not just the wrong field. This is the "Identify the client in the tax software" step in the AI Tax Prep setup screen; see [Step 2 - identify the client in the tax software](/reference/products/ai-tax-prep/workflow-overview#step-2---identify-the-client-in-the-tax-software). ## How the match works The client selected at setup is the same client record the connected tax software uses for the run. Filed does not fuzzy-match on client name. For ProConnect, Filed adds a second selector for the exact **2025 individual return**. If only one eligible return exists, it is selected automatically. If several returns share a display name, Filed distinguishes them as Return 1, Return 2, and so on. The selected client and return are both persisted with the tax-prep run and reused if data entry is started later from the Binder. ## What happens if the wrong client or version is targeted If the identifier does not correspond to any return tax software can find, the bot fails before writing anything, with the error `CLIENT_NOT_FOUND` - see [Task status indicators](/reference/products/ai-tax-prep/workflow-overview#task-status-indicators). This is the safe failure mode: nothing is written to the wrong place because the return could not be located at all. The riskier case is a valid client or return that is not the one the preparer intended. This is why it matters to double-check both selectors against tax software before running tax prep, particularly when the Filed client name differs from the taxpayer name in tax software or when more than one return exists for the year. ## Recovering from a wrong-version send If data entry runs against the wrong version of a return, treat it the same way as any other unwanted entry: use the Backups panel to restore the affected return to its pre-Filed state. See [Reverting tax prep with a backup](/reference/products/ai-tax-prep/reverting-with-backups) for the full walkthrough. Because backups are captured per run, the safest recovery is the **Before data entry** backup captured for that run. ## Before you run tax prep * Confirm the client identifier against tax software directly, not from memory - especially for clients with multiple return years or copies open at once. * If in doubt about which version is active, resolve it in tax software first rather than guessing at setup. * Re-run tax prep uses the same identifier entered originally; if the client's active version changes between the initial run and a rerun, revisit this step before rerunning. See [Rerunning and re-exporting](/reference/products/ai-tax-prep/rerun-and-match-and-update). # Reverting with backups ## Why you might need to revert If the data-entry bot writes something wrong, if a rerun goes sideways, or if you simply want to undo a batch of automated entries and start over manually, the Backups panel provides the recovery record. The restore method depends on the connected tax software. See [Verifying entries](/reference/products/ai-tax-prep/verifying-entries) for the field-level check that catches most problems before a revert is ever needed. ## Where backups come from Every full AI Tax Prep run creates up to three backups, described in [The backups panel](/reference/products/ai-tax-prep/summary-tab#the-backups-panel): | Backup | When it's captured | | ----------------- | ---------------------------------------------------------------------------------------------- | | Initial | Before Filed changes anything - the return exactly as it existed in tax software at the start. | | Before data entry | Immediately before the bot begins filling fields. | | After data entry | Once the bot finishes. | The panel is reached via the archive icon in the AI prep summary, and every backup has a download button. ## Choosing which backup to restore **Something went wrong during or after data entry.** Restore **Before data entry**. This puts the return back exactly where it was right before Filed touched it, so you can re-enter manually or trigger a clean rerun. **You want to undo everything, including a prior-year import.** Restore **Initial**. This is the earliest snapshot Filed has, from before any Filed action at all. **You want a record of what Filed actually wrote, without reverting anything.** Download **After data entry** for your files; there's no need to restore it since it matches the return's current state. ## How to revert **Walkthrough: revert a return using a backup** 1. Open the client's **AI prep summary** and click the archive icon to open the **Backups** panel. 2. Choose the backup that matches the state you want to return to (see above) and click its download button. 3. For tax software that produces a native backup file, restore that file using the software's normal restore workflow. For **ProConnect**, the download is a structured recovery snapshot rather than an importable native backup. Contact Filed support to reverse the exact data-entry run. The restore removes or reverts changes made by that run while preserving newer preparer edits as conflicts. See [ProConnect backups and recovery](/reference/plugins/integrations/tax-software/proconnect-tax/proconnect-backup-and-recovery). ## After reverting Once the return is restored, Filed's own view of field status (Confirmed / Flagged / Pending / Manual on the Summary) still reflects the run that was reverted, not the restored file. If you plan to re-enter or rerun after restoring, see [Rerunning and re-exporting](/reference/products/ai-tax-prep/rerun-and-match-and-update) for what a fresh run does with the client's current tax-software state. # 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#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#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#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). 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#after-data-entry-completes). # Re-running after new documents ## When this applies A client's Binder often keeps growing after the first AI Tax Prep run: a late K-1 arrives, a corrected 1099 comes in, or a customer uploads a document that was missing at intake. This page covers what happens to the return when you re-run AI Tax Prep after new documents like these have been added to the Binder. For the broader mechanics of a rerun, see [Rerunning and re-exporting](/reference/products/ai-tax-prep/rerun-and-match-and-update). This page focuses specifically on the "new documents added" case. ## What happens when you re-run Re-running picks up every document currently in the Binder, including anything added since the last run, not just what was there originally. * **New or corrected data from the added documents is entered.** If a new document introduces a value Filed hasn't planned for yet, that value is written in. * **Existing entries are not overwritten if the field already has a value.** Re-running does not blindly re-enter every field. A field that already holds a value in tax software is left alone; only fields that are still blank get the newly extracted data written into them. In other words, a rerun after new documents is additive: it fills in what's missing rather than replacing what's already there. ## At a glance | Scenario | Does the new data go into Filed? | Does rerunning overwrite what's already in tax software? | What you need to do | | ------------------------------------------------------------------------ | ------------------------------------------------------------------ | -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | A new document is added to the Binder | Yes | No, as long as the field is currently blank | Re-run tax prep from the Forms or Summary tab | | A corrected document is added, replacing one already used in a prior run | Yes, but only into fields you've cleared out in tax software first | No, if the field still has a value in it | Clear the field in tax software (or make the correction directly in the Binder), then re-run | | A correction or new addition is made directly on the Binder's Forms tab | Yes | Yes, the edited field is overwritten | Send to tax prep from the Forms tab. For a small, one-off change, it's usually faster to just make the edit directly in tax software instead | ## Editing the Forms tab directly Editing a value on the Binder's Forms tab and sending it to tax prep is the one path that does overwrite an existing entry, since it's a deliberate edit rather than a passive rerun. This is the right tool when you need a correction to actually replace what's in tax software. See [Forms](/reference/products/binder/forms) for how to edit a value there. For a single small correction, it's often quicker to just make the change directly in tax software rather than routing it through Filed. ## Why this matters for corrected documents Because existing values are only left alone when the field is blank, a rerun is reliable for filling in gaps left by newly added documents, but it is not the tool for pushing a corrected number into a field that's already populated. If a new document corrects a value that was already entered, that field needs a manual check afterward. Re-running alone will not overwrite it. If you need a correction to actually overwrite what's in tax software, make the correction directly in the Binder before sending to tax prep. See [Should I re-run tax prep after uploading additional documents?](/reference/products/ai-tax-prep/frequently-asked-questions#should-i-re-run-tax-prep-after-uploading-additional-documents) for the decision guide on when a rerun is the right move versus a manual correction. ## Before you re-run * Confirm the new documents have finished processing and appear in the Binder's Docs tab before triggering a rerun. See [What is the Binder?](/reference/products/binder). * Download a fresh backup first. See [Reverting tax prep with a backup](/reference/products/ai-tax-prep/reverting-with-backups). This is your fastest way back to a known state if a field doesn't land the way you expected. ## After the rerun Review the Summary tab's Confirmed / Flagged / Pending / Manual counts as you would after any run, and check that fields fed by the new documents landed where expected. See [Summary tab](/reference/products/ai-tax-prep/summary-tab#after-data-entry-completes). # Video walk-through ## Full product demo {% embed url="" %} ## What this video covers * Uploading a client's source documents * Running AI Tax Prep and what the processing step does * Reading the Forms tab and verifying extracted values against their sources * Responding to the AI's Pre-Entry Notes (Observations) * Reviewing results after data entry ## Related articles * [Workflow overview](/reference/products/ai-tax-prep/workflow-overview) - the step-by-step written guide to the full process * [Forms tab](/reference/products/ai-tax-prep/forms-tab) - how to review and act on AI-detected forms * [Pre-Entry Notes notifications](/reference/products/ai-tax-prep/pre-entry-notes-notifications) - how to read and respond to AI flags * [Source Files tab](/reference/products/ai-tax-prep/source-files-tab) - the documents AI Tax Prep worked from * [Frequently asked questions](/reference/products/ai-tax-prep/frequently-asked-questions) - answers to the most common questions # Downloading client files ## When to download client files ## Downloading source documents from the client page ## Downloading tax software backups from the Summary tab ## Important: do not re-upload to start over # FAQ ## K-1 extraction ### How does Filed AI extract and process K-1 data? ### What exactly does Filed extract from each K-1 type? ### Why does the AI flag a potential K-1 duplication in Pre-Entry Notes? *** ## Editing and reviewing AI work ### Can I edit and review Filed AI's work? ### How do I know what needs checking before the return goes to tax software? *** ## Uploading more documents ### What if I need to upload more documents for a client? ### Should I re-run tax prep after uploading additional documents? See [Re-running after new documents](/reference/products/ai-tax-prep/rerunning-after-new-documents) for what actually happens to the return when you do re-run: new documents fill in blank fields, but fields that already have a value are left alone. *** ## Real estate and multiple properties ### How should I upload real estate tax documents for a client with multiple properties? ### What if the AI flags a duplicate for real estate tax amounts? # Binder ## What is the Binder? The Binder is the per-client document workspace in Filed where all review work happens. It is shared across products: both AI Tax Prep and AI Review read from and write into the same Binder for a given client, so every team member works from a single source of truth. When files are uploaded for a client, Filed AI automatically splits and classifies each file into individual subdocuments before they appear in the Binder. A single uploaded PDF can produce several Binder entries, one for each detected form or document type. The team works from these classified subdocuments, not from raw files. The Binder belongs to the client, not to any single workflow. Whether you are preparing a return, reviewing it, or both, the Binder is where source documents, annotations, extracted values, workpapers, and sign-offs all live together. {% embed url="" %} ## How the Binder is organized The Binder uses a three-panel layout: * **Left panel** - the document list and navigation tree. * **Center panel** - the open document and the annotation toolbar. * **Right panel** - three tabs: Notes & flags, the AI Chat assistant, and Shortcuts. Three tabs across the top of the Binder control which workspace is active: Docs, Forms, and Leads. Forms holds AI Tax Prep output and Leads holds AI Review leadsheets; each is populated once the corresponding product has run. ### Docs tab The Docs tab is the primary document review workspace. Subdocuments are grouped into named categories in the left panel, and clicking any subdocument opens it in the center viewer with the full annotation toolbar available. Two status signals appear at the top of the document list: the missing-documents checklist and Filed AI observations. See [Organizing Documents](/reference/products/binder/organizing-documents) for category management and [Annotating and Reviewing](/reference/products/binder/annotating-and-reviewing) for annotation tools. ### Forms tab The Forms tab displays the tax forms and screens that Filed AI extracted from the client's uploaded documents. It is populated after AI Tax Prep runs for this client; before then it is empty. See [Forms](/reference/products/binder/forms) for details. ### Leads tab The Leads tab contains the AI Review workpapers (leadsheets). It supports two views: a spreadsheet-style row view and an issue card view. It is populated after AI Review runs for this client. See [Leadsheets](/reference/products/binder/leadsheets) for details. ## What the Binder shows you The fundamental unit in the Binder is the subdocument. When Filed AI processes an uploaded file, it detects each individual form or item within that file and creates a separate subdocument for each one. Each subdocument has a type (for example, W-2 or 1099-INT), an issuer, and a tax year, and it is automatically placed in the appropriate category. This means the document list in the Binder reflects the logical structure of the client's tax situation, not the physical structure of the files that were uploaded. A single uploaded PDF from a brokerage may produce multiple subdocuments for different 1099 form types, each sitting in its correct category. ## Missing documents and observations Two status signals in the Docs tab help the team identify what still needs attention. The missing-documents checklist compares uploaded documents against the prior year return and lists document types that Filed AI expects for this return but that have not yet appeared in the Binder. The sidebar row shows an amber count badge when items are open and a green checkmark when all are accounted for. Each missing item shows the form type, issuer, and an AI-generated explanation of why it is expected. Items can be dismissed individually if they are not applicable. Filed AI observations are flags and notes surfaced during document processing. They appear both in a dedicated center panel and as anchored marks on the pages they came from. Observations are distinct from human-placed annotations: they are AI-generated and are labeled as either flags or notes. An observation can be dismissed once reviewed, and it can also be the starting point for adding a human flag to the document. ## Downloading the Binder The Binder download dialog offers up to five options: * **PDF workpaper** - documents in Binder order with annotations embedded; Output items excluded automatically. * **Checklist** of missing items - when any exist. * **Forms Excel workpaper** - for business returns when AI Tax Prep is enabled. * **Source documents** - the original uploaded files. * **Leadsheets** as Excel or CSV - when AI Review is enabled. **Walkthrough: download the Binder** 1. In the Docs panel, open the **⋯** (More options) menu and choose **Download workpaper** to open the Download dialog. Check the items to include in the export: **PDF workpaper**, **Checklist (missing items, if any)**, **Source documents (uploaded files)**, and **Leadsheets** (with an Excel or CSV format selector). Options that don't apply to the client are hidden. ![The Binder Download dialog with its export options](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-download/image1.webp) 2. Leave **PDF workpaper** checked and click **Download**. The PDF is generated in Binder order with annotations embedded; **Output** documents are automatically excluded from the PDF. {% embed url="" %} ## In this section * [Organizing Documents](/reference/products/binder/organizing-documents) - categorize, reorder, and manage subdocuments * [Missing Documents Tracking](/reference/products/binder/missing-documents-tracking) - how Filed uses the prior-year return to know what's outstanding * [Marking Document Dispositions](/reference/products/binder/marking-document-dispositions) - recording why a missing item was dismissed (final K-1, extension, N/A) * [Annotating and Reviewing](/reference/products/binder/annotating-and-reviewing) - notes, tickmarks, flags, highlights, cross-references, stamps, and the calculator * [Observations: Dismissing and Restoring](/reference/products/binder/observations-visibility) - working through AI-surfaced observations * [Forms](/reference/products/binder/forms) - view and edit extracted tax-prep form values * [Leadsheets](/reference/products/binder/leadsheets) - review AI Review workpapers by row or by issue * [Template Automation](/reference/products/binder/template-automation) - completing a firm's own templates automatically * [Binder Chat](/reference/products/binder/chat) - ask the AI assistant questions about the client's documents * [Activity and Sign-off](/reference/products/binder/activity-and-sign-off) - the Notes & flags feed, threads, @mentions, and multi-level sign-off # Organizing documents ## How Filed AI classifies your documents When files are uploaded for a client, Filed AI processes each file and detects the individual forms and items it contains. Each detected item becomes a separate subdocument in the Binder, assigned a type (for example, W-2, 1099-INT, or 1099-R), an issuer, and a tax year. The Binder displays these classified subdocuments rather than the original uploaded files. A single uploaded PDF may produce several subdocuments if it contains multiple distinct forms. This means the document count in the Binder will typically be higher than the number of files uploaded. ## The Docs tab layout The left panel in the Docs tab shows a scrollable document tree. Subdocuments are grouped into named categories displayed as collapsible sections. Two broader buckets sit above the category list: Source documents (containing the current year client documents) and Prior year (containing any prior year documents that were uploaded). At the top of the document tree, two rows provide access to the missing-documents checklist and the Filed AI observations panel. Below those, the category list begins. Clicking a subdocument opens it in the center viewer. The annotation toolbar appears above the viewer when a document is open. The right panel shows the Notes & flags feed, chat, or shortcuts depending on which tab is selected. For 1040 returns, the default category order is: General, Income, Adjustments / Deductions, Retirement and Penalty Forms, Taxes / Credits, Payments, Other Forms / Filings, Next Year. Two system categories, Output and "Excluded / Not Taxable", are always pinned at the end of the list and cannot be deleted or moved. Other return types have their own default category sets. ## Reordering documents and categories Documents can be dragged to a new position within their current category or moved to a different category in a single gesture. Categories themselves can be reordered the same way using the drag handle to the left of the category name. **Walkthrough: reorder documents and categories** 1. In the Docs tree, grab a subdocument by its six-dot drag handle and drag it to a new position within its category, or onto a different category to move it there. Release to drop. 2. To reorder categories, drag a category by the handle to the left of its name to a new position. The new order is saved automatically and persists when you refresh the Binder. ## Managing categories The three-dot menu on each category provides rename and delete actions. A new category can be added from the overflow menu near the download button at the top of the Docs panel. Deleting a category removes it from the Binder order for this client's binder. The Output and "Excluded / Not Taxable" categories are system-managed and do not have the same management options as regular categories. **Walkthrough: manage categories** 1. Hover a category in the Docs tree and open its **three-dot menu** to **Rename** or **Delete** it. Deleting a category removes it from this binder's order (its document types are not reassigned automatically). 2. Add a new category from the overflow menu near the top of the Docs panel, then name it. 3. The **Output** and **Excluded / Not Taxable** categories are system-managed: they stay pinned at the end of the list and cannot be renamed, moved, or deleted. (The same category controls, with screenshots, are shown for workspace defaults in [Binder settings](/reference/workspace-and-settings/binder-settings).) ## The missing-documents checklist The missing-documents checklist lists document types that Filed AI expects for this return based on the prior year but that have not yet appeared in the Binder. The checklist row at the top of the document tree shows an amber count badge when items are open and a green checkmark when all are resolved. Clicking the row opens the missing-documents panel in the center. Each item shows the expected form type, the issuer where applicable, and an AI-generated explanation of why the document is expected. Items can be uploaded directly from the panel, or dismissed individually if they are not applicable to this year's return. Dismissed items can be restored. Each missing-document item also supports a comment thread, so the team can discuss a specific missing item directly within the checklist rather than in a separate channel. **Walkthrough: work the missing-documents checklist** 1. Click the **Missing documents** row at the top of the document tree to open the checklist in the center. Each item shows the expected form type, the source/issuer tag, and an AI-generated explanation of why the document is expected, along with **Upload**, **Dismiss**, and **Comment** actions. ![The missing-documents panel listing expected documents with AI reasons](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-missing-documents/image1.webp) 2. Use **Upload** to add the document directly from the panel, or **Dismiss** an item that does not apply to this year's return. A dismissed item appears struck through with a **Restore** button, and the open count decreases. ![A dismissed missing-document item shown struck through with a Restore button](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-missing-documents/image2.webp) ## Workspace-level binder defaults Workspace admins can configure the default category and document-type order per return type (1040, 1065, 1120, 1120S, 1041, and 990) in Settings under the Binder section. From there, categories can be renamed, reordered, deleted, or added, and document types within each category can be managed. Changes can be reset to Filed defaults at any time. An important constraint: workspace defaults apply only to new Binders created after the change is saved. Existing Binders for current clients keep their current category order and are not affected. To apply a new default structure to an existing Binder, the category order in that Binder must be updated manually. # Missing documents tracking ## How Filed knows what's missing Filed builds the missing-documents checklist by comparing what's been uploaded this year against the client's prior-year return. If a document type appeared last year - a K-1 from a specific partnership, a 1099 from a specific brokerage - and no equivalent has been uploaded this year, Filed lists it as expected but not yet received. This is why the checklist requires a prior-year return to be meaningful: without one, Filed has nothing to compare against. This is the same comparison engine described in [How Filed compares current-year values against prior year](/reference/products/ai-review/prior-year-comparison); the missing-documents checklist is simply the "not yet uploaded" output of that comparison, surfaced during AI Tax Prep rather than later during review. ## Where the checklist appears The checklist sits at the top of the Docs tab's document tree, with an amber count badge when items are still open and a green checkmark once everything is accounted for. Clicking it opens the panel in the center, where each item shows the expected form type, the issuer where known, and an AI-generated explanation of why it's expected. See [The missing-documents checklist](/reference/products/binder/organizing-documents#the-missing-documents-checklist). The same information also appears in AI Tax Prep's Pre-Entry Notes before any data entry happens - see [Missing documents](/reference/products/ai-tax-prep/pre-entry-notes-tab#missing-documents), including the summary line "Based on prior year return the client is missing documentation for X / Y items." ## Resolving a missing-document item Each item supports **Upload** (add the file directly from the panel) and **Dismiss** (mark it as not applicable to this year, without uploading anything). Dismissed items can be restored. See [Marking document dispositions](/reference/products/binder/marking-document-dispositions) for how to record *why* an item was dismissed - final K-1, extended, no longer applicable - since the dismiss action itself doesn't currently capture a reason. ## Why a first-year client won't have a missing-documents checklist Without a prior-year return on file, Filed has no baseline to compare against, so the checklist will be empty regardless of how complete the current year's documents actually are. This isn't a sign that everything has been uploaded - it means the comparison simply couldn't run. Import or upload a prior-year return for the client if one exists, so future returns get the benefit of this check. # Marking document dispositions ## What a "disposition" means here When a missing-document item doesn't need to be resolved by uploading a file, it needs a disposition instead - a record of *why* it's being left open. Common reasons: this was the client's final K-1 from a partnership they've exited, the return itself is on extension so the document isn't expected yet, or the item genuinely does not apply to this client this year (N/A). ## What's available today The missing-documents checklist currently supports a single **Dismiss** action per item, with a matching **Restore** if a dismissal needs to be undone - see [The missing-documents checklist](/reference/products/binder/organizing-documents#the-missing-documents-checklist). Dismissing removes the item from the open count, but dismissal by itself doesn't capture *which* of the reasons above applied. ## Recording the reason today Until a dedicated disposition field exists, record the reason using the comment thread available on each missing-document item, before or when dismissing it: **Walkthrough: dismiss with a recorded reason** 1. Open the missing-documents checklist and find the item. 2. Click **Comment** and note the reason - for example, "Final K-1 from Riverside Partners; client's interest was fully liquidated in \[prior year]" or "Return is on extension; 1099 not expected until \[date]." 3. Click **Dismiss**. The item is struck through and the open count decreases; the comment thread remains attached to the item so the reason is preserved for anyone reviewing later. This keeps the reasoning attached to the specific item, visible to anyone who opens it later, even though it isn't yet a structured field you can filter or report on. ## If you need to reverse a disposition Use **Restore** on the dismissed item to bring it back into the open checklist - useful if a document that was marked final or N/A turns out to be needed after all (for example, the client's K-1 wasn't actually final). # Annotating and reviewing ## The annotation toolbar The annotation toolbar appears above the center document viewer when a subdocument is open on the Docs tab. It is available on the web app and is not shown when the missing-documents checklist or observations panel is the active center view. The toolbar contains two groups of tools. Primary tools are always visible: | Tool | Shortcut | Purpose | | ---------------- | -------- | ------------------------------------------------------------------- | | Select | V | Select, move, and edit existing annotations | | Pan | H | Drag to pan around the page without placing annotations | | Note | N | Drop a timestamped, attributed note on a specific location | | Check (Tickmark) | C | Place a checkmark to mark a location as reviewed | | Flag | F | Mark a spot that needs attention, with an optional explanatory note | | Highlight | G | Highlight a region of text or an area on the page | Secondary tools appear in the overflow area on smaller screens or via the expanded toolbar: | Tool | Shortcut | Purpose | | --------------- | -------- | ------------------------------------------------------------------------- | | Textbox | T | Add free-form text directly onto the document surface | | Stamps | S | Apply a pre-set stamp label to the document | | Cross-Reference | X | Link a figure on this document to its matching figure on another document | | Calculator | K | Open a tape calculator in the right panel and save the result as a mark | | Eraser | E | Remove existing annotations | ## Notes A note is a timestamped, attributed mark dropped on a specific location on the document page. Notes are attributed to the team member who placed them and appear in the Notes & flags feed. Any note can grow into a conversation thread when teammates reply to it. **Walkthrough: add a note** 1. Click the **Note** tool (N) in the toolbar, then click the spot on the document where the note belongs. A note marker is placed and a composer opens in the right panel. ![A note marker on the document with the note composer open](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-note/image1.webp) 2. Type your note and click **Save**. The note appears in the Notes & flags feed, attributed to you with a timestamp, and a **Reply…** box lets you (or a teammate) open it into a thread. ![The saved note in the feed with a reply box to start a thread](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-note/image2.webp) ## Tickmarks The Check tool places a tickmark on the document to indicate that a specific location has been reviewed. A tickmark is a lightweight confirmation mark, not a formal sign-off. It signals to the team that the annotating reviewer has looked at a particular item. Tickmarks appear in the Notes & flags feed and can be filtered there. ## Flags A flag marks a location that needs attention. It can carry an optional explanatory note. Open flags are visible in the Notes & flags feed and serve as a checklist of items still requiring resolution. Filed AI can also place flags automatically from the AI alerts panel. Sign-offs and flags are independent signals: signing off a document does not automatically clear flags. A reviewer can sign off while leaving flags open for someone else to act on. **Walkthrough: place a flag** 1. Click the **Flag** tool (F) in the toolbar, then click the spot on the document that needs attention. A red flag marker is placed and a note composer opens. 2. Type an optional explanatory note and click **Save**. The open flag appears in the Notes & flags feed and a flag indicator shows on the document in the Docs tree. ![A red flag placed on the document with its note shown in the feed](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-flag/image1.webp) ## Highlights The Highlight tool marks a region of text or an area on the page. It is useful for drawing attention to specific figures or passages without adding a full note or flag. Highlights appear in the Notes & flags feed and can be filtered there. ## Textboxes The Textbox tool adds free-form text directly onto the document surface. Text placed with this tool appears as an overlay on the document and travels with the document in the downloaded PDF workpaper. Textboxes are distinct from notes: they sit on the document visually rather than appearing as a pin-style marker. ## Stamps Stamps apply a pre-set label to the document. Six stamp types are available: Reviewed, Approved, Rejected, Draft, Copy, and Confidential. Stamps appear as visual overlays on the document and are included in the downloaded PDF workpaper. **Walkthrough: apply a stamp** 1. Click the **Stamps** tool (S) in the toolbar to open the stamp palette, which offers Reviewed, Approved, Rejected, Draft, Copy, and Confidential. ![The Stamps palette with the six stamp types](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-stamps/image1.webp) 2. Select a stamp type, then click the spot on the document where it should go. The stamp appears as a visual overlay on the page and is included when the Binder is downloaded as a PDF workpaper. ![A "Reviewed" stamp placed on the document](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-stamps/image2.webp) ## Cross-references (tie-outs) A cross-reference links a figure on one subdocument to its matching figure on another, creating the digital equivalent of a pencil tie-out line. Two linked anchor marks are created: one on each document. Clicking either anchor jumps directly to the paired document and page. Cross-references connect marks across two different subdocuments. The two halves of a cross-reference remain linked; removing one removes both. **Walkthrough: link a cross-reference (tie-out)** The Cross-Reference tool lives in the **More tools** overflow (the **⋯** at the end of the toolbar), alongside Textbox, Calculator, and Eraser. ![The More tools overflow showing the Cross-Reference tool](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-cross-reference/image1.webp) 1. Open Document A, activate the **Cross-Reference** tool (X), and click the source figure. Name the reference and save. An anchor mark is placed on Document A. 2. Open Document B, activate the **Cross-Reference** tool again, click the matching figure, and link it to the existing reference. A paired anchor is placed on Document B. 3. The two anchors are now linked: clicking either anchor jumps directly to the paired document and page. Removing one anchor removes both. ## Editing and removing annotations The Select tool (V) allows existing annotations to be moved or edited in place. Clicking an annotation with the Select tool opens its edit state. The Eraser tool (E) removes an annotation permanently. Removing an annotation that has a comment thread attached also removes the thread. **Walkthrough: edit and remove annotations** 1. Click the **Select** tool (V), then click an existing annotation to select it. You can drag it to reposition it, or open its edit state to change the text. 2. To remove an annotation, open **More tools** (the **⋯** at the end of the toolbar) and choose the **Eraser** (E), then click the mark you want to delete. The annotation is removed from the document and disappears from the Notes & flags feed (removing an annotation that has a thread also removes the thread). ![A flag removed with the Eraser — the marker is gone from the document and the feed](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-select-eraser/image1.webp) ## The tape calculator The Calculator tool (K) opens a tape calculator in the right panel. Entries can be labeled and the result is saved as an annotation mark on the document. The saved mark stores the expression, individual labeled entries, and the result. Calculator marks appear in the Notes & flags feed and travel with the document in the PDF workpaper. ## Annotations in the PDF workpaper When the Binder is downloaded as a PDF workpaper, all annotations are embedded in the output. Notes, flags, highlights, textboxes, stamps, and cross-reference anchors all appear in the PDF at their placed positions. Output-category documents are excluded from the PDF workpaper automatically. ## Acting on Filed AI observations Filed AI observations are flags and notes surfaced automatically during document processing. They appear both in a dedicated panel (accessed via the observations row at the top of the document tree) and as anchored marks on the document pages they reference. The observations panel displays a count of active observations broken down by flags and notes. Each observation can be dismissed once reviewed. A dismissed observation appears struck through in the list and its document anchor is removed from the page. Dismissed observations can be restored. From any observation, a human flag can be added to the same document location. This is useful when the AI has surfaced something worth tracking formally in the team's review workflow. **Walkthrough: act on AI observations** 1. Click **Observations** at the top of the document tree to open the consolidated observations panel. Each observation shows the document it came from, the AI's finding, and actions: **View in source doc**, **Dismiss**, and **Comment**. The note icon on an observation lets you add a human flag at the same document location. ![The observations panel listing active AI observations with their document anchors](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-observations/image1.webp) 2. Click **Dismiss** on an observation once you have reviewed it. It appears struck through with a "Dismissed by …" line and its document anchor is removed. A **Restore** button lets you bring it back. ![A dismissed observation shown struck through, with a Restore button](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-observations/image2.webp) # Observations: dismissing and restoring ## What an observation is Filed AI observations are flags and notes the AI surfaces automatically during document processing - distinct from notes or flags a person places manually with the annotation toolbar. They appear both in a dedicated observations panel and as anchored marks on the document pages they reference. See [Acting on Filed AI observations](/reference/products/binder/annotating-and-reviewing#acting-on-filed-ai-observations). ## Dismissing an observation Each observation in the panel has **View in source doc**, **Dismiss**, and **Comment** actions. Dismissing one you've reviewed strikes it through in the list, removes its anchor from the document page, and shows a "Dismissed by …" line recording who did it. **Walkthrough: dismiss and restore an observation** 1. Open the **Observations** panel from the row at the top of the document tree. 2. Review the observation's finding and source, then click **Dismiss** once you've decided it doesn't need further action. 3. The dismissed item appears struck through with a **Restore** button. Click **Restore** at any time to bring it back into the active list. ## Who can see an observation Observations are visible to anyone on the team with access to the client's binder - they aren't hidden behind a specific sign-off level. Dismissing an observation doesn't remove it from the record; it's struck through and attributed, so a partner reviewing later can still see what was surfaced and who cleared it. ## Observations vs. human flags Dismissing an observation is not the same as resolving a flag. If an observation surfaces something worth tracking formally as part of the team's review workflow, add a human flag at the same location directly from the observation - see [Acting on Filed AI observations](/reference/products/binder/annotating-and-reviewing#acting-on-filed-ai-observations). The flag then follows normal flag behavior (visible in the Notes & flags feed, independent of sign-off) rather than the AI-observation dismiss/restore lifecycle. # Forms ## What the Forms tab shows The Forms tab displays the tax forms and screens that Filed AI detected and extracted from the client's uploaded documents. It is the interface between the source documents in the Binder and the tax return: Filed AI reads the documents and populates form fields automatically, so the Forms tab shows what the AI extracted and where it came from. Each extracted value is tied back to the source subdocument that drove it, so preparers can verify AI extraction against the original document without leaving the Binder. ## When the Forms tab appears The Forms tab is populated after AI Tax Prep runs for this client; before then it is empty. See the AI Tax Prep section for setup details. ## Reading the extraction grid The Forms tab presents extracted data in a structured grid. Each row corresponds to a form field or line item. The grid shows the extracted value alongside a reference to the source subdocument that the AI read to produce it. Clicking the source reference opens the relevant subdocument in the center viewer at the page where the value appears, making it straightforward to verify extraction accuracy against the original document. The grid columns are **Field**, **Value** (the AI-extracted value), **Entry** (your reviewed/corrected value), and **References** (the AI's explanation and a link to the source subdocument). ## Editing extracted values When a preparer finds that an extracted value is incorrect or incomplete, it can be corrected directly in the Forms tab. **Walkthrough: edit an extracted value** 1. On the Forms tab, each row shows the **Field**, the AI-extracted **Value**, an **Entry** column for your correction, and the **References** explaining where the AI read it. Click into the **Entry** cell for a field and type the corrected value. ![The Forms extraction grid with Field, Value, Entry, and References columns](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-forms/image1.webp) 2. Your entry is saved in the **Entry** column alongside the original AI-extracted **Value**, so both remain visible and the correction is what flows downstream into the return. Changing the underlying source document and re-running tax prep re-extracts the **Value**. ## How Forms relates to tax prep The Forms tab is a quality-check layer between source documents and the tax return. Preparers use it to confirm that Filed AI read each document correctly before the extracted values flow downstream into the return preparation workflow. The Forms tab and the AI Tax Prep workflow are part of the same product and operate on the same extracted data. See the AI Tax Prep section for the full workflow, including how values move from the Binder into the return and what state the forms must be in before they can be used. ## Navigating between forms The Forms tab covers multiple form screens corresponding to the different schedules and statements in the return. **Walkthrough: navigate between forms and verify sources** 1. Use the forms tree in the left panel to switch between form screens (for example, the W-2 under Income and Estimated payments under Payments). The search control at the top of the panel locates a specific form. 2. In the **References** column of any row, click the source reference (the source-document chip with the ↗ icon) to open that subdocument in the center viewer at the page where the value appears, so you can verify the extracted figure against the original. ![The Forms tab with the forms tree and per-row source references](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-forms/image1.webp) # Leadsheets ## What leadsheets are Leadsheets are the tax-review workpapers produced by Filed's AI Review product. They are the digital equivalent of traditional review leadsheets: structured workpapers that document what was reviewed and what conclusions were reached. Filed AI populates them automatically from the client's documents, and the review team works through them to complete the review engagement. Leadsheets appear in the Binder's Leads tab and are the primary workspace for the AI Review workflow. ## When the Leads tab appears The Leads tab is only visible when AI Review is enabled for this client. If the tab is not present in the Binder, AI Review has not been activated for this return. See the AI Review section for setup details. ## Row view - reviewing by leadsheet The default view in the Leads tab is the row view, which presents individual leadsheet rows in a spreadsheet-style grid. Each row corresponds to a specific item, figure, or assertion on the workpaper. From any row, the source document that supports that figure can be opened directly in the center viewer for verification. The Notes & flags feed in the right panel filters to show only activity relevant to the currently open leadsheet, so notes and flags placed during review are scoped to the sheet being worked. ## Issue view - reviewing by issue The issue view (accessed by switching to the issues sub-view) presents AI Review findings as cards grouped by the underlying issue they relate to rather than by sheet. This view is useful for scanning a specific type of problem across multiple sheets at once, where the row view is better suited for working through a single sheet methodically. ## Tracing a figure back to its source and prior year A leadsheet row is not just the current-year number - it carries the trail behind that number. Each row can show the prior-year value alongside the current figure, so a jump between years (a dividend total that doubled, a deduction that disappeared) is visible without opening the prior-year return separately. When a figure is an aggregation of several source amounts - for example, a dividends total built from several 1099-DIV forms - the row shows the components that were summed to reach it, not just the total. This makes it possible to check a rollup figure against its individual contributors instead of trusting the total on faith. From any row, the same reasoning connects to source: opening the source document from a row (see [Row view](#row-view---reviewing-by-leadsheet)) shows exactly which line on which document the AI used, at the level of an individual figure rather than the form as a whole. ## Deep-linking from AI Review AI Review can link directly into a specific leadsheet and a specific row in the Binder. Following such a link opens the Leads tab directly to the relevant sheet and highlights the relevant row. The row highlight clears when the user navigates away. This connection between AI Review issue cards and the underlying workpaper rows is how the review workflow surfaces detail-level evidence. ## Signing off on leadsheets Leadsheets support sign-off at two levels: an entire leadsheet can be signed off, or individual rows within a leadsheet can be signed off. Both use the same four-level sign-off model as document sign-off: Level 0 (AI implicit, applied automatically when there are no open AI issues), Level 1 (preparer), Level 2 (reviewer), and Level 3 (partner or admin). A leadsheet sign-off is a formal assertion that the workpaper has been reviewed at the signed level. Signing off at a higher level implies that lower-level review is complete. A sign-off on a leadsheet or row becomes stale if the leadsheet or row is modified after the sign-off was placed. The stale state is surfaced in the UI and the expected workflow is to address the change and sign off again. Sign-offs can be undone. See [Activity and Sign-off](/reference/products/binder/activity-and-sign-off) for the full sign-off model. ## Exporting leadsheets Leadsheets can be exported as Excel or CSV from the Binder download dialog. **Walkthrough: export leadsheets** 1. Open the Download dialog (Docs panel **⋯** menu → **Download workpaper**) and make sure **Leadsheets** is checked. Use the format selector next to it to choose between **Excel** and **CSV**. ![The Download dialog with the Leadsheets format selector showing Excel and CSV](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/leadsheet-export/image1.webp) 2. Click **Download** to generate the leadsheet export in the chosen format. # Template automation ## The idea Many firms already have their own standard templates for engagement work: a 1040 workbook, an AICPA-style checklist, a firm-specific lead sheet layout. Rather than replacing those with Filed's own formats, the goal is for Filed to complete a firm's existing template automatically, using the same document intelligence that powers Forms, Pre-Entry Notes, and leadsheets - so the deliverable a firm is already used to producing gets filled in without manual data entry. ## What this looks like today A firm's template is provided to Filed, and Filed populates it with the client's extracted and reviewed data rather than a preparer copying figures in by hand. The result is intended to be a completed version of the firm's own document - not a Filed-branded substitute - so nothing changes about what the firm files or delivers internally. ## Where to check current template automation availability Given this capability is still maturing, check with your Filed contact on: * Which template types are supported today (1040 workbook, AICPA checklist, lead sheet layouts, or others) * How to register or upload a firm's own template * Whether this is available self-serve or requires setup assistance ## Related * [Reading lead sheets](/reference/products/binder/leadsheets) - Filed's own generated leadsheet format, available today independent of any firm-specific template * [Downloading the Binder](/reference/products/binder#downloading-the-binder) - the existing PDF, Excel, and CSV export options that work today regardless of template automation status # Chat ## What Binder Chat is Binder Chat is an AI assistant scoped to the open client's Binder. It answers questions about that client's documents, surfaces what still needs review, and can take actions within the Binder on the reviewer's behalf. Its answers are grounded in the client's actual documents, with citations linking directly to the source. Binder Chat is distinct from the standalone client Chat view (the "Ask" view accessible from the client home screen). Binder Chat is embedded in the Binder's right panel and is aware of the full Binder context: which documents are present, what has been annotated, what is missing, and what the prior year looked like. Binder Chat is available in the web app. ## Opening Chat The Chat panel lives in the right side of the Binder. Clicking the Chat tab in the right panel opens it. The panel includes a header with controls to start a new conversation and to access prior conversation history. **Walkthrough: open and use Binder Chat** 1. Click the **Chat** tab in the Binder's right panel. The empty state shows a greeting and a set of **Suggestions** (starter prompts) such as "What still needs my review?", "Which documents are flagged?", and "What changed since last year?". ![The Binder Chat panel with starter prompt suggestions](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-chat/image1.webp) 2. Click a suggestion or type your own question in the message box and send it. When the answer draws on specific documents, the response includes citations; clicking a citation opens that subdocument in the center viewer at the relevant page. The message box also supports dictation, so a question can be spoken instead of typed while a document stays open in the center viewer. 3. Use the **+** button in the panel header to start a new conversation, and the **⋯** (more) control to access prior conversation history. Conversations are saved per client and the most recent one resumes automatically when you reopen Chat. ## What you can ask Binder Chat understands the full context of the client's Binder. Starter prompts offered when opening Chat include: * "What's in this binder?" - an overview of the documents present and how they are organized * "What still needs my review?" - documents or workpapers that are open, unflagged, or unsigned * "Which documents are flagged?" - a summary of open flags across the Binder * "Does the income tie to the return?" - an AI-driven reconciliation check against the documents * "What changed since last year?" - new, missing, or changed items compared to the prior year Questions can go beyond these starters. Chat can be asked to summarize a specific document, explain an observation, identify uncategorized items, or locate a figure across the Binder. Before opening individual source documents, it can help to ask a broad question first - such as "what's this client's tax position?" - to get an overview grounded in the client's income sources and estimated position. See [Prompting best practices](/reference/products/chat-and-analyst/prompting-best-practices#start-broad-then-go-deep) for more on this approach. ## Cited answers and navigating to sources When Binder Chat answers a question that draws from specific documents, it includes citations in its response. Clicking a citation opens the cited subdocument in the center viewer at the relevant page. This makes it quick to verify any claim Chat makes against the original source without leaving the Binder. ## Getting output in other formats Binder Chat is not limited to written answers. Asking for a table, CSV, or spreadsheet - for example, "give me a CSV of every W-2 and the wages reported on each" - returns the answer as a downloadable file rather than only prose. Use this when the answer is meant to be handed off or used outside of the conversation, not just read. ## Multiple conversations per client A client is not limited to a single ongoing conversation. Starting a new conversation with the **+** button keeps a fresh line of inquiry separate from one already in progress - useful when moving from a general question about the binder to working through a specific finding, without one thread's context bleeding into the other. Every conversation is retained; nothing is lost by starting a new one, and any prior conversation can be reopened from the **⋯** history control. ## Taking actions from Chat Binder Chat is not read-only. It can take actions within the Binder: adding a note or flag, placing a checkmark, signing off a document, or surfacing related marks. When Chat proposes an action, the action is shown as a proposal for the reviewer to approve before it executes. Chat does not modify the Binder without a confirmation step. ## Conversation persistence and history Conversations in Binder Chat are saved per client. Reopening Chat for a client resumes the most recent conversation automatically. Prior conversations are accessible from the conversation history control in the panel header, and a new conversation can be started at any time without losing the history. ## Chat vs. @agent in threads Binder Chat is a real-time conversational interface covering the whole Binder. It is the right tool for broad questions about the client's documents and for taking actions across the Binder. The @agent mention in an annotation thread is a separate mechanism. Tagging @agent in a reply to a note, flag, or other annotation mark triggers a background AI response posted into that specific thread. This is useful when a question is attached to a specific location on a document and the response should live alongside the annotation rather than in a separate chat panel. See [Activity and Sign-off](/reference/products/binder/activity-and-sign-off) for the @agent thread flow. # Activity & sign-off ## The Notes & flags feed The Notes & flags tab in the right panel is a running log of activity on the workpaper: notes, flags, tickmarks, highlights, textboxes, stamps, calculators, cross-references, and Filed AI observations and alerts. Entries are attributed to the team member or AI system that created them. Sign-offs are deliberately kept out of this feed (they would be too noisy); they are tracked on the document or leadsheet itself, shown as the sign-off control and stamp. The feed is the single source of truth for what has been annotated, flagged, and noted, and by whom. ## Filtering the Notes & flags feed The feed can be filtered by annotation type to narrow the view. Available filters include: Mentions, This file, Exclude deleted, and individual types including Observations, Checkmarks, Flags, Highlights, Text boxes, Stamps, Calculators, Cross-refs, Info, and AI alerts. Selecting a subdocument in the left panel automatically narrows the feed to show only activity on that document. This makes it straightforward to see the complete annotation history for a specific subdocument while reviewing it. ## Annotation threads and replies Any item in the Notes & flags feed can become a conversation thread. Replying to a feed item opens a thread associated with that annotation. Multiple team members can reply to the same thread. Threads persist alongside the annotation they belong to. Threads are the primary way team members discuss specific findings without leaving the Binder. ## @mentions and teammate notifications A team member can be @mentioned in any thread reply by typing their name after the @ symbol. The mentioned person receives a notification and can open the thread directly from it. This is useful for escalating a question to a specific reviewer or asking someone to look at a particular document location without context switching out of the Binder. ## Asking @agent in a thread @agent can be mentioned in a thread reply to trigger an AI response posted back into that thread. The agent answers using the full Binder and client document context. Its response is posted as a background task, appearing in the thread on the next refresh rather than in real time. When the agent proposes an action (such as adding a flag, placing a checkmark, signing off a document, or hiding an annotation), the proposal is surfaced as an approval card. The action does not execute until a team member approves it. Responses posted by @agent are public and visible to all workspace members with access to this Binder. The agent's display name is configurable per workspace. ## Sign-off levels The Binder uses a four-level sign-off model. Level 0 is an AI-implicit sign-off that is applied automatically when a subdocument has no open AI issues; it is not a human action. Levels 1 through 3 are human sign-offs: | Level | Role | | ----- | ---------------- | | L1 | Preparer | | L2 | Reviewer | | L3 | Partner or admin | A user's available sign-off level is determined by their workspace role. Sign-offs at each level are sequential: an L2 sign-off implies L1 work is complete. An L3 sign-off implies both L1 and L2 are complete. Sign-offs can be undone by the reviewer who placed them. ## Signing off a document A subdocument is signed off from the Docs tab while the document is open in the center viewer. The sign-off is recorded on the document itself, showing the level, the reviewer, and the timestamp. Sign-offs and flags are independent signals: a reviewer can sign off while leaving flags open for someone else to act on. **Walkthrough: sign off a subdocument** 1. Open a subdocument in the center viewer, then click the sign-off control in the top-right corner of the document. The document is signed off at the level allowed by your role, a sign-off indicator appears on the document, and the document (and its category) show as signed in the Docs tree. ![A document signed off, with the sign-off indicator and the Docs tree marked](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-signoff/image1.webp) 2. To undo, click the sign-off indicator again. The document returns to an unsigned state. ![The document returned to an unsigned state after undo](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-signoff/image2.webp) ## Signing off a leadsheet or row Leadsheets support sign-off at two granularities: an entire leadsheet or an individual row. The same L1 / L2 / L3 chain applies. The sign-off indicators appear on both the row and the leadsheet header. ## What invalidates a sign-off A sign-off becomes stale when the signed document or leadsheet row is modified after the sign-off was placed. The stale state is surfaced in the UI with the message: "Your sign-off is stale - Modified after sign-off. Sign off again as L{level}." The stale status is set automatically by the system when a modification is detected. The expected workflow is to address the change that caused the stale state and then sign off again. A stale sign-off counts as unsigned for the purposes of review tracking. ## Undoing a sign-off A sign-off can be undone by the reviewer who placed it. Undoing returns the document or row to an unsigned state. **Walkthrough: undo a sign-off** With a signed-off document open, click the sign-off indicator in the top-right corner again to undo it. The indicator clears and the document (and its category in the Docs tree) return to an unsigned state. ![The document returned to an unsigned state after undoing the sign-off](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-signoff/image2.webp) # AI Review ## What AI Review does AI Review reads a draft tax return and cross-checks it against the source documents already in the client's binder. It surfaces discrepancies, missing items, and potential errors as structured findings called leadsheets, which appear in the binder's Leads tab. The AI handles the cross-referencing work; the preparer reviews each finding and decides how to act on it. ## What AI Review checks AI Review compares values on the draft return against source documents in the binder, including W-2s, 1099s, K-1s, payroll summaries, prior-year returns, trial balances, and other supporting materials. It identifies: * Value mismatches between the draft and source evidence * Missing items flagged in the binder * Arithmetic inconsistencies across forms * Form-level anomalies Most findings are anchored to a specific form and line on the return. Filing-level findings, such as a required form that is missing, reference the form only. Supported return types: * Form 1040 (individuals) * Form 1120-S (S corporations) * Form 1065 (partnerships) * Form 1120 (C corporations) * Form 1041 (estates and trusts) * Form 990 (tax-exempt organizations) AI Review automatically scopes its checks to the forms applicable to the client's configured return type. ### Issue severity levels Each finding carries one of four severity levels: **Critical** - The finding indicates a significant discrepancy or missing item that should be resolved before the return is filed. **High** - Strong evidence of a mismatch or inconsistency between the draft and source documents. Warrants immediate attention. **Medium** - A potential issue that warrants review. The evidence is present but the discrepancy may be explainable. **Low** - An informational or low-confidence finding. May reflect a minor inconsistency or an item to verify, but is less likely to require a correction. Severity is assigned by the AI based on the evidence in the binder. The preparer makes the final judgment on each finding. ## Before you run AI Review AI Review uses whatever source documents are in the binder at the time of the run, so a more complete binder produces better findings. Before starting, upload the client's W-2s, 1099s, K-1s, and other supporting documents to the binder. The more evidence available, the more precisely AI Review can cross-check the draft return. ## Running AI Review {% embed url="" %} **Walkthrough: run AI Review** 1. Open **AI Review** from the client hub. On **Step 1 of 2 (Upload the draft 1040 return)**, add the draft return PDF via the drop zone or **Browse files**, then click **Next: Confirm source documents**. ![AI Review step 1: upload the draft return](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/ai-review/image1.webp) 2. On **Step 2 of 2 (Confirm source documents)**, review the binder preview - the source documents grouped by category and the missing-documents count - to make sure the binder looks complete. Use **Go to Binder** to add anything missing, then click **Start review**. ![AI Review step 2: confirm the binder source documents](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/ai-review/image2.webp) 3. AI Review runs and shows an in-progress loader ("Running AI Review") while it generates leadsheets. This usually takes a few minutes and updates automatically when ready, transitioning to the completed summary page (see [Reading the results](#reading-the-results)). ![The AI Review in-progress loader](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/ai-review/image3.webp) ## Reading the results When the review completes, the summary page shows: * The client name, tax year, and total number of findings * A four-tile breakdown with the count of Critical, High, Medium, and Low findings * A written narrative summarizing the review * A section listing findings grouped by form, with per-form counts The "Open leadsheets" button takes you to the Leads tab, where you can work through each finding in detail. ## Working through findings in the Leads tab ## Re-running AI Review You can re-run AI Review at any time, for example after adding new source documents to the binder or when a revised draft is ready. Each run produces a fresh, complete set of leadsheets and becomes the active result. Prior runs remain accessible by selecting them in the sidebar; they are not deleted, but binder flags update to reflect the latest run. ## In this section * [**Understanding flags**](/reference/products/ai-review/understanding-flags) - Where a finding's rule comes from, how to turn a check on or off, and a worked example of what AI Review catches that tax software won't. * [**Managing review protocols**](/reference/products/ai-review/managing-review-protocols) - Built-in and firm-authored checks, and how admins enable or disable them. * [**Prior-year comparison**](/reference/products/ai-review/prior-year-comparison) - How current-year values get compared against last year's return. * [**Sign-off levels**](/reference/products/ai-review/sign-off-levels) - What L0-L3 mean and who signs at each level. * [**Focus mode**](/reference/products/ai-review/focus-mode) - Keyboard-driven review of fields one at a time, with source evidence expanded alongside. * [**Re-review workflow**](/reference/products/ai-review/re-review-workflow) - The fix-in-tax-software, re-export, re-review loop. * [**Downloading work papers**](/reference/products/ai-review/downloading-work-papers) - Exporting the signed-off leadsheets as the final CSV or Excel work paper. * **Frequently asked questions** - Answers to common questions about what AI Review checks, supported return types, timing, severity levels, and how findings relate to the Leads tab. Planned future pages: Signing off findings, Supported return types. # Understanding flags ## Where a flag's rule comes from Every finding AI Review surfaces traces back to a specific check, not a generic pass over the return. These checks are the same protocol mechanism documented in the [Playbook](/reference/playbook/creating-protocols): firm-wide and personal rules that can be reviewed, edited in plain language, and turned on or off. AI Review-scoped protocols are what decide which checks run on a given review. This means a flag is never a black box. If a finding looks wrong or unexpected, the protocol behind it can be opened in the Playbook to see exactly what it checks for and adjusted or disabled if it does not fit the firm's judgment. ## Turning a check on or off Protocols scoped to the AI Review task type can be disabled from the Playbook without affecting AI Tax Prep, Chat, or other task types - see [Task types](/reference/playbook/creating-protocols#choosing-the-right-task-type). Disabling a protocol means it is skipped on the next run; it does not retroactively remove findings already on an existing set of leadsheets. Re-run AI Review after disabling a check to produce a clean set of leadsheets without it. ## Example: wages vs. Medicare wages One of AI Review's built-in checks compares Box 1 (wages) against Box 5 (Medicare wages) on a W-2. These two boxes are usually close but not identical - pre-tax deductions like a 401(k) contribution reduce Box 1 but not Box 5 - so the check looks for a difference that falls outside the normal range for those deductions rather than flagging any difference at all. This is useful because tax software does not perform this cross-check on its own: it accepts whatever values are entered in each box independently. A transposed digit or a data-entry error on either box will pass through undetected by the software, but AI Review catches it because it is comparing the return against the source W-2 evidence. The same evidence-based approach is why AI Review can catch situations involving a corrected W-2: if a corrected form supersedes an original, comparing the return only against the most recent version - rather than trusting whichever copy the return happens to be entered from - is what surfaces a mismatch. If a finding references box amounts that don't match your expectation, check whether more than one version of that document (original and corrected) exists in the binder. ## Reading a flag card Each finding card in the Leads tab shows: * The severity level (Critical, High, Medium, or Low) - see [Issue severity levels](/reference/products/ai-review#issue-severity-levels) * The form and line the finding is anchored to * A description of the discrepancy * The evidence the AI used to reach that conclusion * A comment thread for discussing the finding with colleagues See [Working through findings in the Leads tab](/reference/products/ai-review#working-through-findings-in-the-leads-tab) for the full row and issue views. ## When a flag doesn't apply Not every flag indicates an error. Severity reflects the AI's confidence and the significance of the pattern it found, not a final verdict - see [What do the severity levels mean?](/reference/products/ai-review/frequently-asked-questions#what-do-the-severity-levels-mean). Use the comment thread to record why a finding was determined to be a non-issue, then sign off the row to clear it. See [Signing off on leadsheets](/reference/products/binder/leadsheets#signing-off-on-leadsheets). # Managing review protocols ## AI Review's checks are protocols Every check AI Review runs - the wages-vs-Medicare-wages comparison, missing-item detection, arithmetic checks, and more - is a protocol in the AI Review task type's Playbook, the same protocol mechanism used across Filed. See [Understanding flags](/reference/products/ai-review/understanding-flags#where-a-flags-rule-comes-from) for how a specific flag traces back to the protocol that produced it, and [Creating protocols](/reference/playbook/creating-protocols) for how protocols work in general. ## Built-in review protocols Filed ships a set of curated, built-in protocols scoped to AI Review, organized by return type (1040, 1120-S, 1065, 1120, 1041, 990). These are active by default for every preparer at the firm and can only be turned off or overridden by an admin - preparers cannot edit them directly. See [Built-in (curated) protocols](/reference/playbook/yours-vs-firms-protocols#built-in-curated-protocols). ## Adding your own review protocol Any preparer can propose a personal AI Review protocol through Chat, the same way any other protocol is authored - see [Step 1 - express your intent in Chat](/reference/playbook/creating-protocols#step-1---express-your-intent-in-chat). To bring a personal check to the whole firm, use **Share with firm** and have an admin approve it, following the same promotion flow used for any task type - see [Promoting a personal protocol to the firm](/reference/playbook/yours-vs-firms-protocols#promoting-a-personal-protocol-to-the-firm). ## Turning a check off for one review only To skip a check for a single run without disabling it for future reviews, use the per-run opt-out described in [Turning protocols on or off for a specific prep](/reference/playbook/toggling-protocols-per-run). ## Where to see which protocols shaped a specific set of leadsheets Each finding on a leadsheet traces back to the protocol behind it - see [Where a flag's rule comes from](/reference/products/ai-review/understanding-flags#where-a-flags-rule-comes-from). To check the full set of protocols active for the AI Review task type generally, open **Playbook → AI Review** and review both the **Yours** and **Firm's** sections. ## Turning a review check off firm-wide An admin can disable a curated AI Review protocol, or override it with a firm-authored replacement, from the **Firm's** section of the AI Review Playbook tab. Disabling suspends the check without deleting it; it can be re-enabled at any time. See [Admin governance](/reference/playbook/yours-vs-firms-protocols#admin-governance). # Prior-year comparison ## The prior year as a baseline Filed uses the client's prior-year return as a baseline in two related places: during AI Tax Prep's reconciliation step, and on AI Review's leadsheets. Both draw from the same underlying idea - a current-year value is easier to judge with the prior year sitting right next to it - but they serve different moments in the workflow. ## During AI Tax Prep: reconciliation When a prior-year tax-software backup is available, AI Tax Prep's reconciliation phase compares newly extracted data against it to resolve sources of truth and flag conflicts it can't resolve automatically. This is what powers the missing-documents checklist (a document type present last year but absent this year gets flagged - see [Missing documents](/reference/products/binder/missing-documents-tracking)) and feeds some of the Observations severity flags described in [Pre-Entry Notes Notifications](/reference/products/ai-tax-prep/pre-entry-notes-notifications). See [How Filed processes the documents](/reference/products/ai-tax-prep/workflow-overview#how-filed-processes-the-documents). ## On leadsheets: the prior-year value alongside the current one Once a return reaches AI Review, leadsheet rows can show the prior-year value directly alongside the current figure, so a meaningful year-over-year change (a dividend total that doubled, a deduction that disappeared entirely) is visible without pulling up last year's return separately. When a current-year figure is itself a rollup of several source documents, the row also shows the individual components that were summed to reach it - so an unexpected prior-year jump can be traced down to which specific component changed. See [Tracing a figure back to its source and prior year](/reference/products/binder/leadsheets#tracing-a-figure-back-to-its-source-and-prior-year). ## Why this catches things a straight document-to-return check would miss A discrepancy check that only looks at the current year's documents can miss things that are only obvious in context - an amount that's correct on its own but wildly different from every prior year, for instance. Comparing against the prior year surfaces exactly this kind of change for a human to judge, without requiring the reviewer to remember or look up what last year's return said. ## Where to look * Before data entry, in AI Tax Prep: [Pre-Entry Notes](/reference/products/ai-tax-prep/pre-entry-notes-tab) and the missing-documents checklist. * During review, in AI Review: leadsheet rows in the [Leads tab](/reference/products/binder/leadsheets#tracing-a-figure-back-to-its-source-and-prior-year). # Sign-off levels ## The short version Filed uses one sign-off model everywhere in the Binder, including on AI Review's leadsheets: four levels, L0 through L3, where each higher level implies the ones below it are done. | Level | Who | How it's applied | | ----- | ---------------- | ---------------------------------------------------------------------------------------- | | L0 | AI (implicit) | Applied automatically when there are no open AI issues on the item - not a human action. | | L1 | Preparer | First human sign-off. | | L2 | Reviewer | Implies L1 is complete. | | L3 | Partner or admin | Implies L1 and L2 are complete. | This is the same model documented in full in [Activity and sign-off](/reference/products/binder/activity-and-sign-off#sign-off-levels) - read that page for how sign-offs are placed, undone, and what makes a sign-off go stale. ## Sign-off on leadsheets specifically Leadsheets support sign-off at two granularities: an individual row, or the entire leadsheet. Both use the same L1-L3 human levels (L0 remains implicit - it reflects the AI having no open issue on that item, not a person signing off). Signing off a whole leadsheet at, say, L2 asserts that both the L1 preparer pass and the L2 reviewer pass are complete for every row on it. See [Signing off on leadsheets](/reference/products/binder/leadsheets#signing-off-on-leadsheets). ## Who can sign at which level A preparer's available sign-off level is determined by their workspace role - a preparer-level user can place an L1 sign-off but not an L2 or L3. This applies uniformly across documents and leadsheets. ## A stale sign-off counts as unsigned If a signed row or leadsheet is modified afterward, the sign-off goes stale and the UI prompts for a fresh sign-off at the same level. A stale sign-off is treated as unsigned for review-tracking purposes until it's redone. See [What invalidates a sign-off](/reference/products/binder/activity-and-sign-off#what-invalidates-a-sign-off). # Focus mode ## What Focus mode is Focus mode is a distraction-free way to work through entered or flagged fields one at a time without leaving the screen to open the source document separately. It pairs the field currently under review with its source evidence side by side, so tying an entered value back to the document it came from does not require switching tabs or scrolling to find the right page. ## Opening Focus mode ## Keyboard navigation Focus mode is built around two keyboard shortcuts so a reviewer can move through every field without reaching for the mouse: | Key | Action | | --- | -------------------------- | | N | Move to the next field | | P | Move to the previous field | ## Expanded source view While a field is active in Focus mode, its source document expands so the relevant area of the page is visible without leaving the field. The section of the source that the AI used to extract the value is highlighted, making it fast to confirm - or challenge - the AI's reasoning for a specific entry. ## Tying the entered value back to source Focus mode shows three things for the active field at once: the source document evidence, the value Filed extracted, and the value that ended up in tax software. This is the same underlying comparison described in [Verifying entries](/reference/products/ai-tax-prep/verifying-entries); Focus mode is a faster way to work through many fields in sequence rather than opening each one individually from the Forms tab. ## When to use Focus mode Focus mode is best suited to working through a batch of flagged fields end to end - for example, clearing every Flagged field after a data-entry run, or moving through an AI Review finding list form by form. For a single one-off lookup, opening the form directly from the [Forms tab](/reference/products/ai-tax-prep/forms-tab) or a leadsheet row is equally fine. # Re-review workflow ## The loop: fix, re-export, re-review AI Review is designed to be run more than once on the same client. The typical cycle is: 1. Run AI Review on a draft return and work through the findings in the Leads tab. 2. Correct the issues that need correcting directly in tax software. 3. Produce an updated draft return PDF from tax software. 4. Bring the updated PDF back into AI Review to start a fresh run. 5. Repeat until the findings on the latest run are clear, signed off, or explained. Each run is independent and produces a complete, fresh set of leadsheets rather than patching the previous run. See [Re-running AI Review](/reference/products/ai-review#re-running-ai-review) for what happens to prior runs when a new one starts. ## Getting the updated return back into Filed There are two ways to bring a revised draft back into AI Review: * **Upload it directly.** Start a new run from the client's AI Review page and drop the updated PDF into Step 1, the same flow used for the first run. See [Running AI Review](/reference/products/ai-review#running-ai-review). * **Print it in with Filed Printer.** If [Filed Printer](/reference/plugins/filed-printer) is set up, printing the revised return from tax software sends it straight into the client's workspace - Filed matches it to the client automatically from the SSN on a 1040. The printed file lands under the client's AI Review, where **Create Review** starts the run. Either path produces the same result: a new AI Review run compared against the current state of the binder. ## The final leadsheet set is the work paper Once the findings on the latest run are cleared, sign off the leadsheets - by row or by whole sheet, using the same [sign-off levels](/reference/products/ai-review/sign-off-levels) as the rest of the Binder - and export them. See [Downloading signed-off lead sheets as work papers](/reference/products/ai-review/downloading-work-papers) for the full walkthrough; the exported leadsheets are the signed-off work paper for the engagement. ## Sign-off carries across runs A leadsheet sign-off is scoped to the run it was placed on. Because a new run produces a fresh set of leadsheets, previously signed-off findings are not automatically carried forward onto the new run - each new run's leadsheets reflect the current state of the return and need their own sign-off pass. # Downloading work papers ## The deliverable is the exported leadsheet set Once a review's findings are cleared and signed off, the leadsheets themselves - not a separate report - are the work paper for the engagement. Exporting them produces a record of what was checked, what was found, and who signed off on each item, in a format that can be filed, archived, or handed to whoever needs it outside of Filed. ## Sign off before exporting Export what you actually want to stand as the completed record: sign off each row or the whole leadsheet first, using the L1-L3 model described in [Sign-off levels](/reference/products/ai-review/sign-off-levels). See [Signing off on leadsheets](/reference/products/binder/leadsheets#signing-off-on-leadsheets) for the walkthrough. ## Exporting **Walkthrough: export the signed-off leadsheets** 1. Open the Download dialog from the Docs panel's **⋯** menu and choose **Download workpaper**. 2. Make sure **Leadsheets** is checked, and use the format selector to choose **Excel** or **CSV**. 3. Click **Download** to generate the export. See [Exporting leadsheets](/reference/products/binder/leadsheets#exporting-leadsheets) for the full walkthrough and screenshot. ## Choosing Excel vs. CSV Both formats contain the same underlying leadsheet data. Excel is generally easier to review or annotate further outside Filed; CSV is a better fit for feeding the data into another system or spreadsheet-based process. Pick whichever the downstream use calls for. ## This fits into the broader re-review loop Exporting is usually the last step after a round of fixes and a fresh review - see [Re-review workflow](/reference/products/ai-review/re-review-workflow) for the full fix-in-tax-software, re-export, re-review cycle this export typically sits at the end of. # FAQ ## What does AI Review actually check? AI Review cross-checks the values on a draft return against the source documents in the binder: W-2s, 1099s, K-1s, payroll summaries, prior-year returns, trial balances, and similar materials. It catches value mismatches between what the draft shows and what the evidence supports, missing items flagged in the binder, and form-level inconsistencies. AI Review checks the return against the evidence in the binder; it does not evaluate compliance rules in isolation. ## Which return types does AI Review support? AI Review supports: Form 1040 (individuals), Form 1120-S (S corporations), Form 1065 (partnerships), Form 1120 (C corporations), Form 1041 (estates and trusts), and Form 990 (tax-exempt organizations). Checks are scoped automatically to the forms applicable to the client's configured return type. ## What file formats can I upload for the draft return? The draft return must be a PDF. The uploader accepts one or more PDF files. Binder source documents can be PDFs, images, Excel files, or Word documents, but the draft return specifically must be in PDF format. ## How long does AI Review take? AI Review typically completes in a few minutes. The page updates automatically when the review is ready; no manual refresh is needed. Processing time varies with the number and size of source documents in the binder and the complexity of the return. ## What if the binder is missing documents? The binder preview screen on step 2 of the initiation flow shows missing document flags for the client's configured checklist. You can open the binder in a new tab from that screen to upload missing documents without losing your place in the review flow. Running AI Review with an incomplete binder is allowed, but findings are limited to the evidence that is present. ## What do the severity levels mean? * **Critical** - A finding that should be resolved before the return is filed. * **High** - Strong evidence of a discrepancy between the draft and source documents. * **Medium** - A potential issue that warrants review; the evidence is present but the discrepancy may be explainable. * **Low** - An informational or low-confidence finding that is less likely to require a correction. Severity is assigned by the AI and should be treated as a starting point for the reviewer's judgment, not a final determination. ## Can I run AI Review more than once? Yes. You can start a new run at any time using the "+" button in the AI Review sidebar. Common reasons to re-run: new source documents were added to the binder, or a revised draft return is available. ## What happens to previous results when I re-run? Each run is independent and remains visible in the run history sidebar. The most recent run becomes the active set of leadsheets and the active set of binder flags. Earlier runs remain accessible by selecting them in the sidebar; they are not deleted. ## A finding looks wrong - what should I do? Use the comment thread on the finding card to note the discrepancy and discuss it with colleagues. If the finding is a false positive, document that reasoning in the comment thread. A reviewer can sign off the row to mark it cleared even if the underlying item was determined to be a non-issue. ## How do AI Review results relate to the Leads tab in the binder? AI Review writes its findings directly to the Leads tab as leadsheets, one per form on the return. The Leads tab is the working surface for reviewing and clearing findings; AI Review is what creates them. Any binder user with access to the client can see and work through the leadsheets once the review completes. ## Does AI Review replace the manual review process? No. AI Review is a first-pass assistant that handles the cross-referencing and evidence-gathering steps that would otherwise be manual. The preparer still reviews every finding, exercises professional judgment, and signs off on each item. AI Review accelerates the process; it does not replace the CPA's role. # AI Tax Planning ## What AI Tax Planning does AI Tax Planning reads a client's finalized tax return and produces forward-looking tax strategies with estimated savings. Where AI Review finds errors in a draft, AI Tax Planning looks ahead and surfaces opportunities to present during a planning conversation. * Each strategy cites the specific figures on the return that make it applicable. * Savings estimates are calculated from arithmetic on the return's actual numbers, not guessed. * Strategies are grouped by planning domain and sorted by estimated savings. * The plan also includes a written narrative overview and a built-in advisor chat aware of the strategies and underlying return data. ## What kinds of strategies it surfaces The planning domains vary by entity type. The AI surfaces only strategies the return's facts support, and stays silent on domains the data does not support. **Individuals (Form 1040):** retirement contributions and Roth conversions; investment gain and loss timing; equity compensation; charitable giving vehicles; real estate depreciation and deferral; business-owner deductions; health and medical accounts; education funding; income timing and bracket management; credits and incentives; family and dependent planning; Social Security claiming strategy; estate and gift considerations. **Business entities (Form 1120-S, 1065, 1120, 1041):** reasonable compensation; the QBI and pass-through deduction; basis and loss limitations; distributions management; retirement plan design; SALT workarounds; exit and succession planning; entity structure; R\&D credits. **Tax-exempt organizations (Form 990):** unrelated business income considerations and related compliance planning. ## Before you run AI Tax Planning * AI Tax Planning analyzes a finalized return, not a draft. Fully prepare the return before triggering a plan. * It does not run automatically after AI Review; trigger it separately from the client's page. * The richer the return (more schedules, K-1s, and supporting forms), the more domains the advisor can evaluate. ## Running AI Tax Planning **Walkthrough: run AI Tax Planning** 1. Open **AI Tax Planning** from the client hub. On the single-step **Upload the final 1040 return** screen, add the finalized return PDF via the drop zone or **Browse files**, then click **Start tax planning**. ![AI Tax Planning: upload the finalized return](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/ai-tax-planning/image1.webp) 2. AI Tax Planning analyzes the return and shows an in-progress loader ("Building your tax plan") while it finds planning strategies. This usually takes a few minutes and updates automatically when ready. ![The AI Tax Planning in-progress loader](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/ai-tax-planning/image2.webp) 3. When the run completes, the plan appears with the savings band and the strategy cards sorted by estimated savings (see [Reading the tax plan](#reading-the-tax-plan)). ## Reading the tax plan When the plan is ready, the page shows the client name, tax year, and strategy count, followed by: * **Savings band** - estimated savings broken down by horizon (This year, Multi-year, Lifetime, Event-driven), so the total opportunity is visible without combining figures from different time frames. * **Global narrative** - a summary of the key opportunities. * **Strategy cards** - sorted by estimated savings. Savings figures are computed from arithmetic on the return's actual numbers. The calculation behind each figure is verifiable and shown on the card in a dedicated Calculations section. ### Understanding savings horizons Each strategy is tagged with one of four savings horizons: * **This year** - A one-time or current-year benefit. For example, an HSA contribution made before the filing deadline. * **Multi-year** - A benefit that recurs over several years. For example, adjusting withholding or accelerating depreciation on a recurring asset. * **Lifetime** - A benefit that applies indefinitely. For example, optimizing Social Security claiming age or restructuring required minimum distributions. * **Event-driven** - A benefit triggered by a future transaction, such as a business sale, property disposition, or stock option exercise. Savings figures are never summed across horizons. A lifetime benefit and a current-year benefit represent different types of value and cannot be meaningfully added together. ## Working through strategy cards Each card shows the strategy title, estimated savings figure, savings horizon badge, and planning domain badge. If a dollar amount cannot be computed from the return, the savings field shows a dash with a tooltip explaining why. Expanding a card reveals: * **Applicability** - The specific facts from the return that make this strategy relevant to this client. * **Implementation plan** - An ordered list of steps to act on the strategy. * **Document references** - Source documents cited as evidence. Clicking a reference opens that document in the binder. * **Calculations** - The arithmetic behind the savings figure, shown as a verifiable formula. Appears only when a dollar estimate is present. * **Assumptions** - Any conditions or caveats the estimate depends on. ### Selecting and dismissing strategies Each strategy is in one of three states: * **Proposed** (default) - No action has been taken yet. * **Selected** - The firm intends to pursue this strategy with the client. * **Dismissed** - The strategy is not applicable or not being pursued for this client. Use the Select and Dismiss buttons to record the firm's decision; a dismissed strategy can be restored at any time. Selections and dismissals persist across re-runs by domain and strategy identity, so a previously selected or dismissed strategy retains its status when a new plan is generated. ## Using the advisor chat The plan includes a built-in advisor chat that knows the client's plan, the full set of strategies, and the underlying return data. Use it to ask follow-up questions, request client-facing summaries, explore edge cases, probe a strategy's assumptions, or ask how strategies interact. ## Re-running AI Tax Planning Re-run when a revised or amended return becomes available, or when planning for a new tax year. Each run is stored in the sidebar history. Selections and dismissals carry forward by domain and strategy identity, preserving the firm's working decisions. ## Which return types are supported AI Tax Planning supports: * **Form 1040** - individuals * **Form 1120-S** - S corporations * **Form 1065** - partnerships * **Form 1120** - C corporations * **Form 1041** - trusts and estates * **Form 990** - tax-exempt organizations The planning domains and strategy vocabulary differ by entity type; the AI selects the appropriate domain set automatically based on the client's configured return type. ## Pages to add later Planned future pages in this section: * **Understanding strategies** - Strategy card anatomy, savings calculations, and applicability evidence in depth. * **Presenting the plan with clients** - Workflow for using the plan during a client meeting. * **Planning habits** - How workspace and user-level planning overlays customize strategy generation. * **Planning by return type** - Domain coverage reference per entity type. # Chat & Analyst ## What is conversational AI in Filed? Filed embeds an AI assistant in multiple places across the product. All surfaces share the same underlying engine but differ in scope: per-client Chat is bounded to one client's documents and return data, while the firm-wide Analyst spans the entire workspace. Answers are grounded in real data from your binder documents, return outputs, and your firm's book of business, not generic knowledge. ## The three surfaces at a glance | Surface | Where to find it | Scope | Best for | | --------------------- | -------------------------- | --------------------------------- | -------------------------------------------------------------------- | | Per-client Chat | Client hub, Chat task card | One client's documents and return | Questions about a single client's tax position, documents, or return | | Firm-wide Analyst | Left navigation | Entire workspace | Cross-client pipeline questions, aggregate queries, tax research | | Home "Ask a question" | Home page | Entire workspace | Quick entry point; opens a new Analyst thread automatically | ## Per-client Chat Per-client Chat appears as a task card on a client's hub once binder creation is complete. The assistant is scoped entirely to that client: it can read the binder documents, the prepared return, the tax position summary, review findings, and client notes. It cannot see any other client's data. See [Per-client Chat](/reference/products/chat-and-analyst/client-chat) for full details. ## Firm-wide Analyst The Analyst is accessible from the left navigation and spans the entire workspace. It can answer questions that cross client boundaries, such as which clients are missing documents, who is likely to owe, and which returns are ready to file. It also supports general tax research using live web search. The Analyst maintains a persistent thread history. See [Analyst](/reference/products/chat-and-analyst/analyst) for full details. ## Home "Ask a question" box The Home page includes a quick-entry box for asking a question. Submitting a message there navigates automatically to the Analyst and opens a new thread. Threads started from the Home box live in the Analyst's thread history; there is no separate Home conversation history. ## Choosing the right surface **"I have a question about one specific client"** - Use per-client Chat. The assistant can cite binder documents and drill into the return. **"I want to see which clients are missing docs, ready to file, or likely to owe"** - Use the Analyst. It queries your full book of business. **"I want to look up a current tax rate, threshold, or IRS rule"** - Use the Analyst. It fetches live data from the web and cites its sources. **"I'm on the Home page and have a quick question"** - Type it in the Home box. You will land in the Analyst with a new thread. ## In this section * **Per-client Chat** - Ask questions grounded in one client's documents and return data. * **Firm-wide Analyst** - Cross-client queries, pipeline overviews, and tax research. * [**Chat features**](/reference/products/chat-and-analyst/chat-features) - Dictate, source citations, flags and notes that persist into the binder, and alternate output formats. * [**Prompting best practices**](/reference/products/chat-and-analyst/prompting-best-practices) - Getting better answers, using dictation, requesting CSV or spreadsheet output, and choosing between Chat and Analyst. # Client chat ## What is per-client Chat? Per-client Chat is a conversational assistant on the client hub, scoped entirely to one client. It can read every document in the client's binder, the prepared return, the tax position summary, data-entry notes, and review findings. It cannot see any other client's data in the workspace. Once the binder is processed, Chat is available any time you need to ask a question about that client. ## Before you start: binder readiness Chat becomes active only after the client's binder has finished processing (binder creation is complete). While the binder is still being created, the Chat task card shows a loading state indicating that setup is in progress. If binder creation failed, a retry option is available. Document quality affects answer quality: a more complete binder with clearly readable source documents produces more precise answers. ## Opening Chat for a client **Walkthrough: opening Chat for a client** 1. On the client hub, open the **Chat** task card (available once binder creation is complete). The chat interface loads scoped to that client, with the client shown as a chip in the message box and a set of **Suggestions** (starter prompt chips) below it. 2. Type your own question or click a suggested prompt to begin. Use the **+** button at the top of the left panel to start a new conversation, and the thread list below the search box to return to and resume a prior conversation. ![The per-client Chat interface on load, showing the conversation sidebar, the client-scoped message box, and the starter prompt suggestions](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/client-chat-opening/image1.webp) ## What the assistant knows about this client The assistant has access to the following for the selected client: * Tax position summary: taxpayer profile, household composition, dependents, income sources, and estimated tax position. * The prepared draft return for the current year. * Tax-prep and tax-review run outputs, including the cover memo and review findings. * Data-entry and extraction notes, and flagged binder items. * Binder checklist: missing documents, data gaps, and conflicts. * All processed source documents and their extracted content. * Client-specific saved memories from prior sessions. The assistant does not pull data from any other client in the workspace. ## Questions you can ask The chat interface shows a set of suggested prompts drawn from the full prompt pool. You can use these as starting points or ask any free-form question about the client. Sample prompts from the pool: * "What documents is this client missing?" * "Any big changes from last year?" * "Do they owe or are they getting a refund?" * "Anything that could trigger an audit?" * "Did they make estimated tax payments?" * "What's their effective tax rate?" * "Any carried losses or credits to apply?" * "Did they have any major life events?" * "How's their retirement contribution look?" * "Any K-1s or pass-through income?" These cover common starting points across missing documents, return summary, year-over-year changes, risk items, specific data points, and life events. Free-form questions beyond these starters work equally well. ## How the assistant cites its answers When an answer draws from a specific document in the binder, the response includes a citation. Tapping the citation opens the referenced document or page in the binder's source viewer. Citations let you verify the source of an answer quickly without leaving the conversation. ## Navigating from Chat The assistant can navigate you directly to the current client's Tax Prep, Review, Binder, Planning, and Chat pages, plus the workspace Skills settings page. For example, asking "Go to their review findings" will open the Review page for that client. The assistant cannot navigate to the clients list, switch to a different client, or open the workspace Analyst. ## What the assistant can and cannot do **Can do:** * Answer questions about this client's documents, return data, and tax position. * Cite specific source documents with links into the binder viewer. * Answer general tax research questions using live web search. * Navigate to the client's Tax Prep, Review, Binder, Planning, and Chat pages, plus the workspace Skills settings page. * Propose binder actions such as adding a note or flagging an item; these are proposals that the user confirms. **Cannot do:** * Access data from any other client or answer cross-client aggregate questions. * File or transmit anything to a tax authority. * Navigate to pages outside the five supported client-level destinations. ## Conversation history Conversations persist per client. Returning to Chat for a client resumes the most recent thread. You can start a new conversation at any time. For a searchable history across workspace-level threads, or to ask questions that span multiple clients, use the Analyst. # Analyst ## What is the Analyst? The Analyst is a firm-wide conversational assistant accessible from the left navigation. It is scoped to the entire workspace and can answer questions that span all clients: who is missing documents, which returns are ready to file, who is at risk of an underpayment penalty, and similar pipeline questions. It also supports general tax research, fetching current IRS figures and rule details using live web search. The Analyst maintains a persistent, searchable thread history. ## Opening the Analyst The Analyst is in the left navigation. The landing view shows a hero area, a message composer, and a set of starter prompt chips sampled from the full prompt pool. You can also reach the Analyst from the Home page: typing a question in the "Ask a question" box and submitting it opens a new Analyst thread automatically and navigates you there. ## What data the Analyst can reach The Analyst queries a synthesized index called the Dataview, which covers every client-year pair in the workspace that has been processed. For each client and tax year, the index includes: * Client identity and return type. * Filing attributes (filing status, entity type, tax year). * Income-source flags (for example, whether the client has W-2 income, self-employment income, rental income, or K-1s). * Deduction and credit flags. * Business-related flags. * Key dollar amounts from the return. * A synthesized text narrative describing the client's overall tax position. The index does not include raw source documents. For document-level questions such as "What does their W-2 say?", use per-client Chat instead. ## Firm-operations questions The Analyst is well suited to questions about your filing pipeline and client book. Sample questions: * "Which clients are still missing documents?" * "Who's going to owe this year?" * "Which returns are ready to file?" * "Who should I put on extension?" * "Who's at risk of an underpayment penalty?" * "Which clients are waiting on K-1s?" * "Who had a big income jump this year?" These queries run against the Dataview index. Results are at the client level, not the document level. A client appears in results only after their binder has been created. ## Tax research questions The Analyst can answer general tax questions by fetching current information from the web. This means thresholds, rates, phase-outs, and deadlines are sourced from live data rather than training-data recall. Sample questions: * "What's the bonus depreciation rate this year?" * "Who qualifies for the QBI deduction?" * "What are the estimated-tax safe harbors?" * "What are the crypto reporting rules now?" * "How do the passive activity loss rules work?" * "What counts as reasonable S-corp compensation?" For any answer based on an external source, the Analyst will cite where the information came from. ## Saved threads and conversation history The Analyst maintains a persistent list of saved threads. Threads are listed in a panel and are searchable, so you can return to a prior conversation or pick up where you left off. A specific thread can be linked to directly using the `?thread=` URL parameter in the Analyst URL, which is useful for bookmarking a running conversation. ## Interpreting Analyst answers A few things to keep in mind when reading Analyst responses: * Aggregate counts (for example, "23 clients are missing documents") are based on the Dataview index. A client appears in results only after their binder has been created. * Dollar figures come from return data at the time of last processing. * For tax-law answers sourced from the web, look for source attribution in the response. * If a result seems off, ask the Analyst to show its reasoning or the underlying data it used. * The Analyst counts by distinct client, not by tax year, to avoid double-counting clients who have multiple years in the workspace. ## Limitations and scope boundaries * The Analyst does not have access to raw source documents. For document-level detail, use per-client Chat. * The Dataview index is populated by binder creation. Clients whose binders have not yet been processed will not appear in Analyst results. * The Analyst cannot navigate to an individual client's pages or change the product view to a specific client. * The Analyst cannot file or transmit anything to a tax authority. ## Skills and firm protocols The Analyst's behavior can be shaped by skills: saved instruction sets that load when relevant to the type of question being asked. Firm admins can author and publish custom skills to define how the Analyst responds to specific categories of questions, for example a firm-specific checklist for extension decisions or a preferred format for client summaries. # Chat features This page collects the features shared across Filed's chat surfaces - Binder Chat and per-client Chat. For what each surface knows and how to open it, see [Binder Chat](/reference/products/binder/chat) and [Per-client Chat](/reference/products/chat-and-analyst/client-chat). ## Dictate The message box in both Binder Chat and per-client Chat accepts voice input as an alternative to typing. This is useful when a document is already open and switching focus to type would break your place - dictate the question, review the transcribed text, and send it the same way as a typed message. ## Trace: citations back to source When an answer draws on a specific document, the response includes a citation. Clicking it opens the cited subdocument in the center viewer at the relevant page, so any claim the assistant makes can be checked against the original evidence without leaving the conversation. See [Cited answers and navigating to sources](/reference/products/binder/chat#cited-answers-and-navigating-to-sources). ## Flags and notes persist into the binder Chat is not limited to answering questions - it can take actions in the Binder: adding a note, placing a flag, applying a checkmark, or signing off an item. These are always shown as a proposal first; nothing is written to the binder until you approve it. Once approved, the resulting note or flag behaves exactly like one placed manually with the annotation toolbar - it shows up in the [Notes & flags feed](/reference/products/binder/activity-and-sign-off#the-notes--flags-feed) and persists with the binder going forward, not just within the chat conversation. See [Taking actions from Chat](/reference/products/binder/chat#taking-actions-from-chat). ## Alternate output formats (CSV and more) Both surfaces can return an answer as a downloadable file instead of only prose - ask for a table, a CSV, or a spreadsheet and the response comes back in that format. This is the right tool when the answer needs to be handed off, filed, or processed outside of Filed rather than just read on screen. ## Multiple conversations per client A client isn't limited to one ongoing thread. Starting a new conversation keeps a fresh line of inquiry separate from one already in progress, and nothing is lost - every conversation is retained and reachable from the history control. See [Multiple conversations per client](/reference/products/binder/chat#multiple-conversations-per-client). ## See also [Prompting best practices](/reference/products/chat-and-analyst/prompting-best-practices) for how to get better answers out of these features. # Prompting best practices ## Start broad, then go deep Before opening individual documents, ask Chat for an overview: "What's this client's tax position?" or "What's in this binder?" surfaces a summary grounded in the client's tax position data - taxpayer profile, income sources, and estimated position, as described in [What the assistant knows about this client](/reference/products/chat-and-analyst/client-chat#what-the-assistant-knows-about-this-client). Starting here builds context before diving into individual source documents, and often surfaces which documents are worth opening first. ## Be specific about what you want back A vague question gets a general answer. Naming the form, the box, the client, or the year narrows the assistant's search and produces a more precise citation. Compare "did their income change?" with "how did Schedule C income change from last year?" - both are valid questions, but the second points the assistant at a specific comparison instead of a general summary. ## Use dictation for hands-busy review The message box supports voice input - useful when a document is open and typing would mean switching focus away from it. Dictate the question, review the transcribed text before sending, and the assistant answers the same way it would a typed message. ## Ask for output in the format you need Chat and Analyst can produce more than a written answer. Asking for a table, a CSV, or a spreadsheet - for example, "give me a CSV of every client missing a K-1" - returns the answer as a downloadable file instead of only prose. This is useful for anything you plan to hand off, file, or process outside of Filed rather than just read on screen. ## Verify before you rely on an answer Every claim grounded in a document comes with a citation. Click it before treating the answer as final - especially for anything that will inform a filing decision. See [Cited answers and navigating to sources](/reference/products/binder/chat#cited-answers-and-navigating-to-sources) in Binder Chat and [How the assistant cites its answers](/reference/products/chat-and-analyst/client-chat#how-the-assistant-cites-its-answers) in per-client Chat. ## Let the assistant take the next step, but review the proposal Both per-client Chat and Binder Chat can propose Binder actions - adding a note, placing a flag, signing off an item - directly from the conversation. These show up as a proposal to approve, not an action already taken. Read the proposal the same way you would review a flag: confirm it matches your intent before approving it. ## Use separate conversations for separate lines of inquiry Starting a new conversation (the **+** control) keeps an unrelated question from cluttering the thread you are actively using to work through a specific issue. Conversation history is saved per client, so nothing is lost by starting fresh - see [Conversation history](/reference/products/chat-and-analyst/client-chat#conversation-history). ## Choose the right surface first Before prompting, confirm you are in the surface that can actually answer the question - see [Choosing the right surface](/reference/products/chat-and-analyst#choosing-the-right-surface). A cross-client question asked in per-client Chat will come back empty; the same question in the Analyst works because it has workspace-wide scope. # Playbook ## What is Playbook? Playbook is a library of natural-language protocols that teach the AI assistant how your firm - and you personally - want each task handled. Every protocol you save is applied automatically whenever the assistant runs that type of task. Unlike instructions you type into a Chat session, protocols persist across sessions and clients: you write a rule once, and the assistant follows it every time without you having to repeat it. ## How protocols work Each protocol has two parts: * **Description (the trigger)** - tells the system what situation this protocol applies to. The assistant reads it to decide whether the protocol is relevant for the current run. * **Body (the instruction)** - the actual guidance the assistant follows when the protocol is active, written in plain language with as much or as little detail as the rule requires. When a task starts, the assistant automatically loads every active protocol for that task type and reads them as part of its working context. No manual step is needed at run time. The protocols are injected into the assistant's prompt as a structured block, so the guidance is available from the first action the assistant takes. ## The five task types Protocols are organized by the type of work they govern. A protocol created for one task type will not run during any other. * **AI Tax Prep** -- Protocols that shape how the AI Tax Prep assistant fills returns, handles specific schedules, and resolves data-entry decisions. * **AI Review** -- Protocols that influence how the AI Review assistant applies check rules, flags findings, and writes leadsheet observations. * **AI Tax Planning** -- Protocols that guide AI Tax Planning when identifying strategies and preparing planning materials. * **Binder** -- Protocols that affect how the assistant handles document processing, categorization, and binder organization. * **Chat** -- Protocols that carry persistent preferences into general Chat sessions. ## Your protocols vs. your firm's protocols Every Playbook tab shows two sections, "Yours" and "Firm's": * **Yours** are personal protocols. Only you can see them, and they run only during your own task sessions. Use them to encode your individual working style, preferences for certain client types, or rules you want to test before sharing more broadly. * **Firm's** are shared protocols. They run for every preparer at the firm during the relevant task type, and are either curated defaults shipped by Filed or personal protocols that an admin has promoted to firm scope. See [Yours vs. Firm's Protocols](/reference/playbook/yours-vs-firms-protocols) for details on scope, promotion, and admin governance. ## Where Playbook lives in the app Playbook appears as a dedicated entry in the left-side navigation. Clicking it lands you on the AI Tax Prep tab by default. The left sidebar inside Playbook lists all five task types in order: AI Tax Prep, AI Review, AI Tax Planning, Binder, Chat. Clicking a task type shows its protocol list. Each task-type page shows two sections stacked vertically: Yours at the top, Firm's below. Each row shows the protocol name, its one-line description (the trigger), the author, and a status badge. Clicking a protocol name opens its detail view, which shows the full body text and an activity timeline recording every lifecycle event. ## Why protocols beat one-off instructions There are three ways to give the assistant guidance, and they behave very differently: * **Typing an instruction in Chat** works for that session only. Once the conversation ends, the instruction is gone, and the assistant starts fresh on the next client. * **A personal protocol in Yours** persists permanently. Every time you run that task type, the assistant applies it automatically - whether you are on your first client of the day or your fiftieth. * **A firm protocol in Firm's** does the same, but for every preparer at the firm. Consistency that would otherwise depend on everyone remembering to mention the same thing in Chat is enforced automatically at run time. For a practice with multiple preparers and many clients, the compounding effect is significant: the assistant's behavior becomes predictable and consistent across the whole team without any manual coordination. ## In this section * [Creating Protocols](/reference/playbook/creating-protocols) -- How to author a new personal protocol through Chat and confirm it is active in the Playbook list. * [Yours vs. Firm's Protocols](/reference/playbook/yours-vs-firms-protocols) -- Scope, ownership, the promotion workflow from personal to firm, and admin governance. # Creating protocols ## How protocols are created Protocols are authored through the Chat assistant, not through a standalone form. You describe a preference or rule in plain language - "whenever you're doing tax prep, always check..." or "remember to..." - and the assistant proposes a structured protocol based on what you said. Chat is the authoring surface by design, so the protocol body stays grounded in the natural language you actually use to describe your firm's preferences. Once the assistant proposes a protocol, you review it, refine it through conversation if needed, and approve it. Approval writes the protocol immediately to your personal Playbook list, where it becomes active right away. Chat can only create personal ("Yours") protocols; promoting a protocol to firm scope is a separate admin-gated step. ## Step 1 - express your intent in Chat **Walkthrough: express a protocol intent in Chat** 1. Open a Chat session (from a client's Chat tab, or any Chat surface) and type a protocol-triggering phrase in plain language - "remember to...", "whenever you do tax prep...", or "always check...". For example: "Remember to always verify Box 1 wages against the prior-year return before completing tax prep." 2. The assistant recognizes the intent, confirms the rule it heard, and asks any clarifying questions it needs (for example, which return types it applies to and whether there is a variance threshold) before drafting a protocol. ![The assistant recognizing a protocol intent and asking clarifying questions](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/protocol-create-chat/image1.webp) ## Step 2 - review the proposed protocol **Walkthrough: review the proposed protocol** Once you have answered the assistant's questions, it drafts the protocol and opens a proposal panel. The panel shows the full protocol for review: the auto-generated kebab-case **name**, the **description** (the trigger that decides when the protocol applies), and the **body** (the full instruction, including purpose, when it applies, what to do, examples, and when not to apply). A **Save protocol** and **Discard** action sit at the bottom. ![The proposal panel showing the protocol name, description, and full body](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/protocol-create-chat/image2.webp) To refine before saving, keep chatting - tell the assistant what to change ("only apply this to 1040 returns", "raise the threshold to 15%") and it revises the proposal in place under the same name. Save only once the description and body read the way you want. ### The description field (trigger) The description is what the system evaluates to decide whether a protocol applies to the current run. It also appears as the one-line label in the Playbook list, so it is the first thing you and your colleagues see when scanning your protocol library. A good description is specific enough that the protocol does not activate in situations it was not designed for: "During tax prep when a Schedule C is present" is more reliable than "during tax prep." The description is required, with a maximum length of 1,024 characters. ### The body field (instruction) The body is the full instruction the assistant follows when the protocol is active. It supports Markdown, so you can use bullet lists, numbered steps, conditions, and emphasis to make the rule clear. The assistant reads the body cold, with no prior context about why the rule exists, so it should be self-contained and actionable on its own. The body is required, with a maximum size of 8,000 bytes and 500 lines. ## Step 3 - approve and save **Walkthrough: approve and save the protocol** 1. Click **Save protocol** on the proposal panel. The assistant confirms in the conversation - the proposal card collapses to a compact "Saved to your protocols" card with the protocol name, and the assistant restates the rule it will now follow. ![The assistant confirming the protocol was saved to your protocols](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/protocol-create-chat/image3.webp) 2. Open **Playbook** from the left sidebar and select the matching task type (here, **AI Tax Prep**). The new protocol appears in the **Yours** section with an **Active** status badge, meaning it runs immediately on your future task sessions of that type. ![The saved protocol in the Yours section of Playbook with an Active badge](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/protocol-create-chat/image4.webp) ## Choosing the right task type When the assistant proposes a protocol, it infers the intended task type from your conversation. If you are in an AI Tax Prep session and say "always check for a Schedule C before proceeding," the assistant assigns the protocol to AI Tax Prep. If it guesses incorrectly, you can correct it during the review step before approving. Protocols are task-type-specific. A protocol saved under AI Tax Prep will not run during AI Review, AI Tax Planning, Binder, or Chat sessions, and vice versa. The five task types are AI Tax Prep, AI Review, AI Tax Planning, Binder, and Chat. If a rule genuinely applies to more than one task type, create a separate protocol for each. ## Editing a protocol after creation **Walkthrough: edit a protocol after creation** Protocols are edited through the Chat assistant. In any Chat, name the protocol and describe the change ("update my missing-docs-check protocol to also flag prior-year carryovers"). The assistant revises the protocol and re-proposes it with the same name, so approving the revision updates it in place rather than creating a duplicate. The updated protocol then reflects the change in the Playbook list. ## Toggling a protocol for a single run Disabling (below) is a persistent, Playbook-level change. To skip a protocol for just one run without disabling it going forward, see [Turning protocols on or off for a specific prep](/reference/playbook/toggling-protocols-per-run). ## Enabling and disabling a protocol All new protocols are active when they are first saved. A disabled protocol remains visible in the Playbook list but is skipped at run time, so it is not injected into the assistant's context. Disabling lets you suspend a protocol temporarily without deleting it. **Walkthrough: manage a protocol from the list** Select a protocol's checkbox in the Playbook list to reveal its actions. From here you can **Share with firm** (personal protocols) and, from the **More actions** menu, **Delete** the protocol. Firm protocols are managed by admins from the **Firm's** section (where the actions are **Approve** and **Deny** for pending items). To temporarily change a protocol's behavior without deleting it, edit it through Chat (see above) so it no longer matches the situations you want to skip. ## Naming conventions and limits Protocol names are auto-generated in kebab-case by the Chat assistant when it proposes the protocol. You can change the name during the review step before approving. Key constraints: * **Name**: kebab-case only (lowercase letters, numbers, and hyphens). Maximum 64 characters. Must be unique within the same task type and scope (personal or firm). Reserved names used by Filed's built-in Chat tools cannot be used. * **Description**: Required. Maximum 1,024 characters. No control characters. * **Body**: Required. Maximum 8,000 bytes. Maximum 500 lines. ## More worked examples A protocol is meant to encode a rule your best preparers or reviewers already apply from experience, expressed once so the whole team benefits from it. Two more examples, beyond the Box 1 wages check in Step 1: **A threshold on Form 1116 (foreign tax credit).** "When a client has foreign tax credit and the amount on Form 1116 is below $600 for a single filer or $1,200 for married filing jointly, check whether the simplified limitation election (no Form 1116 required) applies instead, and note the reasoning in Pre-Entry Notes." This encodes a judgment call - when the simpler path is available - that would otherwise depend on an individual preparer remembering the de minimis threshold. **An HSA distribution check.** "Whenever a client has HSA distributions reported on Form 1099-SA, confirm that qualified medical expense documentation is present in the binder before marking the distribution as non-taxable. If documentation is missing, flag it in Pre-Entry Notes as a required follow-up." This turns a firm's due-diligence standard on HSA distributions into a rule Filed applies automatically on every return that has one, rather than relying on each preparer to remember to check. Both examples follow the same shape as any protocol: a specific trigger (the description) and a self-contained instruction (the body) that does not assume the assistant remembers anything about the client beyond what is in the current binder. ## Tips for writing effective protocols **Be specific in the description.** The description is evaluated at run time to decide whether the protocol applies. Vague triggers like "during tax prep" can fire in situations where they are not relevant. Triggers like "when a Schedule C is present" or "when the client has K-1 income from a partnership" activate the protocol precisely when you need it. **Write the body as if the assistant has never seen this client before.** The body is read cold, with no memory of previous sessions or other protocols. If the rule depends on a concept (a form type, a firm policy, a threshold), spell it out rather than assuming the assistant will infer it. **Avoid duplicating firm protocols.** Before saving a personal protocol, check the Firm's section for the same task type. If a firm protocol already covers the rule, a personal duplicate adds overhead without changing behavior (byte-identical pairs are de-duplicated automatically). To override a firm rule for your own runs, write a personal protocol with the same name and a different body; your version takes precedence. **Keep each protocol focused.** A protocol covering one specific job is easier to maintain, reason about, and update than one that bundles five unrelated rules. If a body is growing very long, consider splitting it into two protocols with more targeted descriptions. **Use the Chat assistant to iterate.** You do not need to get the protocol right on the first proposal. Describe what is wrong, and the assistant revises and re-proposes with the same name, so the update lands in place rather than creating a duplicate. # Yours vs. firm's protocols ## Two tiers, one Playbook Every Playbook tab shows the same two sections: "Yours" at the top and "Firm's" below. Both are visible to every preparer, so you can see what the firm expects and avoid writing personal protocols that duplicate what is already enforced at the firm level. Both contribute to what runs when the assistant processes a task; the difference is who the protocols apply to and who controls them. ## Your protocols ("Yours") Personal protocols are created by you, visible only to you, and run only during your own task sessions. Admins cannot see or edit your personal protocols. They represent your individual working preferences, rules you apply to specific client types, or guidance you are testing before suggesting it for the whole firm. Chat can only create personal protocols. There is no path in Chat to author a firm protocol directly. ### Who can create and edit them Any preparer can create personal protocols through Chat. Only the preparer who owns a personal protocol can edit or delete it. No approval workflow is required. A new personal protocol becomes active immediately when you approve the Chat proposal. ### When they apply Your personal protocols are loaded alongside firm protocols whenever you run a task. If you have a personal protocol with the same name as a firm protocol under the same task type, your personal version takes precedence: the firm version is skipped for your run only, and other preparers continue to see the firm version. If your personal protocol and the firm protocol with the same name have identical bodies, the system automatically de-duplicates them and uses only the firm copy. This avoids injecting the same instruction twice without any behavior change. ## Firm's protocols ("Firm's") Firm protocols run for every preparer at the firm during the relevant task type. They appear in the "Firm's" section of every preparer's Playbook view. There are two kinds of firm protocols: curated (built-in) protocols and firm-authored protocols. ### Built-in (curated) protocols Filed ships a set of curated protocols for the AI Review and AI Tax Planning task types. They are organized by return type (1040, 1120S, 1065, 1041, 990, and so on), so each return type has domain-specific review rules or planning strategies bundled in. Curated protocols are active by default for all preparers. Admins can disable a curated protocol or replace it with a firm-authored version that overrides the default. If a firm-authored override is later removed, the curated default automatically becomes active again. Preparers cannot edit curated protocols. ### Firm-authored protocols Firm-authored protocols are promoted from a preparer's personal Yours list by an admin. Once promoted, the firm copy is independent: edits the original preparer makes to their personal version do not automatically update the firm copy. Only admins can edit or remove firm-authored protocols. ## Promoting a personal protocol to the firm A preparer with a personal protocol they want the whole firm to use can request promotion. The action is labeled "Share with firm" in the protocol's actions menu. **Walkthrough: share a protocol with the firm** 1. In the **Yours** section, select a personal protocol's checkbox and click **Share with firm**. ![A selected personal protocol with the Share with firm action](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/protocol-share-with-firm/image1.webp) 2. The protocol's badge in **Yours** changes to **Waiting**, and a copy appears in the **Firm's** section with a **Pending** badge awaiting admin review. ![The protocol showing Waiting in Yours and Pending in Firm's](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/protocol-share-with-firm/image2.webp) ### What admins see during review When a preparer requests promotion, the protocol appears in the Firm's section with a Pending status badge. Admins can open the protocol's detail page to read the full description and body, see who submitted the request, and review the activity timeline. The admin then chooses to approve or deny. ### Approval **Walkthrough: approve a pending protocol (admin)** 1. As an admin, select the pending protocol's checkbox in the **Firm's** section. An action bar appears with **Approve** and **Deny**. ![The pending protocol selected with Approve and Deny actions](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/protocol-approve/image1.webp) 2. Click **Approve**. The protocol becomes **Active** in the Firm's section, and the original author's personal copy in **Yours** updates to a **Shared** badge. ![The protocol Active in Firm's and Shared in Yours after approval](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/protocol-approve/image2.webp) On approval, the protocol is copied to firm scope and becomes immediately active for all preparers at the firm. The original preparer's personal copy remains in their Yours list with its status updated to "Shared." From that point on, the firm copy is what runs, both for the original preparer and for everyone else. The personal copy is still present: if the original preparer later edits their local version to differ from the firm copy, their personal version takes precedence for their own runs. ### Denial **Walkthrough: deny a pending protocol (admin)** 1. As an admin, select the pending protocol in the **Firm's** section and click **Deny** (an optional deny reason may be requested). ![The pending protocol selected with the Deny action](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/protocol-deny/image1.webp) 2. The protocol is removed from the Firm's pending list, and the author's personal copy stays in **Yours** with a **Denied** badge. The preparer can revise and resubmit; any deny reason appears on the protocol's detail. ![The denied protocol shown in Yours with a Denied badge](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/protocol-deny/image2.webp) On denial, the protocol is not promoted. The preparer's personal copy remains in Yours and continues running for them. The deny reason, if the admin provided one, appears on the protocol's detail page. The preparer can revise the protocol and resubmit. ## Precedence: what runs when both exist The rule: if you have a personal protocol and a firm protocol with the same name under the same task type, your personal version wins for your runs, and the firm version is not injected during your sessions. This lets individual preparers override firm defaults when they have a specific reason to. If the bodies of the personal and firm versions are byte-for-byte identical, the system de-duplicates them and uses only the firm copy. This prevents the same instruction from appearing twice in the assistant's context, which would waste token budget without any change in behavior. ## Protocol status reference | Status | Where it appears | Meaning | | -------- | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | Active | Yours and Firm's | Running normally. No badge shown; the default state. | | Disabled | Firm's | Exists in the list but skipped at run time. Admins can re-enable it. | | Waiting | Yours | You have requested promotion to the firm. Awaiting admin decision. | | Shared | Yours | Your protocol was approved and promoted. The firm copy is now active for all preparers. | | Denied | Yours | Promotion was rejected. Your personal copy is still active for your runs. The deny reason (if provided) is visible on the detail page. | | Pending | Firm's | An admin sees this badge on a protocol awaiting their approval or denial. | Personal protocols that are not in any promotion workflow show no status badge; they are simply active. ## Admin governance Admins have full control over the Firm's section for their workspace. **Disabling a firm protocol** suspends it without removing it. The protocol remains in the Firm's list with a Disabled badge and can be re-enabled at any time. This applies to both curated and firm-authored protocols. *Walkthrough:* 1. Open **Playbook** from the left sidebar and select the **AI Review** task type. 2. In the **Firm's** section, select the protocol's checkbox and choose the disable action. The protocol remains listed with a **Disabled** badge and is skipped on future runs; existing leadsheets from prior runs are not retroactively changed. **Removing a firm-authored protocol** permanently deletes it from firm scope. Preparers who had that protocol in their Yours list as Shared will see their personal copy revert to its previous status. This action cannot be undone. **Removing a firm override of a curated protocol** reverts that position to the bundled curated default. The curated default becomes active again immediately. **Approving or denying a promotion request** requires admin role. Only one promotion request for a given protocol name can be pending at a time. If a preparer tries to share a protocol that already has a pending request from another preparer under the same name, the system rejects the second request until the first is decided. The activity timeline on any protocol's detail page records its full history: creation, every promotion request, approval or denial decisions, enables and disables, and the actor and timestamp for each event. This gives admins a complete audit trail for firm-scope protocol changes. # Toggling protocols per run ## Two different kinds of "off" There are two different ways to stop a protocol from applying, and they are not the same: * **Disabling a protocol** (covered in [Enabling and disabling a protocol](/reference/playbook/creating-protocols#enabling-and-disabling-a-protocol)) turns it off everywhere, for every future run, until it is re-enabled. This is a persistent change to your Playbook or the firm's. * **Opting a protocol out for a single run** leaves it enabled in the Playbook, but skips it for just the run you're working on right now. This is the tool for "I know this rule usually applies, but not to this specific client's situation this one time." ## Where the per-run toggle appears When starting or reviewing a task, active protocols that apply to that task type are shown with an option to opt out for that run specifically - without touching their Playbook-level Active status. This is confirmed for AI Review runs, where an opt-out control appears alongside the protocols that would otherwise apply to that review. ## When to use a per-run toggle instead of disabling Use the per-run toggle when a protocol is generally correct but doesn't fit one specific case - for example, a firm-wide threshold protocol that shouldn't apply to an unusual client this year. Use full disabling (from the Playbook) when a protocol is wrong or no longer wanted at all, for every future run. Opting out for a single run does not change the protocol's Active/Disabled status in the Playbook - the next run defaults back to the protocol applying normally, unless it's opted out again. ## Where to check what applied to a specific run # Plugins & integrations Plugins are the connections that make Filed useful at the point of work. They fall into two groups: * **Prowork** surfaces bring Filed's AI assistant into the tools preparers already use every day. * **Integrations** pull client data from the systems where it already lives. Together they let Filed read from the right sources and respond in the right place. The Plugins page is at **Plugins** in the Filed web app. ## Prowork - bring AI where you work Prowork puts Filed's AI assistant inside the tools preparers spend their day in: a Windows desktop sidebar, an Excel task pane, and a Google Sheets sidebar. The AI comes to the preparer rather than requiring a context switch to a separate app. Each Prowork installation is called a surface. A surface is tied to a specific device and user combination, so installing on a laptop and a desktop creates two separate surfaces, each with its own name and login code. One person can have multiple surfaces across different tools and devices. ### Desktop A Windows native app that docks as a sidebar on the right side of the screen, sitting alongside tax software automatically when it opens. [Learn more about Prowork Desktop](/reference/plugins/prowork/desktop). ### Excel An Office task pane add-in that opens a Filed sidebar inside any Excel workbook, letting preparers chat with the AI and write data directly into the active sheet. [Learn more about Prowork for Excel](/reference/plugins/prowork/excel). ### Google Sheets A Google Workspace add-on that delivers the same Filed AI sidebar inside Google Sheets, with the same capabilities as the Excel add-in. [Learn more about Prowork for Google Sheets](/reference/plugins/prowork/google-sheets). ## Integrations - connect your data sources Integrations are the connections to the systems where client data already lives. They are what give Prowork and the rest of Filed their context: when a preparer asks about a client's income, Filed pulls the answer from the documents and data that integrations have made available. Integrations are set up once at the workspace level. Any team member with the right permissions can connect an integration, and once connected it is available to everyone in the workspace. ### Integration guide library The expanded catalog is organized for accounting firms in the same order as the Integrations page: 1. [Tax software](/reference/plugins/integrations/tax-software) 2. [Practice management](/reference/plugins/integrations/practice-management) 3. [Accounting & ERP](/reference/plugins/integrations/accounting-and-erp) 4. [Document management](/reference/plugins/integrations/document-management) 5. [Communications](/reference/plugins/integrations/communications) 6. [Productivity](/reference/plugins/integrations/productivity) 7. [Documents & signatures](/reference/plugins/integrations/documents-and-signatures) 8. [CRM](/reference/plugins/integrations/crm) 9. [Payroll, spend & payments](/reference/plugins/integrations/payroll-spend-and-payments) Each guide explains the purpose of the connection, the access to prepare, and the connection flow. Detailed guides for existing DMS, email, and tax-software integrations remain available in their original sections. ## MCP - connect AI assistants The Filed MCP server connects your workspace to AI assistants like ChatGPT and Claude over the Model Context Protocol. The assistant can query your workspace, make changes, and upload files, authenticated through Filed's own sign-in. [Learn more about MCP](broken://pages/SGuspVhUrfdEZQCgedo3), or jump straight to the setup guides for [ChatGPT](broken://pages/ejGZNIxlZA8XtGfvG41G) and [Claude](broken://pages/Mpr3vt2Vq1glfjtheHlJ). ## Filed Printer *Coming soon!* Filed Printer is a virtual printer that appears in the operating system's printer list. Preparers can print from any desktop application - tax software, a browser, a PDF viewer - and the document lands directly in their Filed workspace. It appears under **Others** on the Plugins page. [Learn more about Filed Printer](/reference/plugins/filed-printer). ## How connecting works The general pattern is the same across all plugins: find the plugin on the Plugins page, click **Install** or **Connect**, complete the guided steps, and the plugin shows as active. The two groups use different authentication models: * **Prowork surfaces** use a login-code model: Filed generates a short-lived token that the preparer pastes into the app or add-in. The token is scoped to one workspace and one device and should not be shared. * **Integrations** use either OAuth (the provider's own authorization screen) or credential entry (username and password for the service), depending on what the provider supports. ## Permissions and team access * **Integrations** are connected by workspace admins on behalf of the whole workspace. * **Prowork surfaces** (Desktop, Excel, and Google Sheets) are installed by each team member on their own devices and accounts. * **Filed Printer** is per-user too: each person sets it up on each computer they use, and each workspace requires its own separate printer setup. All Prowork installations across the workspace appear in the Installations table on each Prowork plugin page, so admins can see which devices are connected. # Integration guides Provider-by-provider integration setup for Filed. These guides follow the same order as the Integrations page. A workspace administrator creates each connection in **Plugins**; the account they authorize determines what Filed can access. 1. [Tax software](/reference/plugins/integrations/tax-software) 2. [Practice management](/reference/plugins/integrations/practice-management) 3. [Accounting & ERP](/reference/plugins/integrations/accounting-and-erp) 4. [Document management](/reference/plugins/integrations/document-management) 5. [Communications](/reference/plugins/integrations/communications) 6. [Productivity](/reference/plugins/integrations/productivity) 7. [Documents & signatures](/reference/plugins/integrations/documents-and-signatures) 8. [CRM](/reference/plugins/integrations/crm) 9. [Payroll, spend & payments](/reference/plugins/integrations/payroll-spend-and-payments) ## Connection flow ### 1. Name the connection and choose access Select the provider in **Plugins**, choose **Connect**, and enter a name that identifies the account or environment. Read access is always enabled. Write access is enabled by default, but you can clear it to make the connection read-only; you can change this later from the connection settings. ### 2. Authorize the provider Filed then opens the provider's sign-in page or, for organization-specific apps, asks for the required credentials in the next dialog step. ### 3. Authorize and verify Approve the provider's consent screen and return to Filed. Filed verifies the connection before it becomes active. Pending or failed connections can be reconnected from the provider page. # Tax software Use these guides to connect AI Tax Prep to the firm tax software environment. Connect only from a firm-managed workstation with access to the intended data location. These integrations can also be used in Filed Chat and Routines. Read access is always enabled; turn off write access when Filed should not perform data-entry actions. * [CCH Axcess](/reference/plugins/integrations/tax-software/cch-axcess) * [UltraTax CS](/reference/plugins/integrations/tax-software/ultratax-cs) * [Lacerte](/reference/plugins/integrations/tax-software/lacerte) * [Drake](/reference/plugins/integrations/tax-software/drake) * [GoSystem Tax RS](/reference/plugins/integrations/tax-software/gosystem-tax-rs) * [ProConnect Tax](/reference/plugins/integrations/tax-software/proconnect-tax) # CCH Axcess With this integration connected, Filed **AI Tax Prep** can use the available CCH Axcess data as part of the tax-preparation workflow. You can also use the connection in Filed **Chat** and **Routines**. When **Write** access is enabled, Filed can complete approved data-entry work in CCH Axcess; review the return in CCH Axcess before filing or finalizing the work. Filed integrates with CCH Axcess Tax as a cloud connection - no software needs to be installed on firm workstations. Filed authenticates using a dedicated CCH Axcess login and can sync your client roster, read existing return data for AI preparation, and write completed data entry back into returns automatically. ## What this integration does Filed supports three capabilities with CCH Axcess Tax: * **Sync client list** - Filed imports your full client roster from CCH Axcess so it can match prepared returns to the right clients. Client list sync does not include SSNs. * **Read return data** - Filed captures a client's current return from CCH Axcess and uses it as a starting point for AI preparation. * **Enter return data** - After AI preparation is complete, Filed writes the finished data entry directly back into the client's return in CCH Axcess. Firms with the CCH Axcess Tax API Kit get fully automated sync: Filed handles client list refresh, return reads, and data-entry writes without any manual file exchange. To set up an API Kit firm, follow [Connect CCH Axcess API with Filed](/reference/plugins/integrations/tax-software/cch-axcess/connect-cch-axcess-api-with-filed) to create the client ID and client secret, then find the integrator key required for the API connection. ## Prerequisites * A CCH Axcess Tax account with admin access. * A dedicated CCH Axcess login created specifically for Filed - do not use a personal login. * For direct CCH authentication, admin ability to configure two-factor authentication (2FA) device pairing and the dedicated login's Account ID, User ID, and password. * For Microsoft SSO authentication, support from an IT administrator who manages Microsoft 365, CCH user provisioning, permissions, and security policies. * Knowledge of whether your firm has the CCH Axcess Tax API Kit. * The **Return transfer** functional right granted to the security group used by the dedicated Filed login. If your firm uses Microsoft single sign-on (SSO) to access CCH, complete the Microsoft SSO setup below before connecting the integration. ## Microsoft SSO authentication setup Your IT team must create and configure a dedicated Microsoft 365 user account for Filed. Do not use an individual employee's account. Once the Microsoft account has been created, your IT team should: 1. Sync or provision the new user in CCH by following your firm's established Microsoft-to-CCH workflow. 2. Assign the permissions the user needs to access the relevant CCH services and data. 3. Sign in to CCH with the new account to confirm that synchronization and permissions are working correctly. 4. Share the account's email address and password with Filed through an approved secure channel. 5. If 2FA remains enabled, enter the account's TOTP secret in the **Authenticator key** field in the CCH integration setup in Filed. {% hint style="warning" %} The account must support unattended access. Configure one of these options: * **Keep 2FA enabled:** Configure time-based one-time password (TOTP) authentication and enter the TOTP secret in the **Authenticator key** field in Filed. Filed uses the key to generate a verification code when signing in. * **Disable 2FA:** If your organization's security policy permits it, disable 2FA or exempt the dedicated account from interactive MFA requirements. Filed can then sign in without a second-factor prompt. Treat the TOTP secret like a password and enter it only through the approved setup flow. Avoid Microsoft Authenticator tied to an individual employee, as it can prevent reliable access. {% endhint %} This setup should be completed by someone on your IT team who manages Microsoft 365, CCH user provisioning, permissions, and security policies. ## Connecting CCH Axcess to Filed For direct CCH authentication, setup involves two steps in Filed: first connecting an authenticator (2FA pairing), then adding the login credentials. Both steps must be completed before the connection becomes active. The 2FA pairing and credential steps below apply to direct CCH logins. If your firm uses Microsoft SSO, complete the Microsoft SSO authentication setup above and coordinate the secure credential handoff with Filed. ### Setting up two-factor authentication (2FA) CCH Axcess requires 2FA for every sign-in. Filed acts as the authenticator, generating verification codes automatically each time it accesses CCH Axcess on your behalf. The pairing works by exchanging a second-factor backup code: instead of scanning CCH Axcess's QR code with a phone app, you give that backup code to Filed. Filed uses it to generate the 6-digit code needed to complete the pairing - and from that point forward generates codes automatically. Have both CCH Axcess and Filed open side by side before you start - one step is time-sensitive, so you'll want to move between the two quickly. **Pairing steps:** 1. In CCH Axcess, open **User Options** from the left navigation of the Dashboard. ![Open User Options from the CCH Axcess Dashboard](/files/YIWhcD9n6BH9uu2XbgoY) 2. Under **Change login profile**, select **2-Step verification device pairing**. ![Select 2-Step verification device pairing under Change login profile](/files/28tKKrtUX24U7r8xbZ1n) 3. Select **Google Authenticator or another authenticator application**, make sure its radio button is selected, and click **Pair device**. ![Select Google Authenticator or another authenticator application and click Pair device](/files/NYj6lhLi0TsWhpJihCbD) 4. For **What type of device do you have?**, select **Other** and click **Continue**. ![Select Other as the device type and click Continue](/files/j5bAhfCzoovwie13KrxT) 5. CCH Axcess displays a QR code. Copy the **second-factor backup code** shown under the QR code, then click **Continue**. ![Copy the second-factor backup code shown under the QR code](/files/w9uvPeWIw2dNQ4DGEj9f) 6. Go back to Filed and open the CCH Axcess integration page. In the **Connect authenticator** window, paste the copied code into the **Second-factor backup code** field and click **Generate code**. ![Paste the backup code into the Second-factor backup code field and click Generate code](/files/GEAp84iRd2j4lFKc8ED8) 7. Filed displays a 6-digit verification code. Copy it and return to CCH Axcess promptly - the code expires after about 30 seconds. If it expires before you use it, click **New code** in Filed. ![Copy the 6-digit code Filed generates](/files/oUqcn91548sw1UBdMP3l) 8. Paste the code into the **Enter Code** field in CCH Axcess and click **Continue**. ![Paste the code into the Enter Code field and click Continue](/files/gIhrrShpibQODivr49A4) 9. Click **Close** in the **Setup Complete!** dialog. ![Click Close in the Setup Complete dialog](/files/0T2qOUBsOwt37zpD8rqg) 10. Back on the device pairing screen, confirm the **Google Authenticator or another authenticator application** option is selected - its status should now show **Paired**. ![Confirm the Google Authenticator option shows Paired](/files/H5A5hQU77yaGZBXej6YG) 11. Return to Filed and click **I entered the code** to confirm the setup. **Troubleshooting 2FA pairing:** * **Setup unfinished** - You entered a backup code but did not finish confirming the pairing in CCH Axcess. Click "Finish setup" in Filed, generate a new code, and complete the steps in CCH Axcess. * **CCH Axcess rejects the code** - The code expired before it was entered (codes are valid for 30 seconds). Click "New code" in Filed and enter the fresh code promptly. * **Device was unpaired in CCH Axcess** - The previous pairing is no longer valid. Click "Update authenticator" in Filed and complete the pairing again with a new second-factor backup code. ### Adding credentials Once the authenticator is confirmed, Filed unlocks the credential step. You will enter the Account ID, User ID, and password for the dedicated login. Filed verifies the sign-in immediately and marks the connection active once the check succeeds. ### Confirming your business unit and office During setup, Filed asks for your Business Unit name and Office name. These values must match exactly what is configured in CCH Axcess. The defaults are "Main" for Business Unit and "Main Office" for Office - if your firm uses different names, you will need to look them up. To find the correct names: 1. Log into CCH Axcess Dashboard as an admin and open Firm settings in the bottom-left corner. 2. Navigate to Organizational Units. 3. Check the Offices tab for your Office name and the Business Units tab for your Business Unit name. 4. Copy the exact values into Filed, then click Configure. ### Granting Return transfer access Filed needs the **Return transfer** functional right enabled in CCH Axcess. This makes the **Transfer to ProSystem fx** option available in CCH, which Filed uses to read the current state of a return during tax prep. This does not mean preparers need to manually transfer returns. The permission only needs to be available so Filed can access the return data it needs. To grant the permission: 1. Open **CCH Axcess Dashboard**. 2. Click **Application Links**. 3. Under **Security**, click **Security groups**. ![CCH Axcess Dashboard with Security groups highlighted](/files/sdZebS1dLBICe6t7kKep) 4. In the **Security Groups** grid, right-click the security group used by the Filed CCH login. 5. Click **Open**. 6. In the navigation pane, click **Functional rights**. 7. Open the **Tax** tab. 8. Find **Return transfer** under **Tax Preparation**. 9. Set **Return transfer** to **Grant**. 10. Click **Save & Close**. ![CCH Axcess Functional rights with Return transfer set to Grant](/files/3jQUhhVwZPYPHrVS4Ik0) After the permission is granted, the CCH login used by Filed should have access to the **Transfer to ProSystem fx** option in Return Manager. If the option is still missing, check that: * The permission was added to the correct security group. * The CCH login used by Filed belongs to that security group. * No other group or role has **Return transfer** set to **Never allow**. * The user has signed out and back in after the permission change. ## Tax prep workflow With the CCH Axcess Tax API Kit, Filed handles the entire sync cycle automatically. Filed refreshes the client list on a daily schedule. When you start tax preparation for a client, Filed reads the client's existing return data from CCH Axcess automatically. After AI preparation is complete, Filed writes the finished data entry directly into the return in CCH Axcess - no file downloads or uploads required. ## K-1s already imported in CCH Axcess If K-1 data has already been imported directly into CCH Axcess through its own import functionality, do not also upload those K-1 PDFs to Filed. Doing so risks entering the same data twice. Two approaches to avoid duplication: * **Exclude in Filed:** Open the Forms view during the AI Tax Prep workflow, locate the K-1 documents, and select Exclude. Filed will skip processing those forms. * **Don't upload the K-1 PDFs:** The simplest option is to leave K-1 PDFs out when uploading source documents to Filed in the first place. If Filed's Checklist flags missing K-1s, this is not a problem - the data already exists in CCH Axcess. You can ignore the flag or mark it as reviewed. ## Troubleshooting ### Return not populating after import First, open the return in CCH Axcess and click the Recalc button. Manual recalculation resolves most cases where data appears missing after import. If data still does not appear, navigate to CCH Dashboard, open Application Links, then Batch Manager, and click Refresh Job Status. Check the Job Status section for the import job: * **Complete** - the import finished successfully; the issue may be elsewhere. * **Exception (Failed or Partial Success)** - click the Exception status to see error details. Screenshot the error and contact Filed support. If Filed cannot read the return or CCH hides the **Transfer to ProSystem fx** option, confirm that the dedicated Filed login has the **Return transfer** functional right granted. ### Client not found in Filed The daily sync may not have run yet for a client recently added to CCH Axcess. To trigger a manual sync: navigate to the Tax Software page in Filed, click the three-dot menu next to CCH Axcess Tax, and choose Sync clients, then Sync. ### "Sync failed to complete" error Click Sync in the top-right corner to retry. If the error persists, contact Filed support. ### Diagnostic 49842 - withholding mismatch CCH Axcess may raise diagnostic error 49842 with the message: "The amount of withholding must equal the amount of withholding reported on Form(s) W-2, Schedule(s) K-1, Form(s) 1099, Form(s) W-2G and Form 8959, line 24 for electronic filing." Resolution: 1. Open Return Manager and select the affected return. 2. Click Utilities, then Rebuild. 3. Select Continue, then OK. 4. Open the rebuilt return (it will be marked "V2"). 5. Run Recalc. For further detail, see CCH support article 000158186. ## Frequently asked questions **Should I upload K-1s to Filed if they are already imported in CCH Axcess?** No. See the K-1s section above. **How do I find a client's ID in CCH Axcess?** The Client ID is visible in Return Manager as the identifier associated with each return (for example, 123-AFILED). **How often does Filed sync my client list from CCH Axcess?** Filed refreshes the client list daily. ## Capabilities ### Review return and client information Use Filed to retrieve the client and return information available through this tax-software connection. This gives preparers and reviewers a starting point without manually re-keying the same information. ### Prepare approved data-entry work When **Write** access is enabled, Filed can prepare and run approved data-entry work in the connected tax environment. Use this for repeatable preparation workflows, then review the return in the tax software before filing. ### Keep the connection operational Use the connection to validate access, recover from a disconnected desktop session, and keep the firm’s tax-work workflow linked to the correct environment. # Connect CCH Axcess API with Filed If your firm uses the CCH Axcess Tax API Kit, you need three values to connect it to Filed: 1. **Client ID** 2. **Client secret** 3. **Integrator key** The first part of this guide registers Filed as a third-party application and creates the client ID and client secret. The final section shows you where to find the integrator key in the CCH Axcess Developer Portal. ## Before you start Make sure you have: * Access to the CCH Axcess Dashboard. * Permission to manage third-party applications for your firm. * Access to the [CCH Axcess Developer Portal](https://developers.cchaxcess.com/). * A secure place to save the client ID, client secret, and integrator key. {% hint style="warning" %} Treat the client secret and integrator key like passwords. Save them in your firm's approved password manager or secure credential store. {% endhint %} ## 1. Open Developer Tools 1. Open the CCH Axcess **Dashboard**. 2. Select **Application Links** in the left navigation.
CCH Axcess Dashboard with Application Links in the left navigation

Select Application Links from the Dashboard.

3. Under **Firm**, select **Developer Tools**.
Application Links page with Developer Tools under Firm

Open Developer Tools under Firm.

## 2. Add the application 1. On the **Manage Third Party Applications** page, click **+ Add Application**.
Manage Third Party Applications page with application names and client IDs blurred

Click + Add Application.

2. Complete **Application Details**: * **Application name:** Enter any descriptive name, such as `Filed`. * **Application type:** Leave this set to **AuthorizationCode**. * **Description:** This is optional. * **Access token lifetime:** Filed recommends **2 hour**. * **Refresh token lifetime:** Filed recommends **4 Weeks**. 3. Click **Next**.
Application Details with a two-hour access token lifetime and four-week refresh token lifetime

Use a two-hour access token lifetime and a four-week refresh token lifetime.

## 3. Leave the scope definition unchanged On the **Scope Definition** step, leave the existing settings unchanged and click **Next**. ## 4. Configure OAuth settings On the **OAuth Settings** step: 1. Under **Redirect URL**, add the following URL: ``` https://web.apps.filed.com/integrations/oauth/callback ``` 2. Select the checkmark to save the URL. 3. Under **Post Logout Redirect URL**, add the same URL: ``` https://web.apps.filed.com/integrations/oauth/callback ``` 4. Select the checkmark to save the URL.
OAuth Settings with the Filed callback URL entered as both redirect URLs

Use the Filed callback URL for both redirect URL fields.

## 5. Save the client ID and client secret 1. Copy the **Client ID** and save it securely. 2. Click **Finish**. 3. CCH Axcess displays the **Client secret**. Copy it and save it securely with the client ID. You now have the client ID and client secret. Complete the next section to get the integrator key. ## 6. Find the integrator key 1. Sign in to the [CCH Axcess Developer Portal](https://developers.cchaxcess.com/). 2. Open the [Profile page](https://developers.cchaxcess.com/profile), or select **Profile** from the top navigation. 3. Under **Subscriptions**, find an active subscription. 4. Select **Show** next to either the **Primary key** or **Secondary key**. 5. Copy the displayed value and save it securely as the **Integrator key**. You can use either available key.
CCH Axcess Developer Portal Profile page showing primary and secondary subscription keys

Use one of the available subscription keys as the integrator key.

## Credentials to provide to Filed You should now have all three values required for the CCH Axcess API connection: * **Client ID** from step 5. * **Client secret** from step 5. * **Integrator key** from step 6. # UltraTax CS Connect UltraTax CS to use its client and return data in Filed **AI Tax Prep**, **Chat**, and **Routines**. With **Write** access enabled, Filed can complete approved data-entry work in UltraTax CS. Always review the return in UltraTax CS before filing or finalizing it. Filed supports two UltraTax CS workflows: * **Standard workflow:** Pair Filed with the Windows workstation that runs UltraTax CS. Filed can sync clients, read returns, and enter prepared data through the Filed Desktop app. * **Manual workflow:** If you use Thomson Reuters Virtual Office, Rightworks, another hosted environment, or any setup where direct desktop sync is unavailable, export the client list and exchange UltraTax backup files manually. ## What this integration does * **Sync client list:** Filed reads the UltraTax CS client roster from the paired workstation so it can match prepared returns to the right clients. A manual Excel upload is also available as a fallback. * **Read return data:** Filed captures a client's current return data from UltraTax CS as a starting point for AI preparation. * **Enter return data:** After AI preparation is complete, Filed enters the approved data into the client's return in UltraTax CS. ## Prerequisites ### Standard workflow * UltraTax CS installed on a Windows workstation. * The Filed Desktop app installed and running on that same workstation. * Access to the folder where UltraTax CS stores client data. The usual location for tax year 2025 is `C:\WinCSI\UT25DATA`. * A workstation that can remain online whenever Filed needs to sync or perform tax-preparation work. You do not need to enter Thomson Reuters credentials or a two-factor secret in Filed to connect the current Desktop app integration. ### Manual workflow * Access to UltraTax CS through Thomson Reuters Virtual Office or Rightworks. * Permission to export a client listing from UltraTax CS. * Permission to create and restore UltraTax client backup files. ## Connect UltraTax CS to Filed Use these steps for the standard workflow: 1. In Filed, go to **Plugins > Integrations > UltraTax CS**. 2. Click **Connect UltraTax CS**. 3. Name the connection and review the requested Read and Write access. 4. Select the desktop that runs UltraTax CS. If it is not listed, click **Register this device** and follow the prompts to install or open the Filed Desktop app on that workstation. 5. Wait for Filed to show that the connection is active. 6. On the connection page, find **Data folder**. Enter the folder where UltraTax CS stores client data, such as `C:\WinCSI\UT25DATA`, then click **Save folder**. 7. In **Client list**, click **Sync Clients**. Keep the Filed Desktop app open while the sync runs. Filed reads the client roster directly from the configured UltraTax data folder. You do not need to export a Client Listing Report for the normal sync flow. ### Manual client-list workflow Use the manual client-list workflow for Thomson Reuters Virtual Office, Rightworks, other hosted environments, or any setup where the Filed Desktop app cannot sync the roster directly. 1. In UltraTax CS, export the **Client Listing Report** as an Excel file. 2. In Filed, upload the exported report in the **Client list** section. 3. Export and upload a new report whenever clients are added or changed in UltraTax CS. The following video walks through the UltraTax client-list export: {% embed url="" %} The manual client-list export imports the firm's roster into Filed. It is separate from the per-client backup-file workflow used to move return data into and out of hosted UltraTax environments. ## Tax prep workflow: Standard Once the desktop is paired, the data folder is saved, and the client list is synced, Filed can use the connected workflow. When you start tax preparation for a client, Filed reads the client's return data from UltraTax CS through the Desktop app. After AI preparation is complete, Filed enters the approved data into UltraTax CS and packages a backup. You can download a completed backup from the client's **Output** tab under **View Backups** if you want to archive or review it. Keep UltraTax CS and the Filed Desktop app available on the paired workstation while a sync or data-entry job is running. Close the client return in UltraTax CS before Filed reads or writes it. ## Tax prep workflow: Virtual Office and Rightworks Thomson Reuters Virtual Office, Rightworks, and similar hosted environments may not allow the Filed Desktop app to run alongside UltraTax CS. In these environments, use the manual client-list workflow above to import the roster, then exchange backup files for each client's tax-preparation work. 1. [Create and upload an UltraTax client backup file](/reference/plugins/integrations/tax-software/ultratax-cs/backing-up-a-client-in-ultratax-cs). 2. Filed prepares the return using the UltraTax backup file and source documents. When preparation is complete, you receive an email and in-app notification, and the status updates to **Data Entry Completed**. 3. Download the completed backup and [restore it in UltraTax CS](/reference/plugins/integrations/tax-software/ultratax-cs/restoring-a-backup-into-ultratax-cs). If you need the return as it was before Filed's preparation, download the **Sync by Filed** version from the backups list. It is the earliest entry and appears at the bottom of the list. ## Troubleshooting ### Filed Desktop disconnects or stops syncing The workstation may have restarted, gone offline, or signed out. Open the Filed Desktop app on the paired UltraTax workstation and confirm that the connection is active. Keeping the paired workstation online reduces interruptions. ### Sync Clients is unavailable Open the Filed Desktop app on the paired workstation. In Filed, confirm that the connection page shows the desktop as online. If the wrong workstation is paired, create a new UltraTax CS connection and select the workstation that runs UltraTax CS. ### Client sync fails or a client is missing Confirm that **Data folder** on the UltraTax CS connection page points to the current UltraTax client-data folder. For tax year 2025, the usual location is `C:\WinCSI\UT25DATA`. Save the folder, then click **Sync Clients** again. Run another sync whenever clients are added or changed in UltraTax CS. ### Return data is not reading or entering correctly Confirm that the data folder on the connection page matches the folder where UltraTax CS stores the client's files. Also close the client in UltraTax CS before Filed attempts to read or write the return. An open client can prevent Filed from accessing it. ## Frequently asked questions **Do I need to give Filed my Thomson Reuters username, password, or two-factor secret?** No. The current standard connection pairs Filed with the Windows workstation running UltraTax CS and does not request those credentials. **How do I keep my UltraTax client list in sync with Filed?** Open the UltraTax CS connection page and click **Sync Clients**. Run another sync whenever clients are added or changed in UltraTax CS. If you use Virtual Office, Rightworks, another hosted environment, or cannot use direct desktop sync, export a new Client Listing Report and upload it to Filed instead. **Do I need the Filed Desktop app if I use Thomson Reuters Virtual Office?** No. Virtual Office and Rightworks users can export and upload the client list manually, then use backup files to move each client's return data into and out of Filed. **What happens to my original UltraTax return after Filed enters data?** Filed packages a backup of the return before data entry. You can download the pre-entry snapshot from the **Output** tab under **View Backups** if you need to restore the original state. **Can I use the backup-file workflow if I have the Desktop app?** The backup-file workflow is intended for environments where the Desktop app cannot be installed. If the Desktop app is available, the standard connected workflow is simpler and recommended. ## Capabilities ### Review return and client information Use Filed to retrieve the client and return information available through this connection. This gives preparers and reviewers a starting point without manually entering the same information again. ### Prepare approved data-entry work When **Write** access is enabled, Filed can prepare and run approved data-entry work in the connected tax environment. Review the return in UltraTax CS before filing. ### Keep the connection operational Use the connection page to confirm the paired desktop is online, update the UltraTax data folder, sync the client list, and recover from a disconnected desktop session. # Backing up a client If you use Thomson Reuters Virtual Office, Rightworks, or the backup-file workflow, you exchange UltraTax backup ZIP files with Filed instead of using the Desktop app. This guide covers: 1. **How to get the backup ZIP** from UltraTax CS (File > Backup). 2. **How to upload the backup** to Filed to start tax prep. > To import a backup back into UltraTax CS after Filed finishes data entry, see [Restoring a backup into UltraTax CS](/reference/plugins/integrations/tax-software/ultratax-cs/restoring-a-backup-into-ultratax-cs). {% embed url="" %} *** ## 1. Getting the backup ZIP from UltraTax CS Use **File > Backup** to export a client's return data as a ZIP file. ### Open the Backup dialog In UltraTax CS, click **File** in the menu bar, then click **Backup...** from the dropdown menu.
UltraTax CS File menu with Backup highlighted

Open the File menu and select Backup.

### Select the client The Backup dialog opens. The client appears in the **Available** list on the left. Click the client row to highlight it, then click **Select >** to move it to the **Selected** list on the right. Set the **Backup location** on the right side to the folder where you want to save the ZIP file (for example, `C:\Users\taxprepadmin\Desktop\backups`). You can click **Modify Backup Location...** to change it.
Backup dialog with client in Available list

Select the client from the Available list and set the backup location.

### Click Backup With the client in the **Selected** list and the backup location set, click the **Backup** button at the bottom right. UltraTax creates the backup ZIP file in the location you chose.
Client in Selected list, ready to backup

Click Backup to export the client's return as a ZIP file.

*** ## 2. Uploading the backup to Filed Once you have the backup ZIP from UltraTax CS, upload it to Filed to start tax prep and data entry. ### How to get there 1. On the **Clients** page, select a client. 2. Click on the **Tax Prep** card. 3. The **initiate page** appears — this is where you upload the backup and configure the run. ### Upload the backup on the initiate page 4. Under **Connect a tax software**, confirm **UltraTax CS** is selected. 5. Under **Identify the client in the tax software** (optional), select the client from the **Software client id** dropdown if you want Filed to match the client automatically. 6. Under **Upload last year's backup**, drag and drop the backup ZIP file into the upload area, or click **Browse files** to select it. ZIP files are supported. 7. Click **Continue** to start tax prep.
Filed initiate tax prep page with backup upload area

Upload the UltraTax backup ZIP on the initiate page to start data entry.

Filed will restore the backup on the VM before data entry starts. Once AI preparation is complete, you receive a notification and can download the completed backup from the client's Output tab under **View Backups**. To import that backup back into UltraTax CS, see [Restoring a backup into UltraTax CS](/reference/plugins/integrations/tax-software/ultratax-cs/restoring-a-backup-into-ultratax-cs). *** ## Tips * **Backup vs. Restore.** Backup (File > Backup) exports data out of UltraTax as a ZIP. Restore (File > Restore) imports a ZIP back into UltraTax. * **Entity filter.** The Backup dialog has entity checkboxes at the bottom (1040, 1120, 1065, 1041, etc.). Make sure the correct entity type is checked so your client appears in the Available list. # Restoring a backup Use **File > Restore** to import a backup ZIP file back into UltraTax CS — for example, after Filed completes data entry and you download the result. This guide covers the restore side of the backup-file workflow. To create a backup ZIP or upload one to Filed, see [Backing up a client in UltraTax CS](/reference/plugins/integrations/tax-software/ultratax-cs/backing-up-a-client-in-ultratax-cs). *** ## Open the Restore dialog In UltraTax CS, click **File** in the menu bar, then click **Restore...** from the dropdown menu.
UltraTax CS File menu with Restore highlighted

Open the File menu and select Restore.

## Set the backup location and select the client The Restore dialog opens. On the right side under **Backup data**, click **Change Backup Location...** and navigate to the folder where you saved the backup file. Once the backup location is set, the client appears in the **Available** list on the left. Click the client row to highlight it, then click **Select >** to move it to the **Selected** list on the right.
Restore dialog showing client in Available list

The client appears in the Available list after setting the backup location.

## Confirm the client is in the Selected list Verify the client now appears in the **Selected** column on the right side of the dialog. The Available count should show 0 and Selected should show 1.
Client moved to Selected list

The client has been moved to the Selected list, ready to restore.

## Click Restore Click the **Restore** button at the bottom right of the dialog. If UltraTax prompts you to confirm overwriting existing data for this client, click **Yes** (or **Yes to All** if restoring multiple clients).
Restore dialog ready to restore

Click Restore to complete the process.

The restore completes and the client's return now contains the imported data. Open the client in UltraTax CS to review. *** ## Tips * **Backup vs. Restore.** Backup (File > Backup) exports data out of UltraTax as a ZIP. Restore (File > Restore) imports a ZIP back into UltraTax. * **Entity filter.** The Restore dialog has entity checkboxes at the bottom (1040, 1120, 1065, 1041, etc.). Make sure the correct entity type is checked so your client appears in the Available list. * **Restore overwrites existing data.** If the client already has data in UltraTax CS, the restore replaces it with the backup contents. If you want to keep the current state, create a backup first before restoring. # Lacerte With this integration connected, Filed **AI Tax Prep** can use the available Lacerte data as part of the tax-preparation workflow. You can also use the connection in Filed **Chat** and **Routines**. When **Write** access is enabled, Filed can complete approved data-entry work in Lacerte; review the return in Lacerte before filing or finalizing the work. 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. **Best practice:** Every user onboarded into Filed installs the copy of Filed desktop app just like the tax softwares. Filed app needs to work on the same machine where the tax software is installed. Every user gets their own Filed app installation. ## 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. ## Capabilities ### Review return and client information Use Filed to retrieve the client and return information available through this tax-software connection. This gives preparers and reviewers a starting point without manually re-keying the same information. ### Prepare approved data-entry work When **Write** access is enabled, Filed can prepare and run approved data-entry work in the connected tax environment. Use this for repeatable preparation workflows, then review the return in the tax software before filing. ### Keep the connection operational Use the connection to validate access, recover from a disconnected desktop session, and keep the firm’s tax-work workflow linked to the correct environment. # Setting up the Lacerte SDK Use this guide to enable Lacerte client-list syncing and data entry on a Windows computer running Filed Desktop. The setup normally takes about 15 minutes and requires Windows administrator access. ## Before you start Confirm that: * Lacerte 2025 is installed. * Lacerte opens normally and displays the firm's clients. * Filed Desktop is installed on the same Windows computer. * You have Windows administrator access. * The following installer is saved on the Windows Desktop: ``` Lacertetax-SDK-Installer-64-1.0.0.501.msi ``` ## 1. Close Lacerte and Filed 1. Ask the user to save their work. 2. Close Lacerte completely. 3. Close Filed Desktop completely. 4. Open Task Manager by pressing `Ctrl` + `Shift` + `Esc`. 5. Confirm that no Lacerte or Filed applications remain under **Processes**. {% hint style="warning" %} Do not install the SDK while Lacerte is running. An open Lacerte process can prevent required SDK components from being registered correctly, even if the installation log reports success. {% endhint %} ## 2. Remove an existing Lacerte SDK 1. Open **Windows Settings**. 2. Select **Apps > Installed apps**. 3. Search for `Lacerte`. 4. If **Lacerte SDK (64-bit)** appears, uninstall it. 5. Restart the computer. If the SDK is not listed, continue to the next step without uninstalling it. ## 3. Open PowerShell as an administrator 1. Open the Windows Start menu. 2. Search for `PowerShell`. 3. Right-click **Windows PowerShell**. 4. Select **Run as administrator**. 5. Approve the Windows security prompt. ## 4. Install and check the SDK Copy the entire block below, paste it into PowerShell, and press `Enter`: ```powershell $msi = "$env:USERPROFILE\Desktop\Lacertetax-SDK-Installer-64-1.0.0.501.msi" $log = "$env:USERPROFILE\Desktop\lacerte-sdk-install.log" if (!(Test-Path $msi)) { Write-Host "FAIL: The installer was not found on the Desktop." ` -ForegroundColor Red } else { Write-Host "Installing Lacerte SDK. Please wait..." $process = Start-Process msiexec.exe ` -ArgumentList @('/i', "`"$msi`"", '/L*v', "`"$log`"") ` -Wait ` -PassThru if (!(Test-Path $log)) { Write-Host "FAIL: The installation log was not created." ` -ForegroundColor Red } else { $success = Select-String $log ` -SimpleMatch "Installation success or error status: 0" ` -Quiet $errors = Select-String $log ` -Pattern "Return value 3|Failing with hr=|80070005|Access is denied" ` -Quiet if (($process.ExitCode -in @(0, 1641, 3010)) -and $success -and !$errors) { Write-Host "PASS: Lacerte SDK installed successfully. Restart the computer." ` -ForegroundColor Green } else { Write-Host "FAIL: Installation did not complete cleanly. Send the log to Filed Support." ` -ForegroundColor Red } } } ``` The Lacerte SDK may not display an installer window, progress bar, or completion message. This is expected. Keep PowerShell open and wait for it to display a green `PASS` or red `FAIL` result. If the result is `FAIL`, stop and send the following file from the Desktop to Filed Support: ``` lacerte-sdk-install.log ``` ## 5. Restart the computer If the installation result was `PASS`, restart Windows before opening Lacerte or Filed Desktop. ## 6. Verify the installation after restarting Open PowerShell, copy the entire block below, and press `Enter`: ```powershell $dll = 'C:\Program Files (x86)\Common Files\Lacerte Shared\LacerteSDK\ClientDataAccess2025.dll' $clsid = 'Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{999EBD1D-666C-48F9-8E81-47249EDBF8FC}' $appId = 'Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\AppID\{999EBD1D-666C-48F9-8E81-47249EDBF8FC}' if ((Test-Path $dll) -and (Test-Path $clsid) -and (Test-Path $appId)) { Write-Host "PASS: Lacerte SDK is installed and registered correctly." ` -ForegroundColor Green } else { Write-Host "FAIL: Lacerte SDK verification failed." ` -ForegroundColor Red } ``` The expected result is: ``` PASS: Lacerte SDK is installed and registered correctly. ``` {% hint style="info" %} The `Program Files (x86)` and `WOW6432Node` names are expected locations used by Intuit's official installer. Do not install a different SDK because of these names. {% endhint %} ## 7. Sync the client list in Filed 1. Open ProWork Desktop on the computer running Lacerte and confirm that it is connected. 2. Open Filed in your web browser and go to **Plugins**. 3. Open the **Lacerte** integration. 4. Under **Your connections** or **Shared connections**, select the Lacerte connection you set up. 5. In the **Data folder** section, confirm that Filed is using the correct Lacerte data folder. Filed may detect the folder automatically when Lacerte is installed on a local drive. 6. In the **Client list** section, click **Sync Clients**. 7. Keep ProWork Desktop open while the button displays **Syncing...**. 8. Confirm that the Lacerte clients appear in the **Client list** section when the sync finishes. Clicking **Sync Clients** in Filed sends a **List Clients** action to the paired ProWork Desktop app. You do not need to start this action manually in the desktop app. ## If Sync Clients still fails Send the following information to Filed Support: * A screenshot of the sync error on the Lacerte connection page in Filed. * The `lacerte-sdk-install.log` file from the Windows Desktop. * A screenshot of the post-restart verification result. * The configured Lacerte data-folder path. * Confirmation that ProWork Desktop was open and connected during the sync. * Confirmation that the clients appear normally inside Lacerte. Do not repeatedly reinstall the SDK before the installation log has been reviewed. # Drake With this integration connected, Filed **AI Tax Prep** can use the available Drake Tax data as part of the tax-preparation workflow. You can also use the connection in Filed **Chat** and **Routines**. When **Write** access is enabled, Filed can complete approved data-entry work in Drake Tax; review the return in Drake Tax before filing or finalizing the work. Filed integrates with Drake Tax through two paths: the standard workflow uses the Prowork App installed on a Windows workstation that runs Drake Tax, and the backup-file workflow serves firms using Rightworks hosted environments where the Prowork App cannot be installed. ## What this integration does Filed supports automated data entry for Drake Tax: after AI preparation is complete, Filed enters the finished data directly into the client's Drake return on the connected workstation. Filed can also sync your client list from Drake so it can match prepared returns to the right clients and let you search and manage them in Filed. Return data reading for Drake Tax is a planned capability and is not yet available. For current-season use, source documents and a Drake backup file are uploaded to Filed manually, and the completed backup is restored into Drake once preparation is done. ## Prerequisites * Drake Tax installed on a Windows workstation (standard workflow), or access to a Rightworks-hosted Drake environment. * Admin access to Drake Tax to create and restore backup files. * For the standard workflow: the Prowork App, available to download during the connection setup flow in Filed. * An always-on Windows machine is recommended to keep the Prowork App connection stable. **Best practice:** Every user onboarded into Filed installs the copy of Filed desktop app just like the tax softwares. Filed app needs to work on the same machine where the tax software is installed. Every user gets their own Filed app installation. ## Connecting Drake to Filed To link Drake Tax, navigate to **Plugins & integrations**, select **Drake**, download and install the Prowork App on the Drake workstation, then sign in with your Connection ID and Password, point it at the Drake data folder, and activate the connection. [Open the Drake connection walkthrough](https://studio.saltfish.ai/demo-share/demo_1783955587065_l5k0vvbps) The Prowork App can be installed on more than one workstation. If the machine running the app restarts or the app closes, reopen it and sign in before Filed's next sync. ## Syncing clients from Drake Once Drake is connected, sync your client list so Filed can match prepared returns to the right clients and let you quickly search and manage clients in Filed. [Open the client-sync walkthrough](https://studio.saltfish.ai/demo-share/demo_1783955935781_1ucccv57b) ## Tax prep workflow - standard (with Prowork App) Once the Prowork App is connected, open the client in Filed and click Start Tax Prep. Provide the client's source documents and prior-year return. Filed's AI prepares the return and, when complete, enters the finished data directly into the client's Drake return on the connected workstation. Review the return in Drake and finalize before filing. ## Tax prep workflow - Rightworks (without Prowork App) Rightworks is a hosted environment where the Prowork App cannot be installed. For these firms, you exchange Drake backup files manually. **Part 1 - Create and upload a Drake backup:** **Part 2 - AI preparation runs:** Filed prepares the return using the uploaded backup and source documents. When preparation is complete, you receive an email and in-app notification and the status updates to "Data Entry Completed." **Part 3 - Download and restore in Drake:** **Rolling back to the original version:** If you need the return as it was before Filed's preparation, download the "Sync by Filed" version from the backups list (the earliest entry, shown at the bottom of the list). ## Troubleshooting ### Prowork App disconnects or connection goes inactive The most common cause is that the machine restarted, the user logged out, or a network interruption caused the app to go offline. Reopen the Prowork App on the Drake workstation, re-enter credentials if prompted, and verify that the connection shows "Connection active." Setting the machine as always-on reduces the frequency of this issue. ### Backup file won't import into Drake * Make sure the file is extracted and unzipped before attempting the import. * Confirm the data location selected in Drake matches where the backup file was saved. * If Drake warns that the client already exists, click Yes to overwrite - this is the expected prompt. * If Drake asks whether to open in data entry, click Yes. ### Data entry errors or missing fields after restore Review the return in Drake after restore to verify all fields are populated correctly. If specific fields are incorrect, correct them manually in Drake. If data entry failed entirely, re-download the "Prepared by Filed" backup and attempt the restore again. ## Frequently asked questions **Can I use Drake Tax if my firm uses Rightworks?** Yes. Use the backup-file workflow described above. **Do I need the Prowork App if I use Rightworks?** No. The backup-file workflow requires no Prowork App installation. **What is the difference between the "Prepared by Filed" and "Sync by Filed" backup versions?** "Prepared by Filed" is the completed backup after AI preparation and data entry. "Sync by Filed" is the earliest backup, capturing the return as it was when it was first synced or uploaded to Filed. Use "Sync by Filed" to roll back to the original state. **Can I run multiple Drake backups for the same client?** Yes. Each time you upload a backup for a client, it becomes the version Filed uses for the next preparation run. Prior uploads are retained in the backups list. **What if a new client was not rolled over from the prior year in Drake?** Create the client in Drake first, then export a backup to upload to Filed. Filed cannot prepare a return without a Drake backup that contains a valid client record. ## Capabilities ### Review return and client information Use Filed to retrieve the client and return information available through this tax-software connection. This gives preparers and reviewers a starting point without manually re-keying the same information. ### Prepare approved data-entry work When **Write** access is enabled, Filed can prepare and run approved data-entry work in the connected tax environment. Use this for repeatable preparation workflows, then review the return in the tax software before filing. ### Keep the connection operational Use the connection to validate access, recover from a disconnected desktop session, and keep the firm’s tax-work workflow linked to the correct environment. # GoSystem Tax RS With this integration connected, Filed **AI Tax Prep** can use the available GoSystem Tax RS data as part of the tax-preparation workflow. You can also use the connection in Filed **Chat** and **Routines**. When **Write** access is enabled, Filed can complete approved data-entry work in GoSystem Tax RS; review the return in GoSystem Tax RS before filing or finalizing the work. ## What you need * A GoSystem Tax RS user with access to the correct firm, engagement, client, and return years. * The appropriate production or sandbox environment selected before you authorize. ## Connect GoSystem Tax RS 1. Select **GoSystem Tax RS** in Filed and name the connection for the firm environment. 2. Sign in with the GoSystem user that has the intended access. 3. Approve the provider authorization, then return to Filed. 4. Wait for the connection to verify before using it in a workflow. ## Verify and troubleshoot If the intended clients are unavailable, ask the GoSystem administrator to review product entitlements, security groups, and tax-year access. Use a dedicated firm account instead of sharing credentials between preparers. ## Capabilities ### Review return and client information Use Filed to retrieve the client and return information available through this tax-software connection. This gives preparers and reviewers a starting point without manually re-keying the same information. ### Prepare approved data-entry work When **Write** access is enabled, Filed can prepare and run approved data-entry work in the connected tax environment. Use this for repeatable preparation workflows, then review the return in the tax software before filing. ### Keep the connection operational Use the connection to validate access, recover from a disconnected desktop session, and keep the firm’s tax-work workflow linked to the correct environment. # ProConnect Tax With this integration connected, Filed **AI Tax Prep** can use the available ProConnect Tax data as part of the tax-preparation workflow. You can also use the connection in Filed **Chat** and **Routines**. When **Write** access is enabled, Filed can complete approved data-entry work in ProConnect Tax; review the return in ProConnect Tax before filing or finalizing the work. Filed integrates with Intuit ProConnect as a cloud connection - no software needs to be installed on firm workstations. Filed accesses your ProConnect account through a dedicated user account added to your firm's ProConnect subscription, which allows it to sync the client roster, read existing return data for AI preparation, and write completed data entry back into returns. ## What this integration does Filed supports three capabilities with ProConnect: * **Sync client list** - Filed imports your full ProConnect client roster so it can match prepared returns to the right clients. * **Read return data** - Filed reads a client's current return data from ProConnect to use as a starting point for AI preparation. * **Enter return data** - After AI preparation is complete, Filed writes the finished data entry into the client's ProConnect return using the dedicated Filed user credentials. ## Prerequisites * A ProConnect Tax account with administrator access. * A current-year tax return already created in ProConnect for at least one client. ProConnect requires an active return before the Filed connection can be verified. * The phone number associated with your ProConnect account, for 2FA verification during setup. ## Connecting ProConnect to Filed The connection is established in three phases: setting up a Filed user account in ProConnect, adding that user to your ProConnect account, and completing 2FA verification in Filed. {% embed url="" %} **Phase 1 - Filed account setup:** **Phase 2 - ProConnect account configuration:** Sign into ProConnect as an administrator. Navigate to Settings in the top-right corner, then Manage and invite users, then Add user. Enter the following: * First name: Filed * Last name: User * Email: paste the unique email address generated by Filed in Phase 1 Assign the Advanced tax access role. Click Edit client access and select the checkbox for all clients. Click Send invite. If the ProConnect subscription does not allow adding an Advanced tax access user, a standard all-access user works as a fallback. However, with standard access, you will need to manually update the Filed user's client access in ProConnect each time a new client is added during tax season. **Phase 3 - Verify in Filed:** Return to Filed and click "I've sent the invitation." Enter the 6-digit 2FA code sent to the phone number provided in Phase 1. Click Verify Code. 2FA may be requested more than once during initial verification - this is expected. Once verified, the ProConnect connection becomes active. ## Tax prep workflow Once the connection is active, Filed syncs the ProConnect client list so clients appear in Filed's workspace. When you start tax preparation for a client, Filed reads the client's existing return data from ProConnect. After AI preparation is complete, Filed enters the finished data into the client's ProConnect return using the dedicated Filed user. Review the return in ProConnect and finalize before filing. ## Managing client access If the Filed user was added with Advanced tax access (all clients), no further action is needed as new clients are created in ProConnect. If the Filed user was added with standard access, you must edit the Filed user in ProConnect each time a new client is added and explicitly grant access to that client. Navigate to Settings, Manage and invite users, find the Filed User entry, click Edit client access, and add the new client. If the Filed user's access is revoked or the email address changes, the connection must be re-established from the Connect tab in Filed. ## Troubleshooting ### Invitation not received or ProConnect user setup fails The invitation email goes to Filed's system - you will not receive it in your inbox, and no action is needed after clicking Send invite. If ProConnect returns an error when adding the user, confirm the email address was copied exactly from Filed without extra spaces or characters. If Advanced tax access is not available on your ProConnect plan, add a standard all-access user instead. ### 2FA verification fails or times out The 6-digit code is sent to the phone number entered in Phase 1 and expires quickly. Request a new code from Filed and enter it promptly. 2FA may be requested more than once during initial verification - this is normal. Confirm the phone number is correct before retrying. ### Filed cannot read or enter data for a specific client This usually means the Filed user in ProConnect does not have access to that client. In ProConnect, go to Settings, Manage and invite users, find the Filed User, click Edit client access, and add the missing client. If the Filed user already has all-clients access, confirm that a current-year tax return for the client exists in ProConnect. ### Connection becomes inactive after setup ProConnect connections can become inactive if the Filed user's password or access is changed in ProConnect, or if the invitation link expired before verification was completed. Disconnect and reconnect ProConnect from the Connect tab in Filed, starting the three-phase flow again. ## Frequently asked questions **Does Filed have access to my entire ProConnect account?** Filed accesses ProConnect only through the dedicated Filed user account you create. Its access is limited to what you grant that user - all clients if you selected all-clients access, or only the clients you explicitly add if you used standard access. **What happens to the Filed user in ProConnect when I disconnect the integration?** The Filed user remains in your ProConnect account. You can remove it manually through Settings, Manage and invite users in ProConnect if you no longer want it there. **Can I connect multiple ProConnect accounts to one Filed workspace?** **Do I need to create the current-year return before connecting?** Yes. ProConnect requires at least one active return to exist before the Filed connection can be verified during setup. **How does Filed handle newly added clients in ProConnect?** With all-clients Advanced tax access, Filed sees new clients automatically on the next sync. With standard access, you must update the Filed user's client access in ProConnect for each new client. **What role level does the Filed user need in ProConnect?** Advanced tax access is recommended because it grants access to all current and future clients without manual updates. A standard all-access user also works but requires you to update client access manually whenever a new client is added. ## Capabilities ### Review return and client information Use Filed to retrieve the client and return information available through this tax-software connection. This gives preparers and reviewers a starting point without manually re-keying the same information. ### Prepare approved data-entry work When **Write** access is enabled, Filed can prepare and run approved data-entry work in the connected tax environment. Use this for repeatable preparation workflows, then review the return in the tax software before filing. ### Keep the connection operational Use the connection to validate access, recover from a disconnected desktop session, and keep the firm’s tax-work workflow linked to the correct environment. # Tax prep and data entry Select the exact ProConnect client and 2025 individual return, run AI Tax Prep, and review verified data-entry results. ProConnect tax prep starts from an existing return. Filed reads that return in the signed-in ProConnect browser session, reconciles it with the client's source documents, and writes only the planned changes back to the same return. ## Before you start Confirm that: * ProConnect shows as **Connected** in Filed. * The latest client sync has finished. * The dedicated Filed user can access the client. * The client has an eligible **2025 individual (`IND`) return** in ProConnect. * The client's source documents have been uploaded to Filed. The client name in Filed can differ from the taxpayer name in ProConnect. Treat the ProConnect client and return shown in the selector as the write target and verify both before continuing. ## Select the exact return 1. Open the client in Filed and start **AI Tax Prep**. 2. In **Connect a tax software**, select the active **Intuit ProConnect Tax** connection. 3. Expand **Identify the client in the tax software** and select the matching ProConnect client. 4. Under **2025 individual return**, select the exact return you want Filed to prepare. 5. Turn on **Enter the return into the tax software** if data entry should run automatically after reconciliation. 6. Review any selected protocols and click **Run tax prep**. If the selected client has one eligible return, Filed selects it automatically. If several eligible returns have the same display name, Filed labels them **Return 1**, **Return 2**, and so on. Return IDs remain internal and are not shown as the primary label. If the return selector says that no eligible return was found, [sync ProConnect](broken://pages/gcXKaJzI33DxinkjkXhc#sync-the-client-list) and verify the return is a 2025 individual return. Filed does not substitute another return or fuzzy-match by client name. ## What happens during the run ### 1. Existing-return read and backup Filed signs in to ProConnect and reads the selected return across the supported input screens. This initial read includes prior-year information carried in the return and current-year data already entered by a human preparer. The complete read serves two purposes: * the existing-return context used during reconciliation; and * the immutable **Before data entry** recovery snapshot for this run. There is no `.DAT` import or export in the ProConnect workflow. ### 2. Extraction and reconciliation Filed extracts the uploaded source documents and compares them with the existing ProConnect return. Reconciliation decides whether each item should create a new row, update an existing field, remain unchanged, or be sent for human review. The resulting data-entry plan is tied to the selected ProConnect client and return. Filed validates that target before dispatch and validates the complete payload again inside the authenticated browser before changing the return. ### 3. Data entry and verification Filed applies the plan through ProConnect's input screens using read-modify-write operations. It then reads the affected values back from ProConnect and compares them with the planned values. The result appears as: * **Confirmed** - the value read back from ProConnect matches the planned value. * **Flagged** - the value needs human review because the written and verified values differ or the result is uncertain. * **Pending** - verification has not resolved the field yet. * **Manual** - Filed did not enter the field automatically. In the Binder, each ProConnect screen is shown with a readable form prefix, such as **W-2 · s11**. Open **Technical details** only when you need the underlying screen, field, or operation identity. ### 4. Draft return PDF After data entry, Filed asks ProConnect to print the return. When ProConnect produces the PDF, the AI Tax Prep summary shows a **Draft return** preview with an **Open** button. The same PDF can be passed directly to AI Review. ## Run data entry later from the Binder If you ran extraction and reconciliation without enabling data entry: 1. Open the client's **Binder > Forms**. 2. Review the planned forms and source references. 3. Click **Send to data entry**. 4. Confirm the selected ProConnect return and start the entry run. Filed reuses the exact client and return saved with the tax-prep run. If the saved return is no longer eligible, select a current 2025 individual return before continuing. ## Review the completed work From the AI Tax Prep summary: * Check the Confirmed, Flagged, Pending, and Manual totals. * Open a form to compare **Planned**, **In ProConnect**, and **Result** values. * Use source links in the Binder to verify values against the uploaded document. * Preview or open the draft return PDF when available. * Open **Backups** to see the snapshots associated with the run. See [ProConnect backups and recovery](/reference/plugins/integrations/tax-software/proconnect-tax/proconnect-backup-and-recovery) before requesting a rollback. # Backups and recovery How Filed captures ProConnect return snapshots and how support can reverse an exact data-entry run without overwriting newer preparer edits. 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. # Practice management These connections help Filed use work, clients, and task assignments already managed by your firm. Start with read-only access unless Filed should create or update tasks or records. * [Asana](/reference/plugins/integrations/practice-management/asana) * [Karbon](/reference/plugins/integrations/practice-management/karbon) * [ClickUp](/reference/plugins/integrations/practice-management/clickup) * [monday.com](/reference/plugins/integrations/practice-management/monday-com) * [Trello](/reference/plugins/integrations/practice-management/trello) # Asana With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Asana and, when **Write** access is enabled, perform approved actions in Asana. This integration to Filed is connected via our integration provider [Composio](https://composio.dev/) ## Connect Asana 1. Create an **Asana** connection and name it for the firm team or workspace. 2. Sign in with an Asana user who belongs to the required workspace, teams, and projects. 3. Approve the authorization request and return to Filed. 4. Verify with a non-sensitive project before enabling write access. If a project is missing, add the authorized Asana user to that project. Private projects remain unavailable until that user has membership. ## Verify the connection After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm workspace, team, and project membership. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow. ## Manage permissions Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying Asana data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change. ## Troubleshooting **The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has workspace, team, and project membership. **The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review workspace, team, and project membership, then reconnect if the account or environment was wrong. **The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding Asana information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Asana data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Summarize the Asana information for \[client name] for \[date range].” * “Find items in Asana that need review before \[deadline].” * “With write access enabled, prepare the approved Asana update and show the proposed changes first.” ## Capabilities ### See work and deadlines in one place Use Filed to retrieve the projects, tasks, assignments, and due dates available to the connected practice-management account. This gives Chat and Routines firm context for client work. ### Create or update approved work When **Write** access is enabled, Filed can support creating and updating approved tasks or work items. Use this for consistent follow-up and assignment workflows after your firm has reviewed the outcome. ### Work within existing project access Filed can only use the workspaces, teams, projects, and boards the authorized user can access. Manage that scope in the provider rather than sharing a broader login. # Karbon Connect Karbon to import the clients, work items, and documents your team uses for tax preparation. Karbon remains your system of record, while Filed keeps the selected work and documents in sync. ## Before you start A Karbon administrator should complete this setup. You need access to **Settings** and **API Applications** in Karbon. If these options are not available, ask a Karbon administrator to complete the Karbon steps or grant you the required permissions. ## Sign in to Karbon 1. Open [Karbon](https://app.karbonhq.com). 2. Click **Continue with Google**. 3. Choose the Google account associated with your Karbon workspace. If you already have an active Karbon session, Karbon opens your workspace without showing the sign-in screen. ## Open the Filed API application 1. Open the main menu in Karbon. 2. Click **Settings**. 3. Under **Integrations and Tools**, click **API Applications**. 4. Find the Filed application. 5. Click **Manage**. The exact Filed application name can vary by environment. ![Karbon Connected Apps page with the API Applications tab selected and a Filed application](https://assets.apps.filed.com/walkthroughs/connect-karbon/image1.webp) If you cannot see **Settings** or **API Applications**, confirm that you are signed in to the correct Karbon account and have administrator access. ## Copy the Karbon credentials The Filed API application provides two credentials: * **Application ID:** The API bearer token that identifies the Filed application. * **Access Key:** The JWT access key that authorizes the connection to your Karbon account. Click **Copy** next to each field. Keep this page open until the connection is verified in Filed. ![Karbon API Authentication page with masked Application ID and Access Key fields](https://assets.apps.filed.com/walkthroughs/connect-karbon/image2.webp) > **Important:** The Application ID and Access Key grant account-level access to Karbon data. Treat both values as secrets. Do not send them by email, paste them into chat, or store them in a shared document. ## Verify the connection in Filed 1. Return to Filed. 2. Open **Connect** from the left navigation. 3. Click **Practice Management**. 4. Find **Karbon** and click **Connect**. 5. Paste the Karbon **Application ID** and **Access Key** into the matching fields. 6. Click **Verify connection**. Filed checks the credentials against Karbon. If verification fails, copy both values again from the same Karbon API application. Confirm that no spaces were added before or after either value. ## Troubleshooting ### The Filed API application is missing in Karbon Confirm that you are in the correct Karbon account. If the application is still missing, contact your Filed account manager before creating a different API application. ### Karbon verification fails in Filed Copy the Application ID and Access Key again from \*\*Settings > API Applications > Filed > Manage\*\*. Make sure each value is pasted into its matching field. ### Clients or work are missing after setup Review the work types selected during configuration. Filed only imports work that matches the selected Karbon work types. ### The Access Key was rotated Rotating the Access Key immediately invalidates the previous key. Open the Karbon connection in Filed, replace the old Access Key, and verify the connection again. # ClickUp With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Clickup and, when **Write** access is enabled, perform approved actions in Clickup. This integration to Filed is connected via our integration provider [Composio](https://composio.dev/) ## Connect ClickUp 1. Name the connection for the ClickUp workspace. 2. Authorize with a user who can access the required Workspace, Space, Folder, and Lists. 3. Return to Filed and wait for verification. 4. Keep write access off when Filed should only read task data. If tasks are unavailable, confirm that the connected user can access the list and that it belongs to the selected ClickUp workspace. ## Verify the connection After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm Workspace, Space, Folder, and List access. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow. ## Manage permissions Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying ClickUp data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change. ## Troubleshooting **The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has Workspace, Space, Folder, and List access. **The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review Workspace, Space, Folder, and List access, then reconnect if the account or environment was wrong. **The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding ClickUp information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with ClickUp data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Summarize the Clickup information for \[client name] for \[date range].” * “Find items in Clickup that need review before \[deadline].” * “With write access enabled, prepare the approved Clickup update and show the proposed changes first.” ## Capabilities ### See work and deadlines in one place Use Filed to retrieve the projects, tasks, assignments, and due dates available to the connected practice-management account. This gives Chat and Routines firm context for client work. ### Create or update approved work When **Write** access is enabled, Filed can support creating and updating approved tasks or work items. Use this for consistent follow-up and assignment workflows after your firm has reviewed the outcome. ### Work within existing project access Filed can only use the workspaces, teams, projects, and boards the authorized user can access. Manage that scope in the provider rather than sharing a broader login. # monday.com With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Monday Com and, when **Write** access is enabled, perform approved actions in Monday Com. This integration to Filed is connected via our integration provider [Composio](https://composio.dev/) ## Connect monday.com 1. Name the connection for the correct monday.com account or team. 2. Sign in with a user who can open the required boards and workspaces. 3. Approve authorization and return to Filed for verification. 4. Enable write only when Filed may create or update board items. If a board is missing, share it with the connected user instead of using a broader account than necessary. ## Verify the connection After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm workspace and board access. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow. ## Manage permissions Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying monday.com data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change. ## Troubleshooting **The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has workspace and board access. **The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review workspace and board access, then reconnect if the account or environment was wrong. **The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding monday.com information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with monday.com data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Summarize the Monday Com information for \[client name] for \[date range].” * “Find items in Monday Com that need review before \[deadline].” * “With write access enabled, prepare the approved Monday Com update and show the proposed changes first.” ## Capabilities ### See work and deadlines in one place Use Filed to retrieve the projects, tasks, assignments, and due dates available to the connected practice-management account. This gives Chat and Routines firm context for client work. ### Create or update approved work When **Write** access is enabled, Filed can support creating and updating approved tasks or work items. Use this for consistent follow-up and assignment workflows after your firm has reviewed the outcome. ### Work within existing project access Filed can only use the workspaces, teams, projects, and boards the authorized user can access. Manage that scope in the provider rather than sharing a broader login. # Trello With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Trello and, when **Write** access is enabled, perform approved actions in Trello. This integration to Filed is connected via our integration provider [Composio](https://composio.dev/) ## Connect Trello 1. Name the connection for the intended Trello workspace or board group. 2. Sign in with a member of the required Workspace and boards. 3. Approve authorization and return to Filed. 4. Verify against a known board before enabling write access. If a board does not appear, make the authorized user a board member. Use a dedicated firm account for client-sensitive boards. ## Verify the connection After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm Workspace and board membership. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow. ## Manage permissions Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying Trello data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change. ## Troubleshooting **The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has Workspace and board membership. **The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review Workspace and board membership, then reconnect if the account or environment was wrong. **The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding Trello information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Trello data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Summarize the Trello information for \[client name] for \[date range].” * “Find items in Trello that need review before \[deadline].” * “With write access enabled, prepare the approved Trello update and show the proposed changes first.” ## Capabilities ### See work and deadlines in one place Use Filed to retrieve the projects, tasks, assignments, and due dates available to the connected practice-management account. This gives Chat and Routines firm context for client work. ### Create or update approved work When **Write** access is enabled, Filed can support creating and updating approved tasks or work items. Use this for consistent follow-up and assignment workflows after your firm has reviewed the outcome. ### Work within existing project access Filed can only use the workspaces, teams, projects, and boards the authorized user can access. Manage that scope in the provider rather than sharing a broader login. # Accounting & ERP Connect an accounting administrator or dedicated integration user with access only to the companies and records Filed needs. Keep write access disabled until your firm has approved posting or record changes. * [QuickBooks Online](/reference/plugins/integrations/accounting-and-erp/quickbooks-online) * [NetSuite](/reference/plugins/integrations/accounting-and-erp/netsuite) # QuickBooks Online With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from QuickBooks Online and, when **Write** access is enabled, perform approved actions in QuickBooks Online. This integration to Filed is connected via our integration provider [Composio](https://composio.dev/) ## What you need * An Intuit user with access to the intended QuickBooks Online company. * Approval before enabling write access for transactions, invoices, or other accounting records. ## Connect QuickBooks Online 1. Create a connection and name it for the QuickBooks company. 2. Sign in with the appropriate Intuit user and select the correct company when prompted. 3. Approve access, then return to Filed for verification. 4. Verify against a known company before allowing write actions. If the wrong company opens, cancel and reconnect with the correct Intuit account. If the company is missing, ask its QuickBooks administrator to grant the user access. ## Verify the connection After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm Intuit user and company access. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow. ## Manage permissions Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying QuickBooks Online data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change. ## Troubleshooting **The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has Intuit user and company access. **The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review Intuit user and company access, then reconnect if the account or environment was wrong. **The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding QuickBooks Online information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with QuickBooks Online data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Summarize the QuickBooks Online information for \[client name] for \[date range].” * “Find records in QuickBooks Online that need review before \[deadline].” * “With write access enabled, prepare the approved QuickBooks Online update and show the proposed changes first.” ## Capabilities ### Review financial records Use Filed to retrieve the accounting or ERP information available to the connected account. This is useful for reconciliation, tax preparation context, and review workflows. ### Prepare approved accounting changes When **Write** access is enabled, Filed can prepare or run approved updates supported by the provider. Use this only after validating the company, environment, and accounting policy involved. ### Keep production changes controlled Use a separate connection for production and sandbox environments where applicable. Turn off Write when the connection is used only for reporting or review. # NetSuite With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from NetSuite and, when **Write** access is enabled, perform approved actions in NetSuite. This integration to Filed is connected via our integration provider [Composio](https://composio.dev/) ## What you need * A NetSuite OAuth client ID, client secret, and account ID from your NetSuite administrator. * A NetSuite role that can access the records Filed should use. ## Connect NetSuite 1. Create the connection and enter the requested client ID, client secret, and account ID. An account ID may look like `1234567_SB1`. 2. Continue to NetSuite, sign in with the authorized user, and approve access. 3. Return to Filed and wait for the connection to verify. 4. Keep write access off until a test workflow succeeds. If authorization fails, verify the OAuth integration record, redirect URL, role permissions, and account ID with your NetSuite administrator. Never reuse another customer's OAuth credentials. ## Verify the connection After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm OAuth application, account ID, and role permissions. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow. ## Manage permissions Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying NetSuite data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change. ## Troubleshooting **The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has OAuth application, account ID, and role permissions. **The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review OAuth application, account ID, and role permissions, then reconnect if the account or environment was wrong. **The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding NetSuite information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with NetSuite data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Summarize the NetSuite information for \[client name] for \[date range].” * “Find records in NetSuite that need review before \[deadline].” * “With write access enabled, prepare the approved NetSuite update and show the proposed changes first.” ## Capabilities ### Review financial records Use Filed to retrieve the accounting or ERP information available to the connected account. This is useful for reconciliation, tax preparation context, and review workflows. ### Prepare approved accounting changes When **Write** access is enabled, Filed can prepare or run approved updates supported by the provider. Use this only after validating the company, environment, and accounting policy involved. ### Keep production changes controlled Use a separate connection for production and sandbox environments where applicable. Turn off Write when the connection is used only for reporting or review. # Document management Document connections can access only the files, folders, sites, and shares that the authorized user can already open. Connect the narrowest firm-managed account that has the client documents you need. * [Google Drive](/reference/plugins/integrations/document-management/google-drive) * [SharePoint](/reference/plugins/integrations/document-management/sharepoint) * [SmartVault](/reference/plugins/integrations/document-management/smartvault) * [Box](/reference/plugins/integrations/document-management/box) * [Dropbox](/reference/plugins/integrations/document-management/dropbox) * [OneDrive](/reference/plugins/integrations/document-management/onedrive) * [Egnyte](/reference/plugins/integrations/document-management/egnyte) # Google Drive Connect Google Drive to Filed and control which Drive content Filed can read or change. With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Google Drive and, when **Write** access is enabled, perform approved actions in Google Drive. Connect Google Drive when client source documents, workpapers, or completed deliverables live in Google Drive or a Google shared drive. Filed uses the permissions already assigned to the Google account you authorize; it does not gain access to content that account cannot open. ## Before you connect Choose the Google account deliberately. It should be a firm-managed account that can access the client folders and shared drives that your team expects Filed to use. Before starting, confirm the account can: * Open the relevant Google Drive folders and files in the browser. * Access any shared drives used for client work. * Create or edit files in those locations if you intend to allow write actions. * Complete your firm's Google Workspace sign-in and multi-factor authentication requirements. If your firm uses Google Workspace, ask an administrator whether the Filed Google OAuth application has been approved. Workspace policy can block a consent screen even when the user has access to the files. ## Create the connection 1. Go to **Plugins & integrations** and select **Google Drive**. 2. Give the connection a clear name. Include the team, entity, or Drive scope when useful, such as `Tax Team Shared Drive` or `Smith CPA Google Drive`. 3. Review the connection permissions: * **Read** is always enabled and allows Filed to retrieve information from the Drive content available to the authorized account. * **Write** is enabled by default. Clear it if Filed should only read documents. You can change this later in the connection settings. 4. Select **Continue** to open Google sign-in. ## Authorize Google 1. Sign in with the intended Google account. If the account chooser shows a personal account, choose **Use another account** instead of proceeding with the wrong identity. 2. Review the permissions Google displays. These permissions let Filed work with the Drive files available to the selected account. 3. Select **Allow** to complete authorization. 4. Return to Filed and wait for the connection status to change to **Active**. The Google account, Google Workspace policies, shared-drive membership, and individual folder sharing rules all continue to govern what the connection can access. ## Verify the connection After the connection is active, use a known non-sensitive client folder to verify that Filed can see the expected documents. If your workflow needs to create or organize files, test that behavior in a safe folder before enabling write access for production work. For shared drives, verify that the connected account is a member of the drive itself. A folder link alone is not always enough to grant access to all expected content. ## Manage write access Turn off **Write** in the connection settings to make the connection read-only. Filed can continue to retrieve information from authorized Drive content, but it cannot run capabilities that create, upload, move, rename, or delete Drive content. Use read-only access when Filed is used for document review, search, or context gathering. Enable write only when your firm has approved Filed to modify Drive data. ## Reconnect or remove the connection Use **Reconnect** when Google access was revoked, the account password or multi-factor setup changed, or the connection shows pending or failed. Reconnect with the same intended firm account unless your firm is intentionally changing the ownership of the connection. Use **Remove** only when the connection should no longer be available in Filed. Removing it does not delete any files from Google Drive. ## Troubleshooting ### Google blocks the consent screen Your Google Workspace administrator may need to approve the OAuth application or requested scopes. Send the administrator the exact message shown by Google; do not bypass the policy by connecting a personal Google account. ### The wrong Google account was authorized Remove the pending or active connection and create a new one. Sign out of Google first, or choose **Use another account** at the Google account picker. ### A shared drive or folder is missing Open the folder in Google Drive as the authorized user. If it is unavailable there, Filed cannot access it either. Add the user to the shared drive or share the folder with that account, then reconnect or retry the operation. ### Filed can read files but cannot change them Check the connection's **Write** setting first. If Write is enabled, confirm that the Google account has Editor-level access to the target folder and that the folder is not restricted by shared-drive policy. ### The connection becomes failed after working previously The Google authorization may have been revoked, the account may have lost access, or Workspace policy may have changed. Select **Reconnect**, complete Google authorization again, and verify access to a known folder. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding Google Drive information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Google Drive data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find the Google Drive folder for \[client name] and list the most recent source documents.” * “Summarize the tax documents in \[folder name] and flag anything that appears missing.” * “With write access enabled, create an approved folder structure for \[client name] and upload \[file name].” ## Capabilities ### Find and read client documents Use Filed to browse, search, and retrieve the files and folders available to the connected account. This is useful for gathering source documents, answering questions, and preparing a client file for review. ### Organize approved content When **Write** access is enabled, Filed can create folders and upload, move, rename, or update approved documents where the connected account has permission. Use this to keep client deliverables and workpapers in the agreed location. ### Preserve your provider’s access model Filed works within existing folder, site, shared-drive, or library permissions. Use the provider’s own sharing controls to decide which client content the connection can reach. # SharePoint Connect SharePoint to Filed and control which sites, libraries, and documents Filed can read or change. With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from SharePoint and, when **Write** access is enabled, perform approved actions in SharePoint. Connect SharePoint when client documents are stored in Microsoft 365 sites and document libraries. Filed can access only the SharePoint content that the Microsoft account you authorize can already open. Site membership, library permissions, sensitivity labels, conditional-access policies, and Microsoft 365 administrator controls remain in effect. ## Before you connect Use a firm-managed Microsoft 365 account with access to the specific SharePoint sites and document libraries your team intends to use. Confirm the account can: * Open the relevant SharePoint site and library in a browser. * View the client folders and files you expect Filed to use. * Create or edit files in those libraries if write actions will be enabled. * Complete your organization's Microsoft sign-in, multi-factor authentication, and conditional-access checks. For a Microsoft 365 tenant with strict app controls, ask a Microsoft administrator to confirm that the Filed OAuth application and its requested Microsoft Graph permissions are allowed. A successful sign-in does not override tenant consent or site policy. ## Create the connection 1. Open **Plugins & integrations** and select **SharePoint**. 2. Give the connection a clear, durable name, such as `US Tax SharePoint` or `Acme Client Library`. 3. Review the connection permissions: * **Read** is always enabled and allows Filed to retrieve information from SharePoint content the authorized account can access. * **Write** is enabled by default. Clear it to make the connection read-only. You can change it later from the connection settings. 4. Select **Continue** to begin Microsoft authorization. ## Authorize Microsoft 365 1. Sign in with the Microsoft work account that has the required SharePoint access. Do not use a personal Microsoft account unless the relevant SharePoint content is intentionally owned there. 2. Complete your organization's multi-factor authentication or conditional-access steps. 3. Review and accept the requested permissions if your organization permits the application. 4. Return to Filed and wait for the connection to verify as **Active**. If Microsoft shows an administrator-approval message, send that request to your Microsoft 365 administrator. Do not try to work around it with a broader or unrelated account. ## Verify the connection After the connection is active, check a known site and document library that the authorized account should be able to open. For any workflow that writes content, test in a non-production folder first. SharePoint permissions can differ at the site, library, folder, and file levels. Verify the exact target location rather than assuming that access to one site provides access to all sites. ## Manage write access Turn off **Write** in the connection settings to make the connection read-only. Filed can still retrieve information from SharePoint, but it cannot use write capabilities such as creating, uploading, moving, renaming, updating, or deleting content. Use read-only access for document discovery, review, or context gathering. Enable write only when your firm has approved Filed to change SharePoint data and the connected account has the required permission in the target library. ## Reconnect or remove the connection Use **Reconnect** after Microsoft authorization is revoked, a password or multi-factor method changes, the user's role changes, or the connection shows pending or failed. Reconnect with the correct firm account and verify the intended site afterward. Use **Remove** only when the connection should no longer be used in Filed. Removing a connection never deletes SharePoint sites, libraries, or files. ## Troubleshooting ### Microsoft says administrator approval is required Your Microsoft 365 tenant requires administrator consent for the application or its requested permissions. Ask a tenant administrator to review the request. The person approving should understand the intended sites and data scope before granting consent. ### The connection is active but a SharePoint site or library is missing Open the site and library as the authorized Microsoft user. If it is not available there, Filed cannot access it. Add the user to the site or grant the correct library permission, then reconnect or retry the operation. ### Filed can read files but cannot change them Confirm that **Write** is enabled in Filed. Then check the connected user's permission in the exact SharePoint library or folder. Read-only access, a restrictive sensitivity label, retention policy, or a library-specific permission can prevent changes even when the user can browse the site. ### A personal Microsoft account opens instead of the work account Sign out of Microsoft in the authorization window and restart the connection. Choose the organization's work account. If the browser keeps selecting the wrong account, use a private browsing window or ask the user to clear the active Microsoft session. ### The connection fails after a policy or role change Conditional-access policy, tenant consent, site membership, or licensing may have changed. Reconnect after the Microsoft administrator confirms the user still has both app authorization and access to the intended SharePoint locations. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding SharePoint information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with SharePoint data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find the SharePoint folder for \[client name] and list the most recent source documents.” * “Summarize the tax documents in \[folder name] and flag anything that appears missing.” * “With write access enabled, create an approved folder structure for \[client name] and upload \[file name].” ## Capabilities ### Find and read client documents Use Filed to browse, search, and retrieve the files and folders available to the connected account. This is useful for gathering source documents, answering questions, and preparing a client file for review. ### Organize approved content When **Write** access is enabled, Filed can create folders and upload, move, rename, or update approved documents where the connected account has permission. Use this to keep client deliverables and workpapers in the agreed location. ### Preserve your provider’s access model Filed works within existing folder, site, shared-drive, or library permissions. Use the provider’s own sharing controls to decide which client content the connection can reach. # SmartVault With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from SmartVault and, when **Write** access is enabled, perform approved actions in SmartVault. ## What this integration does The SmartVault integration gives Filed direct access to client documents stored in your SmartVault vaults, without manual uploads. SmartVault organizes content in a three-level hierarchy: Account, Vault, and Folder. Filed navigates this hierarchy to locate client folders and maps them to client records. Once clients are imported, Filed can read and write files within each client's SmartVault folder, so your team can file documents back to SmartVault directly from Filed. SmartVault uses autonomous authentication. Filed uses the SmartVault API client and RSA private key that you provide for this connection to request a short-lived delegation token for the selected SmartVault user. There is no browser sign-in or OAuth popup. ## Before you start You need a SmartVault account with access to the vaults that contain your client files. Client folders must be organized with one folder per client inside a vault. You also need these values from your SmartVault autonomous API client: * Client ID * Delegated user email address — the SmartVault account Filed will act as * Firm URI * RSA private key — PEM or base64-encoded PKCS#8 format The delegated SmartVault user must have already authorized the API client and have access to the folders Filed needs. Filed encrypts these values as connection credentials and uses them only to authenticate this SmartVault connection. ## Connecting SmartVault to Filed 1. Go to **Plugins**, then open **SmartVault**. 2. Select **Connect SmartVault** and name the connection. 3. Enter the Client ID, delegated user email, Firm URI, and RSA private key. 4. Select **Connect SmartVault**. Filed verifies the credentials and connects without opening a SmartVault sign-in page. ## Importing clients from SmartVault ## What Filed can do with SmartVault Once connected, Filed exposes the following actions against your SmartVault vaults: **Browsing and finding files** * List the contents of a folder using the Account/Vault/Folder path * Retrieve metadata for a specific file or folder node * Search for files and folders by name within a folder subtree **Managing files and folders** * Download a file * Upload a file to a folder * Create a new folder * Move a file or folder to a different path * Copy a file or folder to a destination path * Delete a file or folder These capabilities power binder creation and update: when Filed prepares a client's binder, it uses this action set to retrieve source documents from SmartVault and to file completed documents back. ## Troubleshooting **Connection error while connecting.** Confirm the Client ID, delegated user email, Firm URI, and RSA private key are entered correctly. The private key must be PEM or base64-encoded PKCS#8. Also confirm the delegated user has authorized the API client in SmartVault and has access to the required vaults. **401 Unauthorized while browsing files.** Confirm the connection is active and reconnect after correcting the delegated user or API client authorization. The delegated user needs permission for the specific Account/Vault/Folder path being accessed. **Clients are not appearing after import.** Confirm that the SmartVault account used during connection has access to the vaults and that client folders exist at the correct level in the Account/Vault/Folder hierarchy. Filed maps the immediate children of the selected path as client records; deeply nested structures will not be detected. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding SmartVault information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with SmartVault data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find the SmartVault folder for \[client name] and list the most recent source documents.” * “Summarize the tax documents in \[folder name] and flag anything that appears missing.” * “With write access enabled, create an approved folder structure for \[client name] and upload \[file name].” ## Capabilities ### Find and read client documents Use Filed to browse, search, and retrieve the files and folders available to the connected account. This is useful for gathering source documents, answering questions, and preparing a client file for review. ### Organize approved content When **Write** access is enabled, Filed can create folders and upload, move, rename, or update approved documents where the connected account has permission. Use this to keep client deliverables and workpapers in the agreed location. ### Preserve your provider’s access model Filed works within existing folder, site, shared-drive, or library permissions. Use the provider’s own sharing controls to decide which client content the connection can reach. # Box With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Box and, when **Write** access is enabled, perform approved actions in Box. ## What this integration does The Box integration gives Filed direct access to client documents stored in Box, without manual uploads. You designate one Box folder as the root; sub-folders inside it map one-to-one to client records in Filed. Once clients are imported, Filed can read and organize files within each client's Box folder. Uploading new files to Box is not supported through this connector. Box is the only DMS integration that supports collaboration management. Filed can create, view, update, and remove Box collaborations on files and folders, with access roles ranging from viewer and uploader through editor and co-owner. This makes it well suited to firms that need to control per-item access directly from Filed. Filed authenticates with Box using the standard OAuth 2.0 authorization code flow, holding the access and refresh tokens issued by Box and refreshing them automatically in the background. ## Before you start You need a Box account with access to the folder containing your client sub-folders. To use collaboration management features, the connected account should hold owner or co-owner access on the relevant folders. The top-level folder must be organized with one sub-folder per client at the immediate first level. ## Connecting Box to Filed ## Importing clients from Box ## What Filed can do with Box Once connected, Filed exposes the following actions against your Box account: **Searching and browsing** * Search across files, folders, and web links by keyword, with paginated results * List files within a folder * List folders within a folder * Browse all items (files and folders) within a folder * Retrieve metadata for a specific file * Retrieve metadata for a specific folder **Managing files and folders** * Download a file * Create a new folder * Copy a file to another folder, optionally renaming it * Copy a folder and its contents to a destination folder * Update a file's name, description, parent folder, or tags * Update a folder's name, description, parent folder, tags, or collaboration settings * Delete a file (moved to trash by default, or permanently deleted) * Delete a folder, including its contents **Collaboration management** * Create a collaboration granting a user or group access to a file or folder, with one of the following roles: viewer, uploader, previewer, previewer uploader, editor, or co-owner * Retrieve details of a specific collaboration * List pending collaborations for the connected account * Update a collaboration's role, status, expiry date, or path visibility * Remove a collaboration These capabilities power binder creation and update: when Filed prepares a client's binder, it uses this action set to retrieve source documents from Box and to file completed documents back. ## Troubleshooting **Connection error on the DMS page.** Disconnect and reconnect. Verify that the Box account you used still has access to the folder you originally selected. **Clients are not appearing after import.** The top-level folder you selected must contain sub-folders at exactly one level deep, one per client. If the folder structure does not match, reconnect and select the correct folder level. **Collaboration errors.** Filed can only manage collaborations for items where the connected account holds sufficient access rights. If a collaboration action fails, verify that the connected Box account has owner or co-owner access on the affected folder. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding Box information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Box data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find the Box folder for \[client name] and list the most recent source documents.” * “Summarize the tax documents in \[folder name] and flag anything that appears missing.” * “With write access enabled, create an approved folder structure for \[client name] and upload \[file name].” ## Capabilities ### Find and read client documents Use Filed to browse, search, and retrieve the files and folders available to the connected account. This is useful for gathering source documents, answering questions, and preparing a client file for review. ### Organize approved content When **Write** access is enabled, Filed can create folders and upload, move, rename, or update approved documents where the connected account has permission. Use this to keep client deliverables and workpapers in the agreed location. ### Preserve your provider’s access model Filed works within existing folder, site, shared-drive, or library permissions. Use the provider’s own sharing controls to decide which client content the connection can reach. # Dropbox With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Dropbox and, when **Write** access is enabled, perform approved actions in Dropbox. ## What this integration does The Dropbox integration gives Filed direct access to client documents stored in Dropbox, without manual uploads. You designate one Dropbox folder as the root; sub-folders inside it map one-to-one to client records in Filed. Once clients are imported, Filed can read, organize, and write files within each client's Dropbox folder, so your team can file documents back to Dropbox directly from Filed. Dropbox is one of two DMS integrations that supports file version history. Filed can list all saved revisions of a file and restore it to any earlier version. It can also generate short-lived temporary streaming links for files, which expire after four hours. Filed authenticates with Dropbox using OAuth 2.0 with offline access, so tokens are refreshed automatically in the background without requiring repeated sign-ins. ## Before you start You need a Dropbox account with access to the folder containing your client sub-folders. The top-level folder must be organized with one sub-folder per client at the immediate first level. ## Connecting Dropbox to Filed ## Importing clients from Dropbox ## What Filed can do with Dropbox Once connected, Filed exposes the following actions against your Dropbox account: **Searching and browsing** * Search for files and folders by query text, optionally scoped to a specific path * List the contents of a folder, with optional recursion and pagination * Retrieve metadata for a specific file or folder **Managing files and folders** * Download a file * Upload a file to a folder * Create a new folder * Copy a file or folder to a different path * Move a file or folder to a different path * Delete a file or folder **Temporary links** * Generate a short-lived streaming link for a file that can be used for direct downloads (link expires after four hours) **Version history** * List the revision history of a file * Restore a file to a previous revision These capabilities power binder creation and update: when Filed prepares a client's binder, it uses this action set to retrieve source documents from Dropbox and to file completed documents back. ## Troubleshooting **Connection error on the DMS page.** Disconnect and reconnect. Verify that the Dropbox account you used still has access to the folder you originally selected. **Clients are not appearing after import.** The top-level folder you selected must contain sub-folders at exactly one level deep, one per client. If the folder structure does not match, reconnect and select the correct folder level. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding Dropbox information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Dropbox data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find the Dropbox folder for \[client name] and list the most recent source documents.” * “Summarize the tax documents in \[folder name] and flag anything that appears missing.” * “With write access enabled, create an approved folder structure for \[client name] and upload \[file name].” ## Capabilities ### Find and read client documents Use Filed to browse, search, and retrieve the files and folders available to the connected account. This is useful for gathering source documents, answering questions, and preparing a client file for review. ### Organize approved content When **Write** access is enabled, Filed can create folders and upload, move, rename, or update approved documents where the connected account has permission. Use this to keep client deliverables and workpapers in the agreed location. ### Preserve your provider’s access model Filed works within existing folder, site, shared-drive, or library permissions. Use the provider’s own sharing controls to decide which client content the connection can reach. # OneDrive With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from OneDrive and, when **Write** access is enabled, perform approved actions in OneDrive. ## Connect OneDrive 1. Create a **OneDrive** connection and name it for the Microsoft user or department. 2. Sign in with the user who owns, or is shared on, the required files. 3. Approve Microsoft consent and return to Filed for verification. 4. Test a known file before allowing write actions. OneDrive access is limited to the connected user's files and items shared with them. Use SharePoint instead for files stored in a team document library. ## Verify the connection After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm file ownership and sharing access. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow. ## Manage permissions Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying OneDrive data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change. ## Troubleshooting **The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has file ownership and sharing access. **The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review file ownership and sharing access, then reconnect if the account or environment was wrong. **The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding OneDrive information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with OneDrive data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find the OneDrive folder for \[client name] and list the most recent source documents.” * “Summarize the tax documents in \[folder name] and flag anything that appears missing.” * “With write access enabled, create an approved folder structure for \[client name] and upload \[file name].” ## Capabilities ### Find and read client documents Use Filed to browse, search, and retrieve the files and folders available to the connected account. This is useful for gathering source documents, answering questions, and preparing a client file for review. ### Organize approved content When **Write** access is enabled, Filed can create folders and upload, move, rename, or update approved documents where the connected account has permission. Use this to keep client deliverables and workpapers in the agreed location. ### Preserve your provider’s access model Filed works within existing folder, site, shared-drive, or library permissions. Use the provider’s own sharing controls to decide which client content the connection can reach. # Egnyte With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Egnyte and, when **Write** access is enabled, perform approved actions in Egnyte. This integration to Filed is connected via our integration provider [Composio](https://composio.dev/) ## What you need * An Egnyte OAuth client ID and client secret from your administrator. * Your Egnyte domain, such as `acme` for `acme.egnyte.com`. * A user who can access the intended folders. ## Connect Egnyte 1. Enter the client ID, client secret, and Egnyte domain in the credential step. 2. Continue to Egnyte and sign in with the authorized user. 3. Approve access, return to Filed, and wait for verification. 4. Keep write access off until your firm approves file changes through Filed. If authorization fails, have your Egnyte administrator confirm the OAuth app's redirect URL and tenant domain. ## Verify the connection After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm OAuth application values, domain, and folder access. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow. ## Manage permissions Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying Egnyte data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change. ## Troubleshooting **The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has OAuth application values, domain, and folder access. **The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review OAuth application values, domain, and folder access, then reconnect if the account or environment was wrong. **The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding Egnyte information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Egnyte data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find the Egnyte folder for \[client name] and list the most recent source documents.” * “Summarize the tax documents in \[folder name] and flag anything that appears missing.” * “With write access enabled, create an approved folder structure for \[client name] and upload \[file name].” ## Capabilities ### Find and read client documents Use Filed to browse, search, and retrieve the files and folders available to the connected account. This is useful for gathering source documents, answering questions, and preparing a client file for review. ### Organize approved content When **Write** access is enabled, Filed can create folders and upload, move, rename, or update approved documents where the connected account has permission. Use this to keep client deliverables and workpapers in the agreed location. ### Preserve your provider’s access model Filed works within existing folder, site, shared-drive, or library permissions. Use the provider’s own sharing controls to decide which client content the connection can reach. # Communications Connect only mailboxes, calendars, and meeting accounts your firm has approved for Filed. A provider's existing sharing and mailbox permissions continue to apply. * [Gmail](/reference/plugins/integrations/communications/gmail) * [Outlook](/reference/plugins/integrations/communications/outlook) * [IMAP Email](/reference/plugins/integrations/communications/imap-email) * [Google Calendar](/reference/plugins/integrations/communications/google-calendar) * [Calendly](/reference/plugins/integrations/communications/calendly) * [Google Meet](/reference/plugins/integrations/communications/google-meet) # Gmail With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Gmail and, when **Write** access is enabled, perform approved actions in Gmail. The Gmail integration connects a Gmail or Google Workspace account to Filed using the IMAP and SMTP protocols. Filed reads your mailbox and sends messages on your behalf, authenticated with a Google App Password rather than your regular Google account password. ## What this integration does Gmail authenticates over IMAP using a 16-character App Password that you generate from your Google Account security settings. This means your main Google password is never entered into Filed, and the connection is not affected by single sign-on or organization-level OAuth restrictions. Outbound messages are sent via SMTP. Unlike the Outlook integration, Gmail's SMTP server does not automatically copy sent messages to your Sent folder; whether a copy appears there depends on your Gmail settings. ## Before you start You need a Gmail or Google Workspace account with 2-Step Verification already enabled. Google only displays the App Password option after 2-Step Verification is turned on. You will generate a 16-character App Password from your Google Account and paste it into Filed during setup. Copy and store it immediately; Google does not display it again after the dialog is closed. ## Generating a Google app password ## Connecting Gmail to Filed ## What Filed can do with Gmail **List mailboxes** - returns all Gmail labels and folders available in the account, including system folders such as Inbox and Sent Mail as well as any custom labels. **List messages** - retrieves an envelope listing of messages in any mailbox folder, with support for a keyword search query, a date filter (messages received after a given date), a maximum result count, and pagination using a continuation token. **Get message** - fetches the full content of a specific message identified by its mailbox path and UID. The response includes the subject, sender, recipients (To and CC), date, plain-text and HTML body, read/unread status, and a list of attachments with each attachment's filename, content type, and size. **Send message** - composes and sends a message from the connected Gmail account via SMTP. Supports To, CC, and BCC recipients, a subject, and a plain-text or HTML body. To reply within an existing thread, supply the thread identifier. ## Troubleshooting **Authentication failed** - Filed is receiving a credentials rejection from Google's IMAP server. The most common cause is entering your regular Gmail password instead of the App Password. The App Password is exactly 16 characters and contains no spaces (Google displays it in groups of four for readability). Confirm you are pasting the correct value. **App Password option not visible in Google Account** - The App Passwords section only appears after 2-Step Verification is fully configured on the account. Complete 2-Step Verification setup and then return to generate the password. **Connection stops working after it was previously active** - Google can revoke App Passwords when certain account security events occur, such as a password change or a security alert. If the connection shows an error, generate a new App Password from your Google Account and reconnect. **Google Workspace accounts** - Some Workspace administrators restrict which apps can connect via IMAP. If connection consistently fails for a Workspace account, ask your Google Workspace administrator to confirm that IMAP access is enabled for your account in the Admin console. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding Gmail information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Gmail data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find recent Gmail information related to \[client name] and summarize the key items.” * “Show me anything from the last 30 days that needs a response or follow-up.” * “With write access enabled, create the approved follow-up for \[client name] for my review.” ## Capabilities ### Review communication context Use Filed to retrieve the emails, calendar information, or meeting context available to the connected account. This helps your team find client follow-ups, deadlines, and outstanding requests. ### Coordinate approved follow-up When **Write** access is enabled, Filed can help create approved communications, events, or tasks supported by the provider. Use this for supervised follow-up workflows rather than unsupervised outreach. ### Keep access scoped to the right account The connection sees only what the authorized account can access. Use a firm-managed mailbox or calendar and its sharing settings to control scope. # Outlook With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Outlook and, when **Write** access is enabled, perform approved actions in Outlook. The Outlook integration connects a Microsoft 365 or Outlook.com account to Filed using Microsoft OAuth2. You authorize Filed through a standard Microsoft sign-in window; no password is entered into Filed directly. ## What this integration does When you connect Outlook, Filed opens a Microsoft sign-in window and requests permission scopes for IMAP access to your mailbox and the ability to send mail on your behalf, along with standard identity scopes. After you sign in and accept those permissions, Microsoft issues Filed a pair of tokens. Filed uses one token to read your mailbox over IMAP and a separate token to send messages through the Microsoft Graph API. Tokens are refreshed automatically in the background, so the connection remains active without requiring you to re-authorize periodically. Outbound messages sent through the Outlook integration are automatically saved to your Sent Items folder by Microsoft Graph. This is a built-in behavior of the Graph sending path and requires no additional configuration. The Outlook integration is designed for Microsoft 365 and Outlook.com accounts. On-premises Exchange servers that do not expose Microsoft OAuth are not supported; use the IMAP Email integration for those. ## Before you start You need a Microsoft 365 or Outlook.com account. If your organization manages Microsoft 365, confirm with your IT administrator that third-party app access is not blocked in your Azure AD tenant. If it is restricted, your administrator can approve Filed in the Azure AD app consent settings, or your firm can use the IMAP Email integration as an alternative. ## Connecting Outlook to Filed ## What Filed can do with Outlook **List mailboxes** - returns all folders available in the connected Outlook mailbox, including Inbox, Sent Items, Drafts, and any custom folders. **List messages** - retrieves an envelope listing of messages in any mailbox folder, with support for a keyword search query, a date filter (messages received after a given date), a maximum result count, and pagination using a continuation token. **Get message** - fetches the full content of a specific message identified by its mailbox path and UID. The response includes the subject, sender, recipients (To and CC), date, plain-text and HTML body, read/unread status, and a list of attachments with each attachment's filename, content type, and size. **Send message** - composes and sends a message from the connected Outlook account via the Microsoft Graph API. Supports To, CC, and BCC recipients, a subject, and a plain-text or HTML body. Sent messages are automatically saved to your Sent Items folder. ## Troubleshooting **Microsoft sign-in window does not open** - The sign-in flow opens in a pop-up window. If nothing appears, check that your browser is not blocking pop-ups for Filed and allow them if needed. **Access denied or admin approval required** - Your organization's Azure AD tenant may require administrator consent before users can authorize third-party applications. Ask your IT administrator to approve Filed in Azure AD, or switch to the IMAP Email integration which does not require Azure AD consent. **Connection shows an error after a password or account change** - Changing your Microsoft account password or certain account security events can invalidate the OAuth tokens Filed holds. Disconnect the integration and reconnect to issue fresh tokens. **Sent messages do not appear in Sent Items** - The Outlook integration sends via Microsoft Graph with the save-to-sent-items option enabled. If sent messages are missing, confirm that the Microsoft account connected in Filed matches the account you are checking in Outlook. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding Outlook information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Outlook data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find recent Outlook information related to \[client name] and summarize the key items.” * “Show me anything from the last 30 days that needs a response or follow-up.” * “With write access enabled, create the approved follow-up for \[client name] for my review.” ## Capabilities ### Review communication context Use Filed to retrieve the emails, calendar information, or meeting context available to the connected account. This helps your team find client follow-ups, deadlines, and outstanding requests. ### Coordinate approved follow-up When **Write** access is enabled, Filed can help create approved communications, events, or tasks supported by the provider. Use this for supervised follow-up workflows rather than unsupervised outreach. ### Keep access scoped to the right account The connection sees only what the authorized account can access. Use a firm-managed mailbox or calendar and its sharing settings to control scope. # IMAP Email With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from IMAP Email and, when **Write** access is enabled, perform approved actions in IMAP Email. The IMAP Email integration connects any IMAP and SMTP compatible mailbox to Filed using server credentials you provide. It is the most flexible email option and works with custom business email addresses, hosted Exchange servers, and any other provider that supports standard IMAP access. ## What this integration does IMAP Email authenticates directly with your mail server using a username and password (or an app-specific password if your provider requires one for third-party clients). Filed establishes an IMAP connection to read your mailbox and an SMTP connection to send messages. Because this integration works at the protocol level rather than through a provider-specific API, it is compatible with a wide range of mail servers. However, since IMAP credentials cannot be refreshed automatically the way OAuth tokens can, the connection will show an error if your password changes and will need to be reconnected with updated credentials. SMTP does not automatically copy sent messages to a Sent folder on the server. Whether a copy appears in your Sent folder depends on your mail server's configuration and any rules you have set in your email client. ## Before you start You need the following information from your email provider or IT administrator: * IMAP server hostname and port (typically port 993 with TLS) * SMTP server hostname and port (typically port 587 with TLS) * Your email username (usually your full email address) and password * Whether each server requires TLS If your provider requires an app-specific password for IMAP access (common with accounts that have two-factor authentication enabled), generate that password before starting. Do not use your main account password if the provider does not support it for IMAP. Common server settings for reference: | Provider | IMAP Host | IMAP Port | SMTP Host | SMTP Port | | ---------------- | --------------------- | --------- | ------------------ | --------- | | Google Workspace | imap.gmail.com | 993 | smtp.gmail.com | 587 | | Microsoft 365 | outlook.office365.com | 993 | smtp.office365.com | 587 | | Apple iCloud | imap.mail.me.com | 993 | smtp.mail.me.com | 587 | For Google Workspace accounts, use the dedicated Gmail integration instead of IMAP Email if possible, as it handles the App Password flow with pre-filled server settings. ## Connecting IMAP email to Filed Filed prompts for your IMAP server host, port, username, and password. SMTP settings default to the same host as your IMAP server; expand Advanced settings to enter a different SMTP host, port, or separate SMTP credentials if your provider uses different servers for inbound and outbound mail. ## What Filed can do with IMAP email **List mailboxes** - returns all folders present on the IMAP server for the connected account, including any server-side folder hierarchy your provider maintains. **List messages** - retrieves an envelope listing of messages in any mailbox folder, with support for a keyword search query, a date filter (messages received after a given date), a maximum result count, and pagination using a continuation token. **Get message** - fetches the full content of a specific message identified by its mailbox path and UID. The response includes the subject, sender, recipients (To and CC), date, plain-text and HTML body, read/unread status, and a list of attachments with each attachment's filename, content type, and size. **Send message** - composes and sends a message from the connected account via your SMTP server. Supports To, CC, and BCC recipients, a subject, and a plain-text or HTML body. ## Troubleshooting **Authentication failed** - The IMAP server rejected the username or password. Verify that you are using the correct credentials for IMAP access. If your provider requires an app-specific password for third-party clients (rather than your main account password), generate one and use that instead. **Connection refused or timeout** - Filed cannot reach the IMAP server at the address and port entered. Double-check that the hostname and port are correct. Some providers require you to enable IMAP access in your account settings before a third-party client can connect; consult your provider's documentation. **SMTP sending fails but IMAP reads correctly** - The SMTP settings may differ from the IMAP settings. Expand Advanced settings in the connection form and confirm the SMTP host and port are correct. If your provider uses separate credentials for outbound mail, enter them in the SMTP username and password fields. **Connection worked previously but now shows an error** - If your password changed, the stored credentials are no longer valid. Reconnect the integration with the updated password. Some servers also close idle connections after extended inactivity; if errors appear intermittently, confirm with your provider that persistent third-party connections are supported. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding IMAP Email information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with IMAP Email data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find recent IMAP Email information related to \[client name] and summarize the key items.” * “Show me anything from the last 30 days that needs a response or follow-up.” * “With write access enabled, create the approved follow-up for \[client name] for my review.” ## Capabilities ### Review communication context Use Filed to retrieve the emails, calendar information, or meeting context available to the connected account. This helps your team find client follow-ups, deadlines, and outstanding requests. ### Coordinate approved follow-up When **Write** access is enabled, Filed can help create approved communications, events, or tasks supported by the provider. Use this for supervised follow-up workflows rather than unsupervised outreach. ### Keep access scoped to the right account The connection sees only what the authorized account can access. Use a firm-managed mailbox or calendar and its sharing settings to control scope. # Google Calendar With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Google Calendar and, when **Write** access is enabled, perform approved actions in Google Calendar. ## Connect Google Calendar 1. Create a Google Calendar connection and name it for the account or scheduling team. 2. Sign in with an account that can access the calendars Filed should use. 3. Approve authorization and return to Filed. 4. Verify a known shared calendar before enabling write access. If a calendar is missing, share it with the connected account. Google Calendar sharing controls remain in effect. ## Verify the connection After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm calendar sharing and Workspace consent. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow. ## Manage permissions Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying Google Calendar data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change. ## Troubleshooting **The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has calendar sharing and Workspace consent. **The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review calendar sharing and Workspace consent, then reconnect if the account or environment was wrong. **The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding Google Calendar information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Google Calendar data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find recent Google Calendar information related to \[client name] and summarize the key items.” * “Show me anything from the last 30 days that needs a response or follow-up.” * “With write access enabled, create the approved follow-up for \[client name] for my review.” ## Capabilities ### Review communication context Use Filed to retrieve the emails, calendar information, or meeting context available to the connected account. This helps your team find client follow-ups, deadlines, and outstanding requests. ### Coordinate approved follow-up When **Write** access is enabled, Filed can help create approved communications, events, or tasks supported by the provider. Use this for supervised follow-up workflows rather than unsupervised outreach. ### Keep access scoped to the right account The connection sees only what the authorized account can access. Use a firm-managed mailbox or calendar and its sharing settings to control scope. # Calendly With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Calendly and, when **Write** access is enabled, perform approved actions in Calendly. This integration to Filed is connected via our integration provider [Composio](https://composio.dev/) ## Connect Calendly 1. Name the connection for the firm or scheduling team. 2. Sign in with a user who can access the intended Calendly organization and event types. 3. Approve authorization, return to Filed, and verify the connection. 4. Keep write access off unless Filed may create or update scheduling data. If event types are missing, verify that the connected user belongs to the intended organization. ## Verify the connection After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm organization membership and event-type access. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow. ## Manage permissions Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying Calendly data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change. ## Troubleshooting **The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has organization membership and event-type access. **The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review organization membership and event-type access, then reconnect if the account or environment was wrong. **The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding Calendly information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Calendly data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find recent Calendly information related to \[client name] and summarize the key items.” * “Show me anything from the last 30 days that needs a response or follow-up.” * “With write access enabled, create the approved follow-up for \[client name] for my review.” ## Capabilities ### Review communication context Use Filed to retrieve the emails, calendar information, or meeting context available to the connected account. This helps your team find client follow-ups, deadlines, and outstanding requests. ### Coordinate approved follow-up When **Write** access is enabled, Filed can help create approved communications, events, or tasks supported by the provider. Use this for supervised follow-up workflows rather than unsupervised outreach. ### Keep access scoped to the right account The connection sees only what the authorized account can access. Use a firm-managed mailbox or calendar and its sharing settings to control scope. # Google Meet With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Google Meet and, when **Write** access is enabled, perform approved actions in Google Meet. ## Connect Google Meet 1. Create a Google Meet connection and name it for the Workspace account or team. 2. Sign in with a Google account that can access the meeting and calendar information you need. 3. Approve the requested Google permissions and return to Filed. 4. Verify the connection before using meeting information in a workflow. If consent is blocked, ask a Google Workspace administrator to review the OAuth app and requested scopes. ## Verify the connection After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm Workspace consent and calendar access. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow. ## Manage permissions Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying Google Meet data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change. ## Troubleshooting **The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has Workspace consent and calendar access. **The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review Workspace consent and calendar access, then reconnect if the account or environment was wrong. **The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding Google Meet information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Google Meet data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find recent Google Meet information related to \[client name] and summarize the key items.” * “Show me anything from the last 30 days that needs a response or follow-up.” * “With write access enabled, create the approved follow-up for \[client name] for my review.” ## Capabilities ### Review communication context Use Filed to retrieve the emails, calendar information, or meeting context available to the connected account. This helps your team find client follow-ups, deadlines, and outstanding requests. ### Coordinate approved follow-up When **Write** access is enabled, Filed can help create approved communications, events, or tasks supported by the provider. Use this for supervised follow-up workflows rather than unsupervised outreach. ### Keep access scoped to the right account The connection sees only what the authorized account can access. Use a firm-managed mailbox or calendar and its sharing settings to control scope. # Productivity Connect a firm-managed account with access to the documents, spreadsheets, tasks, and workspace content Filed should use. Enable write only for approved creation or update workflows. * [Microsoft Excel](/reference/plugins/integrations/productivity/microsoft-excel) * [Microsoft To Do](/reference/plugins/integrations/productivity/microsoft-to-do) * [Google Sheets](/reference/plugins/integrations/productivity/google-sheets) * [Google Docs](/reference/plugins/integrations/productivity/google-docs) * [Google Forms](/reference/plugins/integrations/productivity/google-forms) * [Google Tasks](/reference/plugins/integrations/productivity/google-tasks) * [Google Slides](/reference/plugins/integrations/productivity/google-slides) * [Notion](/reference/plugins/integrations/productivity/notion) * [Airtable](/reference/plugins/integrations/productivity/airtable) # Microsoft Excel With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Microsoft Excel and, when **Write** access is enabled, perform approved actions in Microsoft Excel. ## Connect Microsoft Excel 1. Name the connection for the Microsoft account or team. 2. Sign in with the user that can access the workbooks Filed should use. 3. Approve Microsoft consent and return to Filed for verification. 4. Test with a non-production workbook before enabling write access. Files stored in OneDrive or SharePoint still follow that user's file permissions. ## Verify the connection After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm Microsoft consent and workbook access. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow. ## Manage permissions Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying Microsoft Excel data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change. ## Troubleshooting **The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has Microsoft consent and workbook access. **The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review Microsoft consent and workbook access, then reconnect if the account or environment was wrong. **The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding Microsoft Excel information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Microsoft Excel data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Summarize the Microsoft Excel information for \[client name] for \[date range].” * “Find items in Microsoft Excel that need review before \[deadline].” * “With write access enabled, prepare the approved Microsoft Excel update and show the proposed changes first.” ## Capabilities ### Review financial operations information Use Filed to retrieve the payroll, spend, payment, or billing information available to the connected account. This helps with review, reconciliation, and deadline-driven operational work. ### Prepare approved financial operations changes When **Write** access is enabled, Filed can support provider actions that your firm has approved. Review the proposed change carefully before allowing it to affect live financial records. ### Separate reporting from action Use read-only access for reporting and analysis. Enable Write only for a dedicated connection whose owner and scope are appropriate for production financial activity. --- [Next Page](/llms-full.txt/1)