CCH Axcess Configuration
On 9/18/23, K1x's CCH integration was updated to use the CCH Marketplace integration. As part of this, no configuration is needed by clients in CCH to send data.
K1 Aggregator Configuration
All clients who use the CCH integration must have a subscription for the integration added to their tenant for K1 Aggregator. Without the subscription, you will not have the option to send K-1 data to CCH.
To send K-1 data to CCH for an instance, the CCH Return ID needs to be entered for each instance in K1 Aggregator.
The return ID can be found in this section of CCH in the 'RETURN ID' column.
If the Return ID is missing for any instance, an error will occur when attempting to send data for that instance.
Sending K-1 Data to CCH
Once all work is done in K1 Aggregator and you are ready to send K-1 data to CCH, navigate to the Home page.
To start the integration process, select which instances you would like to include and then select the bulk menu and Send Data to CCH Axcess.
This will initiate the integration request and take you to the integration wizard.
Step 1
The first step of the wizard is confirming the instances you selected to include in the integration request.
Step 2
The next step will be to select which investments to include.
A dropdown allows you to switch between instances being sent and investments for each instance can be checked/unchecked to include/exclude. By default, all investments are included.
Step 3
This step can be ignored, you should click next without making any changes on this page.
The Foreign Forms step is not currently support.
Step 4
The validation step will check that the required fields for the integration are populated with data.
This step does not validate the required fields matching to the CCH locator, it only validates that the fields are present in K1 Aggregator.
Click the 'Validate' button. Once validation is complete, click the 'Send Data' button.
Data will not be able to be sent until validation happens. If any required fields are missing, you can correct them on this page and revalidate.
Once all validation errors are addressed, you can select which status to update the investments to and send.
The send page will provide the status of the integration request and, if there are any errors or warnings, will display those once the integration request is complete.
Troubleshooting
FAQs
- What fields are required in K1 Aggregator to send K-1 data to CCH?
- Investment Name, Investment EIN, and Activity Number for each activity being sent must be entered in K1 Aggregator and match CCH. For each instance being sent, the Return ID from CCH must also be entered.
- Do I need to have the activity created in CCH before sending an activity from K1 Aggregator?
- Yes, the activities must already exist in CCH and the activity numbers entered in K1 Aggregator must match the activity you want to send K-1 data into.
- What's an Integrator Key and is it required?
- Early users of the CCH integration may have entered an integrator key with their Client ID and Client Secret. The use of the integrator key will be going away, but instructions on obtaining it for use can be found on CCH's Registering the Open Integration Kit page.
- All investments must have a unique name, otherwise you will receive an error during the validation step.
- How do I send data to a C-Corp 1120 entity? There is no activity number for these activities in CCH.
- When integrating a 1120 return, matching logic is based on the Partnership EIN, Partners EIN, and Partnership Name. These 3 fields must be populated in CCH and must match the investment in Aggregator for the integration to send data.
For mapping details, please refer to this article: K1 Aggregator to CCH Field Mappings