--- title: CCH ProSystem fx Integration Guide description: Learn how to export validated K-1 data from K1 Aggregator and import it into CCH ProSystem fx using the ProSystem fx Retrofit Desktop Tool. This guide walks through the complete integration workflow, including one-time setup, exporting data from K1 Aggregator, importing into ProSystem fx, and verifying the results. It also covers supported return types, supported data, and common troubleshooting tips. --- [Skip to content](https://support.k1x.io/k1-aggregator-cch-prosystem-fx-integration-guide#main-content) [Submit A Support Ticket](https://support.k1x.io/kb-tickets/new?hsLang=en-us) [Client portal](https://support.k1x.io/tickets?hsLang=en-us) [![Group 16](https://support.k1x.io/hs-fs/hubfs/Group%2016.png?width=75&height=75&name=Group%2016.png)](https://support.k1x.io/?hsLang=en-us) - [Knowledge Base](https://support.k1x.io/) Open main navigation Close main navigation - [Knowledge Base](https://support.k1x.io/) - [Submit A Support Ticket](https://support.k1x.io/kb-tickets/new) - [Client portal](https://support.k1x.io/tickets) How can we help? - There are no suggestions because the search field is empty. 1. [K1x Knowledge Base](https://support.k1x.io/?hsLang=en-us) 2. [K1 Aggregator](https://support.k1x.io/k1-aggregator?hsLang=en-us) 3. [Integrations - UltraTax, Profx, OIT](https://support.k1x.io/k1-aggregator?hsLang=en-us#integrations-ultratax-profx-oit) September 23, 2026 # CCH ProSystem fx Integration Guide ## Customer setup and workflow reference ### Use this guide to prepare CCH ProSystem fx Desktop, map K1 Aggregator records, export reviewed K-1 data, import it through the Retrofit Desktop Tool, and verify the result. The integration depends on exact identifiers and pre-existing ProSystem fx activity records. Complete the prerequisites before your first transfer. ### Integration Overview K1 Aggregator transfers validated K-1 data into CCH ProSystem fx through the ProSystem fx Retrofit Desktop Tool. The standard workflow is: 1. Prepare the ProSystem fx desktop environment and target return. 2. Create and verify the passthrough, activity, and Section 199A records that will receive data. 3. Enter the matching identifiers in K1 Aggregator and review the K-1 data. 4. Export selected investments, import the ZIP package through Retrofit, and verify the results in ProSystem fx. **Supported Return Types and Data**  | **Return Type** | **Supported** | | --- | --- | | Form 1040 | Yes | | Form 1041 | Yes | | Form 1065 | Yes | | Form 1120 | Yes | | Form 1120-S | Yes | | 990 Series | Yes | --- ### Supported Data | **Data Type** | **1040** | **1041** | **1065** | **1120** | **1120-S** | **990** | | --- | --- | --- | --- | --- | --- | --- | | General Information | Yes | Yes | Yes | Yes | Yes | Yes | | Federal Line Items | Yes | Yes | Yes | Yes | Yes | No | | Section 199A | Yes | Yes | Yes | Yes | Yes | No | | UBI | No | No | No | No | No | Yes | | State QBI | Yes | Yes | Yes | Yes | Yes | Yes | | Multiple Activities | Yes | Yes | Yes | Yes | Yes | Yes | | Schedule K-3 | Yes | Yes | No | No | No | No | --- ### Before Your First Export **Confirm the desktop and drive configuration** The Retrofit Desktop Tool must run in the same Windows environment that can access ProSystem fx and its required program and data locations. Before importing: - Install and configure the supported Retrofit Desktop Tool for your ProSystem fx environment. - Confirm that the Windows user running Retrofit can open ProSystem fx and access the required program and data locations. - If ProSystem fx uses a mapped network drive, confirm that the same drive letter is mapped and available to the Windows user running Retrofit. Do not substitute a different drive letter or an unmapped network path. - If the mapped drive is unavailable in Retrofit, stop and correct the desktop or network configuration before importing. **Confirm access and Office Group ID** Use a ProSystem fx account authorized to run Retrofit and update the target return. Confirm any Supervisor or firm-configured permissions required by your organization. **Important:** Note the **Office Group ID** associated with the return, you will need to enter this before exporting the data. Do not use the descriptive office-group name unless it is also the actual configured **identifier**. If you do not know the correct value, check with your ProSystem fx administrator before exporting. **Confirm the ProSystem fx Return ID** Enter the return identifier and version in K1 Aggregator. Remove the leading tax-year and return-type segment and remove the V from the version segment. | **ProSystem fx Return ID** | **Enter in K1 Aggregator** | | --- | --- | | 25I:5281:V1 | 5281:1 | | 24I:DARCY:V2 | DARCY:2 | --- ### Use the K-1 record linked to Worksheet View You can work in either Worksheet View or Interview View, but you must use the IRS K-1 record that is linked to the supported worksheet structure. For a partnership K-1: - Worksheet View: **Use** Partnership Passthrough (K-1 1065)**, also identified as Worksheet 25.** - Interview View: **Use** IRS K-1 1065 Passthrough Income**. This is the Interview View representation of the same supported record.** - Do not use:Schedule K-1 Passthrough Income or Loss**. This is the legacy Interview record and is not the destination used by the integration.** **Important:** An activity entered only in **Schedule K-1 Passthrough Income or Loss** will not appear in the supported Worksheet View structure and will not provide the intended destination for the integration. ### Confirm the identifying numbers - **Return-level Identifying Number.** The primary taxpayer SSN or entity EIN in K1 Aggregator must match ProSystem fx exactly, including hyphens. - **K-1 matching information.** Confirm the partnership EIN and partner identifying number on the K-1 record. These values must agree with the existing ProSystem fx record used for the transfer. **Important:** An incorrect, partial, or differently formatted identifying number can result in no transfer or an incomplete transfer that appears successful in Retrofit. ### Create and verify the passthrough activities Each destination must already exist in ProSystem fx before export. Completing General Information alone is not sufficient. For every passthrough activity: 1. Create or open the passthrough entity in ProSystem fx. 2. Enter the partnership EIN and the applicable partner identifying number. 3. Create the Activity record. 4. Enter the Activity Number and the Name or description of activity. 5. Calculate and save the return. 6. Confirm the activity appears in the ProSystem fx Pass-through Activity Listing. 7. Enter the corresponding Entity ID and Activity Number in K1 Aggregator. For a multi-activity K-1, repeat this process for each destination activity. Activity numbers may repeat under different entities, so always verify the Entity ID and Activity Number together. ### Prepare Section 199A QBI records When Section 199A data will be transferred, establish the QBI records in ProSystem fx before exporting: 1. Create each applicable QBI record in ProSystem fx. 2. Enter the QBI activity name and EIN. 3. Calculate and save the return. 4. Record the QBI number assigned by ProSystem fx to each record. 5. Enter that QBI number on the corresponding Section 199A record in K1 Aggregator. 6. Confirm that the QBI number, activity name, and EIN align between both systems. **Important:** Each QBI record needs its own ProSystem fx QBI number. Do not replace the individual QBI numbers with the parent K-1 activity number. ### Review the K 1 data Complete your K1 Aggregator review before export. Review federal data, relevant footnotes, multiple activities, states, Section 199A, and Schedule K-3 when applicable. Resolve validation messages and confirm that the selected investments are ready to send. ### Export from K1 Aggregator Launch the Export Wizard From the Instance Dashboard, open the Actions menu and select Send Data to ProSystem fx Integration. You can also open an instance, select Data Integration, and then select Send Data to ProSystem fx Integration. ### Complete the Export Wizard 1. **Confirm the instance.** Verify that you selected the correct return and version. 2. **Select investments.** For every investment, verify the ProSystem fx Entity ID, Activity Number, and investment information. Review every underlying activity on multi-activity K-1s. 3. **Validate data.** Resolve messages for missing or inconsistent Return ID, Identifying Number, Entity ID, Activity Number, QBI Number, or other required fields. 4. **Enter the Office Group ID.** Use the configured identifier confirmed with your ProSystem fx administrator. 5. **Export the package.** Download the ZIP package and keep it intact. Do not extract or modify the files before import. ### Import through Retrofit 1. Calculate and save the target return, then close it in ProSystem fx. 2. Confirm that the required mapped drive and ProSystem fx locations are available in the current Windows session. 3. Open the Retrofit Desktop Tool. 4. Select the ProFX workflow. 5. Select the intact ZIP package exported from K1 Aggregator. 6. Enter your authorized ProSystem fx username and update the drive from the dropdown if needed (you can simply type over the drive letter 7. Start the import. 8. When Retrofit finishes, reopen the return in ProSystem fx. **Important:** A successful Retrofit message confirms that the package finished processing. It does not confirm that every value reached the correct return, entity, activity, or worksheet. Always complete the verification steps below. ### Verify the import Open the IRS K-1 Worksheets view in ProSystem fx. The integration does not populate the legacy Schedule K-1 Pass Through Income or Loss Interview forms. 1. Confirm that the expected passthrough entities and activities received data. 2. Review general information and representative federal line items. 3. Review state, Section 199A, and Schedule K-3 data when applicable. 4. For multi-activity K-1s, verify every destination activity separately. 5. Compare a representative set of values with the reviewed data in K1 Aggregator before continuing with return preparation. ### Troubleshooting | **Result** | **Check first** | **Next action** | | --- | --- | --- | | Validation fails | Return ID format; exact identifying numbers; Entity ID; Activity Number; QBI Number; Office Group ID | Correct the required field before creating another export. | | Retrofit cannot access ProSystem fx | Mapped drive letter; network access; Windows user; ProSystem fx availability | Restore the same mapped-drive environment used by ProSystem fx, then retry. | | Retrofit reports success but nothing populates | Return closed; Return ID; exact identifying number; IRS K-1 Worksheets view; Entity ID and Activity Number | Preserve the ZIP and contact K1x Support if a controlled single-investment test remains empty. | | Only some data populates | Exact identifying numbers; line-level expected vs actual; each multi-activity destination | Record missing lines and the affected Entity ID and Activity Number; send the evidence to K1x Support. | | A duplicate entity or activity appears | Existing Activity record; activity description; Pass-through Activity Listing; Entity ID and Activity Number | Stop repeated imports. Preserve the test return and package and contact K1x Support. | | Section 199A is missing or misrouted | Pre-existing QBI record; QBI name; EIN; assigned QBI number | Correct the matching QBI records in both systems before exporting again. | ### Information to provide to K1x Support Please reach out to **support@k1x.io** if you are unable to troubleshoot further.  - Tenant, tax year, instance, return name, and affected investment(s). - Full ProSystem fx Return ID. - Entity ID and Activity Number for each affected activity. - QBI number, activity name, and EIN for affected Section 199A records. - The exported ZIP package, source K-1, screenshots, and a concise expected-versus-actual comparison. ### Frequently Asked Questions **Why did Retrofit say the import succeeded when no data appeared?** The success message confirms that Retrofit processed the package. It does not confirm that the Return ID, identifying numbers, entity, activity, or worksheet destination matched. Verify the imported worksheets and all matching identifiers. **Why did Retrofit create a duplicate entity or activity?** Retrofit may not have found a complete matching destination. Verify the partnership EIN, partner identifying number, Entity ID, Activity Number, and activity description. Stop repeated imports until the mismatch is identified. **Does the ProSystem fx return need to be closed?** Yes. Calculate and save the return, then close it before starting Retrofit. **What drive configuration is required?** Retrofit must run in a Windows session that can access the ProSystem fx program and data locations. If ProSystem fx uses a mapped network drive, the same mapped drive letter must be available to the user running Retrofit. **What should I enter for Office Group ID?** Enter the actual configured Office Group ID used by your ProSystem fx environment **Where should I review imported data?** Review the IRS K-1 Worksheets. The integration does not populate the legacy Interview forms, and Interview-based activities are not automatically migrated to the worksheet workflow. **How do I prepare multiple activities?** Create, describe, calculate, and save each destination activity in ProSystem fx. Confirm every activity in the Pass-through Activity Listing, then map each one using its Entity ID and Activity Number. **How do I prepare multiple QBI businesses?** Create every QBI record in ProSystem fx first. Enter its name and EIN, calculate and save, note the QBI number assigned by ProSystem fx, and enter that number on the matching K1 Aggregator QBI record. **Can I import the same package repeatedly while troubleshooting?** Avoid repeated blind imports. They can make the return harder to diagnose. Preserve the original ZIP and test return, verify the environment and identifiers, and use a controlled single-investment test or contact K1x Support. **What should I do if only part of the K-1 transfers?** Do not assume the transfer is complete. Record the lines that transferred and those that did not, identify the affected entity and activity, preserve the ZIP package, and submit the evidence to K1x Support. **Quick reference checklist** Use this checklist before and after each transfer, especially when validating a new return or workstation. | **Stage** | **Confirm** | | --- | --- | | Before export | Supported worksheet workflow; Retrofit access; mapped drive available; permissions; actual Office Group ID; Return ID; exact identifying numbers; Entity ID; Activity Number and description; QBI setup; reviewed K-1 data. | | Before import | Correct intact ZIP; return calculated, saved, and closed; mapped drive available; authorized ProSystem fx user. | | After import | Correct return, entity, worksheet, and activity populated; representative federal, state, 199A, and K-3 values verified as applicable. |   - [General](https://support.k1x.io/general?hsLang=en-us#main-content) - [Account Management - SSO & Okta](https://support.k1x.io/general?hsLang=en-us#account-management-sso-okta) - [FAQ](https://support.k1x.io/general?hsLang=en-us#faq) - [Release Notes](https://support.k1x.io/general?hsLang=en-us#release-notes) - [K1 Aggregator](https://support.k1x.io/k1-aggregator?hsLang=en-us#main-content) - [Getting Started & Administration](https://support.k1x.io/k1-aggregator?hsLang=en-us#getting-started-administration) - [Core Workflows](https://support.k1x.io/k1-aggregator?hsLang=en-us#core-workflows) - [Reader Extraction & Document Upload](https://support.k1x.io/k1-aggregator?hsLang=en-us#reader-extraction-document-upload) - [Aggregator Modules - Investments](https://support.k1x.io/k1-aggregator?hsLang=en-us#aggregator-modules-investments) - [Aggregator Modules - Foreign Forms](https://support.k1x.io/k1-aggregator?hsLang=en-us#aggregator-modules-foreign-forms) - [Aggregator Modules - Reports and Exports](https://support.k1x.io/k1-aggregator?hsLang=en-us#aggregator-modules-reports-and-exports) - [K-1 Aggregator FAQ](https://support.k1x.io/k1-aggregator?hsLang=en-us#k-1-aggregator-faq) - [Integrations - CCH Axcess](https://support.k1x.io/k1-aggregator?hsLang=en-us#integrations-cch-axcess) - [Integrations - GoSystem](https://support.k1x.io/k1-aggregator?hsLang=en-us#integrations-gosystem) - [Integrations - UltraTax, Profx, OIT](https://support.k1x.io/k1-aggregator?hsLang=en-us#integrations-ultratax-profx-oit) - [Integrations - All Other](https://support.k1x.io/k1-aggregator?hsLang=en-us#integrations-all-other) - [990 Tracker](https://support.k1x.io/990-tracker?hsLang=en-us#main-content) - [990 Tracker FAQ](https://support.k1x.io/990-tracker?hsLang=en-us#990-tracker-faq) - [Federal Forms](https://support.k1x.io/990-tracker?hsLang=en-us#federal-forms) - [Federal Forms - 990-T](https://support.k1x.io/990-tracker?hsLang=en-us#federal-forms-990-t) - [Federal Forms - Form 990](https://support.k1x.io/990-tracker?hsLang=en-us#federal-forms-form-990) - [Federal Forms - Form 990 - Form 990 Schedules - Schedule A](https://support.k1x.io/990-tracker?hsLang=en-us#federal-forms-form-990-form-990-schedules-schedule-a) - [Federal Forms - Form 990 - Form 990 Schedules - Schedule B](https://support.k1x.io/990-tracker?hsLang=en-us#federal-forms-form-990-form-990-schedules-schedule-b) - [Federal Forms - Form 990 - Form 990 Schedules - Schedule C](https://support.k1x.io/990-tracker?hsLang=en-us#federal-forms-form-990-form-990-schedules-schedule-c) - [Federal Forms - Form 990 - Form 990 Schedules - Schedule D](https://support.k1x.io/990-tracker?hsLang=en-us#federal-forms-form-990-form-990-schedules-schedule-d) - [Federal Forms - Form 990 - Form 990 Schedules - Schedule K](https://support.k1x.io/990-tracker?hsLang=en-us#federal-forms-form-990-form-990-schedules-schedule-k) - [Federal Forms - Form 990 - Form 990 Schedules - Schedule R](https://support.k1x.io/990-tracker?hsLang=en-us#federal-forms-form-990-form-990-schedules-schedule-r) - [Federal Forms - Form 990 EZ](https://support.k1x.io/990-tracker?hsLang=en-us#federal-forms-form-990-ez) - [Federal Forms - Form 990 PF](https://support.k1x.io/990-tracker?hsLang=en-us#federal-forms-form-990-pf) - [Federal Forms - Other Federal Forms](https://support.k1x.io/990-tracker?hsLang=en-us#federal-forms-other-federal-forms) - [Electronic Filing](https://support.k1x.io/990-tracker?hsLang=en-us#electronic-filing) - [Modules](https://support.k1x.io/990-tracker?hsLang=en-us#modules) - [Modules - Conflict of Interest](https://support.k1x.io/990-tracker?hsLang=en-us#modules-conflict-of-interest) - [Modules - Master Compensation Module](https://support.k1x.io/990-tracker?hsLang=en-us#modules-master-compensation-module) - [State Forms](https://support.k1x.io/990-tracker?hsLang=en-us#state-forms) - [State Forms - Arizona](https://support.k1x.io/990-tracker?hsLang=en-us#state-forms-arizona) - [State Forms - Massachussets](https://support.k1x.io/990-tracker?hsLang=en-us#state-forms-massachussets) - [State Forms - Mississippi](https://support.k1x.io/990-tracker?hsLang=en-us#state-forms-mississippi) - [State Forms - New Mexico](https://support.k1x.io/990-tracker?hsLang=en-us#state-forms-new-mexico) - [State Forms - West Virginia](https://support.k1x.io/990-tracker?hsLang=en-us#state-forms-west-virginia) - [Troubleshooting](https://support.k1x.io/990-tracker?hsLang=en-us#troubleshooting) - [Troubleshooting - Federal](https://support.k1x.io/990-tracker?hsLang=en-us#troubleshooting-federal) - [Troubleshooting - Federal - Validation Errors](https://support.k1x.io/990-tracker?hsLang=en-us#troubleshooting-federal-validation-errors) - [Troubleshooting - Federal - Validation Errors - Form 990](https://support.k1x.io/990-tracker?hsLang=en-us#troubleshooting-federal-validation-errors-form-990) - [Troubleshooting - Federal - Validation Errors - Form 990-T](https://support.k1x.io/990-tracker?hsLang=en-us#troubleshooting-federal-validation-errors-form-990-t) - [Troubleshooting - Federal - Validation Errors - Form 990-PF](https://support.k1x.io/990-tracker?hsLang=en-us#troubleshooting-federal-validation-errors-form-990-pf) - [Troubleshooting - Federal - Validation Errors - Other Federal Forms](https://support.k1x.io/990-tracker?hsLang=en-us#troubleshooting-federal-validation-errors-other-federal-forms) - [Troubleshooting - Federal - Rejection Errors - Form 990](https://support.k1x.io/990-tracker?hsLang=en-us#troubleshooting-federal-rejection-errors-form-990) - [Troubleshooting - Federal - Rejection Errors - Form 990-T](https://support.k1x.io/990-tracker?hsLang=en-us#troubleshooting-federal-rejection-errors-form-990-t) - [Troubleshooting - Federal - Rejection Errors - Form 990-PF](https://support.k1x.io/990-tracker?hsLang=en-us#troubleshooting-federal-rejection-errors-form-990-pf) - [Troubleshooting - Federal - Rejection Errors - Other Federal Forms](https://support.k1x.io/990-tracker?hsLang=en-us#troubleshooting-federal-rejection-errors-other-federal-forms) - [Troubleshooting - State - Validation Errors](https://support.k1x.io/990-tracker?hsLang=en-us#troubleshooting-state-validation-errors) - [Troubleshooting - State - Rejection Errors](https://support.k1x.io/990-tracker?hsLang=en-us#troubleshooting-state-rejection-errors) - [North Caolina](https://support.k1x.io/990-tracker?hsLang=en-us#north-caolina) - [Forms & Schedules](https://support.k1x.io/990-tracker?hsLang=en-us#forms-schedules) - [K1 Creator](https://support.k1x.io/k1-creator?hsLang=en-us#main-content) - [Core Workflows](https://support.k1x.io/k1-creator?hsLang=en-us#core-workflows) [![k1x logo](https://support.k1x.io/hs-fs/hubfs/k1x%20logo.webp?width=65&height=65&name=k1x%20logo.webp "k1x logo")](https://k1x.io) Privacy Policy | Legal | © 2024 K1x. All Rights Reserved. Patented/Patent-pending AI automation technology | The Digital K-1 Exchange and Digital K-1 Filetype. US2022/0405453 | AI-powered engine to extract data for K-1 PDF. US 2021/0082062 | C-TRAC. US 2010/0010849 1 High Street Court, Morristown, NJ 07960