> For the complete documentation index, see [llms.txt](https://help.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filed.com/reference/plugins/tax-software/cch-axcess.md). # CCH Axcess 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. ## Prerequisites * A CCH Axcess Tax account with admin access. * A dedicated CCH Axcess login created specifically for Filed - do not use a personal login. * Admin ability to configure two-factor authentication (2FA) device pairing for that login. * The dedicated login's Account ID, User ID, and password. * Knowledge of whether your firm has the CCH Axcess Tax API Kit. ## Connecting CCH Axcess to Filed Setting up CCH Axcess 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. ### 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. ## 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. ### 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.filed.com/reference/plugins/tax-software/cch-axcess.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.